From: "Udo van den Heuvel" <udovdh@xs4all.nl>
To: "'Luc Saillard'" <luc@saillard.org>,
"'Marcelo Tosatti'" <marcelo.tosatti@cyclades.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: VIA Rhine ethernet driver bug
Date: Tue, 18 Jan 2005 17:55:34 +0100 [thread overview]
Message-ID: <000701c4fd7e$874a5a00$450aa8c0@hierzo> (raw)
In-Reply-To: <20050117154540.GA2642@sd291.sivit.org>
Hello,
> -----Original Message-----
> From: Luc Saillard [mailto:luc@saillard.org]
> Sent: maandag 17 januari 2005 16:46
> To: Marcelo Tosatti
> Cc: Udo van den Heuvel; linux-kernel@vger.kernel.org
> Subject: Re: VIA Rhine ethernet driver bug
>
>
> On Mon, Jan 17, 2005 at 10:04:27AM -0200, Marcelo Tosatti wrote:
> > On Sat, Jan 15, 2005 at 12:43:33PM +0100, Udo van den Heuvel wrote:
>
> > > On my firewall (VIA EPIA CL-6000 with VIA Rhine network
> chips running FC3
> > > and custom kernels) I see messages like:
> >
> > What kernel version are you using? Its important to inform that.
Problem is in all kernel versions since 1999 or so.
I am at 2.6.10-mm2, experimented with older via-rhince.c drivers.
> It's not a critical bug, but if we can resolv the bug ...
If it drops the link with the net I do think it IS critical.
Most of the time occurences of this bug do make my pppd choke.
ifconfig eth1 down
ifconfig eth1 up
helps.
How can we nail the cause? Fix the bug partly or completely?
Suggestions are very welcome.
Thanks,
Udo
next prev parent reply other threads:[~2005-01-18 16:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 11:43 VIA Rhine ethernet driver bug Udo van den Heuvel
2005-01-17 12:04 ` Marcelo Tosatti
2005-01-17 15:45 ` Luc Saillard
2005-01-18 16:55 ` Udo van den Heuvel [this message]
2005-03-09 20:49 ` jerome lacoste
-- strict thread matches above, loose matches on Subject: below --
2005-01-16 15:31 Udo van den Heuvel
2005-04-10 8:16 Udo van den Heuvel
2005-04-12 15:27 ` Roger Luethi
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='000701c4fd7e$874a5a00$450aa8c0@hierzo' \
--to=udovdh@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=luc@saillard.org \
--cc=marcelo.tosatti@cyclades.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.