From: Matthias Prager <linux@matthiasprager.de>
To: michal.miszewski@gemius.com
Cc: linux-scsi@vger.kernel.org, Matthias Prager <linux@matthiasprager.de>
Subject: Re: megaraid_sas: problem with specific hardware only with kernel 3.2.5 and above
Date: Wed, 19 Dec 2012 11:17:52 +0100 [thread overview]
Message-ID: <50D19450.4010402@matthiasprager.de> (raw)
Hello everyone, hello Michal,
I can confirm and reproduce this issue on a different set of hardware:
Intel S1200BTLR Mainboard
LSI MegaRAID 9266-4i Raid-Controller
I haven't tried using a kernel older than 3.2.5 so far, but with kernels
3.2.24 and 3.5.0 I get the following dmesg output:
[ 2.621164] megasas: 00.00.06.15-rc1 Mon. Mar. 19 17:00:00 PDT 2012
[ 2.621179] megasas: 0x1000:0x005b:0x1000:0x9269: bus 1:slot 0:func 0
[ 2.621599] megasas: Waiting for FW to come to ready state
[ 2.621601] megasas: FW in FAULT state!!
As a result I can't access any drives connected to the controller.
Tested Controller firmwares: 23.7.0-0031, 23.7.0-0035 and 23.9.0-0015
Tested Mainboard BIOSes: R0037 (BMC 1.14, FRUSDR 1.14)
I contacted Intel and LSI support a while ago. Intel shot me down by
telling me this wasn't their problem. LSI at least tried to resolve the
issue but thus far failed to do so.
Unfortunately I don't have access to the system on a day-to-day basis,
but I will test eventual fixes as soon as I get the chance.
---
Matthias Prager
next reply other threads:[~2012-12-19 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 10:17 Matthias Prager [this message]
[not found] <S1755061Ab2L2AAn/20121229000043Z+354@vger.kernel.org>
2012-12-29 0:10 ` megaraid_sas: problem with specific hardware only with kernel 3.2.5 and above Ron A
-- strict thread matches above, loose matches on Subject: below --
2012-12-18 16:07 Michał Miszewski
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=50D19450.4010402@matthiasprager.de \
--to=linux@matthiasprager.de \
--cc=linux-scsi@vger.kernel.org \
--cc=michal.miszewski@gemius.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.