From: Aaron Lehmann <aaronl@vitelus.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Andi Kleen <andi@firstfloor.org>, Jim Paris <jim@jtan.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: Silent corruption with r8169
Date: Wed, 4 Apr 2007 13:06:04 -0700 [thread overview]
Message-ID: <20070404200603.GX15189@vitelus.com> (raw)
In-Reply-To: <20070404184504.GB7814@electric-eye.fr.zoreil.com>
On Wed, Apr 04, 2007 at 08:45:04PM +0200, Francois Romieu wrote:
> > [adding netdev]
> > [meta-comment: I wish people wouldn't use such unnecessarily broad subjects
> > -- how is it the x86-64 port's or AMD's fault when you have broken hardware?
> > Would anybody write "Silent corruption on i386" or "Silent corruption
> > on Intel" or "Silent corruption on Linux"?]
>
> I hope you feel better now that I changed the subject.
>
> Aaron, I see no clear suspect between 2.6.20.1 and current -git
> that could explain nor fix a corruption in the r8169 driver.
>
> Can you apply on top of latest 2.6.21-rc5-git the patches available at
> http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.21-rc5/r8169-20070402
>
> 000[12]-r8169-foo-bar.patch have been committed a few minutes ago: you
> should check if they apply or not.
I'll try to get to testing this, but I'm wondering if people may have
misunderstood my original post. I don't get any corruption over
Ethernet; it's just corruption on the filesystem during certain load
patterns that involve the Realtek ethernet card.
Aaron
next prev parent reply other threads:[~2007-04-04 20:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070401012736.GT15189@vitelus.com>
[not found] ` <20070401030315.GA24080@jim.sh>
[not found] ` <20070401043905.GV15189@vitelus.com>
2007-04-01 13:58 ` Silent corruption on AMD64 Andi Kleen
2007-04-02 17:46 ` NIC data corruption Rick Jones
2007-04-02 18:07 ` Andi Kleen
2007-04-04 5:00 ` Herbert Xu
2007-04-04 18:45 ` Silent corruption with r8169 Francois Romieu
2007-04-04 20:06 ` Aaron Lehmann [this message]
2007-04-04 20:45 ` Francois Romieu
2007-04-05 11:41 ` Andi Kleen
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=20070404200603.GX15189@vitelus.com \
--to=aaronl@vitelus.com \
--cc=andi@firstfloor.org \
--cc=jim@jtan.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).