Created attachment 663919 [details]
Console log showing hang
The latest versions of Tumbleweed, with a pvops enabled -default kernel, are
hanging when installing as a paravirtual guest under Xen. I can reproduce the
problem on a SLES12SP1 host and a Tumbleweed host.
The console log shows a couple of warnings, but the one which appears to be
resulting in the hang is:
[ 3.822185] ------------[ cut here ]------------
[ 3.822198] WARNING: CPU: 0 PID: 1 at ../arch/x86/xen/multicalls.c:129
xen_mc_flush+0x1c5/0x1d0()
[ 3.822204] Modules linked in: sunrpc crct10dif_pclmul crc32_pclmul
crc32c_intel aesni_intel aes_x86_64 xen_netfront xen_blkfront lrw gf128mul
glue_helper ablk_helper cryptd scsi_dh_rdac scsi_dh_emc scsi_dh_alua squashfs
loop
[ 3.822223] CPU: 0 PID: 1 Comm: init Tainted: G W
4.4.0-2-default #1
[ 3.822232] ffffffff81a47911 ffff88003e2cbc10 ffffffff8137f629
0000000000000000
[ 3.822238] ffff88003e2cbc48 ffffffff8107d132 ffff88003f80a2e0
0000000000000001
[ 3.822246] 00007f39dd70a000 0000000000000000 00007f39dd70a000
ffff88003e2cbc58
[ 3.822252] Call Trace:
[ 3.822262] [<ffffffff8101a095>] try_stack_unwind+0x175/0x190
[ 3.822270] [<ffffffff81018fe9>] dump_trace+0x69/0x3a0
[ 3.822275] [<ffffffff8101a0fb>] show_trace_log_lvl+0x4b/0x60
[ 3.822281] [<ffffffff8101942c>] show_stack_log_lvl+0x10c/0x180
[ 3.822286] [<ffffffff8101a195>] show_stack+0x25/0x50
[ 3.822291] [<ffffffff8137f629>] dump_stack+0x4b/0x72
[ 3.822300] [<ffffffff8107d132>] warn_slowpath_common+0x82/0xc0
[ 3.822307] [<ffffffff8107d22a>] warn_slowpath_null+0x1a/0x20
[ 3.822313] [<ffffffff81006b05>] xen_mc_flush+0x1c5/0x1d0
[ 3.822319] [<ffffffff81007365>] xen_leave_lazy_mmu+0x15/0x30
[ 3.822325] [<ffffffff811b637d>] remap_pfn_range+0x34d/0x430
[ 3.822335] [<ffffffff81495b9f>] mmap_mem+0xcf/0x120
[ 3.822343] [<ffffffff811bc867>] mmap_region+0x3f7/0x680
[ 3.822349] [<ffffffff811bce23>] do_mmap+0x333/0x420
[ 3.822356] [<ffffffff811a33f1>] vm_mmap_pgoff+0x91/0xc0
[ 3.822362] [<ffffffff811bb1ff>] SyS_mmap_pgoff+0x19f/0x260
[ 3.822369] [<ffffffff8101c0db>] SyS_mmap+0x1b/0x30
[ 3.822377] [<ffffffff816aa076>] entry_SYSCALL_64_fastpath+0x16/0x75
[ 3.823451] DWARF2 unwinder stuck at entry_SYSCALL_64_fastpath+0x16/0x75
[ 3.823456]
[ 3.823458] Leftover inexact backtrace:
[ 3.823458]
[ 3.823464] ---[ end trace 17b394fd426e244c ]---
Juergen looked at the logs and believed that the system is trying to setup the
framebuffer, and there was a negative return code from a hypercall. He also
believes the installation kernel appears to be okay, so this may be due to a
problem in the install initrd.