mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bradley Chapman <kakadu@gmail.com>
To: Bart Samwel <bart@samwel.tk>
Cc: linux-kernel@vger.kernel.org, Jan Niehusmann <jan@gondor.com>
Subject: Re: Laptop mode causing writes to wrong sectors?
Date: Thu, 17 Nov 2005 16:22:22 +0000	[thread overview]
Message-ID: <e294b46e0511170822w79e5478asf49183c8447c7c77@mail.gmail.com> (raw)
In-Reply-To: <437C9334.3020606@samwel.tk>

Mr. Samwel,

On 11/17/05, Bart Samwel <bart@samwel.tk> wrote:
>
> OK, that's the second report then. I'm beginning to worry. :/
>
> Are you seeing any DMA timeout messages in your kernel log?

Once, when my /var partition got trashed - about thirty or forty loud
and scary messages from the IDE core saying that various disk accesses
(i.e. normal read/writes) were failing. I do believe DMA was
mentioned.

Another time (i.e. just now), I got five Oopses in a row, most of them
in kmem_cache_alloc() but with one in generic_aio_file_read(). 
Unfortunately I am using fglrx right now so they are probably quite
meaningless...*

Most of the time though, I don't see anything.

Fortunately the number of errors encouraged the kernel to remount R/O,
so after a quick jump to single user mode and two e2fsck -f
invocations, it was healed.

>
> Also, both reports are on ext3, which might point to an ext3 problem
> with long commit intervals.
>
> Bradley, Jan, since when have these problems been happening? Kernel
> version-wise, I mean?

They started with 2.6.13. I can't remember ever expereincing random
partition trashing or random file corruption in 2.6.12. I tried
2.6.14.1 - that kernel did Bad Things as well.

So far though, as long as I stay on juice, 2.6.13 seems to behave.

>
> --Bart
>

Brad

* - http://216.55.161.203/theonekea/misc/oopsen.txt
--
SCREW THE ADS! http://adblock.mozdev.org/

  parent reply	other threads:[~2005-11-17 16:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2005-11-17 21:22     ` Bart Samwel
2005-11-17 22:50       ` Bradley Chapman
2005-11-20 21:30 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
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
2005-11-19 23:29             ` Bart Samwel
2005-11-19 23:45               ` Jan Niehusmann
2005-11-21  2:09       ` Bill Davidsen

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=e294b46e0511170822w79e5478asf49183c8447c7c77@mail.gmail.com \
    --to=kakadu@gmail.com \
    --cc=bart@samwel.tk \
    --cc=jan@gondor.com \
    --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

all inboxes | Powered by JetHome®