mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Niehusmann <jan@gondor.com>
To: Bart Samwel <bart@samwel.tk>
Cc: linux-kernel@vger.kernel.org, Zhu Yi <yi.zhu@intel.com>
Subject: Re: Laptop mode causing writes to wrong sectors?
Date: Sat, 19 Nov 2005 16:30:24 +0100	[thread overview]
Message-ID: <20051119153024.GB4725@knautsch.gondor.com> (raw)
In-Reply-To: <20051119140527.GA4725@knautsch.gondor.com>

On Sat, Nov 19, 2005 at 03:05:28PM +0100, Jan Niehusmann wrote:
> That's interesting. Both Bradley and me are using ipw2200, an in the
> madwifi thread, one person also mentions he is using this driver. I
> don't know if madwifi and ipw2200 use common or very similar code. But
> perhaps this problem really is caused by a combination of laptop
> mode / disk spinup and certain wireless drivers?

Perhaps this one is related?

http://bughost.org/bugzilla/show_bug.cgi?id=821

If the corruption caused by this bug could lead to the filesystem
corruption I observed, it would match my observations quite well:

- Corruption started shortly after I upgraded to a kernel with 
  ipw2200 driver version 1.0.8
- Happens when using wireless
- File system corruption happens with laptop mode (because then the
  probability that dirty pages which will be written to disk later can
  be overwritten before the write actually happens is much higher)
- Problem is difficult to reproduce, as it's not deterministic which
  type of data structure gets overwritten, and it can happen only once
  per reboot (or driver reload)

Question is, could this bug cause filesystem corruption without any Oops
visible in the kernel log? Cc: to Zhu Yi at Intel - can you answer this
question?

Jan


  reply	other threads:[~2005-11-19 15:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 18:16 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
2005-11-19 14:05         ` Jan Niehusmann
2005-11-19 15:30           ` Jan Niehusmann [this message]
2005-11-19 23:29             ` Bart Samwel
2005-11-19 23:45               ` Jan Niehusmann
2005-11-21  2:09       ` Bill Davidsen
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=20051119153024.GB4725@knautsch.gondor.com \
    --to=jan@gondor.com \
    --cc=bart@samwel.tk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yi.zhu@intel.com \
    /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

all inboxes | Powered by JetHome®