mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* 3com 3c59x stopped working with 2.6.13-rc[56]
@ 2005-08-22 20:27 solt
  2005-08-22 21:36 ` Andrew Morton
  0 siblings, 1 reply; 4+ messages in thread
From: solt @ 2005-08-22 20:27 UTC (permalink / raw)
  To: linux-kernel

Hello,

i tried to boot 2.6.13-rc5-git4 and 2.6.13-rc6-git13 both with the same
result: my 3com (3c59x driver on 3com 905c) card not working.
Here is what I saw in the logs.
Notice the regularity of the log barfs. They continue the same every 10secs.

The upgrade was committed using:
cd /usr/src/linux
patch -p1 < ../patch-2.6.13-rc5
patch -p1 < ../patch-2.6.13-rc5-git4
make oldconfig
make bzImage modules modules_install install

gcc-4.0.1 from Debian testing.

Any ideas?
Regards,
Maciej


18:27:47: eth1: Setting full-duplex based on MII #24 link partner capability of 05e1.
18:32:02: NETDEV WATCHDOG: eth1: transmit timed out
18:32:02: eth1: transmit timed out, tx_status 00 status e601.
18:32:02:   diagnostics: net 0cfa media 8880 dma 0000003a fifo 8800
18:32:02: eth1: Interrupt posted but not delivered -- IRQ blocked by another device?
18:32:02:   Flags; bus-master 1, dirty 16(0) current 16(0)
18:32:02:   Transmit list 00000000 vs. dff2c200.
18:32:02:   0: @dff2c200  length 80000020 status 00010020
18:32:02:   1: @dff2c2a0  length 8000002a status 0001002a
18:32:02:   2: @dff2c340  length 8000002a status 0001002a
18:32:02:   3: @dff2c3e0  length 80000076 status 00010076
18:32:02:   4: @dff2c480  length 8000002a status 0001002a
18:32:02:   5: @dff2c520  length 8000002a status 0001002a
18:32:02:   6: @dff2c5c0  length 8000002a status 0001002a
18:32:02:   7: @dff2c660  length 8000002a status 0001002a
18:32:02:   8: @dff2c700  length 8000002a status 0001002a
18:32:02:   9: @dff2c7a0  length 8000002a status 0001002a
18:32:02:   10: @dff2c840  length 8000002a status 0001002a
18:32:02:   11: @dff2c8e0  length 80000020 status 00010020
18:32:02:   12: @dff2c980  length 80000020 status 00010020
18:32:02:   13: @dff2ca20  length 80000020 status 00010020
18:32:02:   14: @dff2cac0  length 80000076 status 80010076
18:32:02:   15: @dff2cb60  length 80000020 status 80010020
18:32:02: eth1: Resetting the Tx ring pointer.
18:38:02: NETDEV WATCHDOG: eth1: transmit timed out
18:38:02: eth1: transmit timed out, tx_status 00 status e601.
18:38:02:   diagnostics: net 0cfa media 8880 dma 0000003a fifo 8000
18:38:02: eth1: Interrupt posted but not delivered -- IRQ blocked by another device?
18:38:02:   Flags; bus-master 1, dirty 32(0) current 32(0)
18:38:02:   Transmit list 00000000 vs. dff2c200.
18:38:02:   0: @dff2c200  length 80000020 status 00010020
18:38:02:   1: @dff2c2a0  length 80000020 status 00010020
18:38:02:   2: @dff2c340  length 80000020 status 00010020
18:38:02:   3: @dff2c3e0  length 8000002a status 0001002a
18:38:02:   4: @dff2c480  length 8000002a status 0001002a
18:38:02:   5: @dff2c520  length 8000002a status 0001002a
18:38:02:   6: @dff2c5c0  length 8000002a status 0001002a
18:38:02:   7: @dff2c660  length 8000002a status 0001002a
18:38:02:   8: @dff2c700  length 8000002a status 0001002a
18:38:02:   9: @dff2c7a0  length 8000002a status 0001002a
18:38:02:   10: @dff2c840  length 8000002a status 0001002a
18:38:02:   11: @dff2c8e0  length 8000002a status 0001002a
18:38:02:   12: @dff2c980  length 80000020 status 00010020
18:38:02:   13: @dff2ca20  length 80000076 status 00010076
18:38:02:   14: @dff2cac0  length 80000020 status 80010020
18:38:02:   15: @dff2cb60  length 80000020 status 80010020
18:38:02: eth1: Resetting the Tx ring pointer.
18:38:12: NETDEV WATCHDOG: eth1: transmit timed out
18:38:12: eth1: transmit timed out, tx_status 00 status e601.
18:38:12:   diagnostics: net 0cfa media 8880 dma 0000003a fifo 0000
18:38:12: eth1: Interrupt posted but not delivered -- IRQ blocked by another device?
18:38:12:   Flags; bus-master 1, dirty 48(0) current 48(0)
18:38:12:   Transmit list 00000000 vs. dff2c200.
18:38:12:   0: @dff2c200  length 8000002a status 0001002a
18:38:12:   1: @dff2c2a0  length 8000002a status 0001002a
18:38:12:   2: @dff2c340  length 8000002a status 0001002a
18:38:12:   3: @dff2c3e0  length 8000002a status 0001002a
18:38:12:   4: @dff2c480  length 8000002a status 0001002a
18:38:12:   5: @dff2c520  length 8000002a status 0001002a
18:38:12:   6: @dff2c5c0  length 8000002a status 0001002a
18:38:12:   7: @dff2c660  length 8000002a status 0001002a
18:38:12:   8: @dff2c700  length 8000002a status 0001002a
18:38:12:   9: @dff2c7a0  length 8000002a status 0001002a
18:38:12:   10: @dff2c840  length 8000002a status 0001002a
18:38:12:   11: @dff2c8e0  length 8000002a status 0001002a
18:38:12:   12: @dff2c980  length 8000002a status 0001002a
18:38:12:   13: @dff2ca20  length 8000002a status 0001002a
18:38:12:   14: @dff2cac0  length 8000002a status 8001002a
18:38:12:   15: @dff2cb60  length 8000002a status 8001002a
18:38:12: eth1: Resetting the Tx ring pointer.

^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: 3com 3c59x stopped working with 2.6.13-rc[56]
@ 2005-08-23  3:59 Steve Lee
  0 siblings, 0 replies; 4+ messages in thread
From: Steve Lee @ 2005-08-23  3:59 UTC (permalink / raw)
  To: solt; +Cc: Linux Kernel Mailing List

> i tried to boot 2.6.13-rc5-git4 and 2.6.13-rc6-git13 both with the same
> result: my 3com (3c59x driver on 3com 905c) card not working.
> Here is what I saw in the logs.
> Notice the regularity of the log barfs. They continue the same every
10secs.

I'm currently using 2.6.13-rc6-git13 with the 3c95x driver compiled as a
module,
without any issues.  I've tested all of the 2.6.13-* kernels.  One
noticeable
difference, I've been using gcc-3.4.4 and not gcc-4.0.1.

Steve



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-08-23 14:48 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-08-22 20:27 3com 3c59x stopped working with 2.6.13-rc[56] solt
2005-08-22 21:36 ` Andrew Morton
2005-08-23 14:48   ` Maciej Soltysiak
2005-08-23  3:59 Steve Lee

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®