linux-kernel - Re: Endless ACPI errors on Linus tree (5b664cb235)

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:	Mon, 21 Jul 2008 09:11:44 +0100
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	"Andi Kleen" <andi@...stfloor.org>, "Takashi Iwai" <tiwai@...e.de>
Cc:	<robert.moore@...el.com>, "Len Brown" <lenb@...nel.org>,
	"LKML" <linux-kernel@...r.kernel.org>
Subject: Re: Endless ACPI errors on Linus tree (5b664cb235)

>> > > After someone else observed some problem with this patch earlier, I had
>> > > already sent out attached patch as a replacement one. Any chance you
>> > > could also try this with your box?
>> > 
>> > It resulted in the same error, unfortunately.
>> 
>> Can you send a acpi table dump please?

The situation is even worse here - the (v2) bit width now is divisible by 16,
but still isn't in sync with the v1 field (as is the gpe0 one):

		v1		v2
PM1a_EVT	4		0x10
PM1a_CNT	2		0x10
PM1b_CNT	2		0x10
PM_TMR		4		0x20
GPE0		8		0x20

That would basically mean there's no way to use the v2 fields here - all
the code could do is report the inconsitency, but it would have to use
the v1 field in any case. That's really a shame, and as before I'm
somewhat hesitant to do so. The only way I could easily find myself
doing this would be to introduce a command line option controlling the
behavior here, but that would need to be done outside of the ACPICA
code I'd assume.

Andi, Bob, Len?

Jan

--
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/