mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Burrows <snadge@ugh.net.au>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dodgey Linus BogoMIPS code ;) (solved!)
Date: Mon, 25 Feb 2002 23:33:41 +1100 (EST)	[thread overview]
Message-ID: <20020225232717.N46728-100000@starbug.ugh.net.au> (raw)
In-Reply-To: <3C7A073D.90A33D03@aitel.hist.no>

Thanks all who responded!  It turned out I had a faulty power supply.  It
was causing peculiar failures and then finally a total failure (black
screen).  I have since changed to a new case and everything is fine.

The moral to the story is that computer hardware is not invulnerable.  Try
not to point the finger too soon at software even if other software
"seems" to work properly.

Happy hacking, =)

David.

On Mon, 25 Feb 2002, Helge Hafting wrote:
> David Burrows wrote:
> >
> > On Thu, 21 Feb 2002, Mike Fedyk wrote:
> > > I didn't see one thing mentioning Linus in there... ;)  I could sue if you
> > > were selling something. ;)
> >
> > Kind of.  Except Linus wrote the particular section of code in question.
> > =)
> >
> > > Anyway, jiffies are same as HZ and on i386 100 jiffies/sec, and one timer
> > > interrupt per jiffie.
> >
> > Or perhaps not in the case of my hardware functioning properly one day,
> > and never to boot linux (but fine with everything else) again..
> >
> > I need a sure fire way of testing whether the timer interrupt works,
>
> I once used a printk in the keyboard irq handler to check a
> nonstandard keyboard.  You may put a printk() in the timer interrupt
> handler.
> That should show that the irq handler works.  Of course you don't want
> to
> run such a log-filler for long... :-)
>
> Maybe you can get the machine to boot by skipping the bogomips
> calculation completely - by hardcoding the value your machine used to
> come up with?
> Not for production use - just to get a debugging kernel going.
>
> Helge Hafting
>


      parent reply	other threads:[~2002-02-25 12:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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
2002-02-25 12:33     ` David Burrows [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=20020225232717.N46728-100000@starbug.ugh.net.au \
    --to=snadge@ugh.net.au \
    --cc=helgehaf@aitel.hist.no \
    --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®