From: Denis Vlasenko <vda@ilport.com.ua>
To: Patrick Draper <pdraper@gmail.com>
Cc: Udo van den Heuvel <udovdh@xs4all.nl>, linux-kernel@vger.kernel.org
Subject: Re: VIA Rhine ethernet driver bug (reprise...)
Date: Fri, 26 Aug 2005 09:33:45 +0300 [thread overview]
Message-ID: <200508260933.45402.vda@ilport.com.ua> (raw)
In-Reply-To: <6981e08b0508252043139cfa2d@mail.gmail.com>
On Friday 26 August 2005 06:43, Patrick Draper wrote:
> On 8/23/05, Denis Vlasenko <vda@ilport.com.ua> wrote:
> > >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?
>
> I've refrained from posting here because my hardware is currently in the
> closet, so I can't help too much. I had problems with Rhine on my ME6000
> (VIA Mini-ITX) board. I tried to reset the NIC by unloading kernel modules
> and reloading them, and reinitializing the network, and that didn't work
> for me. The problem was triggered by merely unplugging the ethernet cable.
> When it was plugged back in, the network was gone and only a reboot would
> bring it back.
>
> Sorry I can't file a better bug report, but I won't be able to until
> November at the earliest. But I thought you should know that at least one
> person can't use the approach of resetting the NIC.
May be a known problem. A buglet in MII common code.
Via-rhine maintainer knows about it, as does Jeff.
--
vda
next prev parent reply other threads:[~2005-08-26 6:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 17:29 VIA Rhine ethernet driver bug (reprise...) Udo van den Heuvel
2005-08-23 9:21 ` Denis Vlasenko
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 [this message]
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=200508260933.45402.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=linux-kernel@vger.kernel.org \
--cc=pdraper@gmail.com \
--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