public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: "Andrew Paprocki" <andrew@ishiboo.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Jan Beulich" <jbeulich@novell.com>,
	"Andi Kleen" <ak@linux.intel.com>, "Len Brown" <lenb@kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	robert.moore@intel.com
Subject: Re: ACPI WARNING: at drivers/acpi/tables/tbfadt.c:348 acpi_tb_create_local_fadt+0x147/0x2f4()
Date: Thu, 17 Jul 2008 11:00:14 +0200	[thread overview]
Message-ID: <8763r4yjfl.fsf@basil.nowhere.org> (raw)
In-Reply-To: <76366b180807162034y1e725b15t7658c331bb89b52@mail.gmail.com> (Andrew Paprocki's message of "Wed, 16 Jul 2008 23:34:45 -0400")

"Andrew Paprocki" <andrew@ishiboo.com> writes:

[cc Bob More. What is your opinion?]

> This most definitely broke because of:
>
> commit 01a5bba576b9364b33f61f0cd9fa70c2cf5535e2
> Author: Jan Beulich <jbeulich@novell.com>
> Date:   Wed Jul 16 23:27:08 2008 +0200
>
>     Fix FADT parsing
>
> I added printk()s and this is what is reported here:

Thanks for the detailed analysis. 


>
>         printk(KERN_INFO
>                "xpm1a_event_block bit_width=%d pm1_register_length=%d\n",
>                acpi_gbl_FADT.xpm1a_event_block.bit_width, pm1_register_length);
>         acpi_tb_init_generic_address(&acpi_gbl_xpm1a_enable,
>                                      pm1_register_length,
>                                      (acpi_gbl_FADT.xpm1a_event_block.address +
>                                       pm1_register_length));
>
> [    0.000000] xpm1a_event_block bit_width=8 pm1_register_length=0
>
> The bit width is not % 16, so the following patch addition a few lines
> earlier fails:
>
>         WARN_ON(ACPI_MOD_16(acpi_gbl_FADT.xpm1a_event_block.bit_width));

I'll queue a revert for now until this can be resolved properly.

-Andi

      parent reply	other threads:[~2008-07-17  9:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17  2:29 ACPI WARNING: at drivers/acpi/tables/tbfadt.c:348 acpi_tb_create_local_fadt+0x147/0x2f4() Andrew Paprocki
2008-07-17  3:34 ` Andrew Paprocki
2008-07-17  8:59   ` Jan Beulich
2008-07-17  9:06     ` Andi Kleen
2008-07-17  9:14       ` Jan Beulich
2008-07-17 12:28         ` Andi Kleen
2008-07-17 13:03           ` Andrew Paprocki
2008-07-17 13:58             ` Jan Beulich
2008-07-17 14:32               ` Andrew Paprocki
2008-07-17 15:30                 ` Jan Beulich
2008-07-17 17:20                   ` ACPI WARNING: at drivers/acpi/tables/tbfadt.c:348acpi_tb_create_local_fadt+0x147/0x2f4() Moore, Robert
2008-07-17 17:40                     ` Andi Kleen
2008-07-18  7:53                       ` Jan Beulich
2008-07-18  8:43                     ` Jan Beulich
2008-07-18 16:52                       ` ACPI WARNING: atdrivers/acpi/tables/tbfadt.c:348acpi_tb_create_local_fadt+0x147/0x2f4() Moore, Robert
2008-07-18  9:48                     ` ACPI WARNING: at drivers/acpi/tables/tbfadt.c:348acpi_tb_create_local_fadt+0x147/0x2f4() Jan Beulich
2008-07-17  9:00   ` Andi Kleen [this message]

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=8763r4yjfl.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrew@ishiboo.com \
    --cc=jbeulich@novell.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.moore@intel.com \
    /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