On Wed, 2006-09-20 at 16:11 +0000, carmen wrote:
if you find out how to debug a frozen kernel (ie,
doesnt even get a chance to print a backtrace) let us know. ive been tryin out ingo's
kernel every 6 month or so for the past couple of years on a few differet amd64 rigs using
the above techniques. so far it always blackscreens/reboots right after grub, freezes
during boot, or freezes anywhere from 3 to 20 minutes after booting regardless of load. i
dont want to say the above techniques are a total waste of time, as they do tend to change
when it freezes from eg, right after grub, to later on, etc. so theyre doing something..
same here with 2.6.17-rt8 and a dual opteron system. removing kernel/RT
debugging improves things, but not so much that the system will run for
long. its a bit sad.
2.6.18-rt2 is out now, it's worth a try.
I'd be interested to see if the problem can be reproduced with
the .config I posted. Neither I nor the 64studio guys nor any of their
users can reproduce these problems at all.
Lee