From: David Burrows <snadge@ugh.net.au>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dodgey Linus BogoMIPS code ;) (was Re: baffling linux bug)
Date: Fri, 22 Feb 2002 12:29:20 +1100 (EST) [thread overview]
Message-ID: <20020222122108.I15623-100000@starbug.ugh.net.au> (raw)
In-Reply-To: <20020222011209.GE20060@matchmail.com>
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,
perhaps even a kernel patch to include such a check before initialising
the timers. Is there a possibility of working around such problem? I
would rather destroy this motherboard than sacrifice it to running
inferior operating systems for the remainder of its life. =)
Regards,
Dave.
next parent reply other threads:[~2002-02-22 1:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020222011209.GE20060@matchmail.com>
2002-02-22 1:29 ` David Burrows [this message]
2002-02-25 9:43 ` Helge Hafting
2002-02-25 11:03 ` Zwane Mwaikambo
2002-02-25 12:33 ` Dodgey Linus BogoMIPS code ;) (solved!) David Burrows
[not found] <Pine.LNX.4.33.0202212038150.16271-100000@coffee.psychology.mcmaster.ca>
2002-02-22 1:51 ` Dodgey Linus BogoMIPS code ;) (was Re: baffling linux bug) David Burrows
2002-02-22 2:48 ` Mike Fedyk
2002-02-22 8:51 ` Zwane Mwaikambo
2002-02-21 15:02 baffling linux bug / hardware problem Dave Jones
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=20020222122108.I15623-100000@starbug.ugh.net.au \
--to=snadge@ugh.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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 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®