megaraid_sas: problem with specific hardware only with kernel 3.2.5 and above

megaraid_sas: problem with specific hardware only with kernel 3.2.5 and above

[Michał Miszewski]

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

Re: megaraid_sas: problem with specific hardware only with kernel 3.2.5 and above

[Ron A]

Hello,

After 3 straight days of wrongly debugging the megaraid_sas source code, 
I believe I found the proper work-around/solution for this situation.

Setting linux kernel boot parameter pci=conf1 allows my Intel RAID 
Controller-RMS25PB080 (LSI 2208/Fusion based) to be detected, and the FW 
to transition to Ready state. Without this setting the Card FW responds 
only with 0xF0000000 Fault (Masked).

I found linux kernel series 3.0.0, properly discovered and used the RAID 
card. Things broke for me in kernel series 3.2.0, onward.  So there 
seems to be ?broken? PCI discovery on my Intel s2600 system, using the 
Intel/LSI 2208 card

My System Details:
Card PCI ID: 1000:005b
Card PCI description: LSI Logic / Symbios Logic MegaRAID SAS 2208 
[Thunderbolt] (rev 03) aka Fusion
Card Firmware Version: v23.9.0-0018 (most current to-date)
Card OEM: Intel RAID Module (Card) RMS25PB080 SAS
System Board: s2600CP - E5-2600 Xeon, LGA2011 Socket
System Firmware BIOS level: 01.06.0002 2012/11/15 (most current to-date)

Best Regards,
Ron Allred


> --
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info athttp://vger.kernel.org/majordomo-info.html

Re: megaraid_sas: problem with specific hardware only with kernel 3.2.5 and above

[Matthias Prager]

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