On Tue, 11 Feb 2003 18:44:59 +0100, Henrik Persson wrote:
> RL> _same_ errors my guess is you're still running the old driver. Check
> RL> the log at debug=3.
>
> Darn. The same PROBLEMS, not the same errors. Indeed, the errors are not
> there. But the behaviour is still the same, i.e. slow speeds after a
> while.. :/
No errors at all? No "Transmitter underrun" (at debug>1)? I suspect you hit
two more bugs: If the driver resets the chip (e.g. watchdog timeout),
chances are the chip is programmed to go half-duplex -> performance breaks
down. No problem as long as we deal with errors properly, but the Rhine-II
can throw an error the mainline driver doesn't notice because the interrupt
status registers stay clean.
Can I see a complete log (at debug=3), starting with module insertion?
There's got to be some underrun and watchdog timeout.
> But it's not as bad as it got a few minutes ago when I tested the driver
> from scyld.com.. It totally trashed my NIC.. A shame though, since it ran
Define "trashed". How exactly did it misbehave, what did you have to do to
get it back working? Anything interesting in the log before it breaks?
FWIW, it is possible to get a Rhine into a state where physically removing
the PCI card from the computer and keeping both away from any power source
for an hour still results in the driver hanging on boot (after putting
everything back together, of course). I've gone through this twice so far.
Voodoo magic.
Roger
-
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 : Sat Feb 15 2003 - 22:00:35 EST