Ubuntu
linux-source-2.6.22 package

spurious completions during NCQ Hitachi HTS722016K9A300/HTS722012K9A300/HTS541616J9SA00/HTS542525K9SA00

Bug #137470 reported by Rocco on 2007-09-05

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Fix Released	Medium	Unassigned
	linux-source-2.6.22 (Ubuntu)	Won't Fix	Undecided	Unassigned

Bug Description

Binary package hint: linux-source-2.6.22

I get lots of spurious completions during NCQ on linux-image-2.6.22-10-generic, 2.6.22-10.30 with the following Hitachi harddrive. I read that this was fixed and released in another bug, but obviously it's not for this drive.

hdparm -I /dev/sda
ATA device, with non-removable media
Model Number: Hitachi HTS722016K9A300

dmesg:
[98061.940000] ata1.00: exception Emask 0x2 SAct 0x7fff9 SErr 0x0 action 0x2 frozen
[98061.940000] ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x7fff9 FIS=005040a1:00000004)
[98061.940000] ata1.00: cmd 61/08:00:30:ec:53/00:00:00:00:00/40 tag 0 cdb 0x0 data 4096 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/08:18:a0:ec:1b/00:00:00:00:00/40 tag 3 cdb 0x0 data 4096 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/18:20:00:ed:1b/00:00:00:00:00/40 tag 4 cdb 0x0 data 12288 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/18:28:30:ed:1b/00:00:00:00:00/40 tag 5 cdb 0x0 data 12288 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/08:30:60:ed:1b/00:00:00:00:00/40 tag 6 cdb 0x0 data 4096 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/08:38:98:ed:1b/00:00:00:00:00/40 tag 7 cdb 0x0 data 4096 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/08:40:b8:ed:1b/00:00:00:00:00/40 tag 8 cdb 0x0 data 4096 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/08:48:d0:ed:1b/00:00:00:00:00/40 tag 9 cdb 0x0 data 4096 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/18:50:28:ec:4f/00:00:00:00:00/40 tag 10 cdb 0x0 data 12288 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/08:58:58:ec:4f/00:00:00:00:00/40 tag 11 cdb 0x0 data 4096 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/08:60:60:ec:4f/00:00:00:00:00/40 tag 12 cdb 0x0 data 4096 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/08:68:a8:ee:4f/00:00:00:00:00/40 tag 13 cdb 0x0 data 4096 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/08:70:f8:f0:4f/00:00:00:00:00/40 tag 14 cdb 0x0 data 4096 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/08:78:48:f1:4f/00:00:00:00:00/40 tag 15 cdb 0x0 data 4096 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/08:80:88:ec:9f/00:00:00:00:00/40 tag 16 cdb 0x0 data 4096 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/08:88:e8:ed:9f/00:00:00:00:00/40 tag 17 cdb 0x0 data 4096 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98061.940000] ata1.00: cmd 61/08:90:f8:ed:9f/00:00:00:00:00/40 tag 18 cdb 0x0 data 4096 out
[98061.940000] res 50/00:08:f8:ed:9f/00:00:00:00:00/40 Emask 0x2 (HSM violation)
[98062.252000] ata1: soft resetting port
[98062.424000] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[98062.424000] ata1.00: configured for UDMA/133
[98062.424000] ata1: EH complete
[98062.424000] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
[98062.424000] sd 0:0:0:0: [sda] Write Protect is off
[98062.424000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[98062.424000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Tags:

Revision history for this message

Carl-Christian Salvesen (ccsalvesen) wrote on 2007-09-06:

Download full text (3.4 KiB)

Looks like the same here. Dell Latitude D830 with a Hitachi disk.

hdparm -I /dev/sda:

ATA device, with non-removable media
        Model Number: Hitachi HTS722012K9A300
        Serial Number: 070626DP0300DRG0ZHYA
        Firmware Revision: DCCOC54P
        Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5; Revision: ATA8-AST T13 Project D1697 Revision 0b

dmesg during boot:
[ 51.024000] ata1.00: exception Emask 0x2 SAct 0x7ff5 SErr 0x0 action 0x2 frozen
[ 51.024000] ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x7ff5 FIS=005040a1:00000002)
[ 51.024000] ata1.00: cmd 60/08:00:1f:ff:02/00:00:08:00:00/40 tag 0 cdb 0x0 data 4096 in
[ 51.024000] res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[ 51.024000] ata1.00: cmd 60/08:10:87:5c:36/00:00:02:00:00/40 tag 2 cdb 0x0 data 4096 in
[ 51.024000] res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[ 51.024000] ata1.00: cmd 60/08:20:07:02:34/00:00:02:00:00/40 tag 4 cdb 0x0 data 4096 in
[ 51.024000] res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[ 51.024000] ata1.00: cmd 60/08:28:57:00:59/00:00:08:00:00/40 tag 5 cdb 0x0 data 4096 in
[ 51.024000] res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[ 51.024000] ata1.00: cmd 60/88:30:ef:78:3b/00:00:02:00:00/40 tag 6 cdb 0x0 data 69632 in
[ 51.024000] res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[ 51.024000] ata1.00: cmd 60/08:38:c7:00:48/00:00:02:00:00/40 tag 7 cdb 0x0 data 4096 in
[ 51.024000] res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[ 51.024000] ata1.00: cmd 60/08:40:5f:50:9d/00:00:01:00:00/40 tag 8 cdb 0x0 data 4096 in
[ 51.024000] res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[ 51.024000] ata1.00: cmd 60/08:48:b7:52:9d/00:00:01:00:00/40 tag 9 cdb 0x0 data 4096 in
[ 51.024000] res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[ 51.024000] ata1.00: cmd 60/08:50:bf:10:9e/00:00:01:00:00/40 tag 10 cdb 0x0 data 4096 in
[ 51.024000] res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[ 51.024000] ata1.00: cmd 60/08:58:c7:10:9e/00:00:01:00:00/40 tag 11 cdb 0x0 data 4096 in
[ 51.024000] res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[ 51.024000] ata1.00: cmd 60/08:60:cf:10:9e/00:00:01:00:00/40 tag 12 cdb 0x0 data 4096 in
[ 51.024000] res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[ 51.024000] ata1.00: cmd 60/20:68:d7:10:9e/00:00:01:00:00/40 tag 13 cdb 0x0 data 16384 in
[ 51.024000] res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[ 51.024000] ata1.00: cmd 60/08:70:4f:00:98/00:00:02:00:00/40 tag 14 cdb 0x0 data 4096 in
[ 51.024000] res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[ 51.340000] ata1: soft resetting port
[ 51.512000] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 51.512000] ata1.00: configured for UDMA/133
[ 51.512000] ata1: EH complete
[ 51.512000] sd 0:0:0...

Looks like the same here. Dell Latitude D830 with a Hitachi disk.

hdparm -I /dev/sda:

ATA device, with non-removable media
        Model Number:       Hitachi HTS722012K9A300                 
        Serial Number:      070626DP0300DRG0ZHYA
        Firmware Revision:  DCCOC54P
        Transport:          Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5; Revision: ATA8-AST T13 Project D1697 Revision 0b

dmesg during boot:
[   51.024000] ata1.00: exception Emask 0x2 SAct 0x7ff5 SErr 0x0 action 0x2 frozen
[   51.024000] ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x7ff5 FIS=005040a1:00000002)
[   51.024000] ata1.00: cmd 60/08:00:1f:ff:02/00:00:08:00:00/40 tag 0 cdb 0x0 data 4096 in
[   51.024000]          res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[   51.024000] ata1.00: cmd 60/08:10:87:5c:36/00:00:02:00:00/40 tag 2 cdb 0x0 data 4096 in
[   51.024000]          res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[   51.024000] ata1.00: cmd 60/08:20:07:02:34/00:00:02:00:00/40 tag 4 cdb 0x0 data 4096 in
[   51.024000]          res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[   51.024000] ata1.00: cmd 60/08:28:57:00:59/00:00:08:00:00/40 tag 5 cdb 0x0 data 4096 in
[   51.024000]          res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[   51.024000] ata1.00: cmd 60/88:30:ef:78:3b/00:00:02:00:00/40 tag 6 cdb 0x0 data 69632 in
[   51.024000]          res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[   51.024000] ata1.00: cmd 60/08:38:c7:00:48/00:00:02:00:00/40 tag 7 cdb 0x0 data 4096 in
[   51.024000]          res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[   51.024000] ata1.00: cmd 60/08:40:5f:50:9d/00:00:01:00:00/40 tag 8 cdb 0x0 data 4096 in
[   51.024000]          res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[   51.024000] ata1.00: cmd 60/08:48:b7:52:9d/00:00:01:00:00/40 tag 9 cdb 0x0 data 4096 in
[   51.024000]          res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[   51.024000] ata1.00: cmd 60/08:50:bf:10:9e/00:00:01:00:00/40 tag 10 cdb 0x0 data 4096 in
[   51.024000]          res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[   51.024000] ata1.00: cmd 60/08:58:c7:10:9e/00:00:01:00:00/40 tag 11 cdb 0x0 data 4096 in
[   51.024000]          res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[   51.024000] ata1.00: cmd 60/08:60:cf:10:9e/00:00:01:00:00/40 tag 12 cdb 0x0 data 4096 in
[   51.024000]          res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[   51.024000] ata1.00: cmd 60/20:68:d7:10:9e/00:00:01:00:00/40 tag 13 cdb 0x0 data 16384 in
[   51.024000]          res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[   51.024000] ata1.00: cmd 60/08:70:4f:00:98/00:00:02:00:00/40 tag 14 cdb 0x0 data 4096 in
[   51.024000]          res 50/00:08:4f:00:98/00:00:02:00:00/40 Emask 0x2 (HSM violation)
[   51.340000] ata1: soft resetting port
[   51.512000] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   51.512000] ata1.00: configured for UDMA/133
[   51.512000] ata1: EH complete
[   51.512000] sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
[   51.512000] sd 0:0:0:0: [sda] Write Protect is off
[   51.512000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   51.512000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Revision history for this message

Carl-Christian Salvesen (ccsalvesen) wrote on 2007-09-06:

https://bugzilla.redhat.com/show_bug.cgi?id=249045#c5 -- Maybe fixed upstream?

Revision history for this message

Chuck Short (zulcss) wrote on 2007-09-08:

Added to my git tree

Changed in linux-source-2.6.22:
status:	New → In Progress

Revision history for this message

Rocco (rocco) wrote on 2007-09-17:

Correct me if I'm wrong but only HTS722012K9A300 was added to the list not HTS722016K9A300 which my bug report was talking about. HTS722012K9A300 is the disk in the first comment.....

Revision history for this message

Rocco (rocco) wrote on 2007-09-24:

Please fix this for my drive, especially since you fixed it for the other drive in the first comment.

Rocco (rocco) on 2007-10-03

Changed in linux-source-2.6.22:
status:	In Progress → New

Revision history for this message

Enrico Sardi (enricoss) wrote on 2007-10-04:

Same problem with another hitachi model.

I posted on lkml :

http://groups.google.it/group/linux.kernel/browse_thread/thread/a4bd3c19565a2009/389817602f0cd551?hl=it&lnk=st&q=hitachi+hsm+violation&rnum=3#389817602f0cd551

Someone can add the patch to gutsy?

Thanks a lot!

Enrico

Revision history for this message

Fred (frederic-lespez) wrote on 2007-10-06:

Like Enrico Sardi, I am experiencing this bug too with this disk :
ATA device, with non-removable media
    Model Number: Hitachi HTS541616J9SA00
    Serial Number: SB2461***V3AWE
    Firmware Revision: SB4OC70P

I seems that these models need to be blacklisted. A patch for these harddisks have been applied on kernel 2.6.23 (See lkml thread in Enrico Sardi comment).

This bug is the same as this one :
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/147858/
but for a different HD model and the patch have been backported from 2.6.23.

Please, could you do the same for Hitachi models ?

Revision history for this message

Enrico Sardi (enricoss) wrote on 2007-10-09:

Hi all!

This is a temporary workaround (until the patch arrives...):

sudo gedit /etc/rc.local

and then add the following line:

sh -c "echo 1 > /sys/block/sda/device/queue_depth"

save the file and reboot, this will disable ncq

Bye

Enrico

Revision history for this message

Harvey Muller (hlmuller) wrote on 2007-10-23:

Just a reminder for those that come to this later and are not familiar with bash scripting, Enrico means you should add the line above or before the "exit 0" line. If you add it after the "exit 0" line, then Enrico's line will not run.

Revision history for this message

impact (impact-atlas) wrote on 2007-11-23:

#10

Download full text (4.3 KiB)

I have similar errors occasionally in dmesg with my WD drive (AHCI enabled in bios). Enrico Sardi's workaround works (it seems to reduce disk performance tho :().

Nov 21 11:56:34 msi1719 kernel: [ 242.945605] ata1.00: exception Emask 0x2 SAct 0x7f87d SErr 0x0 action 0x2 frozen
Nov 21 11:56:34 msi1719 kernel: [ 242.945617] ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x7f87d FIS=004040a1:00000400)
Nov 21 11:56:34 msi1719 kernel: [ 242.945631] ata1.00: cmd 61/08:00:9f:a6:b7/00:00:03:00:00/40 tag 0 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [ 242.945634] res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [ 242.945647] ata1.00: cmd 61/10:10:6f:a7:b7/00:00:03:00:00/40 tag 2 cdb 0x0 data 8192 out
Nov 21 11:56:34 msi1719 kernel: [ 242.945650] res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [ 242.945662] ata1.00: cmd 61/10:18:af:a7:b7/00:00:03:00:00/40 tag 3 cdb 0x0 data 8192 out
Nov 21 11:56:34 msi1719 kernel: [ 242.945666] res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [ 242.945677] ata1.00: cmd 61/08:20:f7:a7:b7/00:00:03:00:00/40 tag 4 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [ 242.945681] res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [ 242.945693] ata1.00: cmd 61/08:28:17:a8:b7/00:00:03:00:00/40 tag 5 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [ 242.945696] res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [ 242.945708] ata1.00: cmd 61/08:30:df:a5:b7/00:00:03:00:00/40 tag 6 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [ 242.945711] res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [ 242.945723] ata1.00: cmd 61/08:58:7f:a8:b7/00:00:03:00:00/40 tag 11 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [ 242.945727] res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [ 242.945739] ata1.00: cmd 61/08:60:9f:a8:b7/00:00:03:00:00/40 tag 12 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [ 242.945742] res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [ 242.945754] ata1.00: cmd 61/10:68:df:a6:b7/00:00:03:00:00/40 tag 13 cdb 0x0 data 8192 out
Nov 21 11:56:34 msi1719 kernel: [ 242.945758] res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [ 242.945769] ata1.00: cmd 61/08:70:0f:a7:b7/00:00:03:00:00/40 tag 14 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [ 242.945773] res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [ 242.945785] ata1.00: cmd 61/10:78:3f:a7:b7/00:00:03:00:00/40 tag 15 cdb 0x0 data 8192 out
Nov 21 11:56:34 msi1719 kernel: [ 242.945788] res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [ 242.945800] ata1.00: cmd 61/08:80:27:a...

I have similar errors occasionally in dmesg with my WD drive (AHCI enabled in bios). Enrico Sardi's workaround works (it seems to reduce disk performance tho  :().

Nov 21 11:56:34 msi1719 kernel: [  242.945605] ata1.00: exception Emask 0x2 SAct 0x7f87d SErr 0x0 action 0x2 frozen
Nov 21 11:56:34 msi1719 kernel: [  242.945617] ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x7f87d FIS=004040a1:00000400)
Nov 21 11:56:34 msi1719 kernel: [  242.945631] ata1.00: cmd 61/08:00:9f:a6:b7/00:00:03:00:00/40 tag 0 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [  242.945634]          res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [  242.945647] ata1.00: cmd 61/10:10:6f:a7:b7/00:00:03:00:00/40 tag 2 cdb 0x0 data 8192 out
Nov 21 11:56:34 msi1719 kernel: [  242.945650]          res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [  242.945662] ata1.00: cmd 61/10:18:af:a7:b7/00:00:03:00:00/40 tag 3 cdb 0x0 data 8192 out
Nov 21 11:56:34 msi1719 kernel: [  242.945666]          res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [  242.945677] ata1.00: cmd 61/08:20:f7:a7:b7/00:00:03:00:00/40 tag 4 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [  242.945681]          res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [  242.945693] ata1.00: cmd 61/08:28:17:a8:b7/00:00:03:00:00/40 tag 5 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [  242.945696]          res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [  242.945708] ata1.00: cmd 61/08:30:df:a5:b7/00:00:03:00:00/40 tag 6 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [  242.945711]          res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [  242.945723] ata1.00: cmd 61/08:58:7f:a8:b7/00:00:03:00:00/40 tag 11 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [  242.945727]          res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [  242.945739] ata1.00: cmd 61/08:60:9f:a8:b7/00:00:03:00:00/40 tag 12 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [  242.945742]          res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [  242.945754] ata1.00: cmd 61/10:68:df:a6:b7/00:00:03:00:00/40 tag 13 cdb 0x0 data 8192 out
Nov 21 11:56:34 msi1719 kernel: [  242.945758]          res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [  242.945769] ata1.00: cmd 61/08:70:0f:a7:b7/00:00:03:00:00/40 tag 14 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [  242.945773]          res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [  242.945785] ata1.00: cmd 61/10:78:3f:a7:b7/00:00:03:00:00/40 tag 15 cdb 0x0 data 8192 out
Nov 21 11:56:34 msi1719 kernel: [  242.945788]          res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [  242.945800] ata1.00: cmd 61/08:80:27:a6:b7/00:00:03:00:00/40 tag 16 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [  242.945804]          res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [  242.945815] ata1.00: cmd 61/08:88:37:a6:b7/00:00:03:00:00/40 tag 17 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [  242.945819]          res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [  242.945831] ata1.00: cmd 61/08:90:6f:a6:b7/00:00:03:00:00/40 tag 18 cdb 0x0 data 4096 out
Nov 21 11:56:34 msi1719 kernel: [  242.945834]          res 40/00:94:6f:a6:b7/00:00:03:00:00/40 Emask 0x2 (HSM violation)
Nov 21 11:56:34 msi1719 kernel: [  243.143849] ata1: soft resetting port
Nov 21 11:56:34 msi1719 kernel: [  243.272346] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Nov 21 11:56:34 msi1719 kernel: [  243.315898] ata1.00: configured for UDMA/133
Nov 21 11:56:34 msi1719 kernel: [  243.315950] ata1: EH complete

Computer: MSI GX700PX

ATA device, with non-removable media
        Model Number:       WDC WD2500BEVS-22UST0                   
        Firmware Revision:  01.01A0

Jose De la Rosa (jose-de-la-rosa) on 2007-11-25

Changed in dell:
status:	New → Invalid

Revision history for this message

Matthew Fisher (fishermd-deactivatedaccount) wrote on 2007-12-06:

#11

I'm having the same issue with my System76 Serval as well.

ATA device, with non-removable media
        Model Number: Hitachi HTS542525K9SA00
        Serial Number: <deleted>
        Firmware Revision: BBFOC31P
        Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5; Revision: ATA8-AST T13 Project D1697 Revision 0b

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2007-12-10:

#12

Hi All,

The Hardy Heron kernel was recently uploaded for testing. This kernel was most recently synced with the uptream mainlin kernel, 2.6.24-rc4. I believe a lot of the Hitachi drives listed here were added to the blacklist which should resolve this bug. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2 which is set to come out around Dec 20. However, here are the instructions to install if you choose to do so, otherwise just wait for Alpha2 to come out:

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

Changed in linux:
status:	New → Incomplete

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2007-12-10:

#13

Also just a note that this report will remain open against the actively developed ubuntu kernel. However, against linux-source-2.6.22 it does not meet the criteria for a stable release update and is being closed. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

Changed in linux-source-2.6.22:
status:	New → Won't Fix

Revision history for this message

Harvey Muller (hlmuller) wrote on 2007-12-12:

#14

[Hardy / Alpha 1 / i386]

Leann: ,

The fix in you outline above (2.6.24-1 is kernel updated to) does not work for the Inspiron 1420 with the Hitachi HTS722016K9A300. I continue to get spurious completions. It was however a fun exercise in getting Hardy installed. I have it installed to a separate partition, for further testing under Hardy if necessary.

I've been unable to get Hardy Alpha 1 amd64 successfully installed yet, but if I do, I will test again and report the results.

Best regards,

Harvey

Revision history for this message

Harvey Muller (hlmuller) wrote on 2007-12-12:

#15

[Hardy / Alpha 1 / amd64]

The 2.6.24-1 kernel does not resolve the issue with an amd64 installation either. Didn't figure it would.

Best regards,

Harvey

Revision history for this message

Fred (frederic-lespez) wrote on 2007-12-16:

#16

Leann:
I just installed Hardy Alpha 1, the latest updates and linux-image-2.6.24-1-generic.
The problem seems to have disappeared with Hitachi HTS541616J9SA00
Here is the relevant log messages :
Dec 16 17:48:29 hardy kernel: [ 23.321214] ata3.00: ATA-7: Hitachi HTS541616J9SA00, SB4OC70P, max UDMA/100
Dec 16 17:48:29 hardy kernel: [ 23.321216] ata3.00: 312581808 sectors, multi 16: LBA48 NCQ (not used)
Dec 16 17:48:29 hardy kernel: [ 23.322320] ata3.00: configured for UDMA/100

No more spurious completions !

I will confirm this later after more testing.

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2007-12-19:

#17

Harvey, can you please attach the output of the following command. Thanks!

hdparm -I [device]

Revision history for this message

Harvey Muller (hlmuller) wrote on 2007-12-19:

#18

hdparm -I results Edit (2.8 KiB, text/plain)

Leann,

Sorry for the delay, ; )

The results are attached.

Leann Ogasawara (leannogasawara) on 2007-12-19

Changed in linux:
assignee:	nobody → ubuntu-kernel-team
importance:	Undecided → Medium
status:	Incomplete → Triaged

Revision history for this message

Harvey Muller (hlmuller) wrote on 2007-12-19:

#19

Leann,

Tested hardy-desktop-amd64 (daily 20071218) with kernel version 2.6.24-2, and the problem appears to be resolved. The laptop has been up for over 15 minutes with no "spurious completions" messages. Usually it will have 2-3 messages reported within that timeframe.

Oddly (to me) the queue_depth is at 31.

I will continue checking while uptime increases, and report any further ncq issues if I see them.

Thanks for your help (and the nameless devs that did the work).

Harvey

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2007-12-19:

#20

Per the last few sets of comments, it looks like this issue is resolved with the newer Hardy kernel. I'm going to close this report for now. Please feel free to reopen the report if this issue reappears. Thanks.

Changed in linux:
status:	Triaged → Fix Released

Revision history for this message

Andres Mujica (andres.mujica) wrote on 2007-12-23:

#21

Download full text (6.3 KiB)

I'm having this issue with a vostro 1700 and 2.6.22-14-generic kernel, i've read that it won't get fixed for this kernel, so i wonder what problems would arise in my system if i don´t upgrade to hardy kernel?? would my drive get toasted??.

Also i've found this patch that seems to solve the issue without the need of blacklist each model reported..

http://article.gmane.org/gmane.linux.ide/26012 Issue explanation
http://<email address hidden>/msg240008.html The patch itself.

My hdparm -I /dev/sda

/dev/sda:

ATA device, with non-removable media
        Model Number: ST9160821AS
        Serial Number: removed
        Firmware Revision: 3.CDE
Standards:
        Supported: 7 6 5 4
        Likely used: 7
Configuration:
        Logical max current
        cylinders 16383 16383
        heads 16 16
        sectors/track 63 63
        --
        CHS current addressable sectors: 16514064
        LBA user addressable sectors: 268435455
        LBA48 user addressable sectors: 312581808
        device size with M = 1024*1024: 152627 MBytes
        device size with M = 1000*1000: 160041 MBytes (160 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        Queue depth: 32
        Standby timer values: spec'd by Standard, no device specific minimum
        R/W multiple sector transfer: Max = 16 Current = 8
        Advanced power management level: unknown setting (0x8080)
        Recommended acoustic management value: 128, current value: 0
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           * SMART feature set
                Security Mode feature set
           * Power Management feature set
           * Write cache
           * Look-ahead
           * Host Protected Area feature set
           * WRITE_BUFFER command
           * READ_BUFFER command
           * DOWNLOAD_MICROCODE
           * Advanced Power Management feature set
                SET_MAX security extension
                Automatic Acoustic Management feature set
           * 48-bit Address feature set
           * Mandatory FLUSH_CACHE
           * FLUSH_CACHE_EXT
           * SMART error logging
           * SMART self-test
           * IDLE_IMMEDIATE with UNLOAD
           * SATA-I signaling speed (1.5Gb/s)
           * Native Command Queueing (NCQ)
           * Phy event counters
                Device-initiated interface power management
           * Software settings preservation
           * SMART Command Transport (SCT) feature set
Security:
        Master password revision code = 65534
                supported
        not enabled
        not locked
                frozen
        not expired: security count
        not supported: enhanced erase

and the dmesg | grep ata output

[ 360.444000] ata3: soft resetting port
[ 360...

I'm having this issue with a vostro 1700 and  2.6.22-14-generic kernel, i've read that it won't get fixed for this kernel, so i wonder what problems would arise in my system if i don´t upgrade to hardy kernel?? would my drive get toasted??.

Also i've found this patch that seems to solve the issue without the need of blacklist each model reported..

http://article.gmane.org/gmane.linux.ide/26012    Issue explanation
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg240008.html   The patch itself.

My hdparm -I /dev/sda

/dev/sda:

ATA device, with non-removable media
        Model Number:       ST9160821AS                             
        Serial Number:      removed
        Firmware Revision:  3.CDE   
Standards:
        Supported: 7 6 5 4 
        Likely used: 7
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  268435455
        LBA48  user addressable sectors:  312581808
        device size with M = 1024*1024:      152627 MBytes
        device size with M = 1000*1000:      160041 MBytes (160 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        Queue depth: 32
        Standby timer values: spec'd by Standard, no device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 8
        Advanced power management level: unknown setting (0x8080)
        Recommended acoustic management value: 128, current value: 0
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4 
             Cycle time: no flow control=240ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    SMART feature set
                Security Mode feature set
           *    Power Management feature set
           *    Write cache
           *    Look-ahead
           *    Host Protected Area feature set
           *    WRITE_BUFFER command
           *    READ_BUFFER command
           *    DOWNLOAD_MICROCODE
           *    Advanced Power Management feature set
                SET_MAX security extension
                Automatic Acoustic Management feature set
           *    48-bit Address feature set
           *    Mandatory FLUSH_CACHE
           *    FLUSH_CACHE_EXT
           *    SMART error logging
           *    SMART self-test
           *    IDLE_IMMEDIATE with UNLOAD
           *    SATA-I signaling speed (1.5Gb/s)
           *    Native Command Queueing (NCQ)
           *    Phy event counters
                Device-initiated interface power management
           *    Software settings preservation
           *    SMART Command Transport (SCT) feature set
Security: 
        Master password revision code = 65534
                supported
        not     enabled
        not     locked
                frozen
        not     expired: security count
        not     supported: enhanced erase

and the dmesg | grep ata output

[  360.444000] ata3: soft resetting port
[  360.616000] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  360.624000] ata3.00: configured for UDMA/133
[  360.624000] ata3: EH complete
[ 1520.244000] ata3.00: exception Emask 0x2 SAct 0x7ffc SErr 0x0 action 0x2 frozen
[ 1520.244000] ata3.00: (spurious completions during NCQ issue=0x7fc0 SAct=0x7ffc FIS=004040a1:00000002)
[ 1520.244000] ata3.00: cmd 61/08:10:d1:4e:27/00:00:06:00:00/40 tag 2 cdb 0x0 data 4096 out
[ 1520.244000] ata3.00: cmd 61/08:18:59:4f:27/00:00:06:00:00/40 tag 3 cdb 0x0 data 4096 out
[ 1520.244000] ata3.00: cmd 61/08:20:61:4f:27/00:00:06:00:00/40 tag 4 cdb 0x0 data 4096 out
[ 1520.244000] ata3.00: cmd 61/08:28:71:4f:27/00:00:06:00:00/40 tag 5 cdb 0x0 data 4096 out
[ 1520.244000] ata3.00: cmd 61/10:30:c1:4f:2f/00:00:06:00:00/40 tag 6 cdb 0x0 data 8192 out
[ 1520.244000] ata3.00: cmd 61/08:38:d1:4e:6f/00:00:07:00:00/40 tag 7 cdb 0x0 data 4096 out
[ 1520.244000] ata3.00: cmd 61/10:40:f1:4e:6f/00:00:07:00:00/40 tag 8 cdb 0x0 data 8192 out
[ 1520.244000] ata3.00: cmd 61/08:48:49:4f:6f/00:00:07:00:00/40 tag 9 cdb 0x0 data 4096 out
[ 1520.244000] ata3.00: cmd 61/10:50:19:50:6f/00:00:07:00:00/40 tag 10 cdb 0x0 data 8192 out
[ 1520.244000] ata3.00: cmd 61/08:58:71:50:6f/00:00:07:00:00/40 tag 11 cdb 0x0 data 4096 out
[ 1520.244000] ata3.00: cmd 61/08:60:91:50:6f/00:00:07:00:00/40 tag 12 cdb 0x0 data 4096 out
[ 1520.244000] ata3.00: cmd 61/08:68:61:4f:9f/00:00:07:00:00/40 tag 13 cdb 0x0 data 4096 out
[ 1520.244000] ata3.00: cmd 61/08:70:39:52:9f/00:00:07:00:00/40 tag 14 cdb 0x0 data 4096 out
[ 1520.556000] ata3: soft resetting port
[ 1520.728000] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1520.736000] ata3.00: configured for UDMA/133
[ 1520.736000] ata3: EH complete
[10950.364000] ata3.00: exception Emask 0x2 SAct 0x7fc SErr 0x0 action 0x2 frozen
[10950.364000] ata3.00: (spurious completions during NCQ issue=0x7c0 SAct=0x7fc FIS=004040a1:00000002)
[10950.364000] ata3.00: cmd 61/08:10:f9:4e:3b/00:00:04:00:00/40 tag 2 cdb 0x0 data 4096 out
[10950.364000] ata3.00: cmd 61/08:18:61:4f:3b/00:00:04:00:00/40 tag 3 cdb 0x0 data 4096 out
[10950.364000] ata3.00: cmd 61/10:20:c1:4e:2b/00:00:04:00:00/40 tag 4 cdb 0x0 data 8192 out
[10950.364000] ata3.00: cmd 61/10:28:71:4f:3b/00:00:04:00:00/40 tag 5 cdb 0x0 data 8192 out
[10950.364000] ata3.00: cmd 61/08:30:c1:90:3d/00:00:04:00:00/40 tag 6 cdb 0x0 data 4096 out
[10950.364000] ata3.00: cmd 61/08:38:c9:a6:3d/00:00:04:00:00/40 tag 7 cdb 0x0 data 4096 out
[10950.364000] ata3.00: cmd 61/08:40:11:0f:3e/00:00:04:00:00/40 tag 8 cdb 0x0 data 4096 out
[10950.364000] ata3.00: cmd 61/08:48:49:4f:6f/00:00:07:00:00/40 tag 9 cdb 0x0 data 4096 out
[10950.364000] ata3.00: cmd 61/08:50:91:50:6f/00:00:07:00:00/40 tag 10 cdb 0x0 data 4096 out
[10950.676000] ata3: soft resetting port
[10950.848000] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[10950.856000] ata3.00: configured for UDMA/133
[10950.856000] ata3: EH complete
[18737.040000] ata2: port disabled. ignoring.
[18737.352000] ata5: SATA link down (SStatus 0 SControl 300)
[18737.524000] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[18737.532000] ata3.00: configured for UDMA/133
[18737.580000] ata1.00: configured for UDMA/33

Revision history for this message

impact (impact-atlas) wrote on 2007-12-27:

#22

I tried Hardy Heron Alpha 2 and it works fine in this regard - no more spurious NCQ completions. I'm guessing that the patch which fixes detection of spurious NCQ completion errors (referenced by SEAQ - Andres Mujica) is included.

Revision history for this message

Tomas (tvinar-gmail) wrote on 2008-01-06:

#23

Same problem here with 2.6.22-14-generic

Model Number: HITACHI HTS541612J9SA00
Firmware Revision: SBDIC7UP

Revision history for this message

Enrico Sardi (enricoss) wrote on 2008-01-09:

#24

Hi Tomas,

Did you try my solution?

Bye

Enrico Sardi

Revision history for this message

Tomas (tv35) wrote on 2008-01-09: Re: [Bug 137470] Re: spurious completions during NCQ Hitachi HTS722016K9A300/HTS722012K9A300/HTS541616J9SA00/HTS542525K9SA00

#25

Yes, I did, and it seems to work as a workaround (i.e., since then I
did not see this error in logs). Thank you.

On Jan 9, 2008 6:23 AM, Enrico Sardi <email address hidden> wrote:
> Hi Tomas,
>
> Did you try my solution?
>
> Bye
>
> Enrico Sardi
>
>
> --
> spurious completions during NCQ Hitachi HTS722016K9A300/HTS722012K9A300/HTS541616J9SA00/HTS542525K9SA00
> https://bugs.launchpad.net/bugs/137470
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
--------------------------------------------------------------------------
Tomas Vinar, Postdoctoral Researcher
Biological Statistics and Computational Biology
Cornell University
E-mail: <email address hidden>
Office: 169 Biotechnology Building
Work Phone: +1-607-255-7430

Revision history for this message

Pkapsc (andre-pietsch) wrote on 2008-02-21:

#26

Download full text (4.0 KiB)

Hi all,

I need to disappoint some of you:
Dell Vostro 1700 with a Seagate ST980813ASG

Suggested fix in https://wiki.ubuntu.com/InstallingUbuntuOnADellVostro1700 was to turn off NCQ by piping "1" into /sys/block/sda/device/queue_depth

I did this.

Also I upgraded to 2.6.24 as explained here: http://axebase.net/blog/?p=178 (uses a script "hardy.py")

The problem first occurred to be gone but after about half an hour of working it appeared again:

<--- snip from /var/log/dmesg --->
[ 1866.716836] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout)
[ 1866.716857] ata3: hard resetting link
[ 1867.352238] ata3: port is slow to respond, please be patient (Status 0x80)
[ 1867.867169] ata3: hard resetting link
[ 1867.917645] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1867.919637] ata3.00: configured for UDMA/133
[ 1867.919665] ata3: EH complete
[ 1868.035436] sd 2:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 1868.035580] sd 2:0:0:0: [sda] Write Protect is off
[ 1868.038246] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2371.992310] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout)
[ 2371.992338] ata3: hard resetting link
[ 2372.630043] ata3: port is slow to respond, please be patient (Status 0x80)
[ 2373.098527] ata3: hard resetting link
[ 2373.142150] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2373.144818] ata3.00: configured for UDMA/133
[ 2373.144845] ata3: EH complete
[ 2373.145047] sd 2:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 2373.145089] sd 2:0:0:0: [sda] Write Protect is off
[ 2373.145248] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2398.484827] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout)
[ 2398.484859] ata3: hard resetting link
[ 2401.190281] ata3: port is slow to respond, please be patient (Status 0x80)
[ 2403.768282] ata3: hard resetting link
[ 2404.092050] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2404.094618] ata3.00: configured for UDMA/133
[ 2404.094636] ata3: EH complete
[ 2404.094818] sd 2:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 2404.094859] sd 2:0:0:0: [sda] Write Protect is off
[ 2404.095068] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2558.474374] res 50/00:00:5e:32:04/00:00:00:00:00/e0 Emask 0x50 (ATA bus error)
[ 2558.474405] ata3: hard resetting link
[ 2559.612860] ata3: port is slow to respond, please be patient (Status 0x80)
[ 2560.043102] ata3: hard resetting link
[ 2560.086261] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2560.088424] ata3.00: configured for UDMA/133
[ 2560.088451] ata3: EH complete
[ 2560.104320] sd 2:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 2560.104380] sd 2:0:0:0: [sda] Write Protect is off
[ 2560.107262] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2606.114442] ata3: limiting SATA link speed to 1.5 Gbps
[ 2606.114489] res 40/00:00:5e:32:04/00:00:00:00:00/e0 Emask 0x44 (timeout)
[ 2606.114520] ata3: hard resett...

Hi all,

I need to disappoint some of you:
Dell Vostro 1700 with a Seagate ST980813ASG

Suggested fix in https://wiki.ubuntu.com/InstallingUbuntuOnADellVostro1700 was to turn off NCQ by piping "1" into /sys/block/sda/device/queue_depth

I did this.

Also I upgraded to 2.6.24 as explained here: http://axebase.net/blog/?p=178 (uses a script "hardy.py")

The problem first occurred to be gone but after about half an hour of working it appeared again:

<--- snip from /var/log/dmesg --->
[ 1866.716836]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout)
[ 1866.716857] ata3: hard resetting link
[ 1867.352238] ata3: port is slow to respond, please be patient (Status 0x80)
[ 1867.867169] ata3: hard resetting link
[ 1867.917645] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1867.919637] ata3.00: configured for UDMA/133
[ 1867.919665] ata3: EH complete
[ 1868.035436] sd 2:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 1868.035580] sd 2:0:0:0: [sda] Write Protect is off
[ 1868.038246] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2371.992310]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout)
[ 2371.992338] ata3: hard resetting link
[ 2372.630043] ata3: port is slow to respond, please be patient (Status 0x80)
[ 2373.098527] ata3: hard resetting link
[ 2373.142150] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2373.144818] ata3.00: configured for UDMA/133
[ 2373.144845] ata3: EH complete
[ 2373.145047] sd 2:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 2373.145089] sd 2:0:0:0: [sda] Write Protect is off
[ 2373.145248] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2398.484827]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout)
[ 2398.484859] ata3: hard resetting link
[ 2401.190281] ata3: port is slow to respond, please be patient (Status 0x80)
[ 2403.768282] ata3: hard resetting link
[ 2404.092050] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2404.094618] ata3.00: configured for UDMA/133
[ 2404.094636] ata3: EH complete
[ 2404.094818] sd 2:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 2404.094859] sd 2:0:0:0: [sda] Write Protect is off
[ 2404.095068] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2558.474374]          res 50/00:00:5e:32:04/00:00:00:00:00/e0 Emask 0x50 (ATA bus error)
[ 2558.474405] ata3: hard resetting link
[ 2559.612860] ata3: port is slow to respond, please be patient (Status 0x80)
[ 2560.043102] ata3: hard resetting link
[ 2560.086261] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2560.088424] ata3.00: configured for UDMA/133
[ 2560.088451] ata3: EH complete
[ 2560.104320] sd 2:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 2560.104380] sd 2:0:0:0: [sda] Write Protect is off
[ 2560.107262] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2606.114442] ata3: limiting SATA link speed to 1.5 Gbps
[ 2606.114489]          res 40/00:00:5e:32:04/00:00:00:00:00/e0 Emask 0x44 (timeout)
[ 2606.114520] ata3: hard resetting link
[ 2606.684975] ata3: port is slow to respond, please be patient (Status 0x80)
[ 2607.209738] ata3: hard resetting link
[ 2607.309510] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 2607.312180] ata3.00: configured for UDMA/133
[ 2607.312209] ata3: EH complete
[ 2607.312724] sd 2:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 2607.313137] sd 2:0:0:0: [sda] Write Protect is off
[ 2607.331068] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<--- snap from /var/log/dmesg --->

What should I do now?

I remember to see a patch where NCQ was turned off for ST980813AS in the kernel 2.6.24. But I do have a "ST980813ASG" (note the appended "G"). But then, I have turned off NCQ anyway by piping "1" into /sys/block/sda/device/queue_depth, didn't I?

Do I (and others) experience a wholly different problem here?

TIA
Andre

Revision history for this message

Pkapsc (andre-pietsch) wrote on 2008-02-21:

#27

Hi all

uname -a
Linux vostroxx 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux

Revision history for this message

Pkapsc (andre-pietsch) wrote on 2008-02-27:

#28

Some more logging info
[ 1396.483092] res 50/00:00:d6:7d:89/00:00:00:00:00/e1 Emask 0x50 (ATA bus error)
[ 1396.483112] ata1: hard resetting link
[ 1399.421650] ata1: port is slow to respond, please be patient (Status 0x80)
[ 1403.021202] ata1: hard resetting link
[ 1403.326865] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1403.329406] ata1.00: configured for UDMA/133
[ 1403.329429] ata1: EH complete
[ 1403.402362] sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 1403.402508] sd 0:0:0:0: [sda] Write Protect is off
[ 1403.402694] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1404.285469] res 50/00:00:be:3a:8a/00:00:00:00:00/e1 Emask 0x10 (ATA bus error)
[ 1404.427853] ata1: soft resetting link
[ 1406.924126] ata1: port is slow to respond, please be patient (Status 0xd0)
[ 1409.360792] ata1: hard resetting link
[ 1412.483990] ata1: port is slow to respond, please be patient (Status 0x80)
[ 1415.097181] ata1: hard resetting link
[ 1415.243497] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1415.246061] ata1.00: configured for UDMA/133
[ 1415.246086] ata1: EH complete
[ 1415.300895] sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 1415.310901] sd 0:0:0:0: [sda] Write Protect is off
[ 1415.311407] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1881.827526] res 40/00:00:be:3a:8a/00:00:00:00:00/e1 Emask 0x44 (timeout)
[ 1881.827559] ata1: hard resetting link
[ 1884.557122] ata1: port is slow to respond, please be patient (Status 0x80)
[ 1886.676490] ata1: hard resetting link
[ 1886.839824] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1886.841754] ata1.00: configured for UDMA/133
[ 1886.841784] ata1: EH complete
[ 1886.844734] sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 1886.846095] sd 0:0:0:0: [sda] Write Protect is off
[ 1886.846742] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2160.086015] res 40/00:00:be:3a:8a/00:00:00:00:00/e1 Emask 0x44 (timeout)
[ 2160.086046] ata1: hard resetting link
[ 2162.142880] ata1: port is slow to respond, please be patient (Status 0x80)
[ 2163.788488] ata1: hard resetting link
[ 2163.924745] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2163.927385] ata1.00: configured for UDMA/133
[ 2163.927408] ata1: EH complete
[ 2163.927978] sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 2163.928337] sd 0:0:0:0: [sda] Write Protect is off
[ 2163.928628] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Some more logging info
[ 1396.483092]          res 50/00:00:d6:7d:89/00:00:00:00:00/e1 Emask 0x50 (ATA bus error)
[ 1396.483112] ata1: hard resetting link
[ 1399.421650] ata1: port is slow to respond, please be patient (Status 0x80)
[ 1403.021202] ata1: hard resetting link
[ 1403.326865] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1403.329406] ata1.00: configured for UDMA/133
[ 1403.329429] ata1: EH complete
[ 1403.402362] sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 1403.402508] sd 0:0:0:0: [sda] Write Protect is off
[ 1403.402694] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1404.285469]          res 50/00:00:be:3a:8a/00:00:00:00:00/e1 Emask 0x10 (ATA bus error)
[ 1404.427853] ata1: soft resetting link
[ 1406.924126] ata1: port is slow to respond, please be patient (Status 0xd0)
[ 1409.360792] ata1: hard resetting link
[ 1412.483990] ata1: port is slow to respond, please be patient (Status 0x80)
[ 1415.097181] ata1: hard resetting link
[ 1415.243497] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1415.246061] ata1.00: configured for UDMA/133
[ 1415.246086] ata1: EH complete
[ 1415.300895] sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 1415.310901] sd 0:0:0:0: [sda] Write Protect is off
[ 1415.311407] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1881.827526]          res 40/00:00:be:3a:8a/00:00:00:00:00/e1 Emask 0x44 (timeout)
[ 1881.827559] ata1: hard resetting link
[ 1884.557122] ata1: port is slow to respond, please be patient (Status 0x80)
[ 1886.676490] ata1: hard resetting link
[ 1886.839824] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1886.841754] ata1.00: configured for UDMA/133
[ 1886.841784] ata1: EH complete
[ 1886.844734] sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 1886.846095] sd 0:0:0:0: [sda] Write Protect is off
[ 1886.846742] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2160.086015]          res 40/00:00:be:3a:8a/00:00:00:00:00/e1 Emask 0x44 (timeout)
[ 2160.086046] ata1: hard resetting link
[ 2162.142880] ata1: port is slow to respond, please be patient (Status 0x80)
[ 2163.788488] ata1: hard resetting link
[ 2163.924745] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2163.927385] ata1.00: configured for UDMA/133
[ 2163.927408] ata1: EH complete
[ 2163.927978] sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
[ 2163.928337] sd 0:0:0:0: [sda] Write Protect is off
[ 2163.928628] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Revision history for this message

AnRkey (anrkey) wrote on 2008-03-14:

#29

Enrico

Your workaround sorted my problem out.

I added

sh -c "echo 1 > /sys/block/sda/device/queue_depth"
sh -c "echo 1 > /sys/block/sdb/device/queue_depth"

to my /etc/rc.local

Thanks for this, it will tide me over until hardy stable is out.

John

Revision history for this message

Launchpad Janitor (janitor) wrote on 2008-12-23: Kernel team bugs

#30

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Timothy R. Chavez (timrchavez) on 2014-04-10

Changed in somerville:
status:	New → Invalid
no longer affects:	dell

Revision history for this message

Timothy R. Chavez (timrchavez) wrote on 2014-04-10:

#31

The bug task for the somerville project has been removed by an automated script. This bug has been cloned on that project and is available here: https://bugs.launchpad.net/bugs/1305556

no longer affects:

somerville