public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Valdis.Kletnieks@vt.edu
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
	linux-kernel@vger.kernel.org, madduck@madduck.net
Subject: Re: scary messages: HSM violation during boot of 2.6.18/amd64
Date: Sat, 11 Nov 2006 13:52:07 +0900	[thread overview]
Message-ID: <455556F7.4000802@gmail.com> (raw)
In-Reply-To: <200611102310.kAANAgOf019164@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu wrote:
> On Fri, 10 Nov 2006 23:54:00 +0100, Tomasz Chmielewski said:
> 
>> You use old smartmontools :)
>>
>> -o on / -S on is not supported for sata, unless you use a CVS version of 
>> smartmontools.
> 
> OK, thanks - the Fedora RPM from several days ago is still 5.36 based,
> I just pulled the CVS version and it starts up much more nicely.  Only quirk:
> 
> Nov 10 18:04:32 turing-police smartd[18988]: Device: /dev/sda, opened 
> Nov 10 18:04:32 turing-police smartd[18988]: Device /dev/sda: SATA disks accessed via libata are supported by Linux kernel versions 2.6.15-rc1 and above. Try adding '-d ata' or '-d sat' to the smartd.conf config file line. 
> 
> Well, yeah. I'm on 2.6.19-rc5-mm1 and the config file *has* '-d ata' already. ;)
> I'd file a bug report against that, except it's time for me to leave the office
> and forage for some dinner. :)

For detailed info,

http://thread.gmane.org/gmane.linux.ide/13222/focus=13235

-- 
tejun

  reply	other threads:[~2006-11-11  4:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 15:12 scary messages: HSM violation during boot of 2.6.18/amd64 Tomasz Chmielewski
2006-11-10 15:57 ` 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 [this message]
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=455556F7.4000802@gmail.com \
    --to=htejun@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madduck@madduck.net \
    --cc=mangoo@wpkg.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