From: "Deon George" <kernel@wurley.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Eran Mann <emann@mrv.com>, linux-kernel@vger.kernel.org
Subject: Re: please help - kernel OOPS
Date: Fri, 18 Jul 2003 10:38:38 +1000 [thread overview]
Message-ID: <20030718003838.M79515@wurley.net> (raw)
In-Reply-To: <1058395864.7678.5.camel@dhcp22.swansea.linux.org.uk>
Alan/Eran,
Thanks for your TIPS - I'm thinking that it is the memory being the problem.
I download and run memtest86 v3 and I have many errors (25-35) when it run test #3
and test #4 (I'm just memtest86 without any configuration).
Given that this is the 2nd (different) type of memory Ive tried - I'll get my
supplier to give me something else and hopefully that'll fix the Ooopss..
Thanks for your tips!
...deon
On 16 Jul 2003 23:51:04 +0100, Alan Cox wrote
> On Mer, 2003-07-16 at 23:34, Deon George wrote:
> > G'day Alan,
> >
> > I was wondering if it was a memory issue.
>
> memtest86 should help find this out, as should going into the BIOS and
> setting "safe settings" then seeing if its stable.
>
> > Who makes the the memory that you are using? (I guess you have problems with
the
> > V8000 too right?)
>
> I'm using micron RAM I think.
>
> > > Are you within power budget for your system if its a tiny little PSU
> > > brick ?
> >
> > Are you thinking that the power supply could be the cause of the problem?
>
> I don't know but you mention it occurs when the disks are very active -
> that could be DMA/RAM loading or power
...deon
Wurley Solutions
---
_--_|\ | Deon George
/ \ |
\_.--.*/ |
v | This email coming to you from the 'burbs of Melbourne,
Australia.
prev parent reply other threads:[~2003-07-18 0:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 12:08 Deon George
2003-07-16 15:18 ` Alan Cox
[not found] ` <20030716223431.M85416@wurley.net>
[not found] ` <1058395864.7678.5.camel@dhcp22.swansea.linux.org.uk>
2003-07-18 0:38 ` Deon George [this message]
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=20030718003838.M79515@wurley.net \
--to=kernel@wurley.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=emann@mrv.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®