[Kernel-packages] [Bug 1427075] Re: Stopping and starting KVM partitions results in guest kernel softlockup
This bug was fixed in the package linux - 3.19.0-12.12 --- linux (3.19.0-12.12) vivid; urgency=low [ Andy Whitcroft ] * [Packaging] do_common_tools should always be on * [Packaging] Provides: virtualbox-guest-modules when appropriate - LP: #1434579 [ Chris J Arges ] * Revert "SAUCE: ext4: disable ext4_punch_hole for indirect filesystems" - LP: #1292234 [ Leann Ogasawara ] * Release Tracking Bug - LP: #1439803 [ Timo Aaltonen ] * SAUCE: i915_bpo: Provide a backport driver for Skylake & Cherryview graphics - LP: #1420774 * SAUCE: i915_bpo: Update intel_ips.h file location - LP: #1420774 * SAUCE: i915_bpo: Only support Skylake and Cherryview with the backport driver - LP: #1420774 * SAUCE: i915_bpo: Rename the backport driver to i915_bpo - LP: #1420774 * i915_bpo: [Config] Enable CONFIG_DRM_I915_BPO=m - LP: #1420774 * SAUCE: i915_bpo: Add i915_bpo_*() calls for ubuntu/i915 - LP: #1420774 * SAUCE: i915_bpo: Revert "drm/i915: remove unused power_well/get_cdclk_freq api" - LP: #1420774 * SAUCE: i915_bpo: Add i915_bpo specific power well calls - LP: #1420774 * SAUCE: Backport I915_PARAM_MMAP_VERSION and I915_MMAP_WC - LP: #1420774 * SAUCE: Partial backport of drm/i915: Add ioctl to set per-context parameters - LP: #1420774 * SAUCE: drm/i915: Specify bsd rings through exec flag - LP: #1420774 * SAUCE: drm/i915: add I915_PARAM_HAS_BSD2 to i915_getparam - LP: #1420774 * SAUCE: drm/i915: add component support - LP: #1420774 * SAUCE: drm/i915: Add tiled framebuffer modifiers - LP: #1420774 * SAUCE: Backport new displayable tiling formats - LP: #1420774 * SAUCE: Backport drm_crtc_vblank_reset() helper - LP: #1420774 * SAUCE: drm/i915: Add I915_PARAM_REVISION - LP: #1420774 * SAUCE: drm/i915: Export total subslice and EU counts - LP: #1420774 * SAUCE: i915_bpo: Revert drm/mm: Support 4 GiB and larger ranges - LP: #1420774 [ Upstream Kernel Changes ] * drm/i915/skl: Split the SKL PCI ids by GT - LP: #1420774 * drm: Reorganize probed mode validation - LP: #1420774 * drm: Perform basic sanity checks on probed modes - LP: #1420774 * drm: Do basic sanity checks for user modes - LP: #1420774 * drm/atomic-helper: Export both plane and modeset check helpers - LP: #1420774 * drm/atomic-helper: Again check modeset *before* plane states - LP: #1420774 * drm/atomic: Introduce state->obj backpointers - LP: #1420774 * drm: allow property validation for refcnted props - LP: #1420774 * drm: store property instead of id in obj attachment - LP: #1420774 * drm: get rid of direct property value access - LP: #1420774 * drm: add atomic_set_property wrappers - LP: #1420774 * drm: tweak getconnector locking - LP: #1420774 * drm: add atomic_get_property - LP: #1420774 * drm: Remove unneeded braces for single statement blocks - LP: #1420774 * drm: refactor getproperties/getconnector - LP: #1420774 * drm: add atomic properties - LP: #1420774 * drm/atomic: atomic_check functions - LP: #1420774 * drm: small property creation cleanup - LP: #1420774 * drm/atomic: atomic plane properties - LP: #1420774 * drm/atomic: atomic connector properties - LP: #1420774 * drm: Atomic modeset ioctl - LP: #1420774 * drm/atomic: Hide drm.ko internal interfaces - LP: #1420774 * drm: Ensure universal_planes is set for atomic - LP: #1420774 * drm: fix mismerge in drm_crtc.c - LP: #1420774 * drm: bit of spell-check / editorializing. - LP: #1420774 * drm: add support for tiled/compressed/etc modifier in addfb2 - LP: #1420774 * drm: Add rotation value to plane state - LP: #1420774 * drm: add helper to get crtc timings (v5) - LP: #1420774 * drm: Adding edp1.4 specific dpcd macros - LP: #1420774 * drm/plane-helper: Skip prepare_fb/cleanup_fb when newfb==oldfb - LP: #1420774 * next: drm/atomic: Use copy_from_user to copy 64 bit data from user space - LP: #1420774 * powerpc: Add PVR for POWER8NVL processor - LP: #1438938 * kernel/sched/clock.c: add another clock for use with the soft lockup watchdog - LP: #1427075 * powerpc: add running_clock for powerpc to prevent spurious softlockup warnings - LP: #1427075 * ext4: fix indirect punch hole corruption - LP: #1292234 * fm10k: Clean-up page reuse code - LP: #1397863 * net/fm10k: Avoid double setting of NETIF_F_SG for the HW encapsulation feature mask - LP: #1397863 * fm10k: Check tunnel header length in encap offload - LP: #1397863 * fm10k: Increase the timeout for the data path reset - LP: #1397863 * fm10k: Validate VLAN ID in fm10k_update_xc_addr_pf - LP: #1397863 * fm10k: Resolve compile warnings with W=1 - LP: #1397863 * UBUNTU Config: CONFIG_IXGBE_VXLAN=y - LP: #1397861 * ixgbe:
[Kernel-packages] [Bug 1427075] Re: Stopping and starting KVM partitions results in guest kernel softlockup
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1427075 Title: Stopping and starting KVM partitions results in guest kernel softlockup Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] Stop/continue via qemu monitor can easily trigger soft-lockups due to incorrect VM timekeeping. [Test Case] On a single CPU KVM guest: yes > /dev/null & Followed by (qemu) stop Wait a while, then: (qemu) cont [Fix] The following commits upstream: commit 545a2bf742fb41f17d03486dd8a8c74ad511dec2 commit 4be1b29795d692d512bb67b770665d6f8ea5cb0b -- == Comment: #0 - Cyril Bur - 2015-02-23 18:03:41 == +++ This bug was initially created as a clone of Bug #108455 +++ I was investigating the cause of some ppc64le KVM guest softlockup warnings. On a single CPU KVM guest, I ran something to keep the guest busy: yes > /dev/null & Followed by (qemu) stop Wait a while, then: (qemu) cont We get a softlockup error: BUG: soft lockup - CPU#0 stuck for 9220s! [yes:2389] .__getnstimeofday .getnstimeofday .ktime_get_real .netif_receive_skb .ibmveth_poll .net_rx_action .__do_softirq .irq_exit .__do_irq .call_do_irq .do_IRQ I was going to file it away in the "don't do that" bin, but I notice x86 have something to detect a paused VM and avoid spewing the soft lockup error. Do we need something like this on ppc64? commit 5d1c0f4a80a6df73395fb3fc2c302510f8f09d36 Author: Eric B Munson Date: Sat Mar 10 14:37:28 2012 -0500 watchdog: add check for suspended vm in softlockup detector A suspended VM can cause spurious soft lockup warnings. To avoid these, the watchdog now checks if the kernel knows it was stopped by the host and skips the warning if so. When the watchdog is reset successfully, clear the guest paused flag. == Comment: #1 - Cyril Bur - 2015-02-23 18:03:55 == Hi, I have been working on a fix for guest kernels. This requires two patches: 1/2 commit 545a2bf742fb41f17d03486dd8a8c74ad511dec2 Author: Cyril Bur Date: Thu Feb 12 15:01:24 2015 -0800 kernel/sched/clock.c: add another clock for use with the soft lockup watchdog and 2/2 commit 4be1b29795d692d512bb67b770665d6f8ea5cb0b Author: Cyril Bur Date: Thu Feb 12 15:01:28 2015 -0800 powerpc: add running_clock for powerpc to prevent spurious softlockup warnings Both are in upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427075/+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
[Kernel-packages] [Bug 1427075] Re: Stopping and starting KVM partitions results in guest kernel softlockup
Does this fix need to be applied to 3.16 as well? Or is backporting to Vivid/3.19 sufficient? ** Description changed: + [Impact] + Stop/continue via qemu monitor can easily trigger soft-lockups due to incorrect VM timekeeping. + + [Test Case] + On a single CPU KVM guest: + yes > /dev/null & + + Followed by + (qemu) stop + + Wait a while, then: + (qemu) cont + + [Fix] + The following commits upstream: + commit 545a2bf742fb41f17d03486dd8a8c74ad511dec2 + commit 4be1b29795d692d512bb67b770665d6f8ea5cb0b + + -- + == Comment: #0 - Cyril Bur - 2015-02-23 18:03:41 == +++ This bug was initially created as a clone of Bug #108455 +++ I was investigating the cause of some ppc64le KVM guest softlockup warnings. On a single CPU KVM guest, I ran something to keep the guest busy: yes > /dev/null & Followed by (qemu) stop Wait a while, then: (qemu) cont We get a softlockup error: BUG: soft lockup - CPU#0 stuck for 9220s! [yes:2389] .__getnstimeofday .getnstimeofday .ktime_get_real .netif_receive_skb .ibmveth_poll .net_rx_action .__do_softirq .irq_exit .__do_irq .call_do_irq .do_IRQ I was going to file it away in the "don't do that" bin, but I notice x86 have something to detect a paused VM and avoid spewing the soft lockup error. Do we need something like this on ppc64? commit 5d1c0f4a80a6df73395fb3fc2c302510f8f09d36 Author: Eric B Munson Date: Sat Mar 10 14:37:28 2012 -0500 - watchdog: add check for suspended vm in softlockup detector + watchdog: add check for suspended vm in softlockup detector - A suspended VM can cause spurious soft lockup warnings. To avoid these, the - watchdog now checks if the kernel knows it was stopped by the host and skips - the warning if so. When the watchdog is reset successfully, clear the guest - paused flag. + A suspended VM can cause spurious soft lockup warnings. To avoid these, the + watchdog now checks if the kernel knows it was stopped by the host and skips + the warning if so. When the watchdog is reset successfully, clear the guest + paused flag. == Comment: #1 - Cyril Bur - 2015-02-23 18:03:55 == Hi, I have been working on a fix for guest kernels. This requires two patches: 1/2 commit 545a2bf742fb41f17d03486dd8a8c74ad511dec2 Author: Cyril Bur Date: Thu Feb 12 15:01:24 2015 -0800 - kernel/sched/clock.c: add another clock for use with the soft lockup + kernel/sched/clock.c: add another clock for use with the soft lockup watchdog - and 2/2 commit 4be1b29795d692d512bb67b770665d6f8ea5cb0b Author: Cyril Bur Date: Thu Feb 12 15:01:28 2015 -0800 - powerpc: add running_clock for powerpc to prevent spurious + powerpc: add running_clock for powerpc to prevent spurious softlockup warnings Both are in upstream. -- 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/1427075 Title: Stopping and starting KVM partitions results in guest kernel softlockup Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Stop/continue via qemu monitor can easily trigger soft-lockups due to incorrect VM timekeeping. [Test Case] On a single CPU KVM guest: yes > /dev/null & Followed by (qemu) stop Wait a while, then: (qemu) cont [Fix] The following commits upstream: commit 545a2bf742fb41f17d03486dd8a8c74ad511dec2 commit 4be1b29795d692d512bb67b770665d6f8ea5cb0b -- == Comment: #0 - Cyril Bur - 2015-02-23 18:03:41 == +++ This bug was initially created as a clone of Bug #108455 +++ I was investigating the cause of some ppc64le KVM guest softlockup warnings. On a single CPU KVM guest, I ran something to keep the guest busy: yes > /dev/null & Followed by (qemu) stop Wait a while, then: (qemu) cont We get a softlockup error: BUG: soft lockup - CPU#0 stuck for 9220s! [yes:2389] .__getnstimeofday .getnstimeofday .ktime_get_real .netif_receive_skb .ibmveth_poll .net_rx_action .__do_softirq .irq_exit .__do_irq .call_do_irq .do_IRQ I was going to file it away in the "don't do that" bin, but I notice x86 have something to detect a paused VM and avoid spewing the soft lockup error. Do we need something like this on ppc64? commit 5d1c0f4a80a6df73395fb3fc2c302510f8f09d36 Author: Eric B Munson Date: Sat Mar 10 14:37:28 2012 -0500 watchdog: add check for suspended vm in softlockup detector A suspended VM can cause spurious soft lockup warnings. To avoid these, the watchdog now checks if the kernel knows it was stopped by the host and skips the warning if so. When the watchdog is reset successfully, clear the guest paused flag. == Comment: #1 - Cyril Bur - 2015-02-23 18:03:55 == Hi, I have been working on a fix for guest
[Kernel-packages] [Bug 1427075] Re: Stopping and starting KVM partitions results in guest kernel softlockup
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Chris J Arges (arges) -- 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/1427075 Title: Stopping and starting KVM partitions results in guest kernel softlockup Status in linux package in Ubuntu: Confirmed Bug description: == Comment: #0 - Cyril Bur - 2015-02-23 18:03:41 == +++ This bug was initially created as a clone of Bug #108455 +++ I was investigating the cause of some ppc64le KVM guest softlockup warnings. On a single CPU KVM guest, I ran something to keep the guest busy: yes > /dev/null & Followed by (qemu) stop Wait a while, then: (qemu) cont We get a softlockup error: BUG: soft lockup - CPU#0 stuck for 9220s! [yes:2389] .__getnstimeofday .getnstimeofday .ktime_get_real .netif_receive_skb .ibmveth_poll .net_rx_action .__do_softirq .irq_exit .__do_irq .call_do_irq .do_IRQ I was going to file it away in the "don't do that" bin, but I notice x86 have something to detect a paused VM and avoid spewing the soft lockup error. Do we need something like this on ppc64? commit 5d1c0f4a80a6df73395fb3fc2c302510f8f09d36 Author: Eric B Munson Date: Sat Mar 10 14:37:28 2012 -0500 watchdog: add check for suspended vm in softlockup detector A suspended VM can cause spurious soft lockup warnings. To avoid these, the watchdog now checks if the kernel knows it was stopped by the host and skips the warning if so. When the watchdog is reset successfully, clear the guest paused flag. == Comment: #1 - Cyril Bur - 2015-02-23 18:03:55 == Hi, I have been working on a fix for guest kernels. This requires two patches: 1/2 commit 545a2bf742fb41f17d03486dd8a8c74ad511dec2 Author: Cyril Bur Date: Thu Feb 12 15:01:24 2015 -0800 kernel/sched/clock.c: add another clock for use with the soft lockup watchdog and 2/2 commit 4be1b29795d692d512bb67b770665d6f8ea5cb0b Author: Cyril Bur Date: Thu Feb 12 15:01:28 2015 -0800 powerpc: add running_clock for powerpc to prevent spurious softlockup warnings Both are in upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427075/+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
[Kernel-packages] [Bug 1427075] Re: Stopping and starting KVM partitions results in guest kernel softlockup
** Package changed: ubuntu => linux (Ubuntu) -- 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/1427075 Title: Stopping and starting KVM partitions results in guest kernel softlockup Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Cyril Bur - 2015-02-23 18:03:41 == +++ This bug was initially created as a clone of Bug #108455 +++ I was investigating the cause of some ppc64le KVM guest softlockup warnings. On a single CPU KVM guest, I ran something to keep the guest busy: yes > /dev/null & Followed by (qemu) stop Wait a while, then: (qemu) cont We get a softlockup error: BUG: soft lockup - CPU#0 stuck for 9220s! [yes:2389] .__getnstimeofday .getnstimeofday .ktime_get_real .netif_receive_skb .ibmveth_poll .net_rx_action .__do_softirq .irq_exit .__do_irq .call_do_irq .do_IRQ I was going to file it away in the "don't do that" bin, but I notice x86 have something to detect a paused VM and avoid spewing the soft lockup error. Do we need something like this on ppc64? commit 5d1c0f4a80a6df73395fb3fc2c302510f8f09d36 Author: Eric B Munson Date: Sat Mar 10 14:37:28 2012 -0500 watchdog: add check for suspended vm in softlockup detector A suspended VM can cause spurious soft lockup warnings. To avoid these, the watchdog now checks if the kernel knows it was stopped by the host and skips the warning if so. When the watchdog is reset successfully, clear the guest paused flag. == Comment: #1 - Cyril Bur - 2015-02-23 18:03:55 == Hi, I have been working on a fix for guest kernels. This requires two patches: 1/2 commit 545a2bf742fb41f17d03486dd8a8c74ad511dec2 Author: Cyril Bur Date: Thu Feb 12 15:01:24 2015 -0800 kernel/sched/clock.c: add another clock for use with the soft lockup watchdog and 2/2 commit 4be1b29795d692d512bb67b770665d6f8ea5cb0b Author: Cyril Bur Date: Thu Feb 12 15:01:28 2015 -0800 powerpc: add running_clock for powerpc to prevent spurious softlockup warnings Both are in upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427075/+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
