[Bugme-new] [Bug 13551] New: SATA: link online but device misclassified
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Tue Jun 16 11:07:02 PDT 2009
http://bugzilla.kernel.org/show_bug.cgi?id=13551
Summary: SATA: link online but device misclassified
Product: Drivers
Version: 2.5
Kernel Version: 2.6.29-gentoo-r5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Serial
AssignedTo: rmk at arm.linux.org.uk
ReportedBy: marcbowes at gmail.com
Regression: No
Created an attachment (id=21940)
--> (http://bugzilla.kernel.org/attachment.cgi?id=21940)
dmesg
There is a long wait while booting with my new motherboard (Gigabyte EP45-DQ6)
as it appears to be unable to detect the presence of drives correctly. It (the
motherboard) has 6 SATA slots, and I have 4 drives plugged in. I have attached
the full dmesg output, but the area of interest is:
ata1: link is slow to respond, please be patient (ready=0)
ata1: softreset failed (device not ready)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1: link online but device misclassified, retrying
ata1: link is slow to respond, please be patient (ready=0)
ata1: softreset failed (device not ready)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1: link online but device misclassified, retrying
ata1: link is slow to respond, please be patient (ready=0)
ata1: softreset failed (device not ready)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1: link online but device misclassified, retrying
ata1: limiting SATA link speed to 1.5 Gbps
ata1: softreset failed (device not ready)
ata1: SATA link up to 1.5 Gbps (SStatus 113 SControl 310)
ata1: link online but device misclassified, device detection might fail
ata2: link is slow to respond, please be patient (ready=0)
ata2: softreset failed (device not ready)
... (as with ata1)
Enabling AHCI in the BIOS makes difference (except for numbering). The 4 drives
appear to be working correctly (speeds are good, and I haven't noticed any
hiccups). From the linux-ide mailing list, it has been suggested that the issue
is that the kernel is unable to detect that there are no drives on the other
end of the 2 unused ports.
More information about the Bugme-new
mailing list