SATA III recognized as SATA II

Bug #1525450 reported by Grizzly
6
This bug affects 1 person
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-4.2.0-19-generic 4.2.0-19.23~14.04.1
 (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.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc5-wily

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Grizzly (sven-witterstein) wrote :

Just got to it. In Wily-4.4-Kernel thes issues have disappeared (last 20 boots or so all went OK as expected)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.