From: Matt Garman <matthew.garman@gmail.com>
To: Mdadm <linux-raid@vger.kernel.org>
Subject: status of sas1068 ata-passthrough bug?
Date: Mon, 1 Nov 2010 17:08:38 -0500 [thread overview]
Message-ID: <AANLkTimXicMBtagN0a98eK1DD9rGj4QOqsxiZN32o59Y@mail.gmail.com> (raw)
I've seen a few mentions on this list of kernel bug 14831 / 13594,
where drives on an LSI SAS1068 controller are dropped when smartd is
run:
https://bugzilla.kernel.org/show_bug.cgi?id=14831
https://bugzilla.kernel.org/show_bug.cgi?id=13594
I was just wondering if this bug is "officially" fixed, and if so, in
what kernel version? The Bugzilla entries above don't show it as
fixed, but I saw on this list someone mentioned that it's fixed in
2.6.36 (I think---I can't find that post now).
Thanks,
Matt
next reply other threads:[~2010-11-01 22:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 22:08 Matt Garman [this message]
2010-11-02 22:05 ` status of sas1068 ata-passthrough bug? Cláudio Martins
2010-11-03 3:00 ` Matt Garman
2010-11-03 3:20 ` Cláudio Martins
2010-11-03 3:39 ` Michael Sallaway
2010-11-03 6:29 ` Cláudio Martins
2010-11-03 6:33 ` Michael Sallaway
2010-11-04 12:50 ` Vincent Schut
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=AANLkTimXicMBtagN0a98eK1DD9rGj4QOqsxiZN32o59Y@mail.gmail.com \
--to=matthew.garman@gmail.com \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).