I have tested the proposed kernel and it works for me. Thanks!
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
This bug was fixed in the package linux - 4.4.0-59.80
---
linux (4.4.0-59.80) xenial; urgency=low
[ John Donnelly ]
* Release Tracking Bug
- LP: #1654282
* [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails (LP: #1651602)
- (fix) nvme: only require 1 interrupt vec
Yeah I will get it done now.
--
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 lin
Hello Ross,
can you help us to verify this fix while you're back?
Thanks!
--
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 pa
I'm not able to test this for a couple of weeks due to the holiday
period.
--
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 p
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
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 l
> 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
backpo
https://lists.ubuntu.com/archives/kernel-team/2016-December/081443.html
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Ro
I've run the required command and I've set the status to Confirmed. The
logs won't have much useful in it because the crash is really early on
boot.
Anyway, the following commit should fix the issue:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/x86/xen?id=707e59ba494
apport information
** Tags added: apport-collected xenial
** Description changed:
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:121
FWIW, here is the full boot log (it crashes very early):
[0.014281] Freeing SMP alternatives memory: 28K (820b2000 -
820b9000)
[0.021560] ftrace: allocating 31878 entries in 125 pages
[0.248098] smpboot: Max logical packages: 15
[0.248123] smpboot: APIC(0) Convertin
12 matches
Mail list logo
