From: Jeff Garzik <jeff@garzik.org>
To: Bruce Allen <ballen@gravity.phys.uwm.edu>
Cc: Mark Lord <liml@rtr.ca>, David Greaves <david@dgreaves.com>,
Douglas Gilbert <dougg@torque.net>, Tejun Heo <htejun@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Kai Makisara <Kai.Makisara@kolumbus.fi>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jan Dvorak <fermentol@gmail.com>,
Smartmontools Mailing List
<smartmontools-support@lists.sourceforge.net>,
Klaus Fuerstberger <kfuerstberger@arcor.de>,
Bruce Allen <bruce.allen@aei.mpg.de>
Subject: Re: SMART problems in 2.6.22
Date: Sun, 08 Jul 2007 22:09:40 -0400 [thread overview]
Message-ID: <469198E4.6000200@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0707082003360.23123@trinity.phys.uwm.edu>
On the base point, libata has never enabled SMART on its own. That's
always up to the BIOS, etc.
It's possible that the recent addition of ACPI support will cause disks
to be in different modes than previously expected. ACPI supplies ATA
taskfiles to be pushed to the disk, and who knows what's in there...
Jeff
next prev parent reply other threads:[~2007-07-09 2:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 0:32 SMART problems in 2.6.22 Bruce Allen
2007-07-09 1:14 ` Bruce Allen
2007-07-09 2:09 ` Jeff Garzik [this message]
2007-07-09 17:35 ` Bruce Allen
2007-07-09 17:52 ` Jeff Garzik
2007-07-09 18:02 ` Bruce Allen
2007-07-09 23:35 ` [smartmontools-support] " Adam Spiers
2007-07-10 18:22 ` Mark Lord
2007-07-09 11:55 ` David Greaves
2007-07-09 17:56 ` Bruce Allen
2007-07-09 18:00 ` David Greaves
2007-07-09 18:43 ` Jeff Garzik
2007-07-09 21:11 ` Kai Makisara
2007-07-10 4:24 ` Douglas Gilbert
2007-07-11 1:31 ` Bruce Allen
2007-07-16 10:48 ` Kai Makisara
2007-07-16 11:22 ` Tejun Heo
2007-07-16 11:58 ` Kai Makisara
2007-07-16 13:12 ` Klaus Fuerstberger
2007-07-16 21:27 ` Bruce Allen
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=469198E4.6000200@garzik.org \
--to=jeff@garzik.org \
--cc=Kai.Makisara@kolumbus.fi \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ballen@gravity.phys.uwm.edu \
--cc=bruce.allen@aei.mpg.de \
--cc=david@dgreaves.com \
--cc=dougg@torque.net \
--cc=fermentol@gmail.com \
--cc=htejun@gmail.com \
--cc=kfuerstberger@arcor.de \
--cc=liml@rtr.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=smartmontools-support@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox