From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: VIA Rhine ethernet driver bug (reprise)
Date: Sun, 07 Aug 2005 20:02:07 +0200 [thread overview]
Message-ID: <42F64C9F.602@xs4all.nl> (raw)
Hello,
In january of this year I mentioned a problem with the Linux kernel
driver for VIA Rhine ethernet chips. (see http://lkml.org/lkml/2005/1/15/47)
In the mean time this bug was reproduced quite a number of times on my
Fedora Core 3 (then)/4 (now) box (a VIA CL6000).
An alternative driver by VIA was used (with kernel 2.6.1x,
http://www.viaarena.com/downloads/Source/rhinefet.tgz); this VIA driver
did not have the Oversized ethernet frame bug but consumes quite a lot
of CPU when transfering a steady stream of a few 1000 KB/S, so it is no
good solution.
Since the ethernet connection goes down due to this bug I think I can
mark the bug as critical. The bug is still present in 2.6.12.
The maintainer of the driver cannot fix the bug. Who can?
Please post here and/or email me with your thoughts about a solution,
ways of fixing the bug. Would a small reward help?
Kind regards,
Udo
next reply other threads:[~2005-08-07 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 18:02 Udo van den Heuvel [this message]
2005-08-11 10:34 ` VIA Rhine ethernet driver bug (reprise) 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=42F64C9F.602@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
/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