public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Bart Samwel <bart@samwel.tk>
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 10:26:22 +0100	[thread overview]
Message-ID: <20051119092622.GA13622@midnight.suse.cz> (raw)
In-Reply-To: <437EE4B3.2090408@samwel.tk>

On Sat, Nov 19, 2005 at 09:39:15AM +0100, Bart Samwel wrote:
> Pavel Machek wrote:
> >>My laptop also has a spindown (five min from memory) and I have yet to 
> >>have a problem with it. Don't know if any of that is "spindowns without 
> >>laptopmode" in a useful sense.
> >
> >Unless you can also reproduce the failure... no, probably does not help
> >much.
> 
> Okay, let's recap.
> 
> * There are a lot of people who are not having problems. The people who 
> *are* having problems can usually reproduce them. My interpretation: the 
> problem is triggered by some hardware and/or kernel config settings.
> 
> * A significant proportion of the people who *do* have trouble see 
> messages about DMA timeouts. The problems do also occur on other 
> hardware, but seem to be most pronounced on Thinkpad T40s. On those 
> machines, the DMA timeout problems are triggered *especially* when the 
> madwifi drivers are loaded (see 
> http://bugzilla.ubuntu.com/show_bug.cgi?id=6108).
> 
> Perhaps I should start collection kernel configs and hardware specs, see 
> if there are any unexpected commonalities. The influence of the madwifi 
> drivers suggest that we could be be looking for anything really. What do 
> you think?
 
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. -y/-Y is much tougher and some
drives will not work reliably unless first woken up manually before
issuing a read/write request.

On the other hand, -B is pretty safe on drives that support it, and all
IBM notebook drives do.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2005-11-19  9:26 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 [this message]
2005-11-19 11:10           ` Bart Samwel
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=20051119092622.GA13622@midnight.suse.cz \
    --to=vojtech@suse.cz \
    --cc=bart@samwel.tk \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox