Thread: Re: ethernet driver(bug report)
Brought to you by:
aeb,
bencollins
Menu
▾
▴
linux1394-devel
|
From: Sebastien R. <Seb...@sy...> - 2000-05-11 04:17:37
|
>>>>> "Franck" == =?iso-8859-1?q?Franck=20Bonin?= <iso-8859-1> writes: Franck> Bug reporting with eth1394.c and ieee 1394 subsystem My Franck> Hardware/software Franck> 1) "Insmoding" 2 times the ohci module can crash one or the other Franck> PC... to avoid this problem I have to restart my computer if I want Franck> te re-insmod the ohci module. That's strange. Does it happen also if the pc is not connected on the bus ? Do you remove all the 1394 modules before insmoding ? I don't have a Pyro card here... anybody having the same problem ? Franck> 2) When I am using the ethernet driver with Pyro cards, I can Franck> succesfully ping others computers (flood ping works without any packet Franck> loss). Telnet is working fine, I can also start small X application Franck> like xcalc, xeyes or xclock. But, for exemple, if I was able to start Franck> bigger X applications with Adaptec HotConnect 8920 boards like Franck> Netscape or Xsoldier, It is no more possible with Pyro cards. So it is load related ? Franck> Few time after application start, one board stop receiving packets Franck> from the other board, as they still seem to be sent (by the other Franck> board), according to kernel messages output. Moreover, the failling Franck> card still can send packets. One thing I have noticed but haven't fixed yet is that the bottom halves in the irq handler are sometimes queued but not executed. You can try to call them directly (instead of queueing) and see if it helps. -- Sebastien Rougeaux RSISE, The Australian National University |
|
From: Mark K. <mk...@co...> - 2000-05-11 13:30:18
|
I have some Pyro cards here, both LV22 and LV 23 based. I have not built the kernel in awhile, so I need to do that, but if someone can give me the EXACT instructions for insmod'ing I will be happy to try it out. (I do mean exact! I'm a hardware guy! Take pity!) Let me know. Mark -----Original Message----- From: Sebastien Rougeaux [mailto:Seb...@sy...] Sent: Wednesday, May 10, 2000 9:18 PM To: fra...@ya... Cc: lin...@li... Subject: Re: ethernet driver(bug report) >>>>> "Franck" == =?iso-8859-1?q?Franck=20Bonin?= <iso-8859-1> writes: Franck> Bug reporting with eth1394.c and ieee 1394 subsystem My Franck> Hardware/software Franck> 1) "Insmoding" 2 times the ohci module can crash one or the other Franck> PC... to avoid this problem I have to restart my computer if I want Franck> te re-insmod the ohci module. That's strange. Does it happen also if the pc is not connected on the bus ? Do you remove all the 1394 modules before insmoding ? I don't have a Pyro card here... anybody having the same problem ? Franck> 2) When I am using the ethernet driver with Pyro cards, I can Franck> succesfully ping others computers (flood ping works without any packet Franck> loss). Telnet is working fine, I can also start small X application Franck> like xcalc, xeyes or xclock. But, for exemple, if I was able to start Franck> bigger X applications with Adaptec HotConnect 8920 boards like Franck> Netscape or Xsoldier, It is no more possible with Pyro cards. So it is load related ? Franck> Few time after application start, one board stop receiving packets Franck> from the other board, as they still seem to be sent (by the other Franck> board), according to kernel messages output. Moreover, the failling Franck> card still can send packets. One thing I have noticed but haven't fixed yet is that the bottom halves in the irq handler are sometimes queued but not executed. You can try to call them directly (instead of queueing) and see if it helps. -- Sebastien Rougeaux RSISE, The Australian National University _______________________________________________ mailing list lin...@li... http://lists.sourceforge.net/mailman/listinfo/linux1394-devel |
|
From: <fra...@ya...> - 2000-05-11 14:03:41
|
I may have found when exactly this bug append. Just try this : 1) insmod all the ieee 1394 modules (ieee1394, raw1394 & ohci1394) 2) delmod all the 3 modules. 3) generate a bus reset (by unplugging 1394 cables or insmoding ieee 1394 modules on another node) 4) re-insmod all the 3 modules... 5) CRASH! This bug is repetable as well with my ADS PYRO cards. --- Franck Bonin <Seb...@sy...> a écrit : > >>>>> "Franck" == =?iso-8859-1?q?Franck=20Bonin?= > <iso-8859-1> writes: > > Franck> Bug reporting with eth1394.c and ieee 1394 > subsystem My > Franck> Hardware/software > > Franck> 1) "Insmoding" 2 times the ohci module can > crash one or the other > Franck> PC... to avoid this problem I have to > restart my computer if I want > Franck> te re-insmod the ohci module. > > That's strange. Does it happen also if the pc is not > connected on the > bus ? Do you remove all the 1394 modules before > insmoding ? I don't > have a Pyro card here... anybody having the same > problem ? ___________________________________________________________ Do You Yahoo!? Achetez, vendez! À votre prix! Sur http://encheres.yahoo.fr |
|
From: Sebastien R. <Seb...@sy...> - 2000-05-12 02:20:55
|
>>>>> "Franck" == =?iso-8859-1?q?Franck=20Bonin?= <iso-8859-1> writes: Franck> I may have found when exactly this bug append. Just try this : Franck> 1) insmod all the ieee 1394 modules (ieee1394, raw1394 & ohci1394) Franck> 2) delmod all the 3 modules. Franck> 3) generate a bus reset (by unplugging 1394 cables or insmoding ieee Franck> 1394 modules on another node) Franck> 4) re-insmod all the 3 modules... Franck> 5) CRASH! Franck> This bug is repetable as well with my ADS PYRO cards. It should be fixed now in the latest CVS version. The reason for this is that the board was not reset properly when unloading the driver. Thanks a lot for your bug report, -- Sebastien Rougeaux RSISE, The Australian National University |
|
From: <fra...@ya...> - 2000-05-11 14:03:47
|
I may have found when exactly this bug append. Just try this : 1) insmod all the ieee 1394 modules (ieee1394, raw1394 & ohci1394) 2) delmod all the 3 modules. 3) generate a bus reset (by unplugging 1394 cables or insmoding ieee 1394 modules on another node) 4) re-insmod all the 3 modules... 5) CRASH! This bug is repetable as well with my ADS PYRO cards. --- Franck Bonin <Seb...@sy...> a écrit : > >>>>> "Franck" == =?iso-8859-1?q?Franck=20Bonin?= > <iso-8859-1> writes: > > Franck> Bug reporting with eth1394.c and ieee 1394 > subsystem My > Franck> Hardware/software > > Franck> 1) "Insmoding" 2 times the ohci module can > crash one or the other > Franck> PC... to avoid this problem I have to > restart my computer if I want > Franck> te re-insmod the ohci module. > > That's strange. Does it happen also if the pc is not > connected on the > bus ? Do you remove all the 1394 modules before > insmoding ? I don't > have a Pyro card here... anybody having the same > problem ? ___________________________________________________________ Do You Yahoo!? Achetez, vendez! À votre prix! Sur http://encheres.yahoo.fr |
Thanks for helping keep SourceForge clean.
X