From: Roger Luethi <rl@hellgate.ch>
To: Henrik Persson <nix@socialism.nu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: via rhine bug? (timeouts and resets)
Date: Tue, 11 Feb 2003 19:39:43 +0100 [thread overview]
Message-ID: <20030211183943.GA2443@k3.hellgate.ch> (raw)
In-Reply-To: <200302111745.h1BHjdPY067992@sirius.nix.badanka.com>
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
next prev parent reply other threads:[~2003-02-11 18:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 13:43 via rhine bug? (timeouts and resets) Henrik Persson
2003-02-11 14:18 ` Gianni Tedesco
2003-02-11 14:34 ` Henrik Persson
2003-02-11 16:44 ` Alan Cox
2003-02-11 15:44 ` Roger Luethi
2003-02-11 16:51 ` Henrik Persson
2003-02-11 17:17 ` Roger Luethi
2003-02-11 17:44 ` Henrik Persson
2003-02-11 18:39 ` Roger Luethi [this message]
2003-02-11 18:55 ` Henrik Persson
2003-02-11 19:31 ` Roger Luethi
2003-02-11 20:31 ` Henrik Persson
2003-02-11 21:15 ` Roger Luethi
2003-02-11 17:44 ` Alan Cox
2003-02-12 12:52 ` Roger Luethi
-- strict thread matches above, loose matches on Subject: below --
2003-02-12 14:58 Christian Guggenberger
2003-02-12 16:41 ` Alan Cox
2003-02-12 17:06 ` Christian Guggenberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030211183943.GA2443@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@socialism.nu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox