On Sat, 3 Jun 2000, Marco Colombo wrote:
> 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.
Do you get this problem with other 2.3/2.4.0-test versions too?
(Since you can make it happen with 2.2 I guess you probably can)
However, looking at the fix for the tulip problem I don't think it's the
same problem. Just the same message.
> 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...
Does it send anything at all? (sbin/ifconfig, TX packets)
Do you get any interrupts counted in /proc/interrupts?
There is an old thread on lkml (named '[2.3.51] via-rhine died' around
March 11, links to archives are of course at http://www.tux.org/lkml)
where some, myself included, started getting these messages. It turned out
to be a misaligned buffer that prevented the card from sending anything.
For what it's worth, things are working fine for me. Here is my dmesg for
2.4.0-test1-ac7.
via-rhine.c:v1.05-LK1.1.5 5/2/2000 Written by Donald Becker
http://www.scyld.com/network/via-rhine.html
eth1: VIA VT3043 Rhine at 0xd400, 00:50:ba:a4:15:86, IRQ 19.
eth1: MII PHY found at address 8, status 0x7809 advertising 05e1 Link 0000.
(and Link becomes 41e1 when I turn on the machine "at the other end")
> 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
These are easy to generate with the 2.2 driver, using 'ping -f', netperf,
apache bench (ab), or similar ...
> eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
> last message repeated 7 times
... but I have never managed to get this with 2.2. Hmm.
What do you have to do in 2.2 to generate these?
Oh, and which compiler do you use? Does it go away if you switch to
something like "good old" gcc 2.7.2.3? (using egcs-1.1.2 myself). Some
more experimental/recent gcc's have miscompiled some via-rhine versions.
/Urban
-
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:18 EST