From: Rick Jones <rick.jones2@hp.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Aaron Lehmann <aaronl@vitelus.com>, Jim Paris <jim@jtan.com>,
netdev@vger.kernel.org
Subject: NIC data corruption
Date: Mon, 02 Apr 2007 10:46:00 -0700 [thread overview]
Message-ID: <46114158.2030007@hp.com> (raw)
In-Reply-To: <p737iswqjq4.fsf@bingen.suse.de>
I changed the title to be more accurate, and culled the distribution to
individuals and netdev
The mention of trying to turn-off CKO and see if the data corruption
goes away leads me to ask a possibly "delicate" question:
Should "Linux" only enable CKO on those NICs certified to have
ECC/parity throughout their _entire_ data path?
rick jones
next prev parent reply other threads:[~2007-04-02 17:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 1:27 Silent corruption on AMD64 Aaron Lehmann
2007-04-01 2:52 ` Andrew Morton
2007-04-01 3:20 ` Aaron Lehmann
2007-04-01 3:03 ` Jim Paris
2007-04-01 4:39 ` Aaron Lehmann
2007-04-01 13:58 ` Andi Kleen
2007-04-02 17:46 ` Rick Jones [this message]
2007-04-02 18:07 ` NIC data corruption 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
2007-04-04 20:45 ` Francois Romieu
2007-04-05 11:41 ` Andi Kleen
2007-04-02 13:30 ` Silent corruption on AMD64 Stuart MacDonald
2007-04-02 13:30 ` Stuart MacDonald
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=46114158.2030007@hp.com \
--to=rick.jones2@hp.com \
--cc=aaronl@vitelus.com \
--cc=andi@firstfloor.org \
--cc=jim@jtan.com \
--cc=netdev@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 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.