From: john stultz <johnstul@us.ibm.com>
To: caglar@pardus.org.tr
Cc: Greg Schafer <gschafer@zip.com.au>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@muc.de>
Subject: Re: 2.6.18 Nasty Lockup
Date: Wed, 27 Sep 2006 12:14:59 -0700 [thread overview]
Message-ID: <1159384500.29040.3.camel@localhost> (raw)
In-Reply-To: <200609271245.39591.caglar@pardus.org.tr>
On Wed, 2006-09-27 at 12:45 +0300, S.Çağlar Onur wrote:
> 27 Eyl 2006 Çar 01:50 tarihinde, john stultz şunları yazmıştı:
> > On Wed, 2006-09-27 at 00:15 +0300, S.Çağlar Onur wrote:
> > > 26 Eyl 2006 Sal 15:36 tarihinde, Greg Schafer şunları yazmıştı:
> > > > This is a _hard_ lockup. No oops, no magic sysrq, no nuthin, just a
> > > > completely dead machine with only option the reset button. Usually
> > > > happens within a couple of minutes of desktop use but is 100%
> > > > reproducible. Problem is still there in a fresh checkout of current
> > > > Linus git tree (post 2.6.18).
> > >
> > > Same symptoms here and its reproducible after starting the irqbalance
> > > (0.12 or 0.13), if i disable irqbalance then everything is going fine.
> >
> > Hmm.. Not sure about the connection to irqbalance. You're using the TSC
> > clocksource, so I'm curious if your cpu TSC's are out of sync. Can you
> > boot w/ "clocksource=acpi_pm" to see if that resolves it?
>
> Yep, it solves the problem and system boot normally with irqbalance enabled.
Ok. Good to hear you have a workaround. Now to sort out why your TSCs
are becoming un-synced. From the dmesg you sent me privately, I noticed
that while you have 4 cpus, the following message only shows up once:
ACPI: Processor [CPU1] (supports 8 throttling states)
Does disabling cpufreq change anything?
thanks
-john
next prev parent reply other threads:[~2006-09-27 19:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 12:36 2.6.18 Nasty Lockup Greg Schafer
2006-09-26 13:56 ` Michael Obster
2006-09-26 15:41 ` Ben Duncan
2006-09-26 18:18 ` john stultz
2006-09-26 20:15 ` john stultz
2006-09-26 22:02 ` Greg Schafer
2006-09-26 22:58 ` john stultz
2006-09-26 21:15 ` S.Çağlar Onur
2006-09-26 22:50 ` john stultz
2006-09-27 9:45 ` S.Çağlar Onur
2006-09-27 19:14 ` john stultz [this message]
2006-09-27 20:55 ` Andi Kleen
2006-09-27 21:06 ` S.Çağlar Onur
2006-09-28 11:39 ` S.Çağlar Onur
2006-09-29 8:49 ` S.Çağlar Onur
2006-10-06 22:57 ` john stultz
2006-10-07 15:48 ` S.Çağlar Onur
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=1159384500.29040.3.camel@localhost \
--to=johnstul@us.ibm.com \
--cc=ak@muc.de \
--cc=caglar@pardus.org.tr \
--cc=gschafer@zip.com.au \
--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