mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Burrows <snadge@ugh.net.au>
To: Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Dodgey Linus BogoMIPS code ;) (was Re: baffling linux bug)
Date: Fri, 22 Feb 2002 12:03:03 +1100 (EST)	[thread overview]
Message-ID: <20020222115546.B15623-100000@starbug.ugh.net.au> (raw)
In-Reply-To: <20020221160228.E5583@suse.de>

On Thu, 21 Feb 2002, Dave Jones wrote:
> 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.

I have ran memtest86 all the way through, and shuffled the memory around
(moved them to different slots) and it still crashes in calibrating delay
loop.  FreeBSD and Windows still work.  If I knew how init/main.c worked,
what jiffies are and how they are updated (timer interrupt?), then I would
have some idea of what I'm doing when I step through the BogoMip
calculation code.

Is there some sort of (or can there be) a safety check which tests to see
if the timer is functioning correctly and displays an error message such
as "Timer interrupt is broken, system halted." if it is not.  I don't want
to give up on this hardware yet, ESPECIALLY considering that other
operating systems that I absolutely HATE still continue to work, and my
favourite one doesn't. :(

Thanks again for your time,

David.


  reply	other threads:[~2002-02-22  1:03 UTC|newest]

Thread overview: 9+ 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
2002-02-22  1:03   ` David Burrows [this message]
     [not found] <20020222011209.GE20060@matchmail.com>
2002-02-22  1:29 ` Dodgey Linus BogoMIPS code ;) (was Re: baffling linux bug) David Burrows
2002-02-25  9:43   ` Helge Hafting
2002-02-25 11:03     ` Zwane Mwaikambo
     [not found] <Pine.LNX.4.33.0202212038150.16271-100000@coffee.psychology.mcmaster.ca>
2002-02-22  1:51 ` David Burrows
2002-02-22  2:48   ` Mike Fedyk
2002-02-22  8:51   ` Zwane Mwaikambo

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=20020222115546.B15623-100000@starbug.ugh.net.au \
    --to=snadge@ugh.net.au \
    --cc=davej@suse.de \
    --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®