[Kernel-packages] [Bug 1950706] Re: VMs running under qemu+kvm can't use xsaves processor feature
To help this a bit, the two commits I've seen (there might be others) are https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=52297436199dd https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7204160eb7809 Of those the former is in Focals 5.4 since Ubuntu-kvm-5.4.0-1036.37 The latter is missing. Unless the kernel Team says other commits are needed making this too complex maybe a Focal 5.4 kernel with the second commit backported would allo Aaron to test if this commit is enough on his HW? OTOH the second commit should actually only cache the value, so maybe there are other commits needed anyway, I haven't have more time to look for less obvious commits and the kernel team will be better in doing so anyway. -- 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/1950706 Title: VMs running under qemu+kvm can't use xsaves processor feature Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Invalid Bug description: Virtual machines running under qemu using KVM acceleration run with `-cpu host` can't use the xsaves feature of the processor. An example guest dmesg log is attached, see errors about "unchecked MSR access error". Using a `-cpu` model that doesn't advertise xsaves such as `EPYC` fixes the problem on the guest. The host cpu does support xsaves and Ubuntu doesn't seem to have any issues with it. The guest dmesg provided is running linux mainline 5.15, but the issue happens with every kernel version I've tried, including centos on 4.18.0. The host cpu is a Ryzen 5 3600 nested guests have trouble running in a guest with `-cpu host` or even `-cpu EPYC`. They tend to run, but freeze before they finish booting at random times. Not sure if it's related. Nested guests do seem to be able to run with `-cpu kvm64`. There are no dmesg errors when a nested guest freezes. The Ubuntu host version: Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy qemu-system-x86 qemu-system-x86: Installed: 1:4.2-3ubuntu6.18 Candidate: 1:4.2-3ubuntu6.18 Version table: *** 1:4.2-3ubuntu6.18 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2-3ubuntu6.17 500 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:4.2-3ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu (not installed) ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Nov 12 00:19:10 2021 InstallationDate: Installed on 2021-10-20 (22 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) MachineType: System manufacturer System Product Name ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=screen-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=15509878-abfa-45b1-b8c2-c99db1ececf7 ro SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4002 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4002:bd06/15/2021:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
@manolo once the fix is applied to the generic kernel all the other derivatives will be updated as well. About the ISO I need to check, it'd make sense to update that as well, since there's a critical boot problem in this case. -- 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/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Status in linux source package in Jammy: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro 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.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1950706] Re: VMs running under qemu+kvm can't use xsaves processor feature
Thanks for trying these different things Aaron, by that test result that means that we are actually looking for a kernel commit/fix. The HWE kernel is, among other things, meant to provide new features and better support for new hardware - so in your case you can just continue to use that. @Kernel Team - I'd still ask you to check if there is an individual patch for xsaves on those chips that would make sense to backport to the non-HWE Focal kernel - added a bug task for that? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: Incomplete => Invalid ** 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/1950706 Title: VMs running under qemu+kvm can't use xsaves processor feature Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Invalid Bug description: Virtual machines running under qemu using KVM acceleration run with `-cpu host` can't use the xsaves feature of the processor. An example guest dmesg log is attached, see errors about "unchecked MSR access error". Using a `-cpu` model that doesn't advertise xsaves such as `EPYC` fixes the problem on the guest. The host cpu does support xsaves and Ubuntu doesn't seem to have any issues with it. The guest dmesg provided is running linux mainline 5.15, but the issue happens with every kernel version I've tried, including centos on 4.18.0. The host cpu is a Ryzen 5 3600 nested guests have trouble running in a guest with `-cpu host` or even `-cpu EPYC`. They tend to run, but freeze before they finish booting at random times. Not sure if it's related. Nested guests do seem to be able to run with `-cpu kvm64`. There are no dmesg errors when a nested guest freezes. The Ubuntu host version: Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy qemu-system-x86 qemu-system-x86: Installed: 1:4.2-3ubuntu6.18 Candidate: 1:4.2-3ubuntu6.18 Version table: *** 1:4.2-3ubuntu6.18 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2-3ubuntu6.17 500 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:4.2-3ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu (not installed) ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Nov 12 00:19:10 2021 InstallationDate: Installed on 2021-10-20 (22 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) MachineType: System manufacturer System Product Name ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=screen-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=15509878-abfa-45b1-b8c2-c99db1ececf7 ro SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4002 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4002:bd06/15/2021:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1951055] [NEW] Reinstate ACPI S5 for reboot
Public bug reported: [Impact] On some systems, Intel WiFi device may stop working after reboot. [Fix] Use ACPI S5 for reboot. [Test] 2000 times of reboot stress, and Intel WiFi continues work on affected system. [Where problems could occur] There was a bug introduced by this patch, but the user didn't want to find the root cause. Since we have more control on Ubuntu kernel, we'll fix the root cause properly this time. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Tags: oem-priority originate-from-1948635 somerville ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => Medium ** Tags added: oem-priority originate-from-1948635 somerville -- 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/1951055 Title: Reinstate ACPI S5 for reboot Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: [Impact] On some systems, Intel WiFi device may stop working after reboot. [Fix] Use ACPI S5 for reboot. [Test] 2000 times of reboot stress, and Intel WiFi continues work on affected system. [Where problems could occur] There was a bug introduced by this patch, but the user didn't want to find the root cause. Since we have more control on Ubuntu kernel, we'll fix the root cause properly this time. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951055/+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 1950721] Re: Re-enable CONFIG_PINCTRL_ELKHARTLAKE
** Changed in: linux-intel-5.13 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950721 Title: Re-enable CONFIG_PINCTRL_ELKHARTLAKE Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Fix Committed Bug description: We have test BIOS now for supporting pinctrl. From what we learnt, ODMs also got the BIOS fix, it's now time to re-enable this kernel config. [Impact] Without this fix, pinctrl functionality will be missing. [Test plan] 1. Make sure the computer has a BIOS that supports pinctrl for EHL 2. Before installing the new kernel, GPIO should not work 3. Install the new kernel, and confirm GPIO works [Where problems could occur] If the computer does not have a BIOS that support pinctrl, you will get an error like "kernel NULL pointer dereference in intel_pinctrl_get_soc_data" during system boot. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950721/+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 1950721] Re: Re-enable CONFIG_PINCTRL_ELKHARTLAKE
** Description changed: We have test BIOS now for supporting pinctrl. From what we learnt, ODMs also got the BIOS fix, it's now time to re-enable this kernel config. + + [Impact] + Without this fix, pinctrl functionality will be missing. + + [Test plan] + 1. Make sure the computer has a BIOS that supports pinctrl for EHL + 2. Before installing the new kernel, GPIO should not work + 3. Install the new kernel, and confirm GPIO works + + [Where problems could occur] + If the computer does not have a BIOS that support pinctrl, you will get an error like "kernel NULL pointer dereference in intel_pinctrl_get_soc_data" during system boot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950721 Title: Re-enable CONFIG_PINCTRL_ELKHARTLAKE Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: In Progress Bug description: We have test BIOS now for supporting pinctrl. From what we learnt, ODMs also got the BIOS fix, it's now time to re-enable this kernel config. [Impact] Without this fix, pinctrl functionality will be missing. [Test plan] 1. Make sure the computer has a BIOS that supports pinctrl for EHL 2. Before installing the new kernel, GPIO should not work 3. Install the new kernel, and confirm GPIO works [Where problems could occur] If the computer does not have a BIOS that support pinctrl, you will get an error like "kernel NULL pointer dereference in intel_pinctrl_get_soc_data" during system boot. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950721/+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 1950721] Re: Re-enable CONFIG_PINCTRL_ELKHARTLAKE
** Changed in: linux-intel-5.13 (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950721 Title: Re-enable CONFIG_PINCTRL_ELKHARTLAKE Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: In Progress Bug description: We have test BIOS now for supporting pinctrl. From what we learnt, ODMs also got the BIOS fix, it's now time to re-enable this kernel config. [Impact] Without this fix, pinctrl functionality will be missing. [Test plan] 1. Make sure the computer has a BIOS that supports pinctrl for EHL 2. Before installing the new kernel, GPIO should not work 3. Install the new kernel, and confirm GPIO works [Where problems could occur] If the computer does not have a BIOS that support pinctrl, you will get an error like "kernel NULL pointer dereference in intel_pinctrl_get_soc_data" during system boot. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950721/+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 1786013] Autopkgtest regression report (linux-meta-oracle-5.4/5.4.0.1058.62~18.04.38)
All autopkgtests for the newly accepted linux-meta-oracle-5.4 (5.4.0.1058.62~18.04.38) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
Status changed to 'Confirmed' because the bug affects multiple users. ** 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1751497 Title: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Won't Fix Bug description: [ 136.559610] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Hello, from time to time I find this annoying messages in dmesg in various Ubuntu versions (I believe since 16.04 or 16.10 up until now, including Bionic Beaver daily build). From time to time, the gdm3 crashes. The current HW/SW setup will be described below. I cannot replicate the situation, but it happens. See the excerpt from dmesg output below. [9.386558] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready [9.399079] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12 [9.399134] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13 [9.399208] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14 [9.399274] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15 [ 12.312741] r8169 :03:00.0 enp3s0: link up [ 12.312748] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready [ 13.439863] rfkill: input handler disabled [ 15.125569] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. [ 136.559610] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 [ 136.559618] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2 [ 136.559619] nouveau :01:00.0: msvld: unable to load firmware data [ 136.559622] nouveau :01:00.0: msvld: init failed, -19 [ 1376.746130] lp: driver loaded but no devices found [ 1376.756790] st: Version 20160209, fixed bufsize 32768, s/g segs 256 [ 1381.398605] do_IRQ: 1.37 No irq handler for vector rr HW setup: Asrock Extreme 6 Z97 Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz, 3563 MHz nVidia GK107 [GeForce GT 640] SW setup: Linux bionic 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@bionic:~# lsmod | grep nouveau nouveau 1716224 5 i2c_algo_bit 16384 1 nouveau ttm 106496 1 nouveau drm_kms_helper167936 1 nouveau mxm_wmi16384 1 nouveau drm 401408 8 nouveau,ttm,drm_kms_helper wmi24576 2 mxm_wmi,nouveau video 40960 1 nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751497/+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 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
still present in ubuntu 20.04 Linux 5.11.0-40-generic #44~20.04.2-Ubuntu SMP Tue Oct 26 18:07:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux 01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) Nov 15 18:37:52 localhost kernel: [ 4754.000821] nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2 Nov 15 18:37:52 localhost kernel: [ 4754.000857] nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084d failed with error -2 Nov 15 18:37:52 localhost kernel: [ 4754.000860] nouveau :01:00.0: msvld: unable to load firmware data Nov 15 18:37:52 localhost kernel: [ 4754.000865] nouveau :01:00.0: msvld: init failed, -19 Nov 15 18:38:01 localhost kernel: [ 4763.095679] nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2 lsmod | grep nouveau nouveau 1986560 38 mxm_wmi16384 1 nouveau drm_ttm_helper 16384 1 nouveau ttm73728 2 drm_ttm_helper,nouveau drm_kms_helper237568 1 nouveau i2c_algo_bit 16384 1 nouveau video 53248 1 nouveau wmi32768 2 mxm_wmi,nouveau drm 548864 18 drm_kms_helper,drm_ttm_helper,ttm,nouveau NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Nov 15 18:38:01 localhost kernel: [ 4763.095707] nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084d failed with error -2 Nov 15 18:38:01 localhost kernel: [ 4763.095710] nouveau :01:00.0: msvld: unable to load firmware data Nov 15 18:38:01 localhost kernel: [ 4763.095715] nouveau :01:00.0: msvld: init failed, -19 -- 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/1751497 Title: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Won't Fix Bug description: [ 136.559610] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Hello, from time to time I find this annoying messages in dmesg in various Ubuntu versions (I believe since 16.04 or 16.10 up until now, including Bionic Beaver daily build). From time to time, the gdm3 crashes. The current HW/SW setup will be described below. I cannot replicate the situation, but it happens. See the excerpt from dmesg output below. [9.386558] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready [9.399079] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12 [9.399134] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13 [9.399208] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14 [9.399274] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15 [ 12.312741] r8169 :03:00.0 enp3s0: link up [ 12.312748] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready [ 13.439863] rfkill: input handler disabled [ 15.125569] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. [ 136.559610] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 [ 136.559618] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2 [ 136.559619] nouveau :01:00.0: msvld: unable to load firmware data [ 136.559622] nouveau :01:00.0: msvld: init failed, -19 [ 1376.746130] lp: driver loaded but no devices found [ 1376.756790] st: Version 20160209, fixed bufsize 32768, s/g segs 256 [ 1381.398605] do_IRQ: 1.37 No irq handler for vector rr HW setup: Asrock Extreme 6 Z97 Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz, 3563 MHz nVidia GK107 [GeForce GT 640] SW setup: Linux bionic 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@bionic:~# lsmod | grep nouveau nouveau 1716224 5 i2c_algo_bit 16384 1 nouveau ttm 106496 1 nouveau drm_kms_helper167936 1 nouveau mxm_wmi16384 1 nouveau drm 401408 8 nouveau,ttm,drm_kms_helper wmi24576 2 mxm_wmi,nouveau video 40960 1 nouveau To manage
[Kernel-packages] [Bug 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
** Changed in: linux (Ubuntu) Status: Expired => 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/1751497 Title: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Won't Fix Bug description: [ 136.559610] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Hello, from time to time I find this annoying messages in dmesg in various Ubuntu versions (I believe since 16.04 or 16.10 up until now, including Bionic Beaver daily build). From time to time, the gdm3 crashes. The current HW/SW setup will be described below. I cannot replicate the situation, but it happens. See the excerpt from dmesg output below. [9.386558] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready [9.399079] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12 [9.399134] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13 [9.399208] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14 [9.399274] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15 [ 12.312741] r8169 :03:00.0 enp3s0: link up [ 12.312748] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready [ 13.439863] rfkill: input handler disabled [ 15.125569] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. [ 136.559610] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 [ 136.559618] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2 [ 136.559619] nouveau :01:00.0: msvld: unable to load firmware data [ 136.559622] nouveau :01:00.0: msvld: init failed, -19 [ 1376.746130] lp: driver loaded but no devices found [ 1376.756790] st: Version 20160209, fixed bufsize 32768, s/g segs 256 [ 1381.398605] do_IRQ: 1.37 No irq handler for vector rr HW setup: Asrock Extreme 6 Z97 Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz, 3563 MHz nVidia GK107 [GeForce GT 640] SW setup: Linux bionic 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@bionic:~# lsmod | grep nouveau nouveau 1716224 5 i2c_algo_bit 16384 1 nouveau ttm 106496 1 nouveau drm_kms_helper167936 1 nouveau mxm_wmi16384 1 nouveau drm 401408 8 nouveau,ttm,drm_kms_helper wmi24576 2 mxm_wmi,nouveau video 40960 1 nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751497/+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 1940780] Re: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04
The bug was closed because comment #7 went unanswered. -- 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/1940780 Title: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04 Status in linux-hwe-5.11 package in Ubuntu: Expired Bug description: Just installed ubuntu 20.04 and the screen has been flickering all through. tried applying the ubuntu on Wayland solution but no change. Please help with a solution on workaround for this. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 22 21:39:46 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170] InstallationDate: Installed on 2021-08-22 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP EliteBook Folio G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=4b37b99a-c4bf-42ca-9e24-733b7a991c4d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.release: 1.10 dmi.bios.vendor: HP dmi.bios.version: N91 Ver. 01.10 dmi.board.name: 8170 dmi.board.vendor: HP dmi.board.version: KBC Version 29.68 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 41.104 dmi.modalias: dmi:bvnHP:bvrN91Ver.01.10:bd07/19/2016:br1.10:efr41.104:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.68:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook Folio G1 dmi.product.sku: Z5Z39US#ABA dmi.sys.vendor: HP 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/1940780/+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 1940285] Re: [Teclast F7] Laptop screen flickering on kernels above 5.4 (not included)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1940285 Title: [Teclast F7] Laptop screen flickering on kernels above 5.4 (not included) Status in linux package in Ubuntu: Expired Bug description: Recently, I installed Ubuntu 21.04 on my laptop and I was having the same problem I had like with others distros such as Fedora; for some reason, the screen just ramdonly and briefly turns off, (more like a flickering) and it also "autoregulates" a the brightness, just a little bit down and then a little bit up. I noticed I don't have this problem on Linux Mint, and I also noticed that going back to Kernel 5.8 on either Ubuntu 21.04 or 20.04.2 this problem stops. I have been using Mainline ( https://github.com/bkw777/mainline ) to install previous kernels (5.8 and 5.4 wok just fine, but anything above this problem comes again). Thanks so much beforehand. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285/+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 1940780] Re: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04
[Expired for linux-hwe-5.11 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-hwe-5.11 (Ubuntu) Status: Incomplete => Expired -- 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/1940780 Title: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04 Status in linux-hwe-5.11 package in Ubuntu: Expired Bug description: Just installed ubuntu 20.04 and the screen has been flickering all through. tried applying the ubuntu on Wayland solution but no change. Please help with a solution on workaround for this. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 22 21:39:46 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170] InstallationDate: Installed on 2021-08-22 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP EliteBook Folio G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=4b37b99a-c4bf-42ca-9e24-733b7a991c4d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.release: 1.10 dmi.bios.vendor: HP dmi.bios.version: N91 Ver. 01.10 dmi.board.name: 8170 dmi.board.vendor: HP dmi.board.version: KBC Version 29.68 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 41.104 dmi.modalias: dmi:bvnHP:bvrN91Ver.01.10:bd07/19/2016:br1.10:efr41.104:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.68:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook Folio G1 dmi.product.sku: Z5Z39US#ABA dmi.sys.vendor: HP 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/1940780/+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 1943729] Re: AMD impish Libvirt7.6 nested amd-v, rbd storage broken
[Expired for qemu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qemu (Ubuntu) Status: Incomplete => Expired -- 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/1943729 Title: AMD impish Libvirt7.6 nested amd-v, rbd storage broken Status in ceph package in Ubuntu: Expired Status in libvirt package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in qemu package in Ubuntu: Expired Bug description: Hello, Having issues with AMD and RBD Driver. Running on latest impish, using libvirt7.6ubuntu1. Having following setup (not sure if matters): Dedicated-Host (AMD) -> Level1-KVM (cpu-pass-through, rbd) -> "Customer-VM"=CVM ubuntu20.04 -> impish -> custom What happens? It seems Level1-KVM is struggeling with RBD storage access, breaking/preventing CVM's operating system to fully boot. Half of the booting process is going through, but later at random point in time (still booting the kernel) it seems to deadlock, letting CVM's CPU spin endless. Following tests setups i verified to isolate the issue: Dedicated-Host (Intel) -> Level1-KVM (impish=7.6,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, direct storage=virtio) -> CVM = works Dedicated-Host (Intel) -> Level1-KVM (focal=6.0,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, direct storage=virtio) -> CVM = works --- Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, rbd=virtio) -> CVM = stuck Out of those tests, the issue seems to be IMO located in libvirt 7.6, sadly im not able to check it against 7.4 (which was shortly available for impish, but was already removed from the repo mirror..). Any idears what could make an AMD passthrough break access of RBD, letting CVM stuck accessing storage? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1943729/+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 1943729] Re: AMD impish Libvirt7.6 nested amd-v, rbd storage broken
[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libvirt (Ubuntu) Status: Incomplete => Expired -- 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/1943729 Title: AMD impish Libvirt7.6 nested amd-v, rbd storage broken Status in ceph package in Ubuntu: Expired Status in libvirt package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in qemu package in Ubuntu: Expired Bug description: Hello, Having issues with AMD and RBD Driver. Running on latest impish, using libvirt7.6ubuntu1. Having following setup (not sure if matters): Dedicated-Host (AMD) -> Level1-KVM (cpu-pass-through, rbd) -> "Customer-VM"=CVM ubuntu20.04 -> impish -> custom What happens? It seems Level1-KVM is struggeling with RBD storage access, breaking/preventing CVM's operating system to fully boot. Half of the booting process is going through, but later at random point in time (still booting the kernel) it seems to deadlock, letting CVM's CPU spin endless. Following tests setups i verified to isolate the issue: Dedicated-Host (Intel) -> Level1-KVM (impish=7.6,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, direct storage=virtio) -> CVM = works Dedicated-Host (Intel) -> Level1-KVM (focal=6.0,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, direct storage=virtio) -> CVM = works --- Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, rbd=virtio) -> CVM = stuck Out of those tests, the issue seems to be IMO located in libvirt 7.6, sadly im not able to check it against 7.4 (which was shortly available for impish, but was already removed from the repo mirror..). Any idears what could make an AMD passthrough break access of RBD, letting CVM stuck accessing storage? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1943729/+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 1943729] Re: AMD impish Libvirt7.6 nested amd-v, rbd storage broken
[Expired for ceph (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ceph (Ubuntu) Status: Incomplete => Expired -- 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/1943729 Title: AMD impish Libvirt7.6 nested amd-v, rbd storage broken Status in ceph package in Ubuntu: Expired Status in libvirt package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in qemu package in Ubuntu: Expired Bug description: Hello, Having issues with AMD and RBD Driver. Running on latest impish, using libvirt7.6ubuntu1. Having following setup (not sure if matters): Dedicated-Host (AMD) -> Level1-KVM (cpu-pass-through, rbd) -> "Customer-VM"=CVM ubuntu20.04 -> impish -> custom What happens? It seems Level1-KVM is struggeling with RBD storage access, breaking/preventing CVM's operating system to fully boot. Half of the booting process is going through, but later at random point in time (still booting the kernel) it seems to deadlock, letting CVM's CPU spin endless. Following tests setups i verified to isolate the issue: Dedicated-Host (Intel) -> Level1-KVM (impish=7.6,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, direct storage=virtio) -> CVM = works Dedicated-Host (Intel) -> Level1-KVM (focal=6.0,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, direct storage=virtio) -> CVM = works --- Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, rbd=virtio) -> CVM = stuck Out of those tests, the issue seems to be IMO located in libvirt 7.6, sadly im not able to check it against 7.4 (which was shortly available for impish, but was already removed from the repo mirror..). Any idears what could make an AMD passthrough break access of RBD, letting CVM stuck accessing storage? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1943729/+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 1943684] Re: upgrading from 1.187.15 -> 1.187.16 breaks iwlwifi for intel 8260
[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Expired -- 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/1943684 Title: upgrading from 1.187.15 -> 1.187.16 breaks iwlwifi for intel 8260 Status in linux-firmware package in Ubuntu: Expired Bug description: After a reboot my wifi suddenly didn't work anymore, dmesg showed: [8.711330] iwlwifi :04:00.0: SecBoot CPU1 Status: 0x3040001, CPU2 Status: 0x0 [8.711336] iwlwifi :04:00.0: Collecting data: trigger 15 fired. [8.960114] iwlwifi :04:00.0: Not valid error log pointer 0x for Init uCode [8.960236] iwlwifi :04:00.0: Fseq Registers: [8.960285] iwlwifi :04:00.0: 0x355FFACF | FSEQ_ERROR_CODE [8.960340] iwlwifi :04:00.0: 0x5E555D0C | FSEQ_TOP_INIT_VERSION [8.960390] iwlwifi :04:00.0: 0x00440480 | FSEQ_CNVIO_INIT_VERSION [8.960439] iwlwifi :04:00.0: 0xA056 | FSEQ_OTP_VERSION [8.960488] iwlwifi :04:00.0: 0xBA8CC809 | FSEQ_TOP_CONTENT_VERSION [8.960537] iwlwifi :04:00.0: 0xBF49711A | FSEQ_ALIVE_TOKEN [8.960586] iwlwifi :04:00.0: 0x823938D2 | FSEQ_CNVI_ID [8.960635] iwlwifi :04:00.0: 0x01B9E7F7 | FSEQ_CNVR_ID [8.960684] iwlwifi :04:00.0: 0x0300 | CNVI_AUX_MISC_CHIP [8.960734] iwlwifi :04:00.0: 0x0BADCAFE | CNVR_AUX_MISC_CHIP [8.960783] iwlwifi :04:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [8.960841] iwlwifi :04:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [8.960891] iwlwifi :04:00.0: Failed to start INIT ucode: -110 [8.960903] iwlwifi :04:00.0: Collecting data: trigger 16 fired. [9.994975] iwlwifi :04:00.0: Failed to run INIT ucode: -110 first I thought it was something with secure boot however I didn't change anything in the bios and checking showed that it is infact disabled, also running sudo mokutil --sb-state shows SecureBoot disabled anyways I found out that I had an update of the package linux-firmware from 1.187.16 to 1.187.15 the day before. Downgrading to 1.187 (for unknown reason I couldn't find the binary of the old version 1.187.15 on my notebook nor on the internet anymore), and reloading the module as described in https://openterprise.it/2019/04/linux-reload-intel-wireless-card- kernel-module/ brought the wifi back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1943684/+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 1943729] Re: AMD impish Libvirt7.6 nested amd-v, rbd storage broken
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1943729 Title: AMD impish Libvirt7.6 nested amd-v, rbd storage broken Status in ceph package in Ubuntu: Expired Status in libvirt package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in qemu package in Ubuntu: Expired Bug description: Hello, Having issues with AMD and RBD Driver. Running on latest impish, using libvirt7.6ubuntu1. Having following setup (not sure if matters): Dedicated-Host (AMD) -> Level1-KVM (cpu-pass-through, rbd) -> "Customer-VM"=CVM ubuntu20.04 -> impish -> custom What happens? It seems Level1-KVM is struggeling with RBD storage access, breaking/preventing CVM's operating system to fully boot. Half of the booting process is going through, but later at random point in time (still booting the kernel) it seems to deadlock, letting CVM's CPU spin endless. Following tests setups i verified to isolate the issue: Dedicated-Host (Intel) -> Level1-KVM (impish=7.6,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, direct storage=virtio) -> CVM = works Dedicated-Host (Intel) -> Level1-KVM (focal=6.0,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, direct storage=virtio) -> CVM = works --- Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, rbd=virtio) -> CVM = stuck Out of those tests, the issue seems to be IMO located in libvirt 7.6, sadly im not able to check it against 7.4 (which was shortly available for impish, but was already removed from the repo mirror..). Any idears what could make an AMD passthrough break access of RBD, letting CVM stuck accessing storage? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1943729/+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 1943879] Re: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Expired Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more queues
[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels
Spotted on Focal OEM 5.13.0-1020.24 Running tests... tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855 Summary: passed 8 failed 1 broken 0 skipped 0 warnings 0 ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags added: 5.13 oen ** Changed in: linux-oem-5.13 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Jammy) Status: New => Invalid -- 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/1950644 Title: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Released 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.13 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.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: ubuntu_ltp / finit_module02 fails on Bionic Azure FIPS (4.15.0-2039.43), Bionic Azure (4.15.0-1127.140), Focal Azure (5.4.0-1064.67): tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+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 1803881] Re: thermal thermal_zone4: failed to read out thermal zone (-61)
I see the same error on HP Elitebook 820 G3 on iwlwifi_1 using linux-
firmware 1.187.20 on Ubuntu 20.04
--
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/1803881
Title:
thermal thermal_zone4: failed to read out thermal zone (-61)
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
Thermald can't read zone4. It's making my fan go crazy, this issue
seems to be a bit more controlled in 18.10.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
sudo apt-cache policy thermald
thermald:
Installed: 1.7.0-5ubuntu1
Candidate: 1.7.0-5ubuntu1
Version table:
*** 1.7.0-5ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
cat /sys/class/thermal/thermal_zone4/type
iwlwifi
find /sys/class/thermal/thermal_zone4/ -type f -print -exec cat {} \;
/sys/class/thermal/thermal_zone4/uevent
/sys/class/thermal/thermal_zone4/trip_point_5_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_3_type
passive
/sys/class/thermal/thermal_zone4/trip_point_4_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_2_type
passive
/sys/class/thermal/thermal_zone4/power/runtime_active_time
0
/sys/class/thermal/thermal_zone4/power/runtime_active_kids
0
/sys/class/thermal/thermal_zone4/power/runtime_usage
0
/sys/class/thermal/thermal_zone4/power/runtime_status
unsupported
/sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms
cat: /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms:
Input/output error
/sys/class/thermal/thermal_zone4/power/async
disabled
/sys/class/thermal/thermal_zone4/power/runtime_suspended_time
0
/sys/class/thermal/thermal_zone4/power/runtime_enabled
disabled
/sys/class/thermal/thermal_zone4/power/control
auto
/sys/class/thermal/thermal_zone4/available_policies
power_allocator user_space bang_bang fair_share step_wise
/sys/class/thermal/thermal_zone4/policy
step_wise
/sys/class/thermal/thermal_zone4/trip_point_3_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_1_type
passive
/sys/class/thermal/thermal_zone4/k_d
cat: /sys/class/thermal/thermal_zone4/k_d: Input/output error
/sys/class/thermal/thermal_zone4/sustainable_power
cat: /sys/class/thermal/thermal_zone4/sustainable_power: Input/output error
/sys/class/thermal/thermal_zone4/type
iwlwifi
/sys/class/thermal/thermal_zone4/trip_point_7_type
passive
/sys/class/thermal/thermal_zone4/offset
cat: /sys/class/thermal/thermal_zone4/offset: Input/output error
/sys/class/thermal/thermal_zone4/slope
cat: /sys/class/thermal/thermal_zone4/slope: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_2_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_0_type
passive
/sys/class/thermal/thermal_zone4/trip_point_6_type
passive
/sys/class/thermal/thermal_zone4/emul_temp
cat: /sys/class/thermal/thermal_zone4/emul_temp: Permission denied
/sys/class/thermal/thermal_zone4/k_po
cat: /sys/class/thermal/thermal_zone4/k_po: Input/output error
/sys/class/thermal/thermal_zone4/integral_cutoff
cat: /sys/class/thermal/thermal_zone4/integral_cutoff: Input/output error
/sys/class/thermal/thermal_zone4/k_i
cat: /sys/class/thermal/thermal_zone4/k_i: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_1_temp
-32768000
/sys/class/thermal/thermal_zone4/k_pu
cat: /sys/class/thermal/thermal_zone4/k_pu: Input/output error
/sys/class/thermal/thermal_zone4/temp
46000
/sys/class/thermal/thermal_zone4/trip_point_7_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_5_type
passive
/sys/class/thermal/thermal_zone4/trip_point_0_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_6_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_4_type
passive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803881/+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 1950979] Re: [RTL8821CE] Bluetooth devices seem to pair well but the connection isn't working
** Summary changed: - Cannot connect Bluetooth devices + [RTL8821CE] Bluetooth devices seem to pair well but the connection isn't working ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Package changed: linux (Ubuntu) => rtl8821ce (Ubuntu) -- 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/1950979 Title: [RTL8821CE] Bluetooth devices seem to pair well but the connection isn't working Status in rtl8821ce package in Ubuntu: New Bug description: Bluetooth devices seem to pair well but the connection isn't working. Trying to connect from console output: Attempting to connect to --- Failed to connect: org.bluez.Error.Failed Ubuntu 21.10 bluez 5.60-0ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 14:22:35 2021 InstallationDate: Installed on 2020-09-15 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81LK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=4caf9acd-f72f-4105-b822-542fc17f2c3a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to impish on 2021-09-28 (47 days ago) dmi.bios.date: 11/24/2020 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad L340-15IRH Gaming dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrBGCN33WW:bd11/24/2020:br1.33:efr1.33:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming:skuLENOVO_MT_81LK_BU_idea_FM_IdeaPadL340-15IRHGaming: dmi.product.family: IdeaPad L340-15IRH Gaming dmi.product.name: 81LK dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming dmi.product.version: IdeaPad L340-15IRH Gaming dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 28:39:26:88:F8:0C ACL MTU: 1021:8 SCO MTU: 255:12 UP RUNNING PSCAN ISCAN RX bytes:17530 acl:8 sco:0 events:382 errors:0 TX bytes:37498 acl:8 sco:0 commands:245 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1950979/+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 1921829] Re: RTL8821CE 802.11ac PCIe [10ec:c821] subsystem [17aa:c024] Bluetooth not working
*** This bug is a duplicate of bug 1950979 *** https://bugs.launchpad.net/bugs/1950979 Looks like this has been superseded by bug 1950979 now. ** This bug has been marked a duplicate of bug 1950979 [RTL8821CE] Bluetooth devices seem to pair well but the connection isn't working -- 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/1921829 Title: RTL8821CE 802.11ac PCIe [10ec:c821] subsystem [17aa:c024] Bluetooth not working Status in linux package in Ubuntu: Incomplete Status in rtl8821ce package in Ubuntu: New Bug description: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921829/+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 1929889] Re: [TGL][ADL] Enable CET(Control-flow Enforcement Technology)
@Dimitri John Ledkov (xnox) Yes, it needs to patch glibc for CET support as in bug https://bugs.launchpad.net/intel/+bug/1842239 Could you please share the commit ID that is still needed? These patches listed in the bug are based on v5.13. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929889 Title: [TGL][ADL] Enable CET(Control-flow Enforcement Technology) Status in intel: New Status in intel lookout-canyon series: New Status in linux-intel package in Ubuntu: Triaged Status in linux-intel source package in Focal: New Bug description: Description Enable Tiger Lake ROP CET(Control-flow Enforcement Technology) An upcoming Intel® processor family feature that counters return/jump-oriented programming (ROP) attacks Hardware: Tiger Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929889/+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 1950974] Re: Improve USB Type-C support
** Tags added: oem-priority originate-from-1942825 somerville -- 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/1950974 Title: Improve USB Type-C support Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: [Impact] Error message "ucsi_acpi USBC000:00: GET_CONEECTOR_STATUS failed (-110)" can be found on many systems. [Fix] The main issue is that the PD firmware is unreliable, so use more deterministic methods to make it reliable [Test] The error message is gone. Also tried to plug/unplug USB Type-C power cord, and the status are always reported correctly. [Where problems could occur] This is quite a huge refactor, so regression can be expected. Only target to unstable and latest OEM kernel to reduce risk we are taking. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950974/+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 1950385] Re: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel
*** This bug is a duplicate of bug 1574582 *** https://bugs.launchpad.net/bugs/1574582 ** This bug has been marked a duplicate of bug 1574582 HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-manager -- 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/1950385 Title: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel Status in linux package in Ubuntu: Confirmed Bug description: Focal Fossa 20.04.1 HP lt4120 Snapdragon X5 LTE USB modem stopped working from kernel 5.10.x. It is not seen by Network Manager. Everything worked with 5.8.x kernel. I can't use newer kernel if I want work over HP lt4120 Snapdragon X5 LTE modem. I can't test kernel 5.14 & 5.15 in 20.04 due to libc version not compatible with updated libc from Ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mp 2798 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-07 (554 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 03f0:9d1d HP, Inc HP lt4120 Snapdragon X5 LTE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 820 G3 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 ro quiet splash resume=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 resume_offset=698368 vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.52 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.52 dmi.board.name: 807C dmi.board.vendor: HP dmi.board.version: KBC Version 85.79 dmi.chassis.asset.tag: 5CG60906BD dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.121 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook820G3:pvr:skuL4Q17AV:rvnHP:rn807C:rvrKBCVersion85.79:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 820 G3 dmi.product.sku: L4Q17AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950385/+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 1951034] [NEW] XPS 9310: wifi adapter not working when using linux-image-5.13.0-1019-oem (was working in linux-image-5.13.0-1017-oem)
Public bug reported: I have been using linux-oem-20.04c with my XPS 9310 with no problems, but the recent update to 5.13.0-1019-oem caused my wifi to become inoperative (ath11k_pci, 72:00.0 Network controller: Qualcomm Device 1101 (rev 01)). Choosing 5.13.0-1017-oem from the grub menu is my current work around as the wifi is still working there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-1019-oem 5.13.0-1019.23 ProcVersionSignature: Ubuntu 5.13.0-1017.21-oem 5.13.14 Uname: Linux 5.13.0-1017-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Nov 16 08:10:20 2021 InstallationDate: Installed on 2021-09-13 (63 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-oem-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1951034 Title: XPS 9310: wifi adapter not working when using linux- image-5.13.0-1019-oem (was working in linux-image-5.13.0-1017-oem) Status in linux-signed-oem-5.13 package in Ubuntu: New Bug description: I have been using linux-oem-20.04c with my XPS 9310 with no problems, but the recent update to 5.13.0-1019-oem caused my wifi to become inoperative (ath11k_pci, 72:00.0 Network controller: Qualcomm Device 1101 (rev 01)). Choosing 5.13.0-1017-oem from the grub menu is my current work around as the wifi is still working there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-1019-oem 5.13.0-1019.23 ProcVersionSignature: Ubuntu 5.13.0-1017.21-oem 5.13.14 Uname: Linux 5.13.0-1017-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Nov 16 08:10:20 2021 InstallationDate: Installed on 2021-09-13 (63 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-oem-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.13/+bug/1951034/+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 1949882] Re: linux-aws: Fix backport of RDMA/efa: Expose maximum TX doorbell batch
This bug is awaiting verification that the linux-aws/5.4.0-1060.63 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1949882 Title: linux-aws: Fix backport of RDMA/efa: Expose maximum TX doorbell batch Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-aws source package in Focal: Fix Committed Bug description: SRU Justification [Impact] Communications between the RDMA device and the driver are not complete. The shared structure definition of struct efa_admin_feature_queue_attr_desc is incorrect. [Test Plan] Amazon tested [Where things could go wrong] This patch could further compromise driver/device communications. [Other Info] SF: #00322369 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949882/+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 1945565] Re: [SRU] Revert amdgpu/renoir firmware
I tested 2 laptops with Ryzen 5 5500U (HP Pavilion & ASUS Zenbook). Both of them can't resume from s2idle with linux-firmware v1.187.20. With HP Pavilion I also tried v1.187.15 and v1.187.19. In all cases when you press button to resume laptop from s2idle, power button changes state from a "a slow blink" to constant lighting. But screen doesn't turn on, keyboard doesn't react, SSH doesn't work etc. The only way is to force shut down. On the other hand linux-firmware v1.187.16 & v1.187.17 work fine (I didn't test typeC dongles). Dear maintainers, could you please reintroduce "renoir firmware from 21.20" for Focal? -- 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/1945565 Title: [SRU] Revert amdgpu/renoir firmware Status in OEM Priority Project: Fix Committed Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-firmware source package in Focal: Fix Released Bug description: [Impact] The USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Revert below change, this issue is gone. commit a543b9c1bfd12e60d962acd48108234481a8581f Author: Alex Deucher Date: Thu Jul 1 12:23:11 2021 +0800 amdgpu: update renoir firmware from 21.20 BugLink: https://bugs.launchpad.net/bugs/1934014 From internal git commit: 8b05e03570818d047d7ea0a7388c89c4192fd20b Signed-off-by: Alex Deucher Signed-off-by: Josh Boyer (backported from commit 56ef642160203f8be7e1334feca4a76852c74bc0) [khfeng: Squashed multiple updates into one commit] Signed-off-by: Kai-Heng Feng Signed-off-by: Timo Aaltonen [Test] Verify S3 on renoir's platforms. [Where problems could occur] Renoir based systems can't resume from s2idle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945565/+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 1951011] [NEW] linux-aws: Make a signed kernel
Public bug reported: SRU Justification [Impact] Ubuntu AWS kernels on secure boot instances will not load. [Fix] Generate signed kernels and packages [Test Plan] Boot in a secure boot (UEFI) environment. [Where things could go wrong] This is a new packaging feature. [Other Info] ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu Focal) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Package changed: linux (Ubuntu) => linux-aws (Ubuntu) ** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-aws (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1951011 Title: linux-aws: Make a signed kernel Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Focal: In Progress Bug description: SRU Justification [Impact] Ubuntu AWS kernels on secure boot instances will not load. [Fix] Generate signed kernels and packages [Test Plan] Boot in a secure boot (UEFI) environment. [Where things could go wrong] This is a new packaging feature. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1951011/+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 1950584] Re: cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
** Description changed:
+ [Impact]
+
+
"Commit a365ab6b9dfb ("cpufreq: intel_pstate: Implement the
- ->adjust_perf() callback") caused intel_pstate to use nonzero HWP
- desired values in certain usage scenarios, but it did not prevent
- them from being leaked into the confugirations in which HWP desired
- is expected to be 0"
+ ->adjust_perf() callback") caused intel_pstate to use nonzero HWP
+ desired values in certain usage scenarios, but it did not prevent
+ them from being leaked into the confugirations in which HWP desired
+ is expected to be 0"
I believe I'm seeing this issue on my laptop during suspend/resume. The
upstream fix is:
+ [Fix]
commit dbea75fe18f60e364de6d994fc938a24ba249d81
Author: Rafael J. Wysocki
Date: Wed Nov 3 19:43:47 2021 +0100
- cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
- ---
+ cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
+ ---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC1: cking 2316 F pulseaudio
- /dev/snd/pcmC1D0c: cking 2316 F...m pulseaudio
- /dev/snd/controlC0: cking 2316 F pulseaudio
- /dev/snd/pcmC0D0p: cking 2316 F...m pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: cking 2316 F pulseaudio
+ /dev/snd/pcmC1D0c: cking 2316 F...m pulseaudio
+ /dev/snd/controlC0: cking 2316 F pulseaudio
+ /dev/snd/pcmC0D0p: cking 2316 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-06-07 (156 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210607)
MachineType: LENOVO 20L5CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
RelatedPackageVersions:
- linux-restricted-modules-5.13.0-20-generic N/A
- linux-backports-modules-5.13.0-20-generic N/A
- linux-firmware 1.202
+ linux-restricted-modules-5.13.0-20-generic N/A
+ linux-backports-modules-5.13.0-20-generic N/A
+ linux-firmware 1.202
Tags: jammy
Uname: Linux 5.13.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
vboxusers
_MarkForUpload: True
dmi.bios.date: 01/11/2020
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET55W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.20
dmi.modalias:
dmi:bvnLENOVO:bvrN24ET55W(1.30):bd01/11/2020:br1.30:efr1.20:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
--
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/1950584
Title:
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and
offline
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Hirsute:
New
Status in linux source package in Impish:
New
Bug description:
[Impact]
"Commit a365ab6b9dfb ("cpufreq: intel_pstate: Implement the
->adjust_perf() callback") caused intel_pstate to use nonzero HWP
desired values in certain usage scenarios, but it did not prevent
them from being leaked into the confugirations in which HWP desired
is expected to be 0"
I believe I'm seeing this issue on my laptop during suspend/resume.
The upstream fix is:
[Fix]
commit dbea75fe18f60e364de6d994fc938a24ba249d81
Author: Rafael J. Wysocki
Date: Wed Nov 3 19:43:47 2021 +0100
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: cking 2316 F pulseaudio
/dev/snd/pcmC1D0c: cking 2316 F...m pulseaudio
/dev/snd/controlC0: cking 2316 F pulseaudio
/dev/snd/pcmC0D0p: cking 2316 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
[Kernel-packages] [Bug 1945632] Re: Re-enable DEBUG_INFO_BTF where it was disabled
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945632 Title: Re-enable DEBUG_INFO_BTF where it was disabled Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: Fix Released Status in linux-hwe-5.13 source package in Focal: Fix Released Bug description: [Impact] * pahole used to segfault on 32-bit platforms, which has now been fixed * pahole used to be too old in focal, which is now being SRUed * renable DEBUG_INFO_BTF in all the kernels/arches that had it disabled, as otherwise one cannot compile/use advanced BTF features on newer kernels. [Test Plan] * Check the built kernel's config that it has CONFIG_DEBUG_INFO_BTF=y * Check build log that it contains ``` BTF .btf.vmlinux.bin.o ``` [Where problems could occur] * In the future, kernel may require even newer version of pahole from dwarves, making the builds fail to build again, as building BTF debug information will now be required. Until either BTF is disabled again or pahole is upgraded again. [Other Info] * Latest pahole is available from focal-proposed, hirsute-proposed, impish release, builders-extra PPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945632/+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 1933771] Re: Bluetooth headset random disconnects AX200
** Description changed: + [Impact] + Using several different bluetooth headsets I find that the Bluetooth functionality of the built-in AX200 module of my motherboard keeps randomly disconnecting. I found that this has been fixed in recent Linux firmware updates, but I am not sure that fix has landed yet in Ubuntu Hirsute. Herewith I am posting the link to exactly the issue I am having: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155 And the Linux Firmware commit that resolves this: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180 A related Fedora bug: https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274 It's difficult to relate the upstream kernel version firmware version in which this was fixed (linux-firmware-20210511) to the version of the linux-firmware Ubuntu package (for me). Perhaps someone can comment on whether this has been merged in. I am still experiencing disconnects with 1.197.1 at least. -- Description: Ubuntu 21.04 Release: 21.04 linux-firmware: - Installed: 1.197.1 - Candidate: 1.197.1 + Installed: 1.197.1 + Candidate: 1.197.1 I expected: - Bluetooth headset to remain connected + Bluetooth headset to remain connected What happened: - Bluetooth headset connects, then randomly disconnects and reconnects while playing media + Bluetooth headset connects, then randomly disconnects and reconnects while playing media + + [Test Case] + + See above. + + [Fix] + + Update AX20x firmware blobs. + + [Where Problems Could Occur] + + New firmware blobs so previously working adapter might now fail. ** Changed in: linux-firmware (Ubuntu Hirsute) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-firmware (Ubuntu Hirsute) Status: Confirmed => In Progress -- 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/1933771 Title: Bluetooth headset random disconnects AX200 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Hirsute: In Progress Bug description: [Impact] Using several different bluetooth headsets I find that the Bluetooth functionality of the built-in AX200 module of my motherboard keeps randomly disconnecting. I found that this has been fixed in recent Linux firmware updates, but I am not sure that fix has landed yet in Ubuntu Hirsute. Herewith I am posting the link to exactly the issue I am having: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155 And the Linux Firmware commit that resolves this: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180 A related Fedora bug: https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274 It's difficult to relate the upstream kernel version firmware version in which this was fixed (linux-firmware-20210511) to the version of the linux-firmware Ubuntu package (for me). Perhaps someone can comment on whether this has been merged in. I am still experiencing disconnects with 1.197.1 at least. -- Description: Ubuntu 21.04 Release: 21.04 linux-firmware: Installed: 1.197.1 Candidate: 1.197.1 I expected: Bluetooth headset to remain connected What happened: Bluetooth headset connects, then randomly disconnects and reconnects while playing media [Test Case] See above. [Fix] Update AX20x firmware blobs. [Where Problems Could Occur] New firmware blobs so previously working adapter might now fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1933771] Re: Bluetooth headset random disconnects AX200
** Also affects: linux-firmware (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Invalid -- 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/1933771 Title: Bluetooth headset random disconnects AX200 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Hirsute: Confirmed Bug description: Using several different bluetooth headsets I find that the Bluetooth functionality of the built-in AX200 module of my motherboard keeps randomly disconnecting. I found that this has been fixed in recent Linux firmware updates, but I am not sure that fix has landed yet in Ubuntu Hirsute. Herewith I am posting the link to exactly the issue I am having: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155 And the Linux Firmware commit that resolves this: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180 A related Fedora bug: https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274 It's difficult to relate the upstream kernel version firmware version in which this was fixed (linux-firmware-20210511) to the version of the linux-firmware Ubuntu package (for me). Perhaps someone can comment on whether this has been merged in. I am still experiencing disconnects with 1.197.1 at least. -- Description: Ubuntu 21.04 Release: 21.04 linux-firmware: Installed: 1.197.1 Candidate: 1.197.1 I expected: Bluetooth headset to remain connected What happened: Bluetooth headset connects, then randomly disconnects and reconnects while playing media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1881757] Re: webcam is detected but not working with kernel 5.4.0.33
i have same problem too on my eOS with kernel 5.11.0-40-generic. Maybe using external USB camera can be work well -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1881757 Title: webcam is detected but not working with kernel 5.4.0.33 Status in linux-signed package in Ubuntu: Fix Released Bug description: webcam is detected not working under kernel 5.4.0.33 and 5.4.0.31 . The webcam is functional with kernels 5.0 and 5.6.15 . -usb:1 description: Video product: USB 2.0 Web Camera vendor: Alcor Micro, Corp. physical id: 2 bus info: usb@1:1.2 version: 0.08 capabilities: usb-2.00 configuration: driver=uvcvideo maxpower=200mA speed=480Mbit/s susb; lsb_release -a; uname -a Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1d0b:0021 HAN HUA CABLE & WIRE TECHNOLOGY (J.X.) CO., LTD. Bus 001 Device 003: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux afsal-Excelance 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux more info : https://answers.launchpad.net/ubuntu/+question/691070 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1881757/+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 1950816] Re: Bionic update: upstream stable patchset 2021-11-12
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950816 Title: Bionic update: upstream stable patchset 2021-11-12 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-11-12 Ported from the following upstream stable releases: v4.14.250, v4.19.210 v4.14.251, v4.19.211 v4.19.212 v4.14.252, v4.19.213 from git://git.kernel.org/ net: mdio: introduce a shutdown method to mdio device drivers xen-netback: correct success/error reporting for the SKB-with-fraglist case sparc64: fix pci_iounmap() when CONFIG_PCI is not set ext2: fix sleeping in atomic bugs on error scsi: sd: Free scsi_disk device via put_device() usb: testusb: Fix for showing the connection speed usb: dwc2: check return value after calling platform_get_resource() scsi: ses: Retry failed Send/Receive Diagnostic commands libata: Add ATA_HORKAGE_NO_NCQ_ON_ATI for Samsung 860 and 870 SSD. lib/timerqueue: Rely on rbtree semantics for next timer selftests: be sure to make khdr before other targets UBUNTU: upstream stable to v4.14.250, v4.19.210 Partially revert "usb: Kconfig: using select for USB_COMMON dependency" USB: cdc-acm: fix racy tty buffer accesses USB: cdc-acm: fix break reporting ovl: fix missing negative dentry check in ovl_rename() nfsd4: Handle the NFSv4 READDIR 'dircount' hint being zero xen/balloon: fix cancelled balloon action ARM: dts: omap3430-sdp: Fix NAND device node ARM: dts: qcom: apq8064: use compatible which contains chipid bpf: add also cbpf long jump test cases with heavy expansion bpf, mips: Validate conditional branch offsets xtensa: call irqchip_init only when CONFIG_USE_OF is selected bpf: Fix integer overflow in prealloc_elems_and_freelist() phy: mdio: fix memory leak net_sched: fix NULL deref in fifo_set_limit() powerpc/fsl/dts: Fix phy-connection-type for fm1mac3 ptp_pch: Load module automatically if ID matches ARM: imx6: disable the GIC CPU interface before calling stby-poweroff sequence net: bridge: use nla_total_size_64bit() in br_get_linkxstats_size() netlink: annotate data races around nlk->bound drm/nouveau/debugfs: fix file release memory leak rtnetlink: fix if_nlmsg_stats_size() under estimation i40e: fix endless loop under rtnl i2c: acpi: fix resource leak in reconfiguration device addition net: phy: bcm7xxx: Fixed indirect MMD operations HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS netfilter: ip6_tables: zero-initialize fragment offset mac80211: Drop frames from invalid MAC address in ad-hoc mode m68k: Handle arrivals of multiple signals correctly net: sun: SUNVNET_COMMON should depend on INET scsi: ses: Fix unsigned comparison with less than zero scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported" perf/x86: Reset destroy callback on event init failure sched: Always inline is_percpu_thread() bpf, arm: Fix register clobbering in div/mod implementation i40e: Fix freeing of uninitialized misc IRQ vector UBUNTU: upstream stable to v4.14.251, v4.19.211 mac80211: check return value of rhashtable_init UBUNTU: upstream stable to v4.19.212 stable: clamp SUBLEVEL in 4.14 ALSA: seq: Fix a potential UAF by wrong private_free call order s390: fix strrchr() implementation btrfs: deal with errors when replaying dir entry during log replay btrfs: deal with errors when adding inode reference during log replay btrfs: check for error when looking up inode during dir entry replay xhci: Fix command ring pointer corruption while aborting a command xhci: Enable trust tx length quirk for Fresco FL11 USB controller cb710: avoid NULL pointer subtraction efi/cper: use stack buffer for error record decoding efi: Change down_interruptible() in virt_efi_reset_system() to down_trylock() usb: musb: dsps: Fix the probe error path Input: xpad - add support for another USB ID of Nacon GC-100 USB: serial: qcserial: add EM9191 QDL support USB: serial: option: add Quectel EC200S-CN module support USB: serial: option: add Telit LE910Cx composition 0x1204 USB: serial: option: add prod.
[Kernel-packages] [Bug 1950086] Re: Ubuntu 20.04 freeze
Moments before the computer stops responding. btop++ ** Attachment added: "IMG_2024_230802.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950086/+attachment/5541022/+files/IMG_2024_230802.jpg -- 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/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11
[Kernel-packages] [Bug 1950086] Re: Ubuntu 20.04 freeze
Moments before the computer stops responding. iostat -mxz 2 ** Attachment added: "IMG_2025_135735.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950086/+attachment/5541021/+files/IMG_2025_135735.jpg -- 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/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gke/5.4.0.1056.66)
All autopkgtests for the newly accepted linux-meta-gke (5.4.0.1056.66) for focal have finished running. The following regressions have been reported in tests triggered by the package: dpdk/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gke [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1929889] Re: [TGL][ADL] Enable CET(Control-flow Enforcement Technology)
@ Chao Qin (chaoqin) @anthonywong Do we also need to patch glibc to turn on CET support? Most of Ubuntu binaries have CET enabled, but I thought there was still a patch needed to turn the CET support on due to changes in the CET patches done as per kernel upstream feedback. Or is this patch series compatible with Ubuntu userspace glibc and hence CET will work with this kernel and existing ubuntu binaries? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929889 Title: [TGL][ADL] Enable CET(Control-flow Enforcement Technology) Status in intel: New Status in intel lookout-canyon series: New Status in linux-intel package in Ubuntu: Triaged Status in linux-intel source package in Focal: New Bug description: Description Enable Tiger Lake ROP CET(Control-flow Enforcement Technology) An upcoming Intel® processor family feature that counters return/jump-oriented programming (ROP) attacks Hardware: Tiger Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929889/+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 1899805] Re: UC20 kernel missing /firmware/regulatory.db
$ less pc-kernel_5.4.0-90.101.1_amd64.snap | grep regulatory -rw-r--r-- root/root 4160 2021-08-29 20:49 /firmware/regulatory.db -rw-r--r-- root/root 1182 2021-08-29 20:49 /firmware/regulatory.db.p7s ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899805 Title: UC20 kernel missing /firmware/regulatory.db Status in linux package in Ubuntu: Fix Released Bug description: UC20 kernel missing /firmware/regulatory.db and /firmware/regulatory.db.p7s Whilst present in the UC18 kernel snap. At runtime, this causes failure to load regulatory database, and perform wifi scan. [ 27.510199] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899805/+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 1947174] Re: Add final-checks to check certificates
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947174 Title: Add final-checks to check certificates Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: [Impact] * As part of landing builtin revocation certificates work https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029 it has been identified that many kernels do not correct enforce newly enfoced keys in the derivative flavours. I.e. due to annotations not importing parent annotations, due to not having do_enforce_all, or using older formats of annotations files. * As part fips validation work final-checks got added to check and assert that correct things are turned on. * It has been agreed that having a final-check for builtin system trusted & revocation certificates would be a good thing. If packaging declares that certain certificates should be built-in trusted or revoked, the kernel must be configured pointing at the packaging generated .pem bundle in the config. [Test Plan] * Kernel should build * If trusted or revocation are configured in packaging but the config option is misconfigured (i.e. typo or not set), the kernel build and cranky close should fail [Where problems could occur] * This is a packaging change only, thus may result in valid kernels ftbfs but should be easy to rectify. [Other Info] * Also see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029 and kernels that derived from a primary kernel that had that fixed, and the subsequently failed boot testing due to not enabling those options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947174/+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 1912811] Re: Update dwarves-dfsg in focal to version 1.21 from impish
This bug was fixed in the package dwarves-dfsg - 1.21-0ubuntu1~18.04 --- dwarves-dfsg (1.21-0ubuntu1~18.04) bionic; urgency=medium * Backport new dwarves-dfsg to stable series without upgrading libbpf system-wide (LP: #1912811): + Update lib/bpf to libbpf_0.4.0-1ubuntu1. + Disable lto, since it is disabled in libbpf. + Build with embedded libbpf. + Drop libbpf-dev build dependency. + Lower debhelper-compat to 11. + Cherrypick patch from 1.22 that fixes FTBFS with old elfutils dwarves-dfsg (1.21-0ubuntu1) impish; urgency=medium * New upstream release. Remaining changes: - pahole: cherry-pick removal of the ftrace filter and its related functions to prevent build errors with linux 5.13. - build with libbpf 0.4, as will be required in the next release. dwarves-dfsg (1.20-1ubuntu1) impish; urgency=medium * pahole: remove the ftrace filter and its related functions to prevent build errors with linux 5.13 (LP: #1928244) dwarves-dfsg (1.20-1) unstable; urgency=medium * New upstream release. Changes since 1.19: BTF encoder: - Improve ELF error reporting using elf_errmsg(elf_errno()). - Improve objcopy error handling. - Fix handling of 'restrict' qualifier, that was being treated as a 'const'. - Support SHN_XINDEX in st_shndx symbol indexes, to handle ELF objects with more than 65534 sections, for instance, which happens with kernels built with 'KCFLAGS="-ffunction-sections -fdata-sections", Other cases may include when using FG-ASLR, LTO. - Cope with functions without a name, as seen sometimes when building kernel images with some versions of clang, when a SEGFAULT was taking place. - Fix BTF variable generation for kernel modules, not skipping variables at offset zero. - Fix address size to match what is in the ELF file being processed, to fix using a 64-bit pahole binary to generate BTF for a 32-bit vmlinux image. - Use kernel module ftrace addresses when finding which functions to encode, which increases the number of functions encoded. DWARF loader: - Support DW_AT_data_bit_offset - DW_FORM_implicit_const in attr_numeric() and attr_offset() - Support DW_TAG_GNU_call_site, its the standardized rename of the previously supported DW_TAG_GNU_call_site. build: - Fix compilation on 32-bit architectures. * Refresh patches. * Remove ctfdwdiff and README.cross so to reuse upstream tarball as-is. * Update Standards-Version to 4.5.1 * Update debhelper compatibility to 13: - install missing binaries: btfdiff and fullcircle * Add upstream metadata file * gbp: set upstream tarball compression to xz * Add lintian override for orig-tarball-missing-upstream-signature, see #882694. dwarves-dfsg (1.19-1) unstable; urgency=high * New upstream release. Closes: #978691. Changes since 1.18: - Support split BTF, where a main BTF file, vmlinux, can be used to find types and then a kernel module, for instance, can have just what is unique to it - Update libbpf to get the split BTF support and use some of its functions to load BTF and speed up DWARF loading and BTF encoding - Support cross-compiled ELF binaries with different endianness - Support showing typedefs for anonymous types, like structs, unions and enums - Align enumerators - Workaround bugs in the generation of DWARF records for functions in some gcc versions that were causing breakage in the encoding of BTF - Ignore zero-sized ELF symbols instead of erroring out - Handle union forward declaration properly in the BTF loader - Introduce --numeric_version for use in scripts and Makefiles - Try sole pfunct argument as a function name, just like pahole with type names - Speed up pfunct using some of the load techniques used in pahole - Discard CUs after BTF encoding as they're not used anymore, greatly reducing memory usage and speeding up vmlinux BTF encoding - Revamp how per-CPU variables are encoded in BTF - Include BTF info for static functions - Use BTF's string APIs for strings management, greatly improving performance over the tsearch() - Increase size of DWARF lookup hash table, shaving off about 1 second out of about 20 seconds total for Linux BTF dedup - Stop BTF encoding when errors are found in some DWARF CU - Implement --packed, to show just packed structures, for instance, here are the top 5 packed data structures in the Linux kernel - Fix bug in distros such as OpenSUSE:15.2 where DW_AT_alignment isn't defined * Refresh patches. dwarves-dfsg (1.18-1) unstable; urgency=medium [ Domenico Andreoli ] * New upstream release (changes since 1.17): - Use type information to pretty print raw data from stdin, all documented in the man
[Kernel-packages] [Bug 1950979] [NEW] Cannot connect Bluetooth devices
Public bug reported: Bluetooth devices seem to pair well but the connection isn't working. Trying to connect from console output: Attempting to connect to --- Failed to connect: org.bluez.Error.Failed Ubuntu 21.10 bluez 5.60-0ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 14:22:35 2021 InstallationDate: Installed on 2020-09-15 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81LK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=4caf9acd-f72f-4105-b822-542fc17f2c3a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to impish on 2021-09-28 (47 days ago) dmi.bios.date: 11/24/2020 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad L340-15IRH Gaming dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrBGCN33WW:bd11/24/2020:br1.33:efr1.33:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming:skuLENOVO_MT_81LK_BU_idea_FM_IdeaPadL340-15IRHGaming: dmi.product.family: IdeaPad L340-15IRH Gaming dmi.product.name: 81LK dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming dmi.product.version: IdeaPad L340-15IRH Gaming dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 28:39:26:88:F8:0C ACL MTU: 1021:8 SCO MTU: 255:12 UP RUNNING PSCAN ISCAN RX bytes:17530 acl:8 sco:0 events:382 errors:0 TX bytes:37498 acl:8 sco:0 commands:245 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1950979 Title: Cannot connect Bluetooth devices Status in bluez package in Ubuntu: New Bug description: Bluetooth devices seem to pair well but the connection isn't working. Trying to connect from console output: Attempting to connect to --- Failed to connect: org.bluez.Error.Failed Ubuntu 21.10 bluez 5.60-0ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 14:22:35 2021 InstallationDate: Installed on 2020-09-15 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81LK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=4caf9acd-f72f-4105-b822-542fc17f2c3a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to impish on 2021-09-28 (47 days ago) dmi.bios.date: 11/24/2020 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad L340-15IRH Gaming dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrBGCN33WW:bd11/24/2020:br1.33:efr1.33:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming:skuLENOVO_MT_81LK_BU_idea_FM_IdeaPadL340-15IRHGaming: dmi.product.family: IdeaPad L340-15IRH Gaming dmi.product.name: 81LK dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming dmi.product.version: IdeaPad L340-15IRH Gaming dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 28:39:26:88:F8:0C ACL MTU: 1021:8 SCO MTU: 255:12 UP RUNNING PSCAN ISCAN RX bytes:17530 acl:8 sco:0 events:382 errors:0 TX bytes:37498 acl:8 sco:0 commands:245 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1950979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1946796] Re: ch341 communication problem from kernel.org
I'm not seeing this problem anymore after recent software updates. -- 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/1946796 Title: ch341 communication problem from kernel.org Status in linux package in Ubuntu: Confirmed Bug description: Issue with esp8266 esptool communications. This is a bug known at kernel.org "Bug 214131 - ch341 communication problem" https://bugzilla.kernel.org/show_bug.cgi?id=214131 It has a resolution, however it appears this has not been pushed out to Ubuntu yet so it is affecting my system. The issue causes esptool not to be able to communicate with esp8266/esp32 USB chips. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-88-generic 5.4.0-88.99 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: browna 3672 F pulseaudio /dev/snd/controlC0: browna 3672 F pulseaudio CasperMD5CheckResult: skip Date: Tue Oct 12 22:33:36 2021 HibernationDevice: # RESUME=UUID=5ec6ef50-65f9-40c2-87ee-3a7a9cd01da7 InstallationDate: Installed on 2015-05-07 (2350 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Acer Aspire VN7-571 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=14353e0d-b4a9-4bfa-b347-cc7a99bdc8bd ro quiet splash i8042.nopnp vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: Upgraded to focal on 2020-11-16 (330 days ago) dmi.bios.date: 09/12/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-571 dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd09/12/2014:svnAcer:pnAspireVN7-571:pvrV1.08:rvnAcer:rnAspireVN7-571:rvrV1.08:cvnChassisManufacturer:ct10:cvrV1.08: dmi.product.family: Sharkbay System dmi.product.name: Aspire VN7-571 dmi.product.sku: Aspire VN7-571_091B_1.08 dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946796/+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 1934261] Re: use debian source format 3.0 (native)
** Changed in: linux-firmware (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Invalid -- 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/1934261 Title: use debian source format 3.0 (native) Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Focal: Invalid Status in linux-firmware source package in Groovy: Won't Fix Status in linux-firmware source package in Hirsute: Invalid Status in linux-firmware source package in Impish: Invalid Bug description: In Hirsute/Impish, debian source package Standards-Version moved to 4.5.0, and debian/source/format is created with content "3.0 (native)". It should be also helpful to backport this change to other maintaining series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934261/+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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Maybe is late as it seems solved but here you have this info. I installed with an USB Lubuntu 20.04LTS on a Thinkpad E15 gen3 AMD 5500U Radeon graphics. Wifi not worked (MEDIATEK device 796 unsupported) so I upgrade to 5.13.0-1010-oem and Wifi OK. With Lubuntu 21.10 USB iso boot I have the elantech stack corruption (no matter if disable pad) In summary kernel 5.13.0-1010-oem was ok for me (no elantech stack corruption) By the way, will the Lubuntu 21.10 ISO be updated when this bug is corrected? Thank you Andrea -- 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/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Status in linux source package in Jammy: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro 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.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1929256] Re: Intel Bluetooth 8265/8275 not working properly
** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- 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/1929256 Title: Intel Bluetooth 8265/8275 not working properly Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Incomplete Bug description: Turning off the bluetooth from settings doesn't let me turn on the bluetooth again and I have to reboot my pc to make it to work again. I am running Ubuntu 21.04 and this bug is persistent since 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929256/+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 1939528] Re: Need support of Qualcomm WCN6856
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu Impish) Status: New => Confirmed -- 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/1939528 Title: Need support of Qualcomm WCN6856 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux-firmware source package in Hirsute: Confirmed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Incomplete Status in linux-firmware source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Qualcomm WCN685x is not supported yet. [Fix] Qualcomm WCN685x support are mostly available in linux-next and mainline with one patch currently in kvalo/ath tree, and 3 additional in review. [Test Case] Test hardware connectivity, stability with basic checkbox tests: $ lspci -nnk | grep Network -A 3 :02:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0b8] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci [Where problems could occur] While this introduces a new hardware, it might need further polishments. [Other Info] WCN685x WiFi 6E capability is still under development and is moved to next milestone for oem projects. Firmware blobs for both WiFi and Bluetooth are also needed and will be SRUed when a formal release is made. == original bug report == Wireless Driver support: PCI\VEN_17CB_1103_E0B8105B_01 BT driver support: USB\VID_0489_E0C9_0001 Wireless Driver support: PCI\VEN_17CB_1103_01 BT driver support: USB\VID_0489_E0CC_0001 https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/ Already landed to mainline kernel v5.14-rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939528/+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 1939528] Re: Need support of Qualcomm WCN6856
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu Hirsute) Status: New => Confirmed -- 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/1939528 Title: Need support of Qualcomm WCN6856 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux-firmware source package in Hirsute: Confirmed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Incomplete Status in linux-firmware source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Qualcomm WCN685x is not supported yet. [Fix] Qualcomm WCN685x support are mostly available in linux-next and mainline with one patch currently in kvalo/ath tree, and 3 additional in review. [Test Case] Test hardware connectivity, stability with basic checkbox tests: $ lspci -nnk | grep Network -A 3 :02:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0b8] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci [Where problems could occur] While this introduces a new hardware, it might need further polishments. [Other Info] WCN685x WiFi 6E capability is still under development and is moved to next milestone for oem projects. Firmware blobs for both WiFi and Bluetooth are also needed and will be SRUed when a formal release is made. == original bug report == Wireless Driver support: PCI\VEN_17CB_1103_E0B8105B_01 BT driver support: USB\VID_0489_E0C9_0001 Wireless Driver support: PCI\VEN_17CB_1103_01 BT driver support: USB\VID_0489_E0CC_0001 https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/ Already landed to mainline kernel v5.14-rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939528/+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 1939528] Re: Need support of Qualcomm WCN6856
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1939528 Title: Need support of Qualcomm WCN6856 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux-firmware source package in Hirsute: Confirmed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Incomplete Status in linux-firmware source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Qualcomm WCN685x is not supported yet. [Fix] Qualcomm WCN685x support are mostly available in linux-next and mainline with one patch currently in kvalo/ath tree, and 3 additional in review. [Test Case] Test hardware connectivity, stability with basic checkbox tests: $ lspci -nnk | grep Network -A 3 :02:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0b8] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci [Where problems could occur] While this introduces a new hardware, it might need further polishments. [Other Info] WCN685x WiFi 6E capability is still under development and is moved to next milestone for oem projects. Firmware blobs for both WiFi and Bluetooth are also needed and will be SRUed when a formal release is made. == original bug report == Wireless Driver support: PCI\VEN_17CB_1103_E0B8105B_01 BT driver support: USB\VID_0489_E0C9_0001 Wireless Driver support: PCI\VEN_17CB_1103_01 BT driver support: USB\VID_0489_E0CC_0001 https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/ Already landed to mainline kernel v5.14-rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939528/+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 1950974] [NEW] Improve USB Type-C support
Public bug reported: [Impact] Error message "ucsi_acpi USBC000:00: GET_CONEECTOR_STATUS failed (-110)" can be found on many systems. [Fix] The main issue is that the PD firmware is unreliable, so use more deterministic methods to make it reliable [Test] The error message is gone. Also tried to plug/unplug USB Type-C power cord, and the status are always reported correctly. [Where problems could occur] This is quite a huge refactor, so regression can be expected. Only target to unstable and latest OEM kernel to reduce risk we are taking. ** Affects: linux (Ubuntu) Importance: Low Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Low Status: Confirmed ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => Low -- 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/1950974 Title: Improve USB Type-C support Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: [Impact] Error message "ucsi_acpi USBC000:00: GET_CONEECTOR_STATUS failed (-110)" can be found on many systems. [Fix] The main issue is that the PD firmware is unreliable, so use more deterministic methods to make it reliable [Test] The error message is gone. Also tried to plug/unplug USB Type-C power cord, and the status are always reported correctly. [Where problems could occur] This is quite a huge refactor, so regression can be expected. Only target to unstable and latest OEM kernel to reduce risk we are taking. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950974/+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 1950968] 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 1950968 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: impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950968 Title: v5.15 RT kernel fails to boot on some arm64 instances Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: d2021.10.26/jammy/linux-realtime/5.15.0-1002.2 failed to boot on helo- kernel.arm64 without any logs. - Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-1002-realtime Found initrd image: /boot/initrd.img-5.15.0-1002-realtime Found linux image: /boot/vmlinuz-5.13.0-21-generic Found initrd image: /boot/initrd.img-5.13.0-21-generic done . Rebooting for installed Kernel meta package Traceback (most recent call last): File "/home/maas/ckct/sut-prep", line 187, in exit(app.main(args)) File "/home/maas/ckct/sut-prep", line 74, in main if instance.provision(): File "/home/maas/ckct/lib/target.py", line 1301, in provision s.reboot(progress=reboot) File "/home/maas/ckct/lib/target.py", line 621, in reboot s.wait_for_target() File "/home/maas/ckct/lib/target.py", line 173, in wait_for_target raise WaitForTarget(message) lib.target.WaitForTarget: The specified timeout (30 minutes) was reached while waiting for the target system (10.229.83.183) to come back up. WARNING - [2021-11-15 10:42:43.270713] ssh command (return): uname -vr (0) 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 09:01:50 UTC 2021 - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950968/+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 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
Not a linux-firmware issues since the firwmare blobs will be provided by a different package. Marking linux-firmware tasks as 'invalid'. ** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Status: Confirmed => Invalid ** Changed in: linux-firmware (Ubuntu Hirsute) Status: Confirmed => Invalid ** Changed in: linux-firmware (Ubuntu Impish) Status: Confirmed => Invalid -- 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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in alsa-topology-conf package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in alsa-topology-conf source package in Focal: New Status in alsa-ucm-conf source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in linux-firmware source package in Focal: Invalid Status in alsa-topology-conf source package in Hirsute: New Status in alsa-ucm-conf source package in Hirsute: Won't Fix Status in linux source package in Hirsute: Fix Released Status in linux-firmware source package in Hirsute: Invalid Status in alsa-topology-conf source package in Impish: New Status in alsa-ucm-conf source package in Impish: Won't Fix Status in linux source package in Impish: Fix Released Status in linux-firmware source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Skylake, Kabylake, Kabylake-refresh, Amberlake and some other platforms where audio is of SPT (PCH) type, HDA (with DSP capabilities) plus DMIC configuration is supported on these with skylake driver since kernel 5.8. However, no sound card can be detected w/o the topology binary file in /lib/firmware and corresponding ucm file. [Fix] The kernel config CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC needa to be enabled for the snd_soc_skl driver to support HDA+DMIC configuration. And the topology binary file and UCM files need to be located in the correct path based on Intel's suggestion. https://gist.github.com/crojewsk/4e6382bfb0dbfaaf60513174211f29cb. [Test] On the Skylake/Kabylake platforms with either the PCI device 8086:9d70 and 8086:9d71, boot up the machine and check the existence of the sound card by either 'aplay -l' or 'pactl list' command. [Where problems could occur] Should be low risk, it only affects limited Intel Platforms with particular PCI device IDs + HDA plus DMIC configuration. == Original Bug Description == Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name:
[Kernel-packages] [Bug 1950968] [NEW] v5.15 RT kernel fails to boot on some arm64 instances
Public bug reported: d2021.10.26/jammy/linux-realtime/5.15.0-1002.2 failed to boot on helo- kernel.arm64 without any logs. - Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-1002-realtime Found initrd image: /boot/initrd.img-5.15.0-1002-realtime Found linux image: /boot/vmlinuz-5.13.0-21-generic Found initrd image: /boot/initrd.img-5.13.0-21-generic done . Rebooting for installed Kernel meta package Traceback (most recent call last): File "/home/maas/ckct/sut-prep", line 187, in exit(app.main(args)) File "/home/maas/ckct/sut-prep", line 74, in main if instance.provision(): File "/home/maas/ckct/lib/target.py", line 1301, in provision s.reboot(progress=reboot) File "/home/maas/ckct/lib/target.py", line 621, in reboot s.wait_for_target() File "/home/maas/ckct/lib/target.py", line 173, in wait_for_target raise WaitForTarget(message) lib.target.WaitForTarget: The specified timeout (30 minutes) was reached while waiting for the target system (10.229.83.183) to come back up. WARNING - [2021-11-15 10:42:43.270713] ssh command (return): uname -vr (0) 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 09:01:50 UTC 2021 - ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1950968 Title: v5.15 RT kernel fails to boot on some arm64 instances Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: d2021.10.26/jammy/linux-realtime/5.15.0-1002.2 failed to boot on helo- kernel.arm64 without any logs. - Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-1002-realtime Found initrd image: /boot/initrd.img-5.15.0-1002-realtime Found linux image: /boot/vmlinuz-5.13.0-21-generic Found initrd image: /boot/initrd.img-5.13.0-21-generic done . Rebooting for installed Kernel meta package Traceback (most recent call last): File "/home/maas/ckct/sut-prep", line 187, in exit(app.main(args)) File "/home/maas/ckct/sut-prep", line 74, in main if instance.provision(): File "/home/maas/ckct/lib/target.py", line 1301, in provision s.reboot(progress=reboot) File "/home/maas/ckct/lib/target.py", line 621, in reboot s.wait_for_target() File "/home/maas/ckct/lib/target.py", line 173, in wait_for_target raise WaitForTarget(message) lib.target.WaitForTarget: The specified timeout (30 minutes) was reached while waiting for the target system (10.229.83.183) to come back up. WARNING - [2021-11-15 10:42:43.270713] ssh command (return): uname -vr (0) 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 09:01:50 UTC 2021 - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950968/+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 1947188] Re: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted
I cannot reproduce this. Your system must be misconfigured somehow or otherwise in a bad state. I fail to see how this could be a linux- firmware package problem. ubuntu@ubuntu-focal:~$ sudo dpkg -i linux-firmware_1.187.19_all.deb (Reading database ... 78866 files and directories currently installed.) Preparing to unpack linux-firmware_1.187.19_all.deb ... Unpacking linux-firmware (1.187.19) over (1.187.17) ... Setting up linux-firmware (1.187.19) ... update-initramfs: Generating /boot/initrd.img-5.4.0-29-generic One indication that the system is not happy is that the kernel is flooding the logs with: Oct 14 17:55:38 KI0540 kernel: ath10k_pci :01:00.0: invalid ht params rate 1440 100kbps nss 2 mcs 7 -- 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/1947188 Title: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted Status in linux-firmware package in Ubuntu: New Bug description: this is encountered when I tried apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.17 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kumaradepu 2858 F pulseaudio CasperMD5CheckResult: skip Date: Thu Oct 14 22:53:56 2021 Dependencies: ErrorMessage: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (20 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5539 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5300 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=f7268264-7e38-446b-b987-ce6c36322ac6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: linux-firmware Title: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0932VT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd01/22/2021:br1.13:svnDellInc.:pnLatitude5300:pvr:sku08B7:rvnDellInc.:rn0932VT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5300 dmi.product.sku: 08B7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1947188/+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, >z_sa_hdl)) failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi (Ubuntu) Status: New => Confirmed -- 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, >z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in linux-raspi source package in Impish: Confirmed Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released 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, >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 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+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, >z_sa_hdl)) failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi (Ubuntu Impish) Status: New => Confirmed -- 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, >z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in linux-raspi source package in Impish: Confirmed Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released 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, >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 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+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, >z_sa_hdl)) failed
@enoriel - I've read carefully the info in this ticket; I'm still contemplating the Hirsute to Impish upgrade and *really* glad I didn't pull the trigger earlier!! The bad news is that it seems clear that the original Impish kernel (5.13.0-19) corrupted filesystems it ran against; thus running any (older/newer) kernel that doesn't include the bug won't "undo" the corruption. I *believe* only ZFS-encrypted filesystems were affected. https://bugs.launchpad.net/ubuntu/+source/zfs- linux/+bug/1906476/comments/64 and https://bugs.launchpad.net/ubuntu/+source/zfs- linux/+bug/1906476/comments/47 have suggestions on how to rescue your filesystem. It may be best to boot the system to be rescued by other means and import the corrupted filesystem onto it; a Hirsute ISO should do as its ZFS version is close enough to the one used by Impish (2.0.x) but I haven't tested any of this; merely collating info above. I'm still unclear as to whether a Hirsute -> Impish upgrade is safe. A clear cut statement by Canonical wouldn't go amiss given the severity of this issue (to put it mildly)... -- 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, >z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in linux-raspi source package in Impish: Confirmed Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released 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, >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]
[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, >z_sa_hdl)) failed
As many people here, I upgraded my encrypted ZFS Ubuntu system to 21.10, unaware of the issues with ZFS, I only used 5.13.0-19 for a day, and began to notice odd things, like: incapacity to suspend to RAM, freezes, some process were impossible to kill. I updated my kernel to 5.13.0-20 and then 5.13.0-21, but I still have issues with my ZFS encrypted filesystem. It seems the kernel update does not fix everything. Even now it is unable to suspend (it says some process refuse to suspend), which is really annoying for a laptop. Moreoever, automatically scheduled "updatedb" and "apt update" get stuck. Even system shutdown often takes a long time, to the point I have to force it with power button. Many times it seems to get stuck waiting for AppArmor. In addition I keep getting errors with stack traces in dmesg, I put an example in attachment. Now I am wondering what I should do to repair it ? I considered trying to downgrade my kernel to 5.11.0-37 which was my version before upgrading to 21.10, but it was automatically removed, and it does not seem very easy to put it back. I am wondering if it is worth the hassle. Besides, the ZFS version was also upgraded in the process, and it is not clear to me whether I could keep the new version with the old kernel, or not. It seems to have evolved from 0.8.4-1ubuntu11.3 to 2.0.2-1ubuntu5.1, and then 2.0.2-1ubuntu5.2, and 2.0.6-1ubuntu2 (though oddly I cannot find any trace of this last version being installed in apt logs). I am wondering if rolling back to 0.8.4 can do any good ? My whole system is based on ZFS, if I have to reinstall it all, it will take me days to put everything back. Is there a real corruption on the filesystem, which would be interpreted as such by an older ZFS version, or is it just new 2.0.x versions that are disturbed by it ? Would there be a way to fix the corruption ? Deleting some files or changing meta-data ? Any help would be greatly appreciated ! Thank you. ** Attachment added: "zfs_panic_trace_2025.log" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476/+attachment/5540947/+files/zfs_panic_trace_2025.log -- 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, >z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in linux-raspi source package in Impish: New Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released 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, >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
[Kernel-packages] [Bug 1950958] [NEW] Fixes for modetest helpers for 5.13
Public bug reported: [From] https://github.com/raspberrypi/linux/pull/4673 [Description] Hi, This is the same PR than #4672, for 5.13 [From] https://github.com/raspberrypi/linux/pull/4672 [Description] Hi, Here's a series of a few issues in the KMS commit code that were introduced by moving to generic helpers in (mainline) 5.12. I'll submit a similar PR for 5.13 at least, since it's what Canonical is using, and can submit it to any other branch if relevant. 5.10 doesn't suffer from those issues since the commits were applied, and then reverted. Maxime ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-raspi (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Impish) Importance: Undecided Status: New ** Description changed: [From] https://github.com/raspberrypi/linux/pull/4673 [Description] Hi, This is the same PR than #4672, for 5.13 + + [From] + https://github.com/raspberrypi/linux/pull/4672 + + [Description] + Hi, + + Here's a series of a few issues in the KMS commit code that were + introduced by moving to generic helpers in (mainline) 5.12. + + I'll submit a similar PR for 5.13 at least, since it's what Canonical is + using, and can submit it to any other branch if relevant. 5.10 doesn't + suffer from those issues since the commits were applied, and then + reverted. + + Maxime ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid -- 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/1950958 Title: Fixes for modetest helpers for 5.13 Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Impish: New Bug description: [From] https://github.com/raspberrypi/linux/pull/4673 [Description] Hi, This is the same PR than #4672, for 5.13 [From] https://github.com/raspberrypi/linux/pull/4672 [Description] Hi, Here's a series of a few issues in the KMS commit code that were introduced by moving to generic helpers in (mainline) 5.12. I'll submit a similar PR for 5.13 at least, since it's what Canonical is using, and can submit it to any other branch if relevant. 5.10 doesn't suffer from those issues since the commits were applied, and then reverted. Maxime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950958/+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 1950921] 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 1950921 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 -- 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/1950921 Title: Following update, grub stuck in loop. Status in linux package in Ubuntu: Incomplete Bug description: Following a restart of Ubuntu server to finish updates, the computer is stuck at the grub boot screen. Selecting ubuntu to start unly returns the computer to the grub screen. The computer is a virtual machine running on Hyper-V (windows server 16). The computer starts correctly if the network card is disconnected during the first part of the boot process. The same issue has occurred on both desktop and server VMs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.30 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Sun Nov 14 22:22:45 2021 InstallationDate: Installed on 2021-07-16 (121 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) PackageArchitecture: all ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950921/+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, >z_sa_hdl)) failed
The raspi kernel based on 5.13.0-20.20 is not yet in updates, it's still in proposed. Can you test 5.13.0-1010.12 from impish-proposed? -- 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, >z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in linux-raspi source package in Impish: New Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released 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, >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 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+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 1950921] Re: Following update, grub stuck in loop.
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 ** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950921 Title: Following update, grub stuck in loop. Status in linux package in Ubuntu: New Bug description: Following a restart of Ubuntu server to finish updates, the computer is stuck at the grub boot screen. Selecting ubuntu to start unly returns the computer to the grub screen. The computer is a virtual machine running on Hyper-V (windows server 16). The computer starts correctly if the network card is disconnected during the first part of the boot process. The same issue has occurred on both desktop and server VMs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.30 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Sun Nov 14 22:22:45 2021 InstallationDate: Installed on 2021-07-16 (121 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) PackageArchitecture: all ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950921/+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 1950921] [NEW] Following update, grub stuck in loop.
You have been subscribed to a public bug: Following a restart of Ubuntu server to finish updates, the computer is stuck at the grub boot screen. Selecting ubuntu to start unly returns the computer to the grub screen. The computer is a virtual machine running on Hyper-V (windows server 16). The computer starts correctly if the network card is disconnected during the first part of the boot process. The same issue has occurred on both desktop and server VMs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.30 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Sun Nov 14 22:22:45 2021 InstallationDate: Installed on 2021-07-16 (121 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) PackageArchitecture: all ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal uec-images -- Following update, grub stuck in loop. https://bugs.launchpad.net/bugs/1950921 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1950952] [NEW] user_notification_addfd in seccomp/seccomp_bpf of ubuntu_kernel_selftests failed on F-OEM-5.14
Public bug reported: Issue found on Focal OEM 5.14.0-1008.8 with node spitfire I think this is a new case, probably introduced by this commit: https://github.com/torvalds/linux/commit/e540ad97e73cefb41e93d0c06d0fe6a8620a77e0 Test log: # # RUN global.user_notification_addfd ... # # seccomp_bpf.c:3989:user_notification_addfd:Expected listener (18) == nextfd++ (9) # # user_notification_addfd: Test terminated by assertion # # FAIL global.user_notification_addfd # not ok 49 global.user_notification_addfd ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Tags: 5.14 amd64 focal oem sru-20211108 ubuntu-kernel-selftests ** Tags added: 5.14 amd64 focal oem sru-20211108 ubuntu-kernel-selftests ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New -- 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/1950952 Title: user_notification_addfd in seccomp/seccomp_bpf of ubuntu_kernel_selftests failed on F-OEM-5.14 Status in ubuntu-kernel-tests: New Status in linux-oem-5.14 package in Ubuntu: New Bug description: Issue found on Focal OEM 5.14.0-1008.8 with node spitfire I think this is a new case, probably introduced by this commit: https://github.com/torvalds/linux/commit/e540ad97e73cefb41e93d0c06d0fe6a8620a77e0 Test log: # # RUN global.user_notification_addfd ... # # seccomp_bpf.c:3989:user_notification_addfd:Expected listener (18) == nextfd++ (9) # # user_notification_addfd: Test terminated by assertion # # FAIL global.user_notification_addfd # not ok 49 global.user_notification_addfd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950952/+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 1948436] Re: Add RevID field to VPD info in EEPROM
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1948436 Title: Add RevID field to VPD info in EEPROM Status in linux-bluefield package in Ubuntu: Fix Committed Bug description: SRU Justification: [Impact] Currently, the VPD info stored in the EEPROM does not include a Rev ID. This field is incremented when a PN goes through minor HW changes. Sometimes, SW needs to differentiate the two versions of the card. Hence, this field should be supported in the EEPROM MFG partition. [Fix] EC (Engineering Changes) field is used to denote the HW Revision of a PN. Add it to the EEPROM MFG and provide a sysfs entry to access the same via mlx-bootctl. [Test Case] This field is typically programmed at the manufacturing step using the bfcfg tool which uses the write mechanism in the driver and then the MFG partition is locked. Reading the "rev" sysfs will show the current value. [Regression Potential] Can be considered minimum. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1948436/+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 1948434] Re: Check if secure boot is enabled with development keys
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1948434 Title: Check if secure boot is enabled with development keys Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: In Progress Bug description: SRU Justification: [Impact] Currently, there is no indication from mlx-bootctl when the user reads the lifecycle_state sysfs as to whether secure boot is enabled with development keys or production keys. In order to make this clear to the user, add a check in the driver. [Fix] Check the secure boot development mode status bit. If secure boot is enabled with the development key, then print it to the output buffer when lifecycle_state_show() is invoked. [Test Case] On a system in secure state, if it has been programmed with development keys, then reading the lifecycle_state sysfs entry in the mlx-bootctl driver should print a message that indicates the same. Similarly, a secure system which has been programmed with production keys must print the appropriate message when the lifecycle_state sysfs is read. [Regression Potential] Can be considered minimum. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1948434/+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 1950949] [NEW] Jammy update: v5.15.2 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.2 upstream stable release from git://git.kernel.org/ Linux 5.15.2 rsi: fix control-message timeout media: staging/intel-ipu3: css: Fix wrong size comparison imgu_css_fw_init staging: r8188eu: fix memleak in rtw_wx_set_enc_ext staging: rtl8192u: fix control-message timeouts staging: r8712u: fix control-message timeout comedi: vmk80xx: fix bulk and interrupt message timeouts comedi: vmk80xx: fix bulk-buffer overflow comedi: vmk80xx: fix transfer-buffer overflows comedi: ni_usb6501: fix NULL-deref in command paths comedi: dt9812: fix DMA buffers on stack isofs: Fix out of bound access for corrupted isofs image staging: rtl8712: fix use-after-free in rtl8712_dl_fw btrfs: fix lzo_decompress_bio() kmap leakage kfence: default to dynamic branch instead of static keys mode kfence: always use static branches to guard kfence_alloc() binder: don't detect sender/target during buffer cleanup binder: use cred instead of task for getsecid binder: use cred instead of task for selinux checks binder: use euid from cred instead of using task Revert "proc/wchan: use printk format instead of lookup_symbol_name()" usb-storage: Add compatibility quirk flags for iODD 2531/2541 usb: musb: Balance list entry in musb_gadget_queue usb: gadget: Mark USB_FSL_QE broken on 64-bit usb: ehci: handshake CMD_RUN instead of STS_HALT Revert "x86/kvm: fix vcpu-id indexed array sizes" KVM: x86: avoid warning with -Wbitwise-instead-of-logical ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: 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/1950949 Title: Jammy update: v5.15.2 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.2 upstream stable release from git://git.kernel.org/ Linux 5.15.2 rsi: fix control-message timeout media: staging/intel-ipu3: css: Fix wrong size comparison imgu_css_fw_init staging: r8188eu: fix memleak in rtw_wx_set_enc_ext staging: rtl8192u: fix control-message timeouts staging: r8712u: fix control-message timeout comedi: vmk80xx: fix bulk and interrupt message timeouts comedi: vmk80xx: fix bulk-buffer overflow comedi: vmk80xx: fix transfer-buffer overflows comedi: ni_usb6501: fix NULL-deref in command paths comedi: dt9812: fix DMA buffers on stack isofs: Fix out of bound access for corrupted isofs image staging: rtl8712: fix use-after-free in rtl8712_dl_fw btrfs: fix lzo_decompress_bio() kmap leakage kfence: default to dynamic branch instead of static keys mode kfence: always use static branches to guard kfence_alloc() binder: don't detect sender/target during buffer cleanup binder: use cred instead of task for getsecid binder: use cred instead of task for selinux checks binder: use euid from cred instead of using task Revert "proc/wchan: use printk format instead of lookup_symbol_name()" usb-storage: Add compatibility quirk flags for iODD 2531/2541 usb: musb: Balance list entry in musb_gadget_queue usb: gadget: Mark USB_FSL_QE broken on 64-bit usb: ehci: handshake CMD_RUN instead of STS_HALT Revert "x86/kvm: fix vcpu-id indexed array sizes" KVM: x86: avoid warning with -Wbitwise-instead-of-logical To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
