From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, lists@ssl-mail.com
Cc: Juergen Gross <JGross@suse.com>,
Daniel Kiper <daniel.kiper@oracle.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
xen-devel@lists.xen.org
Subject: Re: Xen 4.7.0 boot PANIC on kernel 4.7.0-4 + UEFI ?
Date: Wed, 3 Aug 2016 15:03:42 +0100 [thread overview]
Message-ID: <9d54e28d-7d6d-e38b-5d4d-5ab6657b9c32@citrix.com> (raw)
In-Reply-To: <57A2145B0200007800102460@prv-mh.provo.novell.com>
On 03/08/16 14:57, Jan Beulich wrote:
>>>> On 03.08.16 at 15:33, <lists@ssl-mail.com> wrote:
>> On Wed, Aug 3, 2016, at 02:01 AM, Jan Beulich wrote:
>>> Thanks. Does the use of /mapbs really matter for booting? I was
>>> assuming it would be relevant only for shutdown/reboot?
>> It has no effect on boot. With or without the "/mapbs" it boots Xen OK.
> As expected.
>
>> Without the "/mapbs" the system used to crash on reboot, but still continued
>> with a reboot. Reboot with the "/mapbs" was OK.
>>
>> Now, even with the "/mapbs" the system crashes on reboot.
> But afaict in a different way:
>
>> [ 196.052042] reboot: Restarting system
>> (XEN) [2016-08-03 13:06:54] Hardware Dom0 shutdown: rebooting machine
>> (XEN) [2016-08-03 13:06:54] APIC error on CPU0: 40(00)
>> (XEN) [2016-08-03 13:06:54] ----[ Xen-4.7.0_09-454 x86_64 debug=n Not tainted ]----
>> (XEN) [2016-08-03 13:06:54] CPU: 0
>> (XEN) [2016-08-03 13:06:54] RIP: e008:[<000000009e746340>] 000000009e746340
>> [...]
>> (XEN) [2016-08-03 13:30:44] ****************************************
>> (XEN) [2016-08-03 13:30:44] Panic on CPU 0:
>> (XEN) [2016-08-03 13:30:44] GENERAL PROTECTION FAULT
>> (XEN) [2016-08-03 13:30:44] [error_code=0000]
>> (XEN) [2016-08-03 13:30:44] ****************************************
> A #GP fault in firmware code. Not much we can do about, I'm afraid,
> except for having you go with one of the mentioned workarounds
> (and perhaps getting in touch with the BIOS vendor).
One bit you snipped was
(XEN) [2016-08-03 13:06:54] Xen code around <000000009e746340>
(000000009e746340):
(XEN) [2016-08-03 13:06:54] 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
(XEN) [2016-08-03 13:06:54] Xen stack trace from rsp=ffff83008ce27dc0:
which shows that the EFI firmware has ended up in a block of zeroes.
This clearly isn't conducive to its overall health.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-03 14:03 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 23:32 Xen 4.7.0 boot PANIC on kernel 4.7.0-4 + UEFI ? lists
2016-07-27 1:43 ` lists
2016-07-27 15:50 ` Andrew Cooper
2016-07-27 16:21 ` lists
2016-07-27 16:34 ` Andrew Cooper
2016-07-27 16:54 ` lists
2016-07-27 16:56 ` Andrew Cooper
2016-07-27 18:22 ` lists
2016-07-27 18:28 ` Andrew Cooper
2016-07-27 18:36 ` lists
2016-07-28 0:28 ` lists
2016-07-28 0:53 ` lists
2016-07-28 1:09 ` Konrad Rzeszutek Wilk
2016-07-28 17:20 ` lists
2016-07-28 18:21 ` Daniel Kiper
2016-07-28 18:25 ` lists
2016-07-28 19:05 ` Daniel Kiper
2016-07-28 19:06 ` lists
2016-07-29 14:36 ` lists
2016-07-29 15:42 ` Konrad Rzeszutek Wilk
2016-07-29 15:57 ` lists
2016-07-29 16:03 ` Konrad Rzeszutek Wilk
2016-07-29 16:12 ` lists
2016-08-01 20:11 ` lists
2016-08-01 22:27 ` [BUG] " lists
2016-08-02 6:57 ` Jan Beulich
2016-08-02 13:16 ` lists
2016-08-02 19:02 ` lists
2016-08-03 9:01 ` Jan Beulich
2016-08-03 13:33 ` lists
2016-08-03 13:57 ` Jan Beulich
2016-08-03 14:03 ` Andrew Cooper [this message]
2016-08-03 14:50 ` lists
2016-08-03 15:41 ` lists
2016-08-04 15:21 ` lists
2016-07-28 14:09 ` Vitaly Kuznetsov
2016-07-28 14:18 ` lists
2016-07-27 18:33 ` Juergen Gross
2016-08-02 6:36 ` Jan Beulich
2016-08-02 13:13 ` lists
2016-08-02 13:38 ` Jan Beulich
2016-08-02 13:54 ` lists
2016-08-02 14:13 ` Jan Beulich
2016-08-02 14:25 ` lists
2016-08-02 14:50 ` Jan Beulich
2016-08-02 15:04 ` lists
2016-08-02 15:55 ` Jan Beulich
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=9d54e28d-7d6d-e38b-5d4d-5ab6657b9c32@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=daniel.kiper@oracle.com \
--cc=lists@ssl-mail.com \
--cc=vkuznets@redhat.com \
--cc=xen-devel@lists.xen.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.