All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael" <michael.sallaway@gmail.com>
To: <ray-gmail@madrabbit.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: PROBLEM: Oops when doing disk heavy disk I/O
Date: Wed, 25 Oct 2006 22:28:02 +1000	[thread overview]
Message-ID: <453f585d.299e45f8.4666.371b@mx.google.com> (raw)
In-Reply-To: <2c0942db0610242112r738fe4ccg8702ef5175a7927c@mail.gmail.com>

 

> -----Original Message-----
> From: Ray Lee [mailto:madrabbit@gmail.com] 
> Sent: Wednesday, 25 October 2006 2:13 PM
> 
> Try swapping out the RAM (or getting it down to 1Gig). Try a really
> old kernel, such as debian's 2.6.8 package.
> 
> Ray

Well, what do you know -- that seems to have fixed it! I took out one stick
of RAM (so it's down to 1 gig) and it seems to work fine, now, without any
boot parameters or anything. (mind you, murphy's law will dictate that it'll
crash about 30 seconds after I send this...)

I'm amazed at that -- but I'm not going to look a gift horse in the mouth,
this has been frustrating me for far too long. :-)

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...

Thanks heaps for the suggestion!

Cheers,
Michael




  reply	other threads:[~2006-10-25 12:28 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 [this message]
2006-10-25 15:08             ` Ray Lee
2006-10-25 15:24             ` Paulo Marques
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=453f585d.299e45f8.4666.371b@mx.google.com \
    --to=michael.sallaway@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.