All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-kernel@vger.kernel.org
Cc: madduck@madduck.net
Subject: Re: scary messages: HSM violation during boot of 2.6.18/amd64
Date: Fri, 10 Nov 2006 16:12:10 +0100	[thread overview]
Message-ID: <455496CA.5040405@wpkg.org> (raw)

> Hi, I just upgraded my workstation to 2.6.18.2. It has four SATA
> drives in a RAID10, connected to the system in pairs on Promise and
> Via on-board controllers.
> 
> Now on every boot, I see several messages like this for the drives
> connected to the VIA controller (VT6420):
> 
>   ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
>   ata2.00: tag 0 cmd 0xb0 Emask 0x2 stat 0x50 err 0x0 (HSM violation)
>   ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
>   ata1.00: tag 0 cmd 0xb0 Emask 0x2 stat 0x50 err 0x0 (HSM violation)
> 
> What do these mean?
> 
> Also, for the first of the two drives on the Promise/FastTrak
> PDC20378 controller, I see messages like this:
> 
>   ata3: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
> 
> What about those?
> 
> I saw none of that under 2.6.17.x. Should I be worried?

I saw similar when using smartctl / smartd with wrong options (without 
-d ata; in short, smartd tried to talk "IDE language" to SATA device...).


-- 
Tomasz Chmielewski
http://wpkg.org


             reply	other threads:[~2006-11-10 15:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 15:12 Tomasz Chmielewski [this message]
2006-11-10 15:57 ` scary messages: HSM violation during boot of 2.6.18/amd64 martin f krafft
2006-11-10 22:39 ` Valdis.Kletnieks
2006-11-10 22:54   ` Tomasz Chmielewski
2006-11-10 23:10     ` Valdis.Kletnieks
2006-11-11  4:52       ` Tejun Heo
2006-11-11 20:24     ` martin f krafft
  -- strict thread matches above, loose matches on Subject: below --
2006-11-10 14:49 martin f krafft

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=455496CA.5040405@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madduck@madduck.net \
    /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.