From: Jan Niehusmann <jan@gondor.com>
To: Bart Samwel <bart@samwel.tk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Laptop mode causing writes to wrong sectors?
Date: Thu, 17 Nov 2005 11:33:53 +0100 [thread overview]
Message-ID: <20051117103352.GA4832@knautsch.gondor.com> (raw)
In-Reply-To: <437C4C8B.4030502@samwel.tk>
[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]
On Thu, Nov 17, 2005 at 10:25:31AM +0100, Bart Samwel wrote:
> Youch. I assumed this was all the same fs! It is the same HD though?
Yes, same HD, same notebook, no hardware changes.
> >But this should definitely have been detected by an fsck, right?
>
> Yes. And you've had this problem before, even. Googling for "e2fsck
> block bitmap differences" shows me this as the third entry. :)
>
> http://lkml.org/lkml/2003/8/3/166
>
> If you didn't get those messages, then this is not the problem, apparently.
Ok - this was on a different computer, so it's not really related, but
the important point is that fsck didn't report any errors so the
write into the middle of another file was not caused by a bad
filesystem.
> There is a known problem with laptop mode where, often during
> spindown/spinup, the kernel emits DMA timeout errors.
>
> http://lkml.org/lkml/2005/8/21/48
>
> According to Andrea Gelmini (the original reporter of this problem) this
> can lead to system freezes on some kernels, and corruption on others.
> Are you seeing these errors somewhere in your logs?
No ide errors at all in the kernel logs, which cover more than one
month.
> What's your hardware? A Thinkpad perhaps?
ASUS M2400N with a SAMSUNG MP0804H 80GB hard drive (this is not
the original hard drive - the notbook was delivered with a 60GB
drive). Centrino chipset, 1.6GHz Pentium M. Hard drive running in udma5
mode. 512MB RAM, Intel Pro Wireless 2100 replaced with an Intel Pro
Wireless 2200 wireless lan card, and a CardMan 4000 card reader in the
pccard slot - not that I think these have any influence on the hard drive,
but this is the complete hardware description.
Jan
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 307 bytes --]
next prev parent reply other threads:[~2005-11-17 10:33 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 [this message]
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
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=20051117103352.GA4832@knautsch.gondor.com \
--to=jan@gondor.com \
--cc=bart@samwel.tk \
--cc=linux-kernel@vger.kernel.org \
/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