[lkml]   [2003]   [Aug]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: nforce2 lockups
Thank you!!!

I had done this before but without the nolapic option. That appears to have been the solution. Ran a whole day without one lockup where before 10 minutes was rarely achieved.

I don't know if you knew I had a $20 reward for the fix, but it looks like you got it.

Going to run a few more days just to be sure, but send me your address and I will send you the $20 after stressing my system a bit more.

It looks like the nolapic kernel parameter was just recently introduced. I tried it in both the 2.4.22-rc2 kernel and the 2.6.0-test3 kernel with success in both.

Would still like apic to be completely fixed in the nforce2 chipsets, but I am just happy to have a working system again.

Thanks again,

----- Original Message -----
From: Patrick Dreker <>
Date: Thursday, August 21, 2003 8:05 pm
Subject: Re: nforce2 lockups

> Hash: SHA1
> Am Thursday 21 August 2003 03:39 schrieb
> zum
> Thema Re: nforce2 lockups:
> > and it did cure my spurious interrupt problem, but
> unfortunately, my
> > lockups have returned.
> I managed to stabilize my Board, but I don't think the trick was
> obvious:
> Disable alle APIC related kernel Options (Local APIC and IO-APIC),
> disable
> APIC Mode in the BIOS. Check on reboot if it still talks about the
> APIC in
> the boot messages (How? IIRC mine did, which was why I did not
> think that
> disabling the APIC helped... Actually somehow it still was
> activated. Could
> ACPI be part of this?). If it does try noapic and/or nolapic boot
> options.
> If you completely shut off the APIC it runs stable, but 1 of the 3
> Controllers is not assigned an interrupt. All this with ACPI
> enabled (ACPI
> patch 20030730 and kernel 2.6.0-test3).
> - --
> Patrick Dreker
> GPG KeyID : 0xFCC2F7A7 (Patrick Dreker)
> Fingerprint: 7A21 FC7F 707A C498 F370 1008 7044 66DA FCC2 F7A7
> Key available from keyservers or
> Version: GnuPG v1.2.2 (GNU/Linux)
> iD8DBQE/RKdhcERm2vzC96cRAtjAAJ4y5oOm7uhtPqWtaS/S+mnWTr9C5gCdF3hK
> 2JQZ86psKDmWO74wxrINSRE=
> =YbYq

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:48    [W:0.022 / U:2.868 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site