[Bug 956526] New: PANIC on Xen Dom0 restart
http://bugzilla.suse.com/show_bug.cgi?id=956526 Bug ID: 956526 Summary: PANIC on Xen Dom0 restart Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Critical Priority: P5 - None Component: Xen Assignee: xen-bugs@suse.de Reporter: 9b3e05a5@opayq.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I've a Xen Dom0 running on x86_64/EFI hardware. Distro is Leap, lsb_release -rd Description: openSUSE Leap 42.1 (x86_64) Release: 42.1 Kernel's pvops from Kernel:Stable uname -rm 4.3.0-17.g6a48ac7-default x86_64 Xen's from Virtualization rpm -qa | grep -i ^xen xen-libs-4.6.0_04-398.1.x86_64 xen-4.6.0_04-398.1.x86_64 xen-tools-4.6.0_04-398.1.x86_64 Dom0/DomU are up xl list Name ID Mem VCPUs State Time(s) Domain-0 0 3069 1 r----- 29.7 teste 1 1024 1 -b---- 5.0 At reboot shutdown -r now serial console output shows the following TRACE ... [ OK ] Reached target Shutdown. dracut Warning: Killing all remaining processes mdadm: stopped /dev/md4 mdadm: stopped /dev/md3 mdadm: stopped /dev/md2 mdadm: stopped /dev/md0 mdadm: stopped /dev/md1 Rebooting. [ 485.124984] reboot: Restarting system (XEN) [2015-11-24 19:40:28] Hardware Dom0 shutdown: rebooting machine (XEN) [2015-11-24 19:40:28] APIC error on CPU0: 40(00) (XEN) [2015-11-24 19:40:28] ----[ Xen-4.6.0_04-398 x86_64 debug=n Tainted: C ]---- (XEN) [2015-11-24 19:40:28] CPU: 0 (XEN) [2015-11-24 19:40:28] RIP: e008:[<000000009e557340>] 000000009e557340 (XEN) [2015-11-24 19:40:28] RFLAGS: 0000000000010202 CONTEXT: hypervisor (d0v0) (XEN) [2015-11-24 19:40:28] rax: 000000009e557340 rbx: 0000000000000000 rcx: 0000000000000000 (XEN) [2015-11-24 19:40:28] rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000000000000 (XEN) [2015-11-24 19:40:28] rbp: 0000000000000000 rsp: ffff83008cadfdc0 r8: 0000000000000000 (XEN) [2015-11-24 19:40:28] r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 (XEN) [2015-11-24 19:40:28] r12: 0000000000000000 r13: 0000000000000cf9 r14: 0000000000000065 (XEN) [2015-11-24 19:40:28] r15: ffff830000000000 cr0: 0000000080050033 cr4: 00000000001526e0 (XEN) [2015-11-24 19:40:28] cr3: 000000084518c000 cr2: 000000009e557340 (XEN) [2015-11-24 19:40:28] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) [2015-11-24 19:40:28] Xen stack trace from rsp=ffff83008cadfdc0: (XEN) [2015-11-24 19:40:28] 000000009efe42f6 0000000000000065 ffff82d08022b8ca efff000000000000 (XEN) [2015-11-24 19:40:28] ffff82d080269000 000000084518c000 ffff82d08022bada 000000085d46e000 (XEN) [2015-11-24 19:40:28] 0000000000000000 0000000000152660 000000000000e008 0000000000000292 (XEN) [2015-11-24 19:40:28] 0000000000000000 00000000fffffffe ffff82d0801821e8 ffff82d08038f9c0 (XEN) [2015-11-24 19:40:28] 0000000000000010 000083008cadfe98 0000000000000000 00000070f406f3d2 (XEN) [2015-11-24 19:40:28] 0000000000000001 0000000000000001 ffff83084514b000 ffff83084514b158 (XEN) [2015-11-24 19:40:28] 0000000000000002 00000000fee1dead ffff82d08012a03f ffff83008cadff18 (XEN) [2015-11-24 19:40:28] ffff82d0801058a1 0000000000000000 0000000000000000 ffff880094a3fdc0 (XEN) [2015-11-24 19:40:28] ffffffff81f13cc0 ffffffff81e4d460 ffff82d080129172 0000000100000000 (XEN) [2015-11-24 19:40:28] 0000000000000000 ffff83008da9d000 ffff880094a3fd98 ffffffff81f13cc0 (XEN) [2015-11-24 19:40:28] ffff83008da9d000 ffff880094a3fdc0 ffff82d080228070 ffffc9004081ade0 (XEN) [2015-11-24 19:40:28] ffff88011c47fe18 ffffc9004081ae60 ffffc9004081ae0c ffff880094a3fdc0 (XEN) [2015-11-24 19:40:28] 0000000000000200 0000000000000216 0000000000000008 0000000000000001 (XEN) [2015-11-24 19:40:28] 0000000000000000 000000000000001d ffffffff810013aa 0000000000000200 (XEN) [2015-11-24 19:40:28] ffff880094a3fdac 0000000000000002 0001010000000000 ffffffff810013aa (XEN) [2015-11-24 19:40:28] 000000000000e033 0000000000000216 ffff880094a3fd90 000000000000e02b (XEN) [2015-11-24 19:40:28] 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) [2015-11-24 19:40:28] 0000000000000000 ffff83008da9d000 0000000000000000 0000000000000000 (XEN) [2015-11-24 19:40:28] Xen call trace: (XEN) [2015-11-24 19:40:28] [<000000009e557340>] 000000009e557340 (XEN) [2015-11-24 19:40:28] [<ffff82d08022b8ca>] efi_rs_enter+0xfa/0x120 (XEN) [2015-11-24 19:40:28] [<ffff82d08022bada>] efi_reset_system+0x3a/0x60 (XEN) [2015-11-24 19:40:28] [<ffff82d0801821e8>] machine_restart+0x208/0x2d0 (XEN) [2015-11-24 19:40:28] [<ffff82d08012a03f>] hwdom_shutdown+0xbf/0xc0 (XEN) [2015-11-24 19:40:28] [<ffff82d0801058a1>] domain_shutdown+0xf1/0x100 (XEN) [2015-11-24 19:40:28] [<ffff82d080129172>] do_sched_op+0x1d2/0x410 (XEN) [2015-11-24 19:40:28] [<ffff82d080228070>] lstar_enter+0xa0/0xa5 (XEN) [2015-11-24 19:40:28] (XEN) [2015-11-24 19:40:28] Pagetable walk from 000000009e557340: (XEN) [2015-11-24 19:40:28] L4[0x000] = 000000084518b063 ffffffffffffffff (XEN) [2015-11-24 19:40:28] L3[0x002] = 000000008ca7c063 ffffffffffffffff (XEN) [2015-11-24 19:40:28] L2[0x0f2] = 000000009e3ff063 ffffffffffffffff (XEN) [2015-11-24 19:40:28] L1[0x157] = 800000009e557163 ffffffffffffffff (XEN) [2015-11-24 19:40:28] (XEN) [2015-11-24 19:40:28] **************************************** (XEN) [2015-11-24 19:40:28] Panic on CPU 0: (XEN) [2015-11-24 19:40:28] FATAL PAGE FAULT (XEN) [2015-11-24 19:40:28] [error_code=0011] (XEN) [2015-11-24 19:40:28] Faulting linear address: 000000009e557340 (XEN) [2015-11-24 19:40:28] **************************************** (XEN) [2015-11-24 19:40:28] (XEN) [2015-11-24 19:40:28] Reboot in five seconds... Reboot proceeds & completes, and there _seem_, yet, to be no persistent effects on rebooted system. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c1 --- Comment #1 from boo35 boo35 <9b3e05a5@opayq.com> --- in #xen, suggestion's made to pass /mapbs to xen.efi exec. IIUC, can be done at EFI Shell>, but not clear how that's done in the grub2/multiboot config. Here's a relevant thread: http://lists.xen.org/archives/html/xen-devel/2015-07/msg05138.html and the original mapbs support commit @upstream: http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=cbf41e0514389b65f545e1b1... fwiw, the thread author states "I had to give up on grub" ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c2 --- Comment #2 from boo35 boo35 <9b3e05a5@opayq.com> --- *Manually* editing auto-generated grub2 config, edit /boot/grub2/grub.cfg ... ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### menuentry 'openSUSE Leap 42.1, with Xen hypervisor' --class opensuse --class gnu-linux --class gnu --class os --class xen $menuentry_id_option 'xen-gnulinux-simple-4716053b-39da-4cc1-a7ce-72171b862357' { echo 'Loading Xen 4.6.0_04-398 with Linux 4.3.0-17.g6a48ac7-default ...' - chainloader $cmdpath/xen-4.6.0_04-398.efi xen-4.6.0_04-398.efi config.1 + chainloader $cmdpath/xen-4.6.0_04-398.efi xen-4.6.0_04-398.efi config.1 /mapbs } submenu 'Advanced options for openSUSE Leap 42.1 (with Xen hypervisor)' $menuentry_id_option 'gnulinux-advanced-4716053b-39da-4cc1-a7ce-72171b862357' { submenu 'Xen hypervisor, version 4.6.0_04-398' $menuentry_id_option 'xen-hypervisor-4.6.0_04-398-4716053b-39da-4cc1-a7ce-72171b862357' { menuentry 'openSUSE Leap 42.1, with Xen 4.6.0_04-398 and Linux 4.3.0-17.g6a48ac7-default' --class opensuse --class gnu-linux --class gnu --class os --class xen $menuentry_id_option 'xen-gnulinux-4.3.0-17.g6a48ac7-default-advanced-4716053b-39da-4cc1-a7ce-72171b862357' { echo 'Loading Xen 4.6.0_04-398 with Linux 4.3.0-17.g6a48ac7-default ...' - chainloader $cmdpath/xen-4.6.0_04-398.efi xen-4.6.0_04-398.efi config.2 + chainloader $cmdpath/xen-4.6.0_04-398.efi xen-4.6.0_04-398.efi config.2 /mapbs } } } ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/20_memtest86+ ### ... appears to remedy the PANIC, but leaves an error; @ serial console on reboot, shutdown -r now ... [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ 262.745431] watchdog watchdog0: watchdog did not stop! [ 273.525393] watchdog watchdog0: watchdog did not stop! dracut Warning: Killing all remaining processes mdadm: stopped /dev/md4 mdadm: stopped /dev/md2 mdadm: stopped /dev/md3 mdadm: stopped /dev/md0 mdadm: stopped /dev/md1 Rebooting. [ 274.142642] reboot: Restarting system (XEN) [2015-11-25 15:28:33] Hardware Dom0 shutdown: rebooting machine (XEN) [2015-11-25 15:28:33] APIC error on CPU0: 40(00) (XEN) [2015-11-25 15:28:33] EFI: could not reset system (0) (XEN) [2015-11-25 15:28:33] Resetting with ACPI MEMORY or I/O RESET_REG. (restarts) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c3 --- Comment #3 from boo35 boo35 <9b3e05a5@opayq.com> --- (In reply to boo35 boo35 from comment #2)
(XEN) [2015-11-25 15:28:33] EFI: could not reset system (0)
for ref, this^^ appears to originate https://github.com/xenserver/xen-4.6/blob/23d01fc3768e72e82a40cbe781409856d6... line 162, ... void efi_reset_system(bool_t warm) { EFI_STATUS status; unsigned long cr3 = efi_rs_enter(); if ( !cr3 ) return; status = efi_rs->ResetSystem(warm ? EfiResetWarm : EfiResetCold, EFI_SUCCESS, 0, NULL); efi_rs_leave(cr3); 162 printk(XENLOG_WARNING "EFI: could not reset system (%#lx)\n", status); } ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c4 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com, | |carnold@suse.com, | |jslaby@suse.com, | |mchang@suse.com, | |ohering@suse.com, | |rw@suse.com --- Comment #4 from boo35 boo35 <9b3e05a5@opayq.com> --- Chatting in #grub, adding of these efi flags to auto-generated grub2 config is not currently supported, either in Opensuse's grub implementation, or upstream's. Since Xen on UEFI is a reality, as are these EFI flags for dealing with mainstream EFI firmware issues currently in the wild, there needs to be some mechanism to add these flags to boot config. Similar to kernel flags added to kernel cmd line, Xen flags added to xen options line, etc. Ideally NOT manually, but via grub config autogeneration. I could possibly see something added to efibootmgr as an alternative. Frankly, a virtual sit down between devs @ Grub, Xen & a distro-or-three would go a long way to saving a lot of time all around. Perpetuating differences between up- & down-stream bootloader behavior, particularly w.r.t. Xen & EFI is wasted effort. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526
http://bugzilla.suse.com/show_bug.cgi?id=956526#c5
Andrei Borzenkov
in #xen, suggestion's made to pass /mapbs to xen.efi exec.
I assume the original patch worked at some point and later Xen version has some changes that now require /mapbs. So the actual question is how to detect whether we need /mapbs (or better - do we support in Leap installing both Xen version that needs it and version that does not need it). If we support only Xen that requires /mapbs, fix is easy. Charles, you are listed as Xen bugowner, so asking you here. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526
http://bugzilla.suse.com/show_bug.cgi?id=956526#c6
--- Comment #6 from Michael Chang
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c7 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(carnold@suse.com) |needinfo? --- Comment #7 from boo35 boo35 <9b3e05a5@opayq.com> --- Note that there are other EFI flags that are available/useful. E.g., in the Xen thread alone are mentioned /basevideo, /mapbs, noexitboot & /query I'd guess a longer list can be extracted from the tiaonocore sources. I'm not sure which vendors are using the tiaonocore UEFI vs. 'other'. Although auto-detection may be possible, for which failure? Only one? More? Trying to identify all cases of failure, and all possible flag-combo solutions isn't a tenable solution. The flexibility to have the enduser diagnose (nrokennesss, performances issue, etc), and add flags to config -- as is currently often done for both Kernel & Xen is imo preferable. The "SUSE_EFI_XEN_LOADER_CMDLINE" string seems a simple enough approach. If/when grub@suse and grub@upstream coordinate, pushing that cmdline upstream makes sense. Of course, getting EFI fixed is the best solution; I've already contacted the H/W vendor, and they're working on this issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526
Charles Arnold
http://bugzilla.suse.com/show_bug.cgi?id=956526
http://bugzilla.suse.com/show_bug.cgi?id=956526#c8
Jan Beulich
http://bugzilla.suse.com/show_bug.cgi?id=956526
Jan Beulich
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c9 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(9b3e05a5@opayq.co | |m) | --- Comment #9 from boo35 boo35 <9b3e05a5@opayq.com> ---
I wonder whether the component is still set correctly
maybe, or partly ?
Is this still a report against Xen crashing
The system panics on restart only when Xen's loaded; no Xen, no PANIC That seems a Xen issue.
or is it understood that firmware is broken
It's strongly suspected. The symptoms, discussed in #xen and on Xen ML seem to indicate -- and the /mapbs flag eliminates the PANIC. But, the (XEN) [2015-11-25 15:28:33] EFI: could not reset system (0) remains. Is that firmware, kernel or xen? I don't know ...
and things now really only revolve around how a suitable workaround option can be passed to xen.efi?
In any case -- or more correctly, for the *general* case -- EFI flag options are available, and should be able to be added, whether it's for a specific EFI workaround, or other functionality.
In the former case, we'd need a complete hypervisor log (at "loglvl=all"),
with, or without the /mapbs added? I.e., in the PANIC case, the EFI error only case, or both?
while in the latter case I'd suggest changing component and assignee.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526
http://bugzilla.suse.com/show_bug.cgi?id=956526#c10
Jan Beulich
Is this still a report against Xen crashing
The system panics on restart only when Xen's loaded; no Xen, no PANIC
That seems a Xen issue.
No, it's a firmware issue. The fact that Linux doesn't call certain runtime services functions (because of there being so many bugs in the wild) doesn't make it a Xen bug if the firmware writers don't produce usable code/data. As you've seen we've added, over time, quite a number of workaround options. Another one for you to try would btw be "efi=no-rs" (which goes on the ordinary command line, and hence should avoid all the grub related issues).
or is it understood that firmware is broken
It's strongly suspected. The symptoms, discussed in #xen and on Xen ML seem to indicate -- and the /mapbs flag eliminates the PANIC.
But, the
(XEN) [2015-11-25 15:28:33] EFI: could not reset system (0)
remains.
Is that firmware, kernel or xen? I don't know ...
Another runtime service function that - at the first glance - doesn't do what it's supposed to. But I can't tell for sure without some more detail, and I'd really like to ask to have one issue per bug report only.
and things now really only revolve around how a suitable workaround option can be passed to xen.efi?
In any case -- or more correctly, for the *general* case -- EFI flag options are available, and should be able to be added, whether it's for a specific EFI workaround, or other functionality.
Agreed. But again - you need to settle which issue to track here, and which one(s) to open further reports for.
In the former case, we'd need a complete hypervisor log (at "loglvl=all"),
with, or without the /mapbs added? I.e., in the PANIC case, the EFI error only case, or both?
Since we're talking about the panic case here, I suppose you'd want to omit the /mapbs. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c11 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jbeulich@suse.com Flags| |needinfo?(jbeulich@suse.com | |) --- Comment #11 from boo35 boo35 <9b3e05a5@opayq.com> ---
I'd really like to ask to have one issue per bug report only.
I'll split this up, first. Suggestions as to WHAT/where to split it will help; I'll create the bugs. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526
http://bugzilla.suse.com/show_bug.cgi?id=956526#c12
Jan Beulich
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c13 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|PANIC on Xen Dom0 restart |hypervisor PANIC on Xen | |Dom0 restart; firmware | |workaround required Flags|needinfo?(9b3e05a5@opayq.co | |m) | --- Comment #13 from boo35 boo35 <9b3e05a5@opayq.com> --- (In reply to Jan Beulich from comment #12)
- a hypervisor crash -> here - a grub problem -> split: https://bugzilla.suse.com/show_bug.cgi?id=957383 - a reboot issue -> not yet ...
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c14 --- Comment #14 from boo35 boo35 <9b3e05a5@opayq.com> --- (In reply to Jan Beulich from comment #10)
No, it's a firmware issue. The fact that Linux doesn't call certain runtime services functions (because of there being so many bugs in the wild) doesn't make it a Xen bug if the firmware writers don't produce usable code/data. As you've seen we've added, over time, quite a number of workaround options. Another one for you to try would btw be "efi=no-rs" (which goes on the ordinary command line, and hence should avoid all the grub related issues).
Avoid, or simply mute? I'd rather not cloak a real problem ... I've found the commits for both the /mapbs efi=no-rs 'fix' options. I'm not clear on what they do relative to one another. Is one 'better' here than the other, or should both be in place? Or, simply a matter of 'whatever works' to eliminate the crash? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526
http://bugzilla.suse.com/show_bug.cgi?id=956526#c15
Jan Beulich
(In reply to Jan Beulich from comment #10)
No, it's a firmware issue. The fact that Linux doesn't call certain runtime services functions (because of there being so many bugs in the wild) doesn't make it a Xen bug if the firmware writers don't produce usable code/data. As you've seen we've added, over time, quite a number of workaround options. Another one for you to try would btw be "efi=no-rs" (which goes on the ordinary command line, and hence should avoid all the grub related issues).
Avoid, or simply mute?
Whatever term you prefer.
I've found the commits for both the
/mapbs efi=no-rs
'fix' options. I'm not clear on what they do relative to one another. Is one 'better' here than the other, or should both be in place?
Which one to use depends on the kind of brokenness of your firmware. I consider /mapbs quite ugly, so would generally recommend to prefer efi=no-rs. Now that you settled on which issue to deal with here, please note that there was a complete log requested in #8 for that case. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c16 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(9b3e05a5@opayq.co | |m) | --- Comment #16 from boo35 boo35 <9b3e05a5@opayq.com> --- Set loglvl=all Removed /mapbs efi=no-rs Exec shutdown -r now @ serial console ... Xen 4.6.0_04-398 (c/s ) EFI loader Using configuration file 'xen-4.6.0_04-398.cfg' vmlinuz-4.3.0-20.g82de429-default: 0x000000008c08c000-0x000000008c65ee60 initrd-4.3.0-20.g82de429-default: 0x000000008b121000-0x000000008c08b270 0x0000:0x00:0x19.0x0: ROM: 0x10000 bytes at 0x92892018 0x0000:0x04:0x00.0x0: ROM: 0x8000 bytes at 0x92889018 0x0000:0x10:0x00.0x0: ROM: 0x10800 bytes at 0x92871018 __ __ _ _ __ ___ ___ _ _ _____ ___ ___ \ \/ /___ _ __ | || | / /_ / _ \ / _ \| || | |___ // _ \ ( _ ) \ // _ \ '_ \ | || |_| '_ \| | | | | | | | || |_ __ |_ \ (_) |/ _ \ / \ __/ | | | |__ _| (_) | |_| | | |_| |__ _|__|__) \__, | (_) | /_/\_\___|_| |_| |_|(_)___(_)___/___\___/ |_| |____/ /_/ \___/ |_____| (XEN) Xen version 4.6.0_04-398 (abuild@suse.de) (gcc (SUSE Linux) 4.8.5) debug=n Tue Nov 24 15:44:57 UTC 2015 (XEN) Latest ChangeSet: (XEN) Console output is synchronous. (XEN) Bootloader: EFI (XEN) Command line: dom0_mem=3072M,max:3072M dom0_max_vcpus=1 dom0_vcpus_pin=true cpuidle=1 cpufreq=xen clocksource=hpet iommu=verbose sched=credit vga=gfx-1920x1080x16 com1=115200,8n1,pci (XEN) Video information: (XEN) VGA is graphics mode 800x600, 32 bpp (XEN) Disc information: (XEN) Found 0 MBR signatures (XEN) Found 6 EDD information structures (XEN) EFI RAM map: (XEN) 0000000000000000 - 0000000000058000 (usable) (XEN) 0000000000058000 - 0000000000059000 (reserved) (XEN) 0000000000059000 - 000000000009f000 (usable) (XEN) 000000000009f000 - 00000000000a0000 (reserved) (XEN) 0000000000100000 - 000000008da96000 (usable) (XEN) 000000008da96000 - 000000008da9d000 (ACPI NVS) (XEN) 000000008da9d000 - 000000008e3e3000 (usable) (XEN) 000000008e3e3000 - 000000008e7ea000 (reserved) (XEN) 000000008e7ea000 - 000000009e5b1000 (usable) (XEN) 000000009e5b1000 - 000000009e62e000 (reserved) (XEN) 000000009e62e000 - 000000009e675000 (usable) (XEN) 000000009e675000 - 000000009e7a9000 (ACPI NVS) (XEN) 000000009e7a9000 - 000000009efff000 (reserved) (XEN) 000000009efff000 - 000000009f000000 (usable) (XEN) 00000000f0000000 - 00000000f8000000 (reserved) (XEN) 00000000fec00000 - 00000000fec01000 (reserved) (XEN) 00000000fed00000 - 00000000fed04000 (reserved) (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ff000000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 000000085e000000 (usable) (XEN) ACPI: RSDP 9E779000, 0024 (r2 SUPERM) (XEN) ACPI: XSDT 9E7790A0, 00C4 (r1 SUPERM SMCI--MB 1072009 AMI 10013) (XEN) ACPI: FACP 9E787328, 010C (r5 SUPERM SMCI--MB 1072009 AMI 10013) (XEN) ACPI: DSDT 9E779200, E121 (r2 SUPERM SMCI--MB 0 INTL 20120711) (XEN) ACPI: FACS 9E7A8F80, 0040 (XEN) ACPI: APIC 9E787438, 0072 (r3 SUPERM SMCI--MB 1072009 AMI 10013) (XEN) ACPI: FPDT 9E7874B0, 0044 (r1 SUPERM SMCI--MB 1072009 AMI 10013) (XEN) ACPI: FIDT 9E7874F8, 009C (r1 SUPERM SMCI--MB 1072009 AMI 10013) (XEN) ACPI: SSDT 9E787598, 0C7D (r2 Ther_R Ther_Rvp 1000 INTL 20120711) (XEN) ACPI: SSDT 9E788218, 0539 (r2 PmRef Cpu0Ist 3000 INTL 20051117) (XEN) ACPI: SSDT 9E788758, 0B74 (r2 CpuRef CpuSsdt 3000 INTL 20051117) (XEN) ACPI: SSDT 9E7892D0, 02DE (r2 PmRef Cpu0Tst 3000 INTL 20051117) (XEN) ACPI: SSDT 9E7895B0, 0348 (r2 PmRef ApTst 3000 INTL 20051117) (XEN) ACPI: MCFG 9E7898F8, 003C (r1 SUPERM SMCI--MB 1072009 MSFT 97) (XEN) ACPI: HPET 9E789938, 0038 (r1 SUPERM SMCI--MB 1072009 AMI. 5) (XEN) ACPI: SSDT 9E789970, 0397 (r1 SataRe SataTabl 1000 INTL 20120711) (XEN) ACPI: SSDT 9E789D08, 57F6 (r2 SaSsdt SaSsdt 3000 INTL 20120711) (XEN) ACPI: ASF! 9E78F500, 00A5 (r32 INTEL HCG 1 TFSM F4240) (XEN) ACPI: DMAR 9E78F5A8, 0080 (r1 INTEL BDW 1 INTL 1) (XEN) ACPI: EINJ 9E78F628, 0130 (r1 AMI AMI EINJ 0 0) (XEN) ACPI: ERST 9E78F758, 0230 (r1 AMIER AMI ERST 0 0) (XEN) ACPI: HEST 9E78F988, 00A8 (r1 AMI AMI HEST 0 0) (XEN) ACPI: BERT 9E78FA30, 0030 (r1 AMI AMI BERT 0 0) (XEN) ACPI: BGRT 9E78FA60, 0038 (r0 SUPERM SMCI--MB 1072009 AMI 10013) (XEN) System RAM: 32705MB (33490468kB) (XEN) Domain heap initialised (XEN) Allocated console ring of 64 KiB. (XEN) ACPI: 32/64X FACS address mismatch in FADT - 9e7a8f80/0000000000000000, using 32 (XEN) Processor #0 7:12 APIC version 21 (XEN) Processor #2 7:12 APIC version 21 (XEN) Processor #4 7:12 APIC version 21 (XEN) Processor #6 7:12 APIC version 21 (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) mapped APIC to ffff82cfff7fb000 (fee00000) (XEN) mapped IOAPIC to ffff82cfff7fa000 (fec00000) (XEN) Not enabling x2APIC (upon firmware request) (XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7 (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 3092.890 MHz processor. (XEN) Initing memory sharing. (XEN) spurious 8259A interrupt: IRQ7. (XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB. (XEN) Intel VT-d Snoop Control enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping enabled. (XEN) Intel VT-d Shared EPT tables enabled. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping enabled (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) Suppress EOI broadcast on CPU#0 (XEN) enabled ExtINT on CPU#0 (XEN) ENABLING IO-APIC IRQs (XEN) Using local APIC timer interrupts. (XEN) calibrating APIC timer ... (XEN) ..... CPU clock speed is 3092.8976 MHz. (XEN) ..... host bus clock speed is 99.7708 MHz. (XEN) ..... bus_scale = 0x662c (XEN) [2015-12-01 08:47:18] Platform timer is 14.318MHz HPET (XEN) [2015-12-01 08:47:18] VMX: Supported advanced features: (XEN) [2015-12-01 08:47:18] - APIC MMIO access virtualisation (XEN) [2015-12-01 08:47:18] - APIC TPR shadow (XEN) [2015-12-01 08:47:18] - Extended Page Tables (EPT) (XEN) [2015-12-01 08:47:18] - Virtual-Processor Identifiers (VPID) (XEN) [2015-12-01 08:47:18] - Virtual NMI (XEN) [2015-12-01 08:47:18] - MSR direct-access bitmap (XEN) [2015-12-01 08:47:18] - Unrestricted Guest (XEN) [2015-12-01 08:47:18] - VMCS shadowing (XEN) [2015-12-01 08:47:18] - VM Functions (XEN) [2015-12-01 08:47:18] HVM: ASIDs enabled. (XEN) [2015-12-01 08:47:18] HVM: VMX enabled (XEN) [2015-12-01 08:47:18] HVM: Hardware Assisted Paging (HAP) detected (XEN) [2015-12-01 08:47:18] HVM: HAP page sizes: 4kB, 2MB, 1GB (XEN) [2015-12-01 08:47:18] Suppress EOI broadcast on CPU#1 (XEN) [2015-12-01 08:47:18] masked ExtINT on CPU#1 (XEN) [2015-12-01 08:47:18] [VT-D]INTR-REMAP: Request device [0000:f0:1f.0] fault index 0, iommu reg = ffff82c0003e2000 (XEN) [2015-12-01 08:47:18] [VT-D]INTR-REMAP: reason 22 - Present field in the IRTE entry is clear (XEN) [2015-12-01 08:47:18] Suppress EOI broadcast on CPU#2 (XEN) [2015-12-01 08:47:18] masked ExtINT on CPU#2 (XEN) [2015-12-01 08:47:18] Suppress EOI broadcast on CPU#3 (XEN) [2015-12-01 08:47:18] masked ExtINT on CPU#3 (XEN) [2015-12-01 08:47:18] Brought up 4 CPUs (XEN) [2015-12-01 08:47:18] Dom0 has maximum 216 PIRQs (XEN) [2015-12-01 08:47:18] *** LOADING DOMAIN 0 *** (XEN) [2015-12-01 08:47:18] Xen kernel: 64-bit, lsb, compat32 (XEN) [2015-12-01 08:47:18] Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2264000 (XEN) [2015-12-01 08:47:18] PHYSICAL MEMORY ARRANGEMENT: (XEN) [2015-12-01 08:47:18] Dom0 alloc.: 0000000840000000->0000000844000000 (766101 pages to be allocated) (XEN) [2015-12-01 08:47:18] Init. ramdisk: 000000085d095000->000000085dfff270 (XEN) [2015-12-01 08:47:18] VIRTUAL MEMORY ARRANGEMENT: (XEN) [2015-12-01 08:47:18] Loaded kernel: ffffffff81000000->ffffffff82264000 (XEN) [2015-12-01 08:47:18] Init. ramdisk: 0000000000000000->0000000000000000 (XEN) [2015-12-01 08:47:18] Phys-Mach map: 0000008000000000->0000008000600000 (XEN) [2015-12-01 08:47:18] Start info: ffffffff82264000->ffffffff822644b4 (XEN) [2015-12-01 08:47:18] Page tables: ffffffff82265000->ffffffff8227a000 (XEN) [2015-12-01 08:47:18] Boot stack: ffffffff8227a000->ffffffff8227b000 (XEN) [2015-12-01 08:47:18] TOTAL: ffffffff80000000->ffffffff82400000 (XEN) [2015-12-01 08:47:18] ENTRY ADDRESS: ffffffff81f391f0 (XEN) [2015-12-01 08:47:18] Dom0 has maximum 1 VCPUs (XEN) [2015-12-01 08:47:20] Bogus DMIBAR 0xfed18001 on 0000:00:00.0 (XEN) [2015-12-01 08:47:20] Scrubbing Free RAM on 1 nodes using 4 CPUs (XEN) [2015-12-01 08:47:20] ...................................................................done. (XEN) [2015-12-01 08:47:21] Initial low memory virq threshold set at 0x4000 pages. (XEN) [2015-12-01 08:47:21] Std. Loglevel: Errors and warnings (XEN) [2015-12-01 08:47:21] Guest Loglevel: All (XEN) [2015-12-01 08:47:21] ********************************************** (XEN) [2015-12-01 08:47:21] ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS (XEN) [2015-12-01 08:47:21] ******* This option is intended to aid debugging of Xen by ensuring (XEN) [2015-12-01 08:47:21] ******* that all output is synchronously delivered on the serial line. (XEN) [2015-12-01 08:47:21] ******* However it can introduce SIGNIFICANT latencies and affect (XEN) [2015-12-01 08:47:21] ******* timekeeping. It is NOT recommended for production use! (XEN) [2015-12-01 08:47:21] ********************************************** (XEN) [2015-12-01 08:47:21] 3... 2... 1... (XEN) [2015-12-01 08:47:24] Xen is relinquishing VGA console. (XEN) [2015-12-01 08:47:24] *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) [2015-12-01 08:47:24] Freed 324kB init memory. mapping kernel into physical memory about to get started... [ 0.000000] Linux version 4.3.0-20.g82de429-default (geeko@buildhost) (gcc version 5.2.1 20151008 [gcc-5-branch revision 228597] (SUSE Linux) ) #1 SMP PREEMPT Sun Nov 29 16:26:10 UTC 20) [ 0.000000] efi: EFI_MEMMAP is not enabled. [ 0.000000] esrt: ESRT header is not in the memory map. [ 0.000000] ACPI: RSDP 0x000000009E779000 000024 (v02 SUPERM) [ 0.000000] ACPI: XSDT 0x000000009E7790A0 0000C4 (v01 SUPERM SMCI--MB 01072009 AMI 00010013) [ 0.000000] ACPI: FACP 0x000000009E787328 00010C (v05 SUPERM SMCI--MB 01072009 AMI 00010013) [ 0.000000] ACPI: DSDT 0x000000009E779200 00E121 (v02 SUPERM SMCI--MB 00000000 INTL 20120711) [ 0.000000] ACPI: FACS 0x000000009E7A8F80 000040 [ 0.000000] ACPI: APIC 0x000000009E787438 000072 (v03 SUPERM SMCI--MB 01072009 AMI 00010013) [ 0.000000] ACPI: FPDT 0x000000009E7874B0 000044 (v01 SUPERM SMCI--MB 01072009 AMI 00010013) [ 0.000000] ACPI: FIDT 0x000000009E7874F8 00009C (v01 SUPERM SMCI--MB 01072009 AMI 00010013) [ 0.000000] ACPI: SSDT 0x000000009E787598 000C7D (v02 Ther_R Ther_Rvp 00001000 INTL 20120711) [ 0.000000] ACPI: SSDT 0x000000009E788218 000539 (v02 PmRef Cpu0Ist 00003000 INTL 20051117) [ 0.000000] ACPI: SSDT 0x000000009E788758 000B74 (v02 CpuRef CpuSsdt 00003000 INTL 20051117) [ 0.000000] ACPI: SSDT 0x000000009E7892D0 0002DE (v02 PmRef Cpu0Tst 00003000 INTL 20051117) [ 0.000000] ACPI: SSDT 0x000000009E7895B0 000348 (v02 PmRef ApTst 00003000 INTL 20051117) [ 0.000000] ACPI: MCFG 0x000000009E7898F8 00003C (v01 SUPERM SMCI--MB 01072009 MSFT 00000097) [ 0.000000] ACPI: HPET 0x000000009E789938 000038 (v01 SUPERM SMCI--MB 01072009 AMI. 00000005) [ 0.000000] ACPI: SSDT 0x000000009E789970 000397 (v01 SataRe SataTabl 00001000 INTL 20120711) [ 0.000000] ACPI: SSDT 0x000000009E789D08 0057F6 (v02 SaSsdt SaSsdt 00003000 INTL 20120711) [ 0.000000] ACPI: ASF! 0x000000009E78F500 0000A5 (v32 INTEL HCG 00000001 TFSM 000F4240) [ 0.000000] ACPI: RMAD 0x000000009E78F5A8 000080 (v01 INTEL BDW 00000001 INTL 00000001) [ 0.000000] ACPI: EINJ 0x000000009E78F628 000130 (v01 AMI AMI EINJ 00000000 00000000) [ 0.000000] ACPI: ERST 0x000000009E78F758 000230 (v01 AMIER AMI ERST 00000000 00000000) [ 0.000000] ACPI: HEST 0x000000009E78F988 0000A8 (v01 AMI AMI HEST 00000000 00000000) [ 0.000000] ACPI: BERT 0x000000009E78FA30 000030 (v01 AMI AMI BERT 00000000 00000000) [ 0.000000] ACPI: BGRT 0x000000009E78FA60 000038 (v00 SUPERM SMCI--MB 01072009 AMI 00010013) [ 0.000000] p2m virtual area at ffffc90000000000, size is 40000000 [ 0.000000] Kernel command line: root=UUID=4716053b-39da-4cc1-a7ce-72171b862357 dolvm lvmwait=/dev/mapper/VG0-ROOT rootfstype=ext4 rootflags=journal_checksum noresume showopts n [ 62.614473] ACPI: 8 ACPI AML tables successfully acquired and loaded [ 62.622727] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [ 62.628732] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) [ 62.654264] Ignoring BGRT: invalid status 0 (expected 1) [ 62.668118] cpu 0 spinlock event irq 25 [ 62.671958] Could not initialize VPMU for cpu 0, error -95 [ 62.701897] NMI watchdog: disabled (cpu0): hardware events not enabled [ 62.716772] Grant table initialized [ 62.764746] ACPI: Executed 6 blocks of module-level executable AML code [ 62.778252] ACPI: Dynamic OEM Table Load: [ 62.782264] ACPI: SSDT 0xFFFF88011CCF8000 0003D3 (v02 PmRef Cpu0Cst 00003001 INTL 20051117) [ 62.791467] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20150818/hwxface-580) [ 62.800673] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150818/hwxface-580) (XEN) [2015-12-01 08:47:25] Bogus DMIBAR 0xfed18001 on 0000:00:00.0 [ 62.844530] ACPI: Enabled 7 GPEs in block 00 to 3F [ 62.853520] SCSI subsystem initialized [ 64.124873] audit: type=2000 audit(1448959646.979:1): initialized [ 64.131360] VFS: Disk quotas dquot_6.6.0 [ 64.135406] Key type big_key registered [ 64.139402] Key type asymmetric registered [ 64.143507] Asymmetric key parser 'x509' registered [ 64.183563] hpet_acpi_add: no address or irqs in _CRS [ 65.434498] efivars: duplicate variable: OnBoardLanCheckData-d49d402e-31a1-43c9-b524-d6fc992fb1c7 [ 65.443504] scsi 0:0:0:0: Direct-Access ATA WDC WD30EFRX-68E 0A82 PQ: 0 ANSI: 5 [ 65.456087] mce: Unable to init device /dev/mcelog (rc: -5) [ 65.461738] sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) [ 65.469549] scsi 1:0:0:0: Direct-Access ATA WDC WD30EFRX-68E 0A82 PQ: 0 ANSI: 5 [ 65.477954] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 65.483363] sd 1:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) [ 65.493096] sd 0:0:0:0: [sda] Write Protect is off [ 65.497975] scsi 2:0:0:0: Direct-Access ATA WDC WD30EFRX-68E 0A82 PQ: 0 ANSI: 5 [ 65.507830] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 65.513141] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 65.523849] Key type encrypted registered [ 65.529524] sd 2:0:0:0: [sdc] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) [ 65.540528] sd 1:0:0:0: [sdb] Write Protect is off [ 65.546975] scsi 3:0:0:0: Direct-Access ATA WDC WD30EFRX-68E 0A82 PQ: 0 ANSI: 5 [ 65.556941] sd 2:0:0:0: [sdc] 4096-byte physical blocks [ 65.563814] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 65.576301] sd 3:0:0:0: [sdd] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) [ 65.585838] sd 2:0:0:0: [sdc] Write Protect is off [ 65.592346] scsi 4:0:0:0: Direct-Access ATA ST31000524AS JC4B PQ: 0 ANSI: 5 [ 65.602152] sd 3:0:0:0: [sdd] 4096-byte physical blocks [ 65.609081] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 65.621644] sd 4:0:0:0: [sde] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 65.631084] sd 3:0:0:0: [sdd] Write Protect is off [ 65.637595] sd 4:0:0:0: [sde] Write Protect is off [ 65.644069] scsi 5:0:0:0: Direct-Access ATA ST31000340AS SD1A PQ: 0 ANSI: 5 [ 65.653865] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 65.666403] sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 65.679045] sd 5:0:0:0: [sdf] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 65.688638] sd 0:0:0:0: [sda] Attached SCSI disk [ 65.695230] sd 5:0:0:0: [sdf] Write Protect is off [ 65.701921] sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 65.714931] sd 1:0:0:0: [sdb] Attached SCSI disk [ 65.730730] sd 2:0:0:0: [sdc] Attached SCSI disk [ 65.752778] sd 3:0:0:0: [sdd] Attached SCSI disk [ 65.759679] sd 4:0:0:0: [sde] Attached SCSI disk [ 65.786567] sd 5:0:0:0: [sdf] Attached SCSI disk [ 65.927257] scsi 8:0:0:0: Direct-Access ATA WDC WD10EFRX-68P 0A82 PQ: 0 ANSI: 5 [ 65.937053] sd 8:0:0:0: [sdg] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 65.946374] sd 8:0:0:0: [sdg] 4096-byte physical blocks [ 65.953225] sd 8:0:0:0: [sdg] Write Protect is off [ 65.959586] sd 8:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 65.976499] scsi 9:0:0:0: Direct-Access ATA WDC WD10EFRX-68P 0A82 PQ: 0 ANSI: 5 [ 65.986240] sd 9:0:0:0: [sdh] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 65.995555] sd 9:0:0:0: [sdh] 4096-byte physical blocks [ 66.002390] scsi 10:0:0:0: Direct-Access ATA WDC WD1003FBYX-0 1V02 PQ: 0 ANSI: 5 [ 66.012178] sd 9:0:0:0: [sdh] Write Protect is off [ 66.018557] sd 9:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 66.030773] sd 10:0:0:0: [sdi] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 66.040170] sd 10:0:0:0: [sdi] Write Protect is off [ 66.046707] sd 10:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 66.067971] sd 8:0:0:0: [sdg] Attached SCSI disk [ 66.103631] sd 9:0:0:0: [sdh] Attached SCSI disk [ 66.110215] sd 10:0:0:0: [sdi] Attached SCSI disk [ 66.536707] scsi 11:0:0:0: Direct-Access ATA ST31000524AS JC4B PQ: 0 ANSI: 5 [ 66.546533] sd 11:0:0:0: [sdj] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 66.555890] sd 11:0:0:0: [sdj] Write Protect is off [ 66.562285] sd 11:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 66.599181] random: nonblocking pool is initialized [ 66.631201] sd 11:0:0:0: [sdj] Attached SCSI disk Welcome to openSUSE Leap 42.1 Again shutdown -r now PANIC as above ... dracut Warning: Killing all remaining processes mdadm: stopped /dev/md4 mdadm: stopped /dev/md3 mdadm: stopped /dev/md2 mdadm: stopped /dev/md0 mdadm: stopped /dev/md1 Rebooting. [ 272.120219] reboot: Restarting system (XEN) [2015-12-01 16:50:55] Hardware Dom0 shutdown: rebooting machine (XEN) [2015-12-01 16:50:55] APIC error on CPU0: 40(00) (XEN) [2015-12-01 16:50:55] ----[ Xen-4.6.0_04-398 x86_64 debug=n Tainted: C ]---- (XEN) [2015-12-01 16:50:55] CPU: 0 (XEN) [2015-12-01 16:50:55] RIP: e008:[<000000009e557340>] 000000009e557340 (XEN) [2015-12-01 16:50:55] RFLAGS: 0000000000010202 CONTEXT: hypervisor (d0v0) (XEN) [2015-12-01 16:50:55] rax: 000000009e557340 rbx: 0000000000000000 rcx: 0000000000000000 (XEN) [2015-12-01 16:50:55] rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000000000000 (XEN) [2015-12-01 16:50:55] rbp: 0000000000000000 rsp: ffff83008cadfdc0 r8: 0000000000000000 (XEN) [2015-12-01 16:50:55] r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 (XEN) [2015-12-01 16:50:55] r12: 0000000000000000 r13: 0000000000000cf9 r14: 0000000000000065 (XEN) [2015-12-01 16:50:55] r15: ffff830000000000 cr0: 0000000080050033 cr4: 00000000001526e0 (XEN) [2015-12-01 16:50:55] cr3: 000000084518c000 cr2: 000000009e557340 (XEN) [2015-12-01 16:50:55] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) [2015-12-01 16:50:55] Xen stack trace from rsp=ffff83008cadfdc0: (XEN) [2015-12-01 16:50:55] 000000009efe42f6 0000000000000065 ffff82d08022b8ca efff000000000000 (XEN) [2015-12-01 16:50:55] ffff82d080269000 000000084518c000 ffff82d08022bada 00000006af8a2000 (XEN) [2015-12-01 16:50:55] 0000000000000000 0000000000152660 000000000000e008 0000000000000292 (XEN) [2015-12-01 16:50:55] 0000000000000000 00000000fffffffe ffff82d0801821e8 0000000000000000 (XEN) [2015-12-01 16:50:55] 0000000000000010 000083008cadfe98 0000000000000000 0000003f5c0e3dec (XEN) [2015-12-01 16:50:55] 0000000000000001 0000000000000001 ffff83084514b000 ffff83084514b158 (XEN) [2015-12-01 16:50:55] 0000000000000002 00000000fee1dead ffff82d08012a03f ffff83008cadff18 (XEN) [2015-12-01 16:50:55] ffff82d0801058a1 0000000000000000 0000000000000000 ffff880093dfbdc0 (XEN) [2015-12-01 16:50:55] ffffffff81f13cc0 ffffffff81e4d460 ffff82d080129172 0000000100000000 (XEN) [2015-12-01 16:50:55] 0000000000000000 ffff83008da9d000 ffff880093dfbd98 ffffffff81f13cc0 (XEN) [2015-12-01 16:50:55] ffff83008da9d000 ffff880093dfbdc0 ffff82d080228070 ffff880121c0f3a8 (XEN) [2015-12-01 16:50:55] ffff880121c0f368 0000000000000000 000000000022eff0 ffff880093dfbdc0 (XEN) [2015-12-01 16:50:55] 0000000000000200 0000000000000216 0000000000000008 0000000000000001 (XEN) [2015-12-01 16:50:55] 0000000000000000 000000000000001d ffffffff810013aa 0000000000000200 (XEN) [2015-12-01 16:50:55] ffff880093dfbdac 0000000000000002 0001010000000000 ffffffff810013aa (XEN) [2015-12-01 16:50:55] 000000000000e033 0000000000000216 ffff880093dfbd90 000000000000e02b (XEN) [2015-12-01 16:50:55] 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) [2015-12-01 16:50:55] 0000000000000000 ffff83008da9d000 0000000000000000 0000000000000000 (XEN) [2015-12-01 16:50:55] Xen call trace: (XEN) [2015-12-01 16:50:55] [<000000009e557340>] 000000009e557340 (XEN) [2015-12-01 16:50:55] [<ffff82d08022b8ca>] efi_rs_enter+0xfa/0x120 (XEN) [2015-12-01 16:50:55] [<ffff82d08022bada>] efi_reset_system+0x3a/0x60 (XEN) [2015-12-01 16:50:55] [<ffff82d0801821e8>] machine_restart+0x208/0x2d0 (XEN) [2015-12-01 16:50:55] [<ffff82d08012a03f>] hwdom_shutdown+0xbf/0xc0 (XEN) [2015-12-01 16:50:55] [<ffff82d0801058a1>] domain_shutdown+0xf1/0x100 (XEN) [2015-12-01 16:50:55] [<ffff82d080129172>] do_sched_op+0x1d2/0x410 (XEN) [2015-12-01 16:50:55] [<ffff82d080228070>] lstar_enter+0xa0/0xa5 (XEN) [2015-12-01 16:50:55] (XEN) [2015-12-01 16:50:55] Pagetable walk from 000000009e557340: (XEN) [2015-12-01 16:50:55] L4[0x000] = 000000084518b063 ffffffffffffffff (XEN) [2015-12-01 16:50:55] L3[0x002] = 000000008ca7c063 ffffffffffffffff (XEN) [2015-12-01 16:50:55] L2[0x0f2] = 000000009e3ff063 ffffffffffffffff (XEN) [2015-12-01 16:50:55] L1[0x157] = 800000009e557163 ffffffffffffffff (XEN) [2015-12-01 16:50:55] (XEN) [2015-12-01 16:50:55] **************************************** (XEN) [2015-12-01 16:50:55] Panic on CPU 0: (XEN) [2015-12-01 16:50:55] FATAL PAGE FAULT (XEN) [2015-12-01 16:50:55] [error_code=0011] (XEN) [2015-12-01 16:50:55] Faulting linear address: 000000009e557340 (XEN) [2015-12-01 16:50:55] **************************************** (XEN) [2015-12-01 16:50:55] (XEN) [2015-12-01 16:50:55] Reboot in five seconds... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c17 --- Comment #17 from boo35 boo35 <9b3e05a5@opayq.com> ---
Avoid, or simply mute?
Whatever term you prefer.
It's not an issue of semantics. Do the workarounds provided actually fix a problem? Or simply turn off logging of it. Is that PANIC actually removed, or just not logged, e.g.? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526
http://bugzilla.suse.com/show_bug.cgi?id=956526#c18
--- Comment #18 from Jan Beulich
Is that PANIC actually removed, or just not logged, e.g.?
There are no ways to not log panics or other crashes. If the crash is gone, it's truly gone, not just hidden from you. Also, as to #16 - please to not inline large pieces of data, but attach them instead, to keep bugs manageable. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c19 --- Comment #19 from boo35 boo35 <9b3e05a5@opayq.com> --- fyi, removing /mapbs adding efi=no-rs so that cat /proc/cmdline root=UUID= ... efi=no-rs returns the PANIC. I.e., /mapbs remediates the PANIC; efi=no-rs does not. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526
http://bugzilla.suse.com/show_bug.cgi?id=956526#c20
--- Comment #20 from Jan Beulich
removing /mapbs adding efi=no-rs
so that
cat /proc/cmdline root=UUID= ... efi=no-rs
returns the PANIC.
I.e., /mapbs remediates the PANIC; efi=no-rs does not.
If the option shows up in /proc/cmdline, the you added it to the kernel options instead of the hypervisor ones. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526
http://bugzilla.suse.com/show_bug.cgi?id=956526#c21
Jan Beulich
Set
loglvl=all
Not according to ...
(XEN) Command line: dom0_mem=3072M,max:3072M dom0_max_vcpus=1 dom0_vcpus_pin=true cpuidle=1 cpufreq=xen clocksource=hpet iommu=verbose sched=credit vga=gfx-1920x1080x16 com1=115200,8n1,pci
... this. Yet without that we don't see the EFI memory map. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c22 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(9b3e05a5@opayq.co | |m) | --- Comment #22 from boo35 boo35 <9b3e05a5@opayq.com> --- Created attachment 658101 --> http://bugzilla.suse.com/attachment.cgi?id=658101&action=edit bootlogs1.txt
(XEN) Command line: dom0_mem=3072M,max:3072M dom0_max_vcpus=1 dom0_vcpus_pin=true cpuidle=1 cpufreq=xen clocksource=hpet iommu=verbose sched=credit vga=gfx-1920x1080x16 com1=115200,8n1,pci
That's unfortunately useless. It's the copy from the serial console output, which does not wrap. It's truncated. The full Command Line is actually GRUB_CMDLINE_XEN=" dom0_mem=3072M,max:3072M dom0_max_vcpus=1 dom0_vcpus_pin=true cpuidle=1 cpufreq=xen clocksource=hpet iommu=verbose sched=credit vga=gfx-1920x1080x16 com1=115200,8n1,pci console=com1,vga console_timestamps loglvl=warning guest_loglvl=none/warning sync_console console_to_ring conring_size=64 earlyprintk=vga,keep log_buf_len=10M sched_debug apic_verbosity=verbose log_lvl=all guest_loglvl=all" Where you'll see the actual mistake -- a typo, "log_lvl=all".
If the option shows up in /proc/cmdline, the you added it to the kernel options instead of the hypervisor ones.
That's what I understood to be the "ordinary command line" -- the kernel command line (as in /proc/cmdline), rather than the hypervisor 'options' line. Adding to the hypervisor options does the trick. Attachment with fixes ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526
http://bugzilla.suse.com/show_bug.cgi?id=956526#c23
Jan Beulich
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c24 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jbeulich@suse.com Flags| |needinfo?(jbeulich@suse.com | |) --- Comment #24 from boo35 boo35 <9b3e05a5@opayq.com> --- (In reply to Jan Beulich from comment #23)
Considering your other reboot problem (after having added /mapbs) I suppose "efi=no-rs" would take care of both issues at once. Please let us know.
Sure. What specific additional info are your asking for, beyond that already provided? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526
http://bugzilla.suse.com/show_bug.cgi?id=956526#c25
Jan Beulich
http://bugzilla.suse.com/show_bug.cgi?id=956526
http://bugzilla.suse.com/show_bug.cgi?id=956526#c26
--- Comment #26 from Jan Beulich
http://bugzilla.suse.com/show_bug.cgi?id=956526 http://bugzilla.suse.com/show_bug.cgi?id=956526#c27 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(9b3e05a5@opayq.co | |m) | --- Comment #27 from boo35 boo35 <9b3e05a5@opayq.com> --- (In reply to Jan Beulich from comment #25)
A test with "efi=no-rs" (on the hypervisor command line), with /mapbs removed from the boot loader portion of the hypervisor options.
As already provided,
removing /mapbs adding efi=no-rs ... Adding to the hypervisor options does the trick.
Attachment with fixes ...
cat bootlogs1.txt ... serial console output, efi=no-rs, shutdown - ... loglvl=all guest_loglvl=all" + ... loglvl=all guest_loglvl=all efi=no-rs" ... Warning: Killing all remaining processes mdadm: stopped /dev/md4 mdadm: stopped /dev/md2 mdadm: stopped /dev/md3 mdadm: stopped /dev/md0 mdadm: stopped /dev/md1 Rebooting. [ 247.929305] reboot: Restarting system (XEN) [2015-12-02 14:46:25] Hardware Dom0 shutdown: rebooting machine (XEN) [2015-12-02 14:46:25] APIC error on CPU0: 40(00) (XEN) [2015-12-02 14:46:25] Resetting with ACPI MEMORY or I/O RESET_REG. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956526
http://bugzilla.suse.com/show_bug.cgi?id=956526#c28
Jan Beulich
http://bugzilla.suse.com/show_bug.cgi?id=956526 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|9b3e05a5@opayq.com | -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com