From: Robert Hancock <hancockr@shaw.ca>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN (4)
Date: Sat, 10 Jan 2009 02:25:20 -0600 [thread overview]
Message-ID: <49685B70.8080908@shaw.ca> (raw)
In-Reply-To: <49683957.9070700@gmail.com>
Justin P. Mattock wrote:
> I am seeing this in dmesg:
> FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN (4)
> not sure what this is.
> (the only changes to .config was add kexec,
> coredump, and relocatable kernel options.)
>
> I take it that I'm unable to try this relocatable
> kernel stuff out.(x86_32)?
>
> regards;
>
> Justin P. Mattock
I believe that indicates your BIOS's FADT table contains inconsistent
data. You're sure that only happens with those options set?
next prev parent reply other threads:[~2009-01-10 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 5:59 FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN (4) Justin P. Mattock
2009-01-10 8:25 ` Robert Hancock [this message]
2009-01-10 16:23 ` Justin P. Mattock
2009-01-11 0:02 ` Robert Hancock
2009-01-11 0:23 ` Justin P. Mattock
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=49685B70.8080908@shaw.ca \
--to=hancockr@shaw.ca \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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