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
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Feb 28 2002 - 21:00:13 EST