From: martin f krafft <madduck@madduck.net>
To: linux-kernel@vger.kernel.org
Subject: Re: scary messages: HSM violation during boot of 2.6.18/amd64
Date: Fri, 10 Nov 2006 16:57:48 +0100 [thread overview]
Message-ID: <20061110155748.GA6081@piper.madduck.net> (raw)
In-Reply-To: <455496CA.5040405@wpkg.org>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
also sprach Tomasz Chmielewski <mangoo@wpkg.org> [2006.11.10.1612 +0100]:
> I saw similar when using smartctl / smartd with wrong options (without
> -d ata; in short, smartd tried to talk "IDE language" to SATA device...).
I am using smartd, and you are right: it triggers those messages
after being started:
[smartd start]
kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
kernel: ata2.00: tag 0 cmd 0xb0 Emask 0x2 stat 0x50 err 0x0 (HSM violation)
kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
kernel: ata2: soft resetting port
kernel: ata2.00: configured for UDMA/133
kernel: ata2: EH complete
[...]
kernel: ata3: no sense translation for status: 0x50
kernel: ata3: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
kernel: ata3: status=0x50 { DriveReady SeekComplete }
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
spamtraps: madduck.bogus@madduck.net
"it is only the modern that ever becomes old-fashioned."
-- oscar wilde
[-- Attachment #2: Digital signature (GPG/PGP) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-10 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 15:12 Tomasz Chmielewski
2006-11-10 15:57 ` martin f krafft [this message]
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=20061110155748.GA6081@piper.madduck.net \
--to=madduck@madduck.net \
--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
all inboxes | Powered by JetHome®