[Kernel-packages] [Bug 1942624] Re: NVME "can't change power state from D3Cold to D0 (config space inaccessible)"
** Tags added: impish -- 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/1942624 Title: NVME "can't change power state from D3Cold to D0 (config space inaccessible)" Status in linux package in Ubuntu: Confirmed Bug description: Bug with kernels after version 5.11.0-18 on Lenovo Ideapad 330-15ICH. The NVME drive with my root partition cannot be mounted at boot with an error "can't change power state from D3Cold to D0 (config space inaccessible)". I'm willing to help find a root cause if I don't need to spent too many hours. All Ubuntu kernels after 5.11.0-18 exhibit this bug, but I could boot properly with the official linux kernel 5.13.0. Thanks a lot for your help ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7503 F pulseaudio /dev/snd/pcmC0D0p: chris 7503 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 18:46:35 2021 InstallationDate: Installed on 2019-07-17 (779 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc EasyCamera Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 007: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9d963312-3a16-428d-8efd-f1323c6528f1 ro quiet nosplash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-03 (92 days ago) dmi.bios.date: 10/24/2018 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:br1.29:efr1.29:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942624/+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 1942624] Re: NVME "can't change power state from D3Cold to D0 (config space inaccessible)"
** Attachment added: "dmesg-good.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942624/+attachment/5545039/+files/dmesg-good.txt -- 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/1942624 Title: NVME "can't change power state from D3Cold to D0 (config space inaccessible)" Status in linux package in Ubuntu: Confirmed Bug description: Bug with kernels after version 5.11.0-18 on Lenovo Ideapad 330-15ICH. The NVME drive with my root partition cannot be mounted at boot with an error "can't change power state from D3Cold to D0 (config space inaccessible)". I'm willing to help find a root cause if I don't need to spent too many hours. All Ubuntu kernels after 5.11.0-18 exhibit this bug, but I could boot properly with the official linux kernel 5.13.0. Thanks a lot for your help ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7503 F pulseaudio /dev/snd/pcmC0D0p: chris 7503 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 18:46:35 2021 InstallationDate: Installed on 2019-07-17 (779 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc EasyCamera Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 007: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9d963312-3a16-428d-8efd-f1323c6528f1 ro quiet nosplash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-03 (92 days ago) dmi.bios.date: 10/24/2018 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:br1.29:efr1.29:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942624/+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 1942624] Re: NVME "can't change power state from D3Cold to D0 (config space inaccessible)"
** Attachment added: "lshw.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942624/+attachment/5545037/+files/lshw.txt -- 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/1942624 Title: NVME "can't change power state from D3Cold to D0 (config space inaccessible)" Status in linux package in Ubuntu: Confirmed Bug description: Bug with kernels after version 5.11.0-18 on Lenovo Ideapad 330-15ICH. The NVME drive with my root partition cannot be mounted at boot with an error "can't change power state from D3Cold to D0 (config space inaccessible)". I'm willing to help find a root cause if I don't need to spent too many hours. All Ubuntu kernels after 5.11.0-18 exhibit this bug, but I could boot properly with the official linux kernel 5.13.0. Thanks a lot for your help ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7503 F pulseaudio /dev/snd/pcmC0D0p: chris 7503 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 18:46:35 2021 InstallationDate: Installed on 2019-07-17 (779 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc EasyCamera Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 007: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9d963312-3a16-428d-8efd-f1323c6528f1 ro quiet nosplash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-03 (92 days ago) dmi.bios.date: 10/24/2018 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:br1.29:efr1.29:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942624/+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 1942624] Re: NVME "can't change power state from D3Cold to D0 (config space inaccessible)"
** Attachment added: "dmesg-bad.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942624/+attachment/5545038/+files/dmesg-bad.txt -- 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/1942624 Title: NVME "can't change power state from D3Cold to D0 (config space inaccessible)" Status in linux package in Ubuntu: Confirmed Bug description: Bug with kernels after version 5.11.0-18 on Lenovo Ideapad 330-15ICH. The NVME drive with my root partition cannot be mounted at boot with an error "can't change power state from D3Cold to D0 (config space inaccessible)". I'm willing to help find a root cause if I don't need to spent too many hours. All Ubuntu kernels after 5.11.0-18 exhibit this bug, but I could boot properly with the official linux kernel 5.13.0. Thanks a lot for your help ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7503 F pulseaudio /dev/snd/pcmC0D0p: chris 7503 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 18:46:35 2021 InstallationDate: Installed on 2019-07-17 (779 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc EasyCamera Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 007: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9d963312-3a16-428d-8efd-f1323c6528f1 ro quiet nosplash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-03 (92 days ago) dmi.bios.date: 10/24/2018 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:br1.29:efr1.29:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942624/+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 1942624] Re: NVME "can't change power state from D3Cold to D0 (config space inaccessible)"
I also encounter this bug in the impish 5.13 kernel. The machine boots, but without one of the NVMe devices. This is on a very recent Razer Blade 15 laptop (RZ09-0409x) with two NVMe drives. One with windows and one with Ubuntu. Upstream kernel 5.15 did not have this issue. I was able to bisect the fix back to bc2836859643 ACPI: PM: Do not turn off power resources in unknown state This patch is marked as fixing a commit that first landed in 5.14, but this commit was a rework, and the actual broken logic was introduced much earlier in 5.13. As such, the fix requires a few additional cherry picks. On 5.13.0-22-generic $ dmesg | grep nvme [sudo] password for ubuntu: [1.266638] nvme nvme0: pci function :02:00.0 [1.266646] nvme :02:00.0: can't change power state from D3cold to D0 (config space inaccessible) [1.266696] nvme nvme1: pci function :03:00.0 [1.267189] nvme nvme0: Removing after probe failure status: -19 [1.273614] nvme nvme1: missing or invalid SUBNQN field. [1.273633] nvme nvme1: Shutdown timeout set to 8 seconds [1.290515] nvme nvme1: 16/0/0 default/read/poll queues [1.293385] nvme1n1: p1 p2 [4.297893] EXT4-fs (nvme1n1p2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. [4.584787] EXT4-fs (nvme1n1p2): re-mounted. Opts: errors=remount-ro. Quota mode: none. First nvme device does not show up in lsblk. After apply the following patch set to the master-next of the impish kernel, 587024b8210d ACPI: power: Use u8 as the power resource state data type ca84f18798a4 ACPI: power: Save the last known state of each power resource 6381195ad7d0 ACPI: power: Rework turning off unused power resources db9b6d87a8d4 ACPI: power: Use dev_dbg() to print some messages fad40a624854 ACPI: power: Use acpi_handle_debug() to print debug messages bc2836859643 ACPI: PM: Do not turn off power resources in unknown state The nvme power state error is no longer present, and the device loads properly. Also, the fixing patch was marked for inclusion in 5.14 stable, but never made it since it did not cherry pick cleanly. Just the last two patches in the above list are needed for the 5.14 kernel. -- 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/1942624 Title: NVME "can't change power state from D3Cold to D0 (config space inaccessible)" Status in linux package in Ubuntu: Confirmed Bug description: Bug with kernels after version 5.11.0-18 on Lenovo Ideapad 330-15ICH. The NVME drive with my root partition cannot be mounted at boot with an error "can't change power state from D3Cold to D0 (config space inaccessible)". I'm willing to help find a root cause if I don't need to spent too many hours. All Ubuntu kernels after 5.11.0-18 exhibit this bug, but I could boot properly with the official linux kernel 5.13.0. Thanks a lot for your help ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7503 F pulseaudio /dev/snd/pcmC0D0p: chris 7503 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 18:46:35 2021 InstallationDate: Installed on 2019-07-17 (779 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc EasyCamera Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 007: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9d963312-3a16-428d-8efd-f1323c6528f1 ro quiet nosplash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-03 (92 days ago) dmi.bios.date: 10/24/2018 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:br1.29:efr1.29:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVN
[Kernel-packages] [Bug 1862888] Re: Boot hang on ASUS WS X299 SAGE
Handled by #1867677
--
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/1862888
Title:
Boot hang on ASUS WS X299 SAGE
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
Upstream kernels since 5.3 fail to boot on the ASUS WS X299 SAGE
motherboard with firmware version 1201. This is the result of an
infinite loop while trying to parse a malformed ACPI table. It is
suspected to affect other ASUS motherboards, but I have no first
hand proof of that.
This is particularly troublesome for bionic HWE installs, which
will then fail to boot after upgrading to the 5.3 series eoan
kernel.
[Test Case]
Try to boot an ASUS WS X299 SAGE computer with firmware version 1201.
Eoan and Focal kernels will fail to boot.
Upstream kernel 5.6-rc1 will boot succressfully.
[Fix]
Cherry pick upstream 2b73ea379624 ("x86/boot: Handle malformed SRAT
tables during early ACPI parsing")
[Regression Potential]
Low. Any system affected by this patch is already failing to boot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862888/+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 1862888] Re: Boot hang on ASUS WS X299 SAGE
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1862888
Title:
Boot hang on ASUS WS X299 SAGE
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
Upstream kernels since 5.3 fail to boot on the ASUS WS X299 SAGE
motherboard with firmware version 1201. This is the result of an
infinite loop while trying to parse a malformed ACPI table. It is
suspected to affect other ASUS motherboards, but I have no first
hand proof of that.
This is particularly troublesome for bionic HWE installs, which
will then fail to boot after upgrading to the 5.3 series eoan
kernel.
[Test Case]
Try to boot an ASUS WS X299 SAGE computer with firmware version 1201.
Eoan and Focal kernels will fail to boot.
Upstream kernel 5.6-rc1 will boot succressfully.
[Fix]
Cherry pick upstream 2b73ea379624 ("x86/boot: Handle malformed SRAT
tables during early ACPI parsing")
[Regression Potential]
Low. Any system affected by this patch is already failing to boot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862888/+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 1862888] [NEW] Boot hang on ASUS WS X299 SAGE
Public bug reported:
[Impact]
Upstream kernels since 5.3 fail to boot on the ASUS WS X299 SAGE
motherboard with firmware version 1201. This is the result of an
infinite loop while trying to parse a malformed ACPI table. It is
suspected to affect other ASUS motherboards, but I have no first
hand proof of that.
This is particularly troublesome for bionic HWE installs, which
will then fail to boot after upgrading to the 5.3 series eoan
kernel.
[Test Case]
Try to boot an ASUS WS X299 SAGE computer with firmware version 1201.
Eoan and Focal kernels will fail to boot.
Upstream kernel 5.6-rc1 will boot succressfully.
[Fix]
Cherry pick upstream 2b73ea379624 ("x86/boot: Handle malformed SRAT
tables during early ACPI parsing")
[Regression Potential]
Low. Any system affected by this patch is already failing to boot.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: cherry-pick eoan focal
--
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/1862888
Title:
Boot hang on ASUS WS X299 SAGE
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
Upstream kernels since 5.3 fail to boot on the ASUS WS X299 SAGE
motherboard with firmware version 1201. This is the result of an
infinite loop while trying to parse a malformed ACPI table. It is
suspected to affect other ASUS motherboards, but I have no first
hand proof of that.
This is particularly troublesome for bionic HWE installs, which
will then fail to boot after upgrading to the 5.3 series eoan
kernel.
[Test Case]
Try to boot an ASUS WS X299 SAGE computer with firmware version 1201.
Eoan and Focal kernels will fail to boot.
Upstream kernel 5.6-rc1 will boot succressfully.
[Fix]
Cherry pick upstream 2b73ea379624 ("x86/boot: Handle malformed SRAT
tables during early ACPI parsing")
[Regression Potential]
Low. Any system affected by this patch is already failing to boot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862888/+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 1815831] Re: [ALSA] [PATCH] System76 darp5 and oryp5 fixups
Any chance this could land in the xenial HWE kernel as well? -- 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/1815831 Title: [ALSA] [PATCH] System76 darp5 and oryp5 fixups Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification Impact: The System76 darp5 and oryp5 platforms need audio driverquirks to fix up the pin configuration. Fix: One backport from upstream, and one cherry pick from the upstream sound tree. Test Case: Backports have been tested on the affected hardware. Regression Potential: These are quirks for specific PCI device ids and thus are not expected to introduce regressions for any other hardware. --- Two fixups are needed to support the headset microphone on the System76 darp5 and oryp5. The darp5 patch is attached here, the oryp5 patch will be attached on the next comment. On the System76 Darter Pro (darp5), there is a headset microphone input attached to 0x1a that does not have a jack detect. In order to get it working, the pin configuration needs to be set correctly, and the ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied. This is similar to the MIC_NO_PRESENCE fixups for some Dell laptops, except we have a separate microphone jack that is already configured correctly. On the System76 Oryx Pro (oryp5), there is a headset microphone input attached to 0x19 that does not have a jack detect. In order to get it working, the pin configuration needs to be set correctly, and the ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied. This is similar to the MIC_NO_PRESENCE fixups for some Dell laptops, except we have a separate microphone jack that is already configured correctly. Since the ALC1220 does not have a fixup similar to ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC, I have exposed the fixup from the ALC269 in a way that it can be accessed from the alc1220_fixup_system76_oryp5 function. In addition, the alc1220_fixup_clevo_p950 needs to be applied to gain speaker output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815831/+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 1794398] [NEW] nvidia-persistenced requires libnvidia-cfg
Public bug reported: Sep 25 16:58:17 server nvidia-persistenced[773]: Started (773) Sep 25 16:58:17 server nvidia-persistenced[771]: nvidia-persistenced failed to initialize. Check syslog for more details. Sep 25 16:58:17 server nvidia-persistenced[773]: Failed to open libnvidia-cfg.so.1: libnvidia-cfg.so.1: cannot open shared object file: No such file or directory Sep 25 16:58:17 server nvidia-persistenced[773]: PID file unlocked. Sep 25 16:58:17 server nvidia-persistenced[773]: PID file closed. Sep 25 16:58:17 server nvidia-persistenced[773]: Shutdown (773) nvidia-persistenced tries to dlopen libnvidia-cfg.so.1, and is useless if it is missing. nvidia-compute-utils-390 should depend on (or at least recommend) libnvidia-cfg1-390 ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1794398 Title: nvidia-persistenced requires libnvidia-cfg Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Sep 25 16:58:17 server nvidia-persistenced[773]: Started (773) Sep 25 16:58:17 server nvidia-persistenced[771]: nvidia-persistenced failed to initialize. Check syslog for more details. Sep 25 16:58:17 server nvidia-persistenced[773]: Failed to open libnvidia-cfg.so.1: libnvidia-cfg.so.1: cannot open shared object file: No such file or directory Sep 25 16:58:17 server nvidia-persistenced[773]: PID file unlocked. Sep 25 16:58:17 server nvidia-persistenced[773]: PID file closed. Sep 25 16:58:17 server nvidia-persistenced[773]: Shutdown (773) nvidia-persistenced tries to dlopen libnvidia-cfg.so.1, and is useless if it is missing. nvidia-compute-utils-390 should depend on (or at least recommend) libnvidia-cfg1-390 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1794398/+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 1774817] Re: Temperature sensors on x470 not reporting correctly
This also applies to the new Threadrippers (2990WX, etc.) Recent commits https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/hwmon/k10temp.c?id=484a84f25ca7817c3662001316ba7d1e06b74ae2 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hwmon/k10temp.c?id=cd6a2064dbf9e485b80c54687f0ce91cca91a6df -- 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/1774817 Title: Temperature sensors on x470 not reporting correctly Status in linux package in Ubuntu: Triaged Bug description: x470-I ROG strix motherboard and Ryzen 2700 After sudo sensors-detect and answering yes to all the probes the net result is: "Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported." sensors output lists: asus-isa- Adapter: ISA adapter cpu_fan:0 RPM nouveau-pci-0900 Adapter: PCI adapter fan1: 0 RPM temp1:+65.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +5.0°C) (emerg = +135.0°C, hyst = +5.0°C) k10temp-pci-00c3 Adapter: PCI adapter temp1:+94.2°C (high = +70.0°C) Where the cpu fan is patently wrong and the k10temp likewise. The nouveau-pci-0900 appears to be the actual CPU temperature. May be related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740736 Other info: Description: Ubuntu 18.04 LTS Release: 18.04 version log: Ubuntu 4.15.0-22.24-generic 4.15.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774817/+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
