From: David Burrows <snadge@ugh.net.au>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dodgey Linus BogoMIPS code ;) (was Re: baffling linux bug)
Date: Fri, 22 Feb 2002 12:51:00 +1100 (EST) [thread overview]
Message-ID: <20020222124629.F15623-100000@starbug.ugh.net.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0202212038150.16271-100000@coffee.psychology.mcmaster.ca>
On Thu, 21 Feb 2002, Mark Hahn wrote:
> > > > 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
> > > sorry if you've already mentioned this, but do you have
> > > CONFIG_X86_UP_*APIC selected (something like "use local apic
> > > for uniprocessors")? if so, it could explain why you
> > > might be failing to receive timer irq's.
> >
> > I've tried with 2.0 kernels, 2.2 kernels and 2.4 kernels. Some of them I
> > can actually get to oops, but most of the time just a hard lock. I
> > believe I have that option disabled, I can't verify that at the moment
> > because I can't even run Linux.
>
> and you said that you have in the past run linux on this machine?
> and that you haven't made any bios changes/upgrades/etc?
> and that your pre-hang (pre-calibrating-delay-loop) messages
> are completely uninformative? also, that you are not making the
> TSC-ful-cpu mistake? actually the latter would be my guess...
Yes, I have been running various versions of Linux without problem on this
same machine for a number of years. I had not changed any hardware or
software between when it was working and when it suddenly started failing.
It is for this reason alone I posted on linux-kernel to get some help.
> > Then why does FreeBSD still work?
>
> I was answering your hypothetical question. freeBSD works because
> it doesn't share any code with linux, of course, same with windows.
I would assume that FreeBSD and Windows would still use the timer for some
reason or another. Therefore whatever sudden quirk that appeared in my
hardware has revealed a bug in Linux..
> > There are folks who would claim that
> > FreeBSD is superior to Linux.... ;)
>
> yeah, and Bhuddism is better than Christianity. such claims tell
> you exactly one thing: the utterer is a twit.
Well I personally don't believe one way or another. Its apples and
oranges as far as I'm concerned, however in this case one could say that
FreeBSD is better because it actually works. ;)
Cheers,
David.
next parent reply other threads:[~2002-02-22 1:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0202212038150.16271-100000@coffee.psychology.mcmaster.ca>
2002-02-22 1:51 ` David Burrows [this message]
2002-02-22 2:48 ` Mike Fedyk
2002-02-22 8:51 ` Zwane Mwaikambo
[not found] <20020222011209.GE20060@matchmail.com>
2002-02-22 1:29 ` David Burrows
2002-02-25 9:43 ` Helge Hafting
2002-02-25 11:03 ` 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=20020222124629.F15623-100000@starbug.ugh.net.au \
--to=snadge@ugh.net.au \
--cc=hahn@physics.mcmaster.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
all inboxes | Powered by JetHome®