From: Dave Jones <davej@suse.de>
To: David Burrows <snadge@ugh.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: baffling linux bug / hardware problem
Date: Thu, 21 Feb 2002 16:02:28 +0100 [thread overview]
Message-ID: <20020221160228.E5583@suse.de> (raw)
In-Reply-To: <20020222013558.X11925-100000@starbug.ugh.net.au>
In-Reply-To: <20020222013558.X11925-100000@starbug.ugh.net.au>; from snadge@ugh.net.au on Fri, Feb 22, 2002 at 01:53:10AM +1100
On Fri, Feb 22, 2002 at 01:53:10AM +1100, David Burrows wrote:
> I have a problem where my computer locks up during "Calibrating Delay
> Loop..". I have been using Linux on this same hardware for many years,
> and it only started doing this 2 days ago. It does not seem to matter
> what kernel version (2.0, 2.2, 2.4.17) I use or what medium I boot from.
I had an old Winchip box that did this. Turned out to be a bad SIMM.
Try running memtest86 for a while.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-02-21 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 14:53 baffling linux bug / hardware problem David Burrows
2002-02-21 15:02 ` Dave Jones [this message]
2002-02-22 1:03 ` Dodgey Linus BogoMIPS code ;) (was Re: baffling linux bug) David Burrows
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=20020221160228.E5583@suse.de \
--to=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=snadge@ugh.net.au \
/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