Hi!
I promised to get back on the stability issue: well it is NOT stable. One boot 
it works, the next is doesn't - behavior is unpredictable

I supply two logs: 
1) the successful boot:

[    2.274525] ata3: SATA max UDMA/133 irq_stat 0x02400000, PHY RDY changed irq 
16
...
[    2.274525] ata3: SATA max UDMA/133 irq_stat 0x02400000, PHY RDY changed irq 
16
...
[    8.236061] ata3.00: qc timeout (cmd 0xec)
[    8.236196] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[    8.556068] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    8.557570] ata3.00: ATA-8: V4-CT032V4SSD2, S5FAMM22, max UDMA/100
[    8.557644] ata3.00: 62533296 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    8.558420] ata3.00: configured for UDMA/100
...
[   22.816084] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[   22.816174] ata3.00: failed command: IDENTIFY DEVICE
[   22.816257] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
[   22.816262]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
[   22.816408] ata3.00: status: { DRDY }
[   22.816479] ata3: hard resetting link
[   23.136067] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   23.138273] ata3.00: configured for UDMA/100
[   23.138378] ata3: EH complete
...
[   40.816319] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[   40.837751] ata3.00: failed command: IDENTIFY DEVICE
[   40.848725] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
[   40.848730]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
[   40.880902] ata3.00: status: { DRDY }
[   40.891862] ata3: hard resetting link
[   41.352330] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   41.354441] ata3.00: configured for UDMA/100
[   41.354496] ata3: EH complete


And 2) the unsuccessful boot:

[    2.239979] ata3: SATA max UDMA/133 abar m1024@0xfddff000 port 0xfddff100 
irq 16
...
[    2.796072] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
...
[    7.796063] ata3.00: qc timeout (cmd 0xec)
[    7.796086] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[    8.116069] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   15.153557]  sdc1
[   15.155748] sd 7:0:0:0: [sdc] Assuming drive cache: write through
...
[   18.116060] ata3.00: qc timeout (cmd 0xec)
[   18.116082] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   18.116095] ata3: limiting SATA link speed to 1.5 Gbps
[   18.436068] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   48.436045] ata3.00: qc timeout (cmd 0xec)
[   48.436063] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   48.756064] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

On the second log: note the long delay after the logged event at
8.116069, this is EXACTLY as appears in the output of DMESG

Any suggestions?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094288

Title:
  11ab:6145 problem with 88SE6145 SATA II controller

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094288/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to