From: Matt Fleming <matt@console-pimps.org>
To: Madper Xie <cxie@redhat.com>
Cc: Matt Fleming <matt.fleming@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
Adam Williamson <awilliam@redhat.com>
Subject: Re: [BUG] can't boot up: unable to handle kernel paging request at ffffffffff340003
Date: Tue, 11 Feb 2014 13:16:40 +0000 [thread overview]
Message-ID: <20140211131640.GD2887@console-pimps.org> (raw)
In-Reply-To: <87mwhy8iaj.fsf@redhat.com>
On Tue, 11 Feb, at 11:00:52AM, Madper Xie wrote:
> it doesn't help, seems the same panic output:
OK, thanks for testing so quickly.
> [ 0.001341] BUG: unable to handle kernel paging request at ffffffffff340003
> [ 0.008339] IP: [<ffffffff81a73794>] efi_bgrt_init+0x9d/0x133
> [ 0.014111] PGD 28fb067 PUD 28fd067 PMD 2bef067 PTE 9376e01800000163
Thinking about this a bit harder that PTE is invalid because bits 52-63
are not zero, which is exactly the problem you were hitting prior to
-rc2, namely that the physical BGRT address is bogus.
Can you post the EFI memory map entries from a dmesg? I just want to
make sure that it really is the BGRT address that is broken and not
something else. Also, please post the ACPI: BGRT entry from your dmesg
too. Thanks.
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-02-11 13:17 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
2014-02-11 3:00 ` Madper Xie
2014-02-11 13:16 ` Matt Fleming [this message]
2014-02-11 13:47 ` Madper Xie
2014-02-11 14:18 ` Matt Fleming
2014-02-12 0:00 ` Rafael J. Wysocki
2014-02-12 16:15 ` Toshi Kani
2014-02-12 16:39 ` Matt Fleming
2014-02-13 10:55 ` Matt Fleming
2014-02-13 13:40 ` Madper Xie
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=20140211131640.GD2887@console-pimps.org \
--to=matt@console-pimps.org \
--cc=awilliam@redhat.com \
--cc=cxie@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@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