From: Roger Luethi <rl@hellgate.ch>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: List of pending v2.4 kernel bugs
Date: Fri, 30 Jul 2004 19:29:39 +0200 [thread overview]
Message-ID: <20040730172939.GA24235@k3.hellgate.ch> (raw)
In-Reply-To: <410A8077.7020308@pobox.com>
On Fri, 30 Jul 2004 13:08:07 -0400, Jeff Garzik wrote:
> I am worried because this specific area of code has been "fixed" at
> least twice in recent memory, making Roger's changes the third attempt
> to address this sort of problem.
I wasn't aware of that. At least for via-rhine, I tracked the history
down back when I investigated the bug. IIRC the bug was introduced when
set_bit was replaced.
> I would really like to see verification of patches on the hardware
> affected (big endian), as well as tests on little endian to ensure
> nothing breaks, before applying them.
As I have pointed out before, I verified for Linux 2.6 that without
the patch, multicasting worked on x86 but not on ppc, and that with
the patch multicasting did work on both platforms. If in 2.4 you prefer
stability over fixes for bugs nobody complained about that's fine by
me, though.
I am more concerned with the remaining drivers that at first glance
looked like they had the same problem (atp, winbond, tulip_core) in
2.6. Did anyone ever test these, or try the patches I posted? The only
feedback I remember was on typhoon, which looked okay to me and indeed
turned out to work.
Roger
next prev parent reply other threads:[~2004-07-30 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 14:26 List of pending v2.4 kernel bugs Marcelo Tosatti
2004-07-20 19:57 ` Zwane Mwaikambo
2004-07-20 19:32 ` Marcelo Tosatti
2004-07-21 11:23 ` Roger Luethi
2004-07-30 15:56 ` Marcelo Tosatti
2004-07-30 17:08 ` Jeff Garzik
2004-07-30 17:29 ` Roger Luethi [this message]
2004-07-30 18:10 ` Jeff Garzik
2004-07-30 18:20 ` Roger Luethi
2004-08-05 13:33 ` Multicast Driver Testing Quick How-To v 0.3 [was: Re: List of pending v2.4 kernel bugs] Roger Luethi
2004-08-10 3:48 ` David Dillow
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=20040730172939.GA24235@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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.