[Kernel-packages] [Bug 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
This is the patch by Alex Deucher that is believed to fix the NULL pointer dereference. I have not tested it but the issue looks very close. It is needed anyway. > Guchun Chen > Regarding the NULL pointer access, it should be duplicated of #2388. And the > fix is "63a9ab264a8c drm/amd/pm/smu7: move variables to where they are used" . ** Patch added: "0001-drm-amd-pm-smu7-move-variables-to-where-they-are-use.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671131/+files/0001-drm-amd-pm-smu7-move-variables-to-where-they-are-use.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not
[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
** No longer affects: zsys (Ubuntu) ** No longer affects: systemd (Ubuntu) ** No longer affects: snapd (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in ubiquity source package in Jammy: Fix Released Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. [Testcase] tl;dr encrypted-zfs, firstboot, `systemctl daemon-reload` must not unmount half of mountpoints, ie. /var/lib. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. [End Testcase] Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+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 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
I've reported the issues upstream on drm side: - https://gitlab.freedesktop.org/drm/amd/-/issues/2540 Linux 5.19 amdgpu: NULL pointer on GCN2 (R9 390X Hawaii/Grenada) - https://gitlab.freedesktop.org/drm/amd/-/issues/2541 Linux 5.19 amdgpu: invalid load on GCN1 (R7 240 Oland) For the NULL pointer dereference, it looks like there is a patch there: - https://gitlab.freedesktop.org/drm/amd/-/issues/2388 https://gitlab.freedesktop.org/drm/amd/uploads/a004996ac0c868dfb032af3c35f7b2c6/0001-drm-amd-pm-smu7-move-variables-to-where-they-are-use.patch I have not tested the patch myself, but the bug this patch fixes looks very similar. ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2540 https://gitlab.freedesktop.org/drm/amd/-/issues/2540 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2541 https://gitlab.freedesktop.org/drm/amd/-/issues/2541 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2388 https://gitlab.freedesktop.org/drm/amd/-/issues/2388 -- 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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display
[Kernel-packages] [Bug 2009289] Re: 22.04 suspend not properly working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009289 Title: 22.04 suspend not properly working Status in linux package in Ubuntu: Expired Bug description: very similar to:+Ubuntu 22.04 suspend improper working but happens always To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009289/+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 1967858] Re: Make arch specific linux-firmware
On Thu, 4 May 2023, 22:35 Mantas Kriaučiūnas, <1967...@bugs.launchpad.net> wrote: > @juergh maybe it would be better simply reuse debian packaging practice > for linux-firmware? Please also look at LP bug #1958518 - this issue is > solved in Debian a long time ago: > > metapackage https://packages.debian.org/sid/firmware-linux depends on > small firmware-linux-free package and firmware-linux-nonfree metapackage > Ubuntu and Debian have different licensing and distribution requirements of what goes into free/nonfree/any. metapackage https://packages.debian.org/sid/firmware-linux-nonfree > depends on most useful "nonfree" firmware, including this pretty > firmware-misc-nonfree package (takes only ~40 MB after installation, > instead of ~900MB sized of Ubuntu's linux-firmware): > https://packages.debian.org/sid/firmware-misc-nonfree > > For example netronome network adapters firmware is packaged separately > in Debian, see https://packages.debian.org/sid/firmware-netronome For many reasons in Debian firmwares are split into multiple source packages which in Ubuntu we do not want for operational reasons. Also in Ubuntu, unlike in Debian, we have support for additional hardware detection and package installation via ubuntu-drivers. > Someone from Ubuntu developers decided simply put all useful and almost > not used firmware into huge package, which is updated very often and > this causes a lot of problems for users, especially who uses SSD storage > or slow internet connection :( > > For example see bug #1972806 - simple change of some device firmware > (few kilobytes size) requires to download ~250MB linux-firmware package > for *every* Ubuntu user. This is a nonsense and waste of bandwidth and > other resources. > There are many optimisations we can do on that front that are orthogonal to this. Adopting Debian packaging split is not enough for us, and thus if we are doing work to split things we need it to be done the most optimal way that will serve all our current needs and the future ones. Just adopting Debian splits will improve things a little for us, but also regress many of our usecases which will break our users. No silver bullet so far. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1967858 Title: Make arch specific linux-firmware Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Mantic: In Progress Bug description: There are many kernel modules that only exist on some architectures. Yet linux-firmware is an arch:all package that ships firmware for all drivers, for all architectures. For example, it is pointless to ship many Intel firmware on non-x86 machines. At the same time it is pointless to ship many Qualcomm firmware on non-arm machines. Or shipping nvidia firmware on architectures that have no Nvidia drivers. Or shipping wifi firmware on IBM Z / PowerPC. It seems like we should build-depend on linux / linux-oem kernels and only install relevant firmware files on relevant architectures only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1967858/+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 1967858] Re: Make arch specific linux-firmware
@juergh maybe it would be better simply reuse debian packaging practice for linux-firmware? Please also look at LP bug #1958518 - this issue is solved in Debian a long time ago: metapackage https://packages.debian.org/sid/firmware-linux depends on small firmware-linux-free package and firmware-linux-nonfree metapackage metapackage https://packages.debian.org/sid/firmware-linux-nonfree depends on most useful "nonfree" firmware, including this pretty firmware-misc-nonfree package (takes only ~40 MB after installation, instead of ~900MB sized of Ubuntu's linux-firmware): https://packages.debian.org/sid/firmware-misc-nonfree For example netronome network adapters firmware is packaged separately in Debian, see https://packages.debian.org/sid/firmware-netronome Someone from Ubuntu developers decided simply put all useful and almost not used firmware into huge package, which is updated very often and this causes a lot of problems for users, especially who uses SSD storage or slow internet connection :( For example see bug #1972806 - simple change of some device firmware (few kilobytes size) requires to download ~250MB linux-firmware package for *every* Ubuntu user. This is a nonsense and waste of bandwidth and other resources. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1967858 Title: Make arch specific linux-firmware Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Mantic: In Progress Bug description: There are many kernel modules that only exist on some architectures. Yet linux-firmware is an arch:all package that ships firmware for all drivers, for all architectures. For example, it is pointless to ship many Intel firmware on non-x86 machines. At the same time it is pointless to ship many Qualcomm firmware on non-arm machines. Or shipping nvidia firmware on architectures that have no Nvidia drivers. Or shipping wifi firmware on IBM Z / PowerPC. It seems like we should build-depend on linux / linux-oem kernels and only install relevant firmware files on relevant architectures only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1967858/+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 1930783] Re: integrity: Problem loading X.509 certificate
Also affects Ideapad 3 15AB7 Ryzen 5825. Kubuntu 23.10 for all Kernels up to linux-next. In all cases, secure boot on or off, MoK enabled or not and fTPM on/off give the same result. fTPM reading is abnormal. $ sudo dmesg | grep fTPM [0.341408] tpm tpm0: AMD fTPM version 0x3004e00020005 causes system stutter; hwrng disabled $ mokutil --sb SecureBoot enabled SecureBoot validation is disabled in shim mokutil --sb SecureBoot disabled sudo dmesg | grep fTPM no reading Here's the x.509 error: $ journalctl -b -1 ...cut here... -X.509 Boot/restart/all Kernels/all cases 23:51:34 mm systemd[1]: Stopped user-runtime-dir@1000.service - User Runtime Directory /run/user/1000. May 03 23:51:34 mm systemd[1]: Removed slice user-1000.slice - User Slice of UID 1000. May 03 23:51:19 mm kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v1): a8d54bbb3825cfb94fa13c9f8a594a195c107b8d' May 03 23:51:19 mm kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v2): 4cf046892d6fd3c9a5b03f98d845f90851dc6a8c' May 03 23:51:19 mm kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v3): 100437bb6de6e469b581e61cd66bce3ef4ed53af' May 03 23:51:19 mm kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (Ubuntu Core 2019): c1d57b8f6b743f23ee41f4f7ee292f06eecadfb9' May 03 23:51:19 mm kernel: zswap: loaded using pool lzo/zbud May 03 23:51:19 mm kernel: Key type .fscrypt registered May 03 23:51:19 mm kernel: Key type fscrypt-provisioning registered May 03 23:51:19 mm kernel: Key type trusted registered May 03 23:51:19 mm kernel: Key type encrypted registered May 03 23:51:19 mm kernel: AppArmor: AppArmor sha1 policy hashing enabled May 03 23:51:19 mm kernel: integrity: Loading X.509 certificate: UEFI:db May 03 23:51:19 mm kernel: integrity: Loaded X.509 cert 'Lenovo UEFI CA 2014: 4b91a68732eaefdd2c8c6b027ec3449e9c8f' May 03 23:51:19 mm kernel: integrity: Loading X.509 certificate: UEFI:db May 03 23:51:19 mm kernel: integrity: Problem loading X.509 certificate -65 May 03 23:51:19 mm kernel: fbcon: Taking over console May 03 23:51:19 mm kernel: integrity: Error adding keys to platform keyring UEFI:db May 03 23:51:19 mm kernel: integrity: Loading X.509 certificate: UEFI:db May 03 23:51:19 mm kernel: Console: switching to colour frame buffer device 240x67 May 03 23:51:19 mm kernel: integrity: Loaded X.509 cert ': 8129c1e0865297b1435ad4a47e4f424e' May 03 23:51:19 mm kernel: integrity: Loading X.509 certificate: UEFI:db May 03 23:51:19 mm kernel: blacklist: Loading compiled-in revocation X.509 certificates May 03 23:51:19 mm kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0' May 03 23:51:19 mm kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2017): 242ade75ac4a15e50d50c84b0d45ff3eae707a03' May 03 23:51:19 mm kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (ESM 2018): 365188c1d374d6b07c3c8f240f8ef722433d6a8b' May 03 23:51:19 mm kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2019): c0746fd6c5da3ae827864651ad66ae47fe24b3e8' May 03 23:51:19 mm kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v1): a8d54bbb3825cfb94fa13c9f8a594a195c107b8d' May 03 23:51:19 mm kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v2): 4cf046892d6fd3c9a5b03f98d845f90851dc6a8c' May 03 23:51:19 mm kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v3): 100437bb6de6e469b581e61cd66bce3ef4ed53af' May 03 23:51:19 mm kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (Ubuntu Core 2019): c1d57b8f6b743f23ee41f4f7ee292f06eecadfb9' May 03 23:51:19 mm kernel: zswap: loaded using pool lzo/zbud May 03 23:51:19 mm kernel: Key type .fscrypt registered May 03 23:51:19 mm kernel: Key type fscrypt-provisioning registered May 03 23:51:19 mm kernel: Key type trusted registered May 03 23:51:19 mm kernel: Key type encrypted registered May 03 23:51:19 mm kernel: AppArmor: AppArmor sha1 policy hashing enabled May 03 23:51:19 mm kernel: integrity: Loading X.509 certificate: UEFI:db May 03 23:51:19 mm kernel: integrity: Loaded X.509 cert 'Lenovo UEFI CA 2014: 4b91a68732eaefdd2c8c6b027ec3449e9c8f' May 03 23:51:19 mm kernel: integrity: Loading X.509 certificate: UEFI:db May 03 23:51:19 mm kernel: integrity: Problem loading X.509 certificate -65 May 03 23:51:19 mm kernel: fbcon: Taking over console May 03 23:51:19 mm kernel: integrity: Error adding keys to platform keyring UEFI:db May 03 23:51:19 mm kernel: integrity: Loading X.509 certificate: UEFI:db May 03 23:51:19 mm kernel: Console: switching to colour frame buffer device 240x67 May 03 23:51:19 mm kernel: Loading compiled-in X.509 certificates May 03 23:51:19 mm kernel: Loaded X.509 cert 'Build time autogenerated kernel key: 1fc0e865c21818e2f5cce3868a567b58070b6c0d' May 03 23:51:19 mm kernel: Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' May 03
[Kernel-packages] [Bug 2018520] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
Additional background info; This is an installation on a MACBook PRO M1 running in Parallels. -- 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/2018520 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: Was updating from 22.10 to 23.04 and error came during upgrade. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parallels 1265 F wireplumber /dev/snd/seq:parallels 1262 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu May 4 09:22:34 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-07 (300 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release arm64 (20220421) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=5a14ccf7-6bac-47b7-a3d6-6c10822fb10d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-04 (0 days ago) acpidump: dmi.bios.date: Mon, 27 Mar 2023 17:35:19 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 1.8.2 (23832) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr1.8.2(23832):bdMon,27Mar2023173519:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018520/+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 2017929] Re: Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs)
Also confirm that 5.15.0-70 boots fine, -71 stops with above error. sudo inxi -v 2 System: Host: *** Kernel: 5.15.0-70-generic x86_64 bits: 64 Desktop: GNOME 42.5 Distro: Ubuntu 22.04.2 LTS (Jammy Jellyfish) Machine: Type: Desktop System: Micro-Star product: MS-7B09 v: 1.0 serial: N/A Mobo: Micro-Star model: X399 GAMING PRO CARBON AC (MS-7B09) v: 1.0 serial: I316363281 UEFI: American Megatrends v: 1.C0 date: 11/14/2018 CPU: Info: 8-core AMD Ryzen Threadripper 2950X [MT MCP MCM] speed (MHz): avg: 2300 min/max: 2200/3500 -- 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/2017929 Title: Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 5.15.0-71 a couple of days ago, my PC sporadically fails to boot. I see the following error messages: "error: cannot allocate kernel buffer error: you need to load the kernel first. Press any key to continue..._ " I am then returned to the GRUB boot menu. This has also been experienced by two other AskUbuntu users: https://askubuntu.com/questions/1465460/after-kernel-update-error- cannot-allocate-kernel-buffer-you-need-to-load-kern . The common theme appears to be Ryzen APUs; two of us have 3400Gs and one has a 7600. In my case, the issue appears to be more likely to occur when I have to force-reboot because the system is frozen (due to a separate bug which I will link when I can find it again). But I have not yet reproduced it. Also the log files attached to this report may not contain relevant information as the last couple of boots worked correctly. I will try to capture a relevant kernel log now that I know this is a kernel issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-71-generic 5.15.0-71.78 ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92 Uname: Linux 5.15.0-71-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matthew1288 F pulseaudio /dev/snd/controlC0: matthew1288 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 17:49:11 2023 InstallationDate: Installed on 2022-01-14 (467 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-71-generic root=UUID=7348d288-7351-45cd-8da2-592c59a4f7dd ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-71-generic N/A linux-backports-modules-5.15.0-71-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-26 (336 days ago) dmi.bios.date: 09/28/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.E3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.E3:bd09/28/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017929/+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 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
** Summary changed: - Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 + Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 -- 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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic 5.19.0.42.38 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname:
[Kernel-packages] [Bug 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2
So to summarize: with Linux 5.19.0-42-generic amdgpu on GCN1: kernel NULL pointer dereference - no display - stuck boot requiring SysRq+K to continue - errors in dmesg - reboot requiring SysRq+B to continue with Linux 5.19.0-42-generic amdgpu on CGN2: kernel UBSAN invalid load, load of value 8 is not a valid value for type '_Bool' - no display - errors in dmesg Both GCN1 and GCN2 devices work with older revisions of the 5.19.0 kernel I haven't reproduce the btrfs issue with Linux 5.19.0-42-generic so I'll ignore that issue and consider it fixed. The amdgpu regression is still there and strongly breaking the usability of Ubuntu. ** Summary changed: - Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable + Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 -- 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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-amdgpu.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671007/+files/dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-amdgpu.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
-- 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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic 5.19.0.42.38 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
** Attachment added: "dmesg.linux-5.19.0-23-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671008/+files/dmesg.linux-5.19.0-23-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package:
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-radeon.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671001/+files/dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-radeon.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-radeon.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671000/+files/dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-radeon.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5670998/+files/dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package:
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5670999/+files/dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
So, in the end I spent some times to do more dmesg logs, just producing 6 of them took me multiple hours because of how slow such kind of computer BIOS is to boot, and also because of how complicated it can be to get a shell when everything goes wrong with those bugs. Something I forgot to mention is that when I get the graphic bug when the system tries to switch from low resolution to high resolution, the system hang, and I can unstuck it by doing SysRq+K. After that the boot continues while the display remains broken, and X11 never starts. When I reboot, it stops the reboot sequence after displaying “Reached target System Reboot”, but never reboots by itself, I then have to do SysRq+B to actually reboot. I totally purged rocm, amdgpu-pro and oneapi stuff to do those tests. It happens that radeon driver works with Linux 5.19.0-42-generic if I use it with both GCN1 R7 240 Oland and GCN2 R9 390X Grenada. As soon as amdgpu is used, the display breaks. amdgpu is required for Vulkan and OpenCL with Orca. It looks like what hangs many things is running amdgpu on GCN1, while amdgpu on GCN1 may only break the display given the version but don't stuck other things. So, here are the 6 logs: ## dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt status: ❌️ broken display ❌️ boot and reboot stuck ❌️ null pointer error in dmesg Linux: 5.19.0-42-generic AMD R7 240 Oland: amdgpu driver AMD R9 R90X Grenada: amdgpu driver cmdline: amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1 amdgpu.ppfeaturemask=0x extra: some extra amdgpu kernel option used symptoms: - no display - stuck boot requiring SysRq+K to continue - errors in dmesg - reboot requiring SysRq+B to continue/ dmesg quote: ``` [5.844957] BUG: kernel NULL pointer dereference, address: [5.845594] #PF: supervisor read access in kernel mode [5.846002] #PF: error_code(0x) - not-present page [5.846362] PGD 0 P4D 0 [5.846697] Oops: [#1] PREEMPT SMP NOPTI [5.847039] CPU: 3 PID: 365 Comm: systemd-udevd Tainted: G OE 5.19.0-42-generic #43-Ubuntu [5.847381] Hardware name: Default string Default string/Default string, BIOS WRX80PRO-F1 08/04/2022 [5.847723] RIP: 0010:smu7_enable_dpm_tasks+0xbdf/0x3280 [amdgpu] [5.848289] Code: 48 8b 83 a0 01 00 00 c6 80 c8 08 00 00 01 4c 8b ab a0 01 00 00 48 8b 83 f8 00 00 00 4c 8b b3 c0 01 00 00 45 8b a5 bc 02 00 00 <4c> 8b 38 41 83 fc 01 0f 84 2e 0b 00 00 41 8b 85 58 02 00 00 83 e8 [5.849015] RSP: 0018:ac30ca967888 EFLAGS: 00010246 [5.849378] RAX: RBX: 9caec3fe6400 RCX: [5.849738] RDX: RSI: RDI: [5.850092] RBP: ac30ca967910 R08: R09: [5.850442] R10: R11: R12: 0002 [5.850787] R13: 9caec71a8000 R14: 9caedc32b240 R15: 0005 [5.851135] FS: 7f45497e88c0() GS:9cecdd2c() knlGS: [5.851487] CS: 0010 DS: ES: CR0: 80050033 [5.851839] CR2: CR3: 00013b2f CR4: 00350ee0 [5.852202] Call Trace: [5.852554] [5.852902] ? cik_smc_rreg+0x56/0x70 [amdgpu] [5.853421] phm_enable_dynamic_state_management+0x54/0xc0 [amdgpu] [5.853973] hwmgr_hw_init+0x179/0x1b0 [amdgpu] [5.854520] pp_hw_init+0x16/0x30 [amdgpu] [5.855079] amdgpu_device_init.cold+0x1e4e/0x202f [amdgpu] [5.855649] amdgpu_driver_load_kms+0x1a/0x160 [amdgpu] [5.856157] amdgpu_pci_probe+0x179/0x3a0 [amdgpu] [5.856662] local_pci_probe+0x47/0x90 [5.857013] pci_call_probe+0x55/0x190 [5.857363] pci_device_probe+0x84/0x120 [5.857710] really_probe+0x1df/0x3b0 [5.858056] __driver_probe_device+0x12c/0x1b0 [5.858397] driver_probe_device+0x24/0xd0 [5.858733] __driver_attach+0x10b/0x210 [5.859063] ? __device_attach_driver+0x170/0x170 [5.859382] bus_for_each_dev+0x90/0xe0 [5.859692] driver_attach+0x1e/0x30 [5.86] bus_add_driver+0x187/0x230 [5.860309] driver_register+0x8f/0x100 [5.860620] __pci_register_driver+0x62/0x70 [5.860932] amdgpu_init+0x95/0x1000 [amdgpu] [5.861413] ? 0xc0776000 [5.861729] do_one_initcall+0x5e/0x240 [5.862049] do_init_module+0x50/0x210 [5.862368] load_module+0xb7d/0xcd0 [5.862689] __do_sys_finit_module+0xc4/0x140 [5.863009] ? __do_sys_finit_module+0xc4/0x140 [5.863327] __x64_sys_finit_module+0x18/0x30 [5.863644] do_syscall_64+0x5b/0x90 [5.863958] ? do_syscall_64+0x67/0x90 [5.864267] ? do_syscall_64+0x67/0x90 [5.864569] entry_SYSCALL_64_after_hwframe+0x63/0xcd [5.864870] RIP: 0033:0x7f4549ec9c4d [5.865171] Code: 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89
[Kernel-packages] [Bug 2018226] Re: autoinstall fails despite BUILD_EXCLUSIVE
** Also affects: dkms (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: dkms (Ubuntu Lunar) Status: New => Confirmed ** Changed in: dkms (Ubuntu Lunar) Importance: Undecided => High ** Changed in: dkms (Ubuntu Lunar) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2018226 Title: autoinstall fails despite BUILD_EXCLUSIVE Status in dkms package in Ubuntu: Confirmed Status in dkms source package in Lunar: Confirmed Bug description: [Impact] Kernel upgrades fail if DKMS packages are currently installed that include BUILD_EXCLUSIVE directives which skip the DKMS build. In this case, the dkms tool incorrectly returns a non-zero exit status. $ sudo /etc/kernel/postinst.d/dkms 6.2.0-20-generic * dkms: running auto installation service for kernel 6.2.0-20-generic Deprecated feature: REMAKE_INITRD (/var/lib/dkms/oem-ethernet-r8169-aspm-support-bionic/4/source/dkms.conf) Deprecated feature: REMAKE_INITRD (/etc/dkms/framework.conf) Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Deprecated feature: REMAKE_INITRD (/var/lib/dkms/oem-ethernet-r8169-aspm-support-bionic/4/source/dkms.conf) Error! The /var/lib/dkms/oem-ethernet-r8169-aspm-support-bionic/4/6.2.0-20-generic/x86_64/dkms.conf for module oem-ethernet-r8169-aspm-support-bionic includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. This indicates that it should not be built. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. [fail] [Test Plan] Install such a DKMS (like [1]), and run: $ sudo /etc/kernel/postinst.d/dkms $(uname -r) This command should return with exit status '0'. [1] http://oem.archive.canonical.com/updates/pool/public/o/oem- ethernet-r8169-aspm-support-bionic-dkms/ [Where problems could occur] This fix changes how DKMS status/results are handled during autoinstall. So problems would only show up if DKMS modules are installed and are being processed (for example during a kernel upgrade or installation). Or if the dkms tool is invoked manually. [Other info] The bug was introduced in upstream dkms version 3.0.9 and fixed in 3.0.11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2018226/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
** Also affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Also affects: ubuntu-drivers-common (Ubuntu Mantic) Importance: Undecided Status: Confirmed ** Also affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Lunar) Status: New => Invalid ** Changed in: ubuntu-drivers-common (Ubuntu Lunar) Status: New => Confirmed ** Changed in: ubuntu-drivers-common (Ubuntu Lunar) Milestone: None => lunar-updates ** Changed in: ubuntu-drivers-common (Ubuntu Mantic) Milestone: ubuntu-23.04 => ubuntu-23.10-beta -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Confirmed Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 2018444] 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/2018444 Title: [ASUS X555LAB] Kernel 6.2 touchpad won´t drag and drop (but 5.19 works) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to lunar lobster, I can´t drag and drop with my touchpad - it jumps around uncontrollably. If I reboot to the last version 5.19, it works ok. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Wed May 3 23:33:53 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2020-07-11 (1026 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. USB Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M MachineType: ASUSTeK COMPUTER INC. X555LAB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=70b396bb-907c-46c9-a9da-18fecdb5f2d0 ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.603 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.603:bd04/16/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X555LAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018444/+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 2016065] Re: Internal 'Genesys Logic, Inc. Hub' disconnects from ASUS PN50 during boot
** Tags removed: fixed-upstream -- 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/2016065 Title: Internal 'Genesys Logic, Inc. Hub' disconnects from ASUS PN50 during boot Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 libinput-bin: Installed: 1.22.1-1 Candidate: 1.22.1-1 Version table: *** 1.22.1-1 500 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status linux-image-generic: Installed: 6.2.0.20.20 Candidate: 6.2.0.20.20 Version table: *** 6.2.0.20.20 500 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status After upgrading to the 23.04 beta from 22.10 the system (an ASUS PN-50 mini-PC) became unresponsive to any (USB) keyboard or mouse input. This is still the case when the Ubuntu recovery option is chosen in the boot menu. Different USB keyboards and mice/plugging unplugging etc have no effect. The system boots all the way to the Ubuntu login screen and can be accessed via ssh. When booted into Windows all is still functioning correctly Unclear if this is a libinput problem, or lies elsewhere (kernel?) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libinput-bin 1.22.1-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown Date: Thu Apr 13 09:00:56 2023 DistUpgraded: 2023-04-10 16:30:22,175 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:87e7] InstallationDate: Installed on 2020-11-14 (879 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=4837ff80-a59b-47c0-ae9d-811d54bad076 ro quiet splash vt.handoff=7 SourcePackage: libinput UpgradeStatus: Upgraded to lunar on 2023-04-10 (2 days ago) dmi.bios.date: 07/06/2022 dmi.bios.release: 6.24 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0624 dmi.board.asset.tag: Default string dmi.board.name: PN50 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0624:bd07/06/2022:br6.24:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50:pvr0624:rvnASUSTeKCOMPUTERINC.:rnPN50:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50 dmi.product.version: 0624 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016065/+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 2018226] Re: autoinstall fails despite BUILD_EXCLUSIVE
** Changed in: dkms (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2018226 Title: autoinstall fails despite BUILD_EXCLUSIVE Status in dkms package in Ubuntu: Confirmed Bug description: [Impact] Kernel upgrades fail if DKMS packages are currently installed that include BUILD_EXCLUSIVE directives which skip the DKMS build. In this case, the dkms tool incorrectly returns a non-zero exit status. $ sudo /etc/kernel/postinst.d/dkms 6.2.0-20-generic * dkms: running auto installation service for kernel 6.2.0-20-generic Deprecated feature: REMAKE_INITRD (/var/lib/dkms/oem-ethernet-r8169-aspm-support-bionic/4/source/dkms.conf) Deprecated feature: REMAKE_INITRD (/etc/dkms/framework.conf) Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Deprecated feature: REMAKE_INITRD (/var/lib/dkms/oem-ethernet-r8169-aspm-support-bionic/4/source/dkms.conf) Error! The /var/lib/dkms/oem-ethernet-r8169-aspm-support-bionic/4/6.2.0-20-generic/x86_64/dkms.conf for module oem-ethernet-r8169-aspm-support-bionic includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. This indicates that it should not be built. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. [fail] [Test Plan] Install such a DKMS (like [1]), and run: $ sudo /etc/kernel/postinst.d/dkms $(uname -r) This command should return with exit status '0'. [1] http://oem.archive.canonical.com/updates/pool/public/o/oem- ethernet-r8169-aspm-support-bionic-dkms/ [Where problems could occur] This fix changes how DKMS status/results are handled during autoinstall. So problems would only show up if DKMS modules are installed and are being processed (for example during a kernel upgrade or installation). Or if the dkms tool is invoked manually. [Other info] The bug was introduced in upstream dkms version 3.0.9 and fixed in 3.0.11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2018226/+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 2018520] 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/2018520 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: Was updating from 22.10 to 23.04 and error came during upgrade. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parallels 1265 F wireplumber /dev/snd/seq:parallels 1262 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu May 4 09:22:34 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-07 (300 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release arm64 (20220421) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=5a14ccf7-6bac-47b7-a3d6-6c10822fb10d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-04 (0 days ago) acpidump: dmi.bios.date: Mon, 27 Mar 2023 17:35:19 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 1.8.2 (23832) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr1.8.2(23832):bdMon,27Mar2023173519:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018520/+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 2018520] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
** Tags removed: need-duplicate-check -- 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/2018520 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: Was updating from 22.10 to 23.04 and error came during upgrade. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parallels 1265 F wireplumber /dev/snd/seq:parallels 1262 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu May 4 09:22:34 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-07 (300 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release arm64 (20220421) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=5a14ccf7-6bac-47b7-a3d6-6c10822fb10d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-04 (0 days ago) acpidump: dmi.bios.date: Mon, 27 Mar 2023 17:35:19 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 1.8.2 (23832) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr1.8.2(23832):bdMon,27Mar2023173519:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018520/+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 2018520] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess
Public bug reported: Was updating from 22.10 to 23.04 and error came during upgrade. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parallels 1265 F wireplumber /dev/snd/seq:parallels 1262 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu May 4 09:22:34 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-07 (300 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release arm64 (20220421) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=5a14ccf7-6bac-47b7-a3d6-6c10822fb10d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-04 (0 days ago) acpidump: dmi.bios.date: Mon, 27 Mar 2023 17:35:19 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 1.8.2 (23832) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr1.8.2(23832):bdMon,27Mar2023173519:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-package arm64 lunar -- 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/2018520 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: Was updating from 22.10 to 23.04 and error came during upgrade. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parallels 1265 F wireplumber /dev/snd/seq:parallels 1262 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu May 4 09:22:34 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-07 (300 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release arm64 (20220421) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=5a14ccf7-6bac-47b7-a3d6-6c10822fb10d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
>>Are you stating that I should not apply the Revert patches at all?
Yes, revert patches are not required since the plan is to merge _all_
"path split" patches in Jammy (as part of the provided patchset).
--
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/1988711
Title:
Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
Fix Released
Bug description:
[IMPACT/Justification]
There are numerous bug fixes included in the more recent version of lpfc That
Broadcom has asked to pull into Jammy and Kinetic to better support customers
in the field who are using the GA kernel and cant or wont move to the HWE
kernels. These all are limited to the lpfc driver itself, no patches to core
code are requested.
[FIX]
A few of these were already landed in Jammy, and all but 6 (ones landed in
6.0 upstream) were already in Kinetic.
b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into
lpfc_sli_prep_abort_xri()
ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved
configuration
ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF
WQE
0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in
queuecommand after VMID
35251b4d79db scsi: lpfc: Set PU field when providing D_ID in
XMIT_ELS_RSP64_CX iocb
f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with
malformed user input
4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in
lpfc_nvme_cancel_iocb()
1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for
nvme_admin_async_event cmd completion
ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for
aborted NVMe cmds
336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT
topology
b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is
aborted
6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after
starget_to_rport()
e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path
refactoring
24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path
refactoring
44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in
lpfc_ct_reject_event()
a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol
independent
ed913cf4a533 scsi: lpfc: Commonize VMID code location
fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for
NVMe I/O
e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
5099478e436f scsi: lpfc: Change VMID registration to be based on fabric
parameters
dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if
lpfc_err_lost_link()
4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in
rscn_recovery_check()
596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
92bd903da12b scsi: lpfc: Fix additional reference counting in
lpfc_bsg_rport_els()
db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in
lpfc_sli_prep_wqe()
a346f28ad231 scsi: lpfc: Remove unneeded variable
66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands
d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq data structure
1045592fc968 scsi: lpfc: Introduce FC_RSCN_MEMENTO flag for tracking post
RSCN completion
6c983d327b9e scsi: lpfc: Register for Application Services FC-4 type in
[Kernel-packages] [Bug 2018444] Re: [ASUS X555LAB] Kernel 6.2 touchpad won´t drag and drop (but 5.19 works)
** Summary changed: - Kernel 6.2 touchpad won´t drag and drop + [ASUS X555LAB] Kernel 6.2 touchpad won´t drag and drop (but 5.19 works) ** Package changed: xorg (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/2018444 Title: [ASUS X555LAB] Kernel 6.2 touchpad won´t drag and drop (but 5.19 works) Status in linux package in Ubuntu: New Bug description: After upgrading to lunar lobster, I can´t drag and drop with my touchpad - it jumps around uncontrollably. If I reboot to the last version 5.19, it works ok. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Wed May 3 23:33:53 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2020-07-11 (1026 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. USB Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M MachineType: ASUSTeK COMPUTER INC. X555LAB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=70b396bb-907c-46c9-a9da-18fecdb5f2d0 ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.603 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.603:bd04/16/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X555LAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018444/+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 2008142] Re: bcmwl driver not installed
** Also affects: ubuntu-release-notes/lunar Importance: Undecided Status: New ** Also affects: ubuntu-release-notes/mantic Importance: Undecided Status: New ** Changed in: ubuntu-release-notes/lunar Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to broadcom-sta in Ubuntu. https://bugs.launchpad.net/bugs/2008142 Title: bcmwl driver not installed Status in ubuntu-desktop-installer: Fix Released Status in Release Notes for Ubuntu: New Status in Release Notes for Ubuntu lunar series: Fix Released Status in Release Notes for Ubuntu mantic series: New Status in broadcom-sta package in Ubuntu: Confirmed Status in subiquity package in Ubuntu: Confirmed Status in broadcom-sta source package in Lunar: Confirmed Status in subiquity source package in Lunar: Won't Fix Bug description: I was testing an installation in qemu and shared a broadcom wireless device with the virtual machine and the drivers for it were not installed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-desktop-installer (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 16:23:38 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-desktop-installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2008142/+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 1988806] Re: Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Triaged
** Also affects: linux-hwe-5.19 (Ubuntu Mantic)
Importance: Undecided
Status: Invalid
** Changed in: linux (Ubuntu Mantic)
Milestone: lunar-updates => ubuntu-23.10-beta
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/1988806
Title:
Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
Status in Release Notes for Ubuntu:
New
Status in linux package in Ubuntu:
Triaged
Status in linux-hwe-5.19 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-5.19 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.19 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Triaged
Status in linux-hwe-5.19 source package in Lunar:
Invalid
Status in linux source package in Mantic:
Triaged
Status in linux-hwe-5.19 source package in Mantic:
Invalid
Bug description:
With below commit in 5.16 upstream kernel, support for
mdev_set_iommu_device() kABI was removed from kernel as there were no
in-tree drivers making use of the kABI.
fda49d97f2c4 ("vfio: remove the unused mdev iommu hook")
This kABI is used by SRIOV based Nvidia vGPU on Ubuntu 22.04. Ampere+
(SRIOV based) Nvidia vGPU use kernel's mdev framework and use this
kABI to pin all guest memory during VM boot.
As HWE kernel (for Ubuntu 22.04) will switch to 5.19 upstream kernel,
it will not include this kABI and as a result will break SRIOV based
Nvidia vGPU. So, filing this bug to request to have a custom patch in
HWE kernel which doesn't remove the support for
mdev_set_iommu_device() kABI.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1988806/+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 2018499] [NEW] Jammy update: v6.1.27 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.27 upstream stable release from git://git.kernel.org/ Linux 6.1.27 riscv: No need to relocate the dtb as it lies in the fixmap region riscv: Do not set initial_boot_params to the linear address of the dtb riscv: Move early dtb mapping into the fixmap region driver core: Don't require dynamic_debug for initcall_debug probe timing USB: serial: option: add UNISOC vendor and TOZED LT70C product btrfs: fix uninitialized variable warnings bluetooth: Perform careful capability checks in hci_sock_ioctl() gpiolib: acpi: Add a ignore wakeup quirk for Clevo NL5xNU drm/fb-helper: set x/yres_virtual in drm_fb_helper_check_var wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() mptcp: fix accept vs worker race mptcp: stops worker on unaccepted sockets at listener close mm/mempolicy: fix use-after-free of VMA iterator KVM: arm64: Retry fault if vma_lookup() results become invalid phy: phy-brcm-usb: Utilize platform_get_irq_byname_optional() um: Only disable SSE on clang to work around old GCC bugs ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2018499 Title: Jammy update: v6.1.27 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Confirmed Status in linux-oem-6.1 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.27 upstream stable release from git://git.kernel.org/ Linux 6.1.27 riscv: No need to relocate the dtb as it lies in the fixmap region riscv: Do not set initial_boot_params to the linear address of the dtb riscv: Move early dtb mapping into the fixmap region driver core: Don't require dynamic_debug for initcall_debug probe timing USB: serial: option: add UNISOC vendor and TOZED LT70C product btrfs: fix uninitialized variable warnings bluetooth: Perform careful capability checks in hci_sock_ioctl() gpiolib: acpi: Add a ignore wakeup quirk for Clevo NL5xNU drm/fb-helper: set x/yres_virtual in drm_fb_helper_check_var wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() mptcp: fix accept vs worker race mptcp: stops worker on unaccepted sockets at listener close mm/mempolicy: fix use-after-free of VMA iterator KVM: arm64: Retry fault if vma_lookup() results become invalid phy: phy-brcm-usb: Utilize platform_get_irq_byname_optional() um: Only disable SSE on clang to work around old GCC bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2018499/+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 2018420] Re: linux kerkel 6.2.0.20-generic failed to install
It generated the logs and I clicked on send, it did not report any errors so I assume it sent everything. -- 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/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF
[Kernel-packages] [Bug 2018420] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670932/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType:
[Kernel-packages] [Bug 2018420] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670931/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType:
[Kernel-packages] [Bug 2018420] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670928/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions.
[Kernel-packages] [Bug 2018420] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670930/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType:
[Kernel-packages] [Bug 2018420] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670929/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType:
[Kernel-packages] [Bug 2018420] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670925/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType:
[Kernel-packages] [Bug 2018420] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670922/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType:
[Kernel-packages] [Bug 2018420] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670927/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType:
[Kernel-packages] [Bug 2018420] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670926/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions.
[Kernel-packages] [Bug 2018420] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670924/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType:
[Kernel-packages] [Bug 2018420] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670923/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType:
[Kernel-packages] [Bug 2018420] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670921/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType: Hewlett-Packard
[Kernel-packages] [Bug 2018420] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670920/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType:
[Kernel-packages] [Bug 2018420] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670919/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType: Hewlett-Packard
[Kernel-packages] [Bug 2018420] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670918/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType:
[Kernel-packages] [Bug 2018420] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670917/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType: Hewlett-Packard
[Kernel-packages] [Bug 2018420] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2018420/+attachment/5670916/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1934 F wireplumber /dev/snd/seq:michael1932 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-01-13 (1572 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. eno1 no wireless extensions. virbr0no wireless extensions. MachineType:
[Kernel-packages] [Bug 2018420] Re: linux kerkel 6.2.0.20-generic failed to install
Launchpad.net Launchpad Home Code Bugs Blueprints Translations Answers Authorize application to access Launchpad on your behalf Confirm Computer Access The Ubuntu computer called michael-HP-Compaq-Elite-8300-SFF wants access to your Launchpad account. If you allow this, every application running on michael-HP-Compaq-Elite-8300-SFF will have read-write access to your Launchpad account, including to your private data. If you're using a public computer, if michael-HP-Compaq-Elite-8300-SFF is not the computer you're using right now, or if something just doesn't feel right about this situation, you should choose "Do Not Allow 'michael-HP-Compaq-Elite-8300-SFF' to Access my Launchpad Account", or close this window now. You can always try again later. Even if you decide to give michael-HP-Compaq-Elite-8300-SFF access to your Launchpad account, you can change your mind later. Allow michael-HP-Compaq-Elite-8300-SFF to access my Launchpad account: ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: apport-collected lunar ** Description changed: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E:
[Kernel-packages] [Bug 2008774] Re: Ubuntu 22.04 not waking up after second suspend
I have an Lenovo T16 AMD Ryzen 7 6850U and the amdgpu-install fixed the balck screen suspend bug, but since then my CPU usage is much higher in idle and the fan is permanently running. I'm currently limited to Ubuntu 22.04 and have to wait for the next LTS version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008774/+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 2018473] [NEW] Jammy update: v6.1.26 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.1.26 upstream stable release
from git://git.kernel.org/
Linux 6.1.26
ASN.1: Fix check for strdup() success
ASoC: fsl_sai: Fix pins setting for i.MX8QM platform
ASoC: fsl_asrc_dma: fix potential null-ptr-deref
ASoC: SOF: pm: Tear down pipelines only if DSP was active
mm/page_alloc: fix potential deadlock on zonelist_update_seq seqlock
fpga: bridge: properly initialize bridge device before populating children
iio: adc: at91-sama5d2_adc: fix an error code in at91_adc_allocate_trigger()
Input: pegasus-notetaker - check pipe type when probing
gcc: disable '-Warray-bounds' for gcc-13 too
sctp: Call inet6_destroy_sock() via sk->sk_destruct().
dccp: Call inet6_destroy_sock() via sk->sk_destruct().
inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy().
purgatory: fix disabling debug info
fuse: always revalidate rename target dentry
MIPS: Define RUNTIME_DISCARD_EXIT in LD script
KVM: arm64: Fix buffer overflow in kvm_arm_set_fw_reg()
KVM: arm64: Make vcpu flag updates non-preemptible
sched/fair: Fixes for capacity inversion detection
sched/fair: Consider capacity inversion in util_fits_cpu()
sched/fair: Detect capacity inversion
mm/mmap: regression fix for unmapped_area{_topdown}
mm: page_alloc: skip regions with hugetlbfs pages when allocating 1G pages
mm: kmsan: handle alloc failures in kmsan_vmap_pages_range_noflush()
mm: kmsan: handle alloc failures in kmsan_ioremap_page_range()
mm/huge_memory.c: warn with pr_warn_ratelimited instead of VM_WARN_ON_ONCE_FOLIO
mm/khugepaged: check again on anon uffd-wp during isolation
mm/userfaultfd: fix uffd-wp handling for THP migration entries
drm/rockchip: vop2: Use regcache_sync() to fix suspend/resume
drm/rockchip: vop2: fix suspend/resume
drm/amd/display: set dcn315 lb bpp to 48
drm/amdgpu: Fix desktop freezed after gpu-reset
drm/i915: Fix fast wake AUX sync len
mmc: sdhci_am654: Set HIGH_SPEED_ENA for SDR12 and SDR25
writeback, cgroup: fix null-ptr-deref write in bdi_split_work_to_wbs
kernel/sys.c: fix and improve control flow in __sys_setres[ug]id()
memstick: fix memory leak if card device is never registered
tools/mm/page_owner_sort.c: fix TGID output when cull=tg is used
nilfs2: initialize unused bytes in segment summary blocks
maple_tree: fix a potential memory leak, OOB access, or other unpredictable bug
maple_tree: fix mas_empty_area() search
maple_tree: make maple state reusable after mas_empty_area_rev()
LoongArch: Mark 3 symbol exports as non-GPL
LoongArch: Fix probing of the CRC32 feature
rust: kernel: Mark rust_fmt_argument as extern "C"
btrfs: get the next extent map during fiemap/lseek more efficiently
ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook
iio: light: tsl2772: fix reading proximity-diodes from device tree
iio: dac: ad5755: Add missing fwnode_handle_put()
drm/amdgpu/vcn: Disable indirect SRAM on Vangogh broken BIOSes
Revert "userfaultfd: don't fail on unrecognized features"
mtd: spi-nor: fix memory leak when using debugfs_lookup()
platform/x86: asus-nb-wmi: Add quirk_asus_tablet_mode to other ROG Flow X13
models
platform/x86: gigabyte-wmi: add support for X570S AORUS ELITE
xen/netback: use same error messages for same errors
nvme-tcp: fix a possible UAF when failing to allocate an io queue
drm: test: Fix 32-bit issue in drm_buddy_test
drm: buddy_allocator: Fix buddy allocator init on 32-bit systems
s390/ptrace: fix PTRACE_GET_LAST_BREAK error handling
platform/x86: gigabyte-wmi: add support for B650 AORUS ELITE AX
net: dsa: b53: mmap: add phy ops
scsi: core: Improve scsi_vpd_inquiry() checks
scsi: megaraid_sas: Fix fw_crash_buffer_show()
selftests: sigaltstack: fix -Wuninitialized
platform/x86 (gigabyte-wmi): Add support for A320M-S2H V2
platform/x86/intel: vsec: Fix a memory leak in intel_vsec_add_aux
f2fs: Fix f2fs_truncate_partial_nodes ftrace event
net: bridge: switchdev: don't notify FDB entries with "master dynamic"
e1000e: Disable TSO on i219-LM card to increase speed
bpf: Fix incorrect verifier pruning due to missing register precision taints
spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe()
mlxsw: pci: Fix possible crash during initialization
net: rpl: fix rpl header size calculation
bonding: Fix memory leak when changing bond type to Ethernet
mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next()
bnxt_en: Do not initialize PTP on older P3/P4 chips
netfilter: nf_tables: tighten netlink attribute requirements for catch-all
elements
netfilter: nf_tables: validate catch-all set elements
i40e: fix
[Kernel-packages] [Bug 2018122] Re: My Headphone is Jack Not Being Detected After Waking From Sleep on Ubuntu 23.04
Thank you for providing additional information and for telling us that you can no longer reproduce this issue. I see that you have also updated the link at Ask Ubuntu. Should this issue reapper please change the bug status to 'Confirmed' I''m closing this as 'Invalid' in order to reduce the number of open bugs although it would have course expired after 60 days anyway. The Ask Ubuntu link will still point anyone affected by this issue here although they should open their own bug report so that their specific hardware / software details are captured by the bug reporting process. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/2018122 Title: My Headphone is Jack Not Being Detected After Waking From Sleep on Ubuntu 23.04 Status in linux package in Ubuntu: Invalid Bug description: If I sleep/wake my computer, the 3.5 mm headphone jack no-longer detects when its gets plugged in. Using Ubuntu 23.04 and pipewire: $ pipewire --version pipewire Compiled with libpipewire 0.3.65 Linked with libpipewire 0.3.65 I can work around this problem by one of two ways: 1. After restart, my headphone jack works as expected. 2. Restarting pipewire, then sleeping/waking my computer again. I've been running the following (not sure if I need both): ``` systemctl --user restart pipewire systemctl --user restart pipewire-pulse.service ``` Please let me know of any other information I should provide, and/or where I should actually post this bug. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-12-18 (500 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE Device(8910) Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81T2 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2022 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y545 PG0 dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0: dmi.product.family: Legion Y545 PG0 dmi.product.name: 81T2 dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0 dmi.product.version: Legion Y545 PG0 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018122/+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 2012755] Re: [IOTG][RPL] Enable Time Coordinated Compute interface driver
This bug is awaiting verification that the linux-intel- iotg/5.15.0-1029.34 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-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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: kernel-spammed-jammy-linux-intel-iotg verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2012755 Title: [IOTG][RPL] Enable Time Coordinated Compute interface driver Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: Description Time Coordinated Compute (TCC) Pseudo SRAM interface support on top of Cache Allocation Technology Hardware: Tiger Lake & Elkhart Lake & Alder Lake & Ice Lake & Raptor Lake Target Release: 22.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.19-linux-221019T120731Z Based on LP bug https://bugs.launchpad.net/intel/+bug/1996675, there are some more updates for this driver as following. 0017-Support-RPL-in-measurement-function.tcc 0018-Assume-default-hardware-prefetch-bitmask-in-measuremen.tcc 0019-tcc-fix-patch-style-problem.tcc 0020-tcc-Map-and-show-crl-version-number-in-proc.tcc 0022-tcc-Update-hardware-prefetcher-disable-bits-for-ADL-an.tcc 0023-tcc-Choose-different-L3-cache-miss-perf-event-for-ADL-.tcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2012755/+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 2017934] Re: [IoTG] Integrated TSN controller (stmmac) driver commits tracker
This bug is awaiting verification that the linux-intel- iotg/5.15.0-1029.34 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-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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: kernel-spammed-jammy-linux-intel-iotg verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2017934 Title: [IoTG] Integrated TSN controller (stmmac) driver commits tracker Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: Based on LP https://bugs.launchpad.net/bugs/2006706 List of cherry-picks required: Adding the actual list of commits to make it easier to reference... The following are the latest updates from our v5.15 kernel https://github.com/intel/linux-intel- quilt/tree/lts-v5.15.71-linux-221214T134252Z 0004-fixup-net-phy-marvell10g-Add-WAKE_PHY-support-to-WOL-.conn 0002-stmmac-intel-Add-ADL-N-PCI-ID.conn --> 30c5601fbf353a40115564e1304a1870978fda29 (v5.18-rc1) 0001-taprio-Add-bitmask-checking-based-on-the-traffic-clas.conn 0053-net-phy-dp83867-Fix-SGMII-FIFO-depth-for-non-OF-devic.conn --> e2a54350dc9642e7dfc07335ca355581caa9dbfe (v6.1-rc6) 0052-net-stmmac-check-supported-linkmode-request-for-set-e.conn 0006-net-stmmac-Add-check-for-supported-EEE-advertisement.conn 0002-net-stmmac-update-EEE-status-when-mac-link-goes-down.conn 0003-net-stmmac-Check-and-exit-when-coalesce-rx-usecs-is-e.conn 0033-Revert-net-sched-taprio-make-qdisc_leaf-see-the-per-n.conn --> af7b29b1deaac6da3bb7637f0e263dfab7bfc7a3 (v6.1-rc1) 0005-taprio-Fix-no-error-return-when-entering-invalid-gate.conn 0005-ethtool-Add-support-for-Frame-Preemption-verification.conn 0008-ethtool-Add-support-for-configuring-frame-preemption-.conn 0020-net-networkproxy-add-MIB-passing-via-shared-memory-me.conn 0042-net-phy-add-wrapper-function-for-setup-master-slave-s.conn 0027-net-phy-reconfigure-PHY-WOL-in-resume-if-WOL-option-s.conn 0025-net-stmmac-Disable-MAC-EEE-when-Network-Proxy-is-enab.conn 0035-net-phy-dp83867-add-TI-PHY-loopback.conn --> 13bd85580b85768238cf726dec0ddd89c06a230a (v6.2-rc1) 0003-net-stmmac-add-FPE-preempt-setting-for-TxQ-preemptibl.conn 0013-net-phy-marvell10g-Add-WAKE_PHY-support-to-WOL-event.conn 0043-net-phy-marvell-add-link-status-check-before-enabling.conn 0040-net-stmmac-add-check-for-supported-mode-before-speed-.conn 0044-net-stmmac-Adjust-mac_capabilities-for-Intel-mGbE-2.5.conn 0022-net-stmmac-enable-network-proxy-MSI-interrupt-support.conn 0007-net-stmmac-restructure-Rx-Tx-hardware-timestamping-fu.conn 0045-net-stmmac-check-CBS-input-values-before-configuratio.conn 0008-net-stmmac-introduce-AF_XDP-ZC-RX-HW-timestamps.conn 0024-net-stmmac-Move-phy-state-machine-handling-into-commo.conn 0048-stmmac-intel-Separate-ADL-N-device-ID-from-TGL.conn 0033-net-phy-update-in-band-AN-mode-when-changing-interfac.conn 0047-net-stmmac-Add-check-for-taprio-basetime-configuratio.conn --> 6d534ee057b62ca9332b988619323ee99c7847c1 (v6.2-rc1) 0039-net-stmmac-Set-MAC-s-flow-control-register-to-reflect.conn --> cc3d2b5fc0d6f8ad8a52da5ea679e5c2ec2adbd4 (v6.1-rc8) 0036-net-stmmac-fix-deadlock-caused-by-taking-RTNL-in-RPM-.conn 0037-net-phy-dp83867-perform-phy-reset-after-modifying-aut.conn 0028-Revert-net-stmmac-trigger-PCS-EEE-to-turn-off-on-link.conn 0014-net-stmmac-Fix-Unbalanced-pm_runtime_enable-warning.conn --> d90d0c175cf2982789d336dda928c0f69d3e8a9d (v5.17-rc1) 0038-net-stmmac-Ensure-tx-function-is-not-running-in-stmma.conn --> 77711683a50477de39757d67ab1a3638220d6860 (v6.1-rc6) 0026-net-phy-skip-disabling-interrupt-when-WOL-is-enabled-.conn 0009-REVERTME-net-stmmac-introduce-AF_XDP-ZC-TX-HW-timesta.conn 0010-net-pcs-xpcs-enable-xpcs-reset-skipping.conn 0018-net-networkproxy-add-network-proxy-heci-client.conn net-stmmac-add-network-proxy-support.conn 0019-net-networkproxy-add-configfs.conn 0015-net-stmmac-skip-runtime-handling-in-mdio-read-write.conn 0012-REVERTME-net-stmmac-Add-support-for-HW-accelerated-VL.conn net: stmmac: only enable DMA interrupts when ready --> 087a7b944c5db409f7c1a68bf4896c56ba54eaff (v5.17-rc7) 0006-net-stmmac-Add-per-packet-time-based-scheduling-for-X.conn 0017-net-networkproxy-introduce-network-proxy-framework.conn 0032-net-pcs-xpcs-combine-C37-SGMII-AN-and-2500BASEX-for-I.conn
[Kernel-packages] [Bug 2018470] 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/2018470 Title: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic 5.19.0.42.38 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64
[Kernel-packages] [Bug 2018470] [NEW] Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
Public bug reported: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic 5.19.0.42.38 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 4 11:52:02 2023 HibernationDevice: RESUME=none MachineType: Default string Default string ProcEnviron: LANGUAGE=fr_FR:en TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb 1 amdgpudrmfb 2 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@ amdgpu.si_support=1 radeon.si_support=0
[Kernel-packages] [Bug 2016065] Re: Internal 'Genesys Logic, Inc. Hub' disconnects from ASUS PN50 during boot
Not quite fixed-upstream It took me a little while to realize that USB works with the 6.3.1 mainline kernel only after restarting from Windows 11. With a cold boot into Ubuntu it is still dead. The restart from Windows11 doesn't give working USB with the 6.2 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016065 Title: Internal 'Genesys Logic, Inc. Hub' disconnects from ASUS PN50 during boot Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 libinput-bin: Installed: 1.22.1-1 Candidate: 1.22.1-1 Version table: *** 1.22.1-1 500 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status linux-image-generic: Installed: 6.2.0.20.20 Candidate: 6.2.0.20.20 Version table: *** 6.2.0.20.20 500 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status After upgrading to the 23.04 beta from 22.10 the system (an ASUS PN-50 mini-PC) became unresponsive to any (USB) keyboard or mouse input. This is still the case when the Ubuntu recovery option is chosen in the boot menu. Different USB keyboards and mice/plugging unplugging etc have no effect. The system boots all the way to the Ubuntu login screen and can be accessed via ssh. When booted into Windows all is still functioning correctly Unclear if this is a libinput problem, or lies elsewhere (kernel?) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libinput-bin 1.22.1-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown Date: Thu Apr 13 09:00:56 2023 DistUpgraded: 2023-04-10 16:30:22,175 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:87e7] InstallationDate: Installed on 2020-11-14 (879 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=4837ff80-a59b-47c0-ae9d-811d54bad076 ro quiet splash vt.handoff=7 SourcePackage: libinput UpgradeStatus: Upgraded to lunar on 2023-04-10 (2 days ago) dmi.bios.date: 07/06/2022 dmi.bios.release: 6.24 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0624 dmi.board.asset.tag: Default string dmi.board.name: PN50 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0624:bd07/06/2022:br6.24:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50:pvr0624:rvnASUSTeKCOMPUTERINC.:rnPN50:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50 dmi.product.version: 0624 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016065/+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 2016920] Re: [UBUNTU 22.04] Standalone dump does not work on NVMe device
Thanks for sharing the conclusion. With that closing the ticket (with the best fit status here 'Invalid'.) ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Jammy) ** No longer affects: linux (Ubuntu Kinetic) ** No longer affects: linux (Ubuntu Lunar) ** No longer affects: s390-tools (Ubuntu Lunar) ** No longer affects: s390-tools (Ubuntu Kinetic) ** No longer affects: s390-tools (Ubuntu Jammy) ** Changed in: s390-tools (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-z-systems Status: Incomplete => 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/2016920 Title: [UBUNTU 22.04] Standalone dump does not work on NVMe device Status in Ubuntu on IBM z Systems: Invalid Status in s390-tools package in Ubuntu: Invalid Bug description: Problem Description: I installed Ubuntu 22.04.1. and created a dump partition on an NVMe disk. However, this dump partition is not able to capture a dump: [414340.280553] kdump-tools[15167]: * unloaded kdump kernel [414376.146205] sysrq: Trigger a crash [414376.146215] Kernel panic - not syncing: sysrq triggered crash [414376.146218] CPU: 13 PID: 16009 Comm: bash Not tainted 5.15.0-69-generic #76-Ubuntu [414376.146222] Hardware name: IBM 3931 A01 704 (LPAR) [414376.146224] Call Trace: [414376.146225] [<000176c3e31a>] dump_stack_lvl+0x62/0x80 [414376.146233] [<000176c3913a>] panic+0x152/0x340 [414376.146237] [<0001768d5cfe>] sysrq_handle_crash+0x2e/0x30 [414376.146242] [<0001768d6952>] __handle_sysrq+0xf2/0x280 [414376.146245] [<0001768d7244>] write_sysrq_trigger+0x54/0x70 [414376.146248] [<000176597faa>] proc_reg_write+0x9a/0xf0 [414376.146252] [<0001764e64dc>] vfs_write+0xbc/0x280 [414376.146255] [<0001764e8a18>] ksys_write+0x68/0x100 [414376.146258] [<000176c4288c>] __do_syscall+0x1bc/0x1f0 [414376.146261] [<000176c4fc98>] system_call+0x78/0xa0 System version 9. Watchdog enabled. Running 'ZBootLoader' version '3.1.5' level 'D51C.D51C_328.13'. OK Success [2.131284] zdump: The dump process started for a 64-bit operating system Linux System Dumper starting Version 3.0 (64 bit) Linux version 5.15.27 (buildd@bos02-s390x-003) (gcc (Ubuntu 11.2.0-18ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Mon Mar 21 16:33:41 UTC 2022 ERROR: open /sys/firmware/ipl/device failed No such file or directory ERROR: Could not enable dump device Dump failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2016920/+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 2018347] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
Yes confirmed, figured that one out last night. Thank you so much you! -- 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/2018347 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: this happened as I was running do-release-upgrade to 23.04 from 22.04 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown Date: Tue May 2 20:53:47 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-22 (1044 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81LK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=60d4978d-b55a-4703-aaf6-31c33fe1f348 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, unpackaged PythonDetails: /usr/bin/python3.11, Python 3.11.2, unpackaged RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-03 (0 days ago) dmi.bios.date: 08/19/2019 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN24WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad L340-15IRH Gaming dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrBGCN24WW:bd08/19/2019:br1.24:efr1.24:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming:skuLENOVO_MT_81LK_BU_idea_FM_IdeaPadL340-15IRHGaming: dmi.product.family: IdeaPad L340-15IRH Gaming dmi.product.name: 81LK dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming dmi.product.version: IdeaPad L340-15IRH Gaming dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018347/+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 2012468] Re: Add Intel QAT Gen4 firmware
@keng-yu, please verify these -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2012468 Title: Add Intel QAT Gen4 firmware Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-firmware source package in Lunar: Fix Released Bug description: [Impact] The two Intel QAT Gen4 firmware files are already upstreamed: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qat_4xxx.bin https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qat_4xxx_mmp.bin Please consider to include them. Please also nominate to Focal and Jammy since they are LTS. [Fix] Cherry pick commit 24c9df9b942518717dd53966712df69ac35c8b90. [Where Problems Could Occur] This is new firmware which will get loaded if the relevant HW is present so could result in all sorts of (kernel) problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2012468/+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 2018282] Re: [IOTG][RPL] TGPIO enabling
** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-intel-iotg (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2018282 Title: [IOTG][RPL] TGPIO enabling Status in linux-intel-iotg package in Ubuntu: Fix Committed Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: Contents from https://bugs.launchpad.net/bugs/1996672 Description Intel Timed-Aware GPIO (TGPIO) Controller enablement. Hardware: Raptor Lake Target Release: 22.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.19-linux-221019T120731Z 0001-drivers-ptp-Add-Enhanced-handling-of-reserve-fields.tgpio 0002-drivers-ptp-Add-PEROUT2-ioctl-frequency-adjustment-i.tgpio 0003-drivers-ptp-Add-user-space-input-polling-interface.tgpio 0004-x86-tsc-Add-TSC-support-functions-to-support-ART-dri.tgpio 0005-drivers-ptp-Add-support-for-PMC-Time-Aware-GPIO-Driv.tgpio 0006-x86-core-TSC-reliable-kernel-arg-prevents-DQ-of-TSC-.tgpio 0007-mfd-intel-ehl-gpio-Introduce-MFD-framework-to-PSE-GP.tgpio 0008-TGPIO-Calling-power-management-calls-without-enterin.tgpio 0009-TGPIO-Fix-PSE-TGPIO-PTP-driver-ioctls-fail.tgpio 0010-Kernel-Argument-Bypassing-ART-Detection.tgpio 0011-GPIO-Fix-for-PSE-GPIO-generating-only-one-event-as-i.tgpio 0012-Added-TGPIO-pin-check-before-input-event-read.tgpio 0013-Added-an-Example-to-adjust-frequency-for-output.tgpio 0014-ptp-tgpio-PSE-TGPIO-crosststamp-counttstamp.tgpio 0015-ptp-Fixed-read-issue-on-PHC-with-zero-n_pins.tgpio 0016-ptp-S-W-workaround-for-PMC-TGPIO-h-w-bug.tgpio 0017-ptp-Fix-for-PSE-TGPIO-Oneshot-output-and-counttstamp.tgpio 0018-ptp-Fix-for-PSE-TGPIO-frequency-Adjustment-issue.tgpio 0019-tgpio-Fix-compilation-errors-for-PSE-TGPIO.tgpio 0020-Added-single-shot-output-mode-support-for-TGPIO.tgpio 0021-Added-an-example-to-poll-for-edges.tgpio 0022-Added-support-to-get-TGPIO-System-Clock-Offset.tgpio 0023-Added-single-shot-output-mode-option-for-TGPIO-pin.tgpio 0024-selftests-ptp-Added-COMPV-GPIO-Input-Mode-for-TGPIO.tgpio 0025-ptp-Introduce-PTP_PINDESC_INPUTPOLL-for-Intel-PMC-TG.tgpio 0026-drivers-ptp-Add-COMPV-GPIO-Mode-for-PSE-TGPIO.tgpio 0027-net-ice-fix-braces-around-scalar-initializer.tgpio 0028-ptp-Add-PTP_EVENT_COUNTER_MODE-in-v1-valid-flags.tgpio 0029-tools-testptp-Update-period-for-periodic-output-mode.tgpio 0030-ptp-Enable-preempt-if-it-is-disabled.tgpio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2018282/+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 2018431] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
You have an unsupported DKMS module (evdi) installed that prevents the kernel upgrade. Please remove it and retry the upgrade. If you still need evdi, install the Ubuntu package: apt install evdi-dkms ** 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/2018431 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: During upgrade from kinetic to lunar ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1639 F wireplumber /dev/snd/controlC1: mark 1639 F wireplumber /dev/snd/seq:mark 1636 F pipewire CRDA: N/A CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-common-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-source-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-utils-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/xserver-xorg-video-nvidia-515_515.76+really.515.65.01-0ubuntu1_amd64.deb CasperMD5CheckResult: fail Date: Wed May 3 21:56:24 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-01 (183 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: SYSTEM_MANUFACTURER HX90 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=887b3140-4d95-48d5-aec2-39d52a18cd30 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-03 (0 days ago) dmi.bios.date: 10/11/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.19 dmi.board.asset.tag: Default string dmi.board.name: HX90 dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.19:bd10/11/2021:br5.19:svnSYSTEM_MANUFACTURER:pnHX90:pvrDefaultstring:rvnDefaultstring:rnHX90:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: HX90 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: SYSTEM_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018431/+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 2018431] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
Building module: Cleaning build area... make -j16 KERNELRELEASE=6.2.0-20-generic all INCLUDEDIR=/lib/modules/6.2.0-20-generic/build/include KVERSION=6.2.0-20-generic DKMS_BUILD=1...(bad exit status: 2) ERROR (dkms apport): binary package for evdi: 1.12.0 not found Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/evdi/1.12.0/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! -- 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/2018431 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: During upgrade from kinetic to lunar ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1639 F wireplumber /dev/snd/controlC1: mark 1639 F wireplumber /dev/snd/seq:mark 1636 F pipewire CRDA: N/A CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-common-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-source-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-utils-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/xserver-xorg-video-nvidia-515_515.76+really.515.65.01-0ubuntu1_amd64.deb CasperMD5CheckResult: fail Date: Wed May 3 21:56:24 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-01 (183 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: SYSTEM_MANUFACTURER HX90 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=887b3140-4d95-48d5-aec2-39d52a18cd30 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-03 (0 days ago) dmi.bios.date: 10/11/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.19 dmi.board.asset.tag: Default string dmi.board.name: HX90 dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.19:bd10/11/2021:br5.19:svnSYSTEM_MANUFACTURER:pnHX90:pvrDefaultstring:rvnDefaultstring:rnHX90:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: HX90 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: SYSTEM_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018431/+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 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Hi Ketan,
Are you stating that I should not apply the Revert patches at all?
Revert "scsi: lpfc: SLI path split: Refactor lpfc_iocbq"
Revert "scsi: lpfc: SLI path split: Refactor fast and slow paths to native SLI4"
Revert "scsi: lpfc: SLI path split: Refactor SCSI paths"
Revert "scsi: lpfc: Fix locking for lpfc_sli_iocbq_lookup()"
Revert "scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()"
Revert "scsi: lpfc: Resolve some cleanup issues following SLI path refactoring"
--
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/1988711
Title:
Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
Fix Released
Bug description:
[IMPACT/Justification]
There are numerous bug fixes included in the more recent version of lpfc That
Broadcom has asked to pull into Jammy and Kinetic to better support customers
in the field who are using the GA kernel and cant or wont move to the HWE
kernels. These all are limited to the lpfc driver itself, no patches to core
code are requested.
[FIX]
A few of these were already landed in Jammy, and all but 6 (ones landed in
6.0 upstream) were already in Kinetic.
b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into
lpfc_sli_prep_abort_xri()
ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved
configuration
ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF
WQE
0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in
queuecommand after VMID
35251b4d79db scsi: lpfc: Set PU field when providing D_ID in
XMIT_ELS_RSP64_CX iocb
f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with
malformed user input
4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in
lpfc_nvme_cancel_iocb()
1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for
nvme_admin_async_event cmd completion
ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for
aborted NVMe cmds
336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT
topology
b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is
aborted
6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after
starget_to_rport()
e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path
refactoring
24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path
refactoring
44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in
lpfc_ct_reject_event()
a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol
independent
ed913cf4a533 scsi: lpfc: Commonize VMID code location
fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for
NVMe I/O
e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
5099478e436f scsi: lpfc: Change VMID registration to be based on fabric
parameters
dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if
lpfc_err_lost_link()
4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in
rscn_recovery_check()
596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
92bd903da12b scsi: lpfc: Fix additional reference counting in
lpfc_bsg_rport_els()
db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in
lpfc_sli_prep_wqe()
a346f28ad231 scsi: lpfc: Remove unneeded variable
66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
ef47575fd982 scsi: lpfc:
[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type. (config not enabled)
I have faced on on Focal linux-kvm SRU Cycle: 2023.04.17 Series: focal Package: linux-kvm Version: 5.4.0-1091.97 Cloud: openstack Instance: cpu4-ram4-disk20 Region: scalingstack_bos02 Operation: sru ** Tags added: sru-20230417 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812622 Title: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type. (config not enabled) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: Won't Fix Status in linux-kvm source package in Cosmic: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Status in linux source package in Focal: New Status in linux-aws source package in Focal: New Status in linux-kvm source package in Focal: Confirmed Bug description: These tests: * fib_tests.sh * fib-onlink-tests.sh * fib_rule_tests.sh All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not supported: selftests: net: fib_tests.sh Single path route test RTNETLINK answers: Operation not supported not ok 1..11 selftests: net: fib_tests.sh [FAIL] selftests: net: fib-onlink-tests.sh Configuring interfaces RTNETLINK answers: Operation not supported not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL] selftests: net: fib_rule_tests.sh RTNETLINK answers: Operation not supported not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL] (works on generic Cosmic kernel) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6 ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17 Uname: Linux 4.18.0-1006-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Mon Jan 21 08:00:22 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812622/+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 2008085] Re: net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault)
This bug was fixed in the package linux-intel-iotg - 5.15.0-1028.33 --- linux-intel-iotg (5.15.0-1028.33) jammy; urgency=medium * jammy/linux-intel-iotg: 5.15.0-1028.33 -proposed tracker (LP: #2011906) * Fail to output sound to external monitor which connects via docking station (LP: #2009024) - [Config] Enable CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM * [adl-n][rpl] support intel power capping framework (LP: #2013032) - powercap: RAPL: Add Power Limit4 support for RaptorLake - powercap: RAPL: Add Power Limit4 support for Alder Lake-N and Raptor Lake-P - powercap: intel_rapl: add support for ALDERLAKE_N * [ADL-PS] Audio is malfunction (LP: #2012584) - ASoC: SOF: Intel: pci-tgl: add ADL-PS support - ASoC: Intel: soc-acpi: Add entry for rt711-sdca-sdw in ADL match table * net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault) (LP: #2008085) - Revert "rtnetlink: Add return value check" - Revert "rtnetlink: Fix unchecked return value of dev_xdp_query_md_btf()" - Revert "igc: Enable HW RX Timestamp for AF_XDP ZC" - Revert "igc: Add BTF based metadata for XDP" - Revert "net/core: XDP metadata BTF netlink API" * Bluetooth: btusb: Add module firmware information for MT7622 and MT7961 (LP: #2011520) - SAUCE: (no-up) Bluetooth: btusb: Add module firmware information for MT7622 and MT7961 [ Ubuntu: 5.15.0-70.77 ] * jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918) * CVE-2023-26545 - net: mpls: fix stale pointer if allocation fails during device rename * CVE-2023-1281 - net/sched: tcindex: update imperfect hash filters respecting rcu * [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support (LP: #1971151) - scsi: mpi3mr: Add bsg device support - scsi: mpi3mr: Add support for driver commands - scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header - scsi: mpi3mr: Add support for MPT commands - scsi: mpi3mr: Add support for PEL commands - scsi: mpi3mr: Expose adapter state to sysfs - scsi: mpi3mr: Add support for NVMe passthrough - scsi: mpi3mr: Update driver version to 8.0.0.69.0 - scsi: mpi3mr: Increase I/O timeout value to 60s - scsi: mpi3mr: Hidden drives not removed during soft reset - scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR - scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() - scsi: mpi3mr: Return error if dma_alloc_coherent() fails - scsi: mpi3mr: Add shost related sysfs attributes - scsi: mpi3mr: Add target device related sysfs attributes - scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings - scsi: mpi3mr: Fix kernel-doc * cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids (LP: #2008519) - cpufreq: intel_pstate: Update EPP for AlderLake mobile - cpufreq: intel_pstate: Adjust balance_performance EPP for Sapphire Rapids * Fail to output sound to external monitor which connects via docking station (LP: #2009024) - [Config] Enable CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Jammy update: v5.15.92 upstream stable release (LP: #2011472) - ARM: dts: imx: Fix pca9547 i2c-mux node name - ARM: dts: vf610: Fix pca9548 i2c-mux node names - arm64: dts: freescale: Fix pca954x i2c-mux node names - arm64: dts: imx8mq-thor96: fix no-mmc property for SDHCI - firmware: arm_scmi: Clear stale xfer->hdr.status - bpf: Skip task with pid=1 in send_signal_common() - erofs/zmap.c: Fix incorrect offset calculation - blk-cgroup: fix missing pd_online_fn() while activating policy - HID: playstation: sanity check DualSense calibration data. - dmaengine: imx-sdma: Fix a possible memory leak in sdma_transfer_init - cifs: fix return of uninitialized rc in dfs_cache_update_tgthint() - extcon: usbc-tusb320: fix kernel-doc warning - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - tools: fix ARRAY_SIZE defines in tools and selftests hdrs - selftests/vm: remove ARRAY_SIZE define from individual tests - selftests: Provide local define of __cpuid_count() - net: fix NULL pointer in skb_segment_list - net: mctp: purge receive queues on sk destruction - Linux 5.15.92 * Jammy update: v5.15.91 upstream stable release (LP: #2011467) - memory: tegra: Remove clients SID override programming - memory: atmel-sdramc: Fix missing clk_disable_unprepare in atmel_ramc_probe() - memory: mvebu-devbus: Fix missing clk_disable_unprepare in mvebu_devbus_probe() - dmaengine: ti: k3-udma: Do conditional decrement of UDMA_CHAN_RT_PEER_BCNT_REG - arm64: dts: imx8mp-phycore-som: Remove invalid PMIC property - ARM:
[Kernel-packages] [Bug 2011520] Re: Bluetooth: btusb: Add module firmware information for MT7622 and MT7961
This bug was fixed in the package linux-intel-iotg - 5.15.0-1028.33 --- linux-intel-iotg (5.15.0-1028.33) jammy; urgency=medium * jammy/linux-intel-iotg: 5.15.0-1028.33 -proposed tracker (LP: #2011906) * Fail to output sound to external monitor which connects via docking station (LP: #2009024) - [Config] Enable CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM * [adl-n][rpl] support intel power capping framework (LP: #2013032) - powercap: RAPL: Add Power Limit4 support for RaptorLake - powercap: RAPL: Add Power Limit4 support for Alder Lake-N and Raptor Lake-P - powercap: intel_rapl: add support for ALDERLAKE_N * [ADL-PS] Audio is malfunction (LP: #2012584) - ASoC: SOF: Intel: pci-tgl: add ADL-PS support - ASoC: Intel: soc-acpi: Add entry for rt711-sdca-sdw in ADL match table * net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault) (LP: #2008085) - Revert "rtnetlink: Add return value check" - Revert "rtnetlink: Fix unchecked return value of dev_xdp_query_md_btf()" - Revert "igc: Enable HW RX Timestamp for AF_XDP ZC" - Revert "igc: Add BTF based metadata for XDP" - Revert "net/core: XDP metadata BTF netlink API" * Bluetooth: btusb: Add module firmware information for MT7622 and MT7961 (LP: #2011520) - SAUCE: (no-up) Bluetooth: btusb: Add module firmware information for MT7622 and MT7961 [ Ubuntu: 5.15.0-70.77 ] * jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918) * CVE-2023-26545 - net: mpls: fix stale pointer if allocation fails during device rename * CVE-2023-1281 - net/sched: tcindex: update imperfect hash filters respecting rcu * [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support (LP: #1971151) - scsi: mpi3mr: Add bsg device support - scsi: mpi3mr: Add support for driver commands - scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header - scsi: mpi3mr: Add support for MPT commands - scsi: mpi3mr: Add support for PEL commands - scsi: mpi3mr: Expose adapter state to sysfs - scsi: mpi3mr: Add support for NVMe passthrough - scsi: mpi3mr: Update driver version to 8.0.0.69.0 - scsi: mpi3mr: Increase I/O timeout value to 60s - scsi: mpi3mr: Hidden drives not removed during soft reset - scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR - scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() - scsi: mpi3mr: Return error if dma_alloc_coherent() fails - scsi: mpi3mr: Add shost related sysfs attributes - scsi: mpi3mr: Add target device related sysfs attributes - scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings - scsi: mpi3mr: Fix kernel-doc * cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids (LP: #2008519) - cpufreq: intel_pstate: Update EPP for AlderLake mobile - cpufreq: intel_pstate: Adjust balance_performance EPP for Sapphire Rapids * Fail to output sound to external monitor which connects via docking station (LP: #2009024) - [Config] Enable CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Jammy update: v5.15.92 upstream stable release (LP: #2011472) - ARM: dts: imx: Fix pca9547 i2c-mux node name - ARM: dts: vf610: Fix pca9548 i2c-mux node names - arm64: dts: freescale: Fix pca954x i2c-mux node names - arm64: dts: imx8mq-thor96: fix no-mmc property for SDHCI - firmware: arm_scmi: Clear stale xfer->hdr.status - bpf: Skip task with pid=1 in send_signal_common() - erofs/zmap.c: Fix incorrect offset calculation - blk-cgroup: fix missing pd_online_fn() while activating policy - HID: playstation: sanity check DualSense calibration data. - dmaengine: imx-sdma: Fix a possible memory leak in sdma_transfer_init - cifs: fix return of uninitialized rc in dfs_cache_update_tgthint() - extcon: usbc-tusb320: fix kernel-doc warning - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - tools: fix ARRAY_SIZE defines in tools and selftests hdrs - selftests/vm: remove ARRAY_SIZE define from individual tests - selftests: Provide local define of __cpuid_count() - net: fix NULL pointer in skb_segment_list - net: mctp: purge receive queues on sk destruction - Linux 5.15.92 * Jammy update: v5.15.91 upstream stable release (LP: #2011467) - memory: tegra: Remove clients SID override programming - memory: atmel-sdramc: Fix missing clk_disable_unprepare in atmel_ramc_probe() - memory: mvebu-devbus: Fix missing clk_disable_unprepare in mvebu_devbus_probe() - dmaengine: ti: k3-udma: Do conditional decrement of UDMA_CHAN_RT_PEER_BCNT_REG - arm64: dts: imx8mp-phycore-som: Remove invalid PMIC property - ARM:
[Kernel-packages] [Bug 2013032] Re: [adl-n][rpl] support intel power capping framework
This bug was fixed in the package linux-intel-iotg - 5.15.0-1028.33 --- linux-intel-iotg (5.15.0-1028.33) jammy; urgency=medium * jammy/linux-intel-iotg: 5.15.0-1028.33 -proposed tracker (LP: #2011906) * Fail to output sound to external monitor which connects via docking station (LP: #2009024) - [Config] Enable CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM * [adl-n][rpl] support intel power capping framework (LP: #2013032) - powercap: RAPL: Add Power Limit4 support for RaptorLake - powercap: RAPL: Add Power Limit4 support for Alder Lake-N and Raptor Lake-P - powercap: intel_rapl: add support for ALDERLAKE_N * [ADL-PS] Audio is malfunction (LP: #2012584) - ASoC: SOF: Intel: pci-tgl: add ADL-PS support - ASoC: Intel: soc-acpi: Add entry for rt711-sdca-sdw in ADL match table * net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault) (LP: #2008085) - Revert "rtnetlink: Add return value check" - Revert "rtnetlink: Fix unchecked return value of dev_xdp_query_md_btf()" - Revert "igc: Enable HW RX Timestamp for AF_XDP ZC" - Revert "igc: Add BTF based metadata for XDP" - Revert "net/core: XDP metadata BTF netlink API" * Bluetooth: btusb: Add module firmware information for MT7622 and MT7961 (LP: #2011520) - SAUCE: (no-up) Bluetooth: btusb: Add module firmware information for MT7622 and MT7961 [ Ubuntu: 5.15.0-70.77 ] * jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918) * CVE-2023-26545 - net: mpls: fix stale pointer if allocation fails during device rename * CVE-2023-1281 - net/sched: tcindex: update imperfect hash filters respecting rcu * [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support (LP: #1971151) - scsi: mpi3mr: Add bsg device support - scsi: mpi3mr: Add support for driver commands - scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header - scsi: mpi3mr: Add support for MPT commands - scsi: mpi3mr: Add support for PEL commands - scsi: mpi3mr: Expose adapter state to sysfs - scsi: mpi3mr: Add support for NVMe passthrough - scsi: mpi3mr: Update driver version to 8.0.0.69.0 - scsi: mpi3mr: Increase I/O timeout value to 60s - scsi: mpi3mr: Hidden drives not removed during soft reset - scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR - scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() - scsi: mpi3mr: Return error if dma_alloc_coherent() fails - scsi: mpi3mr: Add shost related sysfs attributes - scsi: mpi3mr: Add target device related sysfs attributes - scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings - scsi: mpi3mr: Fix kernel-doc * cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids (LP: #2008519) - cpufreq: intel_pstate: Update EPP for AlderLake mobile - cpufreq: intel_pstate: Adjust balance_performance EPP for Sapphire Rapids * Fail to output sound to external monitor which connects via docking station (LP: #2009024) - [Config] Enable CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Jammy update: v5.15.92 upstream stable release (LP: #2011472) - ARM: dts: imx: Fix pca9547 i2c-mux node name - ARM: dts: vf610: Fix pca9548 i2c-mux node names - arm64: dts: freescale: Fix pca954x i2c-mux node names - arm64: dts: imx8mq-thor96: fix no-mmc property for SDHCI - firmware: arm_scmi: Clear stale xfer->hdr.status - bpf: Skip task with pid=1 in send_signal_common() - erofs/zmap.c: Fix incorrect offset calculation - blk-cgroup: fix missing pd_online_fn() while activating policy - HID: playstation: sanity check DualSense calibration data. - dmaengine: imx-sdma: Fix a possible memory leak in sdma_transfer_init - cifs: fix return of uninitialized rc in dfs_cache_update_tgthint() - extcon: usbc-tusb320: fix kernel-doc warning - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - tools: fix ARRAY_SIZE defines in tools and selftests hdrs - selftests/vm: remove ARRAY_SIZE define from individual tests - selftests: Provide local define of __cpuid_count() - net: fix NULL pointer in skb_segment_list - net: mctp: purge receive queues on sk destruction - Linux 5.15.92 * Jammy update: v5.15.91 upstream stable release (LP: #2011467) - memory: tegra: Remove clients SID override programming - memory: atmel-sdramc: Fix missing clk_disable_unprepare in atmel_ramc_probe() - memory: mvebu-devbus: Fix missing clk_disable_unprepare in mvebu_devbus_probe() - dmaengine: ti: k3-udma: Do conditional decrement of UDMA_CHAN_RT_PEER_BCNT_REG - arm64: dts: imx8mp-phycore-som: Remove invalid PMIC property - ARM:
[Kernel-packages] [Bug 2012584] Re: [ADL-PS] Audio is malfunction
This bug was fixed in the package linux-intel-iotg - 5.15.0-1028.33 --- linux-intel-iotg (5.15.0-1028.33) jammy; urgency=medium * jammy/linux-intel-iotg: 5.15.0-1028.33 -proposed tracker (LP: #2011906) * Fail to output sound to external monitor which connects via docking station (LP: #2009024) - [Config] Enable CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM * [adl-n][rpl] support intel power capping framework (LP: #2013032) - powercap: RAPL: Add Power Limit4 support for RaptorLake - powercap: RAPL: Add Power Limit4 support for Alder Lake-N and Raptor Lake-P - powercap: intel_rapl: add support for ALDERLAKE_N * [ADL-PS] Audio is malfunction (LP: #2012584) - ASoC: SOF: Intel: pci-tgl: add ADL-PS support - ASoC: Intel: soc-acpi: Add entry for rt711-sdca-sdw in ADL match table * net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault) (LP: #2008085) - Revert "rtnetlink: Add return value check" - Revert "rtnetlink: Fix unchecked return value of dev_xdp_query_md_btf()" - Revert "igc: Enable HW RX Timestamp for AF_XDP ZC" - Revert "igc: Add BTF based metadata for XDP" - Revert "net/core: XDP metadata BTF netlink API" * Bluetooth: btusb: Add module firmware information for MT7622 and MT7961 (LP: #2011520) - SAUCE: (no-up) Bluetooth: btusb: Add module firmware information for MT7622 and MT7961 [ Ubuntu: 5.15.0-70.77 ] * jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918) * CVE-2023-26545 - net: mpls: fix stale pointer if allocation fails during device rename * CVE-2023-1281 - net/sched: tcindex: update imperfect hash filters respecting rcu * [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support (LP: #1971151) - scsi: mpi3mr: Add bsg device support - scsi: mpi3mr: Add support for driver commands - scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header - scsi: mpi3mr: Add support for MPT commands - scsi: mpi3mr: Add support for PEL commands - scsi: mpi3mr: Expose adapter state to sysfs - scsi: mpi3mr: Add support for NVMe passthrough - scsi: mpi3mr: Update driver version to 8.0.0.69.0 - scsi: mpi3mr: Increase I/O timeout value to 60s - scsi: mpi3mr: Hidden drives not removed during soft reset - scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR - scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() - scsi: mpi3mr: Return error if dma_alloc_coherent() fails - scsi: mpi3mr: Add shost related sysfs attributes - scsi: mpi3mr: Add target device related sysfs attributes - scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings - scsi: mpi3mr: Fix kernel-doc * cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids (LP: #2008519) - cpufreq: intel_pstate: Update EPP for AlderLake mobile - cpufreq: intel_pstate: Adjust balance_performance EPP for Sapphire Rapids * Fail to output sound to external monitor which connects via docking station (LP: #2009024) - [Config] Enable CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Jammy update: v5.15.92 upstream stable release (LP: #2011472) - ARM: dts: imx: Fix pca9547 i2c-mux node name - ARM: dts: vf610: Fix pca9548 i2c-mux node names - arm64: dts: freescale: Fix pca954x i2c-mux node names - arm64: dts: imx8mq-thor96: fix no-mmc property for SDHCI - firmware: arm_scmi: Clear stale xfer->hdr.status - bpf: Skip task with pid=1 in send_signal_common() - erofs/zmap.c: Fix incorrect offset calculation - blk-cgroup: fix missing pd_online_fn() while activating policy - HID: playstation: sanity check DualSense calibration data. - dmaengine: imx-sdma: Fix a possible memory leak in sdma_transfer_init - cifs: fix return of uninitialized rc in dfs_cache_update_tgthint() - extcon: usbc-tusb320: fix kernel-doc warning - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - tools: fix ARRAY_SIZE defines in tools and selftests hdrs - selftests/vm: remove ARRAY_SIZE define from individual tests - selftests: Provide local define of __cpuid_count() - net: fix NULL pointer in skb_segment_list - net: mctp: purge receive queues on sk destruction - Linux 5.15.92 * Jammy update: v5.15.91 upstream stable release (LP: #2011467) - memory: tegra: Remove clients SID override programming - memory: atmel-sdramc: Fix missing clk_disable_unprepare in atmel_ramc_probe() - memory: mvebu-devbus: Fix missing clk_disable_unprepare in mvebu_devbus_probe() - dmaengine: ti: k3-udma: Do conditional decrement of UDMA_CHAN_RT_PEER_BCNT_REG - arm64: dts: imx8mp-phycore-som: Remove invalid PMIC property - ARM:
[Kernel-packages] [Bug 2018347] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
You have an unsupported DKMS module (evdi) installed that prevents the kernel upgrade. Remove it and retry the upgrade. If you still need evdi, install the Ubuntu package: apt install evdi-dkms. ** 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/2018347 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: this happened as I was running do-release-upgrade to 23.04 from 22.04 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown Date: Tue May 2 20:53:47 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-22 (1044 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81LK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=60d4978d-b55a-4703-aaf6-31c33fe1f348 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, unpackaged PythonDetails: /usr/bin/python3.11, Python 3.11.2, unpackaged RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-03 (0 days ago) dmi.bios.date: 08/19/2019 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN24WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad L340-15IRH Gaming dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrBGCN24WW:bd08/19/2019:br1.24:efr1.24:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming:skuLENOVO_MT_81LK_BU_idea_FM_IdeaPadL340-15IRHGaming: dmi.product.family: IdeaPad L340-15IRH Gaming dmi.product.name: 81LK dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming dmi.product.version: IdeaPad L340-15IRH Gaming dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018347/+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 2018347] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
Building module: Cleaning build area... make -j12 KERNELRELEASE=6.2.0-20-generic all INCLUDEDIR=/lib/modules/6.2.0-20-generic/build/include KVERSION=6.2.0-20-generic DKMS_BUILD=1...(bad exit status: 2) ERROR (dkms apport): binary package for evdi: 1.11.0 not found Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/evdi/1.11.0/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! -- 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/2018347 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: this happened as I was running do-release-upgrade to 23.04 from 22.04 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown Date: Tue May 2 20:53:47 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-22 (1044 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81LK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=60d4978d-b55a-4703-aaf6-31c33fe1f348 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, unpackaged PythonDetails: /usr/bin/python3.11, Python 3.11.2, unpackaged RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-03 (0 days ago) dmi.bios.date: 08/19/2019 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN24WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad L340-15IRH Gaming dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrBGCN24WW:bd08/19/2019:br1.24:efr1.24:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming:skuLENOVO_MT_81LK_BU_idea_FM_IdeaPadL340-15IRHGaming: dmi.product.family: IdeaPad L340-15IRH Gaming dmi.product.name: 81LK dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming dmi.product.version: IdeaPad L340-15IRH Gaming dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018347/+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 2018413] Re: package linux-headers-generic-hwe-22.04 6.2.0.20.20 failed to install/upgrade: problemas de dependencias - se deja sin configurar
You have an unsupported DKMS module installed (rtl8723du) that prevents the kernel upgrade. Remove it and retry the upgrade. ** Changed in: linux-meta (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2018413 Title: package linux-headers-generic-hwe-22.04 6.2.0.20.20 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in linux-meta package in Ubuntu: Invalid Bug description: no carga de correctamente el kernel 6.2 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-generic-hwe-22.04 6.2.0.20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luis 1012 F wireplumber /dev/snd/seq:luis 1009 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed May 3 09:38:48 2023 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2022-06-27 (310 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: GPU Company GWTN156-11 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=a03bb4b3-88e7-4cb8-87ce-7b204ed63df4 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux-meta Title: package linux-headers-generic-hwe-22.04 6.2.0.20.20 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: Upgraded to lunar on 2023-05-02 (0 days ago) dmi.bios.date: 06/18/2021 dmi.bios.release: 0.5 dmi.bios.vendor: GPU Company dmi.bios.version: V0.5.0_P21S0M2E0F0L3B0T0P2G00A0U0D601_ENE dmi.board.asset.tag: Default string dmi.board.name: GPU Company dmi.board.vendor: GPU Company dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnGPUCompany:bvrV0.5.0_P21S0M2E0F0L3B0T0P2G00A0U0D601_ENE:bd06/18/2021:br0.5:efr1.5:svnGPUCompany:pnGWTN156-11:pvrDefaultstring:rvnGPUCompany:rnGPUCompany:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:sku: dmi.product.family: GWTN156-11 N Series dmi.product.name: GWTN156-11 dmi.product.sku: dmi.product.version: Default string dmi.sys.vendor: GPU Company To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2018413/+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 2018413] Re: package linux-headers-generic-hwe-22.04 6.2.0.20.20 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Building module: Cleaning build area make -j4 KERNELRELEASE=6.2.0-20-generic -C /lib/modules/6.2.0-20-generic/build M=/var/lib/dkms/rtl8723du/0.1/build...(bad exit status: 2) ERROR (dkms apport): binary package for rtl8723du: 0.1 not found Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/rtl8723du/0.1/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2018413 Title: package linux-headers-generic-hwe-22.04 6.2.0.20.20 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in linux-meta package in Ubuntu: Invalid Bug description: no carga de correctamente el kernel 6.2 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-generic-hwe-22.04 6.2.0.20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luis 1012 F wireplumber /dev/snd/seq:luis 1009 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed May 3 09:38:48 2023 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2022-06-27 (310 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: GPU Company GWTN156-11 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=a03bb4b3-88e7-4cb8-87ce-7b204ed63df4 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux-meta Title: package linux-headers-generic-hwe-22.04 6.2.0.20.20 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: Upgraded to lunar on 2023-05-02 (0 days ago) dmi.bios.date: 06/18/2021 dmi.bios.release: 0.5 dmi.bios.vendor: GPU Company dmi.bios.version: V0.5.0_P21S0M2E0F0L3B0T0P2G00A0U0D601_ENE dmi.board.asset.tag: Default string dmi.board.name: GPU Company dmi.board.vendor: GPU Company dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnGPUCompany:bvrV0.5.0_P21S0M2E0F0L3B0T0P2G00A0U0D601_ENE:bd06/18/2021:br0.5:efr1.5:svnGPUCompany:pnGWTN156-11:pvrDefaultstring:rvnGPUCompany:rnGPUCompany:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:sku: dmi.product.family: GWTN156-11 N Series dmi.product.name: GWTN156-11 dmi.product.sku: dmi.product.version: Default string dmi.sys.vendor: GPU Company To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2018413/+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 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Hi Michael,
We recommend that you do not revert these patches and merge all the lpfc
patches provided in this bug description.
The reason you see revert patches in 5.15 stable tree is because, the
tree partially merged only few "path split" patches causing issues.
This is explained by James in the patchset for stable tree.
https://www.spinics.net/lists/stable/msg603453.html
For Jammy, I would recommend taking all the patches that we submitted
(the patchset already has all the "path split" patches in correct
sequence).
Let me know if you have any questions.
--
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/1988711
Title:
Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
Fix Released
Bug description:
[IMPACT/Justification]
There are numerous bug fixes included in the more recent version of lpfc That
Broadcom has asked to pull into Jammy and Kinetic to better support customers
in the field who are using the GA kernel and cant or wont move to the HWE
kernels. These all are limited to the lpfc driver itself, no patches to core
code are requested.
[FIX]
A few of these were already landed in Jammy, and all but 6 (ones landed in
6.0 upstream) were already in Kinetic.
b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into
lpfc_sli_prep_abort_xri()
ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved
configuration
ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF
WQE
0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in
queuecommand after VMID
35251b4d79db scsi: lpfc: Set PU field when providing D_ID in
XMIT_ELS_RSP64_CX iocb
f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with
malformed user input
4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in
lpfc_nvme_cancel_iocb()
1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for
nvme_admin_async_event cmd completion
ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for
aborted NVMe cmds
336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT
topology
b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is
aborted
6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after
starget_to_rport()
e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path
refactoring
24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path
refactoring
44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in
lpfc_ct_reject_event()
a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol
independent
ed913cf4a533 scsi: lpfc: Commonize VMID code location
fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for
NVMe I/O
e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
5099478e436f scsi: lpfc: Change VMID registration to be based on fabric
parameters
dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if
lpfc_err_lost_link()
4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in
rscn_recovery_check()
596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
92bd903da12b scsi: lpfc: Fix additional reference counting in
lpfc_bsg_rport_els()
db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in
lpfc_sli_prep_wqe()
a346f28ad231 scsi: lpfc: Remove unneeded variable
66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
f4fbf4acaa50 scsi:
[Kernel-packages] [Bug 2018448] 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/2018448 Title: Flickering screen on lenovo x1 carbon 10th, fault errors in dmesg Status in linux package in Ubuntu: Confirmed Bug description: Hi, in lunar (haven't tried others yet), the laptop screen flickers every few minutes, and I get these errors in dmesg when that happens: [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 googling found some hits, but this one seems promising, as it's recent, and has the exact same error message: https://www.spinics.net/lists/intel-gfx/msg317397.html If that is not applied in the lunar kernel, and someone builds me one with the patch applied, I can easily try it. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andreas4727 F pipewire andreas4730 F wireplumber /dev/snd/seq:andreas4727 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 4 07:51:38 2023 MachineType: LENOVO 21CC0093BR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 03/02/2023 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET72W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CC0093BR dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrN3AET72W(1.37):bd03/02/2023:br1.37:efr1.18:svnLENOVO:pn21CC0093BR:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CC0093BR:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CC_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CC0093BR dmi.product.sku: LENOVO_MT_21CC_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018448/+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 2018448] [NEW] Flickering screen on lenovo x1 carbon 10th, fault errors in dmesg
Public bug reported: Hi, in lunar (haven't tried others yet), the laptop screen flickers every few minutes, and I get these errors in dmesg when that happens: [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 googling found some hits, but this one seems promising, as it's recent, and has the exact same error message: https://www.spinics.net/lists/intel-gfx/msg317397.html If that is not applied in the lunar kernel, and someone builds me one with the patch applied, I can easily try it. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andreas4727 F pipewire andreas4730 F wireplumber /dev/snd/seq:andreas4727 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 4 07:51:38 2023 MachineType: LENOVO 21CC0093BR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 03/02/2023 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET72W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CC0093BR dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrN3AET72W(1.37):bd03/02/2023:br1.37:efr1.18:svnLENOVO:pn21CC0093BR:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CC0093BR:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CC_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CC0093BR dmi.product.sku: LENOVO_MT_21CC_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug lunar -- 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/2018448 Title: Flickering screen on lenovo x1 carbon 10th, fault errors in dmesg Status in linux package in Ubuntu: Confirmed Bug description: Hi, in lunar (haven't tried others yet), the laptop screen flickers every few minutes, and I get these errors in dmesg when that happens: [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 googling found some hits, but this one seems promising, as it's recent, and has the exact same error message: https://www.spinics.net/lists/intel-gfx/msg317397.html If that is not applied in the lunar kernel, and someone builds me one with the patch applied, I can easily try it. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andreas4727 F pipewire andreas4730 F wireplumber /dev/snd/seq:andreas4727 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 4 07:51:38 2023 MachineType: LENOVO 21CC0093BR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 03/02/2023 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET72W (1.37 )
