From: David Greaves <david@dgreaves.com>
To: Bruce Allen <ballen@gravity.phys.uwm.edu>
Cc: Jeff Garzik <jeff@garzik.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jan Dvorak <fermentol@gmail.com>,
Klaus Fuerstberger <kfuerstberger@arcor.de>,
Mark Lord <liml@rtr.ca>, Douglas Gilbert <dougg@torque.net>,
Tejun Heo <htejun@gmail.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Smartmontools Mailing List
<smartmontools-support@lists.sourceforge.net>,
Bruce Allen <bruce.allen@aei.mpg.de>
Subject: Re: SMART problems in 2.6.22
Date: Mon, 09 Jul 2007 19:00:40 +0100 [thread overview]
Message-ID: <469277C8.3040107@dgreaves.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0707091236530.7386@trinity.phys.uwm.edu>
Bruce Allen wrote:
> Hi David,
>
>>> http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg164863.html
>
>> This is mine and although it's a 'real' problem, it is something
>> that's easy to hack around by having the suspend script turn on smart
>> after it is resumed. (Of course I can't use resume until a skge wol
>> bug is fixed so I won't see/test this unless asked too.)
>>
>> The smart init scripts run '-s on' when the system boots anyway for my
>> system - this problem only occurs for me during suspend/resume. Maybe
>> smartd should detect that as Alan says.
>
> OK, that should be easy to do. So let's forget about the 'SMART
> disabled' issue. This is easy to fix in multiple ways and is not a LKML
> issue.
Sure.
> David: can you reproduce the more serious problem
> http://article.gmane.org/gmane.linux.utilities.smartmontools/4712
> reported by Jan Dvorak?
Sorry, I haven't seen that problem.
David
next prev parent reply other threads:[~2007-07-09 18:00 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
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 [this message]
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=469277C8.3040107@dgreaves.com \
--to=david@dgreaves.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ballen@gravity.phys.uwm.edu \
--cc=bruce.allen@aei.mpg.de \
--cc=dougg@torque.net \
--cc=fermentol@gmail.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--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