To: linux-kernel@vger.kernel.org
Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11)
References: <OF6617181D.A93B9D63-ON80256DEC.004D7534-80256DEC.0053A823@uk.neceur.com>
	<200311281646.40171.s0348365@sms.ed.ac.uk>
	<frodoid.frodo.87zneg8ipo.fsf@usenet.frodoid.org>
	<20031129025500.GA5611@forming>
From: Julien Oster <frodoid@frodoid.org>
Organization: FRODOID.ORG
Date: Sat, 29 Nov 2003 17:33:08 +0100
In-Reply-To: <20031129025500.GA5611@forming> (Josh McKinney's message of
 "Fri, 28 Nov 2003 21:55:00 -0500")
Message-ID: <frodoid.frodo.87he0njfsr.fsf@usenet.frodoid.org>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org

Josh McKinney <forming@charter.net> writes:

Hello Josh,

> I have also been using a A7N8X deluxe and saw lockups when I first
> recieved the board.  Booting with noapic nolapic solved the problems.
> Later after reading some threads about it I decided to add some stuff to
> a bugzilla that someone else already filed.  After doing this I decided
> to try to crash it like it used to to with apic and lapic but it DID NOT
> CRASH!  This may be due to an updated BIOS, I am using the 1007 Uber
> BIOS, or some updates with the kernel, but I am running 2.6.0-test9-mm3
> rock solid with ACPI, APIC, and local APIC.

Oh! That sounds nice. I also run the latest 1007 BIOS, but that
doesn't help at all. In crontrary, I almost have the impression that
the lockups got worse, but that may be just subjective. But what do
you mean with "1007 Uber BIOS"? What is this "Uber"? Is that a special
BIOS Version?

However, 2.6.0-test9-mm3 might be the key. I'll test this immediately.

Thanks,
Julien
-
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/