Date: Fri, 15 Aug 2003 17:15:21 +0200
From: Clock <clock@twibright.com>
To: kenton.groombridge@us.army.mil
Cc: linux-kernel@vger.kernel.org
Subject: Re: nforce2 lockups
Message-ID: <20030815171521.A683@beton.cybernet.src>
References: <df962fdf9006.df9006df962f@us.army.mil>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <df962fdf9006.df9006df962f@us.army.mil>; from kenton.groombridge@us.army.mil on Fri, Aug 15, 2003 at 09:12:17PM +0900
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1351
Lines: 36

On Fri, Aug 15, 2003 at 09:12:17PM +0900, kenton.groombridge@us.army.mil wrote:
> Hi,
> 
> I found your post looking for a solution to my lockups.  I bet if you do a dmesg, you will find that your nforce2 chipset revision is 162.

Yeah! Look:

NFORCE2: chipset revision 162

:)

> 
> I have found tons of people with this exact problem.  My Abit board will run
> Windows 2000 flawlessly, but lockup in a minute under Linux.

> 
> Currently I have a reward of $20 posted on two lists looking for a solution.  Currently looking to up the ante to $40.
> 
> http://www.nvnews.net/vbulletin/showthread.php?s=&threadid=16264
> 
> http://www.nforcershq.com/forum/viewtopic.php?t=27003
> 
> I don't think the problem is the the IDE.  I have used a promise controller
> and disabled the onboard IDE and still had lockups.  If you find a solution,
> please let me know.  If I find one, I will do likewise.

It looks like the problem is in APIC. When you disable it, it vanishes.
And, when you enable NMI watchdog, which is handled by APIC,
it doesn't work - it couts up to 15 in /proc/interrupts and then stops!

Cl<
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/