Most recent kernel where this bug did not occur: never worked Distribution: Ark Linux Hardware Environment: ASRock 939Dual-SATA2 mainboard (BIOS 1.50), Maxtor 6Y060M0 60GB SATA Harddisk connected to SATA1 port Software Environment: Ark Linux dockyard-devel Problem Description: The sata_uli module loads fine and detects the controller, but fails to see any attached harddisks. The harddisk is seen and identified correctly in the BIOS setup. Related messages on bootup: libata version 1.20 loaded. sata_uli 0000:00:12.1: version 0.5 ACPI: PCI Interrupt 0000:00:12.1[A] -> GSI 19 (level, low) -> IRQ 209 ata1: SATA max UDMA/133 cmd 0xEC00 ctl 0xE082 bmdma 0xD880 irq 209 ata2: SATA max UDMA/133 cmd 0xE000 ctl 0xDC02 bmdma 0xD888 irq 209 ata1: SATA link down (SStatus 0) scsi0: sata_uli ata2: SATA link up 1.5 Gbps (SStatus 113) scsi1 : sata_uli This happens both with an x86 and an x86_64 kernel. Steps to reproduce: Boot Linux on an ASRock 939Dual-SATA2 mainboard w/ an attached Maxtor 6Y060M0 60GB SATA harddisk, try to use the SATA port.
The patches from Tejun Heo solved this issue for me: http://home-tj.org/wiki/index.php/Libata-tj-stable
Created attachment 8837 [details] working boot log with all debug messages enabled in libata