Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756827AbYHYTxx (ORCPT ); Mon, 25 Aug 2008 15:53:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753905AbYHYTxp (ORCPT ); Mon, 25 Aug 2008 15:53:45 -0400 Received: from mx2.redhat.com ([66.187.237.31]:49666 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753215AbYHYTxp (ORCPT ); Mon, 25 Aug 2008 15:53:45 -0400 Date: Mon, 25 Aug 2008 15:50:31 -0400 From: Dave Jones To: Andi Kleen Cc: Vegard Nossum , "H. Peter Anvin" , the arch/x86 maintainers , Linux Kernel Mailing List , Rusty Russell Subject: Re: latest -git: WARNING: at arch/x86/kernel/ipi.c:123 send_IPI_mask_bitmask+0xc3/0xe0() Message-ID: <20080825195029.GA27030@redhat.com> Mail-Followup-To: Dave Jones , Andi Kleen , Vegard Nossum , "H. Peter Anvin" , the arch/x86 maintainers , Linux Kernel Mailing List , Rusty Russell References: <20080822003659.GA7581@redhat.com> <48AE20B8.9000204@kernel.org> <19f34abd0808240220v77bcdd5di32f8f865b18fc49f@mail.gmail.com> <48B19799.6090703@kernel.org> <19f34abd0808241022j1ab6f3e6qd72b9acba5df4892@mail.gmail.com> <19f34abd0808241045r37eb8661h3cc688b6f0513777@mail.gmail.com> <20080824181304.GA5963@redhat.com> <20080825183611.GE26610@one.firstfloor.org> <20080825185450.GD11894@redhat.com> <20080825193926.GF26610@one.firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080825193926.GF26610@one.firstfloor.org> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1796 Lines: 41 On Mon, Aug 25, 2008 at 09:39:26PM +0200, Andi Kleen wrote: > On Mon, Aug 25, 2008 at 02:54:51PM -0400, Dave Jones wrote: > > On Mon, Aug 25, 2008 at 08:36:11PM +0200, Andi Kleen wrote: > > > > Probably because you're using p4-clockmod, and it's crap. > > > > > > Really should really bite the bullet and just remove it. People > > > run in this all the time and I bet you can count the people who > > > actually use it consciously and usefully with one hand. > > > > > > Or at least only make it run when the user set a "I_REALLY_KNOW_WHAT_I_AM_DOING" > > > option explicitely. > > > > We can't really remove it until ACPI processor driver has a better > > response than 'thermal event, argh!, shut down'. > > It only does that when the critical trip point is reached (which > basically means that the BIOS tells it -- "I'm on fire"). What else should > it do in your opinion when this happens? On some systems (for which there aren't BIOS updates) the trip points are set too low. If we get a thermal event that was caused by temporary increased workload, temperature will drop off again when that workload is complete. For sustained workloads we'd get additional thermal events, at which time we make a decision "ok, we've throttled as far as we can, and things are still going badly, power off". In the event of a failed fan or similar, shutting down is obviously the right thing to do, and we'd get further thermal events after throttling which would allow us to do so. Dave -- http://www.codemonkey.org.uk -- 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/