All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Eamonn Hamilton <EAMONN.HAMILTON@saic.com>
Cc: linux-ide@vger.kernel.org, ballen@gravity.phys.uwm.edu
Subject: Re: HSM violation on bootup, ICH7 + ata_piix 2.6.22
Date: Thu, 13 Sep 2007 22:09:22 +0200	[thread overview]
Message-ID: <46E998F2.8070301@gmail.com> (raw)
In-Reply-To: <1189414783.13360.16.camel@ukabzc383.uk.saic.com>

Eamonn Hamilton wrote:
> Thanks for that, I checked the disks and sure enough they were in an
> extended self test, I aborted that and it's all back to normal.
> 
> the only problem, however, is that the system is already running version
> 5.37 of the smartmontools package, which is the most recent as I
> understand it? I don't really want to leave the system with it's disks
> unmonitored, is there anything I can be doing to prevent this behaviour?

Hmmm... That gotta be a different issue then.  Cc'ing Bruce and quoting
the original report.

Eamonn Hamilton wrote:
> > Hi,
> >
> > I'm looking ta a Dell SC440 system for a friend, and it's giving HSM
> > violations at startup.
> >
> > The system itself has an ICH7 chipset, with two seagate ST3160812AS
> > drives attached along with a single ST3400832AS, running kernel 2.6.22
> > and the ata_piix driver.
> >
> > I'm guessing this isn't good  :(
> >
> > Anybody gt any suggestions?
> >
> > The violations are :
> >
> >
> > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> > ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data
> > 123392 in
> >          res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM
> > violation)

-- 
tejun

  reply	other threads:[~2007-09-13 20:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-03 10:39 HSM violation on bootup, ICH7 + ata_piix 2.6.22 Eamonn Hamilton
2007-09-08  7:52 ` Tejun Heo
2007-09-10  8:59   ` Eamonn Hamilton
2007-09-13 20:09     ` Tejun Heo [this message]
2007-09-14 13:56       ` Bruce Allen
2007-09-14 15:09         ` Eamonn Hamilton

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=46E998F2.8070301@gmail.com \
    --to=htejun@gmail.com \
    --cc=EAMONN.HAMILTON@saic.com \
    --cc=ballen@gravity.phys.uwm.edu \
    --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.