linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Jeff Mitchell <jeffrey.mitchell@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: HSM violation errors
Date: Wed, 26 Dec 2007 00:57:35 -0600	[thread overview]
Message-ID: <4771FB5F.6070608@shaw.ca> (raw)
In-Reply-To: <fa.h7PRfrlP7LlqB19GxhqX2RLeHc8@ifi.uio.no>

Jeff Mitchell wrote:
> I'm seeing errors in dmesg and the like.  It appears to be somewhat
> similar to the issue reported here:
> http://kerneltrap.org/mailarchive/linux-kernel/2007/8/25/164711 except
> that my machine doesn't freeze, and everything seems normal --
> hopefully nothing like silent corruption is going on.  Also it's on
> brand new hardware...Intel ICH8 mobile chipset with AHCI.  Output from
> dmesg, hdparm -I /dev/sda and hdparm --drq-hsm-error /dev/sda is
> below...please let me know if there's anything else that would be of
> use (and, of course, if this is something I should be worried about
> :-)  ).
> 
> Thanks.
> Jeff
> 
> 
> dmesg:
> 
> ata1.00: exception Emask 0x2 SAct 0xfffd SErr 0x0 action 0x2 frozen
> ata1.00: spurious completions during NCQ issue=0x1 SAct=0xfffd
> FIS=005040a1:00000002

You didn't say what kernel you were using, but in the latest kernels 
this spurious completion check was removed since it was broken, so this 
error shouldn't happen anymore.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-12-26  6:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.h7PRfrlP7LlqB19GxhqX2RLeHc8@ifi.uio.no>
2007-12-26  6:57 ` Robert Hancock [this message]
2007-12-25  4:53 HSM violation errors Jeff Mitchell

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=4771FB5F.6070608@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=jeffrey.mitchell@gmail.com \
    --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 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).