[Kernel-packages] [Bug 1465136] Re: NVMe shutdown and suspend delay time is too short
This bug was fixed in the package linux - 3.16.0-44.59 --- linux (3.16.0-44.59) utopic; urgency=low [ Brad Figg ] * Release Tracking Bug - LP: #1472030 [ Iyappan Subramanian ] * SAUCE: (no-up) drivers: net: xgene: fix: Out of order descriptor bytes read - LP: #1425576 [ Upstream Kernel Changes ] * Revert tools/vm: fix page-flags build - LP: #1471170 * NVMe: Add shutdown timeout as module parameter. - LP: #1465136 * Drivers: hv: vmbus: Add support for VMBus panic notifier handler - LP: #1463584 * Drivers: hv: vmbus: Correcting truncation error for constant HV_CRASH_CTL_CRASH_NOTIFY - LP: #1463584 * KVM: nVMX: fix lifetime issues for vmcs02 - LP: #1448269 * KVM: nVMX: Fix nested vmexit ack intr before load vmcs01 - LP: #1448269 * mm/slab_common: support the slub_debug boot option on specific object size - LP: #1456952 * kvm: x86: fix kvm_apic_has_events to check for NULL pointer * cpuidle: powernv: Populate cpuidle state details by querying the device-tree - LP: #1470404 * cpuidle: powernv: Read target_residency value of idle states from DT if available - LP: #1470404 * cpuidle: powernv: Avoid endianness conversions while parsing DT - LP: #1470404 * cpuidle: powernv/pseries: Auto-promotion of snooze to deeper idle state - LP: #1470404 * iio: adis16400: Report pressure channel scale - LP: #1471170 * iio: adis16400: Use != channel indices for the two voltage channels - LP: #1471170 * iio: adis16400: Compute the scan mask from channel indices - LP: #1471170 * iio: adis16400: Remove unused variable - LP: #1471170 * iio: adis16400: Fix burst mode - LP: #1471170 * iio: adis16400: Fix burst transfer for adis16448 - LP: #1471170 * USB: serial: ftdi_sio: Add support for a Motion Tracker Development Board - LP: #1471170 * iio: adc: twl6030-gpadc: Fix modalias - LP: #1471170 * serial: imx: Fix DMA handling for IDLE condition aborts - LP: #1471170 * usb: dwc3: gadget: Fix incorrect DEPCMD and DGCMD status macros - LP: #1471170 * ALSA: usb-audio: Add mic volume fix quirk for Logitech Quickcam Fusion - LP: #1471170 * n_tty: Fix auditing support for cannonical mode - LP: #1471170 * drm/i915/hsw: Fix workaround for server AUX channel clock divisor - LP: #1471170 * x86/asm/irq: Stop relying on magic JMP behavior for early_idt_handlers - LP: #1471170 * lib: Fix strnlen_user() to not touch memory after specified maximum - LP: #1471170 * Input: elantech - fix detection of touchpads where the revision matches a known rate - LP: #1471170 * ALSA: hda/realtek - Add a fixup for another Acer Aspire 9420 - LP: #1471170 * ALSA: usb-audio: add MAYA44 USB+ mixer control names - LP: #1471170 * ALSA: usb-audio: fix missing input volume controls in MAYA44 USB(+) - LP: #1471170 * USB: cp210x: add ID for HubZ dual ZigBee and Z-Wave dongle - LP: #1471170 * Input: elantech - add new icbody type - LP: #1471170 * MIPS: Fix enabling of DEBUG_STACKOVERFLOW - LP: #1471170 * xfrm: fix a race in xfrm_state_lookup_byspi - LP: #1471170 * kconfig: Fix warning ‘jump’ may be used uninitialized - LP: #1471170 * scripts/sortextable: suppress warning: `relocs_size' may be used uninitialized - LP: #1471170 * thermal: step_wise: Revert optimization - LP: #1471170 * MIPS: KVM: Do not sign extend on unsigned MMIO load - LP: #1471170 * arch/x86/kvm/mmu.c: work around gcc-4.4.4 bug - LP: #1471170 * net: core: Correct an over-stringent device loop detection. - LP: #1471170 * net: phy: Allow EEE for all RGMII variants - LP: #1471170 * net: dp83640: fix broken calibration routine. - LP: #1471170 * net: dp83640: reinforce locking rules. - LP: #1471170 * unix/caif: sk_socket can disappear when state is unlocked - LP: #1471170 * xen/netback: Properly initialize credit_bytes - LP: #1471170 * udp: fix behavior of wrong checksums - LP: #1471170 * xen: netback: read hotplug script once at start of day. - LP: #1471170 * ipv4/udp: Verify multicast group is ours in upd_v4_early_demux() - LP: #1471170 * bridge: disable softirqs around br_fdb_update to avoid lockup - LP: #1471170 * drm/i915: Assume dual channel LVDS if pixel clock necessitates it - LP: #1471170 * Btrfs: send, add missing check for dead clone root - LP: #1471170 * Btrfs: send, don't leave without decrementing clone root's send_progress - LP: #1471170 * btrfs: incorrect handling for fiemap_fill_next_extent return - LP: #1471170 * btrfs: cleanup orphans while looking up default subvolume - LP: #1471170 * iommu/vt-d: Allow RMRR on graphics devices too - LP: #1471170 * iommu/vt-d: Fix passthrough mode with translation-disabled devices - LP: #1471170 * ata: ahci_mvebu: Fix wrongly set base address for the MBus
[Kernel-packages] [Bug 1465136] Re: NVMe shutdown and suspend delay time is too short
This bug was fixed in the package linux-lts-utopic - 3.16.0-44.59~14.04.1 --- linux-lts-utopic (3.16.0-44.59~14.04.1) trusty; urgency=low [ Brad Figg ] * Release Tracking Bug - LP: #1472223 [ Iyappan Subramanian ] * SAUCE: (no-up) drivers: net: xgene: fix: Out of order descriptor bytes read - LP: #1425576 [ Upstream Kernel Changes ] * Revert tools/vm: fix page-flags build - LP: #1471170 * NVMe: Add shutdown timeout as module parameter. - LP: #1465136 * Drivers: hv: vmbus: Add support for VMBus panic notifier handler - LP: #1463584 * Drivers: hv: vmbus: Correcting truncation error for constant HV_CRASH_CTL_CRASH_NOTIFY - LP: #1463584 * KVM: nVMX: fix lifetime issues for vmcs02 - LP: #1448269 * KVM: nVMX: Fix nested vmexit ack intr before load vmcs01 - LP: #1448269 * mm/slab_common: support the slub_debug boot option on specific object size - LP: #1456952 * kvm: x86: fix kvm_apic_has_events to check for NULL pointer * cpuidle: powernv: Populate cpuidle state details by querying the device-tree - LP: #1470404 * cpuidle: powernv: Read target_residency value of idle states from DT if available - LP: #1470404 * cpuidle: powernv: Avoid endianness conversions while parsing DT - LP: #1470404 * cpuidle: powernv/pseries: Auto-promotion of snooze to deeper idle state - LP: #1470404 * iio: adis16400: Report pressure channel scale - LP: #1471170 * iio: adis16400: Use != channel indices for the two voltage channels - LP: #1471170 * iio: adis16400: Compute the scan mask from channel indices - LP: #1471170 * iio: adis16400: Remove unused variable - LP: #1471170 * iio: adis16400: Fix burst mode - LP: #1471170 * iio: adis16400: Fix burst transfer for adis16448 - LP: #1471170 * USB: serial: ftdi_sio: Add support for a Motion Tracker Development Board - LP: #1471170 * iio: adc: twl6030-gpadc: Fix modalias - LP: #1471170 * serial: imx: Fix DMA handling for IDLE condition aborts - LP: #1471170 * usb: dwc3: gadget: Fix incorrect DEPCMD and DGCMD status macros - LP: #1471170 * ALSA: usb-audio: Add mic volume fix quirk for Logitech Quickcam Fusion - LP: #1471170 * n_tty: Fix auditing support for cannonical mode - LP: #1471170 * drm/i915/hsw: Fix workaround for server AUX channel clock divisor - LP: #1471170 * x86/asm/irq: Stop relying on magic JMP behavior for early_idt_handlers - LP: #1471170 * lib: Fix strnlen_user() to not touch memory after specified maximum - LP: #1471170 * Input: elantech - fix detection of touchpads where the revision matches a known rate - LP: #1471170 * ALSA: hda/realtek - Add a fixup for another Acer Aspire 9420 - LP: #1471170 * ALSA: usb-audio: add MAYA44 USB+ mixer control names - LP: #1471170 * ALSA: usb-audio: fix missing input volume controls in MAYA44 USB(+) - LP: #1471170 * USB: cp210x: add ID for HubZ dual ZigBee and Z-Wave dongle - LP: #1471170 * Input: elantech - add new icbody type - LP: #1471170 * MIPS: Fix enabling of DEBUG_STACKOVERFLOW - LP: #1471170 * xfrm: fix a race in xfrm_state_lookup_byspi - LP: #1471170 * kconfig: Fix warning ‘jump’ may be used uninitialized - LP: #1471170 * scripts/sortextable: suppress warning: `relocs_size' may be used uninitialized - LP: #1471170 * thermal: step_wise: Revert optimization - LP: #1471170 * MIPS: KVM: Do not sign extend on unsigned MMIO load - LP: #1471170 * arch/x86/kvm/mmu.c: work around gcc-4.4.4 bug - LP: #1471170 * net: core: Correct an over-stringent device loop detection. - LP: #1471170 * net: phy: Allow EEE for all RGMII variants - LP: #1471170 * net: dp83640: fix broken calibration routine. - LP: #1471170 * net: dp83640: reinforce locking rules. - LP: #1471170 * unix/caif: sk_socket can disappear when state is unlocked - LP: #1471170 * xen/netback: Properly initialize credit_bytes - LP: #1471170 * udp: fix behavior of wrong checksums - LP: #1471170 * xen: netback: read hotplug script once at start of day. - LP: #1471170 * ipv4/udp: Verify multicast group is ours in upd_v4_early_demux() - LP: #1471170 * bridge: disable softirqs around br_fdb_update to avoid lockup - LP: #1471170 * drm/i915: Assume dual channel LVDS if pixel clock necessitates it - LP: #1471170 * Btrfs: send, add missing check for dead clone root - LP: #1471170 * Btrfs: send, don't leave without decrementing clone root's send_progress - LP: #1471170 * btrfs: incorrect handling for fiemap_fill_next_extent return - LP: #1471170 * btrfs: cleanup orphans while looking up default subvolume - LP: #1471170 * iommu/vt-d: Allow RMRR on graphics devices too - LP: #1471170 * iommu/vt-d: Fix passthrough mode with translation-disabled devices - LP: #1471170 * ata: ahci_mvebu: Fix
[Kernel-packages] [Bug 1465136] Re: NVMe shutdown and suspend delay time is too short
This bug was fixed in the package linux-lts-utopic - 3.16.0-44.59~14.04.1 --- linux-lts-utopic (3.16.0-44.59~14.04.1) trusty; urgency=low [ Brad Figg ] * Release Tracking Bug - LP: #1472223 [ Iyappan Subramanian ] * SAUCE: (no-up) drivers: net: xgene: fix: Out of order descriptor bytes read - LP: #1425576 [ Upstream Kernel Changes ] * Revert tools/vm: fix page-flags build - LP: #1471170 * NVMe: Add shutdown timeout as module parameter. - LP: #1465136 * Drivers: hv: vmbus: Add support for VMBus panic notifier handler - LP: #1463584 * Drivers: hv: vmbus: Correcting truncation error for constant HV_CRASH_CTL_CRASH_NOTIFY - LP: #1463584 * KVM: nVMX: fix lifetime issues for vmcs02 - LP: #1448269 * KVM: nVMX: Fix nested vmexit ack intr before load vmcs01 - LP: #1448269 * mm/slab_common: support the slub_debug boot option on specific object size - LP: #1456952 * kvm: x86: fix kvm_apic_has_events to check for NULL pointer * cpuidle: powernv: Populate cpuidle state details by querying the device-tree - LP: #1470404 * cpuidle: powernv: Read target_residency value of idle states from DT if available - LP: #1470404 * cpuidle: powernv: Avoid endianness conversions while parsing DT - LP: #1470404 * cpuidle: powernv/pseries: Auto-promotion of snooze to deeper idle state - LP: #1470404 * iio: adis16400: Report pressure channel scale - LP: #1471170 * iio: adis16400: Use != channel indices for the two voltage channels - LP: #1471170 * iio: adis16400: Compute the scan mask from channel indices - LP: #1471170 * iio: adis16400: Remove unused variable - LP: #1471170 * iio: adis16400: Fix burst mode - LP: #1471170 * iio: adis16400: Fix burst transfer for adis16448 - LP: #1471170 * USB: serial: ftdi_sio: Add support for a Motion Tracker Development Board - LP: #1471170 * iio: adc: twl6030-gpadc: Fix modalias - LP: #1471170 * serial: imx: Fix DMA handling for IDLE condition aborts - LP: #1471170 * usb: dwc3: gadget: Fix incorrect DEPCMD and DGCMD status macros - LP: #1471170 * ALSA: usb-audio: Add mic volume fix quirk for Logitech Quickcam Fusion - LP: #1471170 * n_tty: Fix auditing support for cannonical mode - LP: #1471170 * drm/i915/hsw: Fix workaround for server AUX channel clock divisor - LP: #1471170 * x86/asm/irq: Stop relying on magic JMP behavior for early_idt_handlers - LP: #1471170 * lib: Fix strnlen_user() to not touch memory after specified maximum - LP: #1471170 * Input: elantech - fix detection of touchpads where the revision matches a known rate - LP: #1471170 * ALSA: hda/realtek - Add a fixup for another Acer Aspire 9420 - LP: #1471170 * ALSA: usb-audio: add MAYA44 USB+ mixer control names - LP: #1471170 * ALSA: usb-audio: fix missing input volume controls in MAYA44 USB(+) - LP: #1471170 * USB: cp210x: add ID for HubZ dual ZigBee and Z-Wave dongle - LP: #1471170 * Input: elantech - add new icbody type - LP: #1471170 * MIPS: Fix enabling of DEBUG_STACKOVERFLOW - LP: #1471170 * xfrm: fix a race in xfrm_state_lookup_byspi - LP: #1471170 * kconfig: Fix warning ‘jump’ may be used uninitialized - LP: #1471170 * scripts/sortextable: suppress warning: `relocs_size' may be used uninitialized - LP: #1471170 * thermal: step_wise: Revert optimization - LP: #1471170 * MIPS: KVM: Do not sign extend on unsigned MMIO load - LP: #1471170 * arch/x86/kvm/mmu.c: work around gcc-4.4.4 bug - LP: #1471170 * net: core: Correct an over-stringent device loop detection. - LP: #1471170 * net: phy: Allow EEE for all RGMII variants - LP: #1471170 * net: dp83640: fix broken calibration routine. - LP: #1471170 * net: dp83640: reinforce locking rules. - LP: #1471170 * unix/caif: sk_socket can disappear when state is unlocked - LP: #1471170 * xen/netback: Properly initialize credit_bytes - LP: #1471170 * udp: fix behavior of wrong checksums - LP: #1471170 * xen: netback: read hotplug script once at start of day. - LP: #1471170 * ipv4/udp: Verify multicast group is ours in upd_v4_early_demux() - LP: #1471170 * bridge: disable softirqs around br_fdb_update to avoid lockup - LP: #1471170 * drm/i915: Assume dual channel LVDS if pixel clock necessitates it - LP: #1471170 * Btrfs: send, add missing check for dead clone root - LP: #1471170 * Btrfs: send, don't leave without decrementing clone root's send_progress - LP: #1471170 * btrfs: incorrect handling for fiemap_fill_next_extent return - LP: #1471170 * btrfs: cleanup orphans while looking up default subvolume - LP: #1471170 * iommu/vt-d: Allow RMRR on graphics devices too - LP: #1471170 * iommu/vt-d: Fix passthrough mode with translation-disabled devices - LP: #1471170 * ata: ahci_mvebu: Fix
[Kernel-packages] [Bug 1465136] Re: NVMe shutdown and suspend delay time is too short
** Changed in: linux-lts-utopic (Ubuntu) Status: Fix Committed = Fix Released -- 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/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+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 1465136] Re: NVMe shutdown and suspend delay time is too short
** Tags removed: verification-needed-trusty verification-needed-utopic ** Tags added: verification-done-trusty verification-done-utopic -- 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/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Fix Committed Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+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 1465136] Re: NVMe shutdown and suspend delay time is too short
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- utopic' to 'verification-done-utopic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Fix Committed Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+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 1465136] Re: NVMe shutdown and suspend delay time is too short
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- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty ** Tags added: verification-needed-utopic -- 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/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Fix Committed Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+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 1465136] Re: NVMe shutdown and suspend delay time is too short
** Changed in: linux-lts-utopic (Ubuntu) Status: New = 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/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Fix Committed Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+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 1465136] Re: NVMe shutdown and suspend delay time is too short
** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New = 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/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+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 1465136] Re: NVMe shutdown and suspend delay time is too short
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-trusty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-utopic (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-trusty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-utopic (Ubuntu Precise) Importance: Undecided Status: New ** No longer affects: linux-lts-trusty (Ubuntu Trusty) ** No longer affects: linux-lts-utopic (Ubuntu Precise) ** No longer affects: linux (Ubuntu Trusty) ** No longer affects: linux (Ubuntu Precise) ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-trusty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-utopic (Ubuntu Utopic) Importance: Undecided Status: New ** No longer affects: linux-lts-utopic (Ubuntu Utopic) ** No longer affects: linux-lts-trusty (Ubuntu Utopic) ** No longer affects: linux-lts-trusty (Ubuntu) ** No longer affects: linux-lts-trusty (Ubuntu Precise) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: New Status in linux source package in Utopic: New Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+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 1465136] Re: NVMe shutdown and suspend delay time is too short
** Changed in: linux (Ubuntu Utopic) Status: New = 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/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: New Status in linux source package in Utopic: Fix Committed Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+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 1465136] Re: NVMe shutdown and suspend delay time is too short
** Also affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu) Assignee: (unassigned) = Alex Hung (alexhung) ** Changed in: linux-lts-utopic (Ubuntu) Assignee: (unassigned) = Alex Hung (alexhung) ** Changed in: linux-lts-trusty (Ubuntu) Importance: Undecided = High ** Changed in: linux-lts-utopic (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: Fix Released Status in linux-lts-trusty package in Ubuntu: New Status in linux-lts-utopic package in Ubuntu: New Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+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 1465136] Re: NVMe shutdown and suspend delay time is too short
As per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/comments/1 . ** Tags added: cherry-pick ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu) Status: In Progress = Fix Released ** Tags added: kernel-fixed-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/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: Fix Released Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+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 1465136] Re: NVMe shutdown and suspend delay time is too short
A patch in newer kernel (3.19 and later) has a fix for this as below: commit 2484f40780b97df1b5eb09e78ce4efaa78b21875 Author: Dan McLeran daniel.mcle...@intel.com Date: Tue Jul 1 09:33:32 2014 -0600 NVMe: Add shutdown timeout as module parameter. The current implementation hard-codes the shutdown timeout to 2 seconds. Some devices take longer than this to complete a normal shutdown. Changing the shutdown timeout to a module parameter with a default timeout of 5 seconds. Signed-off-by: Dan McLeran daniel.mcle...@intel.com Signed-off-by: Matthew Wilcox matthew.r.wil...@intel.com Signed-off-by: Jens Axboe ax...@fb.com However, this patch is not included in 3.13 or 3.16 -- 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/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: In Progress Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+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
