From: Bart Samwel <bart@samwel.tk>
To: Bradley Chapman <kakadu@gmail.com>
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 22:22:00 +0100 [thread overview]
Message-ID: <437CF478.7010406@samwel.tk> (raw)
In-Reply-To: <e294b46e0511170822w79e5478asf49183c8447c7c77@mail.gmail.com>
Bradley Chapman wrote:
> 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.
This could be the problem I was talking about. Was this happening during
spindown or not?
> 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...*
I guess so. They all oops on reading the same address (0x05c2a5bb),
there's something corrupted in the slab cache, cause unknown. Very
possibly fglrx.
> Most of the time though, I don't see anything.
...while still experiencing corruption?
>> 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.
Hmmmm. This means that you could still be experiencing the same thing
that Andrea Gelmini was reporting. Could you try the things he said made
it worse, and check if things go wrong? You are, of course, allowed to
decline because of the risk involved. :-) The things are:
Big activity:
* iozone -A
* unrar big file
* In order to make it happen faster:
cd /proc/sys/vm
echo 100 > dirty_background_ratio
echo 1000000 > dirty_expire_centisecs
echo 100 > dirty_ratio
echo 1000000 > dirty_writeback_centisecs
--Bart
next prev parent reply other threads:[~2005-11-17 21:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 13:22 Laptop mode causing writes to wrong sectors? 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 [this message]
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=437CF478.7010406@samwel.tk \
--to=bart@samwel.tk \
--cc=jan@gondor.com \
--cc=kakadu@gmail.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