Re: via-rhine nic crazyness on PIII Xeon SMP running 2.2.5 - 2.2.11

Marques Johansson (displague@linuxfan.com)
Thu, 12 Aug 1999 16:17:36 -0400 (EDT)

Aha! I just remembered what would happen...
The problem stopped when I got a 10/100mbit fdx switch ... Prior, when i
had only a 10mbs hub it appeared as though the increase in net activity
would cause the nic to want to go into 100mbit mode (even though the hub
could not support it) .. This would give *something wicked*. When i
would unplug the cable from the nic/wait a sec/ and put it back in - it
would work again...
--
  Marques Johansson
displague@linuxfan.com


Warning! This not checked for grammer or speling. You figure it out!
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!




On Thu, 12 Aug 1999, mike burrell wrote:


> I've had the same thing with my Via Rhine (Acer ALN-320) on a non-SMP box. 
> Works great, but if I *REALLY* work it (10Mbit/s solid for a few minutes)
> I'll get "eth0: Something wicked happened! 001a".  If I keep working the
> Ethernet card (usually if I'm compiling something big over NFS), then
> eventually the card will die completely; I'll get non-stop NFS errors; the
> activity LED on the hub won't do anything (though the link LED is still on). 
> Since this box is on NFS root, that means it's time for me to reboot.  The
> workaround is to not do anything really network intensive on this box, which
> works fairly well.  I've gone through via-rhine.c a million times, trying to
> find some significance to 0x001a (since that's the number I always get),
> without any success.  Now I see that some people are getting this thing with
> a different number.  Hmm.  I'll play around with it again and see if I can
> dig up some more info on this bug.






-
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/