From: Toshi Kani <toshi.kani@hp.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org, x86@kernel.org
Subject: EFI tree kernel panic in phys_efi_set_virtual_address_map()
Date: Wed, 11 Dec 2013 17:01:03 -0700 [thread overview]
Message-ID: <1386806463.1791.295.camel@misato.fc.hp.com> (raw)
Hi Boris,
An EFI tree kernel panic'd during boot on one of my systems. It boots
fine when efi=old_map option is specified. So, I think it is caused by
your EFI virtual mapping changes.
The panic message is as follows. I added some printk's to log the
arguments of phys_efi_set_virtual_address_map(). The fault address is
__pa(new_memmap) + 0x20 (too high for the map?).
Thanks,
-Toshi
efi: >> Call phys_efi_set_virtual_address_map()
efi: count 29
efi: desc_size 0x30
efi: new_memmap 0xffff8a03fec16800
efi: __pa(new_memmap) 0x203fec16800
BUG: unable to handle kernel paging request at 00000203fec16820
IP: [<0000000072dcda76>] 0x72dcda75
PGD 0
Oops: 0000 [#1] SMP
Modules linked in:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.12.0+ #52
Hardware name: HP CB920s x1, BIOS Bundle: 005.028.018 SFW: 012.124.000
10/28/2013
task: ffffffff81a10480 ti: ffffffff81a00000 task.ti: ffffffff81a00000
RIP: 0010:[<0000000072dcda76>] [<0000000072dcda76>] 0x72dcda75
RSP: 0000:ffffffff81a01e08 EFLAGS: 00010206
RAX: 00000000725fee18 RBX: 00000000725feda0 RCX: 00000203fec16800
RDX: 0000000072dfe070 RSI: 0000000060000202 RDI: 0000000072dcdac8
RBP: 0000000072dd0560 R08: 0000000000000000 R09: 000000000000001d
R10: 0000000000000030 R11: 8000000000000000 R12: ffff8a03fec16800
R13: 0000000000000001 R14: 000000000000001d R15: 000000000009c000
FS: 0000000000000000(0000) GS:ffff88087fa00000(0000)
knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000203fec16820 CR3: 000000000009c000 CR4: 00000000000406b0
Stack:
0000000072dfb88f 0000000000000001 0000000000000d08 0000000000000000
ffffffff81d79a98 0000000072dcdac8 0000000072dcdb93 0000000000000001
ffffffff81a01f80 0000000000000570 0000000000000000 0000000000000000
Call Trace:
[<ffffffff81045cec>] ? efi_call4+0x6c/0xf0
[<ffffffff81b02f65>] ? efi_enter_virtual_mode+0x229/0x3f1
[<ffffffff81aebdf2>] ? start_kernel+0x36c/0x407
[<ffffffff81aeb88f>] ? repair_env_string+0x5c/0x5c
[<ffffffff81aeb5a3>] ? x86_64_start_reservations+0x2a/0x2c
[<ffffffff81aeb696>] ? x86_64_start_kernel+0xf1/0xf4
Code: Bad RIP value.
RIP [<0000000072dcda76>] 0x72dcda75
RSP <ffffffff81a01e08>
CR2: 00000203fec16820
---[ end trace e50b25032c120443 ]---
next reply other threads:[~2013-12-12 0:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 0:01 Toshi Kani [this message]
2013-12-12 0:29 ` EFI tree kernel panic in phys_efi_set_virtual_address_map() Borislav Petkov
2013-12-12 0:32 ` Toshi Kani
2013-12-12 1:08 ` Toshi Kani
[not found] ` <1386810620.1791.307.camel@misato.fc.hp.com>
2013-12-12 16:23 ` Borislav Petkov
2013-12-12 16:43 ` Toshi Kani
2013-12-12 17:27 ` Toshi Kani
2013-12-12 17:36 ` Toshi Kani
2013-12-12 20:35 ` Borislav Petkov
2013-12-12 20:44 ` Toshi Kani
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=1386806463.1791.295.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=bp@alien8.de \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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