Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754404AbZD3H0W (ORCPT ); Thu, 30 Apr 2009 03:26:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751541AbZD3H0M (ORCPT ); Thu, 30 Apr 2009 03:26:12 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:58931 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750867AbZD3H0L (ORCPT ); Thu, 30 Apr 2009 03:26:11 -0400 Date: Thu, 30 Apr 2009 09:25:56 +0200 From: Ingo Molnar To: Matthew Garrett Cc: "Darrick J. Wong" , Thomas Renninger , linux-kernel , cpufreq@vger.kernel.org, linux-acpi@vger.kernel.org Subject: Re: [PATCH v2] acpi: Fix regression where _PPC is not read at boot even when ignore_ppc=0 Message-ID: <20090430072556.GD16737@elte.hu> References: <20090415225348.GW8311@plum> <20090416002712.GX8311@plum> <200904161201.13409.trenn@suse.de> <20090416174217.GY8311@plum> <20090416224507.GA31984@srcf.ucam.org> <20090428193303.GC6968@plum> <20090428195348.GA8376@srcf.ucam.org> <20090429213930.GE6968@plum> <20090429220037.GA8604@srcf.ucam.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090429220037.GA8604@srcf.ucam.org> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1536 Lines: 37 * Matthew Garrett wrote: > On Wed, Apr 29, 2009 at 02:39:31PM -0700, Darrick J. Wong wrote: > > > I don't know about XP's copy of intelppm.sys, but this would seem to confirm > > that WS03 and WS08 check _PPC at boot time. > > Ok, so that makes things interesting. From what we know about the > T60 (and based on Ingo's report), _PPC may evaluate to 2 on > bootup. However, if this is ignored then later notifications are > correct. This implies that Windows either ignores the initial > evaluation or does something that triggers a notification. > > The only notifications appear to be sent from event methods, so > there's nothing obvious there that we can trigger. I'm actually > quite confused by this now. Ingo, if you re-add that block, does > your system stop working again? That box is working fine now doing ~100 bootup tests per day - so if you send me a suitably changelogged patch (revert?) i can apply that to tip:out-of-tree for testing and we'll find out quickly whether the box stops working. OTOH, if you rely on me figuring out which patch to revert and what to do, it will take an indeterminate amount of time - together with all the other items in my 'would be nice to hack on, given a bit of free time' queue :) Thanks, Ingo -- 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/