Re: NETDEV WATCHDOG: eth2: transmit timed out with 3c905C-TX
Steffen Klassert wrote: On Tue, Jun 06, 2006 at 11:12:45AM +0200, Marco Berizzi wrote: I have moved this damn pc from the remote to my site and I have placed it in production environment with 2.6.17-rc5 No problem after 24 hours (on the remote side the problem was arising after a couple of hours). I have modprobed 3c59x with debug=4. I see only these kind of messages (are they fine?): Jun 5 14:31:25 Pleiadi kernel: eth2: vortex_error(), status=0x8081 Jun 5 14:31:40 Pleiadi last message repeated 3 times Jun 5 14:31:47 Pleiadi kernel: eth2: vortex_error(), status=0x8281 Jun 5 14:31:47 Pleiadi kernel: eth2: Media selection timer tick happened, Autonegotiate. Jun 5 14:31:47 Pleiadi kernel: dev-watchdog_timeo=1250 Jun 5 14:31:47 Pleiadi kernel: eth2: MII transceiver has status 782d. Jun 5 14:31:47 Pleiadi kernel: eth2: Media selection timer finished, Autonegotiate. Jun 5 14:31:51 Pleiadi kernel: eth2: vortex_error(), status=0x8081 Jun 5 14:32:03 Pleiadi last message repeated 2 times Jun 5 14:32:10 Pleiadi kernel: eth2: vortex_error(), status=0x8481 Jun 5 14:32:15 Pleiadi kernel: eth2: vortex_error(), status=0x8081 Jun 5 14:32:46 Pleiadi last message repeated 7 times This is ok, just normal operation of the NIC. The only relevant change, between the remote and my site, is a different ethernet switch where the 3c905C is connected to. Could it be an issue? Well, I think it can. Problems with a switch are mostly related to the autonegotiation of the media type and full/half-duplex. But in your case the autonegotiation seems to be ok (mii-tool/ethtool output). More specific information you can get with the mii-diag and vortex-diag tools. You can find these tools at http://www.scyld.com/ethercard_diag.html There are problems with a cisco switch documented in Documentation/networking/vortex.txt for example. [moved again this pc to the original site] I have modprobed 3c59x with debug=6 and after a while (about 100 minutes) this error has been arised. Here is the log. Doy you see anything relevant? I don't understand why running an ifconfig eth2 down/up 'resolves' the issue for another 100 minutes. Jun 16 14:01:34 Teti kernel: eth2: interrupt, status 8401, latency 2 ticks. Jun 16 14:01:34 Teti kernel: eth2: In interrupt loop, status 8401. Jun 16 14:01:34 Teti kernel: boomerang_interrupt-boomerang_rx Jun 16 14:01:34 Teti kernel: boomerang_rx(): status 8001 Jun 16 14:01:34 Teti kernel: Receiving packet size 60 status a000803c. Jun 16 14:01:34 Teti kernel: eth2: exiting interrupt, status 8000. Jun 16 14:01:34 Teti kernel: eth2: interrupt, status 8401, latency 1 ticks. Jun 16 14:01:34 Teti kernel: eth2: In interrupt loop, status 8401. Jun 16 14:01:34 Teti kernel: boomerang_interrupt-boomerang_rx Jun 16 14:01:34 Teti kernel: boomerang_rx(): status 8001 Jun 16 14:01:34 Teti kernel: Receiving packet size 60 status 803c. Jun 16 14:01:34 Teti kernel: eth2: exiting interrupt, status 8000. Jun 16 14:01:36 Teti kernel: eth2: interrupt, status 8401, latency 2 ticks. Jun 16 14:01:36 Teti kernel: eth2: In interrupt loop, status 8401. Jun 16 14:01:36 Teti kernel: boomerang_interrupt-boomerang_rx Jun 16 14:01:36 Teti kernel: boomerang_rx(): status 8001 Jun 16 14:01:36 Teti kernel: Receiving packet size 82 status 60008052. Jun 16 14:01:36 Teti kernel: eth2: exiting interrupt, status 8000. Jun 16 14:01:36 Teti kernel: eth2: interrupt, status 8401, latency 2 ticks. Jun 16 14:01:36 Teti kernel: eth2: In interrupt loop, status 8401. Jun 16 14:01:36 Teti kernel: boomerang_interrupt-boomerang_rx Jun 16 14:01:36 Teti kernel: boomerang_rx(): status 8001 Jun 16 14:01:36 Teti kernel: Receiving packet size 60 status 803c. Jun 16 14:01:36 Teti kernel: eth2: exiting interrupt, status 8000. Jun 16 14:01:38 Teti kernel: eth2: interrupt, status 8401, latency 2 ticks. Jun 16 14:01:38 Teti kernel: eth2: In interrupt loop, status 8401. Jun 16 14:01:38 Teti kernel: boomerang_interrupt-boomerang_rx Jun 16 14:01:38 Teti kernel: boomerang_rx(): status 8001 Jun 16 14:01:38 Teti kernel: Receiving packet size 60 status 6000803c. Jun 16 14:01:38 Teti kernel: eth2: exiting interrupt, status 8000. Jun 16 14:01:39 Teti kernel: NETDEV WATCHDOG: eth2: transmit timed out Jun 16 14:01:39 Teti kernel: eth2: transmit timed out, tx_status 00 status 8000. Jun 16 14:01:39 Teti kernel: diagnostics: net 0ccc media 8880 dma 00a0 fifo Jun 16 14:01:39 Teti kernel: Flags; bus-master 1, dirty 10411(11) current 10427(11) Jun 16 14:01:39 Teti kernel: Transmit list 159258e0 vs. d59258e0. Jun 16 14:01:39 Teti kernel: 0: @d5925200 length 8086 status 0086 Jun 16 14:01:39 Teti kernel: 1: @d59252a0 length 80ec status 00ec Jun 16 14:01:39 Teti kernel: 2: @d5925340 length 803f status 003f Jun 16 14:01:39 Teti kernel: 3: @d59253e0 length 80ec status 00ec Jun 16 14:01:39 Teti kernel: 4: @d5925480 length 803f status 003f Jun 16 14:01:39 Teti kernel: 5: @d5925520 length
Re: NETDEV WATCHDOG: eth2: transmit timed out with 3c905C-TX
Steffen Klassert wrote: On Tue, May 23, 2006 at 03:36:35PM +0200, Marco Berizzi wrote: Steffen Klassert wrote: On Wed, Apr 05, 2006 at 06:33:18PM +0200, Marco Berizzi wrote: Hello everybody. I'm getting these errors (with packet/connectivity loss) on our firewall after I have plugged in a 3c905C nic. Linux is Slackware 10.2 with vanilla 2.6.16.1. Hints? PS: I have temporary resolved the problem running 'ifconfig eth2 down' and 'ifconfig eth2 up' Apr 5 17:47:07 Teti kernel: eth2: Resetting the Tx ring pointer. Apr 5 17:47:47 Teti last message repeated 4 times Apr 5 17:48:57 Teti last message repeated 7 times Apr 5 17:49:57 Teti last message repeated 6 times Apr 5 17:50:57 Teti last message repeated 6 times Apr 5 17:47:07 Teti kernel: NETDEV WATCHDOG: eth2: transmit timed out There were some problems of this kind with 10base2 networks in 2.6.16. Could you please try whether 2.6.17-rc1 has this problems too? [Sorry for the very huge delay, but after 2.6.17-rc1 upgrade xfs filesystem crashed]. Same problem here with 2.6.17-rc3-git18. Running ifconfig eth2 down and ifconfig eth2 up resolves the problem for a while. Actually I have not really an idea what is going on here, but increasing the debug level could give some more informations. Setting debug=4 is a good start. I have moved this damn pc from the remote to my site and I have placed it in production environment with 2.6.17-rc5 No problem after 24 hours (on the remote side the problem was arising after a couple of hours). I have modprobed 3c59x with debug=4. I see only these kind of messages (are they fine?): Jun 5 14:31:25 Pleiadi kernel: eth2: vortex_error(), status=0x8081 Jun 5 14:31:40 Pleiadi last message repeated 3 times Jun 5 14:31:47 Pleiadi kernel: eth2: vortex_error(), status=0x8281 Jun 5 14:31:47 Pleiadi kernel: eth2: Media selection timer tick happened, Autonegotiate. Jun 5 14:31:47 Pleiadi kernel: dev-watchdog_timeo=1250 Jun 5 14:31:47 Pleiadi kernel: eth2: MII transceiver has status 782d. Jun 5 14:31:47 Pleiadi kernel: eth2: Media selection timer finished, Autonegotiate. Jun 5 14:31:51 Pleiadi kernel: eth2: vortex_error(), status=0x8081 Jun 5 14:32:03 Pleiadi last message repeated 2 times Jun 5 14:32:10 Pleiadi kernel: eth2: vortex_error(), status=0x8481 Jun 5 14:32:15 Pleiadi kernel: eth2: vortex_error(), status=0x8081 Jun 5 14:32:46 Pleiadi last message repeated 7 times The only relevant change, between the remote and my site, is a different ethernet switch where the 3c905C is connected to. Could it be an issue? Did you try older kernel versions too? I started with 2.6.16.x because I need iptables policy match. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: NETDEV WATCHDOG: eth2: transmit timed out with 3c905C-TX
On Tue, Jun 06, 2006 at 11:12:45AM +0200, Marco Berizzi wrote: I have moved this damn pc from the remote to my site and I have placed it in production environment with 2.6.17-rc5 No problem after 24 hours (on the remote side the problem was arising after a couple of hours). I have modprobed 3c59x with debug=4. I see only these kind of messages (are they fine?): Jun 5 14:31:25 Pleiadi kernel: eth2: vortex_error(), status=0x8081 Jun 5 14:31:40 Pleiadi last message repeated 3 times Jun 5 14:31:47 Pleiadi kernel: eth2: vortex_error(), status=0x8281 Jun 5 14:31:47 Pleiadi kernel: eth2: Media selection timer tick happened, Autonegotiate. Jun 5 14:31:47 Pleiadi kernel: dev-watchdog_timeo=1250 Jun 5 14:31:47 Pleiadi kernel: eth2: MII transceiver has status 782d. Jun 5 14:31:47 Pleiadi kernel: eth2: Media selection timer finished, Autonegotiate. Jun 5 14:31:51 Pleiadi kernel: eth2: vortex_error(), status=0x8081 Jun 5 14:32:03 Pleiadi last message repeated 2 times Jun 5 14:32:10 Pleiadi kernel: eth2: vortex_error(), status=0x8481 Jun 5 14:32:15 Pleiadi kernel: eth2: vortex_error(), status=0x8081 Jun 5 14:32:46 Pleiadi last message repeated 7 times This is ok, just normal operation of the NIC. The only relevant change, between the remote and my site, is a different ethernet switch where the 3c905C is connected to. Could it be an issue? Well, I think it can. Problems with a switch are mostly related to the autonegotiation of the media type and full/half-duplex. But in your case the autonegotiation seems to be ok (mii-tool/ethtool output). More specific information you can get with the mii-diag and vortex-diag tools. You can find these tools at http://www.scyld.com/ethercard_diag.html There are problems with a cisco switch documented in Documentation/networking/vortex.txt for example. Steffen - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: NETDEV WATCHDOG: eth2: transmit timed out with 3c905C-TX
Steffen Klassert wrote: On Wed, Apr 05, 2006 at 06:33:18PM +0200, Marco Berizzi wrote: Hello everybody. I'm getting these errors (with packet/connectivity loss) on our firewall after I have plugged in a 3c905C nic. Linux is Slackware 10.2 with vanilla 2.6.16.1. Hints? PS: I have temporary resolved the problem running 'ifconfig eth2 down' and 'ifconfig eth2 up' Apr 5 17:47:07 Teti kernel: eth2: Resetting the Tx ring pointer. Apr 5 17:47:47 Teti last message repeated 4 times Apr 5 17:48:57 Teti last message repeated 7 times Apr 5 17:49:57 Teti last message repeated 6 times Apr 5 17:50:57 Teti last message repeated 6 times Apr 5 17:47:07 Teti kernel: NETDEV WATCHDOG: eth2: transmit timed out There were some problems of this kind with 10base2 networks in 2.6.16. Could you please try whether 2.6.17-rc1 has this problems too? [Sorry for the very huge delay, but after 2.6.17-rc1 upgrade xfs filesystem crashed]. Same problem here with 2.6.17-rc3-git18. Running ifconfig eth2 down and ifconfig eth2 up resolves the problem for a while. Here is lspci -v and dmesg [EMAIL PROTECTED]:/var/log# lspci -v 00:00.0 Host bridge: Intel Corporation 82810E DC-133 GMCH [Graphics Memory Controller Hub] (rev 03) Flags: bus master, fast devsel, latency 0 00:01.0 VGA compatible controller: Intel Corporation 82810E DC-133 CGC [Chipset Graphics Controller] (rev 03) (prog-if 00 [VGA]) Subsystem: Siemens Nixdorf AG: Unknown device 004a Flags: bus master, 66Mhz, medium devsel, latency 0, IRQ 10 Memory at f800 (32-bit, prefetchable) [size=64M] Memory at f400 (32-bit, non-prefetchable) [size=512K] Expansion ROM at unassigned [disabled] Capabilities: [dc] Power Management version 1 00:1e.0 PCI bridge: Intel Corporation 82801AA PCI Bridge (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=80 I/O behind bridge: 2000-2fff Memory behind bridge: f410-f41f Prefetchable memory behind bridge: 2000-200f 00:1f.0 ISA bridge: Intel Corporation 82801AA ISA Bridge (LPC) (rev 02) Flags: bus master, medium devsel, latency 0 00:1f.1 IDE interface: Intel Corporation 82801AA IDE (rev 02) (prog-if 80 [Master]) Subsystem: Intel Corporation 82801AA IDE Flags: bus master, medium devsel, latency 0 I/O ports at 1000 [size=16] 00:1f.2 USB Controller: Intel Corporation 82801AA USB (rev 02) (prog-if 00 [UHCI]) Subsystem: Intel Corporation 82801AA USB Flags: bus master, medium devsel, latency 0, IRQ 9 I/O ports at 1400 [size=32] 00:1f.3 SMBus: Intel Corporation 82801AA SMBus (rev 02) Subsystem: Intel Corporation 82801AA SMBus Flags: medium devsel, IRQ 11 I/O ports at 1800 [size=16] 01:05.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX (rev 10) Subsystem: Accton Technology Corporation EN-1207D Fast Ethernet Adapter Flags: bus master, medium devsel, latency 64, IRQ 10 I/O ports at 2000 [size=256] Memory at f410 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 1 01:07.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX (rev 10) Subsystem: Accton Technology Corporation EN-1207D Fast Ethernet Adapter Flags: bus master, medium devsel, latency 64, IRQ 11 I/O ports at 2400 [size=256] Memory at f4100400 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 2 01:09.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78) Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management NIC Flags: bus master, medium devsel, latency 80, IRQ 7 I/O ports at 2800 [size=128] Memory at f4100800 (32-bit, non-prefetchable) [size=128] Expansion ROM at 2000 [disabled] [size=128K] Capabilities: [dc] Power Management version 2 Linux version 2.6.17-rc3-git18 ([EMAIL PROTECTED]) (gcc version 3.3.6) #1 Thu May 11 11:15:45 CEST 2006 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e6800 - 0010 (reserved) BIOS-e820: 0010 - 17ef (usable) BIOS-e820: 17ef - 17effc00 (ACPI data) BIOS-e820: 17effc00 - 17f0 (ACPI NVS) BIOS-e820: 17f0 - 1800 (reserved) BIOS-e820: fff0 - 0001 (reserved) 382MB LOWMEM available. On node 0 totalpages: 98032 DMA zone: 4096 pages, LIFO batch:0 Normal zone: 93936 pages, LIFO batch:31 DMI 2.3 present. Allocating PCI resources starting at 2000 (gap: 1800:e7f0) Built 1 zonelists Kernel command line: auto BOOT_IMAGE=Linux ro root=301 Local APIC disabled by BIOS -- you can
Re: NETDEV WATCHDOG: eth2: transmit timed out with 3c905C-TX
On Tue, May 23, 2006 at 03:36:35PM +0200, Marco Berizzi wrote: Steffen Klassert wrote: On Wed, Apr 05, 2006 at 06:33:18PM +0200, Marco Berizzi wrote: Hello everybody. I'm getting these errors (with packet/connectivity loss) on our firewall after I have plugged in a 3c905C nic. Linux is Slackware 10.2 with vanilla 2.6.16.1. Hints? PS: I have temporary resolved the problem running 'ifconfig eth2 down' and 'ifconfig eth2 up' Apr 5 17:47:07 Teti kernel: eth2: Resetting the Tx ring pointer. Apr 5 17:47:47 Teti last message repeated 4 times Apr 5 17:48:57 Teti last message repeated 7 times Apr 5 17:49:57 Teti last message repeated 6 times Apr 5 17:50:57 Teti last message repeated 6 times Apr 5 17:47:07 Teti kernel: NETDEV WATCHDOG: eth2: transmit timed out There were some problems of this kind with 10base2 networks in 2.6.16. Could you please try whether 2.6.17-rc1 has this problems too? [Sorry for the very huge delay, but after 2.6.17-rc1 upgrade xfs filesystem crashed]. Same problem here with 2.6.17-rc3-git18. Running ifconfig eth2 down and ifconfig eth2 up resolves the problem for a while. Actually I have not really an idea what is going on here, but increasing the debug level could give some more informations. Setting debug=4 is a good start. Did you try older kernel versions too? Steffen - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: NETDEV WATCHDOG: eth2: transmit timed out with 3c905C-TX
On Wed, Apr 05, 2006 at 06:33:18PM +0200, Marco Berizzi wrote: Hello everybody. I'm getting these errors (with packet/connectivity loss) on our firewall after I have plugged in a 3c905C nic. Linux is Slackware 10.2 with vanilla 2.6.16.1. Hints? PS: I have temporary resolved the problem running 'ifconfig eth2 down' and 'ifconfig eth2 up' Apr 5 17:47:07 Teti kernel: eth2: Resetting the Tx ring pointer. Apr 5 17:47:47 Teti last message repeated 4 times Apr 5 17:48:57 Teti last message repeated 7 times Apr 5 17:49:57 Teti last message repeated 6 times Apr 5 17:50:57 Teti last message repeated 6 times Apr 5 17:47:07 Teti kernel: NETDEV WATCHDOG: eth2: transmit timed out There were some problems of this kind with 10base2 networks in 2.6.16. Could you please try whether 2.6.17-rc1 has this problems too? Steffen - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
