From: John Newman <cachehit@gmail.com>
To: Chris Wright <chrisw@osdl.org>
Cc: linux-kernel@vger.kernel.org, mhenderson@pointserve.com
Subject: Re: kernel crashes with 2.5/2.8
Date: Thu, 2 Dec 2004 19:03:06 -0600 [thread overview]
Message-ID: <abc3398204120217031640ba07@mail.gmail.com> (raw)
In-Reply-To: <20041201111617.M14339@build.pdx.osdl.net>
Ok, I got some time this evening to run memtest86. With the 2650
configured with 2 1GB sticks memtest86 started reprting errors almost
immediately. "Terrfic!" I thought, "this is my problem!" The address
seemed suspicious though: 0007ffedc80 (2047.8MB) is where all the
errors were reported. I decided to let it run all the way through but
it froze at 34% of the first test. Memtest86 also said it did not
support this chipset when I tried to dink with advanced options.
So, I replaced the ram with 4 512MB sticks I had laying around from a
different Dell machine. I booted memtest86 again and what do you
know.... errors @ 0007ffedc80, with completely different RAM. So
obviously these results are fishy.
Someone replied to me off-list and said the only way they could get
their Dell 2650 stable was by running 2.4.28.
--
john
On Wed, 1 Dec 2004 11:16:17 -0800, Chris Wright <chrisw@osdl.org> wrote:
> * John Newman (cachehit@gmail.com) wrote:
> > Nov 24 21:34:10 ptscorp-nis01 kernel: Unable to handle kernel paging
> > request at virtual address 01000004
>
> Possible bad memory. This could be 4 byte offset of NULL with one bit
> flipped. Have you run memtest86?
>
> Also, it'd be useful to keep tabs on the Oopsen. Are they totally
> random, same location, etc.
>
> thanks,
> -chris
>
--
John
prev parent reply other threads:[~2004-12-03 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 17:09 kernel crashes with 2.5/2.8 John Newman
[not found] ` <Pine.LNX.4.53.0412011815090.1909@yvahk01.tjqt.qr>
[not found] ` <abc33982041201093665e56767@mail.gmail.com>
2004-12-01 17:37 ` John Newman
2004-12-01 19:16 ` Chris Wright
2004-12-03 1:03 ` John Newman [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=abc3398204120217031640ba07@mail.gmail.com \
--to=cachehit@gmail.com \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhenderson@pointserve.com \
/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.