netdev - Davicom Ethernet (onboard) with many Tx timeouts...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 3 Jan 2007 22:33:08 -0200
From:	Dâniel Fraga <fragabr@...il.com>
To:	netdev@...r.kernel.org
Subject:  Davicom Ethernet (onboard) with many Tx timeouts...

Linux 2.6.19 (but this problem occurs with previous kernels too)
gcc 4.1.1
pentium 3
Module dmfe.ko

dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
eth0: Davicom DM9102 at pci0000:00:10.0, 00:d0:09:18:e1:8a, irq 5.

00:10.0 Ethernet controller: Davicom Semiconductor, Inc. Ethernet 100/10 MBit (rev 10)
        Subsystem: Unknown device 0291:8212
        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 (5000ns min, 10000ns max)
        Interrupt: pin A routed to IRQ 5
        Region 0: I/O ports at d800 [size=128]
        Region 1: Memory at efffae80 (32-bit, non-prefetchable) [size=128]
        Expansion ROM at eff80000 [disabled] [size=256K]
        Capabilities: [50] Power Management version 1
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

eth0      Link encap:Ethernet  HWaddr 00:D0:09:18:E1:8A  
          inet addr:192.168.102.1  Bcast:192.168.102.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1892874 errors:1 dropped:0 overruns:1 frame:1
          TX packets:1611764 errors:1 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          Interrupt:5 Base address:0xd800 

	Everything works fine, except that I have too many kernel
warnings:

Jan  3 22:10:13 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:10:24 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:10:38 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:11:19 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:11:52 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:15:42 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:15:44 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:16:32 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:16:40 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:16:44 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:17:09 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:17:13 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:17:45 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:18:15 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:18:25 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:20:18 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:22:35 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:23:03 belforts vmunix: eth0: Tx timeout - resetting
Jan  3 22:23:30 belforts vmunix: eth0: Tx timeout - resetting

	and, of course, when this occurs, some packets are lost.

	How can I debug this to see if it's a dmfe module bug or a
hardware problem?

	Thank you very much!

-- 
http://u-br.net
Linux 2.6.19: Avast! A bilge rat!
Sao Paulo - SP

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html