From: "Michał Miszewski" <michal.miszewski@gemius.com>
To: linux-scsi@vger.kernel.org
Subject: megaraid_sas: problem with specific hardware only with kernel 3.2.5 and above
Date: Tue, 18 Dec 2012 17:07:27 +0100 [thread overview]
Message-ID: <50D094BF.7000701@gemius.com> (raw)
megaraid_sas driver fails to initialize the storage controller on
some Intel platforms. The issue concerns at least the following hardware:
Intel Server System R2000IP, which includes:
- Intel Server Board S2600IP4
- Intel Integrated RAID Module RMS25CB080 with RES2SV240 RAID Expander Card
The RAID module is listed by lspci as:
01:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2208
[Thunderbolt] (rev 03)
By trying different kernels, we found out, that the problem occurs with
3.2.5 and newer versions. The problem doesn't occur with kernel 3.2.4
and older.
On kernel version 3.2.5 the output is:
megasas: 00.00.06.12-rc1 Wed. Oct. 5 17:00:00 PDT 2011
megasas: 0x1000:0x005b:0x8086:0x3513: bus 1:slot 0:func 0
megaraid_sas 0000:01:00.0: PCI INT A -> GSI 26 (level, low) -> IRQ 26
megaraid_sas 0000:01:00.0: setting latency timer to 64
megasas: Waiting for FW to come to ready state
megasas: FW in FAULT state!!
On kernel 3.2.4:
megasas: 00.00.06.12-rc1 Wed. Oct. 5 17:00:00 PDT 2011
megasas: 0x1000:0x005b:0x8086:0x3513: bus 1:slot 0:func 0
megaraid_sas 0000:01:00.0: PCI INT A -> GSI 26 (level, low) -> IRQ 26
megaraid_sas 0000:01:00.0: setting latency timer to 64
megasas: FW now in Ready state
The 3.2.5 introduces only one modification:
"PCI: Rework ASPM disable code"
(commit 3c076351c4027a56d5005a39a0b518a4ba393ce2)
It looks like this change in kernel behavior for mainboards that don't
report the support for ASPM has impact on the SAS controller
itself, its' firmware or further communication between the driver and
hardware.
We tried the following firmware versions from Intel:
- 23.9.0-0018 (dated 2012-11-17)
- 23.7.0-0033 (the current one)
I can collect more information about the hardware, boot logs etc. and
test the provided patches according to your directions.
Thanks in advance for any help with this issue.
--
Michał Miszewski
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2012-12-18 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 16:07 Michał Miszewski [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-19 10:17 megaraid_sas: problem with specific hardware only with kernel 3.2.5 and above Matthias Prager
[not found] <S1755061Ab2L2AAn/20121229000043Z+354@vger.kernel.org>
2012-12-29 0:10 ` Ron A
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=50D094BF.7000701@gemius.com \
--to=michal.miszewski@gemius.com \
--cc=linux-scsi@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).