From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: Madper Xie <cxie-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Matt Fleming
<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Matthew Garrett
<matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org>,
Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>
Subject: Re: [BUG] Kernel OOPS when reboot if I set reboot=efi,{warm, cold} (and some questions :-)
Date: Mon, 13 Jan 2014 12:16:36 +0000 [thread overview]
Message-ID: <20140113121636.GA3256@console-pimps.org> (raw)
In-Reply-To: <8738l5zcfp.fsf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Fri, 03 Jan, at 04:39:38PM, Madper Xie wrote:
> Howdy Folks,
> Happy new yeah, happy new bug!
> With a uefi system, I meet following panic when reboot after I adding
> `reboot=efi,warm`
> [call trace]:
> <0>[ 698.736637] reboot: Restarting system
> <5>[ 698.737407] reboot: machine restart
> <1>[ 698.738399] BUG: unable to handle kernel paging request at 00000000ded53e60
> <1>[ 698.738924] IP: [<ffff8800dedb946d>] 0xffff8800dedb946d
> <4>[ 698.739408] PGD 0
> <4>[ 698.739868] Oops: 0000 [#1] SMP
[...]
> According to Call Trace, the panic happen when call ResetSystem() which
> is a uefi run time service. It's seems a asm code in efi_stub_64.S
> I disassembly it with crash got following outputs:
> crash> dis efi_call4
> 0xffffffff810518f0 <efi_call4>: mov %rsp,%rax
> [ ... ]
> 0xffffffff81051918 <efi_call4+40>: movaps %xmm3,0x30(%rsp)
> 0xffffffff8105191d <efi_call4+45>: movaps %xmm4,0x20(%rsp)
> 0xffffffff81051922 <efi_call4+50>: movaps %xmm5,0x10(%rsp)
> 0xffffffff81051927 <efi_call4+55>: sub $0x20,%rsp
> [ ... ]
>
> So it seems the panic happen when SAVE_XMM? Does SAVE_XMM will trigger
> paging? (`unable to handle kernel paging request at 00000000ded53e60`)
No, the crash is happening within the ResetSystem() runtime service.
Checkout the RIP, it's in the direct mapping region (0xffff8800.....).
> in case it's a hardware special issue: My testbed is a DELL xps x8500
> And I'll try to test it on another uefi system.
It looks like your firmware is trying to access physical addresses. Can
you build a kernel from the 'next' branch at,
git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git
That branch includes Borislav's 1:1 mapping work and may fix your issue.
--
Matt Fleming, Intel Open Source Technology Center
prev parent reply other threads:[~2014-01-13 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 8:39 [BUG] Kernel OOPS when reboot if I set reboot=efi,{warm, cold} (and some questions :-) Madper Xie
[not found] ` <8738l5zcfp.fsf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-01-13 12:16 ` Matt Fleming [this message]
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=20140113121636.GA3256@console-pimps.org \
--to=matt-hnk1s37rvnbexh+ff434mdi2o/jbrioy@public.gmane.org \
--cc=bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org \
--cc=cxie-H+wXaHxf7aLQT0dZR+AlfA@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=matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@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;
as well as URLs for NNTP newsgroup(s).