From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel crash debugging
Date: Fri, 11 Nov 2005 14:14:18 -0600 [thread overview]
Message-ID: <4374FB9A.4020400@shaw.ca> (raw)
In-Reply-To: <56Z7S-85a-29@gated-at.bofh.it>
Lee wrote:
> Hello,
>
> I am running kernel version '2.6.13-gentoo-r3'
>
> My hardware is as follows:
> - motherboard: Tyan Tiger 230T
> - processors: 2 Pentium II 1.13Ghz
> - memory: 1.5GB
>
> I have been having intermittent lockups for a while now.
>
> At first, I thought it had something to do with vmware, but this is no occuring with a non-tainted kernel.
First thing I would try with those kind of faults is Memtest86, you
could have some bad RAM or bad memory timing settings..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2005-11-11 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56Z7S-85a-29@gated-at.bofh.it>
2005-11-11 20:14 ` Robert Hancock [this message]
2005-11-11 20:23 ` kernel crash debugging Lee
2005-11-09 14:20 Lee
2005-11-09 14:48 ` Lee
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=4374FB9A.4020400@shaw.ca \
--to=hancockr@shaw.ca \
--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