From: "H. Peter Anvin" <hpa@zytor.com>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: RAID corruption with kernel 3.2?
Date: Sat, 11 Feb 2012 20:43:15 -0800 [thread overview]
Message-ID: <4F374363.8040306@zytor.com> (raw)
In-Reply-To: <CADNH=7GGPdi87v2nJ1Jfsnym133uYdTiJ4yhtj8mJew2FMjFJQ@mail.gmail.com>
On 02/11/2012 08:14 PM, Mathias Burén wrote:
>
> Details? My>3.2 RAID6 still works fine.
>
What is your hardware configuration? Especially your CPU?
The current suspicion -- but we don't know yet -- is that this is a
problem on Sandy Bridge and some Penryn CPUs which have the XSAVE
instruction, but we might very well be completely wrong on that.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-02-12 4:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-12 2:47 RAID corruption with kernel 3.2? H. Peter Anvin
2012-02-12 4:14 ` Mathias Burén
2012-02-12 4:43 ` H. Peter Anvin [this message]
2012-02-12 4:53 ` Mathias Burén
2012-02-12 16:06 ` Holger Kiehl
2012-02-12 18:00 ` H. Peter Anvin
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=4F374363.8040306@zytor.com \
--to=hpa@zytor.com \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@gmail.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