From: "Jan Beulich" <jbeulich@novell.com>
To: "Andi Kleen" <andi@firstfloor.org>, "Takashi Iwai" <tiwai@suse.de>
Cc: <robert.moore@intel.com>, "Len Brown" <lenb@kernel.org>,
"LKML" <linux-kernel@vger.kernel.org>
Subject: Re: Endless ACPI errors on Linus tree (5b664cb235)
Date: Mon, 21 Jul 2008 09:11:44 +0100 [thread overview]
Message-ID: <488460E0.76E4.0078.0@novell.com> (raw)
In-Reply-To: <s5hmykexm53.wl%tiwai@suse.de>
>> > > 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
next prev parent reply other threads:[~2008-07-21 8:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 11:24 Takashi Iwai
2008-07-18 11:35 ` Andi Kleen
2008-07-18 13:15 ` Takashi Iwai
2008-07-18 13:34 ` Takashi Iwai
2008-07-18 15:48 ` Takashi Iwai
2008-07-18 15:52 ` Andi Kleen
2008-07-18 15:56 ` Takashi Iwai
2008-07-18 16:16 ` Jan Beulich
2008-07-18 16:38 ` Takashi Iwai
2008-07-18 16:58 ` Andi Kleen
2008-07-19 9:23 ` Takashi Iwai
2008-07-21 8:11 ` Jan Beulich [this message]
2008-07-21 8:43 ` Andi Kleen
2008-07-23 11:27 ` Jan Beulich
2008-07-23 15:43 ` Moore, Robert
2008-07-23 16:14 ` Jan Beulich
2008-09-17 4:56 ` Andrew Paprocki
2008-09-17 6:43 ` Jan Beulich
2008-09-17 15:04 ` Andi Kleen
2008-07-18 15:52 ` Andi Kleen
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=488460E0.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=andi@firstfloor.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=tiwai@suse.de \
/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®