[Kernel-packages] [Bug 1952817] Re: [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir
** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu) 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/1952817 Title: [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: In Progress Bug description: [Impact] On new amdgpu renoir firmware, the USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Restore the old amdgpu fw, this issue is gone. For new fw, AMD make kernel fix be ready, after backport, the issue is not reproduced on new fw. Cherry-picked from stable kernel release to fix it. [Test] After S3 on renoir's platforms, hotplug USB, the USB3.1 devices works good. [Where problems could occur] AMD renoir platform may have issues when suspend. Jammy already got this commit via stable updates v5.15.3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952817/+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 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@Rick, could you list the using kernel version? Do you remember which kernel version you didn't observe the issue? -- 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/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 Status in thermald package in Ubuntu: In Progress Bug description: I would really like to find out why my cpu's keep reverting back to a cpu powersave mode after I get a kernel update then reboot. I cleaned my laptops vent but this seems to happen whenever a new kernel is updated and installed. https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts- significant-throttling-of- intel-i7-processor?noredirect=1#comment2345549_1366090 Description:Ubuntu 20.04.3 LTS Release:20.04 Computer Summary Computer Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Memory 16315MB (4407MB used) Machine TypeLaptop Operating SystemUbuntu 20.04.3 LTS User Name rt (rt) Date/Time Mon 30 Aug 2021 02:33:09 PM EDT Display Resolution 1920x1080 pixels OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA Intel HDMI Audio Adapter HDA-Intel - HDA Intel PCH Audio Adapter USB-Audio - USB Audio Device Input Devices Power Button Sleep Button Lid Switch Power Button AT Translated Set 2 keyboard USB Audio Device ETPS/2 Elantech Touchpad Logitech Anywhere MX Video Bus HDA Intel PCH Mic HDA Intel PCH Front Headphone HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 Printers (CUPS) OfficeJet_Pro_6978 Default SCSI Disks TSSTcorp CDDVDW SN-208DB ATA INTEL SSDMCEAC12 ATA ST1000LM014-1EJ1 Operating System Version Kernel Linux 5.4.0-81-generic (x86_64) Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31 DistributionUbuntu 20.04.3 LTS Current Session Computer Name sys76 User Name rt (rt) Languageen_US.UTF-8 () Home Directory /home/rt Misc Uptime 20 minutes Load Average0.83, 1.37, 1.62 Available entropy in /dev/random3649 bits (healthy) rt@sys76:~$ dpkg -l *freq* | grep ii rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6 Busy% Bzy_MHz IRQ PkgTmp PkgWatt GFXWatt 2.95800 334747 2.160.01 2.76800 306949 2.150.01 5.85800 512248 2.730.01 11.87 800 800847 3.410.04 8.23800 577847 2.860.05 rt@sys76:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Stepping:3 CPU MHz: 798.103 CPU max MHz: 3400. CPU min MHz: 800. BogoMIPS:4788.65 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache:1 MiB L3 cache:6 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulne rable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitizatio n Vulnerability Spectre v2:Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIB P
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
ok... rt@sys76:~$ sudo cpupower -c all frequency-info [sudo] password for rt: analyzing CPU 0: driver: intel_cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 1: driver: intel_cpufreq CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 2: driver: intel_cpufreq CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 3: driver: intel_cpufreq CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 4: driver: intel_cpufreq CPUs which run at the same hardware frequency: 4 CPUs which need to have their frequency coordinated by software: 4 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 5: driver: intel_cpufreq CPUs which run at the same hardware frequency: 5 CPUs which need to have their frequency coordinated by software: 5 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 6: driver: intel_cpufreq CPUs which run at the same hardware frequency: 6 CPUs which need to have their frequency coordinated by software: 6 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 7: driver: intel_cpufreq CPUs which run at the same hardware frequency: 7 CPUs which need to have their frequency coordinated by software: 7
[Kernel-packages] [Bug 1929889] Re: [TGL][ADL] Enable CET(Control-flow Enforcement Technology)
@Canonical, After speaking to CET experts at Intel, these CET kernel patches are not needed anymore since the feature is still in development and future directions might change. Hence closing this LP as Invalid ** Changed in: linux-intel (Ubuntu Focal) Status: New => Invalid ** Changed in: intel/lookout-canyon Status: New => Invalid ** Changed in: linux-intel (Ubuntu) Status: Triaged => Invalid -- 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: Invalid Status in linux-intel package in Ubuntu: Invalid Status in linux-intel source package in Focal: Invalid 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 1951861] Re: Fix non-working e1000e device after resume
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- 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/1951861 Title: Fix non-working e1000e device after resume Status in HWE Next: New Status in OEM Priority Project: New Status in linux 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: Won't Fix Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Fix Committed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e devices stop working after s2idle resume. [Fix] Revert the offending patch series, which is to bring some minor power saving. [Test] Vendor did extensive tests and didn't find any regression, and the power consumption remains the same. [Where problems could occur] Maybe on some system the series can save some energy, so reverting will cause some power consumption increase. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951861/+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 1945938] Re: [impish] Remove the downstream xr-usb-uart driver
** Tags removed: verification-needed-focal verification-needed-impish ** Tags added: verification-done-focal verification-done-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/1945938 Title: [impish] Remove the downstream xr-usb-uart driver Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: Fix Released Bug description: [Impact] The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel to add support for USB UART chips: Family: USB UART Part Numbers: XR21V1410, XR21V1412, XR21V1414, XR21B1411, XR21B1420, XR21B1422, XR21B1424, XR22801, XR22802, XR22804 [Fix] In 5.13.x, support for these devices was added to the kernel via. following patch series: Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/ There have been long term maintenance challenges with the downstream vendor driver over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver supports most of the above part numbers, let's remove this redundant out-of-tree driver. [Test] The driver was functionally verified to work fine with XR21V1412. The support for other chips with part numbers mentioned above are also supported with the above patch series. [Where problems could occur] The downstream driver was designed to work with specific BIOS configs only defined on an IoT GW project which is locked to use only Xenial ESM and Bionic LTS kernels, there is a low chance of regression on the Impish series. [This is a tracking bug, please do not triage] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945938/+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 1922406]
I have been remaining in a 5.11.10 this whole time to make sure my wifi works. Now I need some features in later kernal versions although this still seems to be a persistent issue. Is there any progress being made on this iwlwifi module loading issue? -- 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/1922406 Title: Intel AX210 Wi-Fi card does not work since updating to 1.196 Status in Linux: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Bug description: Running 21.04, updated daily. Since updating the linux-firmware package yesterday, the Wireless card does not work with current kernel (5.11.0-13). The error message is as follows: Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting for PNVM load! Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start RT ucode: -110 Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: iwl_trans_send_cmd bad state = 1 It **does** work with 5.11.0-11 (previous version) Distro: Ubuntu 21.04 (Hirsute Hippo) Machine: Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW date: 12/23/2020 CPU: Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP L2 cache: 4 MiB To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1922406/+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 1952077] Re: System time doesn't sync with RTC time on boot
** Changed in: linux (Ubuntu Focal) Assignee: Jesse Sung (wenchien) => Dimitri John Ledkov (xnox) ** Changed in: linux (Ubuntu) Assignee: Jesse Sung (wenchien) => Dimitri John Ledkov (xnox) -- 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/1952077 Title: System time doesn't sync with RTC time on boot Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: == Impact == Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE to "rtc0", system time would only be set if the RTC driver is built-in. This may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for amd64, however it is an issue for other architectures since there may not be a proper RTC driver enabled as built-in. Also making every RTC driver that may be used as built-in is not a good option. == Fix == The commit is in mainline since v5.7: commit f9b2a4d6a5f18e0aaf715206a056565c56889d9f Author: Steve Muckle Date: Wed Nov 6 11:46:25 2019 -0800 rtc: class: support hctosys from modular RTC drivers Due to distribution constraints it may not be possible to statically compile the required RTC driver into the kernel. Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled or not) by checking at the end of RTC device registration whether the time should be synced. Signed-off-by: Steve Muckle Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com Signed-off-by: Alexandre Belloni == Risk of Regression == It's a clean cherry-pick for v5.4 and looks straight forward so risk should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952077/+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 1952077] Re: System time doesn't sync with RTC time on boot
The patch was NAKed: https://lists.ubuntu.com/archives/kernel- team/2021-November/126087.html Change the status back to confirmed. ** Changed in: linux (Ubuntu) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Focal) Status: In Progress => 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/1952077 Title: System time doesn't sync with RTC time on boot Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: == Impact == Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE to "rtc0", system time would only be set if the RTC driver is built-in. This may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for amd64, however it is an issue for other architectures since there may not be a proper RTC driver enabled as built-in. Also making every RTC driver that may be used as built-in is not a good option. == Fix == The commit is in mainline since v5.7: commit f9b2a4d6a5f18e0aaf715206a056565c56889d9f Author: Steve Muckle Date: Wed Nov 6 11:46:25 2019 -0800 rtc: class: support hctosys from modular RTC drivers Due to distribution constraints it may not be possible to statically compile the required RTC driver into the kernel. Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled or not) by checking at the end of RTC device registration whether the time should be synced. Signed-off-by: Steve Muckle Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com Signed-off-by: Alexandre Belloni == Risk of Regression == It's a clean cherry-pick for v5.4 and looks straight forward so risk should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952077/+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 1936295] Re: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate
** Changed in: linux (Ubuntu) Assignee: (unassigned) => AaronMa (mapengyu) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: AaronMa (mapengyu) Status: Confirmed ** Also affects: linux (Ubuntu Trusty) 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/1936295 Title: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate the FW bug Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: New Status in linux source package in Jammy: Confirmed Bug description: *Problem description:* On Lenovo Thinkpad T14s, X13, A475 (and probably more models) the Elantech Trackpoint firmware is defective. The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. Currently, the Trackpoint is barely usable and it's impossible to productively work using it. For a long while, Elantech has not yet put forward (nor confirmed) a firmware update. However, there is a Linux kernel patch mitigating the firmware bug. The kernel bugfix discards the wrongly reported packages by the Elantech hardware. This solves the problem for the user. *Solution:* Please apply existing kernel patch here. https://bugzilla.kernel.org/show_bug.cgi?id=209167 Bug entry in the Linux Kernel.org Bugzilla https://bugzilla.kernel.org/attachment.cgi?id=295733=diff Diff of bugfix *T14s and X13 are Ubuntu certified:* The Lenovo Thinkpad T14s and X13 are Ubuntu certified, but apparently this hardware issue has slipped the Ubuntu certification process! https://ubuntu.com/certified/202006-27978 and https://ubuntu.com/certified/202006-27979 *Further information:* https://forums.lenovo.com/t5/Fedora/T14s-AMD-Trackpoint-almost-unusable/m-p/5064952?page=1 Discussion on the bug in the Lenovo forum. E.g. see comment 18 by Lenovo employee MarkRHPearson *My System:* Lenovo Thinkpad T14s (AMD) 20ujs00k00 Ubuntu 21.04 and 20.04 see entries in kernel.org bugzilla for logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936295/+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 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@Rick, please dump frequency info before doing any changed #sudo cpupower -c all frequency-info if governor is powersave, please change to performance then run some loadings, and observe the cpu current frequency #cpupower frequency-set --governor performance -- 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/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 Status in thermald package in Ubuntu: In Progress Bug description: I would really like to find out why my cpu's keep reverting back to a cpu powersave mode after I get a kernel update then reboot. I cleaned my laptops vent but this seems to happen whenever a new kernel is updated and installed. https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts- significant-throttling-of- intel-i7-processor?noredirect=1#comment2345549_1366090 Description:Ubuntu 20.04.3 LTS Release:20.04 Computer Summary Computer Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Memory 16315MB (4407MB used) Machine TypeLaptop Operating SystemUbuntu 20.04.3 LTS User Name rt (rt) Date/Time Mon 30 Aug 2021 02:33:09 PM EDT Display Resolution 1920x1080 pixels OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA Intel HDMI Audio Adapter HDA-Intel - HDA Intel PCH Audio Adapter USB-Audio - USB Audio Device Input Devices Power Button Sleep Button Lid Switch Power Button AT Translated Set 2 keyboard USB Audio Device ETPS/2 Elantech Touchpad Logitech Anywhere MX Video Bus HDA Intel PCH Mic HDA Intel PCH Front Headphone HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 Printers (CUPS) OfficeJet_Pro_6978 Default SCSI Disks TSSTcorp CDDVDW SN-208DB ATA INTEL SSDMCEAC12 ATA ST1000LM014-1EJ1 Operating System Version Kernel Linux 5.4.0-81-generic (x86_64) Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31 DistributionUbuntu 20.04.3 LTS Current Session Computer Name sys76 User Name rt (rt) Languageen_US.UTF-8 () Home Directory /home/rt Misc Uptime 20 minutes Load Average0.83, 1.37, 1.62 Available entropy in /dev/random3649 bits (healthy) rt@sys76:~$ dpkg -l *freq* | grep ii rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6 Busy% Bzy_MHz IRQ PkgTmp PkgWatt GFXWatt 2.95800 334747 2.160.01 2.76800 306949 2.150.01 5.85800 512248 2.730.01 11.87 800 800847 3.410.04 8.23800 577847 2.860.05 rt@sys76:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Stepping:3 CPU MHz: 798.103 CPU max MHz: 3400. CPU min MHz: 800. BogoMIPS:4788.65 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache:1 MiB L3 cache:6 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulne rable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitizatio n
[Kernel-packages] [Bug 1952817] Re: [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir
** Tags removed: originate-from-1949722 ** Tags added: originate-from-1945395 -- 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/1952817 Title: [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: New Bug description: [Impact] On new amdgpu renoir firmware, the USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Restore the old amdgpu fw, this issue is gone. For new fw, AMD make kernel fix be ready, after backport, the issue is not reproduced on new fw. Cherry-picked from stable kernel release to fix it. [Test] After S3 on renoir's platforms, hotplug USB, the USB3.1 devices works good. [Where problems could occur] AMD renoir platform may have issues when suspend. Jammy already got this commit via stable updates v5.15.3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952817/+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 1952385] Re: Fix missing external headset after resume problem for Cirrus CS8409 sound driver
** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Won't Fix -- 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/1952385 Title: Fix missing external headset after resume problem for Cirrus CS8409 sound driver Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.13 package in Ubuntu: New 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.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Triaged Status in linux-oem-5.13 source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On some platforms with Cirrus CS8409 audio codec, the external headset will fail to be detected after system resume. [Fix] Cirrus released a fix and send it upstream for approval. It's trying to schedule a harmless delayed work to do jack detection to reflect the real power state after resume. [Test] Plug-in an external headset in front headset port, suspend/resume the system then check whether the headset function works as expected. [Where problem could occur] Low. It only affect the platforms with Cirrus codec CS8409 which used to have problem. == Original Bug Description == [Summary] System can't detect external headset after suspend [Steps to reproduce] 1. install manifest and boot into OS 2. plug-in an external headset in front headset port 3. un-plug external headset 4. suspend system 5. resume system from suspend 6. plug-in an external headset [Expected result] System could detect external headset after suspend [Actual result] System can't detect external headset after suspend [Failure rate] 3/3 [Additional information] CID: 202110-29567 SKU: DLPV-SFF-DVT-C1 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152 system-manufacturer: Dell Inc. system-product-name: Vostro 3710 bios-version: 0.13.73 CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4680] (rev 0c) kernel-version: 5.13.0-1019-oem [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952385/+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-hwe-5.13/5.13.0.23.23~20.04.10)
All autopkgtests for the newly accepted linux-meta-hwe-5.13 (5.13.0.23.23~20.04.10) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) systemd/245.4-4ubuntu3.13 (ppc64el, s390x, 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-hwe-5.13 [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 1952933] Re: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq
** Changed in: linux (Ubuntu Impish) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952933 Title: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: During MAAS deployment: [ 107.768146] Unable to handle kernel read from unreadable memory at virtual address domain : maas[ 107.943413] Mem abort info: rootserver: 10.229.32.21 rootpath: filename :[ 108.043666] ESR = 0x9604 lpxelinux.0 :: root=squash:http://10.229.32.21:5248/images/ubu[ 108.147045] EC = 0x25: DABT (current EL), IL = 32 bits ntu/arm64/xgene-uboot/impish/stable/squashfs :: mount_squash do[ 108.277541] SET = 0, FnV = 0 wnloading http://10.229.32.21:5248/images/ubuntu/arm64/xgene-ubo[ 108.380921] EA = 0, S1PTW = 0 ot/impish/stable/squashfs to /root.tmp.img Connecting to 10.229[ 108.485351] Data abort info: .32.21:5248 (10.229.32.21:5248) [ 108.586639] ISV = 0, ISS = 0x0004 [ 108.667060] CM = 0, WnR = 0 [ 108.702635] user pgtable: 4k pages, 48-bit VAs, pgdp=00401ce02000 root.tmp.img [ 108.779941] [] pgd=, p4d= 4% [ 108.884372] Internal error: Oops: 9604 [#1] SMP [ 108.948102] Modules linked in: raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx4_ib ib_uverbs ib_core mlx4_en mlx4_core gpio_keys_polled gpio_dwapb crct10dif_ce ahci_xgene gpio_xgene_sb aes_neon_bs aes_neon_blk crypto_simd cryptd [ 109.286243] CPU: 0 PID: 11 Comm: ksoftirqd/0 Not tainted 5.13.0-20-generic #20-Ubuntu [ 109.380233] Hardware name: HP ProLiant m400 Server Cartridge (DT) [ 109.453258] pstate: 6045 (nZCv daif +PAN -UAO -TCO BTYPE=--) [ 109.525342] pc : mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en] [ 109.589087] lr : mlx4_en_poll_rx_cq+0x7c/0x17c [mlx4_en] [ 109.652828] sp : 8000129cbc60 [ 109.692470] x29: 8000129cbc60 x28: 012c x27: 000ff7e95fc0 [ 109.778115] x26: x25: 20908508 x24: 21b40940 [ 109.863763] x23: 20908508 x22: 20908400 x21: 21b4 [ 109.949409] x20: 0040 x19: 0040 x18: 0014 [ 110.035056] x17: 1122e350 x16: cb46f8bb x15: e2b6a183 [ 110.120703] x14: 26fff11e x13: 9312ff0b x12: [ 110.206349] x11: 0006 x10: 0040 x9 : 89119320 [ 110.291997] x8 : 08acdc00 x7 : 02c0 x6 : dff8 [ 110.377642] x5 : 0394 x4 : 03960040 x3 : 21c2 [ 110.463289] x2 : x1 : x0 : [ 110.548937] Call trace: [ 110.578147] mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en] [ 110.637719] __napi_poll+0x40/0x1e0 [ 110.679551] net_rx_action+0x2d8/0x34c [ 110.724513] __do_softirq+0x128/0x388 [ 110.768432] run_ksoftirqd+0x6c/0x94 [ 110.811308] smpboot_thread_fn+0x15c/0x1a0 [ 110.860443] kthread+0x114/0x120 [ 110.899145] ret_from_fork+0x10/0x18 [ 110.942024] Code: 1100fc41 1a82b021 13067c21 93407c21 (f8617800) [ 111.015158] ---[ end trace b37ae99414884442 ]--- [ 111.070550] Kernel panic - not syncing: Oops: Fatal exception in interrupt [ 111.152964] SMP: stopping secondary CPUs [ 111.200016] Kernel Offset: 0x8 from 0x80001000 [ 111.265837] PHYS_OFFSET: 0x40 [ 111.309651] CPU features: 0x0251,0046 [ 111.361915] Memory Limit: none [ 111.398431] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952933/+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-azure/5.13.0.1009.10)
All autopkgtests for the newly accepted linux-meta-azure (5.13.0.1009.10) for impish have finished running. The following regressions have been reported in tests triggered by the package: systemd/248.3-1ubuntu8 (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/impish/update_excuses.html#linux-meta-azure [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 1786013] Autopkgtest regression report (linux-meta-hwe-5.11/5.11.0.42.46~20.04.20)
All autopkgtests for the newly accepted linux-meta-hwe-5.11 (5.11.0.42.46~20.04.20) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.13 (amd64, s390x, ppc64el) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (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-hwe-5.11 [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 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
I have had another user run into the issue in the OpenRGB bug tracker: https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1984#note_749829340 ** Bug watch added: gitlab.com/CalcProgrammer1/OpenRGB/-/issues #1984 https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1984 -- 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/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in linux package in Ubuntu: Confirmed Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950062/+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 1952922] Re: package linux-modules-nvidia-470-5.11.0-41-generic 5.11.0-41.45+2 failed to install/upgrade: installed linux-modules-nvidia-470-5.11.0-41-generic package post-insta
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1952922 Title: package linux-modules-nvidia-470-5.11.0-41-generic 5.11.0-41.45+2 failed to install/upgrade: installed linux-modules- nvidia-470-5.11.0-41-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules package in Ubuntu: New Bug description: - ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-modules-nvidia-470-5.11.0-41-generic 5.11.0-41.45+2 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Dec 1 15:19:53 2021 ErrorMessage: installed linux-modules-nvidia-470-5.11.0-41-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-12-01 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-470-5.11.0-41-generic 5.11.0-41.45+2 failed to install/upgrade: installed linux-modules-nvidia-470-5.11.0-41-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1952922/+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 1945764] Re: crda: Fail to build against OpenSSL 3.0
** Changed in: crda (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1945764 Title: crda: Fail to build against OpenSSL 3.0 Status in crda package in Ubuntu: New Bug description: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpadlibrarian.net/559464520/buildlog_ubuntu-impish- amd64.crda_4.14+git20191112.9856751-1.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 I haven't found any mention of the issue upstream. However, a quick glance at the logs tells me the errors seem due to the use of deprecated APIs combined with -Werror. Thus, a quick fix might be to simply add -Wno-error=deprecated-declarations to the CFLAGS ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1945764/+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
Re: [Kernel-packages] [Bug 1952836] Re: Suspend not working after update to Linux 5.13.0-22
Agreed happened after the linux upgrade, so I selected dist-upgrade in the ubuntu-bug menu because that seemed closest, since I sometimes used apt dist-upgrade for a normal upgrade too. On Wed, 2021-12-01 at 12:07 +, Chris Guiver wrote: > The release-upgrade to 21.10 occurred 47 days ago, so your issue > (filed > against the release-upgrader tool that moved you to 21.10 from 21.04) > is > unlikely the issue, it's more likely related to a kernel upgrade. > > ** 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/1952836 Title: Suspend not working after update to Linux 5.13.0-22 Status in linux package in Ubuntu: Confirmed Bug description: I use suspend frequently, but after the last update of Linux, the restart fails. However it seems to work partly since the disk activity light is showing activities, but the screen remains black and without power. I have to power off the system by pressing the power-off button for 10 seconds. I suspended the system at 1:35 and I will include the /var/log/kern.log I hope it helps. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 01:41:18 2021 InstallationDate: Installed on 2021-10-09 (52 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-10-14 (47 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952836/+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/4.15.0.165.154)
All autopkgtests for the newly accepted linux-meta (4.15.0.165.154) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux/4.15.0-165.173 (s390x, amd64, ppc64el, arm64, i386) 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 [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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Nice write up, I am back to my evdi device from a week and is working flawless now. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1950339] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544717/+files/ProcInterrupts.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544719/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544715/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544718/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544713/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544716/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544722/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544720/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] Re: Screen stays black after going idle or waking up from suspend on AMD laptop
Bug persists in latest update (5.13.0-23-generic) ** Changed in: linux-signed-hwe-5.13 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544723/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544721/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544710/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544709/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544706/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544707/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544714/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544708/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544712/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544711/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio /dev/snd/controlC0: michael2467 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-08 (145 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 Package: linux-signed-hwe-5.13 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+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 1950339] Re: Screen stays black after going idle or waking up from suspend on AMD laptop
apport information ** Tags added: apport-collected ** Description changed: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: michael2467 F pulseaudio + /dev/snd/controlC1: michael2467 F pulseaudio + /dev/snd/controlC0: michael2467 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-07-08 (145 days ago) + InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) + MachineType: LENOVO 20Y1S00C00 + Package: linux-signed-hwe-5.13 + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.13.0-23.23~20.04.1-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-23-generic N/A + linux-backports-modules-5.13.0-23-generic N/A + linux-firmware 1.187.20 + Tags: focal + Uname: Linux 5.13.0-23-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/30/2021 + dmi.bios.release: 1.35 + dmi.bios.vendor: LENOVO + dmi.bios.version: R1BET66W(1.35 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20Y1S00C00 + 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.35 + dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1: + dmi.product.family: ThinkPad P14s Gen 1 + dmi.product.name: 20Y1S00C00 + dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 + dmi.product.version: ThinkPad P14s Gen 1 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1950339/+attachment/5544705/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael2467 F pulseaudio /dev/snd/controlC1: michael2467 F pulseaudio
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle/5.13.0.1011.13)
All autopkgtests for the newly accepted linux-meta-oracle (5.13.0.1011.13) for impish have finished running. The following regressions have been reported in tests triggered by the package: systemd/248.3-1ubuntu8 (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/impish/update_excuses.html#linux-meta-oracle [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 1952933] 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 1952933 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 ** Changed in: linux (Ubuntu Impish) 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/1952933 Title: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: Incomplete Bug description: During MAAS deployment: [ 107.768146] Unable to handle kernel read from unreadable memory at virtual address domain : maas[ 107.943413] Mem abort info: rootserver: 10.229.32.21 rootpath: filename :[ 108.043666] ESR = 0x9604 lpxelinux.0 :: root=squash:http://10.229.32.21:5248/images/ubu[ 108.147045] EC = 0x25: DABT (current EL), IL = 32 bits ntu/arm64/xgene-uboot/impish/stable/squashfs :: mount_squash do[ 108.277541] SET = 0, FnV = 0 wnloading http://10.229.32.21:5248/images/ubuntu/arm64/xgene-ubo[ 108.380921] EA = 0, S1PTW = 0 ot/impish/stable/squashfs to /root.tmp.img Connecting to 10.229[ 108.485351] Data abort info: .32.21:5248 (10.229.32.21:5248) [ 108.586639] ISV = 0, ISS = 0x0004 [ 108.667060] CM = 0, WnR = 0 [ 108.702635] user pgtable: 4k pages, 48-bit VAs, pgdp=00401ce02000 root.tmp.img [ 108.779941] [] pgd=, p4d= 4% [ 108.884372] Internal error: Oops: 9604 [#1] SMP [ 108.948102] Modules linked in: raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx4_ib ib_uverbs ib_core mlx4_en mlx4_core gpio_keys_polled gpio_dwapb crct10dif_ce ahci_xgene gpio_xgene_sb aes_neon_bs aes_neon_blk crypto_simd cryptd [ 109.286243] CPU: 0 PID: 11 Comm: ksoftirqd/0 Not tainted 5.13.0-20-generic #20-Ubuntu [ 109.380233] Hardware name: HP ProLiant m400 Server Cartridge (DT) [ 109.453258] pstate: 6045 (nZCv daif +PAN -UAO -TCO BTYPE=--) [ 109.525342] pc : mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en] [ 109.589087] lr : mlx4_en_poll_rx_cq+0x7c/0x17c [mlx4_en] [ 109.652828] sp : 8000129cbc60 [ 109.692470] x29: 8000129cbc60 x28: 012c x27: 000ff7e95fc0 [ 109.778115] x26: x25: 20908508 x24: 21b40940 [ 109.863763] x23: 20908508 x22: 20908400 x21: 21b4 [ 109.949409] x20: 0040 x19: 0040 x18: 0014 [ 110.035056] x17: 1122e350 x16: cb46f8bb x15: e2b6a183 [ 110.120703] x14: 26fff11e x13: 9312ff0b x12: [ 110.206349] x11: 0006 x10: 0040 x9 : 89119320 [ 110.291997] x8 : 08acdc00 x7 : 02c0 x6 : dff8 [ 110.377642] x5 : 0394 x4 : 03960040 x3 : 21c2 [ 110.463289] x2 : x1 : x0 : [ 110.548937] Call trace: [ 110.578147] mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en] [ 110.637719] __napi_poll+0x40/0x1e0 [ 110.679551] net_rx_action+0x2d8/0x34c [ 110.724513] __do_softirq+0x128/0x388 [ 110.768432] run_ksoftirqd+0x6c/0x94 [ 110.811308] smpboot_thread_fn+0x15c/0x1a0 [ 110.860443] kthread+0x114/0x120 [ 110.899145] ret_from_fork+0x10/0x18 [ 110.942024] Code: 1100fc41 1a82b021 13067c21 93407c21 (f8617800) [ 111.015158] ---[ end trace b37ae99414884442 ]--- [ 111.070550] Kernel panic - not syncing: Oops: Fatal exception in interrupt [ 111.152964] SMP: stopping secondary CPUs [ 111.200016] Kernel Offset: 0x8 from 0x80001000 [ 111.265837] PHYS_OFFSET: 0x40 [ 111.309651] CPU features: 0x0251,0046 [ 111.361915] Memory Limit: none [ 111.398431] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952933/+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 1952933] [NEW] impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq
Public bug reported: During MAAS deployment: [ 107.768146] Unable to handle kernel read from unreadable memory at virtual address domain : maas[ 107.943413] Mem abort info: rootserver: 10.229.32.21 rootpath: filename :[ 108.043666] ESR = 0x9604 lpxelinux.0 :: root=squash:http://10.229.32.21:5248/images/ubu[ 108.147045] EC = 0x25: DABT (current EL), IL = 32 bits ntu/arm64/xgene-uboot/impish/stable/squashfs :: mount_squash do[ 108.277541] SET = 0, FnV = 0 wnloading http://10.229.32.21:5248/images/ubuntu/arm64/xgene-ubo[ 108.380921] EA = 0, S1PTW = 0 ot/impish/stable/squashfs to /root.tmp.img Connecting to 10.229[ 108.485351] Data abort info: .32.21:5248 (10.229.32.21:5248) [ 108.586639] ISV = 0, ISS = 0x0004 [ 108.667060] CM = 0, WnR = 0 [ 108.702635] user pgtable: 4k pages, 48-bit VAs, pgdp=00401ce02000 root.tmp.img [ 108.779941] [] pgd=, p4d= 4% [ 108.884372] Internal error: Oops: 9604 [#1] SMP [ 108.948102] Modules linked in: raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx4_ib ib_uverbs ib_core mlx4_en mlx4_core gpio_keys_polled gpio_dwapb crct10dif_ce ahci_xgene gpio_xgene_sb aes_neon_bs aes_neon_blk crypto_simd cryptd [ 109.286243] CPU: 0 PID: 11 Comm: ksoftirqd/0 Not tainted 5.13.0-20-generic #20-Ubuntu [ 109.380233] Hardware name: HP ProLiant m400 Server Cartridge (DT) [ 109.453258] pstate: 6045 (nZCv daif +PAN -UAO -TCO BTYPE=--) [ 109.525342] pc : mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en] [ 109.589087] lr : mlx4_en_poll_rx_cq+0x7c/0x17c [mlx4_en] [ 109.652828] sp : 8000129cbc60 [ 109.692470] x29: 8000129cbc60 x28: 012c x27: 000ff7e95fc0 [ 109.778115] x26: x25: 20908508 x24: 21b40940 [ 109.863763] x23: 20908508 x22: 20908400 x21: 21b4 [ 109.949409] x20: 0040 x19: 0040 x18: 0014 [ 110.035056] x17: 1122e350 x16: cb46f8bb x15: e2b6a183 [ 110.120703] x14: 26fff11e x13: 9312ff0b x12: [ 110.206349] x11: 0006 x10: 0040 x9 : 89119320 [ 110.291997] x8 : 08acdc00 x7 : 02c0 x6 : dff8 [ 110.377642] x5 : 0394 x4 : 03960040 x3 : 21c2 [ 110.463289] x2 : x1 : x0 : [ 110.548937] Call trace: [ 110.578147] mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en] [ 110.637719] __napi_poll+0x40/0x1e0 [ 110.679551] net_rx_action+0x2d8/0x34c [ 110.724513] __do_softirq+0x128/0x388 [ 110.768432] run_ksoftirqd+0x6c/0x94 [ 110.811308] smpboot_thread_fn+0x15c/0x1a0 [ 110.860443] kthread+0x114/0x120 [ 110.899145] ret_from_fork+0x10/0x18 [ 110.942024] Code: 1100fc41 1a82b021 13067c21 93407c21 (f8617800) [ 111.015158] ---[ end trace b37ae99414884442 ]--- [ 111.070550] Kernel panic - not syncing: Oops: Fatal exception in interrupt [ 111.152964] SMP: stopping secondary CPUs [ 111.200016] Kernel Offset: 0x8 from 0x80001000 [ 111.265837] PHYS_OFFSET: 0x40 [ 111.309651] CPU features: 0x0251,0046 [ 111.361915] Memory Limit: none [ 111.398431] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]--- ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: Incomplete ** Tags: impish ** Also affects: linux (Ubuntu Impish) 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/1952933 Title: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: Incomplete Bug description: During MAAS deployment: [ 107.768146] Unable to handle kernel read from unreadable memory at virtual address domain : maas[ 107.943413] Mem abort info: rootserver: 10.229.32.21 rootpath: filename :[ 108.043666] ESR = 0x9604 lpxelinux.0 :: root=squash:http://10.229.32.21:5248/images/ubu[ 108.147045] EC = 0x25: DABT (current EL), IL = 32 bits ntu/arm64/xgene-uboot/impish/stable/squashfs :: mount_squash do[ 108.277541] SET = 0, FnV = 0 wnloading http://10.229.32.21:5248/images/ubuntu/arm64/xgene-ubo[ 108.380921] EA = 0, S1PTW = 0 ot/impish/stable/squashfs to /root.tmp.img Connecting to 10.229[ 108.485351] Data abort info: .32.21:5248 (10.229.32.21:5248) [ 108.586639] ISV = 0, ISS = 0x0004 [ 108.667060] CM
[Kernel-packages] [Bug 1952621] Re: Bionic/linux-azure: Call trace on Ubuntu 18.04 VM with Standard NV24
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-azure-5.4 (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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1952621 Title: Bionic/linux-azure: Call trace on Ubuntu 18.04 VM with Standard NV24 Status in linux-azure package in Ubuntu: Invalid Status in linux-azure-5.4 package in Ubuntu: New Status in linux-azure source package in Bionic: Invalid Status in linux-azure-5.4 source package in Bionic: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-5.4 source package in Focal: Invalid Bug description: SRU Justification [Impact] During large scale deployment testing, we found below call trace when provisioning Ubuntu 18.04 VM with size Standard_NV24. Engineer deployed instance 10 times and encountered once. It looks like a race condition when probe device, but finally all devices can be probed. [ 4.938162] sysfs: cannot create duplicate filename '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/47505500-0003--3130-444531334632/pci0003:00/0003:00:00.0/config' [ 4.944816] sr 5:0:0:0: [sr0] scsi3-mmc drive: 0x/0x tray [ 4.951818] CPU: 0 PID: 135 Comm: kworker/0:2 Not tainted 5.4.0-1061-azure #64~18.04.1-Ubuntu [ 4.951820] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 4.958943] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 4.955812] Workqueue: hv_pri_chan vmbus_add_channel_work [ 4.955812] Call Trace: [ 4.955812] dump_stack+0x57/0x6d [ 4.955812] sysfs_warn_dup+0x5b/0x70 [ 4.955812] sysfs_add_file_mode_ns+0x158/0x180 [ 4.955812] sysfs_create_bin_file+0x64/0x90 [ 4.955812] pci_create_sysfs_dev_files+0x72/0x270 [ 4.955812] pci_bus_add_device+0x30/0x80 [ 4.955812] pci_bus_add_devices+0x31/0x70 [ 4.955812] hv_pci_probe+0x48c/0x650 [ 4.955812] vmbus_probe+0x3e/0x90 [ 4.955812] really_probe+0xf5/0x440 [ 4.955812] driver_probe_device+0x11b/0x130 [ 4.955812] __device_attach_driver+0x7b/0xe0 [ 4.955812] ? driver_allows_async_probing+0x60/0x60 [ 4.955812] bus_for_each_drv+0x6e/0xb0 [ 4.955812] __device_attach+0xe4/0x160 [ 4.955812] device_initial_probe+0x13/0x20 [ 4.955812] bus_probe_device+0x92/0xa0 [ 4.955812] device_add+0x402/0x690 [ 4.955812] device_register+0x1a/0x20 [ 4.955812] vmbus_device_register+0x5e/0xf0 [ 4.955812] vmbus_add_channel_work+0x2c4/0x640 [ 4.955812] process_one_work+0x209/0x400 [ 4.955812] worker_thread+0x34/0x400 [ 4.955812] kthread+0x121/0x140 [ 4.955812] ? process_one_work+0x400/0x400 [ 4.955812] ? kthread_park+0x90/0x90 [ 4.955812] ret_from_fork+0x35/0x40 [ 5.043612] hv_pci 47505500-0004-0001-3130-444531334632: PCI VMBus probing: Using version 0x10002 [ 5.260563] hv_pci 47505500-0004-0001-3130-444531334632: PCI host bridge to bus 0004:00 Dexuan did some research and it looks like this is a longstanding race condition bug in the generic PCI subsystem (due to the timing, there can be more than 1 place where the PCI code tries to create the same ‘config’ sysfs file): https://patchwork.kernel.org/project/linux-pci/patch/20200716110423.xtfyb3n6tn5ixedh@pali/#23669641 The bug was reported on 7/16/2020, and the last reply was on 6/25/2021. It looks like this has not been fixed after 1+ year… Business Impact [Test Case] Repeated deployment on a Standard_NV24 instance. MS reported the reproduction rate is 3/551 before the patch, and 0/838 with the patch. [Where things could go wrong] Deployments could fail for other reasons. [Other info] SF: #00321027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1952621/+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 1952234] Re: linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver
This bug is awaiting verification that the linux-azure/5.13.0-1009.10
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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.
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-impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure-4.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1952234
Title:
linux-azure: add Icelake servers support in no-HWP mode to
cpufreq/intel_pstate driver
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-4.15 package in Ubuntu:
Invalid
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
Fix Committed
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure-4.15 source package in Focal:
Invalid
Status in linux-azure source package in Hirsute:
Fix Committed
Status in linux-azure-4.15 source package in Hirsute:
Invalid
Status in linux-azure source package in Impish:
Fix Committed
Status in linux-azure-4.15 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Starting with the AH2020 Azure host build, Hyper-V is virtualizing
some registers that provide information about the CPU frequency. The
registers are read-only in a guest VM, so the guest can see the
frequency, but cannot make any modifications.
This feature also requires that the VM Configuration Version be 9.2 or
later, which means it needs to be a new VM type, such as the just
introduced Dv5/Ev5 series, and the new M832v2 VMs.
Within the Linux VM, the presence of the feature is indicated by the
“aperfmperf” flag in the “lscpu” flags output (or in the flags field
in /proc/cpuinfo).
It turns out there is a Linux kernel limitation when running on the
new Intel IceLake processors used for the Dv5/Ev5 series. Upstream
commit fbdc21e9b038 was added to provide IceLake support in the 5.14
kernel.
Microsoft has asked to backport fbdc21e9b038 commit to all supported
kernels.
[Test Plan]
Run Intel IceLake based VM and check the "aperfmperf" flag in the
"lscpu" flags output.
Without the patch the intel_pstate directory is missing from
/sys/devices/system/cpu/ and /sys/devices/system/cpu/cpufreq/ is
empty.
[Where problems could occur]
* intel_pstate driver is always used on Intel IceLake based VMs
without checking for presence of "aperfmperf" CPU flag.
* In earlier (5.4 and 4.15) linux-azure kernels when intel_pstate
driver is used it is in "active" mode instead of "passive" one (as
reported by "cat /sys/devices/system/cpu/intel_pstate/status", also
"cat /sys/devices/system/cpu/cpufreq/policy0/scaling_driver" returns
"intel_pstate" instead of "intel_cpufreq" which is the expected
behavior when in "active" mode).
If a consistent behavior across all kernel versions is desired commit
33aa46f252c7 ("cpufreq: intel_pstate: Use passive mode by default
without HWP") from the upstream should probably also be backported.
* /sys/devices/system/cpu/cpufreq/policy*/scaling_{min,max}_freq files
can be modified and the values reported by kernel will no longer match
the values used by hardware.
[Other Info]
None.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1952234/+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 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
rt@sys76:~$ sudo systemctl status thermald.service ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; v> Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enabl> Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:s> Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4 Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for> Dec 01 09:39:24 sys76 thermald[1319]: Terminating ... Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service... Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request .. Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded. Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service. lines 1-16/16 (END)...skipping... ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; ven> Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable > Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:ste> Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4 Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for r> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for r> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for r> Dec 01 09:39:24 sys76 thermald[1319]: Terminating ... Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service... Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request .. Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded. Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service. ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor pre> Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable --adapt> Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:stepping 0> Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4 Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading > Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading > Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading > Dec 01 09:39:24 sys76 thermald[1319]: Terminating ... Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service... Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request .. Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded. Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service. ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor preset> Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable --adaptive> Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:stepping 0x6:> Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4 Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading raw> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading raw> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading raw> Dec 01 09:39:24 sys76 thermald[1319]: Terminating ... Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service... Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request .. Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded. Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service. ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable --adaptive (code=exited, status=0/> Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels;
[Kernel-packages] [Bug 1932029] Re: Support builtin revoked certificates
This bug is awaiting verification that the linux/4.15.0-165.173 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1932029 Title: Support builtin revoked certificates Status in linux package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure-5.8 source package in Xenial: Invalid Status in linux-hwe-5.8 source package in Xenial: Invalid Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-azure-5.8 source package in Bionic: Invalid Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-azure-5.8 source package in Focal: Fix Released Status in linux-hwe-5.8 source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-azure-5.8 source package in Hirsute: Invalid Status in linux-hwe-5.8 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in revoked certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to communicate revoked certificates to the kernel and depending on how good EFI firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates, however one boots. [Test Plan] * Boot kernel directly, or just with grub, and without shim * Check that $ sudo keyctl list %:.blacklist Contains asymmetric 2012 key. [Where problems could occur] * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. * an ubuntu kernel team regression test is being added to assert that expected revoked certificates have been revoked see https://lists.ubuntu.com/archives/kernel-team/2021-August/122986.html * Previous reviews Unstable & v5.13: https://lists.ubuntu.com/archives/kernel- team/2021-June/121362.html Hirsute & v5.11: https://lists.ubuntu.com/archives/kernel- team/2021-August/122996.html Focal & v5.10 (oem): https://lists.ubuntu.com/archives/kernel- team/2021-August/123470.html Focal & v5.8 (azure): https://lists.ubuntu.com/archives/kernel- team/2021-September/124336.html Focal & v5.4: https://lists.ubuntu.com/archives/kernel- team/2021-October/124497.html Bionic & v4.15: TODO Xenial & v4.4: TODO Trusty & v3.13: TODO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+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 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le
This bug is awaiting verification that the linux/4.15.0-165.173 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- 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/1867570 Title: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [ Impact ] The reuseport_bpf_numa testcase in selftests/net fails on some PowerPC systems with: # selftests: net: reuseport_bpf_numa # IPv4 UDP # send node 0, receive socket 0 # libnuma: Warning: Cannot read node cpumask from sysfs # ./reuseport_bpf_numa: failed to pin to node: No such file or directory not ok 3 selftests: net: reuseport_bpf_numa # exit=1 [ Fix ] In some platforms the numa node numbers are not necessarily consecutive, so when reuseport_bpf_numa iterates on the nodes from 0 to the max available node some of those will not be available. The fix is to change the testcase so it checks whether the node is available before trying to send/receive from it. [ Test ] Run reuseport_bpf_numa from selftests/net in one of the affected test nodes. [ Where Problems Could Occur ] This is a very simple fix which relies on the libnuma exported functions and bitmaps to check whether a numa node number is available on the system. If something is not right on how this check is made or on the libnuma code itself only the reuseport_bpf_numa testcase will be affected by reporting false negatives or having a reduced test coverage. [ Original bug report ] This issue was extracted from the comment in bug 1812638, since that bug will be specific for i386 This reuseport_bpf_numa in net will fail on PowerPC with: The output on B-5.3 P8 is: # selftests: net: reuseport_bpf_numa # IPv4 UDP # send node 0, receive socket 0 # send node 1, receive socket 7 # ./reuseport_bpf_numa: node id/receive socket mismatch not ok 3 selftests: net: reuseport_bpf_numa # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1867570/+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 1928679] Re: Support importing mokx keys into revocation list from the mok table
This bug is awaiting verification that the linux/4.15.0-165.173 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1928679 Title: Support importing mokx keys into revocation list from the mok table Status in linux package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure-5.8 source package in Xenial: Invalid Status in linux-hwe-5.8 source package in Xenial: Invalid Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-azure-5.8 source package in Bionic: Invalid Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-azure-5.8 source package in Focal: Fix Released Status in linux-hwe-5.8 source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-azure-5.8 source package in Hirsute: Invalid Status in linux-hwe-5.8 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx) which revokes many Ubuntu kernel hashes and 2012 signing key. * Kernel should import those into it's %:.blacklist keyring such that it prohibits signed kexec of the revoked kernels. * v5.13-rc1 kernel has learned how to import mokx and how to import full certs into the %:.blacklist keyring. * However, it only does so by reading MokListXRT efi variable. * Due to the large size of Ubuntu's vendor-dbx, shim does not create MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2 MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also exposes MokListXRT via mokvar table, which is easier to parse and contains all the revocations in full. Kernel needs a patch to read MokListXRT via mokvar table. * We have two options on how to proceed from here, either we include the same hashes and certs as our vendordbx in in the kernel as revocation list, or we fix kernel to read MokListXRT via mokvar table * The above is known as CVE-2020-26541 * Separately it would be nice to add informational dmesg messages when revoking signing certificates, as a good indication that signing key rotation events have happened and have been applied correctly. [Test Plan] * Boot kernel with 15.4 based Ubuntu shim * Install keyutils package * Execute $ sudo keyctl list %:.blacklist it should list in exccess of 300+ hash entries. It also must list assymetric Canonical signing key from 2012. * Separately check dmesg to observe that asymmetric canonical signing key from 2012 is revoked. * $ sudo ls /sys/firmware/efi/mok-variables MokListRT MokListXRT SbatLevelRT When booted with shim, the mok-variables directory above should exist, and contain at least `MokListRT MokListXRT SbatLevelRT` files. In kernel messages, the CA certificate should be loaded via MOKvar table i.e: * $ sudo journalctl -b -k | grep -A1 'MOKvar table' Sep 27 13:11:04 champion-spaniel kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Sep 27 13:11:04 champion-spaniel kernel: integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63 [Where problems could occur] * EFI variable storage can be full thus preventing shim to mirror efivars and the moktable. On decent hardware this should not happen, but has been observed to be corrupted on some older EDKII based OVMF instances with small EFI variable storage space (pre-4MB). [Other Info] * The patches to fix the above have been submitted upstream https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/ https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/ This will
[Kernel-packages] [Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
This bug is awaiting verification that the linux/4.15.0-165.173 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- 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/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 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: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] setgid files may be created on setgid directories owned by the directory group by users not belonging to that group. That is restricted to XFS. [Fix/Backport] The fix for 5.11 and 5.10 kernels is one simple commit with a minor backport conflict fixup on 5.10. 5.4, on the other hand, required other 3 pre-requisites, which could be picked cleanly. On 4.15, however, they needed a lot of mangling and fixes. [Test case] creat09 LTP test case. [Potential regression] The creation of files on XFS may have the wrong attributes. Also, on 5.4 and 4.15, the potential regression is larger, also affecting quota, statistics and other interfaces where uid, gid and projid are exposed. = These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve are actually the same test. Issue found on F-oem-5.10.0-1051.53 With LTP upstream head SHA1 2ac54d426 This is not a regression, it's because of a recent update that enables this test on different filesystems: https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a Test failed on XFS with: tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set Test log: Checking for required user/group ids 'nobody' user id and group found. 'bin' user id and group found. 'daemon' user id and group found. Users group found. Sys group found. Required users/groups exist. no big block device was specified on commandline. Tests which require a big block device are disabled. You can specify it with option -z INFO: Test start time: Mon Nov 8 10:00:06 UTC 2021 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 61758 -n 61758 -f /tmp/ltp-shLYORuoRT/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist
[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels
This bug is awaiting verification that the linux/4.15.0-165.173 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- 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_syscalls / 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: Fix Committed 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: Fix Committed 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: Fix Committed 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: Fix Committed 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: [Impact] Some uses of kernel_read_file_from_fd may lead to a WARN when the file is not opened for reading. The WARNING, however, is not present on earlier kernels, which will return a different error code. The fix, however, has been applied to upstream stable and may be worth so tests can PASS without much change. [Fix/Backport] The fix is trivial, but the backport for Focal and Bionic was picked up from 5.4.y upstream stable tree, because the function was moved to a different file. [Test case] The finit_module02 test case from LTP covers this. [Potential regression] kernel_read_file_from_fd is used for module loading and kexec, so there is where regressions might show up. = 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 1952925] [NEW] package linux-modules-5.11.0-41-generic 5.11.0-41.45~20.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.11.0-41-gene
Public bug reported: This happens on an upgrade of system software. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.11.0-41-generic 5.11.0-41.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 30 06:35:15 2021 DpkgTerminalLog: Preparing to unpack .../0-linux-modules-5.11.0-41-generic_5.11.0-41.45~20.04.1_amd64.deb ... Unpacking linux-modules-5.11.0-41-generic (5.11.0-41.45~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-S0NIdl/0-linux-modules-5.11.0-41-generic_5.11.0-41.45~20.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.11.0-41-generic.list-new': Operation not permitted DuplicateSignature: package:linux-modules-5.11.0-41-generic:5.11.0-41.45~20.04.1 Unpacking linux-modules-5.11.0-41-generic (5.11.0-41.45~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-S0NIdl/0-linux-modules-5.11.0-41-generic_5.11.0-41.45~20.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.11.0-41-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-5.11.0-41-generic.list-new': Operation not permitted InstallationDate: Installed on 2021-09-03 (89 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-modules-5.11.0-41-generic 5.11.0-41.45~20.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.11.0-41-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1952925 Title: package linux-modules-5.11.0-41-generic 5.11.0-41.45~20.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- modules-5.11.0-41-generic.list-new': Operation not permitted Status in linux-hwe-5.11 package in Ubuntu: New Bug description: This happens on an upgrade of system software. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.11.0-41-generic 5.11.0-41.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 30 06:35:15 2021 DpkgTerminalLog: Preparing to unpack .../0-linux-modules-5.11.0-41-generic_5.11.0-41.45~20.04.1_amd64.deb ... Unpacking linux-modules-5.11.0-41-generic (5.11.0-41.45~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-S0NIdl/0-linux-modules-5.11.0-41-generic_5.11.0-41.45~20.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.11.0-41-generic.list-new': Operation not permitted DuplicateSignature: package:linux-modules-5.11.0-41-generic:5.11.0-41.45~20.04.1 Unpacking linux-modules-5.11.0-41-generic (5.11.0-41.45~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-S0NIdl/0-linux-modules-5.11.0-41-generic_5.11.0-41.45~20.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.11.0-41-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-5.11.0-41-generic.list-new': Operation not permitted InstallationDate: Installed on 2021-09-03 (89 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-modules-5.11.0-41-generic 5.11.0-41.45~20.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.11.0-41-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1952925/+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 1952922] [NEW] package linux-modules-nvidia-470-5.11.0-41-generic 5.11.0-41.45+2 failed to install/upgrade: installed linux-modules-nvidia-470-5.11.0-41-generic package post-ins
Public bug reported: - ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-modules-nvidia-470-5.11.0-41-generic 5.11.0-41.45+2 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Dec 1 15:19:53 2021 ErrorMessage: installed linux-modules-nvidia-470-5.11.0-41-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-12-01 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-470-5.11.0-41-generic 5.11.0-41.45+2 failed to install/upgrade: installed linux-modules-nvidia-470-5.11.0-41-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute need-duplicate-check third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1952922 Title: package linux-modules-nvidia-470-5.11.0-41-generic 5.11.0-41.45+2 failed to install/upgrade: installed linux-modules- nvidia-470-5.11.0-41-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules package in Ubuntu: New Bug description: - ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-modules-nvidia-470-5.11.0-41-generic 5.11.0-41.45+2 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Dec 1 15:19:53 2021 ErrorMessage: installed linux-modules-nvidia-470-5.11.0-41-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-12-01 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-470-5.11.0-41-generic 5.11.0-41.45+2 failed to install/upgrade: installed linux-modules-nvidia-470-5.11.0-41-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1952922/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
After doing some deeper reading I've come across this bug via the DisplayLink GitHub Repo. As a developer, I recognize that this isn't really the responsiblity of the Canonical Ltd. to hunt down issues that don't relate back to the Core OS - to an extent - so it's not really THEIR fault that an unexpected side-effect was introduced in XServer. That being said, DisplayLink and their "external graphics card" platform powers an overwhelming majority of Home and Office Docking Stations, Conference Rooms, Backpack Adapters, etc. Ultimately frustrated end-users who don't care to dig deep into what the true issue is (including software developers) will give up and just blame Ubuntu and revert to the excuse "Linux is unstable and not a daily operating system" I personally think this is a bad look for Canonical and Ubuntu and will cause a loss in market share due to reduced confidence in the stability of the platform. Basically what I'm saying is - things like this that are glaringly obvious to end-users from the frontend perspective absolutely need to be prioritized and I hope that someone sees this and attempts to get this bug ultimately closed out. This bug has been open since 2020-04-25. I am writing this comment as of 2021-12-01. The bug located over at XServer looks to be closed as of 2020-5-29 - though it's unclear to me if it's completely merged into main. The two teams need to come together and figure this out because like I said previously - this is an extremely bad look from an end-user perspective and just adds to the invalid argument used for years that people use to complain about Linux instability. My Comment on DisplayLink GitHub: - https://github.com/DisplayLink/evdi/issues/61#issuecomment-983603462 - I am on a FRESH install of Ubuntu 20.04 as of October 6th 2021 that I updated many times before actually jumping into using it. - Reference - I started a new job that day and needed to jump into using Linux full time for the type of Software Development work I'd be doing - naturally I've used DisplayLink adapters flawlessly for years (on Windows) so it came as a shock to me that something so glaringly obvious is a problem in a major distribution like Ubuntu. XServer Bug Tracker (Closed): - https://gitlab.freedesktop.org/xorg/xserver/-/issues/1028 ** Bug watch added: github.com/DisplayLink/evdi/issues #61 https://github.com/DisplayLink/evdi/issues/61 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1944080] Re: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error
** Changed in: juju Milestone: 2.9.21 => 2.9.22 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1944080 Title: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error Status in OpenStack RabbitMQ Server Charm: New Status in juju: In Progress Status in ubuntu-fan package in Ubuntu: New Bug description: Hi, Using manual provider on top of VMWare. Juju: 2.9.14 VM: Focal Containers: Bionic I've noticed that, in a given Focal host, 2x Bionic containers may have different behavior: one successfully completes cloud-init whereas the other fails. The failed container errors at "apt update" in cloud- init with: Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease Something wicked happened resolving 'PROXY_IP:' (-9 - Address family for hostname not supported) (Likely this is the line where it breaks: https://github.com/Debian/apt/blob/766b24b7f7484751950c76bc66d3d6cdeaf949a5/methods/connect.cc#L436) Failed container, full cloud-init-output.log: https://pastebin.canonical.com/p/hKNw49mvJP/ Successful container, full cloud-init-output.log: https://pastebin.canonical.com/p/P6MZdQPrWd/ Host syslog: https://pastebin.canonical.com/p/jjMmWRFd9y/ I can see that, on the host, dnsmasq served the FAN IP to the broken container after the "apt-update" was called. - FAILED CONTAINER -: Sep 19 13:02:14 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 252.252.15.198 00:16:3e:da:dd:c4 apt-update on cloud-init was ran: Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at Sun, 19 Sep 2021 13:02:13 +. Up 3.90 seconds. - SUCCESSFUL CONTAINER -: Sep 19 13:09:40 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 252.252.15.253 00:16:3e:d7:6b:ef apt-update on cloud-init was ran: Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at Sun, 19 Sep 2021 13:10:10 +. Up 35.99 seconds. In the case of the Failed Container, the DHCPOFFER arrived 1s after the "apt update" was requested, whereas the Successful Container logged a DHCPOFFER 30s before the "apt update". To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1944080/+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 1952836] Status changed to Confirmed
This change was made by a bot. ** 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/1952836 Title: Suspend not working after update to Linux 5.13.0-22 Status in linux package in Ubuntu: Confirmed Bug description: I use suspend frequently, but after the last update of Linux, the restart fails. However it seems to work partly since the disk activity light is showing activities, but the screen remains black and without power. I have to power off the system by pressing the power-off button for 10 seconds. I suspended the system at 1:35 and I will include the /var/log/kern.log I hope it helps. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 01:41:18 2021 InstallationDate: Installed on 2021-10-09 (52 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-10-14 (47 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952836/+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 1952836] Re: Suspend not working after update to Linux 5.13.0-22
The release-upgrade to 21.10 occurred 47 days ago, so your issue (filed against the release-upgrader tool that moved you to 21.10 from 21.04) is unlikely the issue, it's more likely related to a kernel upgrade. ** 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/1952836 Title: Suspend not working after update to Linux 5.13.0-22 Status in linux package in Ubuntu: New Bug description: I use suspend frequently, but after the last update of Linux, the restart fails. However it seems to work partly since the disk activity light is showing activities, but the screen remains black and without power. I have to power off the system by pressing the power-off button for 10 seconds. I suspended the system at 1:35 and I will include the /var/log/kern.log I hope it helps. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 01:41:18 2021 InstallationDate: Installed on 2021-10-09 (52 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-10-14 (47 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952836/+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 1952836] [NEW] Suspend not working after update to Linux 5.13.0-22
You have been subscribed to a public bug: I use suspend frequently, but after the last update of Linux, the restart fails. However it seems to work partly since the disk activity light is showing activities, but the screen remains black and without power. I have to power off the system by pressing the power-off button for 10 seconds. I suspended the system at 1:35 and I will include the /var/log/kern.log I hope it helps. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 01:41:18 2021 InstallationDate: Installed on 2021-10-09 (52 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-10-14 (47 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade impish third-party-packages wayland-session -- Suspend not working after update to Linux 5.13.0-22 https://bugs.launchpad.net/bugs/1952836 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 1952385] Re: Fix missing external headset after resume problem for Cirrus CS8409 sound driver
New mail from Cirrus Logic: Hi Canonical / Dell team: We have an update on Ubuntu S3 resume issue. Here is the explanation of the update. We have to re-open this issue as the patch was rejected by the maintainer. However we have another patch, that will fix an issue and it was proposed by the maintainer, implemented, and submitted to mainline. This patch has also been merged by upstream. We need to communicate to the customer that for the next kernel ODM build they have to revert the previous patch and apply a new one: https://patchwork.kernel.org/project/alsa- devel/patch/20211128115558.71683-1-vita...@opensource.cirrus.com/ Thanks, Vitaly Short summary: If the OEM kernel is already code freezed, that’s fine and forget about the new patch. If the OEM kernel is NOT yet code- freezed, you might want to consider reverting the current patch (https://patchwork.kernel.org/project/alsa- devel/patch/20211124181908.50672-1-vita...@opensource.cirrus.com/ ) and apply the new patch ( https://patchwork.kernel.org/project/alsa- devel/patch/20211128115558.71683-1-vita...@opensource.cirrus.com/ ). Thank you, JiaBang -- 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/1952385 Title: Fix missing external headset after resume problem for Cirrus CS8409 sound driver Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in linux-oem-5.13 source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: New Bug description: [SRU Justification] [Impact] On some platforms with Cirrus CS8409 audio codec, the external headset will fail to be detected after system resume. [Fix] Cirrus released a fix and send it upstream for approval. It's trying to schedule a harmless delayed work to do jack detection to reflect the real power state after resume. [Test] Plug-in an external headset in front headset port, suspend/resume the system then check whether the headset function works as expected. [Where problem could occur] Low. It only affect the platforms with Cirrus codec CS8409 which used to have problem. == Original Bug Description == [Summary] System can't detect external headset after suspend [Steps to reproduce] 1. install manifest and boot into OS 2. plug-in an external headset in front headset port 3. un-plug external headset 4. suspend system 5. resume system from suspend 6. plug-in an external headset [Expected result] System could detect external headset after suspend [Actual result] System can't detect external headset after suspend [Failure rate] 3/3 [Additional information] CID: 202110-29567 SKU: DLPV-SFF-DVT-C1 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152 system-manufacturer: Dell Inc. system-product-name: Vostro 3710 bios-version: 0.13.73 CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4680] (rev 0c) kernel-version: 5.13.0-1019-oem [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952385/+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 1946229] Re: ZTE Modem USB stick not recognized
Tested again with Linux ubuntu-dev 5.11.0-41-generic #45-Ubuntu SMP Fri Nov 5 11:37:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Now it's working fine. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1946229 Title: ZTE Modem USB stick not recognized Status in linux package in Ubuntu: Invalid Bug description: ~$ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 Linux ubuntu-dev 5.11.0-37-generic #41-Ubuntu SMP Mon Sep 20 16:39:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ZTE Modem USB stick is not recognized. Fails with 'rejecting I/O to dead device' error. [qua out 6 09:47:20 2021] usb 1-3: new high-speed USB device number 19 using xhci_hcd [qua out 6 09:47:20 2021] usb 1-3: New USB device found, idVendor=19d2, idProduct=1588, bcdDevice= 0.00 [qua out 6 09:47:20 2021] usb 1-3: New USB device strings: Mfr=2, Product=3, SerialNumber=5 [qua out 6 09:47:20 2021] usb 1-3: Product: ZTE Mobile Broadband Station [qua out 6 09:47:20 2021] usb 1-3: Manufacturer: ZTE,Incorporated [qua out 6 09:47:20 2021] usb 1-3: SerialNumber: 1234567890ABCDEF [qua out 6 09:47:20 2021] usb-storage 1-3:1.0: USB Mass Storage device detected [qua out 6 09:47:20 2021] scsi host4: usb-storage 1-3:1.0 [qua out 6 09:47:21 2021] usb 1-3: USB disconnect, device number 19 [qua out 6 09:47:21 2021] usb 1-3: new high-speed USB device number 20 using xhci_hcd [qua out 6 09:47:22 2021] usb 1-3: New USB device found, idVendor=19d2, idProduct=1589, bcdDevice= 0.00 [qua out 6 09:47:22 2021] usb 1-3: New USB device strings: Mfr=10, Product=11, SerialNumber=13 [qua out 6 09:47:22 2021] usb 1-3: Product: ZTE Mobile Broadband Station [qua out 6 09:47:22 2021] usb 1-3: Manufacturer: ZTE,Incorporated [qua out 6 09:47:22 2021] usb 1-3: SerialNumber: 1234567890ABCDEF [qua out 6 09:47:22 2021] cdc_ether 1-3:1.0 usb0: register 'cdc_ether' at usb-:00:14.0-3, ZTE CDC Ethernet Device, 06:df:4b:52:02:fd [qua out 6 09:47:22 2021] option 1-3:1.2: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0 [qua out 6 09:47:22 2021] option 1-3:1.3: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB1 [qua out 6 09:47:22 2021] option 1-3:1.4: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB2 [qua out 6 09:47:22 2021] option 1-3:1.5: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB3 [qua out 6 09:47:22 2021] usb-storage 1-3:1.6: USB Mass Storage device detected [qua out 6 09:47:22 2021] scsi host4: usb-storage 1-3:1.6 [qua out 6 09:47:23 2021] scsi 4:0:0:0: CD-ROMZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0 CCS [qua out 6 09:47:23 2021] scsi 4:0:0:1: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 0 CCS [qua out 6 09:47:23 2021] sr 4:0:0:0: [sr0] scsi3-mmc drive: 0x/0x caddy [qua out 6 09:47:59 2021] sr 4:0:0:0: Attached scsi CD-ROM sr0 [qua out 6 09:47:59 2021] sr 4:0:0:0: Attached scsi generic sg4 type 5 [qua out 6 09:47:59 2021] sd 4:0:0:1: Attached scsi generic sg5 type 0 [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] 0 512-byte logical blocks: (0 B/0 B) [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] 0-byte physical blocks [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Test WP failed, assume Write Enabled [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Asking for cache data failed [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Assuming drive cache: write through [qua out 6 09:48:04 2021] usb 1-3: USB disconnect, device number 20 [qua out 6 09:48:04 2021] cdc_ether 1-3:1.0 usb0: unregister 'cdc_ether' usb-:00:14.0-3, ZTE CDC Ethernet Device [qua out 6 09:48:04 2021] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 [qua out 6 09:48:04 2021] option 1-3:1.2: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1 [qua out 6 09:48:04 2021] option 1-3:1.3: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2 [qua out 6 09:48:04 2021] option 1-3:1.4: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3 [qua out 6 09:48:04 2021] option 1-3:1.5: device disconnected [qua out 6 09:48:04 2021] sd 4:0:0:1: [sdd] Attached SCSI removable disk [qua out 6 09:48:04 2021] scsi 4:0:0:0: rejecting I/O to dead device --- ProblemType: Bug ApportVersion:
[Kernel-packages] [Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
I've just 'extracted' the v5 patch set from the upstream mailing-list and attach it here. (builds are ongoing ...) ** Attachment added: "v5 patch set" https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+attachment/5544611/+files/v5-integrity-support-including-firmware-platform-keys-at-build-time.tar.xz -- 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/1903288 Title: Power guest secure boot with static keys: kernel portion Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #2 - Daniel John Axtens - 2020-11-05 20:15:10 == This is the kernel side of changes needed for LPAR/guest secure boot. Because Ubuntu keeps its kernels so wonderfully up to date, I don't think there are any extra patches you need to pick up. (I'll double- check against the 21.04 tree once my git pulls finish!) However, we potentially need some configuration changes to make sure kexec-ing into a crashdump kernel still works. Because Lockdown requires that kexec kernels are signed by a key trusted by IMA, the public key for used for signing the kdump kernel needs to be in the IMA keyring or the platform keyring. For host secure boot (and in the UEFI case), it's loaded into the platform keyring. But in the case of guest secure boot with static keys, it's not loaded into the platform keyring so it needs to be loaded into the IMA keyring. This is easy enough to do. Firstly, load the Secure Boot CA into the .primary_trusted_keys keyring via the CONFIG_SYSTEM_TRUSTED_KEYS property. We assume the key used to sign the kernel is signed by this CA. Then, enable IMA_LOAD_X509, which allows certificates signed by a key on the .primary_trusted_keys keyring to be loaded into the IMA keyring. Then set IMA_X509_PATH to provide a path to the signing key on installed file system. (It may also be possible to do this step in userspace, so long as the CA is trusted by the kernel.) Then that key will be loaded into the .ima keyring at boot and be used to appraise the kexec kernel for crashdumps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+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
