[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
Updated PPA with linux-hwe-5.11/focal version 5.11.0-2037.41~20.04.2+lp1939937.2.ath10k.iram, linux/hirsute version 5.11.0-2038.42+lp1939937.2.ath10k.iram and linux/impish version 5.13.0-2014.14+lp1939937.2.ath10k.iram for testing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939937 Title: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability Status in linux package in Ubuntu: Triaged Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Triaged Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Triaged Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support") in v5.11 fails firmware loading without IRAM recovery feature. However, the latest firmware from https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2 doesn't support IRAM, it follows new official ath10k firmwares may no longer be loadable for kernel newer than v5.11. [Fix] A fix is proposed to http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that turns the lack/failure of IRAM recovery support a warning instead. [Test Case] With this fix, kernel gives errors about the IRAM supportness, but proceeds to remaining procedures as before. ath10k_pci :04:00.0: No hardware memory ath10k_pci :04:00.0: failed to copy target iram contents: -12 ath10k_pci :07:00.0: No hardware memory ath10k_pci :07:00.0: failed to copy target iram contents: -12 [Where problems could occur] So the IRAM recovery feature may or may not be supported in the officially released firmware, and people meet problems when using non-IRAM supported firmware may still have a fallback to use older, but IRAM recovery supported ones. == original bug report == Hello, I use Ubuntu 20.04.2 LTS. The kernel was recently updated to 5.11 5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Since then the ath10k_core driver for my QCA9984 card is broken and only loads ~3 firmware versions from the 3.9.0.2 branch https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2 The firmware versions 70 / 86 / 91 are functional (but these firmware versions are already 2 years old) Responsible for this is the defective patch "ath10k: add target IRAM recovery feature support" https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11&id=9af7c32ceca85da27867dd863697d2aafc80a3f8 If I understand the patch correctly then the driver tries to load firmware with the feature "iram recovery" into the memory of the host (for recvovery purposes). If this fails, the firmware is discarded and the network controller remains unusable. Of course, this is not a desirable behavior for optional firmware features. dmesg: [3.074952] ath: loading out-of-tree module taints kernel. [3.090522] ath: module verification failed: signature and/or required key missing - tainting kernel [3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [7.047910] ath10k_pci :03:00.0: failed to copy target iram contents: -12 [7.103260] ath10k_pci :03:00.0: could not init core (-12) [7.103267] ath10k_pci :03:00.0: could not probe fw (-12) [7.108570] ath10k_pci :04:00.0: failed to copy target iram contents: -12
[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
It seems the updated url is https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=master- pending&id=37a86881331e1451ec357b1fc6738c34fe5230c1 Per review comments in https://lists.ubuntu.com/archives/kernel- team/2021-August/123442.html, switch to pending and wait until this being merged in linux-next. ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Triaged ** Changed in: linux (Ubuntu Impish) Status: In Progress => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939937 Title: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability Status in linux package in Ubuntu: Triaged Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Triaged Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Triaged Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support") in v5.11 fails firmware loading without IRAM recovery feature. However, the latest firmware from https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2 doesn't support IRAM, it follows new official ath10k firmwares may no longer be loadable for kernel newer than v5.11. [Fix] A fix is proposed to http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that turns the lack/failure of IRAM recovery support a warning instead. [Test Case] With this fix, kernel gives errors about the IRAM supportness, but proceeds to remaining procedures as before. ath10k_pci :04:00.0: No hardware memory ath10k_pci :04:00.0: failed to copy target iram contents: -12 ath10k_pci :07:00.0: No hardware memory ath10k_pci :07:00.0: failed to copy target iram contents: -12 [Where problems could occur] So the IRAM recovery feature may or may not be supported in the officially released firmware, and people meet problems when using non-IRAM supported firmware may still have a fallback to use older, but IRAM recovery supported ones. == original bug report == Hello, I use Ubuntu 20.04.2 LTS. The kernel was recently updated to 5.11 5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Since then the ath10k_core driver for my QCA9984 card is broken and only loads ~3 firmware versions from the 3.9.0.2 branch https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2 The firmware versions 70 / 86 / 91 are functional (but these firmware versions are already 2 years old) Responsible for this is the defective patch "ath10k: add target IRAM recovery feature support" https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11&id=9af7c32ceca85da27867dd863697d2aafc80a3f8 If I understand the patch correctly then the driver tries to load firmware with the feature "iram recovery" into the memory of the host (for recvovery purposes). If this fails, the firmware is discarded and the network controller remains unusable. Of course, this is not a desirable behavior for optional firmware features. dmesg: [3.074952] ath: loading out-of-tree module taints kernel. [3.090522] ath: module verification failed: signature and/or required key missing - tainting kernel [3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [7.047910] ath10k_pci :03:00.0: failed to copy targ
[Kernel-packages] [Bug 1941044] Re: ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade to linux-firmware 1.187.16
I think there is a defect in iwlwifi-ty-a0-gf-a0.pnvm that its existence would force older kernels to use FW API 63 or so. The current pnvm file cannot be loaded along with -59 firmware even with v5.15-rc2 kernel, and we'd need -63 fw for ADL platforms anyway. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1941044 Title: ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade to linux-firmware 1.187.16 Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Triaged Bug description: $ lsb_release -rd Description: Ubuntu 20.04.3 LTS $ uname -r 5.11.0-27-generic $ apt-cache policy linux-firmware linux-firmware: Installed: 1.187.16 $ ip a 1: lo 2: enp0s31f6 Device: Lenovo T14 Gen 2 w/ Intel AX210 WiFi [8086:2725] WiFi adapter disappears from network manager and > ip a following update to > linux-firmware 1.187.16 and a restart Able to confirm this package is the problem as the issue can be reversed by downgrading to > linux-firmware 1.187.15 Our organisation has had at least one other identical device experience the same issue before > apt-mark hold linux-firmware was pushed out. Happy to supply any other information or logs on request. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.16 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logansymons 7485 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 25 18:10:49 2021 Dependencies: IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 04f2:b6d0 Chicony Electronics Co., Ltd Integrated Camera Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20W0005AAU PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-27-generic root=/dev/mapper/my_vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.16 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET41W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0005AAU dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET41W(1.41):bd07/08/2021:br1.41:efr1.8:svnLENOVO:pn20W0005AAU:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005AAU:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0005AAU dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1941044/+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 1945144] Re: 20.04.3 causes apps to crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1945144 Title: 20.04.3 causes apps to crash Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Upgraded from 18.04 to 20.04.3. VisualWorks will run and VueScan will run. But they crash in 20.04.3 and not on 18.04. Best guess is that 20.04 broke process manager. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Sep 27 00:08:49 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1945144/+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 1941044] Re: ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade to linux-firmware 1.187.16
This should have been addressed in v5.13-rc1 that bumped FW API to 63. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1941044 Title: ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade to linux-firmware 1.187.16 Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Triaged Bug description: $ lsb_release -rd Description: Ubuntu 20.04.3 LTS $ uname -r 5.11.0-27-generic $ apt-cache policy linux-firmware linux-firmware: Installed: 1.187.16 $ ip a 1: lo 2: enp0s31f6 Device: Lenovo T14 Gen 2 w/ Intel AX210 WiFi [8086:2725] WiFi adapter disappears from network manager and > ip a following update to > linux-firmware 1.187.16 and a restart Able to confirm this package is the problem as the issue can be reversed by downgrading to > linux-firmware 1.187.15 Our organisation has had at least one other identical device experience the same issue before > apt-mark hold linux-firmware was pushed out. Happy to supply any other information or logs on request. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.16 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logansymons 7485 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 25 18:10:49 2021 Dependencies: IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 04f2:b6d0 Chicony Electronics Co., Ltd Integrated Camera Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20W0005AAU PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-27-generic root=/dev/mapper/my_vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.16 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET41W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0005AAU dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET41W(1.41):bd07/08/2021:br1.41:efr1.8:svnLENOVO:pn20W0005AAU:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005AAU:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0005AAU dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1941044/+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 1941044] Re: ax210 wifi adapter disappears with upgrade to linux-firmware 1.187.16
I can reproduce this with TGL platform, AX210 [8086:2725] subsystem [8086:0020], kernel linux-hwe-5.11 and linux-oem-5.10. linux-oem-5.13 works for me, but somehow it claimed otherwise in bug 1943918. ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Focal) Status: New => Triaged ** Summary changed: - ax210 wifi adapter disappears with upgrade to linux-firmware 1.187.16 + ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade to linux-firmware 1.187.16 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1941044 Title: ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade to linux-firmware 1.187.16 Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Triaged Bug description: $ lsb_release -rd Description: Ubuntu 20.04.3 LTS $ uname -r 5.11.0-27-generic $ apt-cache policy linux-firmware linux-firmware: Installed: 1.187.16 $ ip a 1: lo 2: enp0s31f6 Device: Lenovo T14 Gen 2 w/ Intel AX210 WiFi [8086:2725] WiFi adapter disappears from network manager and > ip a following update to > linux-firmware 1.187.16 and a restart Able to confirm this package is the problem as the issue can be reversed by downgrading to > linux-firmware 1.187.15 Our organisation has had at least one other identical device experience the same issue before > apt-mark hold linux-firmware was pushed out. Happy to supply any other information or logs on request. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.16 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logansymons 7485 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 25 18:10:49 2021 Dependencies: IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 04f2:b6d0 Chicony Electronics Co., Ltd Integrated Camera Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20W0005AAU PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-27-generic root=/dev/mapper/my_vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.16 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET41W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0005AAU dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET41W(1.41):bd07/08/2021:br1.41:efr1.8:svnLENOVO:pn20W0005AAU:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005AAU:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0005AAU dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1941044/+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 1930754] Re: e1000e extremly slow
** Description changed: + [Impact] + e1000e on TGP PCH encounters a network speed issue that rx speed is below 1MB/s + + [Fix] + Intel provides 2 patches to fix this + + [Test] + Verified by our Dell and Lenovo platforms and the bug reporter. + + [Where problems could occur] + The fix only applies to e1000e with TGP PCH, and add a flag "E1000_FFLT_DBG_DONT_GATE_WAKE_DMA_CLK". The impact should be minimized and should not lead to other regressions. + + = + We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e on TGP PCH encounters a network speed issue that rx speed is below 1MB/s [Fix] Intel provides 2 patches to fix this [Test] Verified by our Dell and Lenovo platforms and the bug reporter. [Where problems could occur] The fix only applies to e1000e with TGP PCH, and add a flag "E1000_FFLT_DBG_DONT_GATE_WAKE_DMA_CLK". The impact should be minimized and should not lead to other regressions. = We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930754/+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 1943918] Re: iwlwifi version 63.c04f3485.0 fails to load
I can reproduce this with TGL platform, AX210 [8086:2725] subsystem [8086:0020], kernel linux-hwe-5.11 and linux-oem-5.10. linux-oem-5.13 (1012, 1013 and above) works for me. ** This bug is no longer a duplicate of bug 1943915 IPU6 daemon+v4l2loopback is required to enable use for existing applications ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1943918 Title: iwlwifi version 63.c04f3485.0 fails to load Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Bug description: I have Intel WiFi 6E AX210. Using the default 20.04 kernel 5.10 I get wifi to work after removing /lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm https://bugzilla.kernel.org/show_bug.cgi?id=212371 This kernel is loading 59.601f3a66.0 version of iwlwifi driver. When using 5.13.0-1012-oem the kernel tries to load 63.c04f3485.0 which doesn't work [fre sep 17 07:38:34 2021] iwlwifi :72:00.0: enabling device ( -> 0002) [fre sep 17 07:38:34 2021] iwlwifi :72:00.0: api flags index 2 larger than supported by driver [fre sep 17 07:38:34 2021] iwlwifi :72:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.25 [fre sep 17 07:38:34 2021] iwlwifi :72:00.0: loaded firmware version 63.c04f3485.0 ty-a0-gf-a0-63.ucode op_mode iwlmvm [fre sep 17 07:38:34 2021] iwlwifi :72:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: SecBoot CPU1 Status: 0x77a3, CPU2 Status: 0xb03 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: UMAC PC: 0x8047df60 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: LMAC PC: 0x0 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: Loaded firmware version: 63.c04f3485.0 ty-a0-gf-a0-63.ucode [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | ADVANCED_SYSASSERT [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | trm_hw_status0 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | trm_hw_status1 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | branchlink2 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | interruptlink1 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | interruptlink2 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | data1 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | data2 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | data3 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | beacon time [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | tsf low [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | tsf hi [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | time gp1 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | time gp2 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | uCode revision type [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | uCode version major [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | uCode version minor [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | hw version [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | board version [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | hcmd [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | isr0 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | isr1 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | isr2 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | isr3 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | isr4 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | last cmd Id [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | wait_event [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | l2p_control [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | l2p_duration [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | l2p_mhvalid [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | l2p_addr_match [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | lmpm_pmg_sel [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | timestamp [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | flow_handler [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: Start IWL Error Log Dump: [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: Status: 0x, count: 7 [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x201013F2 | ADVANCED_SYSASSERT [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | umac branchlink1 [fre sep 17 07:38:35 2021] iwlwifi
[Kernel-packages] [Bug 1945144] [NEW] 20.04.3 causes apps to crash
Public bug reported: Upgraded from 18.04 to 20.04.3. VisualWorks will run and VueScan will run. But they crash in 20.04.3 and not on 18.04. Best guess is that 20.04 broke process manager. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Sep 27 00:08:49 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1945144 Title: 20.04.3 causes apps to crash Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Upgraded from 18.04 to 20.04.3. VisualWorks will run and VueScan will run. But they crash in 20.04.3 and not on 18.04. Best guess is that 20.04 broke process manager. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Sep 27 00:08:49 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1945144/+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 1909005] Re: Ubuntu does not resume (wake up) from suspend
Seeing this bug on my Dell Inspiron 15, 5515 Ubuntu 20.04.3 5.11.0-36-lowlatency Seeing one of the following two behaviors everytime it goes into suspend: 1) The machine goes into suspend okay, and when I press power it doesn't turn back on from suspend. I hold power to turn off, then press power again and it will come back on. OR 2) The machine goes into suspend okay, and when I press power it turns on but hangs at a black screen. I hold power to turn off, then press power again and it will come back on. Machine is dual booted with Windows and Ubuntu -> only seeing issues in Ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1945136] [NEW] Broken audio capture subsystem
Public bug reported: In Impish the problem of capturing audio by discord (from app or browser does not matter) when broadcasting reappeared. The window is being captured or not - it doesn't matter. It looks like a regression. Webcamoid don't capture sound from micro too. If I set gstreamer method instead of ffmpeg 4.4 then sound appears, but very laggy Discord launched in a browser and streaming an adjacent tab does the same. I don't even know what to report on. Looks like a broken audio capture subsystem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2083 F pulseaudio /dev/snd/controlC0: navycat2083 F pulseaudio /dev/snd/controlC1: navycat2083 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 27 05:06:06 2021 InstallationDate: Installed on 2021-05-28 (121 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Alpha amd64 (20210526) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=bc8287ed-7647-42ae-8f04-6297f1c30b1d ro nouveau.noaccel=1 nouveau.nofbaccel=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.200 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:skuPROJECT_SUB_TAG:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish ** Changed in: linux (Ubuntu) Status: New => 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/1945136 Title: Broken audio capture subsystem Status in linux package in Ubuntu: Confirmed Bug description: In Impish the problem of capturing audio by discord (from app or browser does not matter) when broadcasting reappeared. The window is being captured or not - it doesn't matter. It looks like a regression. Webcamoid don't capture sound from micro too. If I set gstreamer method instead of ffmpeg 4.4 then sound appears, but very laggy Discord launched in a browser and streaming an adjacent tab does the same. I don't even know what to report on. Looks like a broken audio capture subsystem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2083 F pulseaudio /dev/snd/controlC0: navycat2083 F pulseaudio /dev/snd/controlC1: navycat2083 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 27 05:06:06 2021 InstallationDate: Installed on 2021-05-28 (121 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Alpha amd64 (20210526) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=bc8287ed-7647-42ae-8f04-6297f1c30b1d ro nouveau.noaccel=1 nouveau.nofbaccel=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.200 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.
[Kernel-packages] [Bug 1944389] Re: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz
There is a temperature sensor "THP" which has a limit of 53C. This temperature exceeded which calls for thermal throttling to limit to 15W by thermal tables on this system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1944389 Title: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz Status in thermald package in Ubuntu: New Bug description: After update to 1.9.1-1ubuntu0.6 from 1.9.1-1ubuntu0.4 thermald keeps Tigerlake Iris Xe GPU frequency on 400 MHz after reaching some high temperature value. It became impossible to play video games on the laptop. System: Ubuntu 20.04.3 LTS Kernel: 5.10.0-1045-oem Laptop: Dell XPS 9310, CPU: Intel Core i7-1165G7 (Tigerlake), Integrated GPU Iris Xe. BIOS 2.1.1 03/25/2021 Display: 2560x1440 144Hz HDMI USB-C connection Room temperature is 23.5-25.4 degrees Game: Stalker Clear Sky (Wine/Proton Steam) Note: The game itself is very old and loads 100% of one CPU core disregarding of frequency. GPU frequency is monitored by intel-gpu-top GPU frequencies (according to /sys/class/drm/card0/) min/max/boost/efficiency: 100/1300/1300/400 Previous behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. After some time when threshold temperature value (~78 degrees) is reached the GPU frequency decreases to ~660 MHz and FPS to 40-48 FPS. Package temperature decreases to 66-68 degrees. It's possible to play for indefinite amount of time. New behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. But after reaching the threshold temperature (about 81 degrees) GPU frequency decreases to 400 MHz (gt_RP1_freq_mhz -- "efficiency" temperature for the GPU) and stays on this value for the indefinite amount of time. The temperature is maintained on 70-74 degrees. FPS is about 25-30 FPS, it is not possible to play the game anymore. The only way to return the good FPS and frequency is to fold the game window, wait some time and open it again. Also there is a workaround -- limit the CPU frequency to 2001 MHz and disable Intel turbo boost. With such approach package temperature never reaches 80 degrees and it is possible to play game with 500 MHz and 35-40 FPS. Better than nothing. If it is needed I can perform any additional checks, provide CPU frequencies and so on. Most probably regression happened with 1.9.1-1ubuntu0.5, but I tried only versions 0.4 and 0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1944389/+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 1930754] Re: e1000e extremly slow
Patches have been submitted https://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=263466 ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-5.10 (Ubuntu Impish) Importance: Critical Assignee: AceLan Kao (acelankao) Status: Confirmed ** Also affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Impish) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: Confirmed => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Impish) Assignee: AceLan Kao (acelankao) => (unassigned) ** Changed in: linux-oem-5.14 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930754/+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 1943368] Re: Touchpad not recognised
Under windows, does the touchpad connect to i8042/ps2 bus or i2c bus? -- 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/1943368 Title: Touchpad not recognised Status in linux package in Ubuntu: Confirmed Bug description: the touchpad is not recognised ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bem1753 F pulseaudio /dev/snd/pcmC0D0p: bem1753 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 12 15:55:20 2021 InstallationDate: Installed on 2021-08-17 (25 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Medion Akoya E6239 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=a2ea56ce-d8fa-4472-954d-4c580bee4549 ro i8042.nomux=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-08-18 (25 days ago) dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 612 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Akoya E6239 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr612:bd04/09/2014:svnMedion:pnAkoyaE6239:pvr1.0:rvnMedion:rnAkoyaE6239:rvr1.0:cvnMedion:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Akoya E6239 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Medion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943368/+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 1940860] Re: Mellanox NIC interface names change between 5.4 and 5.8
I should say here that I don't really know what changes to subiquity are desirable here. I don't really like the idea of subiquity always using set-name, that just feels wrong, but I can see the problem here too. -- 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/1940860 Title: Mellanox NIC interface names change between 5.4 and 5.8 Status in subiquity: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I noticed on a couple of systems that my network interface names change when upgrading from the focal LTS (5.4) kernel to the focal HWE (both 5.8 & 5.11) kernels. Both systems have Mellanox Connect-X 5 NICs. dannf@bizzy:~$ uname -a Linux bizzy 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:10:30 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0 enp1s0f1 enx3e8734bc294f lo dannf@bizzy:~$ uname -a Linux bizzy 5.8.0-63-generic #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:44 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0np0 enp1s0f1np1 enx3e8734bc294f lo dannf@bizzy:~$ uname -a Linux bizzy 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 15:58:08 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0np0 enp1s0f1np1 enx3e8734bc294f lo I bisected this down to a kernel change: # first bad commit: [c6acd629eec754a9679f922d51f90e44c769b80c] net/mlx5e: Add support for devlink-port in non-representors mode The impact is that your network can fail to come up after transitioning from the LTS kernel to the HWE kernel. Now, this isn't a huge problem for MAAS installs because MAAS configures netplan to always use the same names as were used at commissioning. It does impact subiquity based installs however, which do not. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1940860/+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 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
> While hot-fixing the issue is fine, I feel like this won't be the last bug > like this we run into as long as we choose to mix-and-match versions. > Wouldn't the better solution be adding HWE ZFS userland packages to match the > kernel module? My thoughts exactly. Vote here. https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Committed Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+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 1691556] Re: Can't send audio to Amazon Echo via Bluetooth
This error remains unsolved, amazon echo cannot be paired, as an input and output device. It only works with one of the two -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1691556 Title: Can't send audio to Amazon Echo via Bluetooth Status in bluez package in Ubuntu: Confirmed Bug description: Pairing and coupling to Amazon Echo works, but no sound is heard. I believe the issue is related to the fact that Amazon Echo is paired as a handset (i.e., speaker + microphone) rather than just as a speaker. I believe the critical error is found in a dmesg line such as: Feb 28 10:59:05 n1 bluetoothd[1025]: a2dp-source profile connect failed for 50:F5:DA:A6:3F:EA: Device or resource busy as I describe in the askubuntu.com discussion at: https://askubuntu.com/questions/871630/cant-send-audio-to-amazon-echo- via-bluetooth I have clarified there my thinking and the steps I've taken thus far on this issue, which includes trying debug bluetooth per the Ubuntu wiki page which describes how to do so. This is probably an upstream issue, as Mike H-R has commented there that the problem also occurs on ArchLinux. I and a few others would like to get this resolved, and I am happy to help (I'm a software developer). However, at this point, I'm not sure how to proceed without some assistance. I suppose I could report it to Debain, but I've only ever used Debain vis a vis Ubuntu, so I thought it best to start here. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 17 22:27:59 2017 InstallationDate: Installed on 2015-12-26 (507 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (78 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr: hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:53:60:97:55:17 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:13547334 acl:58 sco:0 events:1935087 errors:0 TX bytes:1652407651 acl:1934967 sco:0 commands:76 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+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 1914685] Re: Please enable CONFIG_UBSAN_BOUNDS
So, 5.14.7 and NVIDIA 470.74 fixes the boot issue. However, isn't potentially harmful to leave CONFIG_UBSAN_TRAP enabled in production builds? The documentation for the flag seems to indicate that warnings would be turned into the errors. https://github.com/torvalds/linux/blob/master/lib/Kconfig.ubsan#L20 As I understand, CONFIG_UBSAN_TRAP is needed to enable CONFIG_UBSAN_LOCAL_BOUNDS, but the issue mentions CONFIG_UBSAN_BOUNDS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1914685 Title: Please enable CONFIG_UBSAN_BOUNDS Status in linux package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Committed Status in linux source package in Groovy: Won't Fix Status in linux-oracle source package in Groovy: Won't Fix Status in linux source package in Hirsute: Confirmed Status in linux-oracle source package in Hirsute: Confirmed Status in linux source package in Impish: Fix Released Status in linux-oracle source package in Impish: Fix Committed Bug description: Enabling CONFIG_UBSAN_BOUNDS is fast and provides good coverage for out-of-bounds array indexing (i.e. it catchings the things that CONFIG_FORTIFY doesn't). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914685/+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 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
NVIDIA driver version 470.74 fixes my usb-c displayport issues. But I still think leaving the CONFIG_UBSAN_TRAP flag in the build is concerning (at least, based on the documentation for the flag). It's probably okay for testing -- 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/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc7. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-04 (62 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: wayland-session hirsute Uname: Linux 5.14.0-051400rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+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 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
Alrighty, so, after having adjusted the grub configuration, this time around, it lasted about 16½ hours before coming to a freeze. Plus, actually, this time, it didn't outright blackscreen. What happened was: it froze and the audio began looping. I let the audio loop for a while in the hopes that the computer would have enough time to write the errors to the log. Hopefully, this has some answers. ** Attachment added: "prevboot-2021-09-26-a.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939966/+attachment/5528266/+files/prevboot-2021-09-26-a.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev:
[Kernel-packages] [Bug 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
The amd64 version still isn't built after the build failure, how can we get that build restarted? Cheers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Committed Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+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 1944389] Re: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz
Here is the log GPU frequency decreased to 400MHz at ~23:50 UTC+3 ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1944389/+attachment/5528265/+files/log.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1944389 Title: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz Status in thermald package in Ubuntu: New Bug description: After update to 1.9.1-1ubuntu0.6 from 1.9.1-1ubuntu0.4 thermald keeps Tigerlake Iris Xe GPU frequency on 400 MHz after reaching some high temperature value. It became impossible to play video games on the laptop. System: Ubuntu 20.04.3 LTS Kernel: 5.10.0-1045-oem Laptop: Dell XPS 9310, CPU: Intel Core i7-1165G7 (Tigerlake), Integrated GPU Iris Xe. BIOS 2.1.1 03/25/2021 Display: 2560x1440 144Hz HDMI USB-C connection Room temperature is 23.5-25.4 degrees Game: Stalker Clear Sky (Wine/Proton Steam) Note: The game itself is very old and loads 100% of one CPU core disregarding of frequency. GPU frequency is monitored by intel-gpu-top GPU frequencies (according to /sys/class/drm/card0/) min/max/boost/efficiency: 100/1300/1300/400 Previous behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. After some time when threshold temperature value (~78 degrees) is reached the GPU frequency decreases to ~660 MHz and FPS to 40-48 FPS. Package temperature decreases to 66-68 degrees. It's possible to play for indefinite amount of time. New behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. But after reaching the threshold temperature (about 81 degrees) GPU frequency decreases to 400 MHz (gt_RP1_freq_mhz -- "efficiency" temperature for the GPU) and stays on this value for the indefinite amount of time. The temperature is maintained on 70-74 degrees. FPS is about 25-30 FPS, it is not possible to play the game anymore. The only way to return the good FPS and frequency is to fold the game window, wait some time and open it again. Also there is a workaround -- limit the CPU frequency to 2001 MHz and disable Intel turbo boost. With such approach package temperature never reaches 80 degrees and it is possible to play game with 500 MHz and 35-40 FPS. Better than nothing. If it is needed I can perform any additional checks, provide CPU frequencies and so on. Most probably regression happened with 1.9.1-1ubuntu0.5, but I tried only versions 0.4 and 0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1944389/+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 1923400] Re: package libnvidia-gl-460 (not installed) failed to install/upgrade: new libnvidia-gl-460:amd64 package pre-installation script subprocess returned error exit status
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1923400 Title: package libnvidia-gl-460 (not installed) failed to install/upgrade: new libnvidia-gl-460:amd64 package pre-installation script subprocess returned error exit status 2 Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: The error was shown by the system. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-gl-460 (not installed) ProcVersionSignature: Ubuntu 4.15.0-130.134-generic 4.15.18 Uname: Linux 4.15.0-130-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 Date: Mon Apr 12 11:19:41 2021 ErrorMessage: new libnvidia-gl-460:amd64 package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2014-12-20 (2304 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-460 Title: package libnvidia-gl-460 (not installed) failed to install/upgrade: new libnvidia-gl-460:amd64 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2021-01-12 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1923400/+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 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
While hot-fixing the issue is fine, I feel like this won't be the last bug like this we run into as long as we choose to mix-and-match versions. Wouldn't the better solution be adding HWE ZFS userland packages to match the kernel module? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Committed Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+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 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
So, out of pure frustration, I wondered if maybe it was the particular SSD slot, so I decided to simply switch my SSDs across the slots on my motherboard (because the Kubuntu installation never crashed). Suddenly, now, that one was crashing, and the Xubuntu installation worked fine (for a while). so I thought it was the SSD slot. Then, the "good" slot started crashing randomly, too. I started looking around for my specific computer, and it turns out that the "soft lockup" is from a misconfiguration in the grub setup. I thought to myself, "I haven't touched my grub. The only time I ever did anything was the `sudo apt dist-upgrade` about three weeks ago." And then it hit me: the crashes started about a day or two after I did a dist-upgrade. So I started looking around, and I found this: https://github.com/jfinancial/linux/blob/main/AMD_Linux_Build.md and subsequently this: https://askubuntu.com/questions/1234299/amd- ryzen-5-3600-ubuntu-20-04-problems/1241636#1241636 so I went into /etc/default/grub and changed the line to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=assign-busses apicmaintimer idle=poll reboot=cold,hard" and did a `sudo update-grub`. So far, my computer has an uptime of around 13 hours, so this is looking promising. Also, I am never, ever, ever updating my kernel ever again, ever. Every time I do, something absolutely vitally, crucially important breaks. This is especially true about Arch and all Arch-based distros (which I'll never use again). I'll try leaving my computer turned on for a week and see if changing that grub line helps. Here's to hoping. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN123456789012
[Kernel-packages] [Bug 1939153] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2: bcmwl kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1939153 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: Not sure - it was a system reported crash ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Fri Aug 6 07:08:38 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu7~20.04.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-10-09 (301 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu7~20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1939153/+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 1943083] Re: [i915] [Braswell] screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen
I installed an older GNU/Linux 5.10.51-051051-generic x86_64 kernel but the problem remained. Maybe I should have gone with an even older kernel, I don't know. -- 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/1943083 Title: [i915] [Braswell] screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen Status in linux package in Ubuntu: Incomplete Bug description: I reported that against mutter, but it can be gnome-shell as well, or even Intel driver/kernel related. It happens since my switch to Impish, I have never seen that issue before. Integrated Intel HD graphics 400 onboard. STEPS to reproduce: 1) Move the mouse pointer to the left edge of the screen 2) See that everything works as expected 3) Open an app so that the window comes up, eg. "Files" 4) Move the mouse pointer to the left edge again. 5) See that the screen goes black for a second, but the mouse pointer stays visible. Observation 1: At first I thought that it was related to dash-to-dock because moving the mouse to the area where I used to have the dock exhibits the flicker (I moved it to bottom for GNOME 40). But it turns out that it doesn't matter: I can turn off the extension completely or move it back to the left and the flicker always occurs. Observation 2: It doesn't happen without any window onscreen. Having a program minimized to the dock doesn't suffice to exhibit the bug. I have to bring up the window and then the bug shows up. Fun Fact 1: "Files" exhibits it more "aggresively" than "Terminal". It is easier to trigger. With gnome-terminal I sometimes can hit the edge with the pointer without triggering the glitch. Observation 3: I cannot record the issue: Recording a screencast via "Ctrl-Alt-Shift-R" doesn't work. Well, the screencasting itself does work, but when recording the screencast the glitch simply doesn't happen. I am a bit lost further debugging this, any help is highly welcome. I guess that my observations rather hint at mutter being to blame. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mutter 40.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 23:03:53 2021 InstallationDate: Installed on 2018-02-23 (1293 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943083/+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 1945112] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1945112 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1945112 Title: AirPod volume is too low - stack exchange fix works Status in linux package in Ubuntu: Incomplete Bug description: see https://unix.stackexchange.com/questions/437468/bluetooth-headset- volume-too-low-only-in-arch ==Reproducer== 1) install Ubuntu 20.4 2) pair with a set of Apple AirPods 3) try to listen to some video 4) put volume up to maximum and repeat 3) 5) turn on volume boost and repeat 4) ==Actual result== at any stage 3, 4 or 5 the audio from the AirPods is extremely quiet, almost too low to hear (though after 5 it becomes audible in a quiet environment) ==Expected result=== It should be possible to hear the sound through the AirPods by default. ==Comment== The following instructions from the stack exchange answer fix the problem Edit /lib/systemd/system/bluetooth.service and change ExecStart=/usr/lib/bluetooth/bluetoothd to ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=avrcp ==Version information== $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.3 Candidate: 5.53-0ubuntu3.3 Version table: *** 5.53-0ubuntu3.3 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.53-0ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 5.53-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945112/+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 1943083] Re: [i915] [Braswell] screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen
Hello Daniel! Sorry for the late reply. The requested log is attached. "Sep 26 17:47:05 amano-desktop gnome-shell[41942]: Failed to post KMS update: drmModeAtomicCommit: Das Argument ist ungültig Sep 26 17:47:05 amano-desktop gnome-shell[41942]: Page flip discarded: drmModeAtomicCommit: Das Argument ist ungültig Sep 26 17:47:05 amano-desktop gnome-shell[41942]: Failed to post KMS update: drmModeAtomicCommit: Das Argument ist ungültig Sep 26 17:47:05 amano-desktop gnome-shell[41942]: Page flip discarded: drmModeAtomicCommit: Das Argument ist ungültig" The german part means (as you would have guessed): The argument is invalid. That's the error that the gnome-shell process throws. Thanks for investigating. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943083/+attachment/5528181/+files/journal.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/1943083 Title: [i915] [Braswell] screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen Status in linux package in Ubuntu: Incomplete Bug description: I reported that against mutter, but it can be gnome-shell as well, or even Intel driver/kernel related. It happens since my switch to Impish, I have never seen that issue before. Integrated Intel HD graphics 400 onboard. STEPS to reproduce: 1) Move the mouse pointer to the left edge of the screen 2) See that everything works as expected 3) Open an app so that the window comes up, eg. "Files" 4) Move the mouse pointer to the left edge again. 5) See that the screen goes black for a second, but the mouse pointer stays visible. Observation 1: At first I thought that it was related to dash-to-dock because moving the mouse to the area where I used to have the dock exhibits the flicker (I moved it to bottom for GNOME 40). But it turns out that it doesn't matter: I can turn off the extension completely or move it back to the left and the flicker always occurs. Observation 2: It doesn't happen without any window onscreen. Having a program minimized to the dock doesn't suffice to exhibit the bug. I have to bring up the window and then the bug shows up. Fun Fact 1: "Files" exhibits it more "aggresively" than "Terminal". It is easier to trigger. With gnome-terminal I sometimes can hit the edge with the pointer without triggering the glitch. Observation 3: I cannot record the issue: Recording a screencast via "Ctrl-Alt-Shift-R" doesn't work. Well, the screencasting itself does work, but when recording the screencast the glitch simply doesn't happen. I am a bit lost further debugging this, any help is highly welcome. I guess that my observations rather hint at mutter being to blame. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mutter 40.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 23:03:53 2021 InstallationDate: Installed on 2018-02-23 (1293 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943083/+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 1945112] Re: AirPod volume is too low - stack exchange fix works
The laptop hardware this is done on is a Dell XPS-13, though I suppose this shouldn't make a difference. ** Attachment added: "lspci-vnvn.log according to bug reporting instructions" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945112/+attachment/5528180/+files/lspci-vnvn.log -- 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/1945112 Title: AirPod volume is too low - stack exchange fix works Status in linux package in Ubuntu: New Bug description: see https://unix.stackexchange.com/questions/437468/bluetooth-headset- volume-too-low-only-in-arch ==Reproducer== 1) install Ubuntu 20.4 2) pair with a set of Apple AirPods 3) try to listen to some video 4) put volume up to maximum and repeat 3) 5) turn on volume boost and repeat 4) ==Actual result== at any stage 3, 4 or 5 the audio from the AirPods is extremely quiet, almost too low to hear (though after 5 it becomes audible in a quiet environment) ==Expected result=== It should be possible to hear the sound through the AirPods by default. ==Comment== The following instructions from the stack exchange answer fix the problem Edit /lib/systemd/system/bluetooth.service and change ExecStart=/usr/lib/bluetooth/bluetoothd to ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=avrcp ==Version information== $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.3 Candidate: 5.53-0ubuntu3.3 Version table: *** 5.53-0ubuntu3.3 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.53-0ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 5.53-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945112/+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 1945112] [NEW] AirPod volume is too low - stack exchange fix works
Public bug reported: see https://unix.stackexchange.com/questions/437468/bluetooth-headset- volume-too-low-only-in-arch ==Reproducer== 1) install Ubuntu 20.4 2) pair with a set of Apple AirPods 3) try to listen to some video 4) put volume up to maximum and repeat 3) 5) turn on volume boost and repeat 4) ==Actual result== at any stage 3, 4 or 5 the audio from the AirPods is extremely quiet, almost too low to hear (though after 5 it becomes audible in a quiet environment) ==Expected result=== It should be possible to hear the sound through the AirPods by default. ==Comment== The following instructions from the stack exchange answer fix the problem Edit /lib/systemd/system/bluetooth.service and change ExecStart=/usr/lib/bluetooth/bluetoothd to ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=avrcp ==Version information== $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 $ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.3 Candidate: 5.53-0ubuntu3.3 Version table: *** 5.53-0ubuntu3.3 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.53-0ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 5.53-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version.log according to bug reporting instructions" https://bugs.launchpad.net/bugs/1945112/+attachment/5528179/+files/version.log -- 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/1945112 Title: AirPod volume is too low - stack exchange fix works Status in linux package in Ubuntu: New Bug description: see https://unix.stackexchange.com/questions/437468/bluetooth-headset- volume-too-low-only-in-arch ==Reproducer== 1) install Ubuntu 20.4 2) pair with a set of Apple AirPods 3) try to listen to some video 4) put volume up to maximum and repeat 3) 5) turn on volume boost and repeat 4) ==Actual result== at any stage 3, 4 or 5 the audio from the AirPods is extremely quiet, almost too low to hear (though after 5 it becomes audible in a quiet environment) ==Expected result=== It should be possible to hear the sound through the AirPods by default. ==Comment== The following instructions from the stack exchange answer fix the problem Edit /lib/systemd/system/bluetooth.service and change ExecStart=/usr/lib/bluetooth/bluetoothd to ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=avrcp ==Version information== $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.3 Candidate: 5.53-0ubuntu3.3 Version table: *** 5.53-0ubuntu3.3 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.53-0ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 5.53-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945112/+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 1927808] Re: rtw88_8821ce causes freeze
I have the same problem on a LENOVO ideacentre AIO 330-20IGM. I put options rtw88_pci disable_aspm=1 in /etc/modprobe.d/rtw88_pci.conf as told by PK Shih, but when I try to check if the change took effect by running cat /sys/module/rtw_pci/parameters/disable_aspm it throws an error that no file or directory. -- 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/1927808 Title: rtw88_8821ce causes freeze Status in linux package in Ubuntu: Confirmed Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
@Royi, Please try 5.11.0-37, if -37 doesn't work, please upload the dmesg. -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Released Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Precsion 5760 - 5.11.0-36-generic, issue not solved (still dummy device) -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Released Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+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 1944752] Re: AER PCIe Bus Error for Asus X541UVK
** Patch removed: "PCI-AER-Clear-error-device-AER-registers-in-aer_irq.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752/+attachment/5528093/+files/PCI-AER-Clear-error-device-AER-registers-in-aer_irq.patch -- 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/1944752 Title: AER PCIe Bus Error for Asus X541UVK Status in linux package in Ubuntu: Incomplete Bug description: I already posted this on the Ubuntu Forums and I'm revisiting it now with more information and accuracy. Whenever I try to install any flavor of *buntu, I always run into this problem; a process taking up all of my CPU and after a while, it crashes the system and the whole screen goes black with text spamming. It shows some PCI errors non-stop, and following some guides online i tried to fix it but never actually succeeded. The distro I was trying to install this time was the default 20.04.2 Ubuntu. My PC is a laptop, it's an ASUS X541UVK with an i7 7500U and Geforce 920MX. At first I thought that there was a problem with the Nvidia GPU but it appears to be with the Realtek BT card. I went to follow this guide: https://forums.linuxmint.com/viewtopic.php?t=305970 (since using pci=nomsi once solved the issue some time ago) And the reproduced steps from the guide above are here (from the live usb): https://imgur.com/a/enq5UCt However this still doesn't solve my problems. I submitted my information at the time on this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 But now I made a duplicate of the bug since my pc has slightly different hardware. Also, I have a little bit more free time now. So, this time, I tried again with Ubuntu 20.04.3 and the results were pretty much the same; after booting up Ubuntu reported an "internal error" and I just managed to open the Gnome System Monitor (and sort the processes by CPU usage) just before the entire pc froze. Here are some pictures: https://imgur.com/a/Sd7TO4y Then, as suggested in the original bug report ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/139 ), I tried booting using the "pci=noaer" option, and the desktop at first booted fine, much quicker than before also, but for a few seconds the screen went black and these appeared on screen: https://imgur.com/a/Ppq2D0W Then after that it just went back to normal, and I didn't notice any anomaly. Also here (again, as suggested in the other bug report) I copy-pasted the results of "lspci -nn" and "dmesg": https://pastebin.com/HMvdhvnz https://pastebin.com/pnjPNcWr I really hope this helps towards finding the issue :) for anything else for me to try, feel free to suggest and I'll try it and report the results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752/+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 1943469] Re: [Asus X541NC] wakes up from sleep mode after 1 second
thank you for your help. at least i know now how to enable sleep, although the problem still persists. i will try to find a way to make this permanent, so i don't have to run it on terminal each time i turn on computer... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943469 Title: [Asus X541NC] wakes up from sleep mode after 1 second Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: computer "wakes up" from sleep mode after 1 second no matter if i wait the given time for it to sleep, or if i put it to sleep with terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 13 18:56:14 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller [1043:16a0] Subsystem: ASUSTeK Computer Inc. GK107M [GeForce 810M] [1043:137e] InstallationDate: Installed on 2021-07-30 (44 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 0bda:b721 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X541NC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=264f931b-e96b-44e9-a13d-bf5c3236a567 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541NC.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541NC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541NC.307:bd06/19/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX541NC:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX541NC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X541NC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943469/+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 1944752] Re: AER PCIe Bus Error for Asus X541UVK
Hello Riccardo o/ Please find the correct patch attached. Unfortunately, I do not have a system that outputs the same AER errors as yours so I am unable to test it out. It would really help if you could please test this patch out and let me know, if it solves the AER message spew. Thanks, Naveen ** Patch added: "PCI-AER-Clear-error-device-AER-registers-in-aer_irq.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752/+attachment/5528116/+files/PCI-AER-Clear-error-device-AER-registers-in-aer_irq.patch -- 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/1944752 Title: AER PCIe Bus Error for Asus X541UVK Status in linux package in Ubuntu: Incomplete Bug description: I already posted this on the Ubuntu Forums and I'm revisiting it now with more information and accuracy. Whenever I try to install any flavor of *buntu, I always run into this problem; a process taking up all of my CPU and after a while, it crashes the system and the whole screen goes black with text spamming. It shows some PCI errors non-stop, and following some guides online i tried to fix it but never actually succeeded. The distro I was trying to install this time was the default 20.04.2 Ubuntu. My PC is a laptop, it's an ASUS X541UVK with an i7 7500U and Geforce 920MX. At first I thought that there was a problem with the Nvidia GPU but it appears to be with the Realtek BT card. I went to follow this guide: https://forums.linuxmint.com/viewtopic.php?t=305970 (since using pci=nomsi once solved the issue some time ago) And the reproduced steps from the guide above are here (from the live usb): https://imgur.com/a/enq5UCt However this still doesn't solve my problems. I submitted my information at the time on this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 But now I made a duplicate of the bug since my pc has slightly different hardware. Also, I have a little bit more free time now. So, this time, I tried again with Ubuntu 20.04.3 and the results were pretty much the same; after booting up Ubuntu reported an "internal error" and I just managed to open the Gnome System Monitor (and sort the processes by CPU usage) just before the entire pc froze. Here are some pictures: https://imgur.com/a/Sd7TO4y Then, as suggested in the original bug report ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/139 ), I tried booting using the "pci=noaer" option, and the desktop at first booted fine, much quicker than before also, but for a few seconds the screen went black and these appeared on screen: https://imgur.com/a/Ppq2D0W Then after that it just went back to normal, and I didn't notice any anomaly. Also here (again, as suggested in the other bug report) I copy-pasted the results of "lspci -nn" and "dmesg": https://pastebin.com/HMvdhvnz https://pastebin.com/pnjPNcWr I really hope this helps towards finding the issue :) for anything else for me to try, feel free to suggest and I'll try it and report the results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752/+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 1945057] Re: Geniatech T230C2 TV dongle is unusable on kernel 5.x.y
** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Focal) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-raspi (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1945057 Title: Geniatech T230C2 TV dongle is unusable on kernel 5.x.y Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: New Bug description: This has been patched for newer kernels upstream, and also on other distros. See: https://github.com/raspberrypi/linux/issues/3809 The symptom you see is this, repeated continually: Sep 25 16:01:36 tardis kernel: [16585.080473] usb 1-1.1.2: dvb_usb_v2: usb_bulk_msg() failed=-110 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-1043-raspi 5.4.0-1043.47 ProcVersionSignature: Ubuntu 5.4.0-1043.47-raspi 5.4.133 Uname: Linux 5.4.0-1043-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: arm64 CasperMD5CheckResult: skip Date: Sat Sep 25 15:57:07 2021 ImageMediaBuild: 20200812 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1945057/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
Have created a 100% reliable reproducer test case and also determined the Ubuntu-specific patch 4701-enable-ARC-FILL-LOCKED-flag.patch to fix Bug #1900889 is likely the cause. [Test Case] The important parts are: - Use encryption - rsync the zfs git tree - Use parallel I/O from silversearcher-ag to access it after a reboot. A simple "find ." or "find . -exec cat {} > /dev/null \;" does not reproduce the issue. Reproduction done using a libvirt VM installed from the Ubuntu Impish daily livecd using a normal ext4 root but with a second 4GB /dev/vdb disk for zfs later = Preparation apt install silversearcher-ag git zfs-dkms zfsutils-linux echo -n testkey2 > /root/testkey git clone https://github.com/openzfs/zfs /root/zfs = Test Execution zpool create test /dev/vdb zfs create test/test -o encryption=on -o keyformat=passphrase -o keylocation=file:///root/testkey rsync -va --progress -HAX /root/zfs/ /test/test/zfs/ # If you access the data now it works fine. reboot zfs load-key test/test zfs mount -a cd /test/test/zfs/ ag DISKS= = Test Result ag hangs, "sudo dmesg" shows an exception [Analysis] I rebuilt the zfs-linux 2.0.6-1ubuntu1 package from ppa:colin-king/zfs-impish without the Ubuntu-specific patch ubuntu/4701-enable-ARC-FILL-LOCKED-flag.patch which fixed Bug #1900889. With this patch disabled the issue does not reproduce. Re-enabling the patch it reproduces reliably every time again. Seems this bug was never sent upstream. No code changes upstream setting the flag ARC_FILL_IN_PLACE appear to have been added since that I can see however interestingly the code for this ARC_FILL_IN_PLACE handling was added to fix a similar sounding issue "Raw receive fix and encrypted objset security fix" in https://github.com/openzfs/zfs/commit/69830602de2d836013a91bd42cc8d36bbebb3aae . This first shipped in zfs 0.8.0 and the original bug was filed against 0.8.3. I also have found the same issue as the original Launchpad bug reported upstream without any fixes and a lot of discussion (and quite a few duplicates linking back to 11679): https://github.com/openzfs/zfs/issues/11679 https://github.com/openzfs/zfs/issues/12014 Without fully understanding the ZFS code in relation to this flag, the code at https://github.com/openzfs/zfs/blob/ce2bdcedf549b2d83ae9df23a3fa0188b33327b7/module/zfs/arc.c#L2026 talks about how this flag is to do with decrypting blocks in the ARC and doing so 'inplace'. It makes some sense thus that I need encryption to reproduce it and it works best after a reboot (thus flushing the ARC) and why I can still read the data in the test case before doing a reboot when it then fails. This patch was added in 0.8.4-1ubuntu15 and I first experienced the issue somewhere between 0.8.4-1ubuntu11 and 0.8.4-1ubuntu16. So it all adds up and I suggest that this patch should be reverted. ** Bug watch added: github.com/openzfs/zfs/issues #11679 https://github.com/openzfs/zfs/issues/11679 ** Bug watch added: github.com/openzfs/zfs/issues #12014 https://github.com/openzfs/zfs/issues/12014 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in zfs-linux package in Ubuntu: In Progress Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Dec
[Kernel-packages] [Bug 1945046] Re: ZFS related tests are failing with F-oem-5.14
** Changed in: linux-oem-5.14 (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945046 Title: ZFS related tests are failing with F-oem-5.14 Status in ubuntu-kernel-tests: New Status in linux-oem-5.14 package in Ubuntu: New Bug description: linux-oem-5.14/5.14.0-1004.4 Tests like: * ubuntu_zfs_fstest * ubuntu_zfs_smoke_test * ubuntu_zfs_stress * ubuntu_zfs_xfs_generic Are failing with: modprobe: FATAL: Module zfs not found in directory /lib/modules/5.14.0-1004-oem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1945046/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
While trying to setup a reproducer that would excercise chrome or wine or something I stumbled across the following reproducer that worked twice in a row in a libvirt VM on my machine today. The general gist is to (1) Create a zfs filesystem with "-o encryption=aes-256-gcm -o compression=zstd -o atime=off -o keyformat=passphrase" (2) rsync a copy of the openzfs git tree into it (3) Reboot (4) Use silversearcher-ag to search the directory for "DISKS=" Precise steps: mkdir src cd src git clone https://github.com/openzfs/zfs sudo apt install zfsutils-linux zfs-initramfs sudo zpool create tank /dev/vdb sudo zfs create tank/lathiat2 -o encryption=aes-256-gcm -o compression=zstd -o atime=off -o keyformat=passphrase rsync -va --progress -HAX /etc/skel /tank/lathiat2/; chown -R lathiat:lathiat /tank/lathiat2; rsync -va --progress /home/lathiat/src/ /tank/lathiat2/src/; chown -R lathiat:lathiat /tank/lathiat2/src/ # reboot sudo zfs load-key tank/lathiat2 sudo zfs mount -a cd /tank/lathiat2/src/zfs/ ag DISKS= Hit on the exact same crash: [ 61.377929] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed [ 61.377930] PANIC at zfs_znode.c:339:zfs_znode_sa_init() Now will test this out on the beta 2.0.6 package and also see if the standard zfs test suite will trigger it or not as a matter of somewhat curiosity. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in zfs-linux package in Ubuntu: In Progress Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __c
[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend
Same problem here on my XPS 9310 all-in-one. -- 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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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