mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Dave Jones <davej@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	Vegard Nossum <vegard.nossum@gmail.com>,
	"H. Peter Anvin" <hpa@kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: latest -git: WARNING: at arch/x86/kernel/ipi.c:123 send_IPI_mask_bitmask+0xc3/0xe0()
Date: Mon, 25 Aug 2008 14:24:03 -0700	[thread overview]
Message-ID: <20080825142403.03d7c354@infradead.org> (raw)
In-Reply-To: <20080825204700.GB27030@redhat.com>

On Mon, 25 Aug 2008 16:47:02 -0400
Dave Jones <davej@redhat.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@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-08-25 21:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 19:51 Vegard Nossum
2008-08-20  1:39 ` Andi Kleen
2008-08-20  6:26   ` Vegard Nossum
2008-08-22  0:36     ` Dave Jones
2008-08-22  2:13       ` H. Peter Anvin
2008-08-22  2:28         ` Andi Kleen
2008-08-22  6:24           ` H. Peter Anvin
2008-08-22  9:35             ` Andi Kleen
2008-08-22 16:41               ` H. Peter Anvin
2008-08-23  6:42                 ` Jeremy Fitzhardinge
2008-08-23  6:44                   ` H. Peter Anvin
2008-08-22 11:13           ` adobriyan
2008-08-24  9:20         ` Vegard Nossum
2008-08-24 16:43           ` H. Peter Anvin
2008-08-24 17:17           ` H. Peter Anvin
2008-08-24 17:22             ` Vegard Nossum
2008-08-24 17:45               ` Vegard Nossum
2008-08-24 17:59                 ` H. Peter Anvin
2008-08-24 18:13                 ` Dave Jones
2008-08-25 18:31                   ` Vegard Nossum
2008-08-25 18:38                     ` Dave Jones
2008-08-25 18:36                   ` Andi Kleen
2008-08-25 18:54                     ` Dave Jones
2008-08-25 19:39                       ` Andi Kleen
2008-08-25 19:50                         ` Dave Jones
2008-08-25 20:36                           ` Andi Kleen
2008-08-25 20:47                             ` Dave Jones
2008-08-25 21:24                               ` Arjan van de Ven [this message]
2008-08-25 19:08                     ` H. Peter Anvin
2008-08-25 19:13                       ` Dave Jones

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=20080825142403.03d7c354@infradead.org \
    --to=arjan@infradead.org \
    --cc=andi@firstfloor.org \
    --cc=davej@redhat.com \
    --cc=hpa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=vegard.nossum@gmail.com \
    --cc=x86@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

all inboxes | Powered by JetHome®