From: Denis Vlasenko <vda@ilport.com.ua>
To: Udo van den Heuvel <udovdh@xs4all.nl>, linux-kernel@vger.kernel.org
Subject: Re: VIA Rhine ethernet driver bug (reprise...)
Date: Tue, 23 Aug 2005 12:21:59 +0300 [thread overview]
Message-ID: <200508231221.59299.vda@ilport.com.ua> (raw)
In-Reply-To: <430A0B69.1060304@xs4all.nl>
[CCing maintaner]
On Monday 22 August 2005 20:29, Udo van den Heuvel wrote:
> Hello,
>
> It appears that the VIA Rhine chipset has some sort of bug which shows
> up in both the standard Linux VIA-Rhine driver and the Rhinefet driver
> that VIA itself provides.
>
> The difference is that the connection is dropped in case of the standard
> Linux driver for VIA Rhine but that the connection remains OK with the
> Rhinefet driver provided by VIA
> (http://www.viaarena.com/downloads/Source/rhinefet.tgz and other places
> on viaarena.com...).
> So VIA Rhinefet driver consumes more CPU but is also more stable.
>
> I wrote about this issue before: http://lkml.org/lkml/2005/8/7/82 &
> http://lkml.org/lkml/2005/1/15/47 etc.
> I opened a bugzilla case: http://bugzilla.kernel.org/show_bug.cgi?id=5030
>
> Who could find out why the standard Linux driver chokes and the Rhinefet
> driver doesn't? Who could fix this bug?
My suggestion was, and still is:
>Since it happens less than once a day, why not just add a code
>to reset the NIC completely in this case, like it is
>typically done in tx_timeout handlers of many NICs, and forget about it?
Do you see any problems in this approach?
--
vda
next prev parent reply other threads:[~2005-08-23 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 17:29 Udo van den Heuvel
2005-08-23 9:21 ` Denis Vlasenko [this message]
2005-08-24 15:50 ` Lee Revell
2005-08-24 16:03 ` Lee Revell
[not found] ` <6981e08b0508252043139cfa2d@mail.gmail.com>
2005-08-26 6:33 ` Denis Vlasenko
2005-08-26 7:49 ` Jeff Garzik
2005-08-26 9:04 ` Roger Luethi
2005-10-04 15:19 ` Jeff Garzik
2005-08-26 10:04 ` Denis Vlasenko
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=200508231221.59299.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=linux-kernel@vger.kernel.org \
--cc=udovdh@xs4all.nl \
/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
all inboxes | Powered by JetHome®