Bug 10682

I forgot to note in the original report that I have tried the following various settings both ways to no imact:

8139_OLD_RX_RESET
8139TOO_8129 
8139TOO_TUNE_TWISTER
8139TOO_PIO

In particular, I have the same behavior with the old and new RX reset settings and I've tried both MMIO and PIO.

Reply-To: akpm@linux-foundation.org

(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Sun, 11 May 2008 16:34:29 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=10682
> 
>            Summary: (net 8139too) dual ethernet system, any reasonable
>                     network causes: NETDEV WATCHDOG: ethN: transmit timed
>                     out
>            Product: Drivers
>            Version: 2.5
>      KernelVersion: 2.6.25.3
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Network
>         AssignedTo: jgarzik@pobox.com
>         ReportedBy: bkuhn@ebb.org
> 
> 
> Latest working kernel version: Unknown
> Earliest failing kernel version: 2.6.24
> Distribution: Ubuntu
> Hardware Environment: eBox-4852
> Software Environment: Standard Ubuntu Hardy install, with self-compiled
> kernel
> direct from kernel.org used fakeroot make-kpkg --initrd kernel_image
> 
> Problem Description:
> 
> I have an eBox-4852 which has two of these ethernet cards in it:
>      Ethernet controller: Realtek Semiconductor Co., Ltd.
>      RTL-8139/8139C/8139C+
> (rev 10
> 
> As soon as I get both ethernet cards up and running and put any reasonable
> load (using the system as a packet-forwarding firewall), one or both of
> them fail for a number of minutes.  Eventually, they usually come back up
> on their own, at which time the following message appears in the syslog:
> 
> kernel: [ 2242.871816] NETDEV WATCHDOG: eth0: transmit timed out
> kernel: [ 2245.885704] eth0: Transmit timeout, status 0d 0000 c07f media 10.
> kernel: [ 2245.885704] eth0: Tx queue start entry 7227  dirty entry 7223.
> kernel: [ 2245.885704] eth0:  Tx descriptor 0 is 0008003c.
> kernel: [ 2245.885704] eth0:  Tx descriptor 1 is 0008003c.
> kernel: [ 2245.885704] eth0:  Tx descriptor 2 is 0008003c.
> kernel: [ 2245.885704] eth0:  Tx descriptor 3 is 00080042. (queue head)
> kernel: [ 2245.885704] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> 
> They are both recognized at boot time to use the 8139too module:
> 
> kernel: [   15.531666] 8139too Fast Ethernet driver 0.9.28
> kernel: [   15.532287] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
> kernel: [   15.532343] PCI: setting IRQ 10 as level-triggered
> kernel: [   15.532352] ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LNKA] ->
> GSI 10 (level, low) -> I
> RQ 10
> kernel: [   15.533338] eth0: RealTek RTL8139 at 0xe800, 44:4d:50:02:e1:cb,
> IRQ
> 10
> kernel: [   15.533394] eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
> kernel: [   15.533817] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
> kernel: [   15.533870] PCI: setting IRQ 11 as level-triggered
> kernel: [   15.533878] ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKD] ->
> GSI 11 (level, low) -> IRQ 11
> kernel: [   15.534759] eth1: RealTek RTL8139 at 0xe400, 44:4d:50:43:41:74,
> IRQ
> 11
> kernel: [   15.534814] eth1:  Identified 8139 chip type 'RTL-8100B/8139D'
> 
> Steps to reproduce:
> 
> It's very simple, one needs only to have this box and run both cards with
> any amount of reasonable load and it occurs within an hour, usually much
> faster.  I read online that sometimes WATCHDOG TIMEOUT means that there is
> bad network infrastructure of some sort.  I have tried many different
> network topologies, hubs, and cables and it always produces the same
> error.  I have also tried all different possible BIOS settings related to
> IRQs.
> 
> Based on advice from online forums and the like, I have also tried the
> following kernel command line settings, in sequence and together in
> various ways, and the behavior is still the same:
> 
> nosmp
> irqpoll
> pci=biosirq
> pci=irqmasq
> pci=routeirq
> 
> 
> Here is all the data from the running system:
> 
>
> ###############################################################################
> /proc/cpuinfo:
> processor       : 0
> vendor_id       : CentaurHauls
> cpu family      : 6
> model           : 13
> model name      : VIA Eden Processor 1200MHz
> stepping        : 0
> cpu MHz         : 1196.956
> cache size      : 128 KB
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 1
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge cmov
> pat
> clflush acpi mmx fxsr sse sse2 tm nx pni est tm2 xtpr rng rng_en ace ace_en
> ace2 ace2_en phe phe_en pmm pmm_en
> bogomips        : 2395.59
> clflush size    : 64
>
> ###############################################################################
> /proc/interrupts:
>            CPU0       
>   0:     131574    XT-PIC-XT        timer
>   1:        761    XT-PIC-XT        i8042
>   2:          0    XT-PIC-XT        cascade
>   7:          0    XT-PIC-XT        parport0
>   8:          7    XT-PIC-XT        rtc
>   9:          0    XT-PIC-XT        acpi
>  10:      38862    XT-PIC-XT        uhci_hcd:usb2, eth0
>  11:    1151499    XT-PIC-XT        ehci_hcd:usb1, eth1
>  14:          0    XT-PIC-XT        pata_via
>  15:      16369    XT-PIC-XT        pata_via
> NMI:          0   Non-maskable interrupts
> TRM:          0   Thermal event interrupts
> SPU:          0   Spurious interrupts
> ERR:          0
>
> ###############################################################################
> /proc/iomem:
> 
> 00000000-0009fbff : System RAM
> 0009fc00-0009ffff : reserved
> 000a0000-000bffff : Video RAM area
> 000c0000-000ce5ff : Video ROM
> 000f0000-000fffff : System ROM
> 00100000-1bfbffff : System RAM
>   00100000-002f182f : Kernel code
>   002f1830-003db41f : Kernel data
>   00433000-0048ed9b : Kernel bss
> 1bfc0000-1bfcdfff : ACPI Tables
> 1bfce000-1bffffff : ACPI Non-volatile Storage
> c0000000-dfffffff : PCI Bus #01
>   c0000000-dfffffff : 0000:01:00.0
> e0000000-efffffff : pnp 00:0d
> f0000000-f7ffffff : 0000:00:00.0
> fcfff400-fcfff4ff : 0000:00:10.4
>   fcfff400-fcfff4ff : ehci_hcd
> fcfff800-fcfff8ff : 0000:00:0b.0
>   fcfff800-fcfff8ff : 8139too
> fcfffc00-fcfffcff : 0000:00:08.0
>   fcfffc00-fcfffcff : 8139too
> fd000000-feafffff : PCI Bus #01
>   fd000000-fdffffff : 0000:01:00.0
>   feaf0000-feafffff : 0000:01:00.0
> feb00000-febfffff : PCI Bus #02
>   febfc000-febfffff : 0000:02:01.0
> fec00000-fec00fff : reserved
> fed00000-fed003ff : HPET 0
> fee00000-fee00fff : reserved
> fff80000-ffffffff : reserved
>
> ###############################################################################
> /proc/ioports:
> 0000-001f : dma1
> 0020-0021 : pic1
> 0040-0043 : timer0
> 0050-0053 : timer1
> 0060-006f : keyboard
> 0070-0077 : rtc
> 0080-008f : dma page reg
> 00a0-00a1 : pic2
> 00c0-00df : dma2
> 00f0-00ff : fpu
> 0170-0177 : 0000:00:0f.0
>   0170-0177 : pata_via
> 01f0-01f7 : 0000:00:0f.0
>   01f0-01f7 : pata_via
> 02f8-02ff : serial
> 0376-0376 : 0000:00:0f.0
>   0376-0376 : pata_via
> 0378-037a : parport0
> 03c0-03df : vga+
> 03e0-03e7 : pnp 00:09
> 03f6-03f6 : 0000:00:0f.0
>   03f6-03f6 : pata_via
> 03f8-03ff : serial
> 0400-041f : pnp 00:09
>   0400-0407 : vt596_smbus
> 04d0-04d1 : pnp 00:09
> 0800-087f : pnp 00:09
>   0800-0803 : ACPI PM1a_EVT_BLK
>   0804-0805 : ACPI PM1a_CNT_BLK
>   0808-080b : ACPI PM_TMR
>   0810-0815 : ACPI CPU throttle
>   0820-0823 : ACPI GPE0_BLK
> 0a00-0a0f : pnp 00:08
> 0a10-0a1f : pnp 00:08
> 0a20-0a2f : pnp 00:08
> 0a30-0a3f : pnp 00:08
> 0a40-0a4f : pnp 00:08
> 0a50-0a5f : pnp 00:08
> 0a60-0a61 : pnp 00:08
> 0cf8-0cff : PCI conf1
> e400-e4ff : 0000:00:0b.0
>   e400-e4ff : 8139too
> e800-e8ff : 0000:00:08.0
>   e800-e8ff : 8139too
> ec00-ec1f : 0000:00:10.0
>   ec00-ec1f : uhci_hcd
> fc00-fc0f : 0000:00:0f.0
>   fc00-fc0f : pata_via
>
> ###############################################################################
> $ lsmod
> Module                  Size  Used by
> af_packet              21760  2 
> video                  19600  0 
> output                  3968  1 video
> sbs                    13960  0 
> sbshc                   6912  1 sbs
> container               4864  0 
> battery                13188  0 
> ac                      6148  0 
> quota_v1                3456  1 
> ext3                  133768  1 
> jbd                    42900  1 ext3
> mbcache                 8448  1 ext3
> lp                     11812  0 
> loop                   18052  0 
> parport_pc             35108  1 
> parport                36168  2 lp,parport_pc
> xt_limit                2816  6 
> pcspkr                  3200  0 
> button                  8336  0 
> i2c_viapro              9236  0 
> xt_multiport            3584  3 
> i2c_core               24848  1 i2c_viapro
> via_agp                10368  1 
> shpchp                 33428  0 
> pci_hotplug            30116  1 shpchp
> agpgart                33840  1 via_agp
> xt_state                2688  60 
> xt_tcpudp               3456  61 
> evdev                  12032  0 
> nf_nat_tftp             2048  0 
> nf_conntrack_tftp       5396  1 nf_nat_tftp
> nf_nat_snmp_basic      10372  0 
> nf_nat_sip              4992  0 
> nf_conntrack_sip        9364  1 nf_nat_sip
> nf_nat_pptp             3968  0 
> nf_conntrack_pptp       7296  1 nf_nat_pptp
> nf_conntrack_proto_gre     5760  1 nf_conntrack_pptp
> nf_nat_proto_gre        3076  1 nf_nat_pptp
> nf_nat_irc              3072  0 
> nf_conntrack_irc        6936  1 nf_nat_irc
> nf_nat_h323             7808  0 
> nf_conntrack_h323      49576  1 nf_nat_h323
> nf_nat_ftp              3584  0 
> nf_conntrack_ftp        8992  1 nf_nat_ftp
> nf_nat_amanda           2688  0 
> ts_kmp                  2304  5 
> nf_conntrack_amanda     5248  1 nf_nat_amanda
> iptable_raw             3072  0 
> iptable_nat             7560  1 
> iptable_mangle          3456  0 
> iptable_filter          3584  1 
> ipt_ttl                 2048  0 
> ipt_recent              9496  0 
> ipt_ecn                 2432  0 
> ipt_ah                  2176  0 
> ipt_addrtype            3072  0 
> ipt_ULOG                9220  0 
> ipt_TTL                 2560  0 
> ipt_REJECT              4352  0 
> ipt_REDIRECT            2176  0 
> ipt_NETMAP              2176  0 
> ipt_MASQUERADE          3712  0 
> nf_nat                 19472  12
>
> nf_nat_tftp,nf_nat_sip,nf_nat_pptp,nf_nat_proto_gre,nf_nat_irc,nf_nat_h323,nf_nat_ftp,nf_nat_amanda,iptable_nat,ipt_REDIRECT,ipt_NETMAP,ipt_MASQUERADE
> nf_conntrack_ipv4      17800  63 iptable_nat,nf_nat
> ipt_LOG                 6400  8 
> ipt_ECN                 3200  0 
> ipt_CLUSTERIP           8580  0 
> nf_conntrack           62884  22
>
> xt_state,nf_nat_tftp,nf_conntrack_tftp,nf_nat_snmp_basic,nf_nat_sip,nf_conntrack_sip,nf_nat_pptp,nf_conntrack_pptp,nf_conntrack_proto_gre,nf_nat_irc,nf_conntrack_irc,nf_nat_h323,nf_conntrack_h323,nf_nat_ftp,nf_conntrack_ftp,nf_nat_amanda,nf_conntrack_amanda,iptable_nat,ipt_MASQUERADE,nf_nat,nf_conntrack_ipv4,ipt_CLUSTERIP
> ip_tables              13328  4
> iptable_raw,iptable_nat,iptable_mangle,iptable_filter
> ip_queue               10000  0 
> arptable_filter         2816  0 
> arpt_mangle             2432  0 
> arp_tables             11792  1 arptable_filter
> x_tables               16516  22
>
> xt_limit,xt_multiport,xt_state,xt_tcpudp,iptable_nat,ipt_ttl,ipt_recent,ipt_ecn,ipt_ah,ipt_addrtype,ipt_ULOG,ipt_TTL,ipt_REJECT,ipt_REDIRECT,ipt_NETMAP,ipt_MASQUERADE,ipt_LOG,ipt_ECN,ipt_CLUSTERIP,ip_tables,arpt_mangle,arp_tables
> jfs                   187716  1 
> sg                     37168  0 
> sd_mod                 29968  5 
> pata_via               12548  4 
> pata_acpi               7424  0 
> ata_generic             8324  0 
> uhci_hcd               24848  0 
> ehci_hcd               36492  0 
> libata                161936  3 pata_via,pata_acpi,ata_generic
> usbcore               145264  3 uhci_hcd,ehci_hcd
> scsi_mod              151180  3 sg,sd_mod,libata
> dock                   10380  1 libata
> 8139too                27136  0 
> mii                     5760  1 8139too
> thermal                18972  0 
> processor              33332  1 thermal
> fan                     5764  0 
> fuse                   48412  1 
>
> ###############################################################################
> $ lspci -vvv
> 00:00.0 Host bridge: VIA Technologies, Inc. CX700 Host Bridge (rev 03)
>         Subsystem: VIA Technologies, Inc. CX700 Host Bridge
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 8
>         Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
>         Capabilities: [80] AGP version 3.5
>                 Status: RQ=8 Iso- ArqSz=0 Cal=2 SBA+ ITACoh- GART64- HTrans-
> 64bit- FW+ AGP3+ Rate=x4,x8
>                 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW-
> Rate=<none>
>         Capabilities: [50] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 00:00.1 Host bridge: VIA Technologies, Inc. CX700 Host Bridge
>         Subsystem: VIA Technologies, Inc. CX700 Host Bridge
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>         Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 0
> 
> 00:00.2 Host bridge: VIA Technologies, Inc. CX700 Host Bridge
>         Subsystem: VIA Technologies, Inc. CX700 Host Bridge
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>         Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 0
> 
> 00:00.3 Host bridge: VIA Technologies, Inc. CX700 Host Bridge
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>         Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 0
> 
> 00:00.4 Host bridge: VIA Technologies, Inc. CX700 Host Bridge
>         Subsystem: VIA Technologies, Inc. CX700 Host Bridge
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>         Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 0
> 
> 00:00.7 Host bridge: VIA Technologies, Inc. CX700 Host Bridge
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>         Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 0
> 
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge (prog-if 00
> [Normal decode])
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B-
>         Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 0
>         Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
>         I/O behind bridge: 0000f000-00000fff
>         Memory behind bridge: fd000000-feafffff
>         Prefetchable memory behind bridge: c0000000-dfffffff
>         Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort+ <SERR- <PERR+
>         BridgeCtl: Parity+ SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-
>         Capabilities: [70] Power Management version 2
>                 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
>         Subsystem: Realtek Semiconductor Co., Ltd. RT8139
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64 (8000ns min, 16000ns max)
>         Interrupt: pin A routed to IRQ 10
>         Region 0: I/O ports at e800 [size=256]
>         Region 1: Memory at fcfffc00 (32-bit, non-prefetchable) [size=256]
>         Capabilities: [50] Power Management version 2
>                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> PME(D0-,D1+,D2+,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
>         Subsystem: Realtek Semiconductor Co., Ltd. RT8139
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64 (8000ns min, 16000ns max)
>         Interrupt: pin A routed to IRQ 11
>         Region 0: I/O ports at e400 [size=256]
>         Region 1: Memory at fcfff800 (32-bit, non-prefetchable) [size=256]
>         Capabilities: [50] Power Management version 2
>                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> PME(D0-,D1+,D2+,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 00:0f.0 IDE interface: VIA Technologies, Inc. CX700M2 IDE (prog-if 8a [Master
> SecP PriP])
>         Subsystem: VIA Technologies, Inc. Unknown device 0581
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 32
>         Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable)
> [size=8]
>         Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable)
> [size=1]
>         Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable)
> [size=8]
>         Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable)
> [size=1]
>         Region 4: I/O ports at fc00 [size=16]
>         Capabilities: [b0] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (rev 90) (prog-if 00 [UHCI])
>         Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64, Cache Line Size: 32 bytes
>         Interrupt: pin A routed to IRQ 10
>         Region 4: I/O ports at ec00 [size=32]
>         Capabilities: [80] Power Management version 2
>                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> PME(D0+,D1+,D2+,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 90) (prog-if 20
> [EHCI])
>         Subsystem: VIA Technologies, Inc. USB 2.0
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64, Cache Line Size: 32 bytes
>         Interrupt: pin D routed to IRQ 11
>         Region 0: Memory at fcfff400 (32-bit, non-prefetchable) [size=256]
>         Capabilities: [80] Power Management version 2
>                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> PME(D0+,D1+,D2+,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>         Capabilities: [88] Debug port
> 
> 00:11.0 ISA bridge: VIA Technologies, Inc. CX700 PCI to ISA Bridge
>         Subsystem: VIA Technologies, Inc. CX700 PCI to ISA Bridge
>         Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Capabilities: [c0] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 00:11.7 Host bridge: VIA Technologies, Inc. CX700 Internal Module Bus
>         Subsystem: VIA Technologies, Inc. CX700 Internal Module Bus
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort+ >SERR- <PERR-
>         Latency: 128
>         Capabilities: [58] HyperTransport: Interrupt Discovery and
> Configuration
> 
> 00:13.0 PCI bridge: VIA Technologies, Inc. CX700 Host Bridge (prog-if 00
> [Normal decode])
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B-
>         Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
>         <TAbort-
> <MAbort+ >SERR- <PERR-
>         Latency: 0
>         Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
>         I/O behind bridge: 0000f000-00000fff
>         Memory behind bridge: feb00000-febfffff
>         Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
>         Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- <SERR- <PERR-
>         BridgeCtl: Parity+ SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
> 
> 01:00.0 VGA compatible controller: VIA Technologies, Inc. CX700M2 UniChrome
> PRO
> II Graphics (rev 03) (prog-if 00 [VGA controller])
>         Subsystem: Unknown device 0908:1975
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64 (500ns min)
>         Interrupt: pin A routed to IRQ 0
>         Region 0: Memory at c0000000 (32-bit, prefetchable) [size=512M]
>         Region 1: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
>         Expansion ROM at feaf0000 [disabled] [size=64K]
>         Capabilities: [60] Power Management version 2
>                 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>         Capabilities: [70] AGP version 3.0
>                 Status: RQ=256 Iso- ArqSz=0 Cal=7 SBA+ ITACoh- GART64-
>                 HTrans-
> 64bit- FW- AGP3+ Rate=x4,x8
>                 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW-
> Rate=<none>
> 
> 02:01.0 Audio device: VIA Technologies, Inc. VIA High Definition Audio
> Controller (rev 10)
>         Subsystem: VIA Technologies, Inc. VIA High Definition Audio
>         Controller
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
>         <TAbort-
> <MAbort- >SERR- <PERR-
>         Latency: 0, Cache Line Size: 32 bytes
>         Interrupt: pin A routed to IRQ 5
>         Region 0: Memory at febfc000 (64-bit, non-prefetchable) [size=16K]
>         Capabilities: [50] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA
> PME(D0+,D1-,D2-,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>         Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+
>         Queue=0/0
> Enable-
>                 Address: 0000000000000000  Data: 0000
>         Capabilities: [70] Express Unknown type IRQ 0
>                 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
>                 Device: Latency L0s <64ns, L1 <1us
>                 Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
>                 Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
>                 Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
>                 Link: Supported Speed unknown, Width x0, ASPM unknown, Port 0
>                 Link: Latency L0s <64ns, L1 <1us
>                 Link: ASPM Disabled CommClk- ExtSynch-
>                 Link: Speed unknown, Width x0
>
> ###############################################################################
> /proc/modules:
> af_packet 21760 2 - Live 0xdcd1c000
> video 19600 0 - Live 0xdcd16000
> output 3968 1 video, Live 0xdcc06000
> sbs 13960 0 - Live 0xdcd3a000
> sbshc 6912 1 sbs, Live 0xdcc31000
> container 4864 0 - Live 0xdcc17000
> battery 13188 0 - Live 0xdcc2c000
> ac 6148 0 - Live 0xdcc14000
> quota_v1 3456 1 - Live 0xdcc04000
> ext3 133768 1 - Live 0xdcef6000
> jbd 42900 1 ext3, Live 0xdcc40000
> mbcache 8448 1 ext3, Live 0xdcc00000
> lp 11812 0 - Live 0xdcbfc000
> loop 18052 0 - Live 0xdcbf6000
> parport_pc 35108 1 - Live 0xdcc22000
> parport 36168 2 lp,parport_pc, Live 0xdcc0a000
> xt_limit 2816 6 - Live 0xdcc08000
> pcspkr 3200 0 - Live 0xdcbe1000
> button 8336 0 - Live 0xdcbf2000
> i2c_viapro 9236 0 - Live 0xdcbdd000
> xt_multiport 3584 3 - Live 0xdc9f7000
> i2c_core 24848 1 i2c_viapro, Live 0xdcc1a000
> via_agp 10368 1 - Live 0xdc9ef000
> shpchp 33428 0 - Live 0xdcbe3000
> pci_hotplug 30116 1 shpchp, Live 0xdcc56000
> agpgart 33840 1 via_agp, Live 0xdcc4c000
> xt_state 2688 60 - Live 0xdc9f3000
> xt_tcpudp 3456 61 - Live 0xdc9f5000
> evdev 12032 0 - Live 0xdc9eb000
> nf_nat_tftp 2048 0 - Live 0xdc9e9000
> nf_conntrack_tftp 5396 1 nf_nat_tftp, Live 0xdc9e6000
> nf_nat_snmp_basic 10372 0 - Live 0xdc9e2000
> nf_nat_sip 4992 0 - Live 0xdc9df000
> nf_conntrack_sip 9364 1 nf_nat_sip, Live 0xdc9db000
> nf_nat_pptp 3968 0 - Live 0xdc9c7000
> nf_conntrack_pptp 7296 1 nf_nat_pptp, Live 0xdc9c4000
> nf_conntrack_proto_gre 5760 1 nf_conntrack_pptp, Live 0xdc9c1000
> nf_nat_proto_gre 3076 1 nf_nat_pptp, Live 0xdc9bf000
> nf_nat_irc 3072 0 - Live 0xdc9ba000
> nf_conntrack_irc 6936 1 nf_nat_irc, Live 0xdc9b7000
> nf_nat_h323 7808 0 - Live 0xdc9b4000
> nf_conntrack_h323 49576 1 nf_nat_h323, Live 0xdc9cd000
> nf_nat_ftp 3584 0 - Live 0xdc9b2000
> nf_conntrack_ftp 8992 1 nf_nat_ftp, Live 0xdc9ae000
> nf_nat_amanda 2688 0 - Live 0xdc9ac000
> ts_kmp 2304 5 - Live 0xdc9bd000
> nf_conntrack_amanda 5248 1 nf_nat_amanda, Live 0xdc9a9000
> iptable_raw 3072 0 - Live 0xdc9a7000
> iptable_nat 7560 1 - Live 0xdc9a4000
> iptable_mangle 3456 0 - Live 0xdc9cb000
> iptable_filter 3584 1 - Live 0xdc9c9000
> ipt_ttl 2048 0 - Live 0xdc99e000
> ipt_recent 9496 0 - Live 0xdc99a000
> ipt_ecn 2432 0 - Live 0xdc998000
> ipt_ah 2176 0 - Live 0xdc996000
> ipt_addrtype 3072 0 - Live 0xdc994000
> ipt_ULOG 9220 0 - Live 0xdc990000
> ipt_TTL 2560 0 - Live 0xdc98e000
> ipt_REJECT 4352 0 - Live 0xdc98b000
> ipt_REDIRECT 2176 0 - Live 0xdc989000
> ipt_NETMAP 2176 0 - Live 0xdc987000
> ipt_MASQUERADE 3712 0 - Live 0xdc985000
> nf_nat 19472 12
>
> nf_nat_tftp,nf_nat_sip,nf_nat_pptp,nf_nat_proto_gre,nf_nat_irc,nf_nat_h323,nf_nat_ftp,nf_nat_amanda,iptable_nat,ipt_REDIRECT,ipt_NETMAP,ipt_MASQUERADE,
> Live 0xdc97f000
> nf_conntrack_ipv4 17800 63 iptable_nat,nf_nat, Live 0xdc979000
> ipt_LOG 6400 8 - Live 0xdc9a1000
> ipt_ECN 3200 0 - Live 0xdc8b0000
> ipt_CLUSTERIP 8580 0 - Live 0xdc8e6000
> nf_conntrack 62884 22
>
> xt_state,nf_nat_tftp,nf_conntrack_tftp,nf_nat_snmp_basic,nf_nat_sip,nf_conntrack_sip,nf_nat_pptp,nf_conntrack_pptp,nf_conntrack_proto_gre,nf_nat_irc,nf_conntrack_irc,nf_nat_h323,nf_conntrack_h323,nf_nat_ftp,nf_conntrack_ftp,nf_nat_amanda,nf_conntrack_amanda,iptable_nat,ipt_MASQUERADE,nf_nat,nf_conntrack_ipv4,ipt_CLUSTERIP,
> Live 0xdc968000
> ip_tables 13328 4 iptable_raw,iptable_nat,iptable_mangle,iptable_filter, Live
> 0xdc8e1000
> ip_queue 10000 0 - Live 0xdc8dd000
> arptable_filter 2816 0 - Live 0xdc8aa000
> arpt_mangle 2432 0 - Live 0xdc89d000
> arp_tables 11792 1 arptable_filter, Live 0xdc8d9000
> x_tables 16516 22
>
> xt_limit,xt_multiport,xt_state,xt_tcpudp,iptable_nat,ipt_ttl,ipt_recent,ipt_ecn,ipt_ah,ipt_addrtype,ipt_ULOG,ipt_TTL,ipt_REJECT,ipt_REDIRECT,ipt_NETMAP,ipt_MASQUERADE,ipt_LOG,ipt_ECN,ipt_CLUSTERIP,ip_tables,arpt_mangle,arp_tables,
> Live 0xdc8d3000
> jfs 187716 1 - Live 0xdc8ef000
> sg 37168 0 - Live 0xdc8c8000
> sd_mod 29968 5 - Live 0xdc8bf000
> pata_via 12548 4 - Live 0xdc8ea000
> pata_acpi 7424 0 - Live 0xdc839000
> ata_generic 8324 0 - Live 0xdc8ac000
> uhci_hcd 24848 0 - Live 0xdc8a2000
> ehci_hcd 36492 0 - Live 0xdc865000
> libata 161936 3 pata_via,pata_acpi,ata_generic, Live 0xdc9fa000
> usbcore 145264 3 uhci_hcd,ehci_hcd, Live 0xdc878000
> scsi_mod 151180 3 sg,sd_mod,libata, Live 0xdc83f000
> dock 10380 1 libata, Live 0xdc835000
> 8139too 27136 0 - Live 0xdc870000
> mii 5760 1 8139too, Live 0xdc832000
> thermal 18972 0 - Live 0xdc82c000
> processor 33332 1 thermal, Live 0xdc822000
> fan 5764 0 - Live 0xdc83c000
> fuse 48412 1 - Live 0xdc8b2000
>
> ###############################################################################
> $ ver_linux:
> 
> If some fields are empty or look unusual you may have an old version.
> Compare to the current minimal requirements in Documentation/Changes.
> 
> Linux buddhist 2.6.25.3 #2 Sun May 11 15:35:44 EDT 2008 i686 GNU/Linux
> 
> Gnu C                  4.2.3
> Gnu make               3.81
> binutils               2.18.0.20080103
> util-linux             2.13.1
> mount                  2.13.1
> module-init-tools      3.3-pre11
> e2fsprogs              1.40.8
> jfsutils               1.1.11
> reiserfsprogs          3.6.19
> pcmciautils            014
> quota-tools            3.15.
> PPP                    2.4.4
> Linux C Library        2.7
> Dynamic linker (ldd)   2.7
> Procps                 3.2.7
> Net-tools              1.60
> Console-tools          0.2.3
> Sh-utils               6.10
> udev                   117
> wireless-tools         29
> Modules Loaded         af_packet video output sbs sbshc container battery ac
> quota_v1 ext3 jbd mbcache lp loop parport_pc parport xt_limit pcspkr button
> i2c_viapro xt_multiport i2c_core via_agp shpchp pci_hotplug agpgart xt_state
> xt_tcpudp evdev nf_nat_tftp nf_conntrack_tftp nf_nat_snmp_basic nf_nat_sip
> nf_conntrack_sip nf_nat_pptp nf_conntrack_pptp nf_conntrack_proto_gre
> nf_nat_proto_gre nf_nat_irc nf_conntrack_irc nf_nat_h323 nf_conntrack_h323
> nf_nat_ftp nf_conntrack_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda
> iptable_raw iptable_nat iptable_mangle iptable_filter ipt_ttl ipt_recent
> ipt_ecn ipt_ah ipt_addrtype ipt_ULOG ipt_TTL ipt_REJECT ipt_REDIRECT
> ipt_NETMAP
> ipt_MASQUERADE nf_nat nf_conntrack_ipv4 ipt_LOG ipt_ECN ipt_CLUSTERIP
> nf_conntrack ip_tables ip_queue arptable_filter arpt_mangle arp_tables
> x_tables
> jfs sg sd_mod pata_via pata_acpi ata_generic uhci_hcd ehci_hcd libata usbcore
> scsi_mod dock 8139too mii thermal processor fan fuse
>
> ###############################################################################
> /proc/version:
> Linux version 2.6.25.3 (root@hughes) (gcc version 4.2.3 (Ubuntu
> 4.2.3-2ubuntu7)) #2 Sun May 11 15:35:44 EDT 2008

I really dont' know where to begin with this, sorry.  It's _probably_ some
platform-related IRQ delivery problem.  But then again it might be
something else :(

It would certainly be valuable to try some older kernels.

Andrew, thanks so much for your quick reply!

I reported this bug:
> > http://bugzilla.kernel.org/show_bug.cgi?id=10682
> >
> >            Summary: (net 8139too) dual ethernet system, any reasonable
> >                     network causes: NETDEV WATCHDOG: ethN: transmit timed
> >                     out
> >            Product: Drivers
> >            Version: 2.5
> >      KernelVersion: 2.6.25.3
> >           Platform: All
> >         OS/Version: Linux
> >               Tree: Mainline
> >          Component: Network
> >         AssignedTo: jgarzik@pobox.com
> >         ReportedBy: bkuhn@ebb.org

Andrew Morton replied:

> I really dont' know where to begin with this, sorry.  It's _probably_
> some platform-related IRQ delivery problem.  But then again it might be
> something else :(

I understand.  FWIW, I tried every BIOS change imaginable to make sure it
wasn't some weird BIOS interaction.

> It would certainly be valuable to try some older kernels.

What are you suggestions regarding "how old"?  My plan *was* to install a
2.4 based distribution next, but if there are specific 2.6.x versions you
think are worth trying, I'm happy to give a try.  I'd rather try the
2.6.x's you suggest first, of course.

> (switched to email.  Please respond via emailed reply-to-all, not via
> the bugzilla web interface).

Sure thing!

   -- bkuhn

Reply-To: akpm@linux-foundation.org

On Mon, 12 May 2008 17:40:14 -0400
"Bradley M. Kuhn" <bkuhn@ebb.org> wrote:

> Andrew, thanks so much for your quick reply!
> 
> I reported this bug:
> > > http://bugzilla.kernel.org/show_bug.cgi?id=10682
> > >
> > >            Summary: (net 8139too) dual ethernet system, any reasonable
> > >                     network causes: NETDEV WATCHDOG: ethN: transmit timed
> > >                     out
> > >            Product: Drivers
> > >            Version: 2.5
> > >      KernelVersion: 2.6.25.3
> > >           Platform: All
> > >         OS/Version: Linux
> > >               Tree: Mainline
> > >          Component: Network
> > >         AssignedTo: jgarzik@pobox.com
> > >         ReportedBy: bkuhn@ebb.org
> 
> Andrew Morton replied:
> 
> > I really dont' know where to begin with this, sorry.  It's _probably_
> > some platform-related IRQ delivery problem.  But then again it might be
> > something else :(
> 
> I understand.  FWIW, I tried every BIOS change imaginable to make sure it
> wasn't some weird BIOS interaction.
> 
> > It would certainly be valuable to try some older kernels.
> 
> What are you suggestions regarding "how old"?  My plan *was* to install a
> 2.4 based distribution next, but if there are specific 2.6.x versions you
> think are worth trying, I'm happy to give a try.  I'd rather try the
> 2.6.x's you suggest first, of course.

I think an early 2.6 would be a good place to start - 2.6.5. 2.6.9, etc.

If that doesn't help then we can probably safely assume that it's
always been busted.  If that kernel works OK then we can drill in more
cloesly, if you're so inclined (which we hope you are ;))

Alex (quoted below) must have seen my bug ticket regarding the 8319too
WATCHDOG bug and replied to me privately.  I include his message below
primarily for posterity on the bug ticket and mailing list archives.  He's
confirming 2.6.23 fails in the same way as well on this particular box
with the two 8139too cards in it.

I expect to try the older kernel versions Andrew suggested in the next few
days and will report back when I have.

Meanwhile, I have vague and more-or-less unfounded theory that this bug is
specific to having two of the same style card in the same box.  Would it
be useful, assuming that I can't make an older kernel work, to try seeing
if I can physically unwire one of the ethernet cards to see if the problem
occurs with only one card wired up?  (This may be undoable without
breaking something on this tiny box, but I'm willing to have a go if folks
think it might help.)
#########################################################################
Date: Tue, 13 May 2008 16:40:46 +0800
To: bkuhn@ebb.org
Subject: Re: (net 8139too) dual ethernet system, any reasonable network causes: NETDEV
From: "Alex REDACTED" <redacted@example.com>

We're using an ebox 4852/4853 with debian linux kernel 2.6.23.

Today during testing, we found the exact problem that you're reporting -  
NETDEV WATCHDOG timeouts when any reasonable network load is placed on
routing between the ethernet ports.

We're using the 8139too driver too, version 0.9.28.

No solutions yet, we will probably look into it as time permits.

Just thought you might appreciate another kernel version data point.

Cheers,
-- 
Alex.
#########################################################################

I wrote:
>> I reported this bug:
>> > > http://bugzilla.kernel.org/show_bug.cgi?id=10682
>> > >            Summary: (net 8139too) dual ethernet system, any reasonable
>> > >                     network causes: NETDEV WATCHDOG: ethN: transmit
>> timed
>> > >                     out
>> > >      KernelVersion: 2.6.25.3

>> Andrew Morton replied:
> I think [trying] an early 2.6 would be a good place to start -
> 2.6.5. 2.6.9, etc.

I had trouble getting 2.6.5 onto the machine with the distribution it
had.  I have installed a different distribution, and now have 2.6.15
running, and it produces the same error.

So, we know the bug was present in 2.6.15.

Now that I have an older distribution, I should be able to try 2.6.5 and
2.6.9 shortly.  Do you expect it will produce substantially different
results from 2.6.15?

> If that doesn't help then we can probably safely assume that it's
> always been busted.  If that kernel works OK then we can drill in more
> cloesly, if you're so inclined (which we hope you are ;))

I'm absolutely inclinded to do so.  What can I do to get you more
information, other than the above?

Maybe some hints...

I'm Running Feroda 8 on an eBox-4853 and encountering the same NETDEV WATCHDOG Issue. All 2.6 Kernels I tried produced the Bug (Fedora Core 2 with standart and yum updated kernel, Fedora 7 and Fedora 8 with Standard and Updated Kernel).

If someone found a fix or workaround (since this Bug Report is Idle since 18 of may) I would be more than happy to try it as nothing I did fixed the issue till now... :o(

However after doing some testing I found out some points that may hopefully help to trace the Bad Guy (I dont mention having tried all noacpi, noirqpoll etc stuff without success):

The number of open connections:
-------------------------------
Altough the bug comes a little sooner with more connections, downloading a single file (eg. linux distribution with http) also triggers the bug after a certain time (usually after 30 to 60, rarelly 100 Mb of Downloaded Single File Data with no other downloads/Browsing active).

Setting eth0 and eth1 to 10 Mbps Full or Half Duplex of 100 Mbps Half Duplex has no effect in resolving the problem.

Tx Queue Len:
-------------
Changing the Tx Queue length has no effect. Setting it to 1 or 100000 has same effect.

Prerequisit for Bug to happen(?):
---------------------------------
The bug (as far I could see) does only happen when both network adapters are used (in my case as a forwarding router/gateway w/ and w/o OpenVPN and Bridge).

I could download big files from and to the box at full Internet speed (1.5 MBps) with no error of any kind, eventually the Hard Drive got full before completion.

Typical Occurence:
------------------
In my case eth0 is connected to Internet Modem/Firewall and eth1 to Network (I also tried connection directly to a computer without a Switch to see if it could be the trigger for the bug, and it did not change anything).

When I download a big file or the doing heavy Web Browsing (eg Reloading constantly a "loaded" web page), after a certain amount of time and Watching both ethX, following events occur:

1-eth0 drops a few packets ~1-5
2-eth0 gets errors and overruns (Nb of errors == Nb of Overruns) 20-50 of these
3-Dropped packets always > Nb Errors == Nb Overruns
4-Eventually eth1 gets screwed too and produces the same events 1 to 3 but with only 5 or 10 Errors/Overruns/Droped


eth0      Link encap:Ethernet  HWaddr 44:4D:50:04:05:AA  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:13820 errors:20 dropped:39 overruns:20 frame:0
          TX packets:9865 errors:0 dropped:0 overruns:1 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:20373389 (19.4 MiB)  TX bytes:816480 (797.3 KiB)
          Interrupt:18 Base address:0x8c00 

eth1      Link encap:Ethernet  HWaddr 44:4D:50:31:20:BA  
          BROADCAST PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:9953 errors:8 dropped:16 overruns:8 frame:0
          TX packets:13836 errors:0 dropped:0 overruns:1 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:830468 (811.0 KiB)  TX bytes:20373842 (19.4 MiB)
          Interrupt:19 Base address:0xa800 


When tracing what functions get called (lots of heavy and dirty "printk" in a modified driver) one can notice as expected that when the bug occurs, There is a call to rtl8139_start_xmit for eth1 followed by solely function calls related to eth0. The again 1 or 2 rtl8139_start_xmit for eth1 and eventually NETDEV TIMEOUT resets the hardware after a long time...

Jun  1 21:21:56 router kernel: In function (eth0) rtl8139_tx_interrupt ...
Jun  1 21:21:56 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:21:56 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:21:56 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:21:56 router kernel: In function (eth1) rtl8139_start_xmit ...
Jun  1 21:21:56 router kernel: In function (eth1) rtl8139_interrupt ...
Jun  1 21:21:56 router kernel: In function (eth1) rtl8139_tx_interrupt ...
Jun  1 21:21:56 router kernel: In function (eth1) rtl8139_interrupt ...
Jun  1 21:21:56 router kernel: In function (eth1) rtl8139_poll ...
Jun  1 21:21:56 router kernel: In function (eth1) rtl8139_rx ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_start_xmit ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_tx_interrupt ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:21:57 router kernel: In function (eth1) rtl8139_start_xmit ...
Jun  1 21:21:57 router kernel: In function (eth1) rtl8139_interrupt ...
Jun  1 21:21:57 router kernel: In function (eth1) rtl8139_poll ...
Jun  1 21:21:57 router kernel: In function (eth1) rtl8139_rx ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_start_xmit ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:21:57 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:21:58 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:21:58 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:21:58 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:21:58 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:21:58 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:21:58 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:21:58 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:21:58 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:21:58 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:21:58 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:21:58 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:21:58 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:21:58 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:22:00 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:22:00 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:22:00 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:22:06 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:22:06 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:22:06 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:22:14 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:22:14 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:22:14 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:22:14 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:22:14 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:22:14 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:22:30 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:22:30 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:22:30 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:22:41 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:22:41 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:22:41 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:22:51 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:22:51 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:22:51 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:22:54 router kernel: In function (eth1) rtl8139_start_xmit ...
Jun  1 21:22:54 router kernel: In function (eth1) rtl8139_start_xmit ...
Jun  1 21:23:23 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:23:23 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:23:23 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:23:29 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:23:29 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:23:29 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:23:41 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:23:41 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:23:41 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:24:08 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:24:08 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:24:08 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:24:08 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:24:08 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:24:08 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:24:30 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:24:30 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:24:30 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:24:41 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:24:41 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:24:41 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:24:53 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:24:53 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:24:53 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:25:30 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:25:30 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:25:30 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:25:37 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:25:37 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:25:37 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:25:41 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:25:41 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:25:41 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:25:51 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:25:51 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:25:51 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:25:54 router kernel: In function (eth1) rtl8139_start_xmit ...
Jun  1 21:26:05 router kernel: NETDEV WATCHDOG: eth1: transmit timed out
Jun  1 21:26:05 router kernel: In function (eth1) rtl8139_tx_timeout ...
Jun  1 21:26:07 router kernel: In function (eth1) rtl8139_interrupt ...
Jun  1 21:26:07 router kernel: In function (eth1) rtl8139_poll ...
Jun  1 21:26:07 router kernel: In function (eth1) rtl8139_rx ...
Jun  1 21:26:08 router kernel: In function (eth1) rtl8139_tx_timeout_task ...
Jun  1 21:26:08 router kernel: In function (eth1) rtl8139_hw_start ...
Jun  1 21:26:08 router kernel: In function (eth1) rtl_check_media ...
Jun  1 21:26:08 router kernel: In function (eth1) mdio_read...
Jun  1 21:26:08 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:26:08 router kernel: In function (eth0) rtl8139_tx_interrupt ...
Jun  1 21:26:08 router kernel: In function (eth1) mdio_read...
Jun  1 21:26:08 router kernel: In function (eth0) rtl8139_interrupt ...
Jun  1 21:26:08 router kernel: In function (eth1) mdio_read...
Jun  1 21:26:08 router kernel: In function (eth1) mdio_read...
Jun  1 21:26:08 router kernel: eth1: link up, 100Mbps, full-duplex, lpa 0xC5E1
Jun  1 21:26:08 router kernel: In function (eth1) rtl8139_start_xmit ...
Jun  1 21:26:08 router kernel: In function (eth0) rtl8139_poll ...
Jun  1 21:26:08 router kernel: In function (eth0) rtl8139_rx ...
Jun  1 21:26:08 router kernel: In function (eth1) rtl8139_interrupt ...
Jun  1 21:26:08 router kernel: In function (eth1) rtl8139_tx_interrupt ...
Jun  1 21:26:08 router kernel: In function (eth1) rtl8139_start_xmit ...

BTW the Network Chips used in these eBoxes are 8100B (http://www.wdlsystems.com/downloads/specs/1EBOX48_s.pdf) and no real 8139xxx!!!

If there is something I can do to help, please feel free to ask. I'll try it out whenever I have some time :o)

Some more Infos on the system:
- HD is a Transcend SSD with 2Gb
- Actual Running Kernel 2.6.24.7-92.fc8

I've recently been testing this problem further using the hardware we have.

We have two versions of eboxes: the 4853 and the 4852. The 4853 has the optional wireless LAN card installed.

We previously experienced the routing issue with the 4853, and after a bit of testing, we have discovered that the 4852 does not exhibit this behaviour for us. We have a number of 4852s, but only one 4853. More than one 4852 has worked flawlessly for us.

I tried removing the wlan card from the 4853, and it still exhibited the routing problem, leading me to believe that there must be a hardware or BIOS difference between these two models.

It's also worth noting that our hardware is different from the models listed in the manual I have. Our versions have a single RS232 port instead of a parallel printer port.

Regards,
Alex White.

Hello,
had the same problem with 2 Realtek ethernet cards
(Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C)

Installed today the new Kernel (2.6.26) Problem seems to be solved. 
(I did varios Download/upload tests over 8 hours with no tx timeout)

I also tested if the Problem exists when only 1 Interface is up.
with kernel 2.6.25.10 it worked fine if only 1 of the interfaces is up 
(direct connection with a pppoe modem)

Regards
Hannes Hofer

I had the same problem (same hardware), installing 2.6.26 solved it partially for me. It basicly works now, but throughput is somewhat limited when both interfaces are under load. Throughput when used as a router is somewhere between 25-35 MBit/s, while each interface is capable to transfer the full 100 MBit/s when used alone. CPU Usage is according to "top" not limiting performance, so maybe theres still some bug in the 2.6.26 driver.

I have eBox-4854. The hardware difference is that eBox-4854 have additional 4 USB ports *instead of* second ethernet port (when compared with eBox-4852/3). So I have only one ethernet port.

The important thing is that I am suffering with the same problem as guys with eBox-4852/3. The problem occurs on my eBox-4854 when I connect something to one of the additional USB ports. When there is nothing connected to the 4 additional USB ports everything works correctly.

I am suspecting that there is something wrong with IRQ routing between the base board of the eBox (the one containing CPU and one ethernet port) and the additional board (the one containing second ethernet port on eBox-4852/3 or additional 4 USB ports on my eBox-4854).

I am running Fedora 8 on my eBox, now with 2.6.25.11-60.fc8 kernel (the latest available, AFAIK).

Just my 2 cents.

I have a similar issue which I have logged as bug 13830 (http://bugzilla.kernel.org/show_bug.cgi?id=13830)

I have the problem with receive packets vanishing - lowering throughput - with just a single inbuilt ethernet device.

Maybe some of these problems are connected with via cx700 chipset
and conflicts between 8139, snd-hda-intel, ehci-hcd, uhci-hcd and via agp,
as described in ID 15372?
For this chipset there are also a few acpi errors AE_NOT_FOUND
(not reported yet - I do not know if they are important)

jb

Closing as obsolete, if this is still seen with modern kernels please re-open and update