From: Paulo Marques <pmarques@grupopie.com>
To: Michael <michael.sallaway@gmail.com>
Cc: ray-gmail@madrabbit.org, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Oops when doing disk heavy disk I/O
Date: Wed, 25 Oct 2006 16:24:38 +0100 [thread overview]
Message-ID: <453F81B6.3080205@grupopie.com> (raw)
In-Reply-To: <453f585d.299e45f8.4666.371b@mx.google.com>
Michael wrote:
>> From: Ray Lee [mailto:madrabbit@gmail.com]
>> Try swapping out the RAM (or getting it down to 1Gig). Try a really
>> old kernel, such as debian's 2.6.8 package.
>
> [...]
> Although, having said that, I'm curious... It is working because there's
> only 1 gig of RAM in there, or because it's only a single stick (ie. not
> dual-channel)? It works fine with both sticks, individually, just not both
> together... I wonder what the cause of it actually is...
Another thing that I would try is to tweak the /proc/sys/vm/dirty_ratio
and /proc/sys/vm/dirty_background_ratio settings.
pdflush appears in your trace and with twice the RAM there is twice the
dirty data to write out. Maybe choosing half the ratio in both settings
with 2Gb of RAM would produce the same amount of dirty data as using
just 1Gb of RAM with the original settings.
This is still a bug, though. This test would just give more debug
information.
--
Paulo "grasping at straws" Marques - www.grupopie.com
"The face of a child can say it all, especially the
mouth part of the face."
next prev parent reply other threads:[~2006-10-25 15:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 15:56 PROBLEM: Oops when doing disk heavy disk I/O Michael Sallaway
2006-10-24 17:26 ` Sergio Monteiro Basto
2006-10-25 0:21 ` Michael
2006-10-25 0:41 ` Sergio Monteiro Basto
2006-10-25 1:25 ` Michael
2006-10-25 4:12 ` Ray Lee
2006-10-25 12:28 ` Michael
2006-10-25 15:08 ` Ray Lee
2006-10-25 15:24 ` Paulo Marques [this message]
2006-10-24 17:43 ` Badari Pulavarty
2006-10-25 0:09 ` Michael
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=453F81B6.3080205@grupopie.com \
--to=pmarques@grupopie.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.sallaway@gmail.com \
--cc=ray-gmail@madrabbit.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