[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

You are right. There is no such bug in 3.13.0-92 kernel for Trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593621 Title: Kernel panic after migration between XenServer 6.5 hosts To manage

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

The 3.19(lts-vivid) kernel is now EOL, so marking that as wont fix. However, the Trusty 3.13 kernel is still supported. I just wanted to confirm you are not seeing this bug on Trusty using the 3.13 kernel? ** Changed in: linux-lts-vivid (Ubuntu) Status: In Progress => Won't Fix **

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

** No longer affects: linux (Ubuntu Trusty) ** Also affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-lts-vivid (Ubuntu) Status: New => In Progress ** Changed in: linux-lts-vivid (Ubuntu Xenial) Status: New => In Progress **

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593621 Title: Kernel panic after migration between XenServer 6.5 hosts

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

Tried 14.04 with 3.19.0-65 kernel. The issue still present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593621 Title: Kernel panic after migration between XenServer 6.5 hosts To manage

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

>>This appears to be fixed in Xenial (16.04) already. Can you confirm? Yes, migration of Ubuntu 16.04 4.4.0-21-generic #37 works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593621 Title:

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

Commit f0f393877c has not landed in upstream 3.13.y and it is now EOL. I'll SRU it to Trusty (14.04) for inclusion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593621 Title: Kernel panic after

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

This appears to be fixed in Xenial (16.04) already. Can you confirm? d0d15b8 xen/events: Don't move disabled irqs git describe --contains d0d15b8 Ubuntu-4.4.0-25.44~31 ** Changed in: linux (Ubuntu Trusty) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status:

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

We have tried patch f0f393877c71ad227d36705d61d1e4062bc29cf5 Seems it's work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593621 Title: Kernel panic after migration between XenServer 6.5 hosts

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

The commit indicated by your bisect was introduced into mainline as of 4.6-rc3 as: ff1e22e xen/events: Mask a moving irq It made its way into the 3.19 and 4.4 stable kernels because it was cc'd to stable. However, it looks like the regression was already fixed in 4.4.14 per your testing results

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

I'll bet this bug was fixed by the following commit, which was cc'd to stable: commit f0f393877c71ad227d36705d61d1e4062bc29cf5 Author: Ross Lagerwall Date: Tue May 10 16:11:00 2016 +0100 xen/events: Don't move disabled irqs ** Also affects: linux (Ubuntu

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

Bisect result: cab4604d2bb86315c120630af75a5f012e476596 is the first bad commit commit cab4604d2bb86315c120630af75a5f012e476596 Author: Boris Ostrovsky Date: Fri Mar 18 10:11:07 2016 -0400 xen/events: Mask a moving irq BugLink:

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

** Changed in: linux (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593621 Title: Kernel panic after migration between XenServer 6.5 hosts To manage

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

Installed v4.4.14 xenial kernel on trusty and verified. It works. No more crashes after migration. Kernel: 4.4.14-040414-generic DISTRIB_CODENAME: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

Hello all, I have probably same issue (freeze on Xenserver 6.5 with timekeeper.c in backtrace) when unsuspending 14.04 VMs with 3.19 kernels. To determine latest stable kernel version I've tested following versions of kernel package: linux-image-3.19.0-56-generic - Unsuspend works, XenMotion -

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

Installed v4.7-rc3-yakkety kernel on trusty and verified. It works. No more crashes after migration. Kernel: 4.7.0-040700rc3-generic DISTRIB_CODENAME: trusty ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

If this bug is not fixed in mainline, we can bisect between 3.19.0-49 and 3.19.0-61 to find the commit that introduced the regression. ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

Same on XenServer 7.0 and Ubuntu Kernel 4.4.0-24-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593621 Title: Kernel panic after migration between XenServer 6.5 hosts To manage

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

apport information ** Tags added: apport-collected trusty ** Description changed: Problem: after live migration from one XenServer 6.5 server to another XenServer 6.5 the Ubuntu VM crashes (see attached screenshot). Affected verions (at least): 1. Ubuntu 14.04 (3.19.0-61-generic)

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593621 Title: Kernel panic after migration between XenServer 6.5 hosts To manage notifications about

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people