lkml.org 
[lkml]   [2002]   [Nov]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subject[2.4.20-rc1, 2.5.46] Network timeouts, ACPI-related
The specific card in question is a 3com 3c905c-tx-m, but the
motherboard (a Soyo KT400 Dragon Ultra) also has a via-rhine on-board
interface that behaves the same way. I can reproduce this on 2.4.18,
2.4.19, 2.4.20-rc1, 2.5.44, 2.5.45, and 2.5.46, with the following
exception: if ACPI is turned on in the 2.5.x kernels (completely on --
if CPU enumeration only is used, the behaviour is the same as if ACPI
is turned off), the network starts working fine again, but USB (using
uhci-hcd) stops working (rather completely -- I have a USB hub that
has an LED to show whether or not it is powered, and it actually shuts
off if ACPI is turned on). The various sub-options of ACPI seem to
have no effect. It does not matter whether the driver is compiled as
a module, or compiled into the kernel.

The following is left in the logs, repeating once per minute or so:

Nov 7 17:03:23 singularity kernel: NETDEV WATCHDOG: eth0: transmit timed out
Nov 7 17:03:23 singularity kernel: eth0: transmit timed out, tx_status 00 status e601.
Nov 7 17:03:23 singularity kernel: diagnostics: net 0ccc media 88c0 dma 0000003a fifo 8000
Nov 7 17:03:23 singularity kernel: eth0: Interrupt posted but not delivered -- IRQ blocked by another device?
Nov 7 17:03:23 singularity kernel: Flags; bus-master 1, dirty 3728(0) current 3728(0)
Nov 7 17:03:23 singularity kernel: Transmit list 00000000 vs. f5fcb200.
Nov 7 17:03:23 singularity kernel: 0: @f5fcb200 length 800000b9 status 000100b9
Nov 7 17:03:23 singularity kernel: 1: @f5fcb240 length 800000b9 status 000100b9
Nov 7 17:03:23 singularity kernel: 2: @f5fcb280 length 800000b9 status 000100b9
Nov 7 17:03:23 singularity kernel: 3: @f5fcb2c0 length 80000079 status 00010079
Nov 7 17:03:23 singularity kernel: 4: @f5fcb300 length 800000a2 status 000100a2
Nov 7 17:03:23 singularity kernel: 5: @f5fcb340 length 80000079 status 00010079
Nov 7 17:03:23 singularity kernel: 6: @f5fcb380 length 80000050 status 00010050
Nov 7 17:03:23 singularity kernel: 7: @f5fcb3c0 length 8000002a status 0001002a
Nov 7 17:03:23 singularity kernel: 8: @f5fcb400 length 80000050 status 00010050
Nov 7 17:03:23 singularity kernel: 9: @f5fcb440 length 8000002a status 0001002a
Nov 7 17:03:23 singularity kernel: 10: @f5fcb480 length 8000002a status 0001002a
Nov 7 17:03:23 singularity kernel: 11: @f5fcb4c0 length 8000002a status 0001002a
Nov 7 17:03:23 singularity kernel: 12: @f5fcb500 length 8000002a status 0001002a
Nov 7 17:03:23 singularity kernel: 13: @f5fcb540 length 8000002a status 0001002a
Nov 7 17:03:23 singularity kernel: 14: @f5fcb580 length 80000050 status 80010050
Nov 7 17:03:23 singularity kernel: 15: @f5fcb5c0 length 8000002a status 8001002a
Nov 7 17:03:23 singularity kernel: eth0: Resetting the Tx ring pointer.


Please let me know if there is anything else useful I can provide or
do.

--
Zed Pobre <zed@debian.org> a.k.a. Zed Pobre <zed@resonant.org>
PGP key and fingerprint available on finger; encrypted mail welcomed.
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2005-03-22 13:30    [W:0.026 / U:0.152 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site