|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Novell Archives Archived content from Novell openSUSE support forums |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
The 8139too Drive int Suse 10.1 is broken. When you pass a lot of
traffic thru it becomes not responsive. In my enviorment I was doing a lot of scans with nessus and found that it is almost random but it will fail within a few minutes. I have also found that useing the pci=routeirq kernel option will delay the problem. If anyone knows a workaround or patch please let me know. Micha |
|
|||
|
micha@anscom.com wrote:
> The 8139too Drive int Suse 10.1 is broken. When you pass a lot of > traffic thru it becomes not responsive. In my enviorment I was doing a > lot of scans with nessus and found that it is almost random but it will > fail within a few minutes. I have also found that useing the > pci=routeirq kernel option will delay the problem. If anyone knows a > workaround or patch please let me know. > > Micha It is important driver and very old one, so it is very well tested and there should be no bugs (well, I know it can be). So before filling bug report on https://bugzilla.novell.com with network card problem, please check obvious: 1) Have you tested/used the same physical network configuration with some other SUSE version or even other distribution? What kernel and driver version was used? 2) How you have found that pci=routeirq might help? It is kernel parameter that has influence on all PCI devices, not only a network card. It could be some other problem that brings more problems including network adapter. 3) Have you checked hardware? Intermittent errors often have thermal or mechanical background. Loose connector, bad cable. Twisted pair cable has limited tolerance to twisting, nicking etc. Check light(s) on network adapter, before and after error appears. Red, orange or no light is not good. Steady green would be good. -- Regards, Rajko M. |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|