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  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:	Wed, 12 Feb 2014 09:15:03 -0700
From:	Toshi Kani <>
To:	Matt Fleming <>
Cc:	Madper Xie <>,
	Matt Fleming <>,
	"" <>,
	"" <>,
	Matthew Garrett <>,
	"Rafael J. Wysocki" <>,
	Josh Triplett <>
Subject: Re: [BUG] can't boot up: unable to handle kernel paging request at

On Tue, 2014-02-11 at 14:18 +0000, Matt Fleming wrote:
> (Entering the realm of ACPI, pulling in more folks)
> On Tue, 11 Feb, at 09:47:57PM, Madper Xie wrote:
> > Thanks for your reply. I attached the all the dmesg outputs for you.
> > [    0.000000] ACPI: BGRT 00000000d9bb5100 00003C (v00 HPQOEM SLIC-BPC 01072009 AMI  00010013)
> Your BGRT table has an extra 4 bytes for some reason, (0x3C should be
> 0x38) and doesn't match the defintion in include/acpi/actbl3.h,
> struct acpi_table_bgrt {
> 	struct acpi_table_header header;	/* Common ACPI table header */
> 	u16 version;
> 	u8 status;
> 	u8 image_type;
> 	u64 image_address;
> 	u32 image_offset_x;
> 	u32 image_offset_y;
> };
> which explains why when we dereference ->image_address we don't get a
> sensible value.
> Guys, what do you make of this? Firmware bug? Full thread here,

Hi Matt,

Yes, I agree that the table size should be 0x38.  However, ACPI spec
states that bit0 of status indicates if the boot image graphic is valid.
This bit is set to 0 (invalid) on the system.  Can you check this bit
and return when invalid? 


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists