[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080825142403.03d7c354@infradead.org>
Date: Mon, 25 Aug 2008 14:24:03 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Dave Jones <davej@...hat.com>
Cc: Andi Kleen <andi@...stfloor.org>,
Vegard Nossum <vegard.nossum@...il.com>,
"H. Peter Anvin" <hpa@...nel.org>,
the arch/x86 maintainers <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: latest -git: WARNING: at arch/x86/kernel/ipi.c:123
send_IPI_mask_bitmask+0xc3/0xe0()
On Mon, 25 Aug 2008 16:47:02 -0400
Dave Jones <davej@...hat.com> wrote:
> On Mon, Aug 25, 2008 at 10:36:49PM +0200, Andi Kleen wrote:
>
> > > If we get a thermal event that was caused by temporary
> > > increased workload, temperature will drop off again when that
> > > workload is complete.
> >
> > But none of the cpufreq governours do this. They only care about
> > load, not about temperature.
>
> Which is good enough to stop p4 laptops from shutting down as
> soon as they've finished booting up.\
that's such an enormous gamble it's not funny.
really; if your bios has broken trippoints we should use the kernel
commandline to disable them (and a dmi blacklist if the amount of
bioses that have it wrong is low.. maybe combined with a date based
threshold).
Just praying that p4clockmod keeps it kinda low enough is not the
answer.
--
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists