[clug] Debugging system lockups
rohan.mitchell at undefined.homelinux.net
Mon May 10 13:32:11 GMT 2004
This sounds exactly like the problem i'm having (I have an abit nf7-s,
which uses nforce2). I had noapic and apic=off in the append line for
lilo, but not nolapic. I'll give it a try over the next few days and let
PS. Cody, i had checked cpu and case temps, and it didnt seem to be
related. Under load the cpu would go to around 50, while it was usually
in the mid-40s when it crashed.
David Tulloh wrote:
> Rohan Mitchell wrote:
>> Hi all,
>> For the last few months, i've been having occasional (maybe once
>> every day or 2) system lockups on my main system, which runs debian
>> testing on kernel 2.6.3. Numlock wont respond, nor will ctrl-alt-f1
>> or magic sysrq key. No messages are left in /var/log/syslog or
>> /var/log/message. It seems to happen more frequently when playing
>> sound or video, but i'm not certain of this.
>> What would everyone suggest to debug this problem?
>> Thanks in advance,
> This shounds like a problem I encountered between the nforce 2
> motherboards and the 2.6 kernels. Basically there is something wrong
> at the io level, causing random lockups. I found the problem was
> worse when I played music but particularily video due to the increased
> io load.
> The fix is to add the kernel option nolapic to the kernel line, simply
> not selecting the option in the configuration stage doesn't seem to be
> Hope this helps,
More information about the linux