From: Alex Thorlton <athorlton-sJ/iWh9BUns@public.gmane.org>
To: Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>
Cc: Russ Anderson <rja-sJ/iWh9BUns@public.gmane.org>,
"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
Matt Fleming
<matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [BUG] Linux 3.14 fails to boot with new EFI changes
Date: Wed, 5 Feb 2014 15:45:36 -0600 [thread overview]
Message-ID: <20140205214536.GT3034@sgi.com> (raw)
In-Reply-To: <20140131142318.GC21873-fF5Pk5pvG8Y@public.gmane.org>
On Fri, Jan 31, 2014 at 03:23:18PM +0100, Borislav Petkov wrote:
> And now my question:
>
> How can I reliably find out which region contains that
> uv_systab.function call?
>
> I need it so that I can map it in the EFI page table and you can
> continue to call that function and you can get back to your reliable way
> to boot.
While working on an answer to this question, I ran across another issue
on some newer hardware, that looks like it's definitely related to this
problem, and might be the root cause.
When booting on a UV2 we die in efi_enter_virtual_mode:
BUG: unable to handle kernel paging request at 0000008f7e848020
IP: [<000000007dadb6a9>] 0x7dadb6a8
PGD 0
Oops: 0000 [#1] SMP
Modules linked in:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.11.0-medusa-00038-gd2f7cbe #821
Hardware name: SGI UV2000/ROMLEY, BIOS SGI UV 2000/3000 series BIOS 01/15/2013
task: ffffffff817ae400 ti: ffffffff8179e000 task.ti: ffffffff8179e000
RIP: 0010:[<000000007dadb6a9>] [<000000007dadb6a9>] 0x7dadb6a8
RSP: 0000:ffffffff8179fd90 EFLAGS: 00010202
RAX: 000000007d9b8e01 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 000000007db074f8 RSI: 000000007d9b8e18 RDI: 0000008f7e848000
RBP: 000000007db074f8 R08: 0000000000000001 R09: 0000008f7e848000
R10: 0000000000000030 R11: ffff880ffffda000 R12: 8000000000000000
R13: 000077ff80000000 R14: ffff888f7e848000 R15: 000000000009b000
FS: 0000000000000000(0000) GS:ffff880fffc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000008f7e848020 CR3: 000000000009b000 CR4: 00000000000406b0
Stack:
fffffffef6000000 0000000000000000 0000000000000000 80000000000001e3
0000000000000030 000000007dadd540 0000000000001f20 0000000060000202
000000007d9b8da0 000000007daf8c6b ffffffff810fd2bc 00000000000000d0
Call Trace:
[<ffffffff810fd2bc>] ? cache_grow+0x1e5/0x236
[<ffffffff8103adac>] ? efi_call4+0x6c/0xf0
[<ffffffff8186452f>] ? efi_enter_virtual_mode+0x1ac/0x328
[<ffffffff8184de98>] ? start_kernel+0x35b/0x3ed
[<ffffffff8184d950>] ? repair_env_string+0x60/0x60
[<ffffffff8184d479>] ? x86_64_start_reservations+0x2e/0x30
[<ffffffff8184d5a3>] ? x86_64_start_kernel+0x128/0x12f
Code: Bad RIP value.
RIP [<000000007dadb6a9>] 0x7dadb6a8
RSP <ffffffff8179fd90>
CR2: 0000008f7e848020
Let me know what other information you need and I'll get it to you ASAP.
Thanks!
- Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alex Thorlton <athorlton@sgi.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Russ Anderson <rja@sgi.com>, "H. Peter Anvin" <hpa@zytor.com>,
Matt Fleming <matt@console-pimps.org>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Re: [BUG] Linux 3.14 fails to boot with new EFI changes
Date: Wed, 5 Feb 2014 15:45:36 -0600 [thread overview]
Message-ID: <20140205214536.GT3034@sgi.com> (raw)
In-Reply-To: <20140131142318.GC21873@pd.tnic>
On Fri, Jan 31, 2014 at 03:23:18PM +0100, Borislav Petkov wrote:
> And now my question:
>
> How can I reliably find out which region contains that
> uv_systab.function call?
>
> I need it so that I can map it in the EFI page table and you can
> continue to call that function and you can get back to your reliable way
> to boot.
While working on an answer to this question, I ran across another issue
on some newer hardware, that looks like it's definitely related to this
problem, and might be the root cause.
When booting on a UV2 we die in efi_enter_virtual_mode:
BUG: unable to handle kernel paging request at 0000008f7e848020
IP: [<000000007dadb6a9>] 0x7dadb6a8
PGD 0
Oops: 0000 [#1] SMP
Modules linked in:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.11.0-medusa-00038-gd2f7cbe #821
Hardware name: SGI UV2000/ROMLEY, BIOS SGI UV 2000/3000 series BIOS 01/15/2013
task: ffffffff817ae400 ti: ffffffff8179e000 task.ti: ffffffff8179e000
RIP: 0010:[<000000007dadb6a9>] [<000000007dadb6a9>] 0x7dadb6a8
RSP: 0000:ffffffff8179fd90 EFLAGS: 00010202
RAX: 000000007d9b8e01 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 000000007db074f8 RSI: 000000007d9b8e18 RDI: 0000008f7e848000
RBP: 000000007db074f8 R08: 0000000000000001 R09: 0000008f7e848000
R10: 0000000000000030 R11: ffff880ffffda000 R12: 8000000000000000
R13: 000077ff80000000 R14: ffff888f7e848000 R15: 000000000009b000
FS: 0000000000000000(0000) GS:ffff880fffc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000008f7e848020 CR3: 000000000009b000 CR4: 00000000000406b0
Stack:
fffffffef6000000 0000000000000000 0000000000000000 80000000000001e3
0000000000000030 000000007dadd540 0000000000001f20 0000000060000202
000000007d9b8da0 000000007daf8c6b ffffffff810fd2bc 00000000000000d0
Call Trace:
[<ffffffff810fd2bc>] ? cache_grow+0x1e5/0x236
[<ffffffff8103adac>] ? efi_call4+0x6c/0xf0
[<ffffffff8186452f>] ? efi_enter_virtual_mode+0x1ac/0x328
[<ffffffff8184de98>] ? start_kernel+0x35b/0x3ed
[<ffffffff8184d950>] ? repair_env_string+0x60/0x60
[<ffffffff8184d479>] ? x86_64_start_reservations+0x2e/0x30
[<ffffffff8184d5a3>] ? x86_64_start_kernel+0x128/0x12f
Code: Bad RIP value.
RIP [<000000007dadb6a9>] 0x7dadb6a8
RSP <ffffffff8179fd90>
CR2: 0000008f7e848020
Let me know what other information you need and I'll get it to you ASAP.
Thanks!
- Alex
next prev parent reply other threads:[~2014-02-05 21:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52E2ADB1.2030007@zytor.com>
[not found] ` <20140124183730.GC11788@pd.tnic>
[not found] ` <20140124184842.GD11788@pd.tnic>
[not found] ` <20140124191709.GT18196@sgi.com>
[not found] ` <20140127222129.GK6839@pd.tnic>
[not found] ` <20140128110552.GA815@pd.tnic>
[not found] ` <20140128200754.GZ18196@sgi.com>
[not found] ` <20140128225905.GN815@pd.tnic>
[not found] ` <20140128234036.GB18196@sgi.com>
[not found] ` <20140129141822.GC24887@pd.tnic>
2014-01-30 22:19 ` [BUG] Linux 3.14 fails to boot with new EFI changes Alex Thorlton
2014-01-30 22:23 ` H. Peter Anvin
2014-01-31 10:07 ` Borislav Petkov
[not found] ` <20140131100722.GA21873-fF5Pk5pvG8Y@public.gmane.org>
2014-01-31 14:02 ` Russ Anderson
2014-01-31 14:02 ` Russ Anderson
[not found] ` <20140131140220.GC22498-sJ/iWh9BUns@public.gmane.org>
2014-01-31 14:23 ` Borislav Petkov
2014-01-31 14:23 ` Borislav Petkov
[not found] ` <20140131142318.GC21873-fF5Pk5pvG8Y@public.gmane.org>
2014-01-31 14:36 ` Borislav Petkov
2014-01-31 14:36 ` Borislav Petkov
2014-02-05 21:45 ` Alex Thorlton [this message]
2014-02-05 21:45 ` Alex Thorlton
[not found] ` <20140205214536.GT3034-sJ/iWh9BUns@public.gmane.org>
2014-02-05 23:15 ` Borislav Petkov
2014-02-05 23:15 ` Borislav Petkov
[not found] ` <20140205231540.GB6364-fF5Pk5pvG8Y@public.gmane.org>
2014-02-11 22:19 ` Alex Thorlton
2014-02-11 22:19 ` Alex Thorlton
[not found] ` <20140211221903.GG27648-sJ/iWh9BUns@public.gmane.org>
2014-02-11 22:36 ` Borislav Petkov
2014-02-11 22:36 ` Borislav Petkov
[not found] ` <20140130221950.GJ3105-sJ/iWh9BUns@public.gmane.org>
2014-01-31 8:04 ` Matt Fleming
2014-01-31 8:04 ` Matt Fleming
[not found] ` <20140131080428.GA29136-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-01-31 13:53 ` Russ Anderson
2014-01-31 13:53 ` Russ Anderson
2014-01-23 22:11 Alex Thorlton
2014-01-23 22:48 ` Borislav Petkov
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=20140205214536.GT3034@sgi.com \
--to=athorlton-sj/iwh9buns@public.gmane.org \
--cc=bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org \
--cc=rja-sJ/iWh9BUns@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.