Date: Tue, 28 Nov 2006 12:55:36 +0800
From: Federico Sevilla III <jijo@free.net.ph>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.18.3 Lockup on Athlon MP
Message-ID: <20061128045536.GD3092@free.net.ph>
Mail-Followup-To: Federico Sevilla III <jijo@free.net.ph>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
References: <20061128031701.GC3092@free.net.ph>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20061128031701.GC3092@free.net.ph>
User-Agent: Mutt/1.5.13 (2006-08-11)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 994
Lines: 24

On Tue, Nov 28, 2006 at 11:17:01AM +0800, Federico Sevilla III wrote:
> I am experiencing hard lock ups on a dual Athlon MP 2600+ with Linux
> kernel 2.6.18.3. This can be reproduced within two minutes by running
> burnK7 from cpuburn. I am sure it's not just a hardware issue, though,
> since running a 2.6.14 kernel using ServerBeach's "RapidRescue"
> environment allows me to run burnK7 for extended periods without
> locking up the machine.

I found the thread "2.6.18 Nasty Lockup" and tried the suggestion to
boot with clocksource=acpi_pm. The two burnK7 processes have been
running (stressing both CPUs) for 90 minutes now and the system
continues to be responsive.

 --> Jijo

-- 
Federico Sevilla III
F S 3 Consulting Inc.
http://www.fs3.ph
-
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/