Mike Latimer changed bug 964342
What Removed Added
Flags needinfo?(mlatimer@suse.com)  

Comment # 18 on bug 964342 from
(In reply to Olaf Hering from comment #17)
> (In reply to Mike Latimer from comment #15)
> > Reopening until we get a complete solution.
> 
> I think for testing it is required to build
> system:install:head/installation-images locally with 'osc build
> --userootforbuild' and use linux/initrd from the resulting binary packages.

Thanks for the tip. I followed your advice and tested a local build. The
problem I pointed out in comment #14 did not occur (so that is good). However,
I then encountered the following situation:

[    3.866285] input: Xen Virtual Keyboard as /devices/virtual/input/input0
[    3.866384] input: Xen Virtual Pointer as /devices/virtual/input/input1
[    3.871274] udevd[215]: failed to execute
'/usr/lib/systemd/systemd-vconsole-setup'
'/usr/lib/systemd/systemd-vconsole-setup': No such file or directory
[    3.871595] udevd[191]: Process '/usr/lib/systemd/systemd-vconsole-setup'
failed with exit code 2.
ok

This issue is easily resolved with something like (which will need to be pushed
upstream):

diff -Nurp a/data/initrd/initrd.file_list b/data/initrd/initrd.file_list
--- a/data/initrd/initrd.file_list      2016-02-22 15:33:21.829186121 -0700
+++ b/data/initrd/initrd.file_list      2016-02-22 15:33:07.097170345 -0700
@@ -366,6 +366,7 @@ procps:

 # maybe we don't need everything...
 systemd:
+  /usr/lib/systemd/systemd-vconsole-setup
   /usr/bin/systemd-detect-virt
   /usr/lib/systemd/systemd-sysctl
   /usr/lib*/libsystemd*.so.*

However, after fixing that issue, there are no further errors or warnings about
xen drivers, and I am still encountering the crash reported in comment #0:

[    4.945829] ------------[ cut here ]------------
[    4.945883] WARNING: CPU: 0 PID: 1 at ../arch/x86/xen/multicalls.c:129
xen_mc_flush+0x1c5/0x1d0()
[    4.945936] Modules linked in: sunrpc xen_kbdfront xen_fbfront syscopyarea
sysfillrect sysimgblt xen_netfront fb_sys_fops xen_blkfront crc32c_intel
scsi_dh_rdac scsi_dh_emc scsi_dh_alua squashfs loop
[    4.948886] CPU: 0 PID: 1 Comm: init Not tainted 4.4.1-1-default #1
[    4.949854]  ffffffff81a47959 ffff88003e2cbc10 ffffffff8137ea59
0000000000000000
[    4.950851]  ffff88003e2cbc48 ffffffff8107c552 ffff88003f80a2e0
0000000000000001
[    4.951829]  00007f831908b000 0000000000000000 00007f831908b000
ffff88003e2cbc58
[    4.952826] Call Trace:
[    4.953778]  [<ffffffff8101a095>] try_stack_unwind+0x175/0x190
[    4.954737]  [<ffffffff81018fe9>] dump_trace+0x69/0x3a0
[    4.955670]  [<ffffffff8101a0fb>] show_trace_log_lvl+0x4b/0x60
[    4.956596]  [<ffffffff8101942c>] show_stack_log_lvl+0x10c/0x180
[    4.957511]  [<ffffffff8101a195>] show_stack+0x25/0x50
[    4.958410]  [<ffffffff8137ea59>] dump_stack+0x4b/0x72
[    4.959295]  [<ffffffff8107c552>] warn_slowpath_common+0x82/0xc0
[    4.960346]  [<ffffffff8107c64a>] warn_slowpath_null+0x1a/0x20
[    4.961227]  [<ffffffff81006b05>] xen_mc_flush+0x1c5/0x1d0
[    4.962109]  [<ffffffff81007365>] xen_leave_lazy_mmu+0x15/0x30
[    4.962987]  [<ffffffff811b581d>] remap_pfn_range+0x34d/0x430
[    4.963864]  [<ffffffff81494f6f>] mmap_mem+0xcf/0x120
[    4.964744]  [<ffffffff811bbd07>] mmap_region+0x3f7/0x680
[    4.965598]  [<ffffffff811bc2c3>] do_mmap+0x333/0x420
[    4.966437]  [<ffffffff811a2891>] vm_mmap_pgoff+0x91/0xc0
[    4.967260]  [<ffffffff811ba69f>] SyS_mmap_pgoff+0x19f/0x260
[    4.968080]  [<ffffffff8101c0db>] SyS_mmap+0x1b/0x30
[    4.968880]  [<ffffffff816a94f6>] entry_SYSCALL_64_fastpath+0x16/0x75
[    4.972514] DWARF2 unwinder stuck at entry_SYSCALL_64_fastpath+0x16/0x75
[    4.973327] 
[    4.974107] Leftover inexact backtrace:
[    4.974107] 
[    4.975646] ---[ end trace c909cd4ca9382cdf ]---

In other words, all of these changes have been helpful, but not directly
related to the crash.


You are receiving this mail because: