netdev - 3c59x: Transmit 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 for Android: free password hash cracker in your pocket

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

Date:   Mon, 7 May 2018 12:26:31 -0400
From:   tedheadster <tedheadster@...il.com>
To:     klassert@...nel.org, netdev <netdev@...r.kernel.org>
Subject: 3c59x: Transmit timeouts

Steffen,
  I am getting mostly transmit errors on a 3c597 Fast Ethernet card.
It is EISA, not PCI. Here is some of the logs with verbosity turned up
a bit:

eth3: using default media 100baseTX
[372] eth3: Initial media type 100baseTX.
eth3:  setting half-duplex.
[372] eth3: vortex_up() irq 9 media status 8882.
<intr> eth3: Media 100baseTX has link beat, 8882.
eth3: transmit timed out, tx_status 00 status 8000.
  diagnostics: net 0c80 media 8882 dma ffffffff fifo 0000
eth3: transmit timed out, tx_status 00 status 8000.
  diagnostics: net 0c80 media 8882 dma ffffffff fifo 0000
eth3: transmit timed out, tx_status 00 status 8000.
  diagnostics: net 0c80 media 8882 dma ffffffff fifo 0000
eth3: transmit timed out, tx_status 00 status 8000.
  diagnostics: net 0c80 media 8882 dma ffffffff fifo 0000
[378] eth3: vortex_close() status 8000, Tx status 00.
[378] eth3: vortex close stats: rx_nocopy 0 rx_copy 0 tx_queued 0 Rx
pre-checksummed 0.

Here is what I got from the registers:

NetworkDiagnostic (net): txEnabled, rxEnabled, statisticsEnabled
MediaStatus (media): auiDisable, linkBeatDetect, linkBeatEnable, crcStripDisable
IntStatus (status): register window 4 selected

I am seeing /proc/interrupts incrementing, so at least some interrupts
are getting to the card.

'tc -s qdisc' reports 4 requeues on 13 packets sent.

'ifconfig' reports 13 tx packets, 11 tx errors, 11 tx dropped (no
overrun, carrier, or collision errors).

I can do the legwork on debugging this. What should I investigate next?

- Matthew