On Sat, 3 Jun 2000, Meelis Roos wrote:
> AC> 2.4.0-test1-ac6
> AC> o Tulip updates (Jeff Garzik)
>
> This breaks my 21143.
> NETDEV WATCHDOG: eth0: transmit timed out
> is all I get. de4x5 works. The card is in 100mbit mode, half-duplex.
> ac4 worked OK. ac7 was the next I tried and it doesn't work. ac6 touched
> tulip so it's probably the cause.
>
> Linux Tulip driver version 0.9.5 (May 30, 2000)
> eth0: Digital DS21143 Tulip rev 65 at 0x6400, 00:48:54:12:83:3F, IRQ 10.
> eth0: EEPROM default media type Autosense.
> eth0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
> eth0: MII transceiver #17 config 3000 status 782d advertising 01e1.
>
> Only the last line and the version differ, earlier the last line read
> eth0: MII transceiver #17 config 3000 status 7829 advertising 01e1.
>
While testing 2.4.0-test1-ac7 I've got a similar problem with a
D-Link 530TX (via-rhine driver). But I think this is an old bug
because i can reproduce it with 2.2.15 (and RHL 2.2.14-12),
drivers version v1.01 2/27/99, v1.05 4/08/2000.
With 2.4.0-test1-ac7 i'm using the included 1.05-LK1.1.5 5/2/2000.
What I get is:
via-rhine.c:v1.05-LK1.1.5 5/2/2000 Written by Donald Becker
http://www.scyld.com/network/via-rhine.html
eth0: VIA VT3043 Rhine at 0xa400, 00:50:ba:c1:e8:93, IRQ 10.
eth0: MII PHY found at address 8, status 0x782d advertising 05e1 Link 41e1.
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
Under 2.2.1[45] the messages were slighlty different:
via-rhine.c:v1.01 2/27/99 Written by Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/via-rhine.html
eth0: VIA VT3043 Rhine at 0xa400, 00:50:ba:c1:e8:93, IRQ 10.
eth0: MII PHY found at address 8, status 0x782d advertising 05e1 Link 41e1.
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
eth0: Something Wicked happened! 001a.
last message repeated 2 times
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
last message repeated 7 times
But looking at the source I can see why (tx_timeout() is now called
by net/sched/sch_generic.c:dev_watchdog() instead of by
via-rhine.c:netdev_timer()), but I can't tell what happens and why.
I've searched a few list archives, but found no answers (just questions).
BTW, I also used to get this:
PCI latency timer (CFLT) is unreasonably low at 32. Setting to 64 clocks.
and set it to 64 in BIOS settings (MB is a ASUS K7V), to get rid of the
message. Does it make sense?
.TM.
--
____/ ____/ /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/ / / ESI s.r.l.
_____/ _____/ _/ Colombo@ESI.it
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:17 EST