Created attachment 691809 [details]
Boot up of 3.7.3-101.fc17.x86_64 via serial port

Description of problem:
When booting with 3.7.3-101.fc17.x86_64, only 1 of 4 devices attached to an mvsas controller are detected. Earlier kernels worked, although the most recent two I used did not do so 100% reliably.

The three missing drives are never detected. The prior kernel I used (3.6.11-1.fc17.x86_64) would intermittently fail to detect one or two at boot, and thus cause havoc for mdraid, but would eventually detect them and I could hot "--re-add" them via mdadm.

Version-Release number of selected component (if applicable):
Kernel 3.6.9-2.fc17.x86_64


How reproducible:
Every time with 3.6.9-2.fc17.x86_64. I would intermittently have problems with 3.6.11-1.fc17.x86_64. I have rolled back to 3.6.9-2.fc17.x86_64 and have not had problems since.


Steps to Reproduce:
1. Hook up multiple SATA drives to a Marvell SAS controller
2. Boot 3.7.3-101.fc17.x86_64
3.
  
Actual results:
Missing drives, and in my case failed or degraded mdadm arrays.

Expected results:
All drives detected and usable by mdadm during boot.


Additional info:
The controller is a Highpoint RocketRAID 2740 with dual Marvell 9485 controllers on board.

06:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9125 PCIe SATA 6.0 Gb/s controller (rev 11)
07:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9125 PCIe SATA 6.0 Gb/s controller (rev 11)

The drives are a mixture of Hitachi and Samsung 2TB SATA drives.

I have a total of 14 drives. There are 6 connected via on motherboard SATA. There are 4 connected via two dual port Marvell AHCI cards. So, 10 are connected by AHCI native SATA and 4 are SATA drives connected via mvsas.