Re: need contact of via-rhine developers

From: H.Rosmanith (Kernel Mailing List) (kernel@wildsau.idv.uni.linz.at)
Date: Tue Aug 20 2002 - 16:59:53 EST


> > thanks! that fixed the transmit-timeouts!

ouch, that was too soon. the new driver performs better, but not 100%
without timeouts.

>
> Btw: The stalling you've seen, was that at 10 or 100 Mbps? Hub or Switch?

a 10 Mbps hub, half duplex connection. I tried with a Surecom and an Asante
hub. I also tried connection the two machines I've been testing with
with a crossover-cable, but things went worse then.

> With debug level 2 (and fixed driver), do you find Abort or Underrun errors
> in your log in situations where stalling occured with the old driver?

old driver, kernel 2.4.19, debug level 2:
  : via-rhine.c:v1.10-LK1.1.13 Nov-17-2001 Written by Donald Becker
  : http://www.scyld.com/network/via-rhine.html
  : via-rhine: reset finished after 5 microseconds.
  : eth0: VIA VT6102 Rhine-II at 0xe800, 00:40:63:c0:b4:8c, IRQ 11.
  : eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 0021.
  : eth0: via_rhine_open() irq 11.
  : eth0: reset finished after 5 microseconds.
  : eth0: Transmit error, Tx status 00008100.
  : NETDEV WATCHDOG: eth0: transmit timed out
  : eth0: Transmit timed out, status 0000, PHY status 786d, resetting...
  : eth0: reset finished after 5 microseconds.

new driver with 2.4.19, debug level 2:
  : via-rhine.c:v1.10-LK1.1.14 May-3-2002 Written by Donald Becker
  : http://www.scyld.com/network/via-rhine.html
  : via-rhine: reset finished after 5 microseconds.
  : eth0: VIA VT6102 Rhine-II at 0xe800, 00:40:63:c0:b4:8c, IRQ 11.
  : eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 0021.
  : eth0: via_rhine_open() irq 11.
  : eth0: reset finished after 5 microseconds.
  : eth0: no IPv6 routers present
  : eth0: Transmit error, Tx status 00008100.
  : eth0: Abort 2008, frame dropped.
  : eth0: Transmit error, Tx status 00008100.
  : eth0: Abort 2008, frame dropped.
  : NETDEV WATCHDOG: eth0: transmit timed out
  : eth0: Transmit timed out, status 0000, PHY status 786d, resetting...
  : eth0: reset finished after 5 microseconds.
  : eth0: Transmit error, Tx status 00008100.
  : eth0: Abort 2008, frame dropped.
  : eth0: Transmit error, Tx status 00008100.
  : eth0: Abort 2008, frame dropped.
  : eth0: Transmit error, Tx status 00008100.
  : eth0: Abort 2008, frame dropped.
  : eth0: Transmit error, Tx status 00008100.
  : eth0: Abort 2008, frame dropped.
  : eth0: Transmit error, Tx status 00008100.
  : eth0: Abort 2008, frame dropped.
  : eth0: Transmit error, Tx status 00008100.
  : eth0: Abort 2008, frame dropped.
  : eth0: Transmit error, Tx status 00008100.
  : eth0: Abort 2008, frame dropped.
  : eth0: Transmit error, Tx status 00008100.
  : eth0: Abort 2008, frame dropped.
  : NETDEV WATCHDOG: eth0: transmit timed out
  : eth0: Transmit timed out, status 0000, PHY status 786d, resetting...
  : eth0: reset finished after 5 microseconds.
  : eth0: Transmit error, Tx status 00008100.
  : eth0: Abort 2008, frame dropped.
  : NETDEV WATCHDOG: eth0: transmit timed out
  : eth0: Transmit timed out, status 0000, PHY status 786d, resetting...
  : eth0: reset finished after 5 microseconds.
  : NETDEV WATCHDOG: eth0: transmit timed out
  : eth0: Transmit timed out, status 0000, PHY status 786d, resetting...
  : eth0: reset finished after 5 microseconds.

shall we continue this via private email?

regards,
h.rosmanith

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Aug 23 2002 - 22:00:21 EST