2001-02-15 18:18:11

by Nathan Walp

[permalink] [raw]
Subject: 2.4.1-ac14 tulip woes

The fix in ac14 for the ac13 patch that killed the tulip driver doesn't
quite work either:

Feb 15 13:04:16 patience kernel: LDT allocated for cloned task!
Feb 15 13:04:55 patience kernel: NETDEV WATCHDOG: eth0: transmit timed
out
Feb 15 13:05:27 patience last message repeated 4 times
Feb 15 13:06:31 patience last message repeated 8 times
Feb 15 13:07:35 patience last message repeated 8 times
Feb 15 13:07:59 patience last message repeated 3 times
Feb 15 13:08:07 patience kernel: NETDEV WATCHDOG: eth0: transmit timed
out
Feb 15 13:08:39 patience last message repeated 4 times
Feb 15 13:08:41 patience init: Switching to runlevel: 6

lspci -v from ac13 w/ ac12 tulip driver:

00:0a.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev
20)
Subsystem: Netgear FA310TX
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at 9800 [size=256]
Memory at e0000000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at <unassigned> [disabled] [size=256K]

dmesg snippet from ac13 w/ ac12 tulip driver:
PCI: Found IRQ 5 for device 00:0a.0
eth0: Lite-On 82c168 PNIC rev 32 at 0x9800, 00:A0:CC:61:CC:D2, IRQ 5.
eth0: MII transceiver #1 config 3000 status 7829 advertising 01e1.

Nathan


2001-02-15 18:44:24

by Manfred Spraul

[permalink] [raw]
Subject: Re: 2.4.1-ac14 tulip woes

Nathan Walp wrote:
>
> The fix in ac14 for the ac13 patch that killed the tulip driver doesn't
> quite work either:
>

I need more details:
does it immediately time out (after a few seconds), or a after a few
minutes.

Which network speed do you use? 100MBit half duplex?

Could you please run the tulip-diag program I send you yesterday?
#tulip-diag -mm -aa -f

both before and after the hang.

Thanks,
Manfred