[vortex] Problem with Nokia ADSL modem/hub and 3c905
Ville Herva
vherva@niksula.hut.fi
Wed Sep 25 11:15:00 2002
On Wed, Jan 24, 2001 at 06:33:30PM -0500, you [Donald Becker] wrote:
> On Thu, 25 Jan 2001, Ville Herva wrote:
>
> >
> > eth0: interrupt, status e401, latency 8, cur_rx 317, dirty_rx 317
> > eth0: In interrupt loop, status e401.
> > In boomerang_rx(), status e001, rx_status 8000.
> > Receiving packet size 60 status 803c.
> > eth0: exiting interrupt, status e000.
> > eth0: vortex_close() status e000, Tx status 00.
> > eth0: vortex close stats: rx_nocopy 137 rx_copy 181 tx_queued 264 Rx
> > pre-checksummed 0.
> > bridge-eth0: lost peer eth0
> > bridge-eth0: down
Just an update: with the same net hardware (3c905a, Nokia ADSL hub M1122),
but with new motherboard (Abit ST6R, i815, UP), and new kernel (2.4.18pre3
and its 3c59x.c) the problem still happens:
Sep 23 20:33:36 babbage kernel: eth0: transmit timed out, tx_status 00 status e000.
Sep 23 20:33:36 babbage kernel: diagnostics: net 0cc0 media 8c02 dma 00000020.
Sep 23 20:33:36 babbage kernel: Flags; bus-master 1, dirty 1(1) current 17(1)
Sep 23 20:33:36 babbage kernel: Transmit list 00000000 vs. c784b240.
Sep 23 20:33:36 babbage kernel: 0: @c784b200 length 8000002a status 8000002a
Sep 23 20:33:36 babbage kernel: 1: @c784b240 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 2: @c784b280 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 3: @c784b2c0 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 4: @c784b300 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 5: @c784b340 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 6: @c784b380 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 7: @c784b3c0 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 8: @c784b400 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 9: @c784b440 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 10: @c784b480 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 11: @c784b4c0 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 12: @c784b500 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 13: @c784b540 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 14: @c784b580 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 15: @c784b5c0 length 8000002a status 8000002a
Sep 23 20:33:36 babbage kernel: eth0: vortex_error(), status=0xe005
Sep 23 20:33:36 babbage kernel: eth0: Transmit error, Tx status register 90.
Sep 23 20:33:36 babbage kernel: Flags; bus-master 1, dirty 1(1) current 17(1)
Sep 23 20:33:36 babbage kernel: Transmit list 0784b280 vs. c784b240.
Sep 23 20:33:36 babbage kernel: 0: @c784b200 length 8000002a status 8000002a
Sep 23 20:33:36 babbage kernel: 1: @c784b240 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 2: @c784b280 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 3: @c784b2c0 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 4: @c784b300 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 5: @c784b340 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 6: @c784b380 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 7: @c784b3c0 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 8: @c784b400 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 9: @c784b440 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 10: @c784b480 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 11: @c784b4c0 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 12: @c784b500 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 13: @c784b540 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 14: @c784b580 length 8000002a status 0000002a
Sep 23 20:33:36 babbage kernel: 15: @c784b5c0 length 8000002a status 8000002a
(...)
This happens when I unplug the cable between 3c905a and M1122 and the replug
it. The link light is on at both ends, but I can't ping until I reboot.
I'm only reporting this, since I vaguely recall that Andrew said (*)
something about an IRQ fix that had went to 2.4ac that should fix this.
(Sorry I lost the original mail from Andrew) I guess it wasn't merged in
mainline before 2.4.18pre3 got out?
-- v --
v@iki.fi
(*) When I first reported this with 2.2.18 or so.