Dodgey Linus BogoMIPS code ;) (was Re: baffling linux bug)
Quoted 2 lines · Mike Fedyk
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. =)
Quoted 2 lines
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.
Quoted 8 lines · David Burrows
Quoted 2 lines · Mike Fedyk
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. =)
Quoted 7 lines
Quoted 2 lines
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
Quoted 4 lines · Helge Hafting
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.
One thing worth keeping in mind also is that Linux makes assumptions about the i8254 timer interval, try booting verbose in FreeBSD and try and see what you get.
Zwane
Re: Dodgey Linus BogoMIPS code ;) (solved!)
In reply to Helge HaftingThanks 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.
Quoted 31 lines · Helge Hafting
Quoted 8 lines · David Burrows
Quoted 2 lines · Mike Fedyk
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. =)
Quoted 7 lines
Quoted 2 lines
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