Re: 2.6.18 Nasty Lockup

[Andi Kleen <ak@muc.de>]

On Wed, Sep 27, 2006 at 12:14:59PM -0700, john stultz wrote:
> 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

On Intel it seems to happen when people overclock their systems.

> 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?

Throttling has nothing to do with cpufreq
(at least not until you use the broken P4 throttling cpufreq
driver, which nobody should). It is normally only used when
the CPU overheats.

-Andi

-
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/