linux-kernel - Re: FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT

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]

Message-ID: <49685B70.8080908@shaw.ca>
Date:	Sat, 10 Jan 2009 02:25:20 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	"Justin P. Mattock" <justinmattock@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN
 (4)

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