SATA III recognized as SATA II
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Following #889071, I want to say that even on Kernel linux-image-
(14.04 LTS with wily-kernel ) the SATA III recognition is a bit shaky, but less than it used to be in the 3.x series.
Also, the SATA-Numbers keep changing, so it is hard to tell which disk has the issue...:
[ 2.481536] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.481568] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.481600] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.485425] ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.649406] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.481503] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) <= Thats unexpected
[ 2.501404] ata14: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2.557461] ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3.468992] ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
(about 10-20% of boots)
---
That's OK, but why different numbers?
[ 2.476286] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.476324] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.476356] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.476386] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.476409] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.480199] ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.500201] ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2.500229] ata14: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3.303818] ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
That is on Asus Sabertooth AMD-FX8350-Board.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1525450
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.