Created attachment 684653 [details] 3.6.11-1.fc17.x86_64 and 3.7.2-204.fc18.x86_64 boot logs Description of problem: Disks attached to a Marvell Technology Group Ltd. MV88SX6081 8-port SATA II PCI-X Controller (Supermicro AOC-SAT2-MV8) are not recognized with the Fedora 18 provided kernel. Version-Release number of selected component (if applicable): kernel-3.7.2-204.fc18.x86_64 How reproducible: 100% Steps to Reproduce: 1. Boot the system, or unload/load the sata_mv driver module 2. 3. Actual results: Driver reports some errors and disables all attached drives. Expected results: Driver allows access to all attached drives. Additional info: The same hardware configuration works perfectly fine with Fedora 17 (i. e. with the 3.6.11-1.fc17.x86_64 kernel). Other hardware information: - Supermicro X8SAX mainboard - Intel Core i7 quad CPU - 24 GB RAM - Supermicro AOC-SAT2-MV8 S-ATA controller (Marvell MV88SX6081) - 8 x Seagate ST3250620NS disk drives attached to MV88SX6081 See also attached boot logs for the FC17 versus FC18 kernels.
I'll have a patch shortly. This looks like https://bugzilla.kernel.org/show_bug.cgi?id=51881
Please give this scratch build a test when it completes: http://koji.fedoraproject.org/koji/taskinfo?taskID=4893420 and let us know if it solves this particular issue for you. The fix will be needed in F17 as well.
(In reply to comment #2) > Please give this scratch build a test when it completes: > > http://koji.fedoraproject.org/koji/taskinfo?taskID=4893420 > > and let us know if it solves this particular issue for you. > > The fix will be needed in F17 as well. The 3.7.4-201.1.fc18.x86_64 kernel boots fine on my system - it does fix the problem for me. Thanks a lot!
(In reply to comment #3) > (In reply to comment #2) > > Please give this scratch build a test when it completes: > > > > http://koji.fedoraproject.org/koji/taskinfo?taskID=4893420 > > > > and let us know if it solves this particular issue for you. > > > > The fix will be needed in F17 as well. > > The 3.7.4-201.1.fc18.x86_64 kernel boots fine on my system - it does fix the > problem for me. > > Thanks a lot! Great. Thanks for testing. I'll get this into Fedora today.
kernel-3.7.4-204.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/kernel-3.7.4-204.fc18
kernel-3.7.4-104.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.7.4-104.fc17
Package kernel-3.7.4-204.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.7.4-204.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-1443/kernel-3.7.4-204.fc18 then log in and leave karma (feedback).
kernel-3.7.4-204.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
kernel-3.7.5-101.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.7.5-101.fc17
kernel-3.7.6-102.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.7.6-102.fc17
kernel-3.7.6-102.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.