From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: Madper Xie <cxie-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Matt Fleming
<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>,
"Rafael J. Wysocki" <rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org>,
Josh Triplett <josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org>
Subject: Re: [BUG] can't boot up: unable to handle kernel paging request at ffffffffff340003
Date: Tue, 11 Feb 2014 14:18:46 +0000 [thread overview]
Message-ID: <20140211141846.GA1725@console-pimps.org> (raw)
In-Reply-To: <87lhxh69u0.fsf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
(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,
http://article.gmane.org/gmane.linux.kernel.efi/3499
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-02-11 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 7:23 [BUG] can't boot up: unable to handle kernel paging request at ffffffffff340003 Madper Xie
2014-02-10 17:52 ` Matt Fleming
[not found] ` <20140210175246.GB2887-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-02-11 3:00 ` Madper Xie
[not found] ` <87mwhy8iaj.fsf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-02-11 13:16 ` Matt Fleming
2014-02-11 13:47 ` Madper Xie
[not found] ` <87lhxh69u0.fsf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-02-11 14:18 ` Matt Fleming [this message]
2014-02-12 0:00 ` Rafael J. Wysocki
[not found] ` <20140211141846.GA1725-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-02-12 16:15 ` Toshi Kani
[not found] ` <1392221703.5612.164.camel-RbGIw1UOYPVo/CpIj0byZw@public.gmane.org>
2014-02-12 16:39 ` Matt Fleming
2014-02-13 10:55 ` Matt Fleming
[not found] ` <20140213105547.GC20717-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-02-13 13:40 ` Madper Xie
[not found] ` <87k3czdtbf.fsf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-02-13 17:10 ` Matthew Garrett
2014-02-13 23:48 ` Rafael J. Wysocki
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=20140211141846.GA1725@console-pimps.org \
--to=matt-hnk1s37rvnbexh+ff434mdi2o/jbrioy@public.gmane.org \
--cc=cxie-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org \
--cc=rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.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