linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Another SATA device with spurious NCQ completions
Date: Tue, 03 Jul 2007 16:42:30 +0900	[thread overview]
Message-ID: <4689FDE6.2080806@gmail.com> (raw)
In-Reply-To: <46800AD3.7050803@redhat.com>

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

  reply	other threads:[~2007-07-03  7:43 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 [this message]
2007-07-03 12:41   ` Krzysztof Oledzki
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=4689FDE6.2080806@gmail.com \
    --to=htejun@gmail.com \
    --cc=cebbert@redhat.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 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).