Wed, Jan 09, 2002 at 10:08:55AM +0100, Dennis Schoen wrote: > yesterday I upgraded a firewall/router of a *busy* customer site > from version 2.4.7 -> 2.4.17. Only 1-2 seconds after the reboot the > network card to the DMZ stopped working. I noticed this messages in > /var/log/messages: > > Jan 8 17:07:45 liquice kernel: 8139too: rx stop wait too long > Jan 8 17:07:46 liquice kernel: eth1: Too much work at interrupt, IntrStatus=0x0050. > Jan 8 17:07:46 liquice kernel: eth1: Too much work at interrupt, IntrStatus=0x0010. > Jan 8 17:07:49 liquice kernel: 8139too: rx stop wait too long > Jan 8 17:07:49 liquice kernel: eth1: Too much work at interrupt, IntrStatus=0x0001. > Jan 8 17:07:51 liquice kernel: eth1: Too much work at interrupt, IntrStatus=0x0001. > Jan 8 17:07:57 liquice kernel: eth1: Too much work at interrupt, IntrStatus=0x0050. > Jan 8 17:07:57 liquice kernel: eth1: Setting 100mbps half-duplex based on auto-negotiated partner ability 40a1. > Jan 8 17:08:09 liquice kernel: NETDEV WATCHDOG: eth1: transmit timed out > Jan 8 17:08:09 liquice kernel: eth1: Setting 100mbps half-duplex based on auto-negotiated partner ability ffff. > > after a reboot the same problem occured. > > Switching back to v2.4.7 solved the problem so I don't think that > it's a hardware issue. Hi dennis, I'm getting these messages too with an identical card... 8139 (rev 10)... seems to have started happening after I went to 2.4.17... strangely enough I'm getting very similar męssages on the machine right beside it.. running 2.4.13, SMP, and a 3com 3c905b (Boomerang). Anyone have any insight on this one? -- Patrick Cole - Debian Developer - John Curtin, ANU - Linear-G Network Solutions - PGP 1024R/60D74C7D C8E0BC7969BE7899AA0FEB16F84BFE5A