From: lists@ssl-mail.com
To: Jan Beulich <JBeulich@suse.com>
Cc: Juergen Gross <JGross@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.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, 03 Aug 2016 06:33:44 -0700 [thread overview]
Message-ID: <1470231224.410832.684828113.540D90BC@webmail.messagingengine.com> (raw)
In-Reply-To: <57A1CF1A020000780010214F@prv-mh.provo.novell.com>
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.
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.
[ 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:06:54] RFLAGS: 0000000000010202 CONTEXT: hypervisor (d0v0)
(XEN) [2016-08-03 13:06:54] rax: 000000009e746340 rbx: 0000000000000000 rcx: 0000000000000000
(XEN) [2016-08-03 13:06:54] rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000000000000
(XEN) [2016-08-03 13:06:54] rbp: 0000000000000000 rsp: ffff83008ce27dc0 r8: 0000000000000000
(XEN) [2016-08-03 13:06:54] r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) [2016-08-03 13:06:54] r12: 0000000000000000 r13: 0000000000000cf9 r14: 0000000000000065
(XEN) [2016-08-03 13:06:54] r15: ffff830000000000 cr0: 0000000080050033 cr4: 00000000001526e0
(XEN) [2016-08-03 13:06:54] cr3: 000000084b4e5000 cr2: 000000009e746340
(XEN) [2016-08-03 13:06:54] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
(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:
(XEN) [2016-08-03 13:06:55] 000000009efe42f6 0000000000000cf9 ffff82d08022f741 efff000000000000
(XEN) [2016-08-03 13:06:55] ffff82d0807fe000 000000084b4e5000 ffff82d08022f94a 000000085da98000
(XEN) [2016-08-03 13:06:55] 0000000000000000 0000000000000007 000000000000e008 0000000000000292
Initializing Adapter 0
...
XEN) [2016-08-03 13:30:44] Xen call trace:
(XEN) [2016-08-03 13:30:44] [<000000009e7463c6>] 000000009e7463c6
(XEN) [2016-08-03 13:30:44] [<ffff82d0801670f6>] i387.c#_vcpu_save_fpu+0x86/0x190
(XEN) [2016-08-03 13:30:44] [<ffff82d08022f94a>] efi_reset_system+0x3a/0x60
(XEN) [2016-08-03 13:30:44] [<ffff82d08018bcc8>] machine_restart+0x208/0x2d0
(XEN) [2016-08-03 13:30:44] [<ffff82d08012bf8d>] hwdom_shutdown+0x7d/0xf0
(XEN) [2016-08-03 13:30:44] [<ffff82d080105871>] domain_shutdown+0xf1/0x100
(XEN) [2016-08-03 13:30:44] [<ffff82d08012b042>] do_sched_op+0x1b2/0x460
(XEN) [2016-08-03 13:30:44] [<ffff82d08022c65b>] lstar_enter+0x9b/0xa0
(XEN) [2016-08-03 13:30:44]
(XEN) [2016-08-03 13:30:44]
(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] ****************************************
And still reboots.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-03 13:33 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 [this message]
2016-08-03 13:57 ` Jan Beulich
2016-08-03 14:03 ` Andrew Cooper
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=1470231224.410832.684828113.540D90BC@webmail.messagingengine.com \
--to=lists@ssl-mail.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=daniel.kiper@oracle.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.