[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.63.0707091236530.7386@trinity.phys.uwm.edu>
Date: Mon, 9 Jul 2007 12:56:01 -0500 (CDT)
From: Bruce Allen <ballen@...vity.phys.uwm.edu>
To: Jeff Garzik <jeff@...zik.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jan Dvorak <fermentol@...il.com>,
Klaus Fuerstberger <kfuerstberger@...or.de>,
David Greaves <david@...eaves.com>
cc: Mark Lord <liml@....ca>, Douglas Gilbert <dougg@...que.net>,
Tejun Heo <htejun@...il.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Smartmontools Mailing List
<smartmontools-support@...ts.sourceforge.net>,
Bruce Allen <bruce.allen@....mpg.de>
Subject: Re: SMART problems in 2.6.22
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.
David: can you reproduce the more serious problem
http://article.gmane.org/gmane.linux.utilities.smartmontools/4712 reported
by Jan Dvorak?
Jeff: this is the problem that really has me concerned.
Jan: what happens if you replace '-d ata' with '-d sat'? This option
should be available in the 5.37 release of smartmontools that you are
using unless the Suse package maintainer is playing games with the version
numbers.
Unfortunately I don't think this will fix the problem, as the bug report
by Klaus Fuerstberger
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428975 is using '-d sat'.
Jeff: the fact that both links given above are reporting the same bug in
two different settings, and the fact that the bug goes away when reverting
2.6.22 to 2.6.21 still has me concerned.
Cheers,
Bruce
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists