Jeff Garzik <jeff <at> garzik.org> writes: > This is an update of the recent libahci patchset, currently available > on the 'libahci' branch of > git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git > [...] > The mv-ahci code is obviously still a bit raw with "#if 0" in places, > but it is nonetheless ready for testing. I tested the libata-dev kernel as of commit c3939cc09. I had to comment out a bunch of code (for example, code related to the sntf board in ahci.c and some other stuff) and add a cap2 variable to the ahci_host_priv struct in ahci.h in order to successfully compile the branch. I also had to comment out the pata_enable check in mv-ahci.c:mv_ahci_init_one in order to get the mv_ahci module to initialize my hardware, even though I have the pata_marvell module blacklisted. My test hardware: Intel D75XBX2 motherboard with 2 onboard SATA controllers - ICH7 controller in AHCI mode - 3 disks (2 x ST3320620AS, 1 x ST3500418AS) - Marvell 88SE6145 controller, using AHCI (ahci.marvell_enable=1) - 3 disks (3 x ST3500418AS) I used "fio surface-scan" for my test (is that a good way to test this?) and I found no regressions from the stock Fedora 12 kernel 2.6.31.6-166.fc12.x86_64. However, I was hoping the latest libata-dev branch resolved this issue: https://bugzilla.redhat.com/show_bug.cgi?id=549981 It did not. I continue to get the same error as described in my bugzilla report with libata-dev. I hope that helps. I am willing to help out with other testing on this hardware, as necessary. Please cc me on replies. Tested-by: Raman Gupta <rocketraman@xxxxxxxxxxx> Cheers, Raman Gupta -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html