All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Hugo Mills <hugo-lkml@carfax.org.uk>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	Tejun Heo <htejun@gmail.com>
Subject: Re: Spurious completions during NCQ
Date: Sat, 16 Feb 2008 09:08:19 -0500	[thread overview]
Message-ID: <47B6EE53.1070101@rtr.ca> (raw)
In-Reply-To: <20080215134658.GB27745@vlad.carfax.org.uk>

Hugo Mills wrote:
>    I'm getting these on my Dell Latitude D830:
> 
> Feb 15 13:06:00 willow kernel: ata1.00: exception Emask 0x2 SAct 0x4 SErr 0x0 action 0x2 frozen
> Feb 15 13:06:00 willow kernel: ata1.00: spurious completions during NCQ issue=0x0 SAct=0x4 FIS=004040a1:00000002
> Feb 15 13:06:00 willow kernel: ata1.00: cmd 61/10:10:26:fb:c4/00:00:02:00:00/40 tag 2 cdb 0x0 data 8192 out
> Feb 15 13:06:00 willow kernel:          res 40/00:10:26:fb:c4/00:00:02:00:00/40 Emask 0x2 (HSM violation)
> Feb 15 13:06:00 willow kernel: ata1: soft resetting port
> Feb 15 13:06:00 willow kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> Feb 15 13:06:00 willow kernel: ata1.00: configured for UDMA/133
> Feb 15 13:06:00 willow kernel: ata1: EH complete
> Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
> Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Write Protect is off
> Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> 
>    In some cases, there are several cmd/res lines listed. It's
> happening about once an hour or so (not correlated with any other
> event that I can see). It doesn't seem to be affecting operation of
> the machine, but it's making me nervous.
> 
>    Can anyone set my mind at rest? (Or suggest a fix?)
..

Tejun, have the spurious completion fixes been backported
to 2.6.23 / 2.6.22 yet ?  Those kernels will be in common use
for some time to come, and this fix is more or less essential.

???

  parent reply	other threads:[~2008-02-16 14:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 13:46 Spurious completions during NCQ Hugo Mills
2008-02-15 15:00 ` Calvin Walton
2008-02-15 15:04   ` Hugo Mills
2008-02-15 15:37     ` Michael Tokarev
2008-02-16 14:08 ` Mark Lord [this message]
2008-03-06  5:56   ` Tejun Heo
2008-03-06  6:05     ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2007-10-13 13:12 Marco Lamberto
2007-09-07 17:57 Sumanth J.V

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=47B6EE53.1070101@rtr.ca \
    --to=liml@rtr.ca \
    --cc=htejun@gmail.com \
    --cc=hugo-lkml@carfax.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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.