From: Bart Samwel <bart@samwel.tk>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Pavel Machek <pavel@ucw.cz>, Bill Davidsen <davidsen@tmr.com>,
linux-kernel@vger.kernel.org
Subject: Re: Laptop mode causing writes to wrong sectors?
Date: Sat, 19 Nov 2005 12:10:34 +0100 [thread overview]
Message-ID: <437F082A.6040301@samwel.tk> (raw)
In-Reply-To: <20051119092622.GA13622@midnight.suse.cz>
Vojtech Pavlik wrote:
> The issue might be that these people are using
>
> hdparm -S xxx
>
> or
>
> hdparm -y / -Y
>
> while a much better way to do
>
> hdparm -B 63
>
> The -S option should in theory be safe, but I remember some drives did
> behave unpredictably if this was used.
Well, some drives have a specific lower limit on the -S values that are
supported. That's the only compatibility problem I've ever encountered
with -S. (And you can find out if a drive has a lower limit by checking
hdparm -i.)
> -y/-Y is much tougher and some
> drives will not work reliably unless first woken up manually before
> issuing a read/write request.
In fact, -Y is problematic but -y usually isn't. -Y puts the drive to
sleep and requires that Linux reset the complete IDE controller before
using it again, while -y simply puts the drive in standby mode, leaving
it up to the drive to decide when it spins up. I've never heard of any
problems with -y.
> On the other hand, -B is pretty safe on drives that support it, and all
> IBM notebook drives do.
Not true, unfortunately. In fact, I had to change the default config of
laptop-mode-tools a while ago so that it wouldn't use -B, as it seemed
to be one of the *causes* of hangup/corruption problems. This was also
an issue on Thinkpads, and I think it was also noted in the ubuntu bug I
linked to earlier.
An additional problem is that the values for -B are not really
standardized, while the values for -S are.
--Bart
next prev parent reply other threads:[~2005-11-19 11:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 18:16 Laptop mode causing writes to wrong sectors? Jan Niehusmann
2005-11-16 20:06 ` Bart Samwel
2005-11-16 21:42 ` Jan Niehusmann
2005-11-17 9:25 ` Bart Samwel
2005-11-17 10:33 ` Jan Niehusmann
2005-11-17 11:36 ` Bart Samwel
2005-11-17 22:33 ` Pavel Machek
2005-11-18 18:45 ` Bill Davidsen
2005-11-18 23:20 ` Pavel Machek
2005-11-19 8:39 ` Bart Samwel
2005-11-19 9:26 ` Vojtech Pavlik
2005-11-19 11:10 ` Bart Samwel [this message]
2005-11-19 14:05 ` Jan Niehusmann
2005-11-19 15:30 ` Jan Niehusmann
2005-11-19 23:29 ` Bart Samwel
2005-11-19 23:45 ` Jan Niehusmann
2005-11-21 2:09 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2005-11-17 13:22 Bradley Chapman
2005-11-17 14:27 ` Bart Samwel
2005-11-17 15:41 ` Jan Niehusmann
2005-11-17 16:05 ` Bart Samwel
2005-11-17 16:22 ` Bradley Chapman
2005-11-17 21:22 ` Bart Samwel
2005-11-17 22:50 ` Bradley Chapman
2005-11-20 21:30 ` Pavel Machek
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=437F082A.6040301@samwel.tk \
--to=bart@samwel.tk \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=vojtech@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.