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 majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to