> It seems like an obvious fix. Both call traces look identical. I can > certainly produce a test kernel and get the reporter to produce some > results.
Just to be clear, both call traces look identical because I wrote that patch to fix this particular issue, but unfortunately didn't get it backported to the stable releases. I'm not sure why we haven't seen it on trusty. Perhaps some initialization ordering or kernel config options changed which exposed the race. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649821 Title: Boot crash in xen_send_IPI_one Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: Every hundred boots or so when booting Ubuntu 16.04 under Xen, it crashes early on boot with the following stack trace: kernel BUG at /build/linux-Ay7j_C/linux-4.4.0/drivers/xen/events/events_base.c:1210! invalid opcode: 0000 [#1] SMP ... RIP: 0010:[<ffffffff814c97c9>] [<ffffffff814c97c9>] xen_send_IPI_one+0x59/0x60 ... Call Trace: [<ffffffff8102be9e>] xen_qlock_kick+0xe/0x10 [<ffffffff810cabc2>] __pv_queued_spin_unlock+0xb2/0xf0 [<ffffffff810ca6d1>] ? __raw_callee_save___pv_queued_spin_unlock+0x11/0x20 [<ffffffff81052936>] ? check_tsc_warp+0x76/0x150 [<ffffffff81052aa6>] check_tsc_sync_source+0x96/0x160 [<ffffffff81051e28>] native_cpu_up+0x3d8/0x9f0 [<ffffffff8102b315>] xen_hvm_cpu_up+0x35/0x80 [<ffffffff8108198c>] _cpu_up+0x13c/0x180 [<ffffffff81081a4a>] cpu_up+0x7a/0xa0 [<ffffffff81f80dfc>] smp_init+0x7f/0x81 [<ffffffff81f5a121>] kernel_init_freeable+0xef/0x212 [<ffffffff81817f30>] ? rest_init+0x80/0x80 [<ffffffff81817f3e>] kernel_init+0xe/0xe0 [<ffffffff8182488f>] ret_from_fork+0x3f/0x70 [<ffffffff81817f30>] ? rest_init+0x80/0x80 This is fixed by the following commit: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/x86/xen?id=707e59ba494372a90d245f18b0c78982caa88e48 Unfortunately this wasn't backported to Linux 4.4. Can you please include this in the next Ubuntu 16.04 kernel release? Thanks Ross --- AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Dec 14 11:48 seq crw-rw---- 1 root audio 116, 33 Dec 14 11:48 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=637c02d7-6135-4ecc-8273-b014d21cf217 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Xen HVM domU Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=6748a82f-b075-401e-ac74-0ebe865003f2 ro console=hvc0 console=tty0 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 RelatedPackageVersions: linux-restricted-modules-4.4.0-53-generic N/A linux-backports-modules-4.4.0-53-generic N/A linux-firmware 1.157.5 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/07/2016 dmi.bios.vendor: Xen dmi.bios.version: 4.7.1-xs131890-d dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.7.1-xs131890-d:bd12/07/2016:svnXen:pnHVMdomU:pvr4.7.1-xs131890-d:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.7.1-xs131890-d dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
