[Kernel-packages] [Bug 1895718] Re: Fix non-working NVMe after S3

2022-09-05 Thread Timo Aaltonen
** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1895718

Title:
  Fix non-working NVMe after S3

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux-oem-5.6 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  KIOXIA NVMe has a 10% chance to stop working after S3.

  [Fix]
  Enable ACS quirk on Intel CML root port.

  [Test]
  With the patch applied, KIOXIA NVMe always works after S3.

  [Regression Potential]
  ACS works at hardware level, so I can't really assess the risk of
  regression. Since Intel confirmed CML also needs ACS quirk, we can only
  trust them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1895718/+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 1895718] Re: Fix non-working NVMe after S3

2020-10-13 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-51.56

---
linux (5.4.0-51.56) focal; urgency=medium

  * Packaging resync (LP: #1786013)
- update dkms package versions

linux (5.4.0-50.55) focal; urgency=medium

  * CVE-2020-16119
- SAUCE: dccp: avoid double free of ccid on child socket

  * CVE-2020-16120
- Revert "UBUNTU: SAUCE: overlayfs: ensure mounter privileges when reading
  directories"
- ovl: pass correct flags for opening real directory
- ovl: switch to mounter creds in readdir
- ovl: verify permissions in ovl_path_open()
- ovl: call secutiry hook in ovl_real_ioctl()
- ovl: check permission to open real file

linux (5.4.0-49.53) focal; urgency=medium

  * focal/linux: 5.4.0-49.53 -proposed tracker (LP: #1896007)

  * Comet Lake PCH-H RAID not support on Ubuntu20.04 (LP: #1892288)
- ahci: Add Intel Comet Lake PCH-H PCI ID

  * Novalink (mkvterm command failure) (LP: #1892546)
- tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()

  * Oops and hang when starting LVM snapshots on 5.4.0-47 (LP: #1894780)
- SAUCE: Revert "mm: memcg/slab: fix memory leak at non-root kmem_cache
  destroy"

  * Intel x710 LOMs do not work on Focal (LP: #1893956)
- i40e: Fix LED blinking flow for X710T*L devices
- i40e: enable X710 support

  * Add/Backport EPYC-v3 and EPYC-Rome CPU model (LP: #1887490)
- kvm: svm: Update svm_xsaves_supported

  * Fix non-working NVMe after S3 (LP: #1895718)
- SAUCE: PCI: Enable ACS quirk on CML root port

  * Focal update: v5.4.65 upstream stable release (LP: #1895881)
- ipv4: Silence suspicious RCU usage warning
- ipv6: Fix sysctl max for fib_multipath_hash_policy
- netlabel: fix problems with mapping removal
- net: usb: dm9601: Add USB ID of Keenetic Plus DSL
- sctp: not disable bh in the whole sctp_get_port_local()
- taprio: Fix using wrong queues in gate mask
- tipc: fix shutdown() of connectionless socket
- net: disable netpoll on fresh napis
- Linux 5.4.65

  * Focal update: v5.4.64 upstream stable release (LP: #1895880)
- HID: quirks: Always poll three more Lenovo PixArt mice
- drm/msm/dpu: Fix scale params in plane validation
- tty: serial: qcom_geni_serial: Drop __init from qcom_geni_console_setup
- drm/msm: add shutdown support for display platform_driver
- hwmon: (applesmc) check status earlier.
- nvmet: Disable keep-alive timer when kato is cleared to 0h
- drm/msm: enable vblank during atomic commits
- habanalabs: validate FW file size
- habanalabs: check correct vmalloc return code
- drm/msm/a6xx: fix gmu start on newer firmware
- ceph: don't allow setlease on cephfs
- drm/omap: fix incorrect lock state
- cpuidle: Fixup IRQ state
- nbd: restore default timeout when setting it to zero
- s390: don't trace preemption in percpu macros
- drm/amd/display: Reject overlay plane configurations in multi-display
  scenarios
- drivers: gpu: amd: Initialize amdgpu_dm_backlight_caps object to 0 in
  amdgpu_dm_update_backlight_caps
- drm/amd/display: Retry AUX write when fail occurs
- drm/amd/display: Fix memleak in amdgpu_dm_mode_config_init
- xen/xenbus: Fix granting of vmalloc'd memory
- fsldma: fix very broken 32-bit ppc ioread64 functionality
- dmaengine: of-dma: Fix of_dma_router_xlate's of_dma_xlate handling
- batman-adv: Avoid uninitialized chaddr when handling DHCP
- batman-adv: Fix own OGM check in aggregated OGMs
- batman-adv: bla: use netif_rx_ni when not in interrupt context
- dmaengine: at_hdmac: check return value of of_find_device_by_node() in
  at_dma_xlate()
- rxrpc: Keep the ACK serial in a var in rxrpc_input_ack()
- rxrpc: Make rxrpc_kernel_get_srtt() indicate validity
- MIPS: mm: BMIPS5000 has inclusive physical caches
- MIPS: BMIPS: Also call bmips_cpu_setup() for secondary cores
- mmc: sdhci-acpi: Fix HS400 tuning for AMDI0040
- netfilter: nf_tables: add NFTA_SET_USERDATA if not null
- netfilter: nf_tables: incorrect enum nft_list_attributes definition
- netfilter: nf_tables: fix destination register zeroing
- net: hns: Fix memleak in hns_nic_dev_probe
- net: systemport: Fix memleak in bcm_sysport_probe
- ravb: Fixed to be able to unload modules
- net: arc_emac: Fix memleak in arc_mdio_probe
- dmaengine: pl330: Fix burst length if burst size is smaller than bus width
- gtp: add GTPA_LINK info to msg sent to userspace
- net: ethernet: ti: cpsw: fix clean up of vlan mc entries for host port
- bnxt_en: Don't query FW when netif_running() is false.
- bnxt_en: Check for zero dir entries in NVRAM.
- bnxt_en: Fix PCI AER error recovery flow
- bnxt_en: Fix possible crash in bnxt_fw_reset_task().
- bnxt_en: fix HWRM error when querying VF temperature
- xfs: fix boundary test in xfs_attr_shortform_verify
- bnxt: don't enable NAPI until rings are ready
  

[Kernel-packages] [Bug 1895718] Re: Fix non-working NVMe after S3

2020-10-13 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1031.32

---
linux-oem-5.6 (5.6.0-1031.32) focal; urgency=medium

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * CVE-2020-16119
- SAUCE: dccp: avoid double free of ccid on child socket

  * CVE-2020-16120
- ovl: pass correct flags for opening real directory
- ovl: switch to mounter creds in readdir
- ovl: verify permissions in ovl_path_open()
- ovl: call secutiry hook in ovl_real_ioctl()
- ovl: check permission to open real file

linux-oem-5.6 (5.6.0-1030.30) focal; urgency=medium

  * focal/linux-oem-5.6: 5.6.0-1030.30 -proposed tracker (LP: #1898714)

  * Fix broken e1000e device after S3 (LP: #1897755)
- SAUCE: e1000e: Increase polling timeout on MDIC ready bit

  * Fix headset jack detection on Dell UFF desktops (LP: #1897508)
- Revert "ALSA: hda: call runtime_allow() for all hda controllers"

  * [SRU][OEM-5.6]Fix AMD system hang after re-plugin USBC-DP dongle
(LP: #1896716)
- drm/amd/display: Move USB-C workaround to after parameter variables are 
set

  * alsa/hda: mic doesn't work on a HP AIO machine (LP: #1897694)
- SAUCE: ALSA: hda/realtek - set mic to auto detect on a HP AIO machine

  * CVE-2020-26088
- net/nfc/rawsock.c: add CAP_NET_RAW check.

  * HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
(LP: #1897501)
- SAUCE: drm/i915/psr: allow overriding PSR disable param by quirk
- SAUCE: drm/dp: add DP_QUIRK_FORCE_PSR_CHIP_DEFAULT quirk to CMN prod-ID
  19-15

linux-oem-5.6 (5.6.0-1029.29) focal; urgency=medium

  * focal/linux-oem-5.6: 5.6.0-1029.29 -proposed tracker (LP: #1895982)

  * linux-libc-dev in proposed cause seccomp_bpf from seccomp in
ubuntu_kernel_selftests to fail on F-oem-5.6 (LP: #1896008)
- seccomp: Fix ioctl number for SECCOMP_IOCTL_NOTIF_ID_VALID

  * Enable LTR for endpoints behind VMD (LP: #1896598)
- SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD

  * CVE-2020-14385
- xfs: fix boundary test in xfs_attr_shortform_verify

  * Fix non-working NVMe after S3 (LP: #1895718)
- SAUCE: PCI: Enable ACS quirk on CML root port

  * CVE-2020-12655
- xfs: add agf freeblocks verify in xfs_agf_verify

  * Thunderbolt3 daisy chain sometimes doesn't work (LP: #1895606)
- thunderbolt: Retry DROM read once if parsing fails

  * CVE-2020-12656
- sunrpc: svcauth_gss_register_pseudoflavor must reject duplicate
  registrations.
- sunrpc: clean up properly in gss_mech_unregister()

  * CVE-2020-15393
- usb: usbtest: fix missing kfree(dev->buf) in usbtest_disconnect

  * CVE-2020-12771
- bcache: fix potential deadlock problem in btree_gc_coalesce

  * CVE-2020-15780
- ACPI: configfs: Disallow loading ACPI tables when locked down

  * CVE-2020-16166
- random32: update the net random state on interrupt and activity

  * Get the extended DPCD according to the related field in the DPCD registers.
(LP: #1893752)
- drm: move DP_MAX_DOWNSTREAM_PORTS from i915 to drm core
- drm/i915/dp: Extract drm_dp_read_dpcd_caps()
- SAUCE: drm/dp_mst: Retrieve extended DPCD caps for topology manager

  * CVE-2020-24394
- nfsd: apply umask on fs without ACL support

 -- Thadeu Lima de Souza Cascardo   Fri, 09 Oct
2020 14:54:05 -0300

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1895718

Title:
  Fix non-working NVMe after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux-oem-5.6 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  KIOXIA NVMe has a 10% chance to stop working after S3.

  [Fix]
  Enable ACS quirk on Intel CML root port.

  [Test]
  With the patch applied, KIOXIA NVMe always works after S3.

  [Regression Potential]
  ACS works at hardware level, so I can't really assess the risk of
  regression. Since Intel confirmed CML also needs ACS quirk, we can only
  trust them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1895718/+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 1895718] Re: Fix non-working NVMe after S3

2020-10-08 Thread Kai-Heng Feng
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1895718

Title:
  Fix non-working NVMe after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Released
Status in linux-oem-5.6 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  KIOXIA NVMe has a 10% chance to stop working after S3.

  [Fix]
  Enable ACS quirk on Intel CML root port.

  [Test]
  With the patch applied, KIOXIA NVMe always works after S3.

  [Regression Potential]
  ACS works at hardware level, so I can't really assess the risk of
  regression. Since Intel confirmed CML also needs ACS quirk, we can only
  trust them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1895718/+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 1895718] Re: Fix non-working NVMe after S3

2020-10-06 Thread Ian
Hi Kai-Heng,

We are working to get verification testing completed, would you be able
to confirm this issue is resolved in Focal 5.4.0-49.53?

Thanks,
Ian

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1895718

Title:
  Fix non-working NVMe after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Released
Status in linux-oem-5.6 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  KIOXIA NVMe has a 10% chance to stop working after S3.

  [Fix]
  Enable ACS quirk on Intel CML root port.

  [Test]
  With the patch applied, KIOXIA NVMe always works after S3.

  [Regression Potential]
  ACS works at hardware level, so I can't really assess the risk of
  regression. Since Intel confirmed CML also needs ACS quirk, we can only
  trust them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1895718/+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 1895718] Re: Fix non-working NVMe after S3

2020-09-29 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.8.0-20.21

---
linux (5.8.0-20.21) groovy; urgency=medium

  * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668)

  * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
(LP: #1853277)
- i2c: core: Call i2c_acpi_install_space_handler() before
  i2c_acpi_register_devices()

  * Enable LTR for endpoints behind VMD (LP: #1896598)
- SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD

  * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062)
- Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing
  nf_defrag_ipv6 support"

  * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3
(LP: #1893914)
- SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC

  * debian/rules editconfigs does not work on s390x to change s390x only configs
(LP: #1863116)
- [Packaging] kernelconfig -- only update/edit configurations on 
architectures
  we have compiler support

  * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event
0x0304) (LP: #1896216)
- s390/pci: fix leak of DMA tables on hard unplug

  * md: improve IO accounting (LP: #1891151)
- md: improve io stats accounting

  * Groovy update: v5.8.10 upstream stable release (LP: #1896078)
- ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm()
- ARM: dts: logicpd-torpedo-baseboard: Fix broken audio
- ARM: dts: logicpd-som-lv-baseboard: Fix broken audio
- ARM: dts: logicpd-som-lv-baseboard: Fix missing video
- regulator: push allocation in regulator_ena_gpio_request() out of lock
- regulator: remove superfluous lock in regulator_resolve_coupling()
- ARM: dts: socfpga: fix register entry for timer3 on Arria10
- ARM: dts: omap5: Fix DSI base address and clocks
- ARM: dts: ls1021a: fix QuadSPI-memory reg range
- ARM: dts: imx7ulp: Correct gpio ranges
- arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build
- ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy
- RDMA/rtrs-srv: Replace device_register with device_initialize and 
device_add
- RDMA/rxe: Fix memleak in rxe_mem_init_user
- RDMA/rxe: Drop pointless checks in rxe_init_ports
- RDMA/rxe: Fix panic when calling kmem_cache_create()
- RDMA/bnxt_re: Do not report transparent vlan from QP1
- RDMA/bnxt_re: Fix the qp table indexing
- RDMA/bnxt_re: Static NQ depth allocation
- RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address
- RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds
- drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux()
- arm64: dts: imx8mq: Fix TMU interrupt property
- drm/sun4i: Fix dsi dcs long write function
- scsi: qla2xxx: Fix regression on sparc64
- scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA
- drm/virtio: fix unblank
- RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ
- RDMA/core: Fix reported speed and width
- scsi: megaraid_sas: Don't call disable_irq from process IRQ poll
- scsi: mpt3sas: Don't call disable_irq from IRQ poll handler
- soundwire: fix double free of dangling pointer
- Revert "kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled"
- interconnect: qcom: Fix small BW votes being truncated to zero
- padata: fix possible padata_works_lock deadlock
- drm/sun4i: Fix DE2 YVU handling
- drm/sun4i: backend: Support alpha property on lowest plane
- drm/sun4i: backend: Disable alpha on the lowest plane on the A20
- KVM: arm64: Update page shift if stage 2 block mapping not supported
- ARM: dts: imx6sx: fix the pad QSPI1B_SCLK mux mode for uart3
- mmc: sdhci-acpi: Clear amd_sdhci_host on reset
- mmc: sdhci-msm: Add retries when all tuning phases are found valid
- spi: stm32: Rate-limit the 'Communication suspended' message
- btrfs: fix NULL pointer dereference after failure to create snapshot
- i2c: npcm7xx: Fix timeout calculation
- block: restore a specific error code in bdev_del_partition
- seccomp: don't leak memory when filter install races
- nvme-fabrics: allow to queue requests for live queues
- spi: stm32: fix pm_runtime_get_sync() error checking
- block: Set same_page to false in __bio_try_merge_page if ret is false
- RDMA/rtrs-srv: Set .release function for rtrs srv device during device 
init
- IB/isert: Fix unaligned immediate-data handling
- ARM: dts: bcm: HR2: Fixed QSPI compatible string
- ARM: dts: NSP: Fixed QSPI compatible string
- ARM: dts: BCM5301X: Fixed QSPI compatible string
- arm64: dts: ns2: Fixed QSPI compatible string
- KVM: nVMX: Fix the update value of nested load IA32_PERF_GLOBAL_CTRL 
control
- KVM: x86: always allow writing '0' to MSR_KVM_ASYNC_PF_EN
- ARC: HSDK: wireup perf irq
- dmaengine: acpi: Put 

[Kernel-packages] [Bug 1895718] Re: Fix non-working NVMe after S3

2020-09-22 Thread Timo Aaltonen
** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1895718

Title:
  Fix non-working NVMe after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.6 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  KIOXIA NVMe has a 10% chance to stop working after S3.

  [Fix]
  Enable ACS quirk on Intel CML root port.

  [Test]
  With the patch applied, KIOXIA NVMe always works after S3.

  [Regression Potential]
  ACS works at hardware level, so I can't really assess the risk of
  regression. Since Intel confirmed CML also needs ACS quirk, we can only
  trust them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1895718/+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 1895718] Re: Fix non-working NVMe after S3

2020-09-21 Thread Ubuntu Kernel Bot
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

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-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1895718

Title:
  Fix non-working NVMe after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.6 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  KIOXIA NVMe has a 10% chance to stop working after S3.

  [Fix]
  Enable ACS quirk on Intel CML root port.

  [Test]
  With the patch applied, KIOXIA NVMe always works after S3.

  [Regression Potential]
  ACS works at hardware level, so I can't really assess the risk of
  regression. Since Intel confirmed CML also needs ACS quirk, we can only
  trust them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1895718/+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 1895718] Re: Fix non-working NVMe after S3

2020-09-17 Thread William Breathitt Gray
** Changed in: linux (Ubuntu Focal)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1895718

Title:
  Fix non-working NVMe after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.6 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  KIOXIA NVMe has a 10% chance to stop working after S3.

  [Fix]
  Enable ACS quirk on Intel CML root port.

  [Test]
  With the patch applied, KIOXIA NVMe always works after S3.

  [Regression Potential]
  ACS works at hardware level, so I can't really assess the risk of
  regression. Since Intel confirmed CML also needs ACS quirk, we can only
  trust them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1895718/+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 1895718] Re: Fix non-working NVMe after S3

2020-09-16 Thread Stefan Bader
** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Groovy)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1895718

Title:
  Fix non-working NVMe after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.6 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  KIOXIA NVMe has a 10% chance to stop working after S3.

  [Fix]
  Enable ACS quirk on Intel CML root port.

  [Test]
  With the patch applied, KIOXIA NVMe always works after S3.

  [Regression Potential]
  ACS works at hardware level, so I can't really assess the risk of
  regression. Since Intel confirmed CML also needs ACS quirk, we can only
  trust them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1895718/+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