[Kernel-packages] [Bug 1988352] Re: focal autopkgtests for hwe-5.11, hwe-5.13 and hwe-5.15 time out on arm
** Tags added: bot-stop-nagging ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- 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/1988352 Title: focal autopkgtests for hwe-5.11, hwe-5.13 and hwe-5.15 time out on arm Status in linux package in Ubuntu: In Progress Bug description: While looking to fix some focal-proposed migrations for zlib, I've noticed these regressions: autopkgtest for linux-hwe-5.11/5.11.0-61.61: amd64: Pass, arm64: Pass, armhf: Regression ♻ , ppc64el: Pass, s390x: Pass autopkgtest for linux-hwe-5.13/5.13.0-52.59~20.04.1: amd64: Pass, arm64: Pass, armhf: Regression ♻ , ppc64el: Pass, s390x: Pass autopkgtest for linux-hwe-5.15/5.15.0-45.48~20.04.1: amd64: Pass, arm64: Regression ♻ , armhf: Regression ♻ , ppc64el: Pass, s390x: Pass They all fail due to timeouts, but worked fine on a local test. I've noticed then that earlier version of hwe kernels (hwe-5.0 and hwe-5.4) were already added to long_tests in autopkgtest-package-configs for armhf. So I think the timeouts can be solved by adding the newer hwe kernels there, too: linux-hwe-5.11/armhf linux-hwe-5.13/armhf linux-hwe-5.15/armhf linux-hwe-5.15/arm6 I've create an MP for this ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.15.0.1018.16)
All autopkgtests for the newly accepted linux-meta-kvm (5.15.0.1018.16) for jammy have finished running. The following regressions have been reported in tests triggered by the package: rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu15 (amd64) digimend-dkms/10-4 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988364] Re: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality
** Also affects: bluez (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu Jammy) Status: New => Triaged ** Changed in: bluez (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Jammy: Triaged Bug description: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality https://github.com/bluez/bluez/issues/313 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+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 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!
Try the latest drm-tip kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm- tip/2022-08-27/amd64/ and if the problem still persists with that then we would usually ask you to report it upstream but it sounds like other people already have: https://gitlab.freedesktop.org/drm/amd/-/issues/2135 https://gitlab.freedesktop.org/drm/amd/-/issues ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2135 https://gitlab.freedesktop.org/drm/amd/-/issues/2135 ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/-/issues/2135 Importance: Unknown Status: Unknown -- 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/1980831 Title: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: When working normally, random freezes happen. Everything freezes, except the mouse cursor. I tried from keyboard to: switch to another window, start a terminal, run a command to restart gnome, enabled ctrl+alt+backspace and tried it to restart X windows, ctrl+alt+delete, switch to another session with ctrl+alt+F1-F9 - nothing works. If I'm listening to something, the sound goes on for a while; sometimes it stops by itself, other times it keeps going. The only way to recover that I've found is to stop the laptop from the power button. For a while I thought it was due to firefox; I installed the deb version and then switched to chrome - same behavior. It didn't happen when I was playing Hollow Knight in Steam, or when I've used the terminal and nothing else. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:27:36 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-16 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1980831/+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 1982739] Re: BlueZ 5.65 release
Rafael, I have opened bug 1988364 to track that issue and future backporting of the fix to jammy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1982739 Title: BlueZ 5.65 release Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.65 to kinetic: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.65.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1982739/+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 1988364] [NEW] Sony WH-1000XM4 missing the A2DP profile and defaults to low quality
Public bug reported: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality https://github.com/bluez/bluez/issues/313 ** Affects: bluez Importance: Unknown Status: Unknown ** Affects: bluez (Ubuntu) Importance: High Status: Fix Released ** Tags: fixed-in-5.65 fixed-upstream rls-jj-incoming ** Bug watch added: github.com/bluez/bluez/issues #313 https://github.com/bluez/bluez/issues/313 ** Also affects: bluez via https://github.com/bluez/bluez/issues/313 Importance: Unknown Status: Unknown ** Changed in: bluez (Ubuntu) Status: New => Fix Released ** Tags added: fixed-in-5.65 fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: Fix Released Bug description: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality https://github.com/bluez/bluez/issues/313 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+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 1988364] Re: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality
The fix is: https://github.com/bluez/bluez/commit/62e591578e3f948e187aacf44ede4286fad37ad7 ** Tags added: rls-jj-incoming ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: Fix Released Bug description: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality https://github.com/bluez/bluez/issues/313 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+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 1910866] Re: nvme drive fails after some time
Hello Kai-Heng, Unrelated to system sleep. -- 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/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Fix Released Status in Debian: New Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:56:28 2021 InstallationDate: Installed on 2020-08-15 (146 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel Corporation NUC8i7HVK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7 RebootRequiredPkgs: linux-image-5.8.0-36-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.0-34-generic N/A linux-backports-modules-5.8.0-34-generic
[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time
João Pedro Seara, Does this issue only happen after system sleep? -- 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/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Fix Released Status in Debian: New Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:56:28 2021 InstallationDate: Installed on 2020-08-15 (146 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel Corporation NUC8i7HVK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7 RebootRequiredPkgs: linux-image-5.8.0-36-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.0-34-generic N/A
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
Thanks for the bug report. Does the ambient light sensor works after system suspend, prior to the kernel upgrade? ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31
[Kernel-packages] [Bug 1924256] Re: nvme unpredictibly disappears after some time
I am observing the same in Ubuntu 22.04 @ 5.15.0-46-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1924256 Title: nvme unpredictibly disappears after some time Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: Hi, I have a Lenovo E15 Gen 2 laptop, bought around 1 month ago, runnning Ubuntu 20.04 (kernel 5.8.0-48-generic) In this Pc, I have a 512 GB nvme running fine, and a 1TB nvme which somehow disappears after some time. Let's I turn on the PC, use it for development, word processing, nothing heavily sollicitating the storage, and after some unpredictable time, the PC freezes, and when it comes back to life, the nvme is unmounted and does not appear anymore until I reboot. I read bug #1910866 which looks very similar, but it is supposed to be fixed in kernel 5.8.0-41.46. As i'm facing the problem with kernel 5.8.0-48-generic, I think it may be another bug. In the output of journalctl, I see this from april, 8th (filtered on kernel messages): avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 576 QID 6 timeout, aborting avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 577 QID 6 timeout, aborting avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 578 QID 6 timeout, aborting avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 579 QID 6 timeout, aborting avril 08 20:38:09 Auckland kernel: nvme nvme0: I/O 468 QID 2 timeout, reset controller avril 08 20:38:40 Auckland kernel: nvme nvme0: I/O 1 QID 0 timeout, reset controller avril 08 20:40:12 Auckland kernel: INFO: task jbd2/nvme0n1p1-:546 blocked for more than 120 seconds. avril 08 20:40:12 Auckland kernel: Not tainted 5.8.0-48-generic #54~20.04.1-Ubuntu avril 08 20:40:12 Auckland kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. avril 08 20:40:12 Auckland kernel: jbd2/nvme0n1p1- D0 546 2 0x4000 avril 08 20:40:12 Auckland kernel: Call Trace: avril 08 20:40:12 Auckland kernel: __schedule+0x394/0xa60 avril 08 20:40:12 Auckland kernel: ? percpu_counter_add_batch+0x50/0x70 avril 08 20:40:12 Auckland kernel: schedule+0x55/0xc0 avril 08 20:40:12 Auckland kernel: io_schedule+0x16/0x40 avril 08 20:40:12 Auckland kernel: rq_qos_wait+0x106/0x180 avril 08 20:40:12 Auckland kernel: ? __wbt_done+0x40/0x40 avril 08 20:40:12 Auckland kernel: ? sysv68_partition+0x290/0x290 avril 08 20:40:12 Auckland kernel: ? wbt_cleanup_cb+0x20/0x20 avril 08 20:40:12 Auckland kernel: wbt_wait+0x9e/0xe0 avril 08 20:40:12 Auckland kernel: __rq_qos_throttle+0x28/0x40 avril 08 20:40:12 Auckland kernel: blk_mq_make_request+0xfa/0x5f0 avril 08 20:40:12 Auckland kernel: generic_make_request+0x2b1/0x3b0 avril 08 20:40:12 Auckland kernel: submit_bio+0x51/0x1b0 avril 08 20:40:12 Auckland kernel: ? bio_add_page+0x6a/0x90 avril 08 20:40:12 Auckland kernel: submit_bh_wbc+0x182/0x1b0 avril 08 20:40:12 Auckland kernel: submit_bh+0x13/0x20 avril 08 20:40:12 Auckland kernel: jbd2_journal_commit_transaction+0x5d0/0x17f0 avril 08 20:40:12 Auckland kernel: kjournald2+0xb6/0x280 avril 08 20:40:12 Auckland kernel: ? wait_woken+0x80/0x80 avril 08 20:40:12 Auckland kernel: kthread+0x114/0x150 avril 08 20:40:12 Auckland kernel: ? commit_timeout+0x20/0x20 avril 08 20:40:12 Auckland kernel: ? kthread_park+0x90/0x90 avril 08 20:40:12 Auckland kernel: ret_from_fork+0x1f/0x30 avril 08 20:40:12 Auckland kernel: INFO: task kworker/u16:68:27721 blocked for more than 120 seconds. avril 08 20:40:12 Auckland kernel: Not tainted 5.8.0-48-generic #54~20.04.1-Ubuntu avril 08 20:40:12 Auckland kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. avril 08 20:40:12 Auckland kernel: kworker/u16:68 D0 27721 2 0x4000 avril 08 20:40:12 Auckland kernel: Workqueue: writeback wb_workfn (flush-259:0) avril 08 20:40:12 Auckland kernel: Call Trace: avril 08 20:40:12 Auckland kernel: __schedule+0x394/0xa60 avril 08 20:40:12 Auckland kernel: ? alloc_pages_current+0x87/0xe0 avril 08 20:40:12 Auckland kernel: ? bit_wait_io_timeout+0x70/0x70 avril 08 20:40:12 Auckland kernel: schedule+0x55/0xc0 avril 08 20:40:12 Auckland kernel: io_schedule+0x16/0x40 avril 08 20:40:12 Auckland kernel: bit_wait_io+0x11/0x50 avril 08 20:40:12 Auckland kernel: __wait_on_bit+0x33/0xa0 avril 08 20:40:12 Auckland kernel: out_of_line_wait_on_bit+0x8d/0xb0 avril 08 20:40:12 Auckland kernel: ? var_wake_function+0x30/0x30 avril 08 20:40:12 Auckland kernel: do_get_write_access+0x29b/0x3c0 avril 08 20:40:12 Auckland kernel: jbd2_journal_get_write_access+0x63/0x90 avril 08 20:40:12 Auckland kernel: __ext4_journal_get_write_access+0x7a/0x120 avril 08 20:40:12 Auckland kernel: ext4_mb_mark_diskspace_used+0x80/0x430 avril 08
[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time
Still observing the same I wrote in my comment above. Now upgraded to 5.15.0-46-generic. This is very frustrating. -- 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/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Fix Released Status in Debian: New Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:56:28 2021 InstallationDate: Installed on 2020-08-15 (146 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel Corporation NUC8i7HVK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7 RebootRequiredPkgs: linux-image-5.8.0-36-generic linux-base RelatedPackageVersions:
[Kernel-packages] [Bug 1924256] Re: nvme unpredictibly disappears after some time
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1924256 Title: nvme unpredictibly disappears after some time Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: Hi, I have a Lenovo E15 Gen 2 laptop, bought around 1 month ago, runnning Ubuntu 20.04 (kernel 5.8.0-48-generic) In this Pc, I have a 512 GB nvme running fine, and a 1TB nvme which somehow disappears after some time. Let's I turn on the PC, use it for development, word processing, nothing heavily sollicitating the storage, and after some unpredictable time, the PC freezes, and when it comes back to life, the nvme is unmounted and does not appear anymore until I reboot. I read bug #1910866 which looks very similar, but it is supposed to be fixed in kernel 5.8.0-41.46. As i'm facing the problem with kernel 5.8.0-48-generic, I think it may be another bug. In the output of journalctl, I see this from april, 8th (filtered on kernel messages): avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 576 QID 6 timeout, aborting avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 577 QID 6 timeout, aborting avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 578 QID 6 timeout, aborting avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 579 QID 6 timeout, aborting avril 08 20:38:09 Auckland kernel: nvme nvme0: I/O 468 QID 2 timeout, reset controller avril 08 20:38:40 Auckland kernel: nvme nvme0: I/O 1 QID 0 timeout, reset controller avril 08 20:40:12 Auckland kernel: INFO: task jbd2/nvme0n1p1-:546 blocked for more than 120 seconds. avril 08 20:40:12 Auckland kernel: Not tainted 5.8.0-48-generic #54~20.04.1-Ubuntu avril 08 20:40:12 Auckland kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. avril 08 20:40:12 Auckland kernel: jbd2/nvme0n1p1- D0 546 2 0x4000 avril 08 20:40:12 Auckland kernel: Call Trace: avril 08 20:40:12 Auckland kernel: __schedule+0x394/0xa60 avril 08 20:40:12 Auckland kernel: ? percpu_counter_add_batch+0x50/0x70 avril 08 20:40:12 Auckland kernel: schedule+0x55/0xc0 avril 08 20:40:12 Auckland kernel: io_schedule+0x16/0x40 avril 08 20:40:12 Auckland kernel: rq_qos_wait+0x106/0x180 avril 08 20:40:12 Auckland kernel: ? __wbt_done+0x40/0x40 avril 08 20:40:12 Auckland kernel: ? sysv68_partition+0x290/0x290 avril 08 20:40:12 Auckland kernel: ? wbt_cleanup_cb+0x20/0x20 avril 08 20:40:12 Auckland kernel: wbt_wait+0x9e/0xe0 avril 08 20:40:12 Auckland kernel: __rq_qos_throttle+0x28/0x40 avril 08 20:40:12 Auckland kernel: blk_mq_make_request+0xfa/0x5f0 avril 08 20:40:12 Auckland kernel: generic_make_request+0x2b1/0x3b0 avril 08 20:40:12 Auckland kernel: submit_bio+0x51/0x1b0 avril 08 20:40:12 Auckland kernel: ? bio_add_page+0x6a/0x90 avril 08 20:40:12 Auckland kernel: submit_bh_wbc+0x182/0x1b0 avril 08 20:40:12 Auckland kernel: submit_bh+0x13/0x20 avril 08 20:40:12 Auckland kernel: jbd2_journal_commit_transaction+0x5d0/0x17f0 avril 08 20:40:12 Auckland kernel: kjournald2+0xb6/0x280 avril 08 20:40:12 Auckland kernel: ? wait_woken+0x80/0x80 avril 08 20:40:12 Auckland kernel: kthread+0x114/0x150 avril 08 20:40:12 Auckland kernel: ? commit_timeout+0x20/0x20 avril 08 20:40:12 Auckland kernel: ? kthread_park+0x90/0x90 avril 08 20:40:12 Auckland kernel: ret_from_fork+0x1f/0x30 avril 08 20:40:12 Auckland kernel: INFO: task kworker/u16:68:27721 blocked for more than 120 seconds. avril 08 20:40:12 Auckland kernel: Not tainted 5.8.0-48-generic #54~20.04.1-Ubuntu avril 08 20:40:12 Auckland kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. avril 08 20:40:12 Auckland kernel: kworker/u16:68 D0 27721 2 0x4000 avril 08 20:40:12 Auckland kernel: Workqueue: writeback wb_workfn (flush-259:0) avril 08 20:40:12 Auckland kernel: Call Trace: avril 08 20:40:12 Auckland kernel: __schedule+0x394/0xa60 avril 08 20:40:12 Auckland kernel: ? alloc_pages_current+0x87/0xe0 avril 08 20:40:12 Auckland kernel: ? bit_wait_io_timeout+0x70/0x70 avril 08 20:40:12 Auckland kernel: schedule+0x55/0xc0 avril 08 20:40:12 Auckland kernel: io_schedule+0x16/0x40 avril 08 20:40:12 Auckland kernel: bit_wait_io+0x11/0x50 avril 08 20:40:12 Auckland kernel: __wait_on_bit+0x33/0xa0 avril 08 20:40:12 Auckland kernel: out_of_line_wait_on_bit+0x8d/0xb0 avril 08 20:40:12 Auckland kernel: ? var_wake_function+0x30/0x30 avril 08 20:40:12 Auckland kernel: do_get_write_access+0x29b/0x3c0 avril 08 20:40:12 Auckland kernel: jbd2_journal_get_write_access+0x63/0x90 avril 08 20:40:12 Auckland kernel: __ext4_journal_get_write_access+0x7a/0x120
[Kernel-packages] [Bug 1981345] Re: jammy: override starfive and allwinner from universe to main
$ rmadison -s jammy,jammy-updates,jammy-proposed -S linux-starfive-5.17|grep universe $ ** Changed in: linux-starfive-5.17 (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1981345 Title: jammy: override starfive and allwinner from universe to main Status in linux-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-meta-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-meta-starfive-5.17 package in Ubuntu: Fix Released Status in linux-starfive-5.17 package in Ubuntu: Fix Released Status in linux-allwinner-5.17 source package in Jammy: Fix Released Status in linux-meta-allwinner-5.17 source package in Jammy: Fix Released Status in linux-meta-starfive-5.17 source package in Jammy: Fix Released Status in linux-starfive-5.17 source package in Jammy: Fix Released Bug description: Kernels must be published in main, please override component to main. As otherwise image building fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1981345/+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 1981345] Re: jammy: override starfive and allwinner from universe to main
$ rmadison -s jammy,jammy-updates,jammy-proposed -S linux-allwinner-5.17|grep universe $ ** Changed in: linux-allwinner-5.17 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-meta-allwinner-5.17 (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1981345 Title: jammy: override starfive and allwinner from universe to main Status in linux-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-meta-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-meta-starfive-5.17 package in Ubuntu: Fix Released Status in linux-starfive-5.17 package in Ubuntu: Fix Released Status in linux-allwinner-5.17 source package in Jammy: Fix Released Status in linux-meta-allwinner-5.17 source package in Jammy: Fix Released Status in linux-meta-starfive-5.17 source package in Jammy: Fix Released Status in linux-starfive-5.17 source package in Jammy: Fix Released Bug description: Kernels must be published in main, please override component to main. As otherwise image building fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1981345/+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 1981345] Re: jammy: override starfive and allwinner from universe to main
$ rmadison -s jammy,jammy-updates,jammy-proposed -S linux-meta-starfive-5.17|grep universe $ ** Changed in: linux-meta-starfive-5.17 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-starfive-5.17 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1981345 Title: jammy: override starfive and allwinner from universe to main Status in linux-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-meta-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-meta-starfive-5.17 package in Ubuntu: Fix Released Status in linux-starfive-5.17 package in Ubuntu: Fix Released Status in linux-allwinner-5.17 source package in Jammy: Fix Released Status in linux-meta-allwinner-5.17 source package in Jammy: Fix Released Status in linux-meta-starfive-5.17 source package in Jammy: Fix Released Status in linux-starfive-5.17 source package in Jammy: Fix Released Bug description: Kernels must be published in main, please override component to main. As otherwise image building fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1981345/+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 1981345] Re: jammy: override starfive and allwinner from universe to main
$ rmadison -s jammy,jammy-updates,jammy-proposed -S linux-meta-allwinner-5.17|grep universe $ ** Changed in: linux-meta-allwinner-5.17 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-meta-starfive-5.17 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1981345 Title: jammy: override starfive and allwinner from universe to main Status in linux-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-meta-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-meta-starfive-5.17 package in Ubuntu: Fix Released Status in linux-starfive-5.17 package in Ubuntu: Fix Released Status in linux-allwinner-5.17 source package in Jammy: Fix Released Status in linux-meta-allwinner-5.17 source package in Jammy: Fix Released Status in linux-meta-starfive-5.17 source package in Jammy: Fix Released Status in linux-starfive-5.17 source package in Jammy: Fix Released Bug description: Kernels must be published in main, please override component to main. As otherwise image building fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1981345/+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 1981345] Re: jammy: override starfive and allwinner from universe to main
In fact they were seeded in jammy and kinetic at the same time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1981345 Title: jammy: override starfive and allwinner from universe to main Status in linux-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-meta-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-meta-starfive-5.17 package in Ubuntu: Fix Released Status in linux-starfive-5.17 package in Ubuntu: Fix Released Status in linux-allwinner-5.17 source package in Jammy: Fix Released Status in linux-meta-allwinner-5.17 source package in Jammy: Fix Released Status in linux-meta-starfive-5.17 source package in Jammy: Fix Released Status in linux-starfive-5.17 source package in Jammy: Fix Released Bug description: Kernels must be published in main, please override component to main. As otherwise image building fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1981345/+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 1981345] Re: jammy: override starfive and allwinner from universe to main
$ rmadison -s jammy,jammy-updates,jammy-proposed -S linux- allwinner-5.17|grep universe ** Changed in: linux-allwinner-5.17 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1981345 Title: jammy: override starfive and allwinner from universe to main Status in linux-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-meta-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-meta-starfive-5.17 package in Ubuntu: Fix Released Status in linux-starfive-5.17 package in Ubuntu: Fix Released Status in linux-allwinner-5.17 source package in Jammy: Fix Released Status in linux-meta-allwinner-5.17 source package in Jammy: Fix Released Status in linux-meta-starfive-5.17 source package in Jammy: Fix Released Status in linux-starfive-5.17 source package in Jammy: Fix Released Bug description: Kernels must be published in main, please override component to main. As otherwise image building fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1981345/+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 1981345] Re: jammy: override starfive and allwinner from universe to main
These have been seeded now in kinetic, so they can also be seeded in jammy and promoted. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1981345 Title: jammy: override starfive and allwinner from universe to main Status in linux-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-meta-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-meta-starfive-5.17 package in Ubuntu: Fix Released Status in linux-starfive-5.17 package in Ubuntu: Fix Released Status in linux-allwinner-5.17 source package in Jammy: Fix Released Status in linux-meta-allwinner-5.17 source package in Jammy: Fix Released Status in linux-meta-starfive-5.17 source package in Jammy: Fix Released Status in linux-starfive-5.17 source package in Jammy: Fix Released Bug description: Kernels must be published in main, please override component to main. As otherwise image building fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1981345/+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 1988295] Re: Please RM proposed NBS of removed source package linux-raspi-unstable
$ remove-package -b -s kinetic-proposed -y -m NBS $(rmadison -s
kinetic,kinetic-proposed -S linux-raspi-unstable | awk '{ print $1 }')
Removing packages from kinetic-proposed:
linux-buildinfo-5.13.0-1002-raspi 5.13.0-1002.2 in kinetic arm64
linux-buildinfo-5.13.0-1002-raspi 5.13.0-1002.2 in kinetic armhf
linux-buildinfo-5.13.0-1002-raspi-nolpae 5.13.0-1002.2 in kinetic armhf
linux-headers-5.13.0-1002-raspi 5.13.0-1002.2 in kinetic arm64
linux-headers-5.13.0-1002-raspi 5.13.0-1002.2 in kinetic armhf
linux-headers-5.13.0-1002-raspi-nolpae 5.13.0-1002.2 in kinetic armhf
linux-image-5.13.0-1002-raspi 5.13.0-1002.2 in kinetic arm64
linux-image-5.13.0-1002-raspi 5.13.0-1002.2 in kinetic armhf
linux-image-5.13.0-1002-raspi-nolpae 5.13.0-1002.2 in kinetic armhf
linux-modules-5.13.0-1002-raspi 5.13.0-1002.2 in kinetic arm64
linux-modules-5.13.0-1002-raspi 5.13.0-1002.2 in kinetic armhf
linux-modules-5.13.0-1002-raspi-nolpae 5.13.0-1002.2 in kinetic armhf
linux-raspi-unstable-headers-5.13.0-1002 5.13.0-1002.2 in kinetic arm64
linux-raspi-unstable-headers-5.13.0-1002 5.13.0-1002.2 in kinetic armhf
linux-raspi-unstable-tools-5.13.0-1002 5.13.0-1002.2 in kinetic arm64
linux-raspi-unstable-tools-5.13.0-1002 5.13.0-1002.2 in kinetic armhf
linux-tools-5.13.0-1002-raspi 5.13.0-1002.2 in kinetic arm64
linux-tools-5.13.0-1002-raspi 5.13.0-1002.2 in kinetic armhf
linux-tools-5.13.0-1002-raspi-nolpae 5.13.0-1002.2 in kinetic armhf
Comment: NBS
19 packages successfully removed.
** Changed in: linux-raspi (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1988295
Title:
Please RM proposed NBS of removed source package linux-raspi-unstable
Status in linux-raspi package in Ubuntu:
Fix Released
Bug description:
I have recently improved supported-kernel-common seeds to keep all
kernel binary packages in main/restricted, even for obsolete ABIs.
This has triggered components missmatches report (SVG only)
https://people.canonical.com/~ubuntu-archive/component-mismatches-
proposed.svg to identify that we have stale left over NBS binary
packages from linux-raspi-unstable source package in jammy-
proposed/universe and kinetic-proposed/universe
Please remove all of the below binary packages from the archive, as
they are NBS with src:linux-raspi-unstable long gone:
$ rmadison -S linux-raspi-unstable
linux-buildinfo-5.13.0-1002-raspi| 5.13.0-1002.2 |
jammy-proposed/universe | arm64, armhf
linux-buildinfo-5.13.0-1002-raspi| 5.13.0-1002.2 |
kinetic-proposed/universe | arm64, armhf
linux-buildinfo-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 |
jammy-proposed/universe | armhf
linux-buildinfo-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 |
kinetic-proposed/universe | armhf
linux-headers-5.13.0-1002-raspi | 5.13.0-1002.2 |
jammy-proposed/universe | arm64, armhf
linux-headers-5.13.0-1002-raspi | 5.13.0-1002.2 |
kinetic-proposed/universe | arm64, armhf
linux-headers-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 |
jammy-proposed/universe | armhf
linux-headers-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 |
kinetic-proposed/universe | armhf
linux-image-5.13.0-1002-raspi| 5.13.0-1002.2 |
jammy-proposed/universe | arm64, armhf
linux-image-5.13.0-1002-raspi| 5.13.0-1002.2 |
kinetic-proposed/universe | arm64, armhf
linux-image-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 |
jammy-proposed/universe | armhf
linux-image-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 |
kinetic-proposed/universe | armhf
linux-modules-5.13.0-1002-raspi | 5.13.0-1002.2 |
jammy-proposed/universe | arm64, armhf
linux-modules-5.13.0-1002-raspi | 5.13.0-1002.2 |
kinetic-proposed/universe | arm64, armhf
linux-modules-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 |
jammy-proposed/universe | armhf
linux-modules-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 |
kinetic-proposed/universe | armhf
linux-raspi-unstable-headers-5.13.0-1002 | 5.13.0-1002.2 |
jammy-proposed/universe | arm64, armhf
linux-raspi-unstable-headers-5.13.0-1002 | 5.13.0-1002.2 |
kinetic-proposed/universe | arm64, armhf
linux-raspi-unstable-tools-5.13.0-1002 | 5.13.0-1002.2 |
jammy-proposed/universe | arm64, armhf
linux-raspi-unstable-tools-5.13.0-1002 | 5.13.0-1002.2 |
kinetic-proposed/universe | arm64, armhf
linux-tools-5.13.0-1002-raspi| 5.13.0-1002.2 |
jammy-proposed/universe | arm64, armhf
linux-tools-5.13.0-1002-raspi| 5.13.0-1002.2 |
kinetic-proposed/universe | arm64, armhf
linux-tools-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 |
jammy-proposed/universe | armhf
[Kernel-packages] [Bug 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
Also, this will be resolved in Kinetic via 5.19 and Jammy 22.04.2 via HWE. ** Tags added: servcert-472 -- 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/1983656 Title: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf) Status in linux package in Ubuntu: Incomplete Bug description: Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in the test kernel v5.15.0-41 and did not resolve the issue. These Virtual Machines do work with the Mainline v5.19 build on the host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related commits that are not currently backported to v5.15 or any upstream stable kernel: 6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings before configuring [v5.18] be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling [v5.19] Additionally during testing if we link down an interface and/or try to use netplan apply to start DHCP instead of manual configuration we triggered the following memory corruption bug: efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF driver [v5.19] It appears that this ice/iavf driver is quite immature as many significant SR-IOV related fixes have landed in each of the recent kernel releases and we may need to consider pro-actively backporting more fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+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 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
Hi Trent, What is the expectation here? To update 5.15? Or also 5.4? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983656 Title: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf) Status in linux package in Ubuntu: Incomplete Bug description: Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in the test kernel v5.15.0-41 and did not resolve the issue. These Virtual Machines do work with the Mainline v5.19 build on the host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related commits that are not currently backported to v5.15 or any upstream stable kernel: 6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings before configuring [v5.18] be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling [v5.19] Additionally during testing if we link down an interface and/or try to use netplan apply to start DHCP instead of manual configuration we triggered the following memory corruption bug: efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF driver [v5.19] It appears that this ice/iavf driver is quite immature as many significant SR-IOV related fixes have landed in each of the recent kernel releases and we may need to consider pro-actively backporting more fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+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 1988354] Re: oem-20.04 transitional package in kinetic's generic lrm does not make sense
** Changed in: linux-restricted-modules (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988354 Title: oem-20.04 transitional package in kinetic's generic lrm does not make sense Status in linux-restricted-modules package in Ubuntu: New Bug description: oem-20.04 transitional package in kinetic's generic lrm does not make sense so probably should be dropped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988354/+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 1967848] Re: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3
This should not be an issue in 18.04.6 (which is using the same 5.4 kernel in 20.04 and has version 12.6.0.4). Apologies that this fell through the cracks. Can you confirm that 18.04.6 resolved the problem? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jeff Lane (bladernr) ** Tags added: servcert-471 -- 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/1967848 Title: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3 Status in linux package in Ubuntu: Incomplete Bug description: This bug is raised as per the suggestion by Jeff Email snapshot: -- File a bug, point me to a patch, and I'll see if I can pull it. Though we'd need more info... for are we talking the 4.15 GA kernel, or the 5.4 kernel? It would be a bit more involved If I have to pull the patch into 4 different kernels in order to get it back into 4.15 to avoid regressions. BUT it's not difficult, assuming any patches are only applied to lpfc. Once it lands in the scsi tree we can start looking, though I'd be more comfy for it to be in linux-next or mainline. I'll also need someone to fill out some info on the bug to create the SRU justification. -- There is an issue in which we are seeing login failure with Ubuntu 18.04.3, inbox driver version 12.0.0.0 but this issue is not seen with Ubuntu 20.04.2 with inbox driver 12.0.0.6. I found that upstream commit id [0a9e9687acaf6ac1198fd41f03d64f8b92e4515e] could potentially fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967848/+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 1988354] [NEW] oem-20.04 transitional package in kinetic's generic lrm does not make sense
Public bug reported: oem-20.04 transitional package in kinetic's generic lrm does not make sense so probably should be dropped. ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988354 Title: oem-20.04 transitional package in kinetic's generic lrm does not make sense Status in linux-restricted-modules package in Ubuntu: New Bug description: oem-20.04 transitional package in kinetic's generic lrm does not make sense so probably should be dropped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988354/+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 1988346] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612787/+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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation
[Kernel-packages] [Bug 1988346] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612785/+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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]:
[Kernel-packages] [Bug 1988346] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612784/+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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation
[Kernel-packages] [Bug 1988346] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612786/+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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation
[Kernel-packages] [Bug 1988346] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612789/+files/RfKill.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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation 'sleep'
[Kernel-packages] [Bug 1988346] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612788/+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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation
[Kernel-packages] [Bug 1988346] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612790/+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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation 'sleep'
[Kernel-packages] [Bug 1988346] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612791/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug
[Kernel-packages] [Bug 1988346] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612782/+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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation 'sleep'
[Kernel-packages] [Bug 1988346] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612783/+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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation 'sleep'
[Kernel-packages] [Bug 1988346] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612781/+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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation 'sleep'
[Kernel-packages] [Bug 1988346] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612778/+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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation 'sleep' finished.
[Kernel-packages] [Bug 1988346] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612776/+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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation
[Kernel-packages] [Bug 1988346] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612779/+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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation 'sleep'
[Kernel-packages] [Bug 1988346] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612777/+files/IwConfig.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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation 'sleep'
[Kernel-packages] [Bug 1988346] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612780/+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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation 'sleep' finished.
[Kernel-packages] [Bug 1988346] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1988346/+attachment/5612775/+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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation 'sleep' finished.
[Kernel-packages] [Bug 1988352] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1988352 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988352 Title: focal autopkgtests for hwe-5.11, hwe-5.13 and hwe-5.15 time out on arm Status in linux package in Ubuntu: Incomplete Bug description: While looking to fix some focal-proposed migrations for zlib, I've noticed these regressions: autopkgtest for linux-hwe-5.11/5.11.0-61.61: amd64: Pass, arm64: Pass, armhf: Regression ♻ , ppc64el: Pass, s390x: Pass autopkgtest for linux-hwe-5.13/5.13.0-52.59~20.04.1: amd64: Pass, arm64: Pass, armhf: Regression ♻ , ppc64el: Pass, s390x: Pass autopkgtest for linux-hwe-5.15/5.15.0-45.48~20.04.1: amd64: Pass, arm64: Regression ♻ , armhf: Regression ♻ , ppc64el: Pass, s390x: Pass They all fail due to timeouts, but worked fine on a local test. I've noticed then that earlier version of hwe kernels (hwe-5.0 and hwe-5.4) were already added to long_tests in autopkgtest-package-configs for armhf. So I think the timeouts can be solved by adding the newer hwe kernels there, too: linux-hwe-5.11/armhf linux-hwe-5.13/armhf linux-hwe-5.15/armhf linux-hwe-5.15/arm6 I've create an MP for this ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988352/+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 1988346] Re: cm32181 module error blocking suspend
apport information ** Tags added: apport-collected jammy wayland-session ** Description changed: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation 'sleep' finished. ``` I think the problem is: > Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 > Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 This issue occurs in kernels: * 5.15.0-47-generic *
[Kernel-packages] [Bug 1988353] [NEW] Jammy update: v5.15.57 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.57 upstream stable release from git://git.kernel.org/ x86/xen: Fix initialisation in hypercall_page after rethunk tools arch x86: Sync the msr-index.h copy with the kernel sources tools headers cpufeatures: Sync with the kernel sources um: Add missing apply_returns() x86: Use -mindirect-branch-cs-prefix for RETPOLINE builds Linux 5.15.57 UBUNTU: Upstream stable to v5.15.57 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - 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: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.15.57 upstream stable release + from git://git.kernel.org/ -v5.15.57 upstream stable release -from git://git.kernel.org/ + x86/xen: Fix initialisation in hypercall_page after rethunk + tools arch x86: Sync the msr-index.h copy with the kernel sources + tools headers cpufeatures: Sync with the kernel sources + um: Add missing apply_returns() + x86: Use -mindirect-branch-cs-prefix for RETPOLINE builds + Linux 5.15.57 + UBUNTU: Upstream stable to v5.15.57 -- 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/1988353 Title: Jammy update: v5.15.57 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.57 upstream stable release from git://git.kernel.org/ x86/xen: Fix initialisation in hypercall_page after rethunk tools arch x86: Sync the msr-index.h copy with the kernel sources tools headers cpufeatures: Sync with the kernel sources um: Add missing apply_returns() x86: Use -mindirect-branch-cs-prefix for RETPOLINE builds Linux 5.15.57 UBUNTU: Upstream stable to v5.15.57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988353/+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 1988352] [NEW] focal autopkgtests for hwe-5.11, hwe-5.13 and hwe-5.15 time out on arm
Public bug reported: While looking to fix some focal-proposed migrations for zlib, I've noticed these regressions: autopkgtest for linux-hwe-5.11/5.11.0-61.61: amd64: Pass, arm64: Pass, armhf: Regression ♻ , ppc64el: Pass, s390x: Pass autopkgtest for linux-hwe-5.13/5.13.0-52.59~20.04.1: amd64: Pass, arm64: Pass, armhf: Regression ♻ , ppc64el: Pass, s390x: Pass autopkgtest for linux-hwe-5.15/5.15.0-45.48~20.04.1: amd64: Pass, arm64: Regression ♻ , armhf: Regression ♻ , ppc64el: Pass, s390x: Pass They all fail due to timeouts, but worked fine on a local test. I've noticed then that earlier version of hwe kernels (hwe-5.0 and hwe-5.4) were already added to long_tests in autopkgtest-package-configs for armhf. So I think the timeouts can be solved by adding the newer hwe kernels there, too: linux-hwe-5.11/armhf linux-hwe-5.13/armhf linux-hwe-5.15/armhf linux-hwe-5.15/arm6 I've create an MP for this ... ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse-focal ** Merge proposal linked: https://code.launchpad.net/~fheimes/autopkgtest-cloud/+git/autopkgtest-package-configs/+merge/429252 -- 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/1988352 Title: focal autopkgtests for hwe-5.11, hwe-5.13 and hwe-5.15 time out on arm Status in linux package in Ubuntu: New Bug description: While looking to fix some focal-proposed migrations for zlib, I've noticed these regressions: autopkgtest for linux-hwe-5.11/5.11.0-61.61: amd64: Pass, arm64: Pass, armhf: Regression ♻ , ppc64el: Pass, s390x: Pass autopkgtest for linux-hwe-5.13/5.13.0-52.59~20.04.1: amd64: Pass, arm64: Pass, armhf: Regression ♻ , ppc64el: Pass, s390x: Pass autopkgtest for linux-hwe-5.15/5.15.0-45.48~20.04.1: amd64: Pass, arm64: Regression ♻ , armhf: Regression ♻ , ppc64el: Pass, s390x: Pass They all fail due to timeouts, but worked fine on a local test. I've noticed then that earlier version of hwe kernels (hwe-5.0 and hwe-5.4) were already added to long_tests in autopkgtest-package-configs for armhf. So I think the timeouts can be solved by adding the newer hwe kernels there, too: linux-hwe-5.11/armhf linux-hwe-5.13/armhf linux-hwe-5.15/armhf linux-hwe-5.15/arm6 I've create an MP for this ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988352/+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 1963615] Re: Add proper runtime PM support to Realtek PCIe cardreader
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1016.17 --- linux-oem-5.17 (5.17.0-1016.17) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1016.17 -proposed tracker (LP: #1983905) * drm/i915, turbostat: Support for ADL-N, RPL-P (LP: #1987265) - tools/power turbostat: Introduce support for RaptorLake - tools/power turbostat: Support RAPTORLAKE P - drm/i915/rpl-s: Add stepping info - drm/i915: Add RPL-S PCI IDs - drm/i915/adl-n: Enable ADL-N platform - drm/i915/rpl-p: Add PCI IDs - drm/i915/adl-n: Add PCH Support for Alder Lake N - drm/i915/adl-n: Add stepping info * CVE-2021-33655 - fbcon: Disallow setting font bigger than screen size - fbcon: Prevent that screen size is smaller than font size - fbmem: Check virtual screen sizes in fb_set_var() * Add proper runtime PM support to Realtek PCIe cardreader (LP: #1963615) - misc: rtsx: Rework runtime power management flow - misc: rtsx: Cleanup power management ops - misc: rtsx: Quiesce rts5249 on system suspend - misc: rtsx: conditionally build rtsx_pm_power_saving() - misc: rtsx: rts522a rts5228 rts5261 support Runtime PM * Fix non-working I219 ethernet after s2idle (LP: #1986751) - Revert "e1000e: Fix possible HW unit hang after an s0ix exit" * Fix invalid MAC address after hotplug tbt dock (LP: #1942999) - SAUCE: igc: wait for the MAC copy when enabled MAC passthrough * AMD Rembrandt: DP tunneling fails with Thunderbolt monitors (LP: #1983143) - drm/amd/display: Fix new dmub notification enabling in DM - SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered. * Enable speaker and mute LEDs for HP laptops (LP: #1982990) - ALSA: hda/realtek: Enable speaker and mute LEDs for HP laptops * Fix drm/amd/pm: enable ASPM by default (LP: #1966680) - drm/amd: Refactor `amdgpu_aspm` to be evaluated per device - drm/amd: Use amdgpu_device_should_use_aspm on navi umd pstate switching - drm/amdgpu: vi: disable ASPM on Intel Alder Lake based systems * CVE-2021-33061 - ixgbe: add the ability for the PF to disable VF link state - ixgbe: add improvement for MDD response functionality - ixgbevf: add disable link state [ Ubuntu: 5.17.0-8.8~22.04.8 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.8 -proposed tracker (LP: #1983907) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.08.08) * GPIO character device v1 API not enabled in kernel (LP: #1953613) - [Config] Enable CONFIG_GPIO_CDEV_V1 * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640) - SAUCE: for aufs mmap: print the virtual file path - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9 (LP: #1982716) - ALSA: hda/realtek: fix mute/micmute LEDs for HP machines -- Timo Aaltonen Mon, 22 Aug 2022 13:50:21 +0300 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33061 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33655 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1963615 Title: Add proper runtime PM support to Realtek PCIe cardreader Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] New generations of Realtek PCIe card reader cannot detect card insertion when the device is in PCI D3. [Fix] Rework the runtime PM flow and add chip specific support. [Test] With the series applied, the device can detect card insertion when it's in PCI D3. [Where problems could occur] System wide power management with less usage like hibernation, kexec reboot, etc. are not tested extensively. So these cases may be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1963615/+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 1942999] Re: Fix invalid MAC address after hotplug tbt dock
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1016.17 --- linux-oem-5.17 (5.17.0-1016.17) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1016.17 -proposed tracker (LP: #1983905) * drm/i915, turbostat: Support for ADL-N, RPL-P (LP: #1987265) - tools/power turbostat: Introduce support for RaptorLake - tools/power turbostat: Support RAPTORLAKE P - drm/i915/rpl-s: Add stepping info - drm/i915: Add RPL-S PCI IDs - drm/i915/adl-n: Enable ADL-N platform - drm/i915/rpl-p: Add PCI IDs - drm/i915/adl-n: Add PCH Support for Alder Lake N - drm/i915/adl-n: Add stepping info * CVE-2021-33655 - fbcon: Disallow setting font bigger than screen size - fbcon: Prevent that screen size is smaller than font size - fbmem: Check virtual screen sizes in fb_set_var() * Add proper runtime PM support to Realtek PCIe cardreader (LP: #1963615) - misc: rtsx: Rework runtime power management flow - misc: rtsx: Cleanup power management ops - misc: rtsx: Quiesce rts5249 on system suspend - misc: rtsx: conditionally build rtsx_pm_power_saving() - misc: rtsx: rts522a rts5228 rts5261 support Runtime PM * Fix non-working I219 ethernet after s2idle (LP: #1986751) - Revert "e1000e: Fix possible HW unit hang after an s0ix exit" * Fix invalid MAC address after hotplug tbt dock (LP: #1942999) - SAUCE: igc: wait for the MAC copy when enabled MAC passthrough * AMD Rembrandt: DP tunneling fails with Thunderbolt monitors (LP: #1983143) - drm/amd/display: Fix new dmub notification enabling in DM - SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered. * Enable speaker and mute LEDs for HP laptops (LP: #1982990) - ALSA: hda/realtek: Enable speaker and mute LEDs for HP laptops * Fix drm/amd/pm: enable ASPM by default (LP: #1966680) - drm/amd: Refactor `amdgpu_aspm` to be evaluated per device - drm/amd: Use amdgpu_device_should_use_aspm on navi umd pstate switching - drm/amdgpu: vi: disable ASPM on Intel Alder Lake based systems * CVE-2021-33061 - ixgbe: add the ability for the PF to disable VF link state - ixgbe: add improvement for MDD response functionality - ixgbevf: add disable link state [ Ubuntu: 5.17.0-8.8~22.04.8 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.8 -proposed tracker (LP: #1983907) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.08.08) * GPIO character device v1 API not enabled in kernel (LP: #1953613) - [Config] Enable CONFIG_GPIO_CDEV_V1 * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640) - SAUCE: for aufs mmap: print the virtual file path - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9 (LP: #1982716) - ALSA: hda/realtek: fix mute/micmute LEDs for HP machines -- Timo Aaltonen Mon, 22 Aug 2022 13:50:21 +0300 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33655 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942999 Title: Fix invalid MAC address after hotplug tbt dock Status in HWE Next: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: SRU justification: [Impact] igc driver can not connect to network after re-plugin thunderbolt dock when MAC passthrough enabled in BIOS. [Fix] Wait for the MAC copy of BIOS when enabled MAC passthrough. Intel engineer wants a different solution and promise to discuss with firmware engineer. Due to the schedule, made this as a short term solution to fix the issue, and wait for the other fix from Intel. [Test] Verified on hardware, after hotplug the thunderbolt cable, Ethernet works fine. [Where problems could occur] It may break the igc driver. Intel still doesn't provide any solution about their approach. In the meantime, this patch is still the only fix. Re-submit it to Jammy, oem-5.17 and Unstable kernel. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1966680] Re: Fix drm/amd/pm: enable ASPM by default
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1016.17
---
linux-oem-5.17 (5.17.0-1016.17) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1016.17 -proposed tracker (LP:
#1983905)
* drm/i915, turbostat: Support for ADL-N, RPL-P (LP: #1987265)
- tools/power turbostat: Introduce support for RaptorLake
- tools/power turbostat: Support RAPTORLAKE P
- drm/i915/rpl-s: Add stepping info
- drm/i915: Add RPL-S PCI IDs
- drm/i915/adl-n: Enable ADL-N platform
- drm/i915/rpl-p: Add PCI IDs
- drm/i915/adl-n: Add PCH Support for Alder Lake N
- drm/i915/adl-n: Add stepping info
* CVE-2021-33655
- fbcon: Disallow setting font bigger than screen size
- fbcon: Prevent that screen size is smaller than font size
- fbmem: Check virtual screen sizes in fb_set_var()
* Add proper runtime PM support to Realtek PCIe cardreader (LP: #1963615)
- misc: rtsx: Rework runtime power management flow
- misc: rtsx: Cleanup power management ops
- misc: rtsx: Quiesce rts5249 on system suspend
- misc: rtsx: conditionally build rtsx_pm_power_saving()
- misc: rtsx: rts522a rts5228 rts5261 support Runtime PM
* Fix non-working I219 ethernet after s2idle (LP: #1986751)
- Revert "e1000e: Fix possible HW unit hang after an s0ix exit"
* Fix invalid MAC address after hotplug tbt dock (LP: #1942999)
- SAUCE: igc: wait for the MAC copy when enabled MAC passthrough
* AMD Rembrandt: DP tunneling fails with Thunderbolt monitors (LP: #1983143)
- drm/amd/display: Fix new dmub notification enabling in DM
- SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered.
* Enable speaker and mute LEDs for HP laptops (LP: #1982990)
- ALSA: hda/realtek: Enable speaker and mute LEDs for HP laptops
* Fix drm/amd/pm: enable ASPM by default (LP: #1966680)
- drm/amd: Refactor `amdgpu_aspm` to be evaluated per device
- drm/amd: Use amdgpu_device_should_use_aspm on navi umd pstate switching
- drm/amdgpu: vi: disable ASPM on Intel Alder Lake based systems
* CVE-2021-33061
- ixgbe: add the ability for the PF to disable VF link state
- ixgbe: add improvement for MDD response functionality
- ixgbevf: add disable link state
[ Ubuntu: 5.17.0-8.8~22.04.8 ]
* jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.8 -proposed tracker (LP: #1983907)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.08.08)
* GPIO character device v1 API not enabled in kernel (LP: #1953613)
- [Config] Enable CONFIG_GPIO_CDEV_V1
* refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: for aufs mmap: print the virtual file path
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
* Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP
440/450/640/650 G9 (LP: #1982716)
- ALSA: hda/realtek: fix mute/micmute LEDs for HP machines
-- Timo Aaltonen Mon, 22 Aug 2022
13:50:21 +0300
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33655
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1966680
Title:
Fix drm/amd/pm: enable ASPM by default
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Bug description:
[Impact]
With WX3200 and 20.04d kernel the unit freezes on resume
[Fix]
commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
by default but a variety of hardware configurations it turns out that this
caused a regression.
Multiple SKUs with wx3200 gpus encounter the resume issue.
Before the real fix is landed, revert commit 0064b0ce85bb first.
[Test Case]
1. plug wx3200 on the adl machine and make it as a output.
2. suspend machine
3. check if machine could resume successfully
[Where problems could occur]
Low, don't make AMDGPU ASPM by default.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1966680/+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 1982716] Re: Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1016.17 --- linux-oem-5.17 (5.17.0-1016.17) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1016.17 -proposed tracker (LP: #1983905) * drm/i915, turbostat: Support for ADL-N, RPL-P (LP: #1987265) - tools/power turbostat: Introduce support for RaptorLake - tools/power turbostat: Support RAPTORLAKE P - drm/i915/rpl-s: Add stepping info - drm/i915: Add RPL-S PCI IDs - drm/i915/adl-n: Enable ADL-N platform - drm/i915/rpl-p: Add PCI IDs - drm/i915/adl-n: Add PCH Support for Alder Lake N - drm/i915/adl-n: Add stepping info * CVE-2021-33655 - fbcon: Disallow setting font bigger than screen size - fbcon: Prevent that screen size is smaller than font size - fbmem: Check virtual screen sizes in fb_set_var() * Add proper runtime PM support to Realtek PCIe cardreader (LP: #1963615) - misc: rtsx: Rework runtime power management flow - misc: rtsx: Cleanup power management ops - misc: rtsx: Quiesce rts5249 on system suspend - misc: rtsx: conditionally build rtsx_pm_power_saving() - misc: rtsx: rts522a rts5228 rts5261 support Runtime PM * Fix non-working I219 ethernet after s2idle (LP: #1986751) - Revert "e1000e: Fix possible HW unit hang after an s0ix exit" * Fix invalid MAC address after hotplug tbt dock (LP: #1942999) - SAUCE: igc: wait for the MAC copy when enabled MAC passthrough * AMD Rembrandt: DP tunneling fails with Thunderbolt monitors (LP: #1983143) - drm/amd/display: Fix new dmub notification enabling in DM - SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered. * Enable speaker and mute LEDs for HP laptops (LP: #1982990) - ALSA: hda/realtek: Enable speaker and mute LEDs for HP laptops * Fix drm/amd/pm: enable ASPM by default (LP: #1966680) - drm/amd: Refactor `amdgpu_aspm` to be evaluated per device - drm/amd: Use amdgpu_device_should_use_aspm on navi umd pstate switching - drm/amdgpu: vi: disable ASPM on Intel Alder Lake based systems * CVE-2021-33061 - ixgbe: add the ability for the PF to disable VF link state - ixgbe: add improvement for MDD response functionality - ixgbevf: add disable link state [ Ubuntu: 5.17.0-8.8~22.04.8 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.8 -proposed tracker (LP: #1983907) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.08.08) * GPIO character device v1 API not enabled in kernel (LP: #1953613) - [Config] Enable CONFIG_GPIO_CDEV_V1 * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640) - SAUCE: for aufs mmap: print the virtual file path - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9 (LP: #1982716) - ALSA: hda/realtek: fix mute/micmute LEDs for HP machines -- Timo Aaltonen Mon, 22 Aug 2022 13:50:21 +0300 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1982716 Title: Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9 Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-hwe-5.17 source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] The audio mute key (F5) and mic-mute LED (F8) don't work on some HP 440/450/640/650 G9 laptops. [Fix] The HP ProBook 440/450 G9 and EliteBook 640/650 G9 have multiple motherboard design and they are using different subsystem ID of audio codec. Add the same quirk for other MBs. [Test] After applying the fix, the mute LEDs are working. [Where problems could occur] It's low risk as it's specific ID for HP new machines. If the HP ships other machines using same SSID, then the LED may not work on those machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982716/+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 1982990] Re: Enable speaker and mute LEDs for HP laptops
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1016.17 --- linux-oem-5.17 (5.17.0-1016.17) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1016.17 -proposed tracker (LP: #1983905) * drm/i915, turbostat: Support for ADL-N, RPL-P (LP: #1987265) - tools/power turbostat: Introduce support for RaptorLake - tools/power turbostat: Support RAPTORLAKE P - drm/i915/rpl-s: Add stepping info - drm/i915: Add RPL-S PCI IDs - drm/i915/adl-n: Enable ADL-N platform - drm/i915/rpl-p: Add PCI IDs - drm/i915/adl-n: Add PCH Support for Alder Lake N - drm/i915/adl-n: Add stepping info * CVE-2021-33655 - fbcon: Disallow setting font bigger than screen size - fbcon: Prevent that screen size is smaller than font size - fbmem: Check virtual screen sizes in fb_set_var() * Add proper runtime PM support to Realtek PCIe cardreader (LP: #1963615) - misc: rtsx: Rework runtime power management flow - misc: rtsx: Cleanup power management ops - misc: rtsx: Quiesce rts5249 on system suspend - misc: rtsx: conditionally build rtsx_pm_power_saving() - misc: rtsx: rts522a rts5228 rts5261 support Runtime PM * Fix non-working I219 ethernet after s2idle (LP: #1986751) - Revert "e1000e: Fix possible HW unit hang after an s0ix exit" * Fix invalid MAC address after hotplug tbt dock (LP: #1942999) - SAUCE: igc: wait for the MAC copy when enabled MAC passthrough * AMD Rembrandt: DP tunneling fails with Thunderbolt monitors (LP: #1983143) - drm/amd/display: Fix new dmub notification enabling in DM - SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered. * Enable speaker and mute LEDs for HP laptops (LP: #1982990) - ALSA: hda/realtek: Enable speaker and mute LEDs for HP laptops * Fix drm/amd/pm: enable ASPM by default (LP: #1966680) - drm/amd: Refactor `amdgpu_aspm` to be evaluated per device - drm/amd: Use amdgpu_device_should_use_aspm on navi umd pstate switching - drm/amdgpu: vi: disable ASPM on Intel Alder Lake based systems * CVE-2021-33061 - ixgbe: add the ability for the PF to disable VF link state - ixgbe: add improvement for MDD response functionality - ixgbevf: add disable link state [ Ubuntu: 5.17.0-8.8~22.04.8 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.8 -proposed tracker (LP: #1983907) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.08.08) * GPIO character device v1 API not enabled in kernel (LP: #1953613) - [Config] Enable CONFIG_GPIO_CDEV_V1 * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640) - SAUCE: for aufs mmap: print the virtual file path - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9 (LP: #1982716) - ALSA: hda/realtek: fix mute/micmute LEDs for HP machines -- Timo Aaltonen Mon, 22 Aug 2022 13:50:21 +0300 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1982990 Title: Enable speaker and mute LEDs for HP laptops Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] Speaker and mute LEDs are not working on two HP laptops. [Fix] Use HDA quirk to enable SPI AMP and use GPIO to control LEDs. [Test] With the fix applied, speaker and mute LEDs are working on both laptops. [Where problems could occur] The quirk use very specific, so unless some broken hardwares use the same IDs, there's no potential regression can happen. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982990/+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 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1016.17 --- linux-oem-5.17 (5.17.0-1016.17) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1016.17 -proposed tracker (LP: #1983905) * drm/i915, turbostat: Support for ADL-N, RPL-P (LP: #1987265) - tools/power turbostat: Introduce support for RaptorLake - tools/power turbostat: Support RAPTORLAKE P - drm/i915/rpl-s: Add stepping info - drm/i915: Add RPL-S PCI IDs - drm/i915/adl-n: Enable ADL-N platform - drm/i915/rpl-p: Add PCI IDs - drm/i915/adl-n: Add PCH Support for Alder Lake N - drm/i915/adl-n: Add stepping info * CVE-2021-33655 - fbcon: Disallow setting font bigger than screen size - fbcon: Prevent that screen size is smaller than font size - fbmem: Check virtual screen sizes in fb_set_var() * Add proper runtime PM support to Realtek PCIe cardreader (LP: #1963615) - misc: rtsx: Rework runtime power management flow - misc: rtsx: Cleanup power management ops - misc: rtsx: Quiesce rts5249 on system suspend - misc: rtsx: conditionally build rtsx_pm_power_saving() - misc: rtsx: rts522a rts5228 rts5261 support Runtime PM * Fix non-working I219 ethernet after s2idle (LP: #1986751) - Revert "e1000e: Fix possible HW unit hang after an s0ix exit" * Fix invalid MAC address after hotplug tbt dock (LP: #1942999) - SAUCE: igc: wait for the MAC copy when enabled MAC passthrough * AMD Rembrandt: DP tunneling fails with Thunderbolt monitors (LP: #1983143) - drm/amd/display: Fix new dmub notification enabling in DM - SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered. * Enable speaker and mute LEDs for HP laptops (LP: #1982990) - ALSA: hda/realtek: Enable speaker and mute LEDs for HP laptops * Fix drm/amd/pm: enable ASPM by default (LP: #1966680) - drm/amd: Refactor `amdgpu_aspm` to be evaluated per device - drm/amd: Use amdgpu_device_should_use_aspm on navi umd pstate switching - drm/amdgpu: vi: disable ASPM on Intel Alder Lake based systems * CVE-2021-33061 - ixgbe: add the ability for the PF to disable VF link state - ixgbe: add improvement for MDD response functionality - ixgbevf: add disable link state [ Ubuntu: 5.17.0-8.8~22.04.8 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.8 -proposed tracker (LP: #1983907) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.08.08) * GPIO character device v1 API not enabled in kernel (LP: #1953613) - [Config] Enable CONFIG_GPIO_CDEV_V1 * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640) - SAUCE: for aufs mmap: print the virtual file path - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9 (LP: #1982716) - ALSA: hda/realtek: fix mute/micmute LEDs for HP machines -- Timo Aaltonen Mon, 22 Aug 2022 13:50:21 +0300 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1983143 Title: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Summary] No video output on Thunderbolt monitor. 1. Connect monitor to DUT directly 2. Connect monitor to DUT via Docking System can detect the monitor and able to change display mode but no output on the monitor [Steps to reproduce] 1. Boot to OS 2. Plug an external monitor via thunderbolt port [Expected result] Display on external monitor normally [Actual result] No vidoe ouput on external monitor [Failure rate] 3/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983143/+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 1987265] Re: drm/i915, turbostat: Support for ADL-N, RPL-P
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1016.17 --- linux-oem-5.17 (5.17.0-1016.17) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1016.17 -proposed tracker (LP: #1983905) * drm/i915, turbostat: Support for ADL-N, RPL-P (LP: #1987265) - tools/power turbostat: Introduce support for RaptorLake - tools/power turbostat: Support RAPTORLAKE P - drm/i915/rpl-s: Add stepping info - drm/i915: Add RPL-S PCI IDs - drm/i915/adl-n: Enable ADL-N platform - drm/i915/rpl-p: Add PCI IDs - drm/i915/adl-n: Add PCH Support for Alder Lake N - drm/i915/adl-n: Add stepping info * CVE-2021-33655 - fbcon: Disallow setting font bigger than screen size - fbcon: Prevent that screen size is smaller than font size - fbmem: Check virtual screen sizes in fb_set_var() * Add proper runtime PM support to Realtek PCIe cardreader (LP: #1963615) - misc: rtsx: Rework runtime power management flow - misc: rtsx: Cleanup power management ops - misc: rtsx: Quiesce rts5249 on system suspend - misc: rtsx: conditionally build rtsx_pm_power_saving() - misc: rtsx: rts522a rts5228 rts5261 support Runtime PM * Fix non-working I219 ethernet after s2idle (LP: #1986751) - Revert "e1000e: Fix possible HW unit hang after an s0ix exit" * Fix invalid MAC address after hotplug tbt dock (LP: #1942999) - SAUCE: igc: wait for the MAC copy when enabled MAC passthrough * AMD Rembrandt: DP tunneling fails with Thunderbolt monitors (LP: #1983143) - drm/amd/display: Fix new dmub notification enabling in DM - SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered. * Enable speaker and mute LEDs for HP laptops (LP: #1982990) - ALSA: hda/realtek: Enable speaker and mute LEDs for HP laptops * Fix drm/amd/pm: enable ASPM by default (LP: #1966680) - drm/amd: Refactor `amdgpu_aspm` to be evaluated per device - drm/amd: Use amdgpu_device_should_use_aspm on navi umd pstate switching - drm/amdgpu: vi: disable ASPM on Intel Alder Lake based systems * CVE-2021-33061 - ixgbe: add the ability for the PF to disable VF link state - ixgbe: add improvement for MDD response functionality - ixgbevf: add disable link state [ Ubuntu: 5.17.0-8.8~22.04.8 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.8 -proposed tracker (LP: #1983907) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.08.08) * GPIO character device v1 API not enabled in kernel (LP: #1953613) - [Config] Enable CONFIG_GPIO_CDEV_V1 * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640) - SAUCE: for aufs mmap: print the virtual file path - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9 (LP: #1982716) - ALSA: hda/realtek: fix mute/micmute LEDs for HP machines -- Timo Aaltonen Mon, 22 Aug 2022 13:50:21 +0300 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33061 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33655 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987265 Title: drm/i915, turbostat: Support for ADL-N, RPL-P Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] We're missing support for ADL-N/RPL-P and some RPL-S pci-id's. [Test case] Boot a system with these pci-id's, see that graphics now work [What could go wrong] These are new pci-id's, no change for current platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1987265/+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 1986751] Re: Fix non-working I219 ethernet after s2idle
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1016.17 --- linux-oem-5.17 (5.17.0-1016.17) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1016.17 -proposed tracker (LP: #1983905) * drm/i915, turbostat: Support for ADL-N, RPL-P (LP: #1987265) - tools/power turbostat: Introduce support for RaptorLake - tools/power turbostat: Support RAPTORLAKE P - drm/i915/rpl-s: Add stepping info - drm/i915: Add RPL-S PCI IDs - drm/i915/adl-n: Enable ADL-N platform - drm/i915/rpl-p: Add PCI IDs - drm/i915/adl-n: Add PCH Support for Alder Lake N - drm/i915/adl-n: Add stepping info * CVE-2021-33655 - fbcon: Disallow setting font bigger than screen size - fbcon: Prevent that screen size is smaller than font size - fbmem: Check virtual screen sizes in fb_set_var() * Add proper runtime PM support to Realtek PCIe cardreader (LP: #1963615) - misc: rtsx: Rework runtime power management flow - misc: rtsx: Cleanup power management ops - misc: rtsx: Quiesce rts5249 on system suspend - misc: rtsx: conditionally build rtsx_pm_power_saving() - misc: rtsx: rts522a rts5228 rts5261 support Runtime PM * Fix non-working I219 ethernet after s2idle (LP: #1986751) - Revert "e1000e: Fix possible HW unit hang after an s0ix exit" * Fix invalid MAC address after hotplug tbt dock (LP: #1942999) - SAUCE: igc: wait for the MAC copy when enabled MAC passthrough * AMD Rembrandt: DP tunneling fails with Thunderbolt monitors (LP: #1983143) - drm/amd/display: Fix new dmub notification enabling in DM - SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered. * Enable speaker and mute LEDs for HP laptops (LP: #1982990) - ALSA: hda/realtek: Enable speaker and mute LEDs for HP laptops * Fix drm/amd/pm: enable ASPM by default (LP: #1966680) - drm/amd: Refactor `amdgpu_aspm` to be evaluated per device - drm/amd: Use amdgpu_device_should_use_aspm on navi umd pstate switching - drm/amdgpu: vi: disable ASPM on Intel Alder Lake based systems * CVE-2021-33061 - ixgbe: add the ability for the PF to disable VF link state - ixgbe: add improvement for MDD response functionality - ixgbevf: add disable link state [ Ubuntu: 5.17.0-8.8~22.04.8 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.8 -proposed tracker (LP: #1983907) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.08.08) * GPIO character device v1 API not enabled in kernel (LP: #1953613) - [Config] Enable CONFIG_GPIO_CDEV_V1 * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640) - SAUCE: for aufs mmap: print the virtual file path - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9 (LP: #1982716) - ALSA: hda/realtek: fix mute/micmute LEDs for HP machines -- Timo Aaltonen Mon, 22 Aug 2022 13:50:21 +0300 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33061 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33655 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1986751 Title: Fix non-working I219 ethernet after s2idle Status in HWE Next: New Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] I219 may stop working after s2idle. The link is up but failed to get an IP address from DHCP server. [Fix] Revert the workaround patch "e1000e: Fix possible HW unit hang after an s0ix exit" so the new fix "e1000e: Enable GPT clock before sending message to CSME" can work. [Test] With the patch applied, the I219 device always get ip address and all the functionalities are working. [Where problems could occur] It's really hard to say since the interaction between I219 and Intel ME is very arcane. The good thing is that the fix is limited to e1000e. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1986751/+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 1988351] [NEW] Jammy update: v5.15.56 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.56 upstream stable release
from git://git.kernel.org/
ALSA: hda - Add fixup for Dell Latitidue E5430
ALSA: hda/conexant: Apply quirk for another HP ProDesk 600 G3 model
ALSA: hda/realtek: Fix headset mic for Acer SF313-51
ALSA: hda/realtek - Fix headset mic problem for a HP machine with alc671
ALSA: hda/realtek - Fix headset mic problem for a HP machine with alc221
ALSA: hda/realtek - Enable the headset-mic on a Xiaomi's laptop
xen/netback: avoid entering xenvif_rx_next_skb() with an empty rx queue
fix race between exit_itimers() and /proc/pid/timers
mm: userfaultfd: fix UFFDIO_CONTINUE on fallocated shmem pages
mm: split huge PUD on wp_huge_pud fallback
tracing/histograms: Fix memory leak problem
net: sock: tracing: Fix sock_exceed_buf_limit not to dereference stale pointer
ip: fix dflt addr selection for connected nexthop
ARM: 9213/1: Print message about disabled Spectre workarounds only once
ARM: 9214/1: alignment: advance IT state after emulating Thumb instruction
wifi: mac80211: fix queue selection for mesh/OCB interfaces
cgroup: Use separate src/dst nodes when preloading css_sets for migration
btrfs: return -EAGAIN for NOWAIT dio reads/writes on compressed and inline
extents
drm/panfrost: Put mapping instead of shmem obj on panfrost_mmu_map_fault_addr()
error
drm/panfrost: Fix shrinker list corruption by madvise IOCTL
fs/remap: constrain dedupe of EOF blocks
nilfs2: fix incorrect masking of permission flags for symlinks
sh: convert nommu io{re,un}map() to static inline functions
Revert "evm: Fix memleak in init_desc"
xfs: only run COW extent recovery when there are no live extents
xfs: don't include bnobt blocks when reserving free block pool
xfs: run callbacks before waking waiters in xlog_state_shutdown_callbacks
xfs: drop async cache flushes from CIL commits.
reset: Fix devm bulk optional exclusive control getter
ARM: dts: imx6qdl-ts7970: Fix ngpio typo and count
spi: amd: Limit max transfer and message size
ARM: 9209/1: Spectre-BHB: avoid pr_info() every time a CPU comes out of idle
ARM: 9210/1: Mark the FDT_FIXED sections as shareable
net/mlx5e: kTLS, Fix build time constant test in TX
net/mlx5e: kTLS, Fix build time constant test in RX
net/mlx5e: Fix enabling sriov while tc nic rules are offloaded
net/mlx5e: Fix capability check for updating vnic env counters
net/mlx5e: Ring the TX doorbell on DMA errors
drm/i915: fix a possible refcount leak in intel_dp_add_mst_connector()
ima: Fix a potential integer overflow in ima_appraise_measurement
ASoC: sgtl5000: Fix noise on shutdown/remove
ASoC: tas2764: Add post reset delays
ASoC: tas2764: Fix and extend FSYNC polarity handling
ASoC: tas2764: Correct playback volume range
ASoC: tas2764: Fix amp gain register offset & default
ASoC: Intel: Skylake: Correct the ssp rate discovery in skl_get_ssp_clks()
ASoC: Intel: Skylake: Correct the handling of fmt_config flexible array
net: stmmac: dwc-qos: Disable split header for Tegra194
net: ethernet: ti: am65-cpsw: Fix devlink port register sequence
sysctl: Fix data races in proc_dointvec().
sysctl: Fix data races in proc_douintvec().
sysctl: Fix data races in proc_dointvec_minmax().
sysctl: Fix data races in proc_douintvec_minmax().
sysctl: Fix data races in proc_doulongvec_minmax().
sysctl: Fix data races in proc_dointvec_jiffies().
tcp: Fix a data-race around sysctl_tcp_max_orphans.
inetpeer: Fix data-races around sysctl.
net: Fix data-races around sysctl_mem.
cipso: Fix data-races around sysctl.
icmp: Fix data-races around sysctl.
ipv4: Fix a data-race around sysctl_fib_sync_mem.
ARM: dts: at91: sama5d2: Fix typo in i2s1 node
ARM: dts: sunxi: Fix SPI NOR campatible on Orange Pi Zero
arm64: dts: broadcom: bcm4908: Fix timer node for BCM4906 SoC
arm64: dts: broadcom: bcm4908: Fix cpu node for smp boot
netfilter: nf_log: incorrect offset to network header
netfilter: nf_tables: replace BUG_ON by element length check
drm/i915/gvt: IS_ERR() vs NULL bug in intel_gvt_update_reg_whitelist()
xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE
lockd: set fl_owner when unlocking files
lockd: fix nlm_close_files
tracing: Fix sleeping while atomic in kdb ftdump
drm/i915/selftests: fix a couple IS_ERR() vs NULL tests
drm/i915/dg2: Add Wa_22011100796
drm/i915/gt: Serialize GRDOM access between multiple engine resets
drm/i915/gt: Serialize TLB invalidates with GT resets
drm/i915/uc: correctly track uc_fw init failure
drm/i915: Require the vm mutex for i915_vma_bind()
bnxt_en: Fix bnxt_reinit_after_abort() code path
bnxt_en: Fix
[Kernel-packages] [Bug 1988346] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1988346 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Incomplete Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]:
[Kernel-packages] [Bug 1988346] [NEW] cm32181 module error blocking suspend
Public bug reported: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation 'sleep' finished. ``` I think the problem is: > Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): > acpi_subsys_suspend+0x0/0x60 returns -121 > Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to > suspend: error -121 This issue occurs in kernels: * 5.15.0-47-generic * Ubuntu 5.15.0-48.54-generic 5.15.53 Description:Ubuntu 22.04.1 LTS Release:22.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added:
[Kernel-packages] [Bug 1967721] Re: Laptop never resuming from standby
Confirmed that on a Thinkpad X260 with 5.15.0-46 suspend works fine. Thanks -- 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/1967721 Title: Laptop never resuming from standby Status in linux package in Ubuntu: Confirmed Bug description: On a Lenovo Thinkpad X260 with 22.04 and 5.15.0-23-generic kernel, after suspending the laptop, it's never possible to wake it up. Neither keyboard nor power button work, only way is to long-press to force poweroff and restart. This did not happen with 21.10. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 08:30:52 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967721/+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 1988338] [NEW] Jammy update: v5.15.55 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.55 upstream stable release from git://git.kernel.org/ NOTE This patch set (v5.15.55) is empty; it contained only one revert: Revert "mtd: rawnand: gpmi: Fix setting busy timeout setting" which was never applied to Jammy. Linux 5.15.55 UBUNTU: Upstream stable to v5.15.55 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Description changed: + SRU Justification - 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: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.15.55 upstream stable release + from git://git.kernel.org/ -v5.15.55 upstream stable release -from git://git.kernel.org/ + NOTE + This patch set (v5.15.55) is empty; it contained only one revert: + Revert "mtd: rawnand: gpmi: Fix setting busy timeout setting" + which was never applied to Jammy. + + Linux 5.15.55 + UBUNTU: Upstream stable to v5.15.55 ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.55 upstream stable release from git://git.kernel.org/ - NOTE - This patch set (v5.15.55) is empty; it contained only one revert: - Revert "mtd: rawnand: gpmi: Fix setting busy timeout setting" - which was never applied to Jammy. + NOTE + This patch set (v5.15.55) is empty; it contained only one revert: + Revert "mtd: rawnand: gpmi: Fix setting busy timeout setting" + which was never applied to Jammy. Linux 5.15.55 UBUNTU: Upstream stable to v5.15.55 -- 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/1988338 Title: Jammy update: v5.15.55 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.55 upstream stable release from git://git.kernel.org/ NOTE This patch set (v5.15.55) is empty; it contained only one revert: Revert "mtd: rawnand: gpmi: Fix setting busy timeout setting" which was never applied to Jammy.
[Kernel-packages] [Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
I am confirming *no more need* of `pci=nocrs` after latest update.
debug info:
```
$ uname -a
Linux SPIN5 5.19.0-76051900-generic #202207312230~1660780566~22.04~9d60db1 SMP
PREEMPT_DYNAMIC Thu A x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Pop
Description:Pop!_OS 22.04 LTS
Release:22.04
Codename: jammy
```
thanks a lot to everyone! :heart:
--
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/1884232
Title:
touchpad and touchscreen doesn't work at all on ACER Spin 5
(SP513-54N)
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
E820 reserved retire memory window, and make other hot-added devices unable
to get the required memory window.
[Fix]
It only can be fixed by a list of quirk to mark those machines out, and
requires below commits from v5.19-rc1 and v5.19-rc3
a2b36ffbf5b6 x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820
regions"
d341838d776a x86/PCI: Disable E820 reserved region clipping via quirks
fa6dae5d8208 x86/PCI: Add kernel cmdline options to use/ignore E820 reserved
regions
4c5e242d3e93 x86/PCI: Clip only host bridge windows for E820 regions
31bf0f433325 x86: Log resource clipping for E820 regions
93d256cd3c1e x86/PCI: Eliminate remove_e820_regions() common subexpressions
[Test]
Verified by the bug reporter.
[Where problems could occur]
The 6 commits are all clean cherry-picked, and the sixth commit reverts the
third commit which are the 2 commits that do real functional changes.
a2b36ffbf5b6 ("x86/PCI: Revert \"x86/PCI: Clip only host bridge windows for
E820 regions\"")
4c5e242d3e93 ("x86/PCI: Clip only host bridge windows for E820 regions")
The fourth and and fifth commits introduce a new quirk to ignore E820
reserved regions and the quirk only affects the listed machines.
Drivers that operates E820 table may fail if we ignore the E820 regions, but
it should have no impact on the listed consumer PCs.
===
Touchpad is not working at all on ACER Spin 5 SP513-54N.
According to
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
I am creating this kernel bug issue.
There are more issues, too, like touchscreen not working and Ubuntu
not installable - see here if interrested
https://askubuntu.com/questions/1251719/
I would like to run Ubuntu on this machine and I am willing to help
with any debug or kernel tweaking... Please let me know.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 4195 F pulseaudio
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 19 10:44:58 2020
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Spin SP513-54N
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
RelatedPackageVersions:
linux-restricted-modules-5.4.0-26-generic N/A
linux-backports-modules-5.4.0-26-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2020
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.00
dmi.board.name: Caboom_IL
dmi.board.vendor: IL
dmi.board.version: V1.00
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.00
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
dmi.product.family: Spin 5
dmi.product.name: Spin SP513-54N
dmi.product.sku:
dmi.product.version: V1.00
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+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 1984103] Comment bridged from LTC Bugzilla
--- Comment From sig...@de.ibm.com 2022-08-31 12:47 EDT---
new test kernel works as expected:
Linux version 5.15.0-47-generic
# grep qcrdinfo /5.15.0-48-genericsys/kernel/debug/s390dbf/qeth*/hex_ascii |
wc -l
7
# ethtool encbd00 | grep Duplex
Duplex: Full
# grep qcrdinfo /sys/kernel/debug/s390dbf/qeth*/hex_ascii | wc -l
9
afterupdate to Linux version 5.15.0-48-generic
# grep qcrdinfo /sys/kernel/debug/s390dbf/qeth*/hex_ascii | wc -l
0
# ethtool encbd00 | grep Duplex
Duplex: Full
# grep qcrdinfo /sys/kernel/debug/s390dbf/qeth*/hex_ascii | wc -l
0
# ethtool encbd00
Settings for encbd00:
Supported ports: [ FIBRE ]
Supported link modes: 1baseSR/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 1baseSR/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1Mb/s
Duplex: Full
Auto-negotiation: on
Port: FIBRE
PHYAD: 0
Transceiver: internal
Link detected: yes
--
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/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Status in Ubuntu on IBM z Systems:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Confirmed
Status in linux source package in Kinetic:
Confirmed
Bug description:
== Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 ==
+++ This bug was initially created as a clone of Bug #199319 +++
Description: s390/qeth: cache link_info for ethtool
Symptom: lost of IP connection and log entries in journalctl:
kernel: qeth 0.0.0365: The qeth device driver failed to
recover an error on the device
Problem: Since commit e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
there was a timing window during recovery, that
qeth_query_card_info could be sent to the card, even before it
was ready for it, leading to a failing card recovery. There is
evidence that this window was hit, as not all callers of
get_link_ksettings() check for netif_device_present.
Solution: Use cached values in qeth_get_link_ksettings(), instead of
calling qeth_query_card_info() and falling back to default
values in case it fails. Link info is already updated when the
card goes online, e.g. after STARTLAN (physical link up). Set
the link info to default values, when the card goes offline or
at STOPLAN (physical link down). A follow-on patch will improve
values reported for link down.
Fixes: e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
Reproduction: enforce a eth device recvoery, while running ethtool multiple
times in parallel and using iperf to get load on the interface.
Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
applicable for most kernel > 3.14
== Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 ==
the inital update came in with kernel 5.1 upstream, but we found it
backported in many older kernel versions
== Comment: #4 - J?rn Siglen - 2022-08-09 08:03:09 ==
the acceptance info of the patch can be found here:
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+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 1988209] Re: application does not display anything
Downgrading nvidia-settings to either of the versions listed below did not change anything. 470.57.01-0ubuntu0.20.04.1 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages *** 440.64-0ubuntu1 500 500 http://192.168.10.7/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1988209 Title: application does not display anything Status in nvidia-settings package in Ubuntu: New Bug description: I just did a fresh install of Ubuntu 20.04.5 and the when launching nvidia-settings the GUI does not display anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-settings 470.57.01-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 30 11:06:06 2022 InstallationDate: Installed on 2022-08-30 (0 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220829.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1988209/+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 1983293] Re: Speaker sound no longer working after 22.04 upgrade on Lenovo X1 Carbon 9Gen
I've had this issue using Ubuntu 20.04 as installed when my Carbon X1 gen9 was delivered Nov 2021. It persists after updating to Ubuntu 21.10 and 22.04. More recently, I've tried the 5.15-generic kernel and currently using the 5.17-oem kernel on 22.04. (No changes to sound quality.) There was a suggestion that it might be a wonky firmware-sof-signed in 21.10 (see #1956215), but Ubuntu 22.04 has moved beyond the 1.7 version of the firmware that was giving install errors. firmware-sof-signed/jammy-updates,jammy-updates,now 2.0-1ubuntu3 all [installed,automatic] $ uname -a 5.17.0-1015-oem #16-Ubuntu SMP PREEMPT x86_64 x86_64 x86_64 GNU/Linux $ lspci | grep -i audio $ aplay -l are identical to this report, and dmidecode shows the same hardware > dmi.product.family: ThinkPad X1 Carbon Gen 9 > dmi.product.name: 20XWCTO1WW I tried a bunch of approaches that did not fix the audio, see https://forums.lenovo.com/t5/Ubuntu/Carbon-X1-Gen9-missing-Bass-speakers/m-p/5116727 The "EasyEffects" solution improves sound quality, but does not fix the issue that the sound plays for approximately 1 second at the correct volume before cutting out to nearly inaudible. A nice tweak once this underlying issue is resolved. Glad some people have figured out whatever fix was necessary, even if it was temporary! Gives me hope. -- 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/1983293 Title: Speaker sound no longer working after 22.04 upgrade on Lenovo X1 Carbon 9Gen Status in linux package in Ubuntu: Confirmed Bug description: After an upgrade to 22.04 my speakers no longer function properly. With the volume at 153% in pavucontrol I can barely hear it (need to put my ear almost next to the speaker). I remember I had the same issue after a fresh install of 21.04 back in December, but I can no longer recall how I fixed it. uname -a 5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux lspci | grep -i audio 00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20) aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 0/1 Subdevice #0: subdevice #0 alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, see screenshot. DAC1 and DAC2 control left and right speaker respectively (when at 0 can not hear anything even with my ear at the speaker). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graphite 2307 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-04 (209 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20XWCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: wayland-session jammy Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss _MarkForUpload: True dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9
[Kernel-packages] [Bug 1988209] Re: application does not display anything
** Tags added: cuqa-manual-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1988209 Title: application does not display anything Status in nvidia-settings package in Ubuntu: New Bug description: I just did a fresh install of Ubuntu 20.04.5 and the when launching nvidia-settings the GUI does not display anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-settings 470.57.01-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 30 11:06:06 2022 InstallationDate: Installed on 2022-08-30 (0 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220829.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1988209/+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 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
Still present in 5.15.0-48-generic 8/31/22 8:01 AM kernel 8/31/22 8:01 AM kernel UBSAN: array-index-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/net/ethernet/aquantia/atlantic/aq_nic.c:1262:48 8/31/22 8:01 AM kernel index 8 is out of range for type 'aq_vec_s *[8]' 8/31/22 8:01 AM kernel CPU: 22 PID: 1987 Comm: daemon-init Tainted: G O 5.15.0-48-generic #54-Ubuntu 8/31/22 8:01 AM kernel Hardware name: To Be Filled By O.E.M. X570 Creator/X570 Creator, BIOS P3.72 05/17/2022 8/31/22 8:01 AM kernel Call Trace: 8/31/22 8:01 AM kernel 8/31/22 8:01 AM kernel show_stack+0x52/0x5c 8/31/22 8:01 AM kernel dump_stack_lvl+0x4a/0x63 8/31/22 8:01 AM kernel dump_stack+0x10/0x16 8/31/22 8:01 AM kernel ubsan_epilogue+0x9/0x49 8/31/22 8:01 AM kernel __ubsan_handle_out_of_bounds.cold+0x44/0x49 8/31/22 8:01 AM kernel ? netdev_has_any_upper_dev+0x48/0x70 8/31/22 8:01 AM kernel ? aq_vec_stop+0x72/0x80 [atlantic] 8/31/22 8:01 AM kernel aq_nic_stop+0x10a/0x110 [atlantic] 8/31/22 8:01 AM kernel aq_ndev_set_features+0x143/0x1a0 [atlantic] 8/31/22 8:01 AM kernel __netdev_update_features+0x184/0x820 8/31/22 8:01 AM kernel dev_disable_lro+0x34/0x150 8/31/22 8:01 AM kernel devinet_sysctl_forward+0x1fb/0x230 8/31/22 8:01 AM kernel proc_sys_call_handler+0x16a/0x2f0 8/31/22 8:01 AM kernel proc_sys_write+0x13/0x20 8/31/22 8:01 AM kernel new_sync_write+0x117/0x1b0 8/31/22 8:01 AM kernel vfs_write+0x1d5/0x270 8/31/22 8:01 AM kernel ksys_write+0x67/0xf0 8/31/22 8:01 AM kernel __x64_sys_write+0x19/0x20 8/31/22 8:01 AM kernel do_syscall_64+0x5c/0xc0 8/31/22 8:01 AM kernel ? exit_to_user_mode_prepare+0x37/0xb0 8/31/22 8:01 AM kernel ? syscall_exit_to_user_mode+0x27/0x50 8/31/22 8:01 AM kernel ? do_syscall_64+0x69/0xc0 8/31/22 8:01 AM kernel entry_SYSCALL_64_after_hwframe+0x61/0xcb 8/31/22 8:01 AM kernel RIP: 0033:0x7fdfff746a6f 8/31/22 8:01 AM kernel Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 19 c0 f7 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 5c c0 f7 ff 48 8/31/22 8:01 AM kernel RSP: 002b:7fdfc37fd810 EFLAGS: 0293 ORIG_RAX: 0001 8/31/22 8:01 AM kernel RAX: ffda RBX: 0002 RCX: 7fdfff746a6f 8/31/22 8:01 AM kernel RDX: 0002 RSI: 7fecf5e5 RDI: 0013 8/31/22 8:01 AM kernel RBP: 7fecf5e5 R08: R09: 0001 8/31/22 8:01 AM kernel R10: R11: 0293 R12: 0013 8/31/22 8:01 AM kernel R13: 0013 R14: R15: 7fdfb4024b50 8/31/22 8:01 AM kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1988322] [NEW] RM 418-server LRM and demote to multiverse
Public bug reported: 418-server is EOL by nvidia upstream however, there is a small number of cards (<<10%, ~40+) that are only supported by 418-server driver and are not supported by any later *-server driver versions. the plan is to stop building LRM for 418-server, not declare transitionals for it, make it dkms-only driver and provide it multiverse, with only the modaliases that are unique to it. this makes 418-server drivers a dead-end w.r.t. LRM transitionals. Please remove the following binary packages only: linux-modules-nvidia-418-server-5.15.0-1003-azure/kinetic 5.15.0-1003.4 amd64 linux-modules-nvidia-418-server-5.15.0-1003-oracle/kinetic 5.15.0-1003.5 amd64 linux-modules-nvidia-418-server-5.15.0-1004-aws/kinetic 5.15.0-1004.6 amd64 linux-modules-nvidia-418-server-5.15.0-1004-gcp/kinetic 5.15.0-1004.7 amd64 linux-modules-nvidia-418-server-5.15.0-1004-intel-iotg/kinetic-proposed 5.15.0-1004.6 amd64 linux-modules-nvidia-418-server-5.15.0-24-lowlatency/kinetic 5.15.0-24.24 amd64 linux-modules-nvidia-418-server-5.15.0-27-generic/kinetic 5.15.0-27.28 amd64 linux-modules-nvidia-418-server-5.17.0-1003-oem/kinetic-proposed 5.17.0-1003.3+1 amd64 linux-modules-nvidia-418-server-aws/kinetic 5.15.0-1004.6 amd64 linux-modules-nvidia-418-server-azure/kinetic 5.15.0-1003.4 amd64 linux-modules-nvidia-418-server-gcp/kinetic 5.15.0-1004.7 amd64 linux-modules-nvidia-418-server-generic/kinetic 5.15.0-27.28 amd64 linux-modules-nvidia-418-server-generic-hwe-20.04/kinetic 5.15.0-27.28 amd64 linux-modules-nvidia-418-server-generic-hwe-20.04-edge/kinetic 5.15.0-27.28 amd64 linux-modules-nvidia-418-server-generic-hwe-22.04/kinetic 5.15.0-27.28 amd64 linux-modules-nvidia-418-server-generic-hwe-22.04-edge/kinetic 5.15.0-27.28 amd64 linux-modules-nvidia-418-server-intel-iotg/kinetic-proposed 5.15.0-1004.6 amd64 linux-modules-nvidia-418-server-lowlatency/kinetic 5.15.0-24.24 amd64 linux-modules-nvidia-418-server-lowlatency-hwe-20.04/kinetic-proposed 5.19.0-1003.3+1 amd64 linux-modules-nvidia-418-server-lowlatency-hwe-20.04-edge/kinetic-proposed 5.19.0-1003.3+1 amd64 linux-modules-nvidia-418-server-lowlatency-hwe-22.04/kinetic 5.15.0-24.24 amd64 linux-modules-nvidia-418-server-lowlatency-hwe-22.04-edge/kinetic 5.15.0-24.24 amd64 linux-modules-nvidia-418-server-oem-22.04/kinetic-proposed 5.17.0-1003.3+1 amd64 linux-modules-nvidia-418-server-oem-22.04a/kinetic-proposed 5.17.0-1003.3+1 amd64 linux-modules-nvidia-418-server-oracle/kinetic 5.15.0-1003.5 amd64 linux-objects-nvidia-418-server-5.15.0-1003-azure/kinetic 5.15.0-1003.4 amd64 linux-objects-nvidia-418-server-5.15.0-1003-oracle/kinetic 5.15.0-1003.5 amd64 linux-objects-nvidia-418-server-5.15.0-1004-aws/kinetic 5.15.0-1004.6 amd64 linux-objects-nvidia-418-server-5.15.0-1004-gcp/kinetic 5.15.0-1004.7 amd64 linux-objects-nvidia-418-server-5.15.0-1004-intel-iotg/kinetic-proposed 5.15.0-1004.6 amd64 linux-objects-nvidia-418-server-5.15.0-24-lowlatency/kinetic 5.15.0-24.24 amd64 linux-objects-nvidia-418-server-5.15.0-27-generic/kinetic 5.15.0-27.28 amd64 linux-objects-nvidia-418-server-5.17.0-1003-oem/kinetic-proposed 5.17.0-1003.3+1 amd64 ** Affects: nvidia-graphics-drivers-418-server (Ubuntu) Importance: Undecided Status: New ** Description changed: 418-server is EOL by nvidia upstream however, there is a small number of cards (<<10%, ~40+) that are only supported by 418-server driver and are not supported by any later *-server driver versions. the plan is to stop building LRM for 418-server, not declare transitionals for it, make it dkms-only driver and provide it multiverse, with only the modaliases that are unique to it. this makes 418-server drivers a dead-end w.r.t. LRM transitionals. + + Please remove the following binary packages only: + + linux-modules-nvidia-418-server-5.15.0-1003-azure/kinetic 5.15.0-1003.4 amd64 + linux-modules-nvidia-418-server-5.15.0-1003-oracle/kinetic 5.15.0-1003.5 amd64 + linux-modules-nvidia-418-server-5.15.0-1004-aws/kinetic 5.15.0-1004.6 amd64 + linux-modules-nvidia-418-server-5.15.0-1004-gcp/kinetic 5.15.0-1004.7 amd64 + linux-modules-nvidia-418-server-5.15.0-1004-intel-iotg/kinetic-proposed 5.15.0-1004.6 amd64 + linux-modules-nvidia-418-server-5.15.0-24-lowlatency/kinetic 5.15.0-24.24 amd64 + linux-modules-nvidia-418-server-5.15.0-27-generic/kinetic 5.15.0-27.28 amd64 + linux-modules-nvidia-418-server-5.17.0-1003-oem/kinetic-proposed 5.17.0-1003.3+1 amd64 + linux-modules-nvidia-418-server-aws/kinetic 5.15.0-1004.6 amd64 + linux-modules-nvidia-418-server-azure/kinetic 5.15.0-1003.4 amd64 + linux-modules-nvidia-418-server-gcp/kinetic 5.15.0-1004.7 amd64 + linux-modules-nvidia-418-server-generic/kinetic 5.15.0-27.28 amd64 + linux-modules-nvidia-418-server-generic-hwe-20.04/kinetic 5.15.0-27.28 amd64 + linux-modules-nvidia-418-server-generic-hwe-20.04-edge/kinetic 5.15.0-27.28 amd64 + linux-modules-nvidia-418-server-generic-hwe-22.04/kinetic 5.15.0-27.28 amd64 +
[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51
> Can this wait until it can be tested properly? Actually this is now. Because the changes not only went into 5.15 but this cycle also into 5.4. See the proposed run compared to current version for the -126 kernel. https://autopkgtest.ubuntu.com/packages/l/lttng-modules/focal/amd64 -- 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/1986921 Title: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Won't Fix Status in lttng-modules package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Won't Fix Status in lttng-modules source package in Jammy: Fix Released Bug description: SRU Justification: Impact: The kernel upstream changed in v5.18 and dropped tracepoints for random. This change was backported to 5.15/jammy in upstream stable 5.15.44. With that the build of lttng-modules-dkms fails. Fix: Backport of an upstream change which checks for the kernel header file which got removed in the process. Additionally the DKMS spec file has to do the same check to be aware of the missing probe module. Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and -47 or later. Currently -47 and later will fail. With the change both should complete. Regression Potential: This changes whether lttng-probe-random.ko is available or not (if it is available the code is unchanged). User- space might be affected if this module is always expected. --- This is a scripted bug report about ADT failures while running lttng- modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1986921/+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 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51
> For focal we can only test the current kernel (hwe-5.15 has not yet picked up the lastest jammy changes because of the upcoming point release) It seems odd to release an SRU without the ability to test what it is fixing. If it turns out not to fix it, we'd have to be doing an SRU again for no good reason. Can this wait until it can be tested properly? -- 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/1986921 Title: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Won't Fix Status in lttng-modules package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Won't Fix Status in lttng-modules source package in Jammy: Fix Released Bug description: SRU Justification: Impact: The kernel upstream changed in v5.18 and dropped tracepoints for random. This change was backported to 5.15/jammy in upstream stable 5.15.44. With that the build of lttng-modules-dkms fails. Fix: Backport of an upstream change which checks for the kernel header file which got removed in the process. Additionally the DKMS spec file has to do the same check to be aware of the missing probe module. Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and -47 or later. Currently -47 and later will fail. With the change both should complete. Regression Potential: This changes whether lttng-probe-random.ko is available or not (if it is available the code is unchanged). User- space might be affected if this module is always expected. --- This is a scripted bug report about ADT failures while running lttng- modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1986921/+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 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter
This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1~18.04.7 --- makedumpfile (1:1.6.5-1ubuntu1~18.04.7) bionic; urgency=medium * debian/rules: Remove "ata_piix.prefer_ms_hyperv=0" (LP: #1978333) -- Heather Lemon Mon, 13 Jun 2022 15:19:39 + -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Released Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Released Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: Fix Released Status in kdump-tools source package in Impish: Invalid Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: Fix Released Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Released Status in makedumpfile source package in Kinetic: Invalid Bug description: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] Create Ubuntu Marketplace VM on Azure ``` ssh -i .ssh/id_rsa ubuntu@ipaddr ``` Install crash dump utilities (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) apt-get install kdump-tools Say (y) to all questions during install kdump-config show *shows the vm is not yet ready to kdump root@bionic3: kdump-config show * no crashkernel= parameter in the kernel cmdline DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:Not ready to kdump kexec command: no kexec command recorded Reboot the VM sudo su As root on the VM after reboot: kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System RAM: 4095MB) cat /proc/sys/kernel/sysrq # make sure this value is greater than 0 #set it to 1 sudo sysctl -w kernel.sysrq=1 the directory of /var/crash should have no crashes yet as well. Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger After a couple of minuties Open new terminal and try to ssh to azure VM, It does not succeed Force a reboot of the VM through the portal or serial console #kdump doesnt work and hangs indefinitely #force reboot VM from Azure console # verify package version of kdump-tool # verify parameter is not listed in the kdump-config show output kdump-config unload kdump-config load kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #trigger another crash echo c > /proc/sysrq-trigger # open new terminal and ssh back into vm cd /var/crash #verify a dump was created linux-image-5.4.0-1086-azure-202208041658.crash [Where Problems Could Occur] This change modifies the debian/rules. The package could fail to build properly if mistyped. [Other] Back-porting a fix from upstream to
[Kernel-packages] [Bug 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter
This bug was fixed in the package makedumpfile - 1:1.6.7-1ubuntu2.4 --- makedumpfile (1:1.6.7-1ubuntu2.4) focal; urgency=low * debian/rules: Remove "ata_piix.prefer_ms_hyperv=0" (LP: #1978333) -- Heather Lemon Mon, 13 Jun 2022 13:59:29 + ** Changed in: makedumpfile (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: makedumpfile (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Released Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Released Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: Fix Released Status in kdump-tools source package in Impish: Invalid Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: Fix Released Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Released Status in makedumpfile source package in Kinetic: Invalid Bug description: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] Create Ubuntu Marketplace VM on Azure ``` ssh -i .ssh/id_rsa ubuntu@ipaddr ``` Install crash dump utilities (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) apt-get install kdump-tools Say (y) to all questions during install kdump-config show *shows the vm is not yet ready to kdump root@bionic3: kdump-config show * no crashkernel= parameter in the kernel cmdline DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:Not ready to kdump kexec command: no kexec command recorded Reboot the VM sudo su As root on the VM after reboot: kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System RAM: 4095MB) cat /proc/sys/kernel/sysrq # make sure this value is greater than 0 #set it to 1 sudo sysctl -w kernel.sysrq=1 the directory of /var/crash should have no crashes yet as well. Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger After a couple of minuties Open new terminal and try to ssh to azure VM, It does not succeed Force a reboot of the VM through the portal or serial console #kdump doesnt work and hangs indefinitely #force reboot VM from Azure console # verify package version of kdump-tool # verify parameter is not listed in the kdump-config show output kdump-config unload kdump-config load kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #trigger another crash echo c > /proc/sysrq-trigger # open new terminal and ssh back into vm cd /var/crash #verify a dump was created
[Kernel-packages] [Bug 1982090] Re: kinetic/linux-raspi: Update to upstream raspberrypi rpi-5.19.y (2022-07-19)
This bug was fixed in the package linux-raspi - 5.19.0-1001.3 --- linux-raspi (5.19.0-1001.3) kinetic; urgency=medium * kinetic/linux-raspi: 5.19.0-1001.3 -proposed tracker (LP: #1982325) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - debian/dkms-versions -- update from kernel-versions (main/master) * Missing overlays/README (LP: #1954757) - SAUCE: Install overlays/README * dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454) - SAUCE: arm: dts: Add 'brcm,bcm2835-pl011' compatible for uart2-5 * kinetic/linux-raspi: Update to upstream raspberrypi rpi-5.19.y (2022-07-19) (LP: #1982090) - arm64: setup: Fix build warning - clk: Drop the rate range on clk_put() - clk: Skip clamping when rounding if there's no boundaries - clk: Introduce clk_get_rate_range() - clk: Mention that .recalc_rate can return 0 on error - clk: Clarify clk_get_rate() expectations - clk: tests: Add test suites description - clk: tests: Add reference to the orphan mux bug report - clk: tests: Add tests for uncached clock - clk: tests: Add tests for single parent mux - clk: tests: Add tests for mux with multiple parents - clk: tests: Add some tests for orphan with multiple parents - clk: Take into account uncached clocks in clk_set_rate_range() - clk: Fix clk_get_parent() documentation - clk: Set req_rate on reparenting - clk: Change clk_core_init_rate_req prototype - clk: Move clk_core_init_rate_req() from clk_core_round_rate_nolock() to its caller - clk: Introduce clk_hw_init_rate_request() - clk: Add our request boundaries in clk_core_init_rate_req - clk: Switch from __clk_determine_rate to clk_core_round_rate_nolock - clk: Introduce clk_core_has_parent() - clk: Stop forwarding clk_rate_requests to the parent - clk: Zero the clk_rate_request structure - clk: Test the clock pointer in clk_hw_get_name() - clk: Introduce the clk_hw_get_rate_range function - clk: qcom: clk-rcg2: Take clock boundaries into consideration for gfx3d - clk: tests: Add some tests for clk_get_rate_range() - clk: tests: Add missing test case for ranges - drm/vc4: Adopt the dma configuration from the HVS or V3D component - Support RPi DPI interface in mode6 for 18-bit color - drm/vc4: Add FKMS as an acceptable node for dma ranges. - drm/vc4: A present but empty dmas disables audio - drm/vc4: Add debugfs node that dumps the current display lists - drm/vc4: Add all the HDMI registers into the debugfs dumps - drm/vc4: Add the 2711 HVS as a suitable DMA node - vc4_hdmi: Report that 3d/stereo is allowed - vc4: Clear unused infoframe packet RAM registers - drm/vc4: Change the default DPI format to being 18bpp, not 24. - vc4/drm: Avoid full hdmi audio fifo writes - vc4/drm: vc4_plane: Remove subpixel positioning check - drm/vc4: Correct pixel order for DSI0 - drm/vc4: Register dsi0 as the correct vc4 encoder type - drm/vc4: Fix dsi0 interrupt support. - drm/vc4: Add correct stop condition to vc4_dsi_encoder_disable iteration - drm/atomic: Don't fixup modes that haven't been reset - drm/vc4: Fix timings for interlaced modes - drm/vc4: Fix margin calculations for the right/bottom edges - drm/vc4: Fix timings for VEC modes - drm/vc4: Refactor VEC TV mode setting - drm/vc4: Fix definition of PAL-M mode - drm/vc4: Add support for more analog TV standards - drm/vc4: Allow setting the TV norm via module parameter - drm/vc4: Refactor mode checking logic - raspberrypi-firmware: Update mailbox commands - drm/vc4: Add firmware-kms mode - drm/vc4: Reset HDMI MISC_CONTROL register. - drm/vc4: Release workaround buffer and DMA in error paths and unbind - drm/vc4: Correct DSI divider calculations - drm/vc4: Add support for gamma on BCM2711 - drm/vc4: Add debugfs node that dumps the vc5 gamma PWL entries - drm/vc4: hvs: Force modeset on gamma lut change - drm/vc4: Relax VEC modeline requirements and add progressive mode support - drm/vc4: Make VEC progressive modes readily accessible - drm: Check whether the gamma lut has changed before updating - drm/vc4: Enable gamma block only when required. - drm/vc4: Only add gamma properties once. - drm/vc4: Validate the size of the gamma_lut - drm/vc4: Add support for composite syncs to vc4_dpi - drm/vc4: Move HDMI reset to pm_resume - drm/vc4: dpi: Add option for inverting pixel clock and output enable - drm/vc4: dpi: Ensure a default format is selected - vc4/drm: Ignore vc4_hdmi->output_enabled for allowing audio (#4759) - drm/vc4: Skip writes to disabled packet RAM - drm/vc4: Add alpha_blend_mode property to each plane. - drm/vc4: Disable Gamma control on HVS5 due to issues writing the table - drm/vc4_hdmi: Add Broadcast RGB property to allow override of RGB range
[Kernel-packages] [Bug 1982739] Re: BlueZ 5.65 release
Will this also be released for jammy soon? I'm running into this issue which should be fixed with 5.65: https://github.com/bluez/bluez/issues/313 ** Bug watch added: github.com/bluez/bluez/issues #313 https://github.com/bluez/bluez/issues/313 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1982739 Title: BlueZ 5.65 release Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.65 to kinetic: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.65.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1982739/+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 1931432] Re: crash FTBFS on riscv64
Progress is being made and crash could be available for 5.20: https://lore.kernel.org/all/20220813031753.3097720-1-xianting.t...@linux.alibaba.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1931432 Title: crash FTBFS on riscv64 Status in crash package in Ubuntu: Confirmed Status in crash source package in Focal: Confirmed Status in crash source package in Groovy: Confirmed Bug description: Crash fails to build from source on riscv at least for Focal and Groovy, later releases may also be affected but I haven't confirm it. Examples of failed builds : Groovy : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630864 Focal : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.04.1/+build/21630885 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931432/+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 1967889] Re: Raise CONFIG_NR_CPUS
** Description changed: [Impact] * Currently our riscv64 kernels don't support more than 8 CPUs. - * The QEMU 7.0 virt machine supports up to 512 harts (CPU threads). + * The QEMU 7.0 virt machine supports up to 512 harts +(CPU hardware threads). - * Raising CONFIG_NR_CPUS to 32 allows us to use a reasonable number of them. This matches the allowed maximum in upstream Linux. Patches for - raising the limit are pending. + * Raising CONFIG_NR_CPUS to the maximum of 32 allows us to use +more of them. [Test Plan] * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 virtual CPUs and see that only 8 of them are used. - * After raising CONFIG_NR_CPUS to 32 all of them should be used. + * After raising CONFIG_NR_CPUS to 32 up to 32 of them should +be used. [Where problems could occur] - * This will use slightly more RAM which might hurt very small + * This will allocate slightly more RAM which might hurt very small machines. [Other Info] * Original bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich ** Description changed: [Impact] * Currently our riscv64 kernels don't support more than 8 CPUs. * The QEMU 7.0 virt machine supports up to 512 harts -(CPU hardware threads). + (CPU hardware threads). * Raising CONFIG_NR_CPUS to the maximum of 32 allows us to use -more of them. + more of them. [Test Plan] * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 virtual CPUs and see that only 8 of them are used. - * After raising CONFIG_NR_CPUS to 32 up to 32 of them should -be used. + * After raising CONFIG_NR_CPUS up to 32 of them should be used. [Where problems could occur] * This will allocate slightly more RAM which might hurt very small machines. [Other Info] * Original bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich ** Description changed: [Impact] * Currently our riscv64 kernels don't support more than 8 CPUs. - * The QEMU 7.0 virt machine supports up to 512 harts - (CPU hardware threads). + * The QEMU 7.0 virt machine supports up to 512 virtual CPUs. * Raising CONFIG_NR_CPUS to the maximum of 32 allows us to use more of them. [Test Plan] * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 virtual CPUs and see that only 8 of them are used. * After raising CONFIG_NR_CPUS up to 32 of them should be used. [Where problems could occur] * This will allocate slightly more RAM which might hurt very small machines. [Other Info] * Original bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1967889 Title: Raise CONFIG_NR_CPUS Status in linux-riscv package in Ubuntu: New Bug description: [Impact] * Currently our riscv64 kernels don't support more than 8 CPUs. * The QEMU 7.0 virt machine supports up to 512 virtual CPUs. * Raising CONFIG_NR_CPUS to the maximum of 32 allows us to use more of them. [Test Plan] * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 virtual CPUs and see that only 8 of them are used. * After raising CONFIG_NR_CPUS up to 32 of them should be used. [Where problems could occur] * This will allocate slightly more RAM which might hurt very small machines. [Other Info] * Original bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967889/+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 1967889] Re: Raise CONFIG_NR_CPUS
** Description changed: [Impact] - * Currently our riscv64 kernels don't support more than 8 CPUs. + * Currently our riscv64 kernels don't support more than 8 CPUs. - * The QEMU 7.0 virt machine supports up to 32 harts (CPU threads). + * The QEMU 7.0 virt machine supports up to 512 harts (CPU threads). - * Raising CONFIG_NR_CPUS to 32 allows us to use all of them. + * Raising CONFIG_NR_CPUS to 32 allows us to use a reasonable number of them. This matches the allowed maximum in upstream Linux. Patches for + raising the limit are pending. [Test Plan] - * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 -virtual CPUs and see that only 8 of them are used. + * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 + virtual CPUs and see that only 8 of them are used. - * After raising CONFIG_NR_CPUS to 32 all of them should be used. + * After raising CONFIG_NR_CPUS to 32 all of them should be used. [Where problems could occur] - * This will use slightly more RAM which might hurt very small -machines. + * This will use slightly more RAM which might hurt very small + machines. [Other Info] - - * Original bug description: + + * Original bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1967889 Title: Raise CONFIG_NR_CPUS Status in linux-riscv package in Ubuntu: New Bug description: [Impact] * Currently our riscv64 kernels don't support more than 8 CPUs. * The QEMU 7.0 virt machine supports up to 512 virtual CPUs. * Raising CONFIG_NR_CPUS to the maximum of 32 allows us to use more of them. [Test Plan] * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 virtual CPUs and see that only 8 of them are used. * After raising CONFIG_NR_CPUS up to 32 of them should be used. [Where problems could occur] * This will allocate slightly more RAM which might hurt very small machines. [Other Info] * Original bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967889/+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 1967889] Re: Raise CONFIG_NR_CPUS
** Description changed: + [Impact] + + * Currently our riscv64 kernels don't support more than 8 CPUs. + + * The QEMU 7.0 virt machine supports up to 32 harts (CPU threads). + + * Raising CONFIG_NR_CPUS to 32 allows us to use all of them. + + [Test Plan] + + * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 +virtual CPUs and see that only 8 of them are used. + + * After raising CONFIG_NR_CPUS to 32 all of them should be used. + + [Where problems could occur] + + * This will use slightly more RAM which might hurt very small +machines. + + [Other Info] + + * Original bug description: + The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1967889 Title: Raise CONFIG_NR_CPUS Status in linux-riscv package in Ubuntu: New Bug description: [Impact] * Currently our riscv64 kernels don't support more than 8 CPUs. * The QEMU 7.0 virt machine supports up to 32 harts (CPU threads). * Raising CONFIG_NR_CPUS to 32 allows us to use all of them. [Test Plan] * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 virtual CPUs and see that only 8 of them are used. * After raising CONFIG_NR_CPUS to 32 all of them should be used. [Where problems could occur] * This will use slightly more RAM which might hurt very small machines. [Other Info] * Original bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967889/+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 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!
Thank you for the info! Finally managed to install the latest mainline kernel (5.19.5). Unfortunately, issue still persists. I started only firefox, using discrete video card, but in about 10 minutes it got stuck again. Today was a pretty bad laptop day - it got stuck about 6 times in 3 hours. Anyway, hope this helps. Anything else I can do? -- 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/1980831 Title: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! Status in linux package in Ubuntu: Incomplete Bug description: When working normally, random freezes happen. Everything freezes, except the mouse cursor. I tried from keyboard to: switch to another window, start a terminal, run a command to restart gnome, enabled ctrl+alt+backspace and tried it to restart X windows, ctrl+alt+delete, switch to another session with ctrl+alt+F1-F9 - nothing works. If I'm listening to something, the sound goes on for a while; sometimes it stops by itself, other times it keeps going. The only way to recover that I've found is to stop the laptop from the power button. For a while I thought it was due to firefox; I installed the deb version and then switched to chrome - same behavior. It didn't happen when I was playing Hollow Knight in Steam, or when I've used the terminal and nothing else. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:27:36 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-16 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980831/+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 1987870] Re: Demote to proposed LRM portions of intel-iotg
** Tags added: update-excuse update-excuses -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1987870 Title: Demote to proposed LRM portions of intel-iotg Status in linux-restricted-modules-intel-iotg package in Ubuntu: Triaged Status in linux-restricted-signatures-intel-iotg package in Ubuntu: Triaged Bug description: v5.19 kernels are ready to migrate in kinetic. via new nvidia and LRM packages all kernels are entangled. intel-iotg kernel has not yet been upgraded to v5.19. to allow src:linux-meta migration, we need to demote to proposed LRM/LRS of intel-iotg kernel to unblock development. an updated version of intel-iotg kernel will happen a bit later. Please demote to proposed linux-restricted-modules-intel-iotg linux- restricted-signatures-intel-iotg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-intel-iotg/+bug/1987870/+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 1988295] [NEW] Please RM proposed NBS of removed source package linux-raspi-unstable
Public bug reported: I have recently improved supported-kernel-common seeds to keep all kernel binary packages in main/restricted, even for obsolete ABIs. This has triggered components missmatches report (SVG only) https://people.canonical.com/~ubuntu-archive/component-mismatches- proposed.svg to identify that we have stale left over NBS binary packages from linux-raspi-unstable source package in jammy- proposed/universe and kinetic-proposed/universe Please remove all of the below binary packages from the archive, as they are NBS with src:linux-raspi-unstable long gone: $ rmadison -S linux-raspi-unstable linux-buildinfo-5.13.0-1002-raspi| 5.13.0-1002.2 | jammy-proposed/universe | arm64, armhf linux-buildinfo-5.13.0-1002-raspi| 5.13.0-1002.2 | kinetic-proposed/universe | arm64, armhf linux-buildinfo-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 | jammy-proposed/universe | armhf linux-buildinfo-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 | kinetic-proposed/universe | armhf linux-headers-5.13.0-1002-raspi | 5.13.0-1002.2 | jammy-proposed/universe | arm64, armhf linux-headers-5.13.0-1002-raspi | 5.13.0-1002.2 | kinetic-proposed/universe | arm64, armhf linux-headers-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 | jammy-proposed/universe | armhf linux-headers-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 | kinetic-proposed/universe | armhf linux-image-5.13.0-1002-raspi| 5.13.0-1002.2 | jammy-proposed/universe | arm64, armhf linux-image-5.13.0-1002-raspi| 5.13.0-1002.2 | kinetic-proposed/universe | arm64, armhf linux-image-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 | jammy-proposed/universe | armhf linux-image-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 | kinetic-proposed/universe | armhf linux-modules-5.13.0-1002-raspi | 5.13.0-1002.2 | jammy-proposed/universe | arm64, armhf linux-modules-5.13.0-1002-raspi | 5.13.0-1002.2 | kinetic-proposed/universe | arm64, armhf linux-modules-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 | jammy-proposed/universe | armhf linux-modules-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 | kinetic-proposed/universe | armhf linux-raspi-unstable-headers-5.13.0-1002 | 5.13.0-1002.2 | jammy-proposed/universe | arm64, armhf linux-raspi-unstable-headers-5.13.0-1002 | 5.13.0-1002.2 | kinetic-proposed/universe | arm64, armhf linux-raspi-unstable-tools-5.13.0-1002 | 5.13.0-1002.2 | jammy-proposed/universe | arm64, armhf linux-raspi-unstable-tools-5.13.0-1002 | 5.13.0-1002.2 | kinetic-proposed/universe | arm64, armhf linux-tools-5.13.0-1002-raspi| 5.13.0-1002.2 | jammy-proposed/universe | arm64, armhf linux-tools-5.13.0-1002-raspi| 5.13.0-1002.2 | kinetic-proposed/universe | arm64, armhf linux-tools-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 | jammy-proposed/universe | armhf linux-tools-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 | kinetic-proposed/universe | armhf ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Triaged ** Changed in: linux-raspi (Ubuntu) Status: New => Confirmed ** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1988295 Title: Please RM proposed NBS of removed source package linux-raspi-unstable Status in linux-raspi package in Ubuntu: Triaged Bug description: I have recently improved supported-kernel-common seeds to keep all kernel binary packages in main/restricted, even for obsolete ABIs. This has triggered components missmatches report (SVG only) https://people.canonical.com/~ubuntu-archive/component-mismatches- proposed.svg to identify that we have stale left over NBS binary packages from linux-raspi-unstable source package in jammy- proposed/universe and kinetic-proposed/universe Please remove all of the below binary packages from the archive, as they are NBS with src:linux-raspi-unstable long gone: $ rmadison -S linux-raspi-unstable linux-buildinfo-5.13.0-1002-raspi| 5.13.0-1002.2 | jammy-proposed/universe | arm64, armhf linux-buildinfo-5.13.0-1002-raspi| 5.13.0-1002.2 | kinetic-proposed/universe | arm64, armhf linux-buildinfo-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 | jammy-proposed/universe | armhf linux-buildinfo-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 | kinetic-proposed/universe | armhf linux-headers-5.13.0-1002-raspi | 5.13.0-1002.2 | jammy-proposed/universe | arm64, armhf linux-headers-5.13.0-1002-raspi | 5.13.0-1002.2 | kinetic-proposed/universe | arm64, armhf linux-headers-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 | jammy-proposed/universe | armhf linux-headers-5.13.0-1002-raspi-nolpae | 5.13.0-1002.2 | kinetic-proposed/universe | armhf linux-image-5.13.0-1002-raspi
[Kernel-packages] [Bug 1955011] Re: ubuntu_kernel_selftests:net:test_bpf BPF_ATOMIC FAIL to select_runtime err=-524 on arm64 and ppc64el
** Tags added: oracle sru-20220808 -- 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/1955011 Title: ubuntu_kernel_selftests:net:test_bpf BPF_ATOMIC FAIL to select_runtime err=-524 on arm64 and ppc64el Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Bug description: ubuntu_kernel_selftests net:test_bpf.sh fails on d2021.10.26/jammy/linux-realtime/5.15.0-1003.3 on arm64 (kuzzle.arm64): --- 15:38:57 DEBUG| [stdout] [ 1099.852735] test_bpf: #309 BPF_ATOMIC | BPF_W, BPF_ADD: Test: 0x12 + 0xab = 0xbd jited:1 30 PASS 15:38:57 DEBUG| [stdout] [ 1099.853012] test_bpf: #310 BPF_ATOMIC | BPF_W, BPF_ADD: Test side effects, r10: 0x12 + 0xab = 0xbd jited:1 28 PASS 15:38:57 DEBUG| [stdout] [ 1099.853489] test_bpf: #311 BPF_ATOMIC | BPF_W, BPF_ADD: Test side effects, r0: 0x12 + 0xab = 0xbd jited:1 28 PASS 15:38:57 DEBUG| [stdout] [ 1099.853585] test_bpf: #312 BPF_ATOMIC | BPF_W, BPF_ADD: Test fetch: 0x12 + 0xab = 0xbd jited:1 28 PASS 15:38:57 DEBUG| [stdout] [ 1099.853677] test_bpf: #313 BPF_ATOMIC | BPF_W, BPF_ADD | BPF_FETCH: Test: 0x12 + 0xab = 0xbd 15:38:57 DEBUG| [stdout] [ 1099.853688] bpf_jit: unknown atomic op code 01 15:38:57 DEBUG| [stdout] [ 1099.853689] FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.853691] test_bpf: #314 BPF_ATOMIC | BPF_W, BPF_ADD | BPF_FETCH: Test side effects, r10: 0x12 + 0xab = 0xbd FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.853701] test_bpf: #315 BPF_ATOMIC | BPF_W, BPF_ADD | BPF_FETCH: Test side effects, r0: 0x12 + 0xab = 0xbd FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.853712] test_bpf: #316 BPF_ATOMIC | BPF_W, BPF_ADD | BPF_FETCH: Test fetch: 0x12 + 0xab = 0xbd FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.853721] test_bpf: #317 BPF_ATOMIC | BPF_DW, BPF_ADD: Test: 0x12 + 0xab = 0xbd jited:1 30 PASS 15:38:57 DEBUG| [stdout] [ 1099.853819] test_bpf: #318 BPF_ATOMIC | BPF_DW, BPF_ADD: Test side effects, r10: 0x12 + 0xab = 0xbd jited:1 28 PASS 15:38:57 DEBUG| [stdout] [ 1099.853909] test_bpf: #319 BPF_ATOMIC | BPF_DW, BPF_ADD: Test side effects, r0: 0x12 + 0xab = 0xbd jited:1 75 PASS 15:38:57 DEBUG| [stdout] [ 1099.854055] test_bpf: #320 BPF_ATOMIC | BPF_DW, BPF_ADD: Test fetch: 0x12 + 0xab = 0xbd jited:1 28 PASS 15:38:57 DEBUG| [stdout] [ 1099.854162] test_bpf: #321 BPF_ATOMIC | BPF_DW, BPF_ADD | BPF_FETCH: Test: 0x12 + 0xab = 0xbd FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854175] test_bpf: #322 BPF_ATOMIC | BPF_DW, BPF_ADD | BPF_FETCH: Test side effects, r10: 0x12 + 0xab = 0xbd FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854184] test_bpf: #323 BPF_ATOMIC | BPF_DW, BPF_ADD | BPF_FETCH: Test side effects, r0: 0x12 + 0xab = 0xbd FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854193] test_bpf: #324 BPF_ATOMIC | BPF_DW, BPF_ADD | BPF_FETCH: Test fetch: 0x12 + 0xab = 0xbd FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854202] test_bpf: #325 BPF_ATOMIC | BPF_W, BPF_AND: Test: 0x12 & 0xab = 0x02 FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854212] test_bpf: #326 BPF_ATOMIC | BPF_W, BPF_AND: Test side effects, r10: 0x12 & 0xab = 0x02 FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854220] test_bpf: #327 BPF_ATOMIC | BPF_W, BPF_AND: Test side effects, r0: 0x12 & 0xab = 0x02 FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854230] test_bpf: #328 BPF_ATOMIC | BPF_W, BPF_AND: Test fetch: 0x12 & 0xab = 0x02 FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854241] test_bpf: #329 BPF_ATOMIC | BPF_W, BPF_AND | BPF_FETCH: Test: 0x12 & 0xab = 0x02 FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854249] test_bpf: #330 BPF_ATOMIC | BPF_W, BPF_AND | BPF_FETCH: Test side effects, r10: 0x12 & 0xab = 0x02 FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854259] test_bpf: #331 BPF_ATOMIC | BPF_W, BPF_AND | BPF_FETCH: Test side effects, r0: 0x12 & 0xab = 0x02 FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854268] test_bpf: #332 BPF_ATOMIC | BPF_W, BPF_AND | BPF_FETCH: Test fetch: 0x12 & 0xab = 0x02 FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854277] test_bpf: #333 BPF_ATOMIC | BPF_DW, BPF_AND: Test: 0x12 & 0xab = 0x02 FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854287] test_bpf: #334 BPF_ATOMIC | BPF_DW, BPF_AND: Test side effects, r10: 0x12 & 0xab = 0x02 FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854298] test_bpf: #335 BPF_ATOMIC | BPF_DW, BPF_AND: Test side effects, r0: 0x12 & 0xab = 0x02 FAIL to select_runtime err=-524 15:38:57 DEBUG| [stdout] [ 1099.854307] test_bpf: #336
[Kernel-packages] [Bug 1987287] Re: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery
** Description changed:
+ SRU Justification:
+ --
+
+ [Impact]
+
+ * If the mlx5 driver is reloading while the recovery flow is happening,
+and if it receives new commands before the command interface is up
+again, this can lead to null pointer that tries to access non-
+initialized command structures.
+
+ * So it's required to avoid processing commands before the command
+interface is up again.
+
+ * This is accomplished by a new cmdif state that helps to avoid
+processing commands while cmdif is not ready.
+
+ [Fix]
+
+ * backport of f7936ddd35d8 f7936ddd35d8b849daf0372770c7c9dbe7910fca
+ "net/mlx5: Avoid processing commands before cmdif is ready"
+
+ [Test Plan]
+
+ * An Ubuntu Server for s390x 18.04 or 20.04 LPAR or z/VM installation
+is needed that has Mellanox cards (RoCE Express 2.1) assigned,
+configured and enabled and that runs a 5.4 kernel (on bionic hwe-5.4).
+
+ * Now trigger a recovery (guess that can be done at the Support Element)
+and reload the driver at the same time.
+
+ * Make sure the module/driver mlx5 is loaded and in use
+(otherwise it can't be removed/unloaded).
+
+ * Now remove/unload the module with:
+sudo modprobe -r mlx5
+and (re-)load it again with:
+sudo modprobe mlx5
+
+ * Due to the lack of RoCE Express 2.1 hardware,
+IBM needs to do the verification.
+
+ [Where problems could occur]
+
+ * In case there is an issue with 'cmdif' it might not have the correct
+interface state, which:
+- either might lead to the fact that commands are not properly blocked
+ and the situation is similar like before
+- or the commands may get always blocked,
+ which render the hardware useless
+- or might block in wrong situation,
+ which will cause unexpected issues and broken behavior.
+
+ * Since the patch got upstream accepted with v5.7-rc7 it's
+not new to the kernel, was already part of groovy (and above)
+and is therefor already in use by newer Ubuntu releases.
+
+ [Other Info]
+
+ * Since the patch is upstream since v5.7-rc7,
+it's already included in jammy and kinetic.
+
+ * Since the upstream patch incl. the line:
+Fixes: e126ba97dba9 ("mlx5: Add driver for Mellanox
+Connect-IB adapters") it looks to me that it was forgotten
+to mark the patch for upstream stable updates.
+ __
+
We recently got a bug report for systems running Ubuntu 20.04 that were
crashing with backtraces pointing at the mlx5 driver's handling of
mlx5_ethtool_get_link_ksettings()
when this is called through the sysfs (going through ethtool might have
different checks).
I managed to find a reliable way to reproduce the issue that I believe isn't
tied to IBM Z at all.
The procedure to reproduce is as follows. I created a script to read
the sysfs attributes for the link's speed and duplex mode in a loop:
#!/usr/bin/env bash
if [ $# -lt 1 ]; then
- echo "Usage: $0 "
- exit 1
+ echo "Usage: $0 "
+ exit 1
fi
while true; do
- cat /sys/class/net/$1/duplex > /dev/null
- cat /sys/class/net/$1/speed > /dev/null
+ cat /sys/class/net/$1/duplex > /dev/null
+ cat /sys/class/net/$1/speed > /dev/null
done
Executed with:
# ./script.sh enP10p0s0
I ran this in one bash session and then in another one I triggered a PCI
reset with
the follwoing command where one needs to replace with the PCI address
of the NIC:
echo 1 > /sys/bus/pci/devices//reset
Then first I got a lot of the following messages:
- mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings:
+ mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings:
query port ptys failed: -5
And then as the mlx5 driver's recovery kicks in the oops as below:
[ 659.103947] mlx5_core 0010:00:00.0: wait vital counter value 0x7b399f
after 1 iterations
[ 659.103947] mlx5_core 0010:00:00.0: mlx5_pci_resume was called
[ 659.103966] mlx5_core 0010:00:00.0: firmware version: 14.32.1010
[ 659.104169] Unable to handle kernel pointer dereference in virtual kernel
address space
[ 659.104171] Failing address: TEID: 0483
[ 659.104172] Fault in home space mode while using kernel ASCE.
[ 659.104173] AS:3d29c007 R3:fffd0007 S:fffd5800
P:003d
[ 659.104200] Oops: 0004 ilc:2 [#1] SMP
[ 659.104202] Modules linked in: s390_trng ism smc pnet chsc_sch eadm_sch
vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm
drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress
zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor
async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx5_ib dm_service_time pkey
zcrypt crc32_vx_s390 ib_uverbs ghash_s390 ib_core qeth_l2 prng aes_s390
des_s390 nvme libdes sha3_512_s390 sha3_256_s390 sha512_s390
[Kernel-packages] [Bug 1967889] Re: Raise CONFIG_NR_CPUS
** Changed in: linux-riscv (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1967889 Title: Raise CONFIG_NR_CPUS Status in linux-riscv package in Ubuntu: New Bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967889/+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 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin2204
--
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/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Status in Ubuntu on IBM z Systems:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Confirmed
Status in linux source package in Kinetic:
Confirmed
Bug description:
== Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 ==
+++ This bug was initially created as a clone of Bug #199319 +++
Description: s390/qeth: cache link_info for ethtool
Symptom: lost of IP connection and log entries in journalctl:
kernel: qeth 0.0.0365: The qeth device driver failed to
recover an error on the device
Problem: Since commit e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
there was a timing window during recovery, that
qeth_query_card_info could be sent to the card, even before it
was ready for it, leading to a failing card recovery. There is
evidence that this window was hit, as not all callers of
get_link_ksettings() check for netif_device_present.
Solution: Use cached values in qeth_get_link_ksettings(), instead of
calling qeth_query_card_info() and falling back to default
values in case it fails. Link info is already updated when the
card goes online, e.g. after STARTLAN (physical link up). Set
the link info to default values, when the card goes offline or
at STOPLAN (physical link down). A follow-on patch will improve
values reported for link down.
Fixes: e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
Reproduction: enforce a eth device recvoery, while running ethtool multiple
times in parallel and using iperf to get load on the interface.
Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
applicable for most kernel > 3.14
== Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 ==
the inital update came in with kernel 5.1 upstream, but we found it
backported in many older kernel versions
== Comment: #4 - J?rn Siglen - 2022-08-09 08:03:09 ==
the acceptance info of the patch can be found here:
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+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 1987869] Re: Demote to proposed LRM portions of linux-oem-5.17
** Tags added: update-excuse ** Tags added: update-excuses -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987869 Title: Demote to proposed LRM portions of linux-oem-5.17 Status in linux-restricted-modules-oem-5.17 package in Ubuntu: Triaged Status in linux-restricted-signatures-oem-5.17 package in Ubuntu: Triaged Bug description: v5.19 kernels are ready to migrate in kinetic. via new nvidia and LRM packages all kernels are entangled. oem-5.17 is an obsolete kernel, and its meta packages will be taken over by src:linux-meta once it migrates to allow src:linux-meta migration, we need to demote to proposed LRM/LRS of oem-5.17 kernel. Once src:linux-meta migrates all of the oem-5.17 packages will be removed completely from the archive. Please demote to proposed linux-restricted-modules-oem-5.17 linux- restricted-signatures-oem-5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-oem-5.17/+bug/1987869/+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 1940972] Re: v5.13 kernel ftrace selftest fails on riscv64 unmatched
5.13 EOL However this issue is still valid for jammy 5.15 riscv. We have this test disabled in ubuntu_kernel_selftests: https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/tree/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py#n163 Thus I will left this bug open. ** Summary changed: - v5.13 kernel ftrace selftest fails on riscv64 unmatched + unc_stack_tracer.tc (Max stack tracer) kernel ftrace selftest fails on riscv64 unmatched ** Tags added: 5.15 jammy ubuntu-kernel-selftests ** Summary changed: - unc_stack_tracer.tc (Max stack tracer) kernel ftrace selftest fails on riscv64 unmatched + func_stack_tracer.tc (Max stack tracer) kernel ftrace selftest fails on riscv64 unmatched -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1940972 Title: func_stack_tracer.tc (Max stack tracer) kernel ftrace selftest fails on riscv64 unmatched Status in Linux: Confirmed Status in ubuntu-kernel-tests: New Status in linux-riscv package in Ubuntu: New Bug description: $ sudo make -C tools/testing/selftests TARGETS=ftrace run_tests ... # [32] ftrace - Max stack tracer [FAIL] ... Testing using 5.13.0-1002.2 the full ftrace suite takes just over 2 hours on unmatched. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1940972/+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 1977962] Re: [UBUNTU 21.10] s390/perf: obtain sie_block from the right address
Updating to Fix Released, because LP#1981864 was updated to Fix
Released.
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1977962
Title:
[UBUNTU 21.10] s390/perf: obtain sie_block from the right address
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
Description: s390/perf: obtain sie_block from the right address
Symptom: Read from unitialized stack memory, incorrect guest
perf data reported, possibly system crash.
Problem: When perf is instructed to record a software-based event and
to trace the guest, i.e. using the following command:
perf kvm --guest --guestvmlinux=endless.elf top -e cpu-clock
The reported guest instruction pointer is inaccurate or
the system may crash.
This is caused by the sie_block being taken from empty1[0]
in sie_block() in arch/s390/kernel/perf_event.c, but since
1179f170b6f0 ("s390: fix fpu restore in entry.S")
it resides at empty1[1].
Solution: Obtain sie_block from the right address in sie_block().
Reproduction: 1. Start a KVM guest executing an endless loop.
2. Determine the instruction address of the loop.
3. Start perf recording for any software event and trace
the guest, for example using this command:
perf kvm --guest --guestvmlinux=endless.elf top -e
cpu-clock
4. The reported guest instruction addresses don't match
the loop's instruction address or the system crashes.
Upstream-ID: c9bfb460c3e4da2462e16b0f0b200990b36b1dd2
BBPF Probl.ID: 198450
Preventive:yes
Reported: -
SupportTicket: -
Reference: -
Date: 2022-06-02
Author:n...@linux.ibm.com
Component: kernel
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c9bfb460c3e4da2462e16b0f0b200990b36b1dd2
Problem occurs / affects impish and jammy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977962/+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 1981773] Re: Make cm32181 sensor work after system suspend
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1981773 Title: Make cm32181 sensor work after system suspend Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] cm32181 ambient light sensor stops working after system suspend. [Fix] Add PM support for cm32181 so it can work after system suspend. [Test] The sysfs in_illuminance_input continues to change after system suspend. [Where problems could occur] This changeset is limited to a specific device, and it already lacks PM support - so the worst case is that it stops working after resume like it always has been. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981773/+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 1981950] Re: Failed to resume from S3 blocked by atlantic driver[1d6a:94c0]
** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1981950 Title: Failed to resume from S3 blocked by atlantic driver[1d6a:94c0] Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] The system with atlantic NIC[1d6a:94c0] fails to resume from S3 and hang with the following errors Jun 7 13:13:54 ubuntu kernel: [ 116.000561] aq_nic_deinit+0xb4/0xd0 [atlantic] Jun 7 13:13:54 ubuntu kernel: [ 116.000566] atl_resume_common+0x6d/0x110 [atlantic] Jun 7 13:13:54 ubuntu kernel: [ 116.000571] aq_pm_resume_restore+0x13/0x20 [atlantic] Jun 7 13:13:54 ubuntu kernel: [ 116.000575] pci_pm_resume+0x5c/0x90 Jun 7 13:13:54 ubuntu kernel: [ 116.000578] ? pci_pm_thaw+0x80/0x80 Jun 7 13:13:54 ubuntu kernel: [ 116.000580] dpm_run_callback+0x4e/0x120 Jun 7 13:13:54 ubuntu kernel: [ 116.000582] device_resume+0xad/0x200 Jun 7 13:13:54 ubuntu kernel: [ 116.000583] async_resume+0x1e/0x40 Jun 7 13:13:54 ubuntu kernel: [ 116.000585] async_run_entry_fn+0x33/0x120 Jun 7 13:13:54 ubuntu kernel: [ 116.000586] process_one_work+0x220/0x3c0 Jun 7 13:13:54 ubuntu kernel: [ 116.000588] worker_thread+0x4d/0x3f0 Jun 7 13:13:54 ubuntu kernel: [ 116.000589] ? process_one_work+0x3c0/0x3c0 Jun 7 13:13:54 ubuntu kernel: [ 116.000591] kthread+0x12a/0x150 Jun 7 13:13:54 ubuntu kernel: [ 116.000592] ? set_kthread_struct+0x40/0x40 Jun 7 13:13:54 ubuntu kernel: [ 116.000593] ret_from_fork+0x22/0x30 Jun 7 13:13:54 ubuntu kernel: [ 116.000596] Jun 7 13:13:54 ubuntu kernel: [ 116.000596] ---[ end trace 9d3fcd41d27dae25 ]--- [Fix] aq_nic_deinit() has been called while suspending, so don't need to call it again on resuming. Applied below 2 commits from v5.19-rc7 fix the issue, and the 2 commits have been applied to stable kernel v5.10, v5.15, and v5.18. 2e15c51fefaf net: atlantic: remove aq_nic_deinit() when resume 0f3325076038 net: atlantic: remove deep parameter on suspend/resume functions [Test] Verified on the system with atlantic NIC[1d6a:94c0] and run S3 test for more than 200 times. [Where problems could occur] The 2 commits remove the redundant code, aq_nic_deinit() has been called while suspending, so we don't need to call it again while resuming, and this fix the issue. I don't think this would introduce any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981950/+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 1982104] Re: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes
** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1982104 Title: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server. Attaching the console logs. Currently, it looks like disabling VT-D option in BIOS settings helps mitigate the issue. Console logs indicate something is wrong in iommu/dmar subsystem. [Fix] The IOMMU driver shares the pasid table for PCI alias devices. When the RID2PASID entry of the shared pasid table has been filled by the first device, the subsequent device will encounter the "DMAR: Setup RID2PASID failed" failure as the pasid entry has already been marked as present. As the result, the IOMMU probing process will be aborted. On the contrary, when any alias device is hot-removed from the system, for example, by writing to /sys/bus/pci/devices/.../remove, the shared RID2PASID will be cleared without any notifications to other devices. As the result, any DMAs from those rest devices are blocked. Sharing pasid table among PCI alias devices could save two memory pages for devices underneath the PCIe-to-PCI bridges. Anyway, considering that those devices are rare on modern platforms that support VT-d in scalable mode and the saved memory is negligible, it's reasonable to remove this part of immature code to make the driver feasible and stable. [Test Case] 1. use the target machine(Intel Sapphire Rapids) and install the kernel with the fix. 2. boot the target machine 3. check dmesg if the error message exists [ 8.120527] pci :03:01.0: DMAR: Setup RID2PASID failed [Where problems could occur] After enable intel_iommu, the errors may be occurred. We need to figure out one by one once the related errors are triggered in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982104/+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 1982716] Re: Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9
** Changed in: oem-priority Status: New => Fix Released ** Changed in: hwe-next Status: Fix Committed => Fix Released ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1982716 Title: Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9 Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-hwe-5.17 source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] The audio mute key (F5) and mic-mute LED (F8) don't work on some HP 440/450/640/650 G9 laptops. [Fix] The HP ProBook 440/450 G9 and EliteBook 640/650 G9 have multiple motherboard design and they are using different subsystem ID of audio codec. Add the same quirk for other MBs. [Test] After applying the fix, the mute LEDs are working. [Where problems could occur] It's low risk as it's specific ID for HP new machines. If the HP ships other machines using same SSID, then the LED may not work on those machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982716/+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 1983297] Re: Additional fix for TGL + AUO panel flickering
** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983297 Title: Additional fix for TGL + AUO panel flickering Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel" alone used to fix the issue on the AUO panel. But the panel starts to flicker like crazy on top of the new stable commits. [Fix] Backport full fix for PSR2 selective fetch, but only enable it on TGL + specific AUO panel. The last three patches which enable PSR2 on ADL-P are dropped. [Test] Originally the backport regressed ADL + BOE panel, so this time we put extra effort to ensure those system are unaffected, while TGL + AUO panel is still fixed. [Where problems could occur] Most code changes only have functional impact when PSR2 selective fetch is enabled. Some of changes are under more general call path for hardware cursor rendering. Notes are added to describe the functional impact for each patch, so if regression really occurrs it's easier to spot the offending commit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983297/+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 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1983143 Title: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Summary] No video output on Thunderbolt monitor. 1. Connect monitor to DUT directly 2. Connect monitor to DUT via Docking System can detect the monitor and able to change display mode but no output on the monitor [Steps to reproduce] 1. Boot to OS 2. Plug an external monitor via thunderbolt port [Expected result] Display on external monitor normally [Actual result] No vidoe ouput on external monitor [Failure rate] 3/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983143/+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 1987287] Re: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery
Test kernels are now available in the following PPA: https://launchpad.net/~fheimes/+archive/ubuntu/lp1987287 (20.04/focal 5.4 as well as 18.04.5/bionic hwe-5.4) -- 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/1987287 Title: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Bug description: We recently got a bug report for systems running Ubuntu 20.04 that were crashing with backtraces pointing at the mlx5 driver's handling of mlx5_ethtool_get_link_ksettings() when this is called through the sysfs (going through ethtool might have different checks). I managed to find a reliable way to reproduce the issue that I believe isn't tied to IBM Z at all. The procedure to reproduce is as follows. I created a script to read the sysfs attributes for the link's speed and duplex mode in a loop: #!/usr/bin/env bash if [ $# -lt 1 ]; then echo "Usage: $0 " exit 1 fi while true; do cat /sys/class/net/$1/duplex > /dev/null cat /sys/class/net/$1/speed > /dev/null done Executed with: # ./script.sh enP10p0s0 I ran this in one bash session and then in another one I triggered a PCI reset with the follwoing command where one needs to replace with the PCI address of the NIC: echo 1 > /sys/bus/pci/devices//reset Then first I got a lot of the following messages: mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings: query port ptys failed: -5 And then as the mlx5 driver's recovery kicks in the oops as below: [ 659.103947] mlx5_core 0010:00:00.0: wait vital counter value 0x7b399f after 1 iterations [ 659.103947] mlx5_core 0010:00:00.0: mlx5_pci_resume was called [ 659.103966] mlx5_core 0010:00:00.0: firmware version: 14.32.1010 [ 659.104169] Unable to handle kernel pointer dereference in virtual kernel address space [ 659.104171] Failing address: TEID: 0483 [ 659.104172] Fault in home space mode while using kernel ASCE. [ 659.104173] AS:3d29c007 R3:fffd0007 S:fffd5800 P:003d [ 659.104200] Oops: 0004 ilc:2 [#1] SMP [ 659.104202] Modules linked in: s390_trng ism smc pnet chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx5_ib dm_service_time pkey zcrypt crc32_vx_s390 ib_uverbs ghash_s390 ib_core qeth_l2 prng aes_s390 des_s390 nvme libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common mlx5_core tls mlxfw ptp nvme_core pps_core dasd_eckd_mod dasd_mod zfcp scsi_transport_fc qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 659.104232] CPU: 6 PID: 438216 Comm: cat Not tainted 5.4.0-124-generic #140-Ubuntu [ 659.104233] Hardware name: IBM 3931 XYZ (LPAR) [ 659.104234] Krnl PSW : 0404c0018000 3bfa661e (__queue_work+0xfe/0x520) [ 659.104241]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 659.104242] Krnl GPRS: 3c291570 0007 7fff [ 659.104243]e2fe46e0 000fffe0 0006 3d039588 [ 659.104244] e2fe46e0 bfb3e000 [ 659.104245]e194c400 03e007d6fb78 3bfa6602 03e007d6f860 [ 659.104251] Krnl Code: 3bfa6612: a77400e5brc 7,3bfa67dc 3bfa6616: 582003acl %r2,940 #3bfa661a: a718lhi %r1,0 >3bfa661e: ba129000cs %r1,%r2,0(%r9) 3bfa6622: a77401a7brc 7,3bfa6970 3bfa6626: e310b0180012lt %r1,24(%r11) 3bfa662c: a78400ffbrc 8,3bfa682a 3bfa6630: c004004bbrcl 0,3bfa66c6 [ 659.104261] Call Trace: [ 659.104263] ([<>] 0x0) [ 659.104265] [<3bfa6aa2>] queue_work_on+0x62/0x70 [ 659.104329] [<03ff80a2920a>] cmd_exec+0x4ea/0x840 [mlx5_core] [ 659.104349] [<03ff80a29680>] mlx5_cmd_exec+0x40/0x70 [mlx5_core] [ 659.104369] [<03ff80a334a8>] mlx5_core_access_reg+0x108/0x150 [mlx5_core] [ 659.104387] [<03ff80a3354e>] mlx5_query_port_ptys+0x5e/0x70 [mlx5_core] [
[Kernel-packages] [Bug 1942999] Re: Fix invalid MAC address after hotplug tbt dock
** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942999 Title: Fix invalid MAC address after hotplug tbt dock Status in HWE Next: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU justification: [Impact] igc driver can not connect to network after re-plugin thunderbolt dock when MAC passthrough enabled in BIOS. [Fix] Wait for the MAC copy of BIOS when enabled MAC passthrough. Intel engineer wants a different solution and promise to discuss with firmware engineer. Due to the schedule, made this as a short term solution to fix the issue, and wait for the other fix from Intel. [Test] Verified on hardware, after hotplug the thunderbolt cable, Ethernet works fine. [Where problems could occur] It may break the igc driver. Intel still doesn't provide any solution about their approach. In the meantime, this patch is still the only fix. Re-submit it to Jammy, oem-5.17 and Unstable kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942999/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1966010] Re: Fix audio on Zbook Studio G9
** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966010 Title: Fix audio on Zbook Studio G9 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Cirrus Logic AMP still doesn't work on Zbook Studio G9. Moreoever, The audio mute LEDs stop working after the said SRU. [Fix] Correcly interpret the debounce time from ACPI to gpiolib, and apply the correct quirk for the audio mute LEDs. [Where problems could occur] It's possible that some hardwares rely on the "wrong" debounce time to work, however the fix is to increase the debounce time, so it's more forgiving than decreasing. The LED fix is only applied to one system, so it's specifi and won't cause too much trouble. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966010/+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 1966680] Re: Fix drm/amd/pm: enable ASPM by default
** Changed in: hwe-next
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1966680
Title:
Fix drm/amd/pm: enable ASPM by default
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Fix Committed
Bug description:
[Impact]
With WX3200 and 20.04d kernel the unit freezes on resume
[Fix]
commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
by default but a variety of hardware configurations it turns out that this
caused a regression.
Multiple SKUs with wx3200 gpus encounter the resume issue.
Before the real fix is landed, revert commit 0064b0ce85bb first.
[Test Case]
1. plug wx3200 on the adl machine and make it as a output.
2. suspend machine
3. check if machine could resume successfully
[Where problems could occur]
Low, don't make AMDGPU ASPM by default.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1966680/+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 1968861] Re: Support Cirrus audio codec configurations for Odin platform
** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1968861 Title: Support Cirrus audio codec configurations for Odin platform Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] CS8409 needs new configuration for Odin platform [Fix] Cirrus provides us 2 patches to add the support which are not in upstream yet ALSA: hda/cs8409: Add Speaker Playback Switch for Cyborg ALSA: hda/cs8409: Support new Odin Variants Below series of patch is required to be applied before these 2. https://lists.ubuntu.com/archives/kernel-team/2022-April/129223.html [Test] Verified on the target machine [Where problems could occur] The first commit only affects the new added Odin platform, and the second one do some modification for other platforms which is hard to know what may lead to. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968861/+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 1969771] Re: Fix beacon loss for rtl8821ce on certain platforms
** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969771 Title: Fix beacon loss for rtl8821ce on certain platforms Status in HWE Next: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] On the intel ADL-U platform, the rtl8821ce suffers the beacon loss frequently because the driver doesn't received any beacon from AP. It causes the wpa-supplicant to reconnect again and again. Given it's critical to user experience and the urgent schedule, we need to SRU before getting approval. [Fix] Realtek release a fix to disable the PCI completion timeout on rtl8821ce so the PCI bus won't get stuck and can handed the received packets to the driver correctly. [Test Case] 1. Connect the WiFi to internet by selecting a internet connected AP 2. ping 8.8.8.8 to check the internet connectivity for at least 5 minutes. 3. Make sure no 'CTRL-EVENT-BEACON-LOSS' event reported from wpa_supplicant [Where problems could occur] Risk should be Low. It's only applied for RTL8821CE to disable the completion timeout capability. == Original Bug Description == [Summary] Wireless keeps connection and loses connection repeatedly. Below test cases are failed: - wireless/wireless_connection_wpa_n_nm_wlp3s0 - after-suspend-wireless/wireless_connection_wpa_bg_nm_wlp3s0 - after-suspend-wireless/wireless_connection_wpa_ac_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_n_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_bg_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_ac_nm_wlp3s0 Issue is also observed on WVA4-DVT2-C1 [Steps to reproduce] 1. Boot into OS 2. Connect network by wireless 3. Run 'sudo apt update' [Expected result] Wireless connection won't break [Actual result] Wireless loses the connection and then connect network, after a while, issue happens again. [Failure rate] 10/10 [Additional information] CID: 202202-29949, 202202-29947 SKU: WMVA5-DVT2-C1, WVA4-DVT2-C1 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-olly-adl+X175 system-manufacturer: Dell Inc. system-product-name: Vostro 3520 bios-version: 0.5.4 CPU: 12th Gen Intel(R) Core(TM) i5-1235U (12x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4628] (rev 0c) :01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f9f] (rev a1) kernel-version: 5.14.0-1024-oem [Stage] Issue reported and logs collected at a later stage To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969771/+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
