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
Date: Tue, 28 Nov 2006 12:55:36 +0800 [thread overview]
Message-ID: <20061128045536.GD3092@free.net.ph> (raw)
In-Reply-To: <20061128031701.GC3092@free.net.ph>
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
prev parent reply other threads:[~2006-11-28 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 3:17 2.6.18.3 Lockup on Athlon MP Federico Sevilla III
2006-11-28 4:55 ` Federico Sevilla III [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061128045536.GD3092@free.net.ph \
--to=jijo@free.net.ph \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox