From: Krzysztof Oledzki <olel@ans.pl>
To: Tejun Heo <htejun@gmail.com>
Cc: Chuck Ebbert <cebbert@redhat.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Another SATA device with spurious NCQ completions
Date: Tue, 03 Jul 2007 14:41:11 +0200 [thread overview]
Message-ID: <468A43E7.2030001@ans.pl> (raw)
In-Reply-To: <4689FDE6.2080806@gmail.com>
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
next prev parent reply other threads:[~2007-07-03 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2007-07-04 4:39 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=468A43E7.2030001@ans.pl \
--to=olel@ans.pl \
--cc=cebbert@redhat.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.