>From a bit of googling and Nick's suggestion (which helped with some extra google terms, I have found that the issue is the following :
C1 Halt Disconnect problem on nForce2 systems Description: A hang is caused when the CPU generates a very fast CONNECT/HALT cycle sequence. Workaround: Set the SYSTEM_IDLE_TIMEOUT to 80 ns. This allows the state-machine and timer to return to a proper state within 80 ns of the CONNECT and probe appearing together. Since the CPU will not issue another HALT within 80 ns of the initial HALT, the failure condition is avoided. I found this here (already posted this once) http://forums.gentoo.org/viewtopic.php?t=169004 Quoting Carl Cerecke <[EMAIL PROTECTED]>: > Nick Rout wrote: > > I read somewhere that on your nforce chipset board you should disable > > either apic or acpi. > > > On Mon, 24 May 2004 10:27:57 +1200 (NZST) > > [EMAIL PROTECTED] wrote: > > > > > >>On the other hand, I'm still getting plenty of lockups since I > installed Gentoo. > >>.. It is definitely improving though as I work my way through various > > >>kernel/driver/framebuffer issues. I'm getting there slowly. > > By and large, regular lockups (i.e. kernel panic/oops, not just X > getting its knickers in a twist) only happens on: > 1. faulty hardware > 2. incorrect BIOS settings > 3. new/exotic hardware > > I once installed Linux on a machine that had been running Windows 95 > (This was some time ago, maybe about Linux 1.2). I was getting a kernel > > oops a couple of times a day. It turned out to be overly aggressive > memory timings in the BIOS. Nobody had noticed on Windows 95 - crashes > were "normal". > > Cheers, > Carl. >
