Well, finally applied the 8.0.16 driver and before updated the kernel to : 2.6.27.35-170.2.94.fc10.i686.
Restarted the firewall so the newly installed kernel would run, compiled the driver and installed it. filename: /lib/modules/2.6.27.35-170.2.94.fc10.i686/kernel/ drivers/net/e1000/e1000.ko version: 8.0.16-NAPI license: GPL description: Intel(R) PRO/1000 Network Driver author: Intel Corporation, <linux.n...@intel.com> srcversion: D8FA73DEE439DF241A1B835 Issued a "modprobe e1000 TxDescriptorStep=4,4,4" and executed my firewall script that also configures the interfaces. This was early this morning. Now, just recently I got the TX Unit Hang again on eth0 interface (the public interface) : ( Same as usual, no traffic in or out ). had to re-execute the firewall script to Oct 6 15:32:54 localhost kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Oct 6 15:32:54 localhost kernel: Tx Queue <0> Oct 6 15:32:54 localhost kernel: TDH <49> Oct 6 15:32:54 localhost kernel: TDT <2d> Oct 6 15:32:54 localhost kernel: next_to_use <2d> Oct 6 15:32:54 localhost kernel: next_to_clean <49> Oct 6 15:32:54 localhost kernel: buffer_info[next_to_clean] Oct 6 15:32:54 localhost kernel: time_stamp <1632f1c> Oct 6 15:32:54 localhost kernel: next_to_watch <49> Oct 6 15:32:54 localhost kernel: jiffies <1633598> Oct 6 15:32:54 localhost kernel: next_to_watch.status <0> Oct 6 15:33:30 localhost kernel: ------------[ cut here ]------------ Oct 6 15:33:30 localhost kernel: WARNING: at net/sched/sch_generic.c: 219 dev_watchdog+0xda/0x12d() Oct 6 15:33:30 localhost kernel: Hardware name: System Product Name Oct 6 15:33:30 localhost kernel: NETDEV WATCHDOG: eth0 (e1000): transmit timed out Oct 6 15:33:30 localhost kernel: Modules linked in: e1000 sit tunnel4 xt_multiport act_nat nf_nat_tftp nf_nat_proto_sctp libcrc32c nf_nat_pptp nf_nat_proto_gre nf_nat_proto_udplite nf_nat_proto_dccp nf_nat_h323 nf_nat_sip nf_nat_snmp_basic nf_nat_amanda nf_nat_irc nf_nat_ftp ebt_snat ebtable_nat ebt_dnat ebtables nf_conntrack_ipv6 nf_conntrack_netlink nfnetlink ts_kmp nf_conntrack_amanda nf_conntrack_tftp nf_conntrack_ftp nf_conntrack_sane nf_conntrack_irc nf_conntrack_netbios_ns nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_proto_dccp nf_conntrack_proto_sctp nf_conntrack_h323 nf_conntrack_proto_udplite ipt_MASQUERADE iptable_nat nf_nat bridge stp bnep sco l2cap bluetooth sunrpc ipv6 dm_multipath uinput snd_via82xx_modem snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_via82xx snd_pcm_oss gameport snd_ac97_codec snd_mixer_oss ac97_bus snd_mpu401_uart snd_rawmidi snd_pcm snd_timer snd_page_alloc k8temp snd_seq_device snd soundcore hwmon sata_via via_rhine mii i2c_viapro i2c_core pcs Oct 6 15:33:30 localhost kernel: pkr floppy ata_generic pata_acpi pata_via [last unloaded: e1000] Oct 6 15:33:30 localhost kernel: Pid: 0, comm: swapper Not tainted 2.6.27.35-170.2.94.fc10.i686 #1 Oct 6 15:33:30 localhost kernel: [<c042db2c>] warn_slowpath+0x69/0x89 Oct 6 15:33:30 localhost kernel: [<c06555b9>] ? ip_rcv_finish +0x279/0x28f Oct 6 15:33:30 localhost kernel: [<c06557bc>] ? ip_rcv+0x1ed/0x217 Oct 6 15:33:30 localhost kernel: [<f8921019>] ? e1000_alloc_rx_buffers +0x176/0x26d [e1000] Oct 6 15:33:30 localhost kernel: [<f8921430>] ? e1000_clean_rx_irq +0x320/0x348 [e1000] Oct 6 15:33:30 localhost kernel: [<c051f076>] ? strlcpy+0x17/0x49 Oct 6 15:33:30 localhost kernel: [<c064295c>] dev_watchdog+0xda/0x12d Oct 6 15:33:30 localhost kernel: [<c0436415>] run_timer_softirq+0x14b/ 0x1bb Oct 6 15:33:30 localhost kernel: [<c0642882>] ? dev_watchdog+0x0/0x12d Oct 6 15:33:30 localhost kernel: [<c0642882>] ? dev_watchdog+0x0/0x12d Oct 6 15:33:30 localhost kernel: [<c043276f>] __do_softirq+0x84/0x109 Oct 6 15:33:30 localhost kernel: [<c04326eb>] ? __do_softirq+0x0/0x109 Oct 6 15:33:30 localhost kernel: [<c0406f1c>] do_softirq+0x77/0xdb Oct 6 15:33:30 localhost kernel: [<c04323d6>] irq_exit+0x44/0x83 Oct 6 15:33:30 localhost kernel: [<c04152ed>] smp_apic_timer_interrupt +0x6e/0x7c Oct 6 15:33:30 localhost kernel: [<c040576d>] apic_timer_interrupt +0x2d/0x34 Oct 6 15:33:30 localhost kernel: [<c041b74f>] ? native_safe_halt +0x5/0x7 Oct 6 15:33:30 localhost kernel: [<c040a15d>] default_idle+0x38/0x6a Oct 6 15:33:30 localhost kernel: [<c0403c61>] cpu_idle+0x101/0x134 Oct 6 15:33:30 localhost kernel: [<c069baba>] rest_init+0x4e/0x50 Oct 6 15:33:30 localhost kernel: ======================= Oct 6 15:33:30 localhost kernel: ---[ end trace 43db0b9a0fcf53c2 ]--- Oct 6 15:33:32 localhost kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX Oct 6 15:37:34 localhost kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX Could this be releated to a very high traffic on my public interface. Becouse, just at that moment my collegue downloaded from one of my FTP servers trough my firewall at ~11.1 MB/s That was about 15:30 or so, and this TX Unit problem came at 15:32 or so. Should I disable TSO for the adapters ? ethtool -K eth0 tso off ethtool -K eth1 tso off ethtool -K eth2 tso off Also, My firewall public interface is connected to HP Procurve 2524 switch. Thanks in advance. Best regards, Svavar O Reykjavik - Iceland ______________________________________ FITON : AUGLÝSINGASTOFA SVAVAR ÖRN EYSTEINSSON KERFISSTJÓRI / SYSTEM ADMINISTRATOR GARÐASTRÆTI 37 101 REYKJAVÍK ICELAND TEL +354 595 3600 GSM +354 862 1624 WWW.FITON.IS ______________________________________ On 1.10.2009, at 22:48, Graham, David wrote: > Hi Svavar, > This looks like a problem that we have seen before on similar > platforms, and I'm hoping that the workaround we have already > provided will resolve the issue. Please follow these steps and let > us know. > > First, we will need to update your driver version from 8.0.6 to the > latest, which includes the workaround. > Please download the e1000-8.0.16 driver from the e1000 sourceforge > site. You'll see the driver tarball when you click on the e1000 > stable link at https://sourceforge.net/projects/e1000/files/ > > Extract the tarball > > tar xvzf e1000-8.0.16.tar.gz > > Build it > cd e1000-8.0.16/src > make > > Install using the new TxDescriptorStep parameter for each of your 3 > interfaces to activate the workaround. > > modprobe e1000 TxDescriptorStep=4,4,4 > > > Bring the interfaces up and retest. > > Please let me know if you need more detail, and I will be glad to > help further. > > Dave > > > -----Original Message----- > From: Svavar Örn Eysteinsson [mailto:sva...@fiton.is] > Sent: Thursday, October 01, 2009 4:43 AM > To: e1000-devel@lists.sourceforge.net > Subject: [E1000-devel] TX Unit hang with Intel Pro/1000 (82541PI) > (e1000) driver on Firewall/NAT machine. Help needed > > Hi. > I'm having a very serious trouble with TX Unit Hang on my Firewall/NAT > machine that serves > 100 pc's and devices and 4 networks. > > The machine has 1.5GB in RAM, AMD Sempron(tm) Processor 2600+ at > 1.6Ghz. > The network cards consist of 3 pieces of Intel Pro/1000 GT Desktop > Adapters 82541PI (rev 05), > and one VIA [Rhine-II] network card. > > My OS is Fedora 10, with 2.6.27.15-170 KERNEL. > My e1000 driver is 8.0.6-NAPI > Iptables is 1.4.1.1 > > > To my problem. Every now and then, I get a "TX Unit Hang" on mostly on > my ETH1 > interface (that is a internal interface) but now these days I'm > getting it at my EXTERNAL > interface (eth0). > > When this Tx Unit Hangs comes up. No traffic is generated in or out on > my firewall machine. > To fix the problem I have to relaunch the Firewall script. Script > generated by Fwbuilder. > When the script has relaunched all traffic is normal. > > We also host many WWW servers, and email servers. I' have recently > inserted a scheduled > cron job to relaunch the firewall script at 1hour basis, but that is > not a solution > for this problem. > > Can someone help me out, or give me some information regarding this > annoying problem. > > Thanks in advance. > > Best regards, > > Svavar O > Reykjavik - Iceland. > > > < Here's my messages.log output > > > Sep 30 00:33:20 localhost kernel: e1000: eth0: e1000_clean_tx_irq: > Detected Tx Unit Hang > Sep 30 00:33:20 localhost kernel: Tx Queue <0> > Sep 30 00:33:20 localhost kernel: TDH <c3> > Sep 30 00:33:20 localhost kernel: TDT <c3> > Sep 30 00:33:20 localhost kernel: next_to_use <c3> > Sep 30 00:33:20 localhost kernel: next_to_clean <d7> > Sep 30 00:33:20 localhost kernel: buffer_info[next_to_clean] > Sep 30 00:33:20 localhost kernel: time_stamp <dae9c1d0> > Sep 30 00:33:20 localhost kernel: next_to_watch <d7> > Sep 30 00:33:20 localhost kernel: jiffies <dae9cb38> > Sep 30 00:33:20 localhost kernel: next_to_watch.status <0> > Sep 30 00:33:22 localhost kernel: e1000: eth0: e1000_clean_tx_irq: > Detected Tx Unit Hang > Sep 30 00:33:22 localhost kernel: Tx Queue <0> > Sep 30 00:33:22 localhost kernel: TDH <c3> > Sep 30 00:33:22 localhost kernel: TDT <c3> > Sep 30 00:33:22 localhost kernel: next_to_use <c3> > Sep 30 00:33:22 localhost kernel: next_to_clean <d7> > Sep 30 00:33:22 localhost kernel: buffer_info[next_to_clean] > Sep 30 00:33:22 localhost kernel: time_stamp <dae9c1d0> > Sep 30 00:33:22 localhost kernel: next_to_watch <d7> > Sep 30 00:33:22 localhost kernel: jiffies <dae9d308> > Sep 30 00:33:22 localhost kernel: next_to_watch.status <0> > > Oct 1 11:17:31 localhost kernel: e1000: eth0: e1000_clean_tx_irq: > Detected Tx Unit Hang > Oct 1 11:17:31 localhost kernel: Tx Queue <0> > Oct 1 11:17:31 localhost kernel: TDH <e2> > Oct 1 11:17:31 localhost kernel: TDT <e2> > Oct 1 11:17:31 localhost kernel: next_to_use <e2> > Oct 1 11:17:31 localhost kernel: next_to_clean <f6> > Oct 1 11:17:31 localhost kernel: buffer_info[next_to_clean] > Oct 1 11:17:31 localhost kernel: time_stamp <e25de7af> > Oct 1 11:17:31 localhost kernel: next_to_watch <f6> > Oct 1 11:17:31 localhost kernel: jiffies <e25debb0> > Oct 1 11:17:31 localhost kernel: next_to_watch.status <0> > Oct 1 11:17:33 localhost kernel: e1000: eth0: e1000_clean_tx_irq: > Detected Tx Unit Hang > Oct 1 11:17:33 localhost kernel: Tx Queue <0> > Oct 1 11:17:33 localhost kernel: TDH <e2> > Oct 1 11:17:33 localhost kernel: TDT <e2> > Oct 1 11:17:33 localhost kernel: next_to_use <e2> > Oct 1 11:17:33 localhost kernel: next_to_clean <f6> > Oct 1 11:17:33 localhost kernel: buffer_info[next_to_clean] > Oct 1 11:17:33 localhost kernel: time_stamp <e25de7af> > Oct 1 11:17:33 localhost kernel: next_to_watch <f6> > Oct 1 11:17:33 localhost kernel: jiffies <e25df380> > Oct 1 11:17:33 localhost kernel: next_to_watch.status <0> > Oct 1 11:17:35 localhost kernel: e1000: eth0: e1000_clean_tx_irq: > Detected Tx Unit Hang > Oct 1 11:17:35 localhost kernel: Tx Queue <0> > Oct 1 11:17:35 localhost kernel: TDH <e2> > Oct 1 11:17:35 localhost kernel: TDT <e2> > Oct 1 11:17:35 localhost kernel: next_to_use <e2> > Oct 1 11:17:35 localhost kernel: next_to_clean <f6> > Oct 1 11:17:35 localhost kernel: buffer_info[next_to_clean] > Oct 1 11:17:35 localhost kernel: time_stamp <e25de7af> > Oct 1 11:17:35 localhost kernel: next_to_watch <f6> > Oct 1 11:17:35 localhost kernel: jiffies <e25dfb50> > Oct 1 11:17:35 localhost kernel: next_to_watch.status <0> > Oct 1 11:17:37 localhost kernel: e1000: eth0: e1000_clean_tx_irq: > Detected Tx Unit Hang > Oct 1 11:17:37 localhost kernel: Tx Queue <0> > Oct 1 11:17:37 localhost kernel: TDH <e2> > Oct 1 11:17:37 localhost kernel: TDT <e2> > Oct 1 11:17:37 localhost kernel: next_to_use <e2> > Oct 1 11:17:37 localhost kernel: next_to_clean <f6> > Oct 1 11:17:37 localhost kernel: buffer_info[next_to_clean] > Oct 1 11:17:37 localhost kernel: time_stamp <e25de7af> > Oct 1 11:17:37 localhost kernel: next_to_watch <f6> > Oct 1 11:17:37 localhost kernel: jiffies <e25e0320> > Oct 1 11:17:37 localhost kernel: next_to_watch.status <0> > Oct 1 11:17:39 localhost kernel: e1000: eth0: e1000_clean_tx_irq: > Detected Tx Unit Hang > Oct 1 11:17:39 localhost kernel: Tx Queue <0> > Oct 1 11:17:39 localhost kernel: TDH <e2> > Oct 1 11:17:39 localhost kernel: TDT <e2> > Oct 1 11:17:39 localhost kernel: next_to_use <e2> > Oct 1 11:17:39 localhost kernel: next_to_clean <f6> > Oct 1 11:17:39 localhost kernel: buffer_info[next_to_clean] > Oct 1 11:17:39 localhost kernel: time_stamp <e25de7af> > Oct 1 11:17:39 localhost kernel: next_to_watch <f6> > Oct 1 11:17:39 localhost kernel: jiffies <e25e0af0> > Oct 1 11:17:39 localhost kernel: next_to_watch.status <0> > > > > > > lspci shows : > > 00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge > 00:00.1 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge > 00:00.2 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge > 00:00.3 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge > 00:00.4 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge > 00:00.7 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge > 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/ > K8T890 South] > 00:0b.0 Ethernet controller: Intel Corporation 82541PI Gigabit > Ethernet Controller (rev 05) > 00:0c.0 Ethernet controller: Intel Corporation 82541PI Gigabit > Ethernet Controller (rev 05) > 00:0d.0 Ethernet controller: Intel Corporation 82541PI Gigabit > Ethernet Controller (rev 05) > 00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID > Controller (rev 80) > 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/ > B/ > VT823x/A/C PIPC Bus Master IDE (rev 06) > 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 > Controller (rev 81) > 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 > Controller (rev 81) > 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 > Controller (rev 81) > 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 > Controller (rev 81) > 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) > 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/ > K8T800/K8T890 South] > 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/ > 8235/8237 AC97 Audio Controller (rev 60) > 00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem > Controller (rev 80) > 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] > (rev 78) > 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/ > Opteron] HyperTransport Technology Configuration > 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/ > Opteron] Address Map > 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/ > Opteron] DRAM Controller > 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/ > Opteron] Miscellaneous Control > 01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M800/ > K8N800/K8N800A [S3 UniChrome Pro] (rev 01) > > > > lsmod shows : > > Module Size Used by > e1000 153668 0 > ipt_LOG 8836 0 > sit 12804 0 > tunnel4 6792 1 sit > dca 9124 0 > xt_multiport 6784 119 > act_nat 8004 0 > nf_nat_tftp 5504 0 > nf_nat_proto_sctp 5892 0 > libcrc32c 6400 1 nf_nat_proto_sctp > nf_nat_pptp 6656 0 > nf_nat_proto_gre 6020 1 nf_nat_pptp > nf_nat_proto_udplite 5892 0 > nf_nat_proto_dccp 5892 0 > nf_nat_h323 9472 0 > nf_nat_sip 9600 0 > nf_nat_snmp_basic 11656 0 > nf_nat_amanda 5760 0 > nf_nat_irc 6016 0 > nf_nat_ftp 6400 0 > ebt_snat 5760 0 > ebtable_nat 5888 0 > ebt_dnat 5632 0 > ebtables 19200 3 ebt_snat,ebtable_nat,ebt_dnat > nf_conntrack_ipv6 15864 0 > nf_conntrack_netlink 17792 0 > nfnetlink 7320 1 nf_conntrack_netlink > ts_kmp 6016 5 > nf_conntrack_amanda 7552 1 nf_nat_amanda > nf_conntrack_tftp 7956 1 nf_nat_tftp > nf_conntrack_ftp 10660 1 nf_nat_ftp > nf_conntrack_sane 8220 0 > nf_conntrack_irc 8868 1 nf_nat_irc > nf_conntrack_netbios_ns 6272 0 > nf_conntrack_sip 18708 1 nf_nat_sip > nf_conntrack_pptp 9092 1 nf_nat_pptp > nf_conntrack_proto_gre 8064 1 nf_conntrack_pptp > nf_conntrack_proto_dccp 9992 0 > nf_conntrack_proto_sctp 10248 0 > nf_conntrack_h323 46336 1 nf_nat_h323 > nf_conntrack_proto_udplite 7560 0 > ipt_MASQUERADE 6528 0 > iptable_nat 8712 1 > nf_nat 17944 14 > nf_nat_tftp > ,nf_nat_proto_sctp > ,nf_nat_pptp > ,nf_nat_proto_gre > ,nf_nat_proto_udplite > ,nf_nat_proto_dccp > ,nf_nat_h323 > ,nf_nat_sip > ,nf_nat_amanda > ,nf_nat_irc,nf_nat_ftp,nf_conntrack_netlink,ipt_MASQUERADE,iptable_nat > bridge 43668 0 > stp 6148 1 bridge > bnep 14848 2 > sco 12932 2 > l2cap 21504 3 bnep > bluetooth 48608 5 bnep,sco,l2cap > sunrpc 156052 3 > ipv6 230132 20 sit,nf_conntrack_ipv6 > dm_multipath 17164 0 > uinput 10624 0 > snd_via82xx 25752 0 > snd_via82xx_modem 14472 0 > gameport 13452 1 snd_via82xx > snd_ac97_codec 95268 2 snd_via82xx,snd_via82xx_modem > ac97_bus 5504 1 snd_ac97_codec > snd_seq_dummy 6660 0 > snd_seq_oss 30364 0 > snd_seq_midi_event 9600 1 snd_seq_oss > snd_seq 48576 5 > snd_seq_dummy,snd_seq_oss,snd_seq_midi_event > snd_pcm_oss 42496 0 > snd_mixer_oss 16896 1 snd_pcm_oss > snd_pcm 65924 4 > snd_via82xx,snd_via82xx_modem,snd_ac97_codec,snd_pcm_oss > snd_timer 22024 2 snd_seq,snd_pcm > snd_page_alloc 11016 3 snd_via82xx,snd_via82xx_modem,snd_pcm > snd_mpu401_uart 10368 1 snd_via82xx > snd_rawmidi 22528 1 snd_mpu401_uart > snd_seq_device 10124 4 > snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi > snd 50616 13 > snd_via82xx > ,snd_via82xx_modem > ,snd_ac97_codec > ,snd_seq_dummy > ,snd_seq_oss > ,snd_seq > ,snd_pcm_oss > ,snd_mixer_oss > ,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device > soundcore 9416 1 snd > i2c_viapro 10772 0 > sata_via 10884 0 > via_rhine 23560 0 > mii 8192 1 via_rhine > k8temp 7936 0 > hwmon 6300 1 k8temp > i2c_core 21396 1 i2c_viapro > pcspkr 6272 0 > floppy 51988 0 > ata_generic 8452 0 > pata_acpi 7680 0 > pata_via 11908 2 > > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf > _______________________________________________ > E1000-devel mailing list > E1000-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/e1000-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
