[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140211131640.GD2887@console-pimps.org>
Date: Tue, 11 Feb 2014 13:16:40 +0000
From: Matt Fleming <matt@...sole-pimps.org>
To: Madper Xie <cxie@...hat.com>
Cc: Matt Fleming <matt.fleming@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
Adam Williamson <awilliam@...hat.com>
Subject: Re: [BUG] can't boot up: unable to handle kernel paging request at
ffffffffff340003
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
--
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/
Powered by blists - more mailing lists