Another SATA device with spurious NCQ completions

linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed

* Another SATA device with spurious NCQ completions
@ 2007-06-25 18:34 Chuck Ebbert
  2007-07-03  7:42 ` Tejun Heo
  0 siblings, 1 reply; 4+ messages in thread
From: Chuck Ebbert @ 2007-06-25 18:34 UTC (permalink / raw)
  To: IDE/ATA development list

From:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=245512


The following error consistently appears at apparently random intervals in syslog:

kernel: ata1.00: exception Emask 0x2 SAct 0x1001 SErr 0x0 action 0x2 frozen
kernel: ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x1001
FIS=004040a1:00000800)
kernel: ata1.00: cmd 61/08:00:39:2b:cc/00:00:08:00:00/40 tag 0 cdb 0x0 data 4096 out
kernel:          res 40/00:00:39:2b:cc/00:00:08:00:00/40 Emask 0x2 (HSM violation)
kernel: ata1.00: cmd 61/08:60:e1:2b:cc/00:00:08:00:00/40 tag 12 cdb 0x0 data
4096 out
kernel:          res 40/00:00:39:2b:cc/00:00:08:00:00/40 Emask 0x2 (HSM violation)

Controller is ATI SB600 using the AHCI driver.
64-bit DMA is disabled.
Disk is:
ata1.00: ATA-7: ST3160812AS, 3.ADJ, max UDMA/133


Can't we just turn off NCQ automatically when this happens?

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Another SATA device with spurious NCQ completions
  2007-06-25 18:34 Another SATA device with spurious NCQ completions Chuck Ebbert
@ 2007-07-03  7:42 ` Tejun Heo
  2007-07-03 12:41   ` Krzysztof Oledzki
  0 siblings, 1 reply; 4+ messages in thread
From: Tejun Heo @ 2007-07-03  7:42 UTC (permalink / raw)
  To: Chuck Ebbert; +Cc: IDE/ATA development list

Chuck Ebbert wrote:
> From:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=245512
> 
> 
> The following error consistently appears at apparently random intervals in syslog:
> 
> kernel: ata1.00: exception Emask 0x2 SAct 0x1001 SErr 0x0 action 0x2 frozen
> kernel: ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x1001
> FIS=004040a1:00000800)
> kernel: ata1.00: cmd 61/08:00:39:2b:cc/00:00:08:00:00/40 tag 0 cdb 0x0 data 4096 out
> kernel:          res 40/00:00:39:2b:cc/00:00:08:00:00/40 Emask 0x2 (HSM violation)
> kernel: ata1.00: cmd 61/08:60:e1:2b:cc/00:00:08:00:00/40 tag 12 cdb 0x0 data
> 4096 out
> kernel:          res 40/00:00:39:2b:cc/00:00:08:00:00/40 Emask 0x2 (HSM violation)
> 
> Controller is ATI SB600 using the AHCI driver.
> 64-bit DMA is disabled.
> Disk is:
> ata1.00: ATA-7: ST3160812AS, 3.ADJ, max UDMA/133
> 
> 
> Can't we just turn off NCQ automatically when this happens?

After sever such occasions, NCQ will be turned off automatically.
Hmm... It's a bit surprising to see this on a Seagate drive tho.  Can
someone crosscheck this by attaching the drive to an intel ahci?

-- 
tejun

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Another SATA device with spurious NCQ completions
  2007-07-03  7:42 ` Tejun Heo
@ 2007-07-03 12:41   ` Krzysztof Oledzki
  2007-07-04  4:39     ` Tejun Heo
  0 siblings, 1 reply; 4+ messages in thread
From: Krzysztof Oledzki @ 2007-07-03 12:41 UTC (permalink / raw)
  To: Tejun Heo; +Cc: Chuck Ebbert, IDE/ATA development list

On 2007-07-03 09:42, Tejun Heo wrote:
> Chuck Ebbert wrote:
>> From:
>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=245512
>>
>>
>> The following error consistently appears at apparently random intervals in syslog:
>>
>> kernel: ata1.00: exception Emask 0x2 SAct 0x1001 SErr 0x0 action 0x2 frozen
>> kernel: ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x1001
>> FIS=004040a1:00000800)
>> kernel: ata1.00: cmd 61/08:00:39:2b:cc/00:00:08:00:00/40 tag 0 cdb 0x0 data 4096 out
>> kernel:          res 40/00:00:39:2b:cc/00:00:08:00:00/40 Emask 0x2 (HSM violation)
>> kernel: ata1.00: cmd 61/08:60:e1:2b:cc/00:00:08:00:00/40 tag 12 cdb 0x0 data
>> 4096 out
>> kernel:          res 40/00:00:39:2b:cc/00:00:08:00:00/40 Emask 0x2 (HSM violation)
>>
>> Controller is ATI SB600 using the AHCI driver.
>> 64-bit DMA is disabled.
>> Disk is:
>> ata1.00: ATA-7: ST3160812AS, 3.ADJ, max UDMA/133
>>
>>
>> Can't we just turn off NCQ automatically when this happens?
> 
> After sever such occasions, NCQ will be turned off automatically.
> Hmm... It's a bit surprising to see this on a Seagate drive tho.  Can
> someone crosscheck this by attaching the drive to an intel ahci?
> 

After upgradin kernel on one of my firewallas (2.6.14->2.6.20) I noticed 
similar problem with another Seagate: ST380817AS connected to ICH6.

ata1: soft resetting port
ata1: hard resetting port
ata1: hard resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: Write Protect is off
SCSI device sda: write cache: enabled, read cache: enabled, doesn't 
support DPO or FUA
ata2: soft resetting port
ata2: hard resetting port
ata2: hard resetting port
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: configured for UDMA/133
ata2: EH complete
SCSI device sdb: 156301488 512-byte hdwr sectors (80026 MB)
sdb: Write Protect is off
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't 
support DPO or FUA
ata1: soft resetting port
ata1: hard resetting port
ata1: hard resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: Write Protect is off
SCSI device sda: write cache: enabled, read cache: enabled, doesn't 
support DPO or FUA
ata1: soft resetting port
ata1: hard resetting port
ata1: hard resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: Write Protect is off
SCSI device sda: write cache: enabled, read cache: enabled, doesn't 
support DPO or FUA
ata2: soft resetting port
ata2: hard resetting port
ata2: hard resetting port
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: configured for UDMA/133
ata2: EH complete
SCSI device sdb: 156301488 512-byte hdwr sectors (80026 MB)
sdb: Write Protect is off
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't 
support DPO or FUA

Disks are working in software (MD) mirror. Disabling NCQ for both disk 
by adding '{ "ST380817AS",    NULL,     ATA_HORKAGE_NONCQ, },' solved my 
issue - there are no more resets.

Part of dmesg:
ahci 0000:00:1f.2: version 2.0
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 4 ports 1.5 Gbps 0xf impl 
SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq pm led slum part
ata1: SATA max UDMA/133 cmd 0xE0802100 ctl 0x0 bmdma 0x0 irq 18
ata2: SATA max UDMA/133 cmd 0xE0802180 ctl 0x0 bmdma 0x0 irq 18
ata3: SATA max UDMA/133 cmd 0xE0802200 ctl 0x0 bmdma 0x0 irq 18
ata4: SATA max UDMA/133 cmd 0xE0802280 ctl 0x0 bmdma 0x0 irq 18
scsi0 : ahci
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-6, max UDMA/133, 156301488 sectors: LBA48 NCQ (not used)
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/133
scsi1 : ahci
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATA-6, max UDMA/133, 156301488 sectors: LBA48 NCQ (not used)
ata2.00: ata2: dev 0 multi count 16
ata2.00: configured for UDMA/133
scsi2 : ahci
ata3: SATA link down (SStatus 0 SControl 300)
scsi3 : ahci
ata4: SATA link down (SStatus 0 SControl 300)
scsi 0:0:0:0: Direct-Access     ATA      ST380817AS       3.42 PQ: 0 ANSI: 5
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't 
support DPO or FUA
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't 
support DPO or FUA
  sda: sda1 sda2 sda3 < sda5 sda6 sda7 >
sd 0:0:0:0: Attached scsi disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: Direct-Access     ATA      ST380817AS       3.42 PQ: 0 ANSI: 5
SCSI device sdb: 156301488 512-byte hdwr sectors (80026 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't 
support DPO or FUA
SCSI device sdb: 156301488 512-byte hdwr sectors (80026 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't 
support DPO or FUA
  sdb: sdb1 sdb2 sdb3 < sdb5 sdb6 sdb7 >
sd 1:0:0:0: Attached scsi disk sdb
sd 1:0:0:0: Attached scsi generic sg1 type 0

Best regards,

			Krzysztof Olędzki

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Another SATA device with spurious NCQ completions
  2007-07-03 12:41   ` Krzysztof Oledzki
@ 2007-07-04  4:39     ` Tejun Heo
  0 siblings, 0 replies; 4+ messages in thread
From: Tejun Heo @ 2007-07-04  4:39 UTC (permalink / raw)
  To: Krzysztof Oledzki; +Cc: Chuck Ebbert, IDE/ATA development list

Krzysztof Oledzki wrote:
> On 2007-07-03 09:42, Tejun Heo wrote:
>> Chuck Ebbert wrote:
>>> From:
>>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=245512
>>>
>>>
>>> The following error consistently appears at apparently random
>>> intervals in syslog:
>>>
>>> kernel: ata1.00: exception Emask 0x2 SAct 0x1001 SErr 0x0 action 0x2
>>> frozen
>>> kernel: ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x1001
>>> FIS=004040a1:00000800)
>>> kernel: ata1.00: cmd 61/08:00:39:2b:cc/00:00:08:00:00/40 tag 0 cdb
>>> 0x0 data 4096 out
>>> kernel:          res 40/00:00:39:2b:cc/00:00:08:00:00/40 Emask 0x2
>>> (HSM violation)
>>> kernel: ata1.00: cmd 61/08:60:e1:2b:cc/00:00:08:00:00/40 tag 12 cdb
>>> 0x0 data
>>> 4096 out
>>> kernel:          res 40/00:00:39:2b:cc/00:00:08:00:00/40 Emask 0x2
>>> (HSM violation)
>>>
>>> Controller is ATI SB600 using the AHCI driver.
>>> 64-bit DMA is disabled.
>>> Disk is:
>>> ata1.00: ATA-7: ST3160812AS, 3.ADJ, max UDMA/133
>>>
>>>
>>> Can't we just turn off NCQ automatically when this happens?
>>
>> After sever such occasions, NCQ will be turned off automatically.
>> Hmm... It's a bit surprising to see this on a Seagate drive tho.  Can
>> someone crosscheck this by attaching the drive to an intel ahci?
>>
> 
> After upgradin kernel on one of my firewallas (2.6.14->2.6.20) I noticed
> similar problem with another Seagate: ST380817AS connected to ICH6.

Can you please give a shot at 2.6.22-rc7?  The log you posted lacks
information about why it's happening.

Thanks.

-- 
tejun

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2007-07-04  4:39 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-06-25 18:34 Another SATA device with spurious NCQ completions Chuck Ebbert
2007-07-03  7:42 ` Tejun Heo
2007-07-03 12:41   ` Krzysztof Oledzki
2007-07-04  4:39     ` Tejun Heo

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).