linux-kernel - Re: [PATCH v2] acpi: Fix regression where _PPC is not read at boot even when ignore

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 30 Apr 2009 09:25:56 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	"Darrick J. Wong" <djwong@...ibm.com>,
	Thomas Renninger <trenn@...e.de>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	cpufreq@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: [PATCH v2] acpi: Fix regression where _PPC is not read at boot
	even when ignore_ppc=0


* Matthew Garrett <mjg59@...f.ucam.org> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/