[Bug 926594] New: Xen4.5+kernel-xen- 3.19.3-3.1 PANIC on every reboot, "Panic on CPU 0: FATAL PAGE FAULT"
http://bugzilla.suse.com/show_bug.cgi?id=926594 Bug ID: 926594 Summary: Xen4.5+kernel-xen- 3.19.3-3.1 PANIC on every reboot, "Panic on CPU 0: FATAL PAGE FAULT" Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: Xen Assignee: jdouglas@suse.com Reporter: lyndat3@your-mail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I'm running kernel-xen-3.19.3-3.1.g0f5134a.x86_64 xen-4.5.0_03-364.3.x86_64 xen-libs-4.5.0_03-364.3.x86_64 xen-tools-4.5.0_03-364.3.x86_64 The system boots completely and functions. On reboot/shutdown -r, it crashes every time. It's 100% reproducible here. Here's the console log. shutdown -r now ... [59407.439868] reboot: Restarting system (XEN) [2015-04-09 13:46:45] Domain 0 shutdown: rebooting machine. (XEN) [2015-04-09 13:46:45] ----[ Xen-4.5.0_03-363 x86_64 debug=n Tainted: C ]---- (XEN) [2015-04-09 13:46:45] CPU: 0 (XEN) [2015-04-09 13:46:45] RIP: e008:[<000000009e6c4000>] 000000009e6c4000 (XEN) [2015-04-09 13:46:45] RFLAGS: 0000000000010247 CONTEXT: hypervisor (XEN) [2015-04-09 13:46:45] rax: 000000009e670340 rbx: 0000000000000000 rcx: 0000000000000000 (XEN) [2015-04-09 13:46:45] rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000000000000 (XEN) [2015-04-09 13:46:45] rbp: 0000000000000000 rsp: ffff82d080457dd0 r8: 0000000000000000 (XEN) [2015-04-09 13:46:45] r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000008 (XEN) [2015-04-09 13:46:45] r12: 0000000000000000 r13: 0000000000000061 r14: 00000000fee1dead (XEN) [2015-04-09 13:46:45] r15: 0000000000000000 cr0: 0000000080050033 cr4: 00000000001526f0 (XEN) [2015-04-09 13:46:45] cr3: 00000008459a3000 cr2: 000000009e6c4000 (XEN) [2015-04-09 13:46:45] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) [2015-04-09 13:46:45] Xen stack trace from rsp=ffff82d080457dd0: (XEN) [2015-04-09 13:46:45] 000000009efe42f6 00000000fee1dead ffff82d0802278a4 efff00000000000a (XEN) [2015-04-09 13:46:45] ffff82d080262000 00000008459a3000 ffff82d080227a7a 000000069462e000 (XEN) [2015-04-09 13:46:45] 0000000000000000 0000000000152670 0000000000000700 0000000000000061 (XEN) [2015-04-09 13:46:45] 0000000000000000 00000000fffffffe ffff82d08018477c ffff82d080457e98 (XEN) [2015-04-09 13:46:45] 0000000080457e58 0000361aa81209b7 0000000000000000 0000000000000001 (XEN) [2015-04-09 13:46:45] 0000000000000001 ffff83084595b000 ffff83084595b138 00000000fee1dead (XEN) [2015-04-09 13:46:45] ffff82d080129c99 0000000000000003 ffff82d080105721 0000000000000000 (XEN) [2015-04-09 13:46:45] 0000000000000000 0000000028121969 ffffffff80a1f100 0000000000000002 (XEN) [2015-04-09 13:46:45] ffff82d080128d3f 00000001ffffffff 0000000000000005 ffff83009e786000 (XEN) [2015-04-09 13:46:45] 00000000000bcbd0 0000000000000000 ffff83009e786000 0000000028121969 (XEN) [2015-04-09 13:46:46] ffff82d080224119 ffffc9000819e080 ffffc9000819e16c ffff8800b610e4a7 (XEN) [2015-04-09 13:46:46] ffffc9000819e168 0000000028121969 0000000000000000 0000000000000282 (XEN) [2015-04-09 13:46:46] 0000000000000064 0000000000000510 0000000000000000 000000000000001d (XEN) [2015-04-09 13:46:46] ffffffff800113aa 0000000000000001 ffff8800306ebe1c 0000000000000002 (XEN) [2015-04-09 13:46:46] 0001010000000000 ffffffff800113aa 000000000000e033 0000000000000282 (XEN) [2015-04-09 13:46:46] ffff8800306ebdf8 000000000000e02b 0000000000000000 0000000000000000 (XEN) [2015-04-09 13:46:46] 0000000000000000 0000000000000000 0000000000000000 ffff83009e786000 (XEN) [2015-04-09 13:46:46] 0000000000000000 0000000000000000 (XEN) [2015-04-09 13:46:46] Xen call trace: (XEN) [2015-04-09 13:46:46] [<000000009e6c4000>] 000000009e6c4000 (XEN) [2015-04-09 13:46:46] [<ffff82d0802278a4>] efi_rs_enter+0xf4/0x110 (XEN) [2015-04-09 13:46:46] [<ffff82d080227a7a>] efi_reset_system+0x3a/0x60 (XEN) [2015-04-09 13:46:46] [<ffff82d08018477c>] machine_restart+0xcc/0x220 (XEN) [2015-04-09 13:46:46] [<ffff82d080129c99>] hwdom_shutdown+0x89/0x90 (XEN) [2015-04-09 13:46:46] [<ffff82d080105721>] domain_shutdown+0xf1/0x100 (XEN) [2015-04-09 13:46:46] [<ffff82d080128d3f>] do_sched_op+0x1af/0x440 (XEN) [2015-04-09 13:46:46] [<ffff82d080224119>] syscall_enter+0xa9/0xae (XEN) [2015-04-09 13:46:46] (XEN) [2015-04-09 13:46:46] Pagetable walk from 000000009e6c4000: (XEN) [2015-04-09 13:46:46] L4[0x000] = 00000008459a2063 ffffffffffffffff (XEN) [2015-04-09 13:46:46] L3[0x002] = 000000008c674063 ffffffffffffffff (XEN) [2015-04-09 13:46:46] L2[0x0f3] = 000000009e5ff063 ffffffffffffffff (XEN) [2015-04-09 13:46:46] L1[0x0c4] = 0000000000000000 ffffffffffffffff (XEN) [2015-04-09 13:46:46] (XEN) [2015-04-09 13:46:46] **************************************** (XEN) [2015-04-09 13:46:46] Panic on CPU 0: (XEN) [2015-04-09 13:46:46] FATAL PAGE FAULT (XEN) [2015-04-09 13:46:46] [error_code=0010] (XEN) [2015-04-09 13:46:46] Faulting linear address: 000000009e6c4000 (XEN) [2015-04-09 13:46:46] **************************************** (XEN) [2015-04-09 13:46:46] (XEN) [2015-04-09 13:46:46] Manual reset required ('noreboot' specified) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 Charles Arnold <carnold@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carnold@suse.com Assignee|jdouglas@suse.com |jbeulich@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 Jan Beulich <jbeulich@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lyndat3@your-mail.com Flags| |needinfo?(lyndat3@your-mail | |.com) --- Comment #1 from Jan Beulich <jbeulich@suse.com> --- As said on the mailing list already, we need the _complete_ serial log minimally at "info" log level. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 lynda t <lyndat3@your-mail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lyndat3@your-mail | |.com) | --- Comment #2 from lynda t <lyndat3@your-mail.com> --- Here's the _complete_ serial log at more-than-minimal 'loglvl=all guest_loglvl=all', from the moment 'shutdown -r now' is exec'd Deactivating swap /dev/dm-1... Deactivating swap /dev/dm-1... Deactivating swap /dev/dm-1... Deactivating swap /dev/dm-1... Deactivating swap /dev/dm-1... Deactivating swap /dev/dm-1... [ OK ] Stopped target Sound Card. [ OK ] Removed slice system-systemd\x2dfsck.slice. Stopping User Manager for UID 0... [ OK ] Stopped target Multi-User System. Stopping Xendomains - start and stop guests on boot and shutdown... Stopping Quota RPC monitor... Stopping OpenSSH Daemon... Stopping Command Scheduler... Stopping System Logging Service... Stopping Login Service... Stopping /etc/init.d/after.local Compatibility... [ OK ] Stopped /etc/init.d/after.local Compatibility. [ OK ] Stopped target Login Prompts. Stopping Serial Getty on xvc0... Stopping Getty on tty1... [ OK ] Deactivated swap /dev/mapper/vg0-SWAP. [ OK ] Deactivated swap /dev/disk/by-uuid/d5a685d3-d375-475...d-c4e937468395. [ OK ] Deactivated swap /dev/disk/by-id/raid-vg0-SWAP. [ OK ] Deactivated swap /dev/disk/by-id/dm-uuid-LVM-BL0eXcs...PVvZufn2ad1194. [ OK ] Deactivated swap /dev/disk/by-id/dm-name-vg0-SWAP. [ OK ] Deactivated swap /dev/vg0/SWAP. [ OK ] Stopped System Logging Service. [ OK ] Stopped Command Scheduler. [ OK ] Stopped Quota RPC monitor. [ OK ] Stopped Login Service. [ OK ] Stopped OpenSSH Daemon. [ OK ] Deactivated swap /dev/dm-1. Stopping Automounts filesystems on demand... [ OK ] Stopped Automounts filesystems on demand. [ OK ] Stopped Xendomains - start and stop guests on boot and shutdown. [ OK ] Stopped target Host and Network Name Lookups. Stopping xencommons... [ OK ] Stopped xencommons. Stopping qemu for xen dom0 disk backend... Stopping xen-init-dom0, initialise Dom0 configuratio...ration stub)... [ OK ] Stopped xen-init-dom0, initialise Dom0 configuration...guration stub). [ OK ] Stopped qemu for xen dom0 disk backend. Stopping Xenconsoled - handles logging from guest co...d hypervisor... [ OK ] Stopped Xenconsoled - handles logging from guest con...and hypervisor. Stopping The Xen xenstore... [ OK ] Stopped The Xen xenstore. [ OK ] Stopped Serial Getty on xvc0. [ OK ] Removed slice system-serial\x2dgetty.slice. Starting Restore /run/initramfs... [ OK ] Removed slice system-getty.slice. Stopping /etc/init.d/boot.local Compatibility... [ OK ] Stopped /etc/init.d/boot.local Compatibility. [ OK ] Started Restore /run/initramfs. [ OK ] Stopped User Manager for UID 0. [ OK ] Removed slice user-0.slice. Stopping Permit User Sessions... [ OK ] Stopped Permit User Sessions. [ OK ] Stopped target Remote File Systems. [ OK ] Stopped target Remote File Systems (Pre). [ OK ] Stopped target RPC Port Mapper. [ OK ] Stopped target Network is Online. [ OK ] Stopped target Network. Stopping wicked managed network interfaces... [45546.986270] br0: port 1(eno1) entered disabled state [45547.100443] e1000e: eno1 NIC Link is Down [45547.121080] device eno1 left promiscuous mode [45547.134846] br0: port 1(eno1) entered disabled state [ OK ] Stopped wicked managed network interfaces. Stopping wicked network nanny service... [ OK ] Stopped wicked network nanny service. Stopping wicked network management service daemon... [ OK ] Stopped wicked network management service daemon. Stopping wicked DHCPv6 supplicant service... Stopping wicked DHCPv4 supplicant service... Stopping wicked AutoIPv4 supplicant service... [ OK ] Stopped wicked DHCPv6 supplicant service. [ OK ] Stopped wicked DHCPv4 supplicant service. [ OK ] Stopped wicked AutoIPv4 supplicant service. Stopping D-Bus System Message Bus... [ OK ] Stopped D-Bus System Message Bus. [ OK ] Stopped target Basic System. [ OK ] Stopped target Slices. [ OK ] Removed slice User and Session Slice. [ OK ] Stopped target Paths. [ OK ] Stopped target Timers. [ OK ] Stopped target Sockets. [ OK ] Closed xenstore ro socket. [ OK ] Closed xenstore socket. Unmounting mount xenstore file system... [ OK ] Closed Syslog Socket. [ OK ] Closed D-Bus System Message Bus Socket. [ OK ] Stopped target System Initialization. Stopping Load/Save Random Seed... Stopping Apply Kernel Variables... [ OK ] Stopped Apply Kernel Variables. Unmounting /sys/kernel/debug... [ OK ] Stopped target Encrypted Volumes. [ OK ] Stopped target Swap. Stopping Update UTMP about System Reboot/Shutdown... Stopping Setup Virtual Console... [ OK ] Stopped Setup Virtual Console. [ OK ] Unmounted mount xenstore file system. [ OK ] Stopped Load/Save Random Seed. [ OK ] Unmounted /sys/kernel/debug. [ OK ] Stopped Update UTMP about System Reboot/Shutdown. Stopping Create Volatile Files and Directories... [ OK ] Stopped Create Volatile Files and Directories. [ OK ] Stopped target Local File Systems. Unmounting /var/cache... [ OK ] Unset automount boot-efi.automount. Unmounting /boot... [ OK ] Unmounted /var/cache. Unmounting /var... [ OK ] Failed unmounting /var. [45548.129285] systemd[1]: Failed unmounting /var. Unmounting /home... [ OK ] Failed unmounting /home. [45548.279255] systemd[1]: Failed unmounting /home. [ OK ] Unmounted /boot. [ OK ] Reached target Unmount All Filesystems. [ OK ] Stopped target Local File Systems (Pre). Stopping Remount Root and Kernel File Systems... [ OK ] Stopped Remount Root and Kernel File Systems. Stopping Replay Read-Ahead Data... [ OK ] Stopped Replay Read-Ahead Data. Stopping Collect Read-Ahead Data... [ OK ] Stopped Collect Read-Ahead Data. [ OK ] Reached target Shutdown. [45549.400089] systemd-journald[1235]: Received SIGTERM from PID 1 (systemd-shutdow). [45549.803511] EXT4-fs (dm-8): re-mounted. Opts: (null) [45549.901443] EXT4-fs (dm-3): re-mounted. Opts: (null) [45550.047949] EXT4-fs (dm-6): re-mounted. Opts: (null) [45550.448346] EXT4-fs (dm-0): re-mounted. Opts: (null) [45550.465696] EXT4-fs (dm-0): re-mounted. Opts: (null) [45550.481225] EXT4-fs (dm-0): re-mounted. Opts: (null) [45550.520931] systemd-shutdown[1]: Cannot finalize remaining file systems and devices, giving up. [45550.736537] dracut: Taking over mdmon processes. [45550.751194] dracut Warning: Killing all remaining processes dracut Warning: Killing all remaining processes [45550.801724] dracut Warning: Unmounted /oldroot. [45550.825634] dracut: Disassembling device-mapper devices [45550.850234] dracut: Waiting for mdraid devices to be clean. [45550.869764] dracut: Disassembling mdraid devices. [45550.910744] md4: detected capacity change from 2000137748480 to 0 [45550.929760] md: md4 stopped. [45550.939115] md: unbind<sdk1> [45550.948465] md: export_rdev(sdk1) [45550.959163] md: unbind<sdm1> [45550.968509] md: export_rdev(sdm1) [45550.979171] md: unbind<sdl1> [45550.988518] md: export_rdev(sdl1) mdadm: stopped /dev/md4 [45551.044706] md3: detected capacity change from 2000137748480 to 0 [45551.063752] md: md3 stopped. [45551.073120] md: unbind<sdj1> [45551.082456] md: export_rdev(sdj1) [45551.093116] md: unbind<sdi1> [45551.102424] md: export_rdev(sdi1) [45551.113027] md: unbind<sdf1> [45551.122297] md: export_rdev(sdf1) [45551.132866] md: unbind<sde1> [45551.142094] md: export_rdev(sde1) mdadm: stopped /dev/md3 [45551.182979] md2: detected capacity change from 6000914464768 to 0 [45551.201920] md: md2 stopped. [45551.211141] md: unbind<sda1> [45551.220365] md: export_rdev(sda1) [45551.230927] md: unbind<sdb1> [45551.240133] md: export_rdev(sdb1) [45551.250605] md: unbind<sdd1> [45551.259786] md: export_rdev(sdd1) [45551.270285] md: unbind<sdc1> [45551.279487] md: export_rdev(sdc1) mdadm: stopped /dev/md2 [45551.355891] md0: detected capacity change from 1073676288 to 0 [45551.374036] md: md0 stopped. [45551.383270] md: unbind<sdg3> [45551.392453] md: export_rdev(sdg3) [45551.402971] md: unbind<sdh3> [45551.412114] md: export_rdev(sdh3) mdadm: stopped /dev/md0 [45551.492145] md1: detected capacity change from 998814253056 to 0 [45551.510694] md: md1 stopped. [45551.519854] md: unbind<sdg4> [45551.528977] md: export_rdev(sdg4) [45551.539443] md: unbind<sdh4> [45551.548562] md: export_rdev(sdh4) mdadm: stopped /dev/md1 Rebooting. [45551.573934] sd 12:0:2:0: [sdm] Synchronizing SCSI cache [45551.590231] sd 12:0:1:0: [sdl] Synchronizing SCSI cache [45551.606510] sd 12:0:0:0: [sdk] Synchronizing SCSI cache [45551.622868] sd 11:0:0:0: [sdj] Synchronizing SCSI cache [45551.639241] sd 10:0:0:0: [sdi] Synchronizing SCSI cache [45551.655500] sd 9:0:0:0: [sdh] Synchronizing SCSI cache [45551.671453] sd 8:0:0:0: [sdg] Synchronizing SCSI cache [45551.687421] sd 5:0:0:0: [sdf] Synchronizing SCSI cache [45551.704693] sd 4:0:0:0: [sde] Synchronizing SCSI cache [45551.720751] sd 3:0:0:0: [sdd] Synchronizing SCSI cache [45551.736697] sd 2:0:0:0: [sdc] Synchronizing SCSI cache [45551.752652] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [45551.768581] sd 0:0:0:0: [sda] Synchronizing SCSI cache (XEN) [2015-04-13 13:09:03] irq.c:2120: dom0: forcing unbind of pirq 201 (XEN) [2015-04-13 13:09:03] irq.c:2120: dom0: forcing unbind of pirq 202 (XEN) [2015-04-13 13:09:03] irq.c:2120: dom0: forcing unbind of pirq 203 (XEN) [2015-04-13 13:09:03] irq.c:2120: dom0: forcing unbind of pirq 190 [45552.084141] e1000e: EEE TX LPI TIMER: 00000011 [45552.135761] reboot: Restarting system (XEN) [2015-04-13 13:09:03] Domain 0 shutdown: rebooting machine. (XEN) [2015-04-13 13:09:03] ----[ Xen-4.5.0_03-364 x86_64 debug=n Tainted: C ]---- (XEN) [2015-04-13 13:09:03] CPU: 0 (XEN) [2015-04-13 13:09:03] RIP: e008:[<000000009e6c4000>] 000000009e6c4000 (XEN) [2015-04-13 13:09:03] RFLAGS: 0000000000010247 CONTEXT: hypervisor (XEN) [2015-04-13 13:09:03] rax: 000000009e670340 rbx: 0000000000000000 rcx: 0000000000000000 (XEN) [2015-04-13 13:09:03] rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000000000000 (XEN) [2015-04-13 13:09:03] rbp: 0000000000000000 rsp: ffff82d080457dd0 r8: 0000000000000000 (XEN) [2015-04-13 13:09:03] r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000008 (XEN) [2015-04-13 13:09:03] r12: 0000000000000000 r13: 0000000000000061 r14: 00000000fee1dead (XEN) [2015-04-13 13:09:03] r15: 0000000000000000 cr0: 0000000080050033 cr4: 00000000001526f0 (XEN) [2015-04-13 13:09:04] cr3: 0000000845982000 cr2: 000000009e6c4000 (XEN) [2015-04-13 13:09:04] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) [2015-04-13 13:09:04] Xen stack trace from rsp=ffff82d080457dd0: (XEN) [2015-04-13 13:09:04] 000000009efe42f6 00000000fee1dead ffff82d0802278a4 efff00000000000a (XEN) [2015-04-13 13:09:04] ffff82d080262000 0000000845982000 ffff82d080227a7a 000000069bc29000 (XEN) [2015-04-13 13:09:04] 0000000000000000 0000000000152670 0000000000000700 0000000000000061 (XEN) [2015-04-13 13:09:04] 0000000000000000 00000000fffffffe ffff82d08018477c ffff82d080457e98 (XEN) [2015-04-13 13:09:04] 0000000080457e58 00002980adb8056c 0000000000000000 0000000000000001 (XEN) [2015-04-13 13:09:04] 0000000000000001 ffff830845948000 ffff830845948138 00000000fee1dead (XEN) [2015-04-13 13:09:04] ffff82d080129c99 0000000000000003 ffff82d080105721 0000000000000000 (XEN) [2015-04-13 13:09:04] 0000000000000000 0000000028121969 ffffffff80a1f100 0000000000000002 (XEN) [2015-04-13 13:09:04] ffff82d080128d3f 0000000100000003 ffff82d080129d0a ffff83009e786000 (XEN) [2015-04-13 13:09:04] ffff83009e786000 00000000000d3aaf ffff83009e786000 0000000028121969 (XEN) [2015-04-13 13:09:04] ffff82d080224119 0000000000000003 0000296def8c6966 0000296def99ad00 (XEN) [2015-04-13 13:09:04] 0000000000000000 0000000028121969 0000000000000000 0000000000000282 (XEN) [2015-04-13 13:09:04] 0000000000000064 000000000000077c 0000000000000000 000000000000001d (XEN) [2015-04-13 13:09:04] ffffffff800113aa 0000000000000001 ffff8800b420fe1c 0000000000000002 (XEN) [2015-04-13 13:09:04] 0001010000000000 ffffffff800113aa 000000000000e033 0000000000000282 (XEN) [2015-04-13 13:09:04] ffff8800b420fdf8 000000000000e02b 0000000000000000 0000000000000000 (XEN) [2015-04-13 13:09:04] 0000000000000000 0000000000000000 0000000000000000 ffff83009e786000 (XEN) [2015-04-13 13:09:04] 0000000000000000 0000000000000000 (XEN) [2015-04-13 13:09:04] Xen call trace: (XEN) [2015-04-13 13:09:04] [<000000009e6c4000>] 000000009e6c4000 (XEN) [2015-04-13 13:09:04] [<ffff82d0802278a4>] efi_rs_enter+0xf4/0x110 (XEN) [2015-04-13 13:09:04] [<ffff82d080227a7a>] efi_reset_system+0x3a/0x60 (XEN) [2015-04-13 13:09:04] [<ffff82d08018477c>] machine_restart+0xcc/0x220 (XEN) [2015-04-13 13:09:04] [<ffff82d080129c99>] hwdom_shutdown+0x89/0x90 (XEN) [2015-04-13 13:09:04] [<ffff82d080105721>] domain_shutdown+0xf1/0x100 (XEN) [2015-04-13 13:09:04] [<ffff82d080128d3f>] do_sched_op+0x1af/0x440 (XEN) [2015-04-13 13:09:04] [<ffff82d080129d0a>] __do_softirq+0x6a/0x90 (XEN) [2015-04-13 13:09:04] [<ffff82d080224119>] syscall_enter+0xa9/0xae (XEN) [2015-04-13 13:09:04] (XEN) [2015-04-13 13:09:04] Pagetable walk from 000000009e6c4000: (XEN) [2015-04-13 13:09:04] L4[0x000] = 0000000845981063 ffffffffffffffff (XEN) [2015-04-13 13:09:04] L3[0x002] = 000000008c674063 ffffffffffffffff (XEN) [2015-04-13 13:09:04] L2[0x0f3] = 000000009e5ff063 ffffffffffffffff (XEN) [2015-04-13 13:09:04] L1[0x0c4] = 0000000000000000 ffffffffffffffff (XEN) [2015-04-13 13:09:04] (XEN) [2015-04-13 13:09:04] **************************************** (XEN) [2015-04-13 13:09:04] Panic on CPU 0: (XEN) [2015-04-13 13:09:04] FATAL PAGE FAULT (XEN) [2015-04-13 13:09:04] [error_code=0010] (XEN) [2015-04-13 13:09:04] Faulting linear address: 000000009e6c4000 (XEN) [2015-04-13 13:09:04] **************************************** (XEN) [2015-04-13 13:09:04] (XEN) [2015-04-13 13:09:04] Manual reset required ('noreboot' specified) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 Jan Beulich <jbeulich@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(lyndat3@your-mail | |.com) --- Comment #3 from Jan Beulich <jbeulich@suse.com> --- Please note that I said "complete", not "from the moment 'shutdown -r now' is exec'd". And please attach logs instead of inlining them. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 --- Comment #4 from lynda t <lyndat3@your-mail.com> --- (In reply to Jan Beulich from comment #3)
Please note that I said "complete", not "from the moment 'shutdown -r now' is exec'd". And please attach logs instead of inlining them.
Can you please just say what you do want, not what you don't? Are you looking for a serial log FROM bootup TO failed shutdown? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 --- Comment #5 from Jan Beulich <jbeulich@suse.com> --- (In reply to lynda t from comment #4)
Are you looking for a serial log FROM bootup TO failed shutdown?
Exactly. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 lynda t <lyndat3@your-mail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lyndat3@your-mail | |.com) | --- Comment #6 from lynda t <lyndat3@your-mail.com> --- Created attachment 630880 --> http://bugzilla.suse.com/attachment.cgi?id=630880&action=edit serial log, from boot to fail @ shutdown, loglvl & guest_loglvl == info attached: serial log, from boot to fail @ shutdown, loglvl & guest_loglvl == info -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 Jan Beulich <jbeulich@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #7 from Jan Beulich <jbeulich@suse.com> --- As suspected the area is not marked for runtime mapping: (XEN) 000009e6c4000-000009e6ddfff type=0 attr=000000000000000f Hence this is a firmware bug. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 Jan Beulich <jbeulich@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #8 from Jan Beulich <jbeulich@suse.com> --- The workaround mentioned is already in the upstream trees for 4.5.1 and 4.4.3, and hence will become available eventually via maintenance update. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 --- Comment #9 from lynda t <lyndat3@your-mail.com> --- (In reply to Jan Beulich from comment #8)
The workaround mentioned is already in the upstream trees for 4.5.1 and 4.4.3, and hence will become available eventually via maintenance update.
This sound then like a definite Xen bug, and that a resolution requires integrating a known fix from upstream. Looking at http://wiki.xenproject.org/wiki/Xen_Project_Hypervisor_Roadmap/4.5, 4.5.1, not even mentioned there, seems like it's many months out still. But this ^^ has been marked 'wontfix'. Does that mean the known fix will not be integrated into existing tree? Just confused a bit. What's meant by a 'maintenance update' here? Does that mean a patch will be backported to the existing 4.5.0 release in openSUSE's Xen sometime in the nearer future? If it does, is there any roadmap / timeline? Can't begin to use Xen in any sort of production until at least this gets resolved. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 --- Comment #10 from Jan Beulich <jbeulich@suse.com> --- (In reply to lynda t from comment #9)
This sound then like a definite Xen bug, and that a resolution requires integrating a known fix from upstream.
Where do you see the Xen bug here? It is a bug of the firmware not to mark for runtime use any code/data that can be accessed by EFI Runtime Services calls.
Looking at http://wiki.xenproject.org/wiki/Xen_Project_Hypervisor_Roadmap/4.5, 4.5.1, not even mentioned there, seems like it's many months out still.
The roadmap only talks about major releases, not stable ones afaik. We're going to cut 4.5.1-rc1 within the next couple of weeks (preparations are already in progress).
But this ^^ has been marked 'wontfix'. Does that mean the known fix will not be integrated into existing tree? Just confused a bit.
For one there is no "known fix", only a workaround (hence the "wontfix"). And then ...
What's meant by a 'maintenance update' here? Does that mean a patch will be backported to the existing 4.5.0 release in openSUSE's Xen sometime in the nearer future? If it does, is there any roadmap / timeline? Can't begin to use Xen in any sort of production until at least this gets resolved.
... 13.2 will pick up 4.4.3 eventually (that'll take some time, as 4.4.2 got released pretty recently), and Factory will presumably pick up 4.5.1 once available, i.e. the workaround will become available. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 --- Comment #11 from lynda t <lyndat3@your-mail.com> --- (In reply to Jan Beulich from comment #10)
(In reply to lynda t from comment #9)
This sound then like a definite Xen bug, and that a resolution requires integrating a known fix from upstream.
Where do you see the Xen bug here? It is a bug of the firmware not to mark for runtime use any code/data that can be accessed by EFI Runtime Services calls.
That's part of the problem -- I don't "see" any bug. There's no reference to a specific commit. I posted this ^^ as a Xen bug, correctly or not. That hasn't been changed by anyone. You've asked for Xen logs, and referenced a line in the Xen output. Then you've said the solution "is already in the upstream trees for 4.5.1:. 4.5.1 sounds like Xen.
The roadmap only talks about major releases, not stable ones afaik. We're going to cut 4.5.1-rc1 within the next couple of weeks (preparations are already in progress).
If that rc will have this ^^ solution in it, that's good to know. Leaves me in the lurch for awhile, but that's how the dust settles. Bunch of other stuff that needs fixing will eat up time anyway ...
For one there is no "known fix", only a workaround (hence the "wontfix"). And then ...
Ok, I guess that means something to dev in detail. I read that differently -- As an end-user filing the bug, my goal is to know if/when a "fixed" version will be packaged & available somewhere we can dl and use it. ok, nm then.
... 13.2 will pick up 4.4.3 eventually (that'll take some time, as 4.4.2 got released pretty recently), and Factory will presumably pick up 4.5.1 once available, i.e. the workaround will become available.
I'm running a 13.2 core, with Xen 4.5.x and kernel-xen from Stable. "Not supported" I know, but it's the only config I find that's close to production ready for my hardware and needs. I'll keep an eye out for the 4.5.1 workaround -- that sounds like it'll solve this problem. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 --- Comment #12 from Jan Beulich <jbeulich@suse.com> --- (In reply to lynda t from comment #11)
That's part of the problem -- I don't "see" any bug. There's no reference to a specific commit.
Not here, but I had mailed it to you in the list conversation: http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=c643fb110a51693e82a3...
I posted this ^^ as a Xen bug, correctly or not. That hasn't been changed by anyone. You've asked for Xen logs, and referenced a line in the Xen output. Then you've said the solution "is already in the upstream trees for 4.5.1:.
I have no idea what you're trying to get at. This is a firmware bug. Period. And there's no solution in Xen, just a workaround (to use another reboot method). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 --- Comment #13 from lynda t <lyndat3@your-mail.com> ---
I have no idea what you're trying to get at. This is a firmware bug. Period. And there's no solution in Xen, just a workaround (to use another reboot method).
I'm not trying to 'get at' anything. You asked a question, I answered. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 lynda t <lyndat3@your-mail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|lyndat3@your-mail.com | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 lynda t <lyndat3@your-mail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX |--- Summary|Xen4.5+kernel-xen- |patched |3.19.3-3.1 PANIC on every |Xen4.5(4.5.0_03-368.1)+kern |reboot, "Panic on CPU 0: |el--xen(4.0.0-4.g27299c0) |FATAL PAGE FAULT" |PANIC on every reboot, | |"Panic on CPU 0: FATAL PAGE | |FAULT" --- Comment #14 from lynda t <lyndat3@your-mail.com> ---
As suspected the area is not marked for runtime mapping:
(XEN) 000009e6c4000-000009e6ddfff type=0 attr=000000000000000f
Hence this is a firmware bug.
The workaround mentioned is already in the upstream trees for 4.5.1 and 4.4.3, and hence will become available eventually via maintenance update.
Not here, but I had mailed it to you in the list conversation: http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=c643fb110a51693e82a3...
Backport of referenced workaround applied https://bugzilla.suse.com/show_bug.cgi?id=928783 No change in behavior "still fails, requiring manual reset, per original report" Redirected back to here "You are correct that this bug is complete. Sorry, but you can't take this bug and evolve it into what is essentially the other bug. You may continue that discussion there and see what Jan has to say." -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 Jan Beulich <jbeulich@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lyndat3@your-mail.com Flags| |needinfo?(lyndat3@your-mail | |.com) --- Comment #15 from Jan Beulich <jbeulich@suse.com> --- I have no idea why you opened that other bug in the first place - it effectively is a duplicate of this one, just worded completely differently. And - as so many times before - the stripped down hypervisor log you provided there to support your claim of "still doesn't work" has too much information removed. In particular I thus cannot verify whether you actually made use of the added workaround (new command line option). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 --- Comment #16 from lynda t <lyndat3@your-mail.com> --- Could you please consider not constantly inflaming discussions with your "I have no idea why you ...". Frankly, I don't care that you don't have any idea why. Your little snit-fits are making it really difficult to want to continue to help. If you'd like an answer, just ask politely for a change. If you can't manage -- then just keep it to yourself. As to the specific issue of opening the other bug -- since you 'asked', more or less -- I opened it to make the backport request separately from this issue. First, it seemed more efficient. It proved to be, as Charles quickly and politely addressed it. Case closed. And it was eminently clear that YOU weren't going to do a thing about it here. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 --- Comment #17 from Jan Beulich <jbeulich@suse.com> --- (In reply to lynda t from comment #16)
Could you please consider not constantly inflaming discussions with your "I have no idea why you ...".
I'm sorry if this came over offending. To me, opening a 2nd bug for the same issue looks like spamming bugzilla. (In fact, even if it wasn't you who opened the first one we'd expect you to look for bugs matching your problem before opening a new one.) Plus you report the problem against a Xen version not in any openSUSE release, i.e. apart from this being a firmware bug (and hence you rather needing to push your hardware vendor for a firmware update) I don't think it is a valid expectation for us to have a workaround for you available immediately. For such expectations I think you'd need to pay for a SLE support contract.
I opened it to make the backport request separately from this issue.
First, it seemed more efficient. It proved to be, as Charles quickly and politely addressed it. Case closed.
And it was eminently clear that YOU weren't going to do a thing about it here.
This is clearly wrong: I _am_ doing things to help this, just perhaps in a way not visible to you. As the upstream stable tree maintainer, I am making sure that 4.5.1 will have the change (unless a regression would be found with it), and that it will get released in as timely a manner as possible. Considering all of the above, this necessarily means that you either have to be a little patient, or apply the workaround on your own until an official update is available. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 --- Comment #18 from lynda t <lyndat3@your-mail.com> --- expectation? immediately? patient? SERIOUSLY? THAT is your 'message'? I'm busting my rear end just as much as anyone trying to help find & work through this current brokenness, as well as in a lot of other places. My timeframe is my business. If I want to try tom communicate effectively with others, that's frankly none of your concern. I'm not getting paid for MY time either, and I'm sure as hell not in the mood to take abuse on top of it. So much for the spirit of community, right? Don't fix your product. I've just about had it, and don't really care any more. And please don't act like you, the company, etc don't also benefit from our work. Find your bugs on your own. Hopefully before they make it into your COMMERCIAL offering. The fact is stuff is broken. Lots of it has been for a long time. I chose to contribute to try and help. And that's what I've been doing. Can't really remember why, now. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 Mike Latimer <mlatimer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mlatimer@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 Jan Beulich <jbeulich@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mlatimer@suse.com | |) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 Mike Latimer <mlatimer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(clatragasl@throam | |.com), | |needinfo?(mlatimer@suse.com | |) | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 Mike Latimer <mlatimer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #22 from Mike Latimer <mlatimer@suse.com> --- The workaround for this firmware bug is committed and does appear to resolve this issue. (We have no debug logs showing the failure with the kernel parameter in place.) As such, it is safe to mark this as closed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926594 Martin Pluskal <mpluskal@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpluskal@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com