[Kernel-packages] [Bug 2063529] Re: Add support for Quectel RM520N-GL modem [1eac:1007]
** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2063529 Title: Add support for Quectel RM520N-GL modem [1eac:1007] Status in HWE Next: In Progress Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] * Add support for Quectel RM520N-GL modem, so the device could be properly probed. 08:00.0 Unassigned class [ff00]: Quectel Wireless Solutions Co., Ltd. Device [1eac:1007] Subsystem: Quectel Wireless Solutions Co., Ltd. Device [1eac:100b] [Test Plan] * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in use` is mht-pci-generic. [Where problems could occur] * These commits only introduces a PID, it won't impact devices which are supported originally. [Other Info] * Upstream commits: https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081 * Lenovo with this device will be enabled by linux-oem-6.5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063529/+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 2058109] Re: Kernel 5.15.0-100 breaks Intel NIC
The latest version in jammy-updates is now 5.15.0-105.115 and 5.15.0-106.116 in proposed. Paul, could you give them a try? ** 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/2058109 Title: Kernel 5.15.0-100 breaks Intel NIC Status in linux package in Ubuntu: Incomplete Bug description: From syslog: Mar 15 12:11:18 kvmMini systemd[1]: Starting Refresh fwupd metadata and update motd... Mar 15 12:11:18 kvmMini fwupdmgr[284042]: Updating lvfs Mar 15 12:11:18 kvmMini fwupdmgr[284042]: Downloading…: 0% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 0% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 1% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 2% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 3% ...trimmed content Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 97% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 98% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:20 kvmMini fwupdmgr[284042]: Successfully downloaded new metadata: 0 local devices supported Mar 15 12:11:20 kvmMini systemd[1]: fwupd-refresh.service: Deactivated successfully. Mar 15 12:11:20 kvmMini systemd[1]: Finished Refresh fwupd metadata and update motd. Mar 15 12:17:01 kvmMini CRON[284549]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 12:23:59 kvmMini kernel: [3519186.337746] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 12:26:49 kvmMini kernel: [3519356.515727] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 13:05:00 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.5pHMXa.mount: Deactivated successfully. Mar 15 13:07:48 kvmMini kernel: [3521815.001961] x86/split lock detection: #AC: CPU 0/KVM/279304 took a split_lock trap at address: 0xf80521c42fb3 Mar 15 13:17:01 kvmMini CRON[289583]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 13:20:49 kvmMini kernel: [3522596.527060] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 13:30:01 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.I79KlX.mount: Deactivated successfully. Mar 15 13:43:22 kvmMini kernel: [3523948.983970] x86/split lock detection: #AC: CPU 0/KVM/279304 took a split_lock trap at address: 0xf80521c42fb3 Mar 15 13:53:22 kvmMini kernel: [3524549.046156] x86/split lock detection: #AC: CPU 0/KVM/1774 took a split_lock trap at address: 0xf8041de42fb3 Mar 15 14:07:33 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.K8Zq9M.mount: Deactivated successfully. Mar 15 14:17:01 kvmMini CRON[294744]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 14:20:03 kvmMini kernel: [3526150.403065] e1000e :00:1f.6 eno2: Detected Hardware Unit Hang: Mar 15 14:20:03 kvmMini kernel: [3526150.403065] TDH <9f> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] TDT <9> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_use <9> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_clean<9e> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] buffer_info[next_to_clean]: Mar 15 14:20:03 kvmMini kernel: [3526150.403065] time_stamp <1348a0aab> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_watch<9f> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] jiffies <1348a0bb0> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_watch.status <0> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] MAC Status <40080083> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY Status <796d> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY 1000BASE-T Status <3800> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY Extended Status<3000> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PCI Status <10> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] e1000e :00:1f.6 eno2: Detected Hardware Unit Hang: Mar 15 14:20:05 kvmMini kernel: [3526152.391042] TDH <9f> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] TDT <9> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] next_to_use
[Kernel-packages] [Bug 2058208] Re: OpenGL renderer AMD defaults to Intel
** Changed in: linux-signed-oem-6.5 (Ubuntu) Assignee: Anthony Wong (anthonywong) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058208 Title: OpenGL renderer AMD defaults to Intel Status in linux-signed-oem-6.5 package in Ubuntu: Invalid Bug description: Checkbox job " com.canonical.certification::graphics/2_valid_opengl_renderer_PCI_ID_0x743f" fails with error: ``` Setting up PRIME GPU offloading for AMD discrete GPU OpenGL renderer string: Mesa Intel(R) Graphics (RPL-S) ERROR: renderer is Intel when DRI_PRIME=1 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-1016-oem 6.5.0-1016.17 ProcVersionSignature: Ubuntu 6.5.0-1016.17-oem 6.5.13 Uname: Linux 6.5.0-1016-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Mar 18 14:46:23 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-abra+X102 InstallationDate: Installed on 2024-03-15 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 SourcePackage: linux-signed-oem-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.5/+bug/2058208/+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 2063077] Re: Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101)
Felipe, thanks for testing. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063077 Title: Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101) Status in linux package in Ubuntu: Fix Committed Bug description: Dear Ubuntu maintainers, I think I found a regression in linux 5.15.0-105. In the past few days, my keyboard stopped working after waking up from suspend (sleep), so I couldn't unlock my laptop. Various workarounds found on the internet helped, but I wanted to investigate if it was a gdm issue, grub, or a hardware failure. I managed to narrow it down to the kernel, which is why I'm filing this bug report. AFAICT the only keys that work are the keyboard lights and the brightness knobs (in the Fn functions). I can confirm that 5.15.0-105 has the issue, and I can consistently reproduce it with the following steps: 1. boot fresh with 5.15.0-105 2. login to my account 3. choose suspend from the power menu 4. wake up Following the same steps above with the last kernel available does not cause the issue (package version 5.15.0-101.111). I'll keep using that one for the time being. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-105-generic 5.15.0-105.115 ProcVersionSignature: Ubuntu 5.15.0-105.115-generic 5.15.148 Uname: Linux 5.15.0-105-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philsf 5465 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 02:58:26 2024 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ab7cb5b3-b98e-4d3a-8923-b75a557d5ddc InstallationDate: Installed on 2018-06-07 (2145 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c1 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-105-generic root=UUID=670af779-d73e-4cb4-b272-d3240de0c998 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-5.15.0-105-generic N/A linux-backports-modules-5.15.0-105-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2023 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0TXW78 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/06/2023:br1.14:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0TXW78:rvrA00:cvnDellInc.:ct10:cvr:sku0810: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063077/+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 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
This fix also requires kernel patches in this series: https://lists.ubuntu.com/archives/kernel-team/2024-April/150378.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: Fix Committed Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-oem-6.8 package in Ubuntu: Triaged Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: Fix Committed Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-meta source package in Noble: Triaged Status in linux-meta-oem-6.8 source package in Noble: Triaged Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+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 2063074] Re: Waydroid breaks nouveau
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- 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/2063074 Title: Waydroid breaks nouveau Status in linux package in Ubuntu: Triaged Bug description: https://waydro.id/ The session is forced to logout. nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30070]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30070]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30107]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30107]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30145]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30145]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 17e0 data 000c nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 17e0 data 0060 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 8 [007f862000 RenderThread[26090]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 8 [007f862000 RenderThread[26090]] subc 0 class c597 mthd 17e0 data 0018 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:neo3373 F pipewire /dev/snd/controlC0: neo3373 F pipewire neo3377 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 07:32:35 2024 InstallationDate: Installed on 2024-03-22 (30 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-31-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash ipv6.disable=1 RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-11 (11 days ago) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063074/+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 2062502] Re: linux-firmware package breaks iwlwifi
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux-firmware (Ubuntu)
Assignee: Anthony Wong (anthonywong) => En-Wei Wu (rickywu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Triaged
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+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 2062063] Re: ULTS 24 linux 6.8.0-22 SOF sound chips wrong name of fw package
** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist ** Changed in: linux (Ubuntu) Importance: Wishlist => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2062063 Title: ULTS 24 linux 6.8.0-22 SOF sound chips wrong name of fw package Status in linux package in Ubuntu: New Bug description: Binary package 'linux-modules-extra'. With a Skylake Intel sound chip I get: [5.911304] sof-audio-pci-intel-tgl :00:1f.3: Check if you have 'sof-firmware' package installed. The actual Ubuntu package to install is called "firmware-sof-signed" rather than "sof-firmware". That can be confusing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062063/+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 2062545] Re: Still, No keyboard after kernel update Linux t-l15 6.5.0-1020-oem
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => AaronMa (mapengyu) -- 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/2062545 Title: Still, No keyboard after kernel update Linux t-l15 6.5.0-1020-oem Status in linux package in Ubuntu: Confirmed Bug description: Hello, I use the ThinkPad L15 Gen4, BIOS version R24ET38W(1.21) together with Xubuntu 22.04.04 LTS kernel 6.5.0-1020-oem, the CPU type is i7-1355U. This combination gives still a not working keyboard after booting. Today the system has upgraded the kernel to Linux version 6.5.0-1020-oem this should solves the keyboard problem introduced in kernel 6.5.0-1019-oem and already reported in: - https://bugs.launchpad.net/bugs/2060727 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060866 This bug fix does not work, I still have no internal keyboard. For the moment I am using kernel 6.5.0-1018-oem which workes fine. Who can/will help? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062545/+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 2061376] Re: Touchpad scroll bounces back 22.04.4
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => 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/2061376 Title: Touchpad scroll bounces back 22.04.4 Status in linux package in Ubuntu: New Bug description: When scrolling anywhere using 2 fingers the scroll bounces back if fingers are lifted up from touchpad. Soft finger point muscles have some flex to them and I strongly believe this causes the scroll bounce back. Easily repeated to both directions. In bounce scroll rapidly moves to the opposite direction of where user wanted to scroll when lifting up fingers. Attached is log file evtest_event5.log from single scroll where there was bounce at lifting fingers. Hardware details: xinput --list WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ xwayland-pointer:16 id=6[slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:16id=7[slave pointer (2)] ⎜ ↳ xwayland-pointer-gestures:16id=8[slave pointer (2)] ⎜ ↳ xwayland-touch:16 id=10 [slave pointer (2)] ⎜ ↳ xwayland-tablet stylus:16 id=11 [slave pointer (2)] ⎜ ↳ xwayland-tablet eraser:16 id=12 [slave pointer (2)] ⎜ ↳ xwayland-tablet cursor:16 id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ xwayland-keyboard:16id=9[slave keyboard (3)] lshw *-input:0 product: Sleep Button physical id: 2 logical name: input0 logical name: /dev/input/event0 capabilities: platform *-input:1 product: Lid Switch physical id: 3 logical name: input1 logical name: /dev/input/event1 capabilities: platform *-input:2 product: Intel HID events physical id: 4 logical name: input17 logical name: /dev/input/event9 capabilities: platform *-input:3 product: ThinkPad Extra Buttons physical id: 5 logical name: input18 logical name: /dev/input/event10 capabilities: platform *-input:4 product: SYNA8007:00 06CB:CD8C Mouse physical id: 6 logical name: input19 logical name: /dev/input/event4 logical name: /dev/input/mouse0 capabilities: i2c *-input:5 product: Power Button physical id: 7 logical name: input2 logical name: /dev/input/event2 capabilities: platform *-input:6 product: SYNA8007:00 06CB:CD8C Touchpad physical id: 8 logical name: input20 logical name: /dev/input/event5 logical name: /dev/input/mouse1 capabilities: i2c *-input:7 product: Video Bus physical id: 9 logical name: input22 logical name: /dev/input/event11 capabilities: platform *-input:8 product: sof-hda-dsp Mic physical id: a logical name: input23 logical name: /dev/input/event12 *-input:9 product: sof-hda-dsp Headphone physical id: b logical name: input24 logical name: /dev/input/event13 *-input:10 product: sof-hda-dsp HDMI/DP,pcm=3 physical id: c logical name: input25 logical name: /dev/input/event14 *-input:11 product: sof-hda-dsp HDMI/DP,pcm=4 physical id: d logical name: input26 logical name: /dev/input/event15 *-input:12 product: sof-hda-dsp HDMI/DP,pcm=5 physical id: e logical name: input27 logical name: /dev/input/event16 *-input:13 product: AT Translated Set 2 keyboard physical id: f logical name: input3 logical name: /dev/input/event3 logical name: input3::capslock logical name: input3::numlock logical name: input3::scrolllock capabilities: i8042 *-input:14 product: TPPS/2 ALPS TrackPoint physical id: 10 logical name: input5 logical name: /dev/input/event6 logical name: /dev/input/mouse2 capabilities: i8042 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages P
[Kernel-packages] [Bug 2062546] Re: Ubuntu 22.04 Lock Screen is changing the brightness level automatically - Asus Vivobook
Does it only happen in the lock screen? Assuming you're using gnome, does turning off automatic brightness make a difference? https://help.gnome.org/users/gnome-help/stable/power-autobrightness.html.en https://itsfoss.com/automatic-brightness-ubuntu/ ** Changed in: linux-signed-hwe-6.5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2062546 Title: Ubuntu 22.04 Lock Screen is changing the brightness level automatically - Asus Vivobook Status in linux-signed-hwe-6.5 package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 Lock Screen is changing the brightness level automatically - Asus Vivobook OLED 15. Also, fingerprint scanner seems not to work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 17:38:06 2024 InstallationDate: Installed on 2024-04-18 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2062546/+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 2062502] Re: linux-firmware package breaks iwlwifi
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2062502 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2062502 Title: linux-firmware package breaks iwlwifi Status in linux-firmware package in Ubuntu: Incomplete Bug description: This package version works: 20230919.git3672ccab-0ubuntu2.1 This one causes firmware SW errors and resets - breaking wifi in iwlwifi driver: 20230919.git3672ccab-0ubuntu2.9 I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade to ...2.9 of the linux-firmware package, I saw many errors that begin like this in syslog: 2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi :00:14.3: Queue 1 is stuck 0 12 2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. 2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi :00:14.3: Start IWL Error Log Dump: 2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi :00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+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 2063074] Re: Waydroid breaks nouveau
Is running waydroid the only way to trigger this issue? Did you observe any problems when not running waydroid? ** 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/2063074 Title: Waydroid breaks nouveau Status in linux package in Ubuntu: Incomplete Bug description: https://waydro.id/ The session is forced to logout. nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30070]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30070]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30107]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30107]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30145]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30145]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 17e0 data 000c nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 17e0 data 0060 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 8 [007f862000 RenderThread[26090]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 8 [007f862000 RenderThread[26090]] subc 0 class c597 mthd 17e0 data 0018 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:neo3373 F pipewire /dev/snd/controlC0: neo3373 F pipewire neo3377 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 07:32:35 2024 InstallationDate: Installed on 2024-03-22 (30 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-31-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash ipv6.disable=1 RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-11 (11 days ago) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063074/+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 2063077] Re: Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101)
** 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/2063077 Title: Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101) Status in linux package in Ubuntu: Incomplete Bug description: Dear Ubuntu maintainers, I think I found a regression in linux 5.15.0-105. In the past few days, my keyboard stopped working after waking up from suspend (sleep), so I couldn't unlock my laptop. Various workarounds found on the internet helped, but I wanted to investigate if it was a gdm issue, grub, or a hardware failure. I managed to narrow it down to the kernel, which is why I'm filing this bug report. AFAICT the only keys that work are the keyboard lights and the brightness knobs (in the Fn functions). I can confirm that 5.15.0-105 has the issue, and I can consistently reproduce it with the following steps: 1. boot fresh with 5.15.0-105 2. login to my account 3. choose suspend from the power menu 4. wake up Following the same steps above with the last kernel available does not cause the issue (package version 5.15.0-101.111). I'll keep using that one for the time being. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-105-generic 5.15.0-105.115 ProcVersionSignature: Ubuntu 5.15.0-105.115-generic 5.15.148 Uname: Linux 5.15.0-105-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philsf 5465 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 02:58:26 2024 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ab7cb5b3-b98e-4d3a-8923-b75a557d5ddc InstallationDate: Installed on 2018-06-07 (2145 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c1 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-105-generic root=UUID=670af779-d73e-4cb4-b272-d3240de0c998 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-5.15.0-105-generic N/A linux-backports-modules-5.15.0-105-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2023 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0TXW78 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/06/2023:br1.14:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0TXW78:rvrA00:cvnDellInc.:ct10:cvr:sku0810: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063077/+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 2063497] Re: MIPI camera on Lenovo Carbon X1 will not work
Thanks for reporting the bug. This will be fixed in the next version of ipu6 driver and kernel update, which is tracked in bug 2061747. -- 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/2063497 Title: MIPI camera on Lenovo Carbon X1 will not work Status in linux package in Ubuntu: New Bug description: I followed the suggestions here for handling the Intel MIPI camera replacing 22.04 for 24.04: https://wiki.ubuntu.com/Lenovo Perhaps I should have installed 22.04? Anyway, this is a new laptop so I went with the new release. I tried both the generic and oem kernel. Same. The pertinent message seems to be: [ 18.420012] intel-ipu6 :00:05.0: Direct firmware load for intel/ipu6ep_fw.bin failed with error -2 [ 18.420017] intel-ipu6 :00:05.0: Requesting signed firmware failed [ 18.420023] intel-ipu6: probe of :00:05.0 failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063497/+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 2062562] Re: Keyboard not working after resume from suspend on Dell XPS 13 laptop
** Changed in: linux-signed (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2062562 Title: Keyboard not working after resume from suspend on Dell XPS 13 laptop Status in linux-signed package in Ubuntu: Incomplete Bug description: After upgrade to 6.5.0-27-generic keyboard stopped working when laptop comes back to life after suspend. When booted with 6.5.0-26-generic everything is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2062562/+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 2062135] Re: Add Cirrus Logic CS35L56 amplifier support
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Chris Chiu (mschiu77) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2062135 Title: Add Cirrus Logic CS35L56 amplifier support Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: SRU Jusitification for Kernel [Impact] Add a driver for the Cirrus Logic CS35L56 amplifier. This is not a standalone HDA device; it provides control of the CS35L56 for systems that use a combination of an HDA codec and CS35L56 amplifiers with audio routed through the HDA codec. If it's not enabled on HDA codec with this amplifier, there will be no sound if play audio via built-in speaker. [Fix] Backport the CS35L56 driver from kernel 6.9-rc [Test Case] 1. Install the kernel w/ CS35L56 driver enabled 2. Install the linux-firmware with latest CS35l56 supported 3. Play audio file on machines w/ CS35L56 amplifier and make sure it's OK [Where problems could occur] Only affects models which have CS35L56 amplifier. Should be no risk to others. = SRU Jusitification for linux-firmware [Impact] No sound if no CS35L56 firmware even the driver is enabled in Linux kernel. [Fix] Add release FW binary of CS35L56 to linux-firmware [Test Case] 1. Install the kernel w/ CS35L56 driver enabled 2. Install the linux-firmware with latest CS35l56 supported 3. Play audio file on machines w/ CS35L56 amplifier and make sure it's OK [Where problems could occur] New firmware is only loaded by the CS35L56, we only need to verify it on the target platform. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2062135/+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 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
** Description changed: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] - The in-tree vsc driver as of v6.8 still need a few fixes to archive the - same supportness to launched Intel IPU6 Camera devices. Commit 1,3, and + The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the + same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] - The dkms is created to be compatible of multiple versions, yet the in- - tree vsc driver transitioning should only happen for kernel >= v6.8. - That is, oem-6.8, noble and linux-unstable will be nominated. + The dkms is created to be compatible of multiple kernel versions, yet + the in-tree vsc driver transitioning should only happen for kernel >= + v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: In Progress Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: In Progress Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+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 2061953] Re: intel_rapl_common: Add support for ARL and LNL
** Tags added: originate-from-203 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2061953 Title: intel_rapl_common: Add support for ARL and LNL Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.8 package in Ubuntu: Fix Released Status in linux source package in Noble: New Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: [Impact] The installer doesn't work without blacklisting intel_rapl_common (snap mounts fail), unless these commits are added. Needs a oneliner fix for both platforms: 4add6e841a3e079 powercap: intel_rapl: Add support for Arrow Lake 876ed77fbed4450 powercap: intel_rapl: Add support for Lunar Lake-M paltform [Test case] Check that snaps work. [Regression potential] Can't regress other platforms, and if these would then fail in other ways, it's still likely better than before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061953/+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 2061953] Re: intel_rapl_common: Add support for ARL and LNL
** Tags added: intel oem-priority originate-from-2044672 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2061953 Title: intel_rapl_common: Add support for ARL and LNL Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.8 package in Ubuntu: Fix Released Status in linux source package in Noble: New Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: [Impact] The installer doesn't work without blacklisting intel_rapl_common (snap mounts fail), unless these commits are added. Needs a oneliner fix for both platforms: 4add6e841a3e079 powercap: intel_rapl: Add support for Arrow Lake 876ed77fbed4450 powercap: intel_rapl: Add support for Lunar Lake-M paltform [Test case] Check that snaps work. [Regression potential] Can't regress other platforms, and if these would then fail in other ways, it's still likely better than before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061953/+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 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ivan Hu (ivan.hu) -- 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/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic Status in linux package in Ubuntu: New Bug description: During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at very early stage of booting process. The last messages displayed on the screen are: EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9 There are not journal logs existed when I boot with previous kernel. Here is the list of the impacted machines that I found so far https://certification.canonical.com/hardware/202106-29206/ https://certification.canonical.com/hardware/202106-29207/ https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202007-28059/ https://certification.canonical.com/hardware/202103-28762/ https://certification.canonical.com/hardware/202012-28510/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+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 2058315] Re: Mute/mic-mute LEDs not functioning on a HP platform
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => Chris Chiu (mschiu77) -- 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/2058315 Title: Mute/mic-mute LEDs not functioning on a HP platform Status in OEM Priority Project: New Status in linux package in Ubuntu: New Bug description: [Impact] LEDs on both mute and mic-mute key are not working on a HP platform. [Fix] The quirk in the commit b2d6a1fd0e3e513f5ebfc152d6fedae093df8e21 (ALSA: hda/realtek: Add quirks for HP G11 Laptops using CS35L56) in linux-next can make it work. [Test] 1. Install the v2023.12.1 of upstream sof-bin (https://github.com/thesofproject/sof-bin/releases/tag/v2023.12.1) 2. Then after the quirk is applied, both the mute and mic-mute LEDs on the keys should toggle accordingly on key presses. [Where problems could occur] If the subsystem ID is somehow reused by vendor for newer hardware, the newer hardware may not be functioning correctly. Also it requires correct tplg files to work. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2058315/+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 2058331] Re: Update amd_sfh for AMD strix series
** Changed in: linux-oem-6.8 (Ubuntu Noble) Assignee: Anthony Wong (anthonywong) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2058331 Title: Update amd_sfh for AMD strix series Status in HWE Next: New Status in linux-oem-6.8 package in Ubuntu: New Status in linux-oem-6.8 source package in Noble: New Bug description: Extend MP2 register region to enable family 1AH based family on the supported OEM platforms, needs to be backported into oem-6.8. [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 Following fixes applied to linus tree: * 90184f90c9ac5 HID: amd_sfh: Set the AMD SFH driver to depend on x86 * 6296562f30b1c HID: amd_sfh: Extend MP2 register access to SFH * 2105e8e00da46 HID: amd_sfh: Improve boot time when SFH is available * c1db0073212ef HID: amd_sfh: Avoid disabling the interrupt * bbf0dec306966 HID: amd_sfh: Update HPD sensor structure elements * 333861f4cca6d HID: amd_sfh: Increase sensor command timeout To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058331/+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 2058578] Re: Add support for several cs35l41 amplifier devices (laptop audio support)
6.8 HWE kernel should be available soon some time after 24.04 release, so once that happens you will be able to install the 6.8 HWE kernel in Jammy and have those commits. ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058578 Title: Add support for several cs35l41 amplifier devices (laptop audio support) Status in linux-hwe-6.5 package in Ubuntu: Triaged Bug description: Support for the cs35l41_hda_property table has been already been backported to hwe-6.5-next: commit eec052d5cff271d7bf6854f28c62c4a6650c379b (HEAD -> hwe-6.5-next, tag: Ubuntu-hwe-6.5-6.5.0-27.28_22.04.1, origin/hwe-6.5-next) Support for several devices has been merged to torvalds/linux v6.8 tag: commit e8f897f4afef0031fe618a8e94127a0934896aba (HEAD, tag: v6.8) It would be great if the following commits for sound/pci/hda/cs35l41_hda_property.c could be cherry-picked for release in the near future (listed newest to oldest): b603d95692e47dc6f5f733e93c3841dc0c01e624 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d be220d2e5544ff094142d263db5cf94d034b5e39 c16dfab33f99fc3ff43d48253bc2784ccb84c1de 8c14dbf36424eb751d70c15f9a671549390057b2 7d65d70161ef75a3991480c91668ac11acedf211 ba7053b4b4a4ddcf530fa2b897e697004715d086 d110858a6925827609d11db8513d76750483ec06 ee694e7db47e1af00ffb29f569904a9ed576868f 916d051730ae48aef8b588fd096fefca4bc0590a ed7326a24a1a9af65fafefd86b505e7c3b968f6d 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 b592ed2e1d78a475f781802e441c499ab446975b 8c4c216db8fb84be9c4ca60d72b2066cf28f 2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f I am running on KDE neon 6.0 release 22.04 Linux Scott-Laptop 6.5.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 x86_64 x86_64 x86_64 GNU/Linux This works fine for me: #!/bin/bash git clone cd jammy git remote add upstream https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git fetch upstream git checkout hwe-6.5-next commits="2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f 8c4c216db8fb84be9c4ca60d72b2066cf28f b592ed2e1d78a475f781802e441c499ab446975b b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 ed7326a24a1a9af65fafefd86b505e7c3b968f6d 916d051730ae48aef8b588fd096fefca4bc0590a ee694e7db47e1af00ffb29f569904a9ed576868f d110858a6925827609d11db8513d76750483ec06 ba7053b4b4a4ddcf530fa2b897e697004715d086 7d65d70161ef75a3991480c91668ac11acedf211 8c14dbf36424eb751d70c15f9a671549390057b2 c16dfab33f99fc3ff43d48253bc2784ccb84c1de be220d2e5544ff094142d263db5cf94d034b5e39 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d b603d95692e47dc6f5f733e93c3841dc0c01e624" for c in $commits; do echo $c git cherry-pick $c done cp /boot/config-$(uname -r) .config make -j16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2058578/+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 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: Anthony Wong (anthonywong) => GuoqingJiang (guoqingjiang) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 09:42:52 2024 InstallationDate: Installed on 2022-06-28 (653 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+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 2061040] Re: I2C HID device sometimes fails to initialize causing touchpad to not work
** Changed in: linux (Ubuntu Noble) Assignee: Anthony Wong (anthonywong) => AaronMa (mapengyu) -- 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/2061040 Title: I2C HID device sometimes fails to initialize causing touchpad to not work Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: Hi, Touchpad on my new Lenovo X1 Carbon (Gen12) with the Sensel haptic pad doesn't work on boot. I see this: | [Thu Apr 11 13:57:26 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack reset within 1000 ms | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | ... | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unbalanced collection at end of report description | [Thu Apr 11 13:57:26 2024] hid-generic: probe of 0018:2C2F:0028.0001 failed with error -22 Per the Arch Linux wiki page[1], removing and reloading the `i2c_hid_acpi` seems to fix it: | [Thu Apr 11 13:58:02 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack reset within 1000 ms | [Thu Apr 11 13:58:02 2024] input: SNSL0028:00 2C2F:0028 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-15/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input15 | [Thu Apr 11 13:58:02 2024] input: SNSL0028:00 2C2F:0028 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-15/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input16 | [Thu Apr 11 13:58:02 2024] hid-multitouch 0018:2C2F:0028.0002: input,hidraw0: I2C HID v1.00 Mouse [SNSL0028:00 2C2F:0028] on i2c-SNSL0028:00 | [Thu Apr 11 13:58:03 2024] psmouse serio1: trackpoint: Synaptics TrackPoint firmware: 0x08, buttons: 3/3 | [Thu Apr 11 13:58:03 2024] input: TPPS/2 Synaptics TrackPoint as /devices/platform/i8042/serio1/input/input18 From that Arch Linux wiki page, it seems to be a bug upstream[2] with the commit fixing this: | https://github.com/torvalds/linux/commit/af93a167eda90192563bce64c4bb989836afac1f Or | https://lore.kernel.org/linux- input/20240331182440.14477-1...@kl.wtf/T/#u Can we get fix this backported? | [hloeung@dharkan tmp]$ apt-cache policy linux-image-generic-hwe-24.04 | linux-image-generic-hwe-24.04: | Installed: 6.8.0-22.22 | Candidate: 6.8.0-22.22 | Version table: | *** 6.8.0-22.22 500 | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 Packages | 100 /var/lib/dpkg/status | [hloeung@dharkan tmp]$ uname -a | Linux dharkan.local 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux | [hloeung@dharkan tmp]$ Thanks, Haw [1]: https://wiki.archlinux.org/title/Lenovo_ThinkPad_Z16_Gen_2 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=2271136 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061040/+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 2058483] Re: touchpad not working
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => 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/2058483 Title: touchpad not working Status in linux package in Ubuntu: New Bug description: The touchpad is not in the xinput list and it doesn't work. I'm using hp pavilion 15 ec1021nl ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 14:21:02 2024 InstallationDate: Installed on 2024-03-20 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058483/+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 2058752] Re: ath11k high jitter and packet loss when operating in 802.11ax mode
** Changed in: linux (Ubuntu)
Assignee: Anthony Wong (anthonywong) => AceLan Kao (acelankao)
--
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/2058752
Title:
ath11k high jitter and packet loss when operating in 802.11ax mode
Status in linux package in Ubuntu:
New
Bug description:
On 6.5.0-26-generic, my QCNFA765 cannot really operate in 802.11ax
mode.
I have a Thinkpad P16s Gen 2 with a (soldered, sadly) QCNFA765 card, which
uses the ath11k driver.
I also have a Ruckus R650 AP, which supports wifi6.
Connecting the two and pinging the AP yields the following:
```
64 bytes from 192.168.16.77: icmp_seq=45 ttl=64 time=22.4 ms
64 bytes from 192.168.16.77: icmp_seq=46 ttl=64 time=29.6 ms
64 bytes from 192.168.16.77: icmp_seq=47 ttl=64 time=26.8 ms
64 bytes from 192.168.16.77: icmp_seq=48 ttl=64 time=2174 ms
64 bytes from 192.168.16.77: icmp_seq=49 ttl=64 time=1158 ms
64 bytes from 192.168.16.77: icmp_seq=50 ttl=64 time=130 ms
64 bytes from 192.168.16.77: icmp_seq=51 ttl=64 time=503 ms
64 bytes from 192.168.16.77: icmp_seq=54 ttl=64 time=1832 ms
64 bytes from 192.168.16.77: icmp_seq=55 ttl=64 time=808 ms
64 bytes from 192.168.16.77: icmp_seq=56 ttl=64 time=9.32 ms
64 bytes from 192.168.16.77: icmp_seq=57 ttl=64 time=2.11 ms
64 bytes from 192.168.16.77: icmp_seq=58 ttl=64 time=25.6 ms
64 bytes from 192.168.16.77: icmp_seq=59 ttl=64 time=30.9 ms
64 bytes from 192.168.16.77: icmp_seq=60 ttl=64 time=95.6 ms
^C
--- 192.168.16.77 ping statistics ---
60 packets transmitted, 55 received, 8.3% packet loss, time 59273ms
rtt min/avg/max/mdev = 2.105/275.084/2344.792/560.334 ms, pipe 3
```
Those periodic bursts of >1s latency make some webpages fail to load
and videochats unusable.
No interference is present in my channel of choice.
Nothing interesting is printed in dmesg while the above occurs.
The above does not happen if:
* I disable wifi 6 in the AP
* I ping a wifi 5 AP (I also have an older R710, which is a 802.11ac AP)
* I ping the R650 in wifi 6 mode from a AX210 on kernel 6.2
* I ping the R650 from a completely different OS and device (e.g. Android)
I'll test with a 24.04 daily image next.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 21 16:58:07 2024
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: root=zfs:zroot/ROOT/ubuntu quiet loglevel=4
rtc_cmos.use_acpi_alarm=1 spl.spl_hostid=0x4605c990
RelatedPackageVersions:
linux-restricted-modules-6.5.0-26-generic N/A
linux-backports-modules-6.5.0-26-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/15/2024
dmi.bios.release: 1.18
dmi.bios.vendor: LENOVO
dmi.bios.version: R2FET38W (1.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21K9001NUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrR2FET38W(1.18):bd01/15/2024:br1.18:efr1.11:svnLENOVO:pn21K9001NUS:pvrThinkPadP16sGen2:rvnLENOVO:rn21K9001NUS:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K9_BU_Think_FM_ThinkPadP16sGen2:
dmi.product.family: ThinkPad P16s Gen 2
dmi.product.name: 21K9001NUS
dmi.product.sku: LENOVO_MT_21K9_BU_Think_FM_ThinkPad P16s Gen 2
dmi.product.version: ThinkPad P16s Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058752/+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 2059820] Re: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: Anthony Wong (anthonywong) => En-Wei Wu (rickywu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059820 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1 Status in linux-signed-hwe-6.5 package in Ubuntu: Invalid Bug description: 每次开机 提示一个报错 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-generic-hwe-22.04:amd64: Remove linux-image-generic-hwe-22.04:amd64: Remove linux-image-6.5.0-26-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 29 16:19:20 2024 ErrorMessage: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2024-03-29 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.11 SourcePackage: linux-signed-hwe-6.5 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059820/+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 2059973] Re: my touch pad doesn't wok at all.
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: Anthony Wong (anthonywong) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059973 Title: my touch pad doesn't wok at all. Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: i'm new at linux. firstly i have installed ubuntu as dual boot besides windows 11 pro. that time the touchpad worked as expected. but when i gain confident enough that i can use linux, i installed ubuntu as primary setup, after that the touch pad is not working. it detects the touch pad as follows cat /proc/bus/input/devices I: Bus=0018 Vendor=06cb Product=ce78 Version=0100 N: Name="SYNA2BA6:00 06CB:CE78 Mouse" P: Phys=i2c-SYNA2BA6:00 S: Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA2BA6:00/0018:06CB:CE78.0001/input/input22 U: Uniq= H: Handlers=mouse0 event19 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 I: Bus=0018 Vendor=06cb Product=ce78 Version=0100 N: Name="SYNA2BA6:00 06CB:CE78 Touchpad" P: Phys=i2c-SYNA2BA6:00 S: Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA2BA6:00/0018:06CB:CE78.0001/input/input23 U: Uniq= H: Handlers=mouse1 event20 B: PROP=5 B: EV=1b B: KEY=e520 1 0 0 0 0 B: ABS=2e08003 B: MSC=20 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 02:29:41 2024 InstallationDate: Installed on 2024-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059973/+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 2060193] Re: iwlwifi microcode crash when using wrong password to join a WPA3 access point
** Changed in: linux-firmware (Ubuntu) Assignee: Anthony Wong (anthonywong) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2060193 Title: iwlwifi microcode crash when using wrong password to join a WPA3 access point Status in linux-firmware package in Ubuntu: New Bug description: I noticed that whenever I try to join a wireless network using WPA3 SAE and type the password wrong, I get a microcode crash from iwlwifi. The chip is Intel 9462 (AX201). Ubuntu release 22.04 LTS, faithfully kept up to date. System info available via: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2058226 Crash log seems to be always similar: Apr 3 22:13:55 waplinuc kernel: [1158486.254336] iwlwifi :00:14.3: Not associated and the session protection is over already... Apr 3 22:13:57 waplinuc kernel: [1158487.456868] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Apr 3 22:13:57 waplinuc kernel: [1158487.456960] iwlwifi :00:14.3: Start IWL Error Log Dump: Apr 3 22:13:57 waplinuc kernel: [1158487.456962] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 Apr 3 22:13:57 waplinuc kernel: [1158487.456965] iwlwifi :00:14.3: Loaded firmware version: 77.206b0184.0 QuZ-a0-jf-b0-77.ucode Apr 3 22:13:57 waplinuc kernel: [1158487.456967] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Apr 3 22:13:57 waplinuc kernel: [1158487.456969] iwlwifi :00:14.3: 0x008022F3 | trm_hw_status0 Apr 3 22:13:57 waplinuc kernel: [1158487.456971] iwlwifi :00:14.3: 0x | trm_hw_status1 Apr 3 22:13:57 waplinuc kernel: [1158487.456973] iwlwifi :00:14.3: 0x004C03F2 | branchlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456974] iwlwifi :00:14.3: 0x64CC | interruptlink1 Apr 3 22:13:57 waplinuc kernel: [1158487.456976] iwlwifi :00:14.3: 0x64CC | interruptlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456977] iwlwifi :00:14.3: 0x0001191E | data1 Apr 3 22:13:57 waplinuc kernel: [1158487.456979] iwlwifi :00:14.3: 0x1000 | data2 Apr 3 22:13:57 waplinuc kernel: [1158487.456980] iwlwifi :00:14.3: 0x | data3 Apr 3 22:13:57 waplinuc kernel: [1158487.456982] iwlwifi :00:14.3: 0x04C0678B | beacon time Apr 3 22:13:57 waplinuc kernel: [1158487.456983] iwlwifi :00:14.3: 0x920B688C | tsf low Apr 3 22:13:57 waplinuc kernel: [1158487.456985] iwlwifi :00:14.3: 0x0221 | tsf hi Apr 3 22:13:57 waplinuc kernel: [1158487.456986] iwlwifi :00:14.3: 0x0DFD | time gp1 Apr 3 22:13:57 waplinuc kernel: [1158487.456988] iwlwifi :00:14.3: 0x00A909B7 | time gp2 Apr 3 22:13:57 waplinuc kernel: [1158487.456989] iwlwifi :00:14.3: 0x0001 | uCode revision type Apr 3 22:13:57 waplinuc kernel: [1158487.456991] iwlwifi :00:14.3: 0x004D | uCode version major Apr 3 22:13:57 waplinuc kernel: [1158487.456992] iwlwifi :00:14.3: 0x206B0184 | uCode version minor Apr 3 22:13:57 waplinuc kernel: [1158487.456994] iwlwifi :00:14.3: 0x0351 | hw version Apr 3 22:13:57 waplinuc kernel: [1158487.456995] iwlwifi :00:14.3: 0x00489001 | board version Apr 3 22:13:57 waplinuc kernel: [1158487.456997] iwlwifi :00:14.3: 0x001C | hcmd Apr 3 22:13:57 waplinuc kernel: [1158487.456998] iwlwifi :00:14.3: 0x00023000 | isr0 Apr 3 22:13:57 waplinuc kernel: [1158487.456999] iwlwifi :00:14.3: 0x0004C000 | isr1 Apr 3 22:13:57 waplinuc kernel: [1158487.457001] iwlwifi :00:14.3: 0x08F80002 | isr2 Apr 3 22:13:57 waplinuc kernel: [1158487.457002] iwlwifi :00:14.3: 0x00C3000C | isr3 Apr 3 22:13:57 waplinuc kernel: [1158487.457004] iwlwifi :00:14.3: 0x | isr4 Apr 3 22:13:57 waplinuc kernel: [1158487.457005] iwlwifi :00:14.3: 0x0101001C | last cmd Id Apr 3 22:13:57 waplinuc kernel: [1158487.457006] iwlwifi :00:14.3: 0x0001191E | wait_event Apr 3 22:13:57 waplinuc kernel: [1158487.457008] iwlwifi :00:14.3: 0x54B6 | l2p_control Apr 3 22:13:57 waplinuc kernel: [1158487.457009] iwlwifi :00:14.3: 0x1C02 | l2p_duration Apr 3 22:13:57 waplinuc kernel: [1158487.457011] iwlwifi :00:14.3: 0x0003 | l2p_mhvalid Apr 3 22:13:57 waplinuc kernel: [1158487.457012] iwlwifi :00:14.3: 0x | l2p_addr_match Apr 3 22:13:57 waplinuc kernel: [1158487.457013] iwlwifi :00:14.3: 0x000B | lmpm_pmg_sel Apr 3 22:13:57 waplinuc kernel: [1158487.457015] iwlwifi :00:14.3: 0x | timestamp Apr 3 22:13:57 waplinuc kernel: [1158487.457016] iwlwifi :00:14.3: 0x88D4 | flow_handler Apr 3 22:13:57 waplinuc kernel: [1158487.457058] iwlwifi :00:14.3: Start IWL Error Log Dump: Apr 3 22:13:57 waplinuc kernel: [1158487.457059] iwlwifi :00:14.3: Transp
[Kernel-packages] [Bug 2060308] Re: no bluetooth detected
Need more hardware info to debug. Can you attach the output of lshw and dmesg? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060308 Title: no bluetooth detected Status in linux-signed-hwe-6.5 package in Ubuntu: Incomplete Bug description: no bluetooth detected ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 16:52:43 2024 InstallationDate: Installed on 2022-12-17 (475 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2060308/+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 2060308] Re: no bluetooth detected
** Summary changed: - no bluettoth detected + no bluetooth detected ** Changed in: linux-signed-hwe-6.5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060308 Title: no bluetooth detected Status in linux-signed-hwe-6.5 package in Ubuntu: Incomplete Bug description: no bluetooth detected ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 16:52:43 2024 InstallationDate: Installed on 2022-12-17 (475 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2060308/+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 2060373] Re: package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade: 의존성 문제 - 설정하지 않고 남겨둠
** Changed in: linux (Ubuntu)
Assignee: Anthony Wong (anthonywong) => En-Wei Wu (rickywu)
--
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/2060373
Title:
package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade:
의존성 문제 - 설정하지 않고 남겨둠
Status in linux package in Ubuntu:
New
Bug description:
This occured while system updater installing packages with no user
operation.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-generic-hwe-22.04 6.5.0.26.26
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jungwonyong 2613 F wireplumber
/dev/snd/controlC0: jungwonyong 2613 F wireplumber
/dev/snd/seq:jungwonyong 2607 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sun Apr 7 12:08:46 2024
ErrorMessage: 의존성 문제 - 설정하지 않고 남겨둠
InstallationDate: Installed on 2024-01-25 (73 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ricifp@/vmlinuz-6.5.0-21-generic
root=ZFS=rpool/ROOT/ubuntu_ricifp ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade:
의존성 문제 - 설정하지 않고 남겨둠
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2021
dmi.bios.release: 16.20
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1620
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H470-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1620:bd07/08/2021:br16.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH470-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060373/+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 2060716] Re: Screen flickering again
** Changed in: linux (Ubuntu)
Assignee: Anthony Wong (anthonywong) => AaronMa (mapengyu)
--
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/2060716
Title:
Screen flickering again
Status in linux package in Ubuntu:
New
Bug description:
There is random screen flickering with the build of kernel 6.5.0-27.
Also other builds of 6.5.0 have this flickering.
The *only* build of this version that does work without flickering is
6.5.0-13
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bf 5114 F pipewire
bf 5119 F wireplumber
/dev/snd/controlC0: bf 5119 F wireplumber
/dev/snd/seq:bf 5114 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 9 18:48:35 2024
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=be4de94b-3fb1-44d1-875a-edcd620dc310
InstallationDate: Installed on 2016-03-18 (2944 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=17026de9-c699-420e-ae96-01ac290b69ef ro quiet splash
i915.enable_psr=0 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-27-generic N/A
linux-backports-modules-6.5.0-27-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2023
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N2VET45W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TK000AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN2VET45W(1.30):bd08/29/2023:br1.30:efr1.11:svnLENOVO:pn20TK000AGE:pvrThinkPadX1ExtremeGen3:rvnLENOVO:rn20TK000AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TK_BU_Think_FM_ThinkPadX1ExtremeGen3:
dmi.product.family: ThinkPad X1 Extreme Gen 3
dmi.product.name: 20TK000AGE
dmi.product.sku: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
dmi.product.version: ThinkPad X1 Extreme Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060716/+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 2060748] Re: iwlwifi error popping up every few minutes in Kubuntu 23.10 using Intel AX210 card
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => AceLan Kao (acelankao) -- 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/2060748 Title: iwlwifi error popping up every few minutes in Kubuntu 23.10 using Intel AX210 card Status in linux package in Ubuntu: New Bug description: I just installed Kubuntu 23.10 (using latest default kernel) on a new desktop PC I built, which uses an AX210NGW DTK M.2 wifi/bluetooth card. Here is output from lspci -v: e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15 Memory at ba30 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi Wifi error popping up every few minutes in Kubuntu I just installed Kubuntu 23.10 on a new desktop PC I built, which uses an AX210NGW DTK M.2 wifi card: Code: e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15 Memory at ba30 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi The internet seems to be somewhat working, but at least once a minute I have two "Network Management" error notifications that pop up in KDE that say "Connection Wired Connection 3 deactivated" and "Wired Interface e2x52e8ae7d39d1: IP configuration was unavailable". I checked the logs in /var/log/dmesg and saw that there were a ton of iwlwifi error messages in there that look like this: [ 44.926474] kernel: Intel(R) Wireless WiFi driver for Linux [ 44.926508] kernel: iwlwifi :e4:00.0: enabling device ( -> 0002) [ 44.927758] kernel: iwlwifi :e4:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x8000 [ 44.927763] kernel: iwlwifi :e4:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000 [ 44.931064] kernel: iwlwifi :e4:00.0: api flags index 2 larger than supported by driver [ 44.931076] kernel: iwlwifi :e4:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41 [ 44.931318] kernel: iwlwifi :e4:00.0: loaded firmware version 83.e8f84e98.0 ty-a0-gf-a0-83.ucode op_mode iwlmvm [ 44.955070] kernel: Bluetooth: Core ver 2.22 [ 44.955089] kernel: NET: Registered PF_BLUETOOTH protocol family [ 44.955090] kernel: Bluetooth: HCI device and connection manager initialized [ 44.955095] kernel: Bluetooth: HCI socket layer initialized [ 44.955097] kernel: Bluetooth: L2CAP socket layer initialized [ 44.955101] kernel: Bluetooth: SCO socket layer initialized [ 45.275827] kernel: Bluetooth: hci0: Device revision is 0 [ 45.275833] kernel: Bluetooth: hci0: Secure boot is enabled [ 45.275836] kernel: Bluetooth: hci0: OTP lock is enabled [ 45.275838] kernel: Bluetooth: hci0: API lock is enabled [ 45.275840] kernel: Bluetooth: hci0: Debug lock is disabled [ 45.275842] kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 45.275845] kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 [ 45.276888] kernel: nvidia :c1:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none [ 45.278400] kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi [ 45.278415] kernel: Bluetooth: hci0: Boot Address: 0x100800 [ 45.278416] kernel: Bluetooth: hci0: Firmware Version: 254-28.23 [ 47.405919] kernel: iwlwifi :e4:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20 [ 47.405936] kernel: iwlwifi :e4:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f [ 47.405945] kernel: iwlwifi :e4:00.0: WFPM_AUTH_KEY_0: 0x90 [ 47.405955] kernel: iwlwifi :e4:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0 [ 47.493908] kernel: iwlwifi :e4:00.0: Registered PHC clock: iwlwifi-PTP, with index: 2 [
[Kernel-packages] [Bug 2060770] Re: NVMe drive fails at high write workload after kernel upgrades
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => 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/2060770 Title: NVMe drive fails at high write workload after kernel upgrades Status in linux package in Ubuntu: New Bug description: My problem is similarly described in this old thread: https://unix.stackexchange.com/questions/742360/ journalctl message: one of the many related logs Apr 09 15:37:40.096850 ** kernel: Linux version 6.5.0-26-lowlatency (buildd@lcy02-amd64-109) (x86_64-linux-gnu-gcc-12 (Ubunntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #26.1~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Mar 13 10:41:42 UTC (Ubuntu 6.5.0-26.26.1~22.04.1-lowlatency 6.5.13) Apr 09 15:43:46.238697 ** kernel: nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 Apr 09 15:43:46.239162 ** kernel: nvme nvme0: Does your device have a faulty power saving mode enabled? Apr 09 15:43:46.239266 ** kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug Apr 09 15:43:46.690200 ** kernel: nvme :06:00.0: enabling device ( -> 0002) Apr 09 15:43:46.690409 ** kernel: nvme nvme0: Disabling device after reset failure: -19 Apr 09 15:43:46.698188 ** kernel: I/O error, dev nvme0n1, sector 1216896 op 0x1:(WRITE) flags 0xc800 phys_seg 1 prio clas> I was using 22.04.4 with hwe kernel, as shown above (kernel 6.5) upgrade to 24.04 dev hoping the problem would be resolved, but no it still exists (kernel 6.8) The problem happens after some kernel upgrades that I'd done after 2024-03-01, but I cannot pinpoint when; the nvme_core kernel param as shown in the message above does not help. The problem does NOT exist with 22.04 regular kernel: Currently I'd created a VM to perform my heavy write workload using pci passthrough of the NVMe drive, and it works okay. Cannot downgrade host to older kernel because of ZFS pool being upgraded VM info (where my NVMe drive works okay) uname -r 5.15.0-78-lowlatency lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.4 LTS Release:22.04 Codename: jammy (maybe) related hardware spec CPU: AMD Ryzen 5750G (x8x4x4) Chipset: AMD B450 NVMe: Samsung MZ1LB960HBJR-000FB (PM983a, f/w EDW73F2Q) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060770/+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 2060989] Re: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess r
** Changed in: linux (Ubuntu)
Assignee: Anthony Wong (anthonywong) => En-Wei Wu (rickywu)
--
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/2060989
Title:
package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
install/upgrade: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
New
Bug description:
-
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nela 2694 F wireplumber
/dev/snd/controlC1: nela 2694 F wireplumber
/dev/snd/seq:nela 2674 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Apr 11 10:13:36 2024
ErrorMessage: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-03-30 (12 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
install/upgrade: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2021
dmi.bios.release: 1.27
dmi.bios.vendor: LENOVO
dmi.bios.version: HACN27WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion S7 15ACH6
dmi.ec.firmware.release: 1.27
dmi.modalias:
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:
dmi.product.family: Legion S7 15ACH6
dmi.product.name: 82K8
dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
dmi.product.version: Legion S7 15ACH6
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060989/+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 2060981] Re: ACPI BIOS errors
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => Ivan Hu (ivan.hu) -- 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/2060981 Title: ACPI BIOS errors Status in linux package in Ubuntu: New Bug description: dmesg show the below ACPI errors, is this normal? # dmesg | grep -i acpi [0.00] BIOS-e820: [mem 0x59cf8000-0x59dc3fff] ACPI data [0.00] BIOS-e820: [mem 0x59dc4000-0x59eb] ACPI NVS [0.00] reserve setup_data: [mem 0x59cf8000-0x59dc3fff] ACPI data [0.00] reserve setup_data: [mem 0x59dc4000-0x59eb] ACPI NVS [0.00] efi: ACPI=0x59dc3000 ACPI 2.0=0x59dc3014 TPMFinalLog=0x59e4a000 SMBIOS=0x5a609000 SMBIOS 3.0=0x5a608000 MEMATTR=0x528f6018 ESRT=0x53983818 MOKvar=0x5a5e4000 INITRD=0x4fde3f98 RNG=0x59d28018 TPMEventLog=0x4fdc7018 [0.020042] ACPI: Early table checksum verification disabled [0.020046] ACPI: RSDP 0x59DC3014 24 (v02 _ASUS_) [0.020052] ACPI: XSDT 0x59DC2728 00011C (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020060] ACPI: FACP 0x59DBD000 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [0.020066] ACPI: DSDT 0x59D6 05C524 (v02 _ASUS_ Notebook 01072009 INTL 20191018) [0.020070] ACPI: FACS 0x59EBC000 40 [0.020074] ACPI: MCFG 0x59DC1000 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [0.020077] ACPI: SSDT 0x59DBE000 00255D (v02 CpuRef CpuSsdt 3000 INTL 20191018) [0.020081] ACPI: FIDT 0x59D5F000 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020084] ACPI: ECDT 0x59D5E000 C1 (v01 _ASUS_ Notebook 01072009 AMI. 0005) [0.020088] ACPI: MSDM 0x59D5D000 55 (v03 _ASUS_ Notebook 01072009 ASUS 0001) [0.020092] ACPI: SSDT 0x59D58000 004F42 (v02 DptfTa DptfTabl 1000 INTL 20191018) [0.020095] ACPI: SSDT 0x59D56000 0017B5 (v02 SaSsdt SaSsdt 3000 INTL 20191018) [0.020099] ACPI: SSDT 0x59D52000 003350 (v02 INTEL IgfxSsdt 3000 INTL 20191018) [0.020103] ACPI: SSDT 0x59D46000 00B1B2 (v02 INTEL TcssSsdt 1000 INTL 20191018) [0.020106] ACPI: HPET 0x59D45000 38 (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020110] ACPI: APIC 0x59D44000 00012C (v04 _ASUS_ Notebook 01072009 AMI 0113) [0.020114] ACPI: SSDT 0x59D43000 0002A7 (v02 _ASUS_ TcssSsdt INTL 20191018) [0.020118] ACPI: SSDT 0x59D3B000 007504 (v02 _ASUS_ TglU_Rvp 1000 INTL 20191018) [0.020122] ACPI: NHLT 0x59D39000 001B54 (v00 _ASUS_ Notebook 01072009 AMI 0113) [0.020126] ACPI: LPIT 0x59D38000 CC (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020129] ACPI: SSDT 0x59D36000 00012A (v02 _ASUS_ TbtTypeC INTL 20191018) [0.020133] ACPI: DBGP 0x59D35000 34 (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020137] ACPI: DBG2 0x59D34000 54 (v00 _ASUS_ Notebook 01072009 AMI 0113) [0.020141] ACPI: SSDT 0x59D33000 000D8A (v02 _ASUS_ UsbCTabl 1000 INTL 20191018) [0.020145] ACPI: DMAR 0x59D32000 B8 (v02 INTEL EDK2 0002 0113) [0.020148] ACPI: SSDT 0x59D31000 0004B8 (v02 HgRef HgRpSsdt 1000 INTL 20191018) [0.020152] ACPI: SSDT 0x59D3 000144 (v02 Intel ADebTabl 1000 INTL 20191018) [0.020155] ACPI: BGRT 0x59D2F000 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020159] ACPI: UEFI 0x59E28000 00063A (v01 INTEL RstVmdE ?? ) [0.020163] ACPI: UEFI 0x59E27000 5C (v01 INTEL RstVmdV ?? ) [0.020166] ACPI: TPM2 0x59D2E000 4C (v04 _ASUS_ Notebook 0001 AMI ) [0.020170] ACPI: SSDT 0x59D2B000 002495 (v01 OptRf1 Opt1Tabl 1000 INTL 20191018) [0.020173] ACPI: PTDT 0x59D2A000 000D44 (v00 _ASUS_ Notebook 0005 MSFT 010D) [0.020177] ACPI: WSMT 0x59D37000 28 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020181] ACPI: FPDT 0x59D29000 44 (v01 _ASUS_ A M I 01072009 AMI 0113) [0.020184] ACPI: Reserving FACP table memory at [mem 0x59dbd000-0x59dbd113] [0.020186] ACPI: Reserving DSDT table memory at [mem 0x59d6-0x59dbc523] [0.020187] ACPI: Reserving FACS table memory at [mem 0x59ebc000-0x59ebc03f] [0.020187] ACPI: Reserving MCFG table memory at [mem 0x59dc1000-0x59dc103b] [0.020188] ACPI: Reserving SSDT table memory at [mem 0x59dbe000-0x59dc055c] [0.020189] ACPI: Reserving FIDT table memory at [mem 0x59d5f000-0x59d5f
[Kernel-packages] [Bug 2058750] Re: i915 GPU HANG: ecode 12:1:db96edba
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: Anthony Wong (anthonywong) => GuoqingJiang (guoqingjiang) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058750 Title: i915 GPU HANG: ecode 12:1:db96edba Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: This has happened several times over a period of months when visiting the site https://www.windy.com and viewing satellite images. The computer completely freezes and must be hard restarted. I don't think I have triggered this freeze by visiting any other site. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 14:14:41 2024 InstallationDate: Installed on 2023-04-12 (344 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2058750/+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 2060727] Re: The keyboard does not work after latest kernel update
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => AaronMa (mapengyu) -- 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/2060727 Title: The keyboard does not work after latest kernel update Status in linux package in Ubuntu: Confirmed Bug description: The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not work after the latest kernel update and its subsequent reboot of the laptop. Nothing else is connected to the laptop. -- In /var/log/apt/history.log , the latest we can see is: Start-Date: 2024-04-09 12:37:28 Commandline: apt full-upgrade Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic) Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28) End-Date: 2024-04-09 12:37:51 -- $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ # Note: It's Kubuntu 23.10 -- $ uname -a Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2060217] Re: NFSv4 fails to mount in noble/s390x
This is a valid bug but since IBM has a fix at upstream that will trickle down to our stable kernels, I am un-assigning myself. ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => (unassigned) -- 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/2060217 Title: NFSv4 fails to mount in noble/s390x Status in Release Notes for Ubuntu: New Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Triaged Status in nfs-utils package in Ubuntu: Invalid Bug description: https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/s390x Looks like it has been failing for a long time already. Log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/s390x/n/nfs-utils/20240404_145924_ef255@/log.gz 339s autopkgtest [14:41:04]: test local-server-client: [--- 340s Killed 340s autopkgtest [14:41:05]: test process requested reboot with marker boot1 364s autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds... 372s FAIL: nfs_home not mounted 373s autopkgtest [14:41:38]: test local-server-client: ---] 373s local-server-client FAIL non-zero exit status 1 and 934s autopkgtest [14:50:59]: test kerberos-mount: [--- 935s Initializing database '/var/lib/krb5kdc/principal' for realm 'DEP8', 935s master key name 'K/M@DEP8' 935s Authenticating as principal root/admin@DEP8 with password. 935s Principal "nfs/nfs-server.dep8@DEP8" created. 935s Authenticating as principal root/admin@DEP8 with password. 935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Authenticating as principal root/admin@DEP8 with password. 935s Principal "host/nfs-server.dep8@DEP8" created. 935s Authenticating as principal root/admin@DEP8 with password. 935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 936s exporting *:/storage 938s mount.nfs: mount system call failed for /mnt 938s umount: /mnt: not mounted. 938s autopkgtest [14:51:02]: test kerberos-mount: ---] 939s kerberos-mount FAIL non-zero exit status 32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2060217/+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 2060101] Re: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera
** Also affects: ipu6-drivers (Ubuntu) Importance: Undecided Status: New ** Changed in: ipu6-drivers (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060101 Title: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in ipu6-drivers source package in Jammy: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in ipu6-drivers source package in Noble: New Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060101/+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 2060101] Re: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera
** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Assignee: You-Sheng Yang (vicamo) Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060101 Title: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060101/+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 2058330] Re: Update amd-pmf for AMD strix series
** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oem (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/2058330 Title: Update amd-pmf for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Status in linux-oem source package in Noble: New Bug description: These updates will be enhanced amd-pmf for family 1AH on the supported OEM platforms, including enabling new revision for BIOS notify events, support static slider by APTS (AMD Performance and Thermal State)...etc. Needs to be backported into oem-6.8. Following are commits merged to linus tree for v6.9-rc1: * 8362e862fb879 platform/x86/amd/pmf: Update sps power thermals according to the platform-profiles * 3eecb434d7f21 platform/x86/amd/pmf: Add support to get sps default APTS index values * 48d38f569261b platform/x86/amd/pmf: Add support to get APTS index numbers for static slider * 6262938eef282 platform/x86/amd/pmf: Add support to notify sbios heart beat event * 5fdc8b82aab4c platform/x86/amd/pmf: Add support to get sbios requests in PMF driver * 233f78e11e1fa platform/x86/amd/pmf: Disable debugfs support for querying power thermals * a33e9e106601b platform/x86/amd/pmf: Differentiate PMF ACPI versions To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058330/+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 2047630] Re: Add quirk to disable i915 fastboot on B PC
** Changed in: hwe-next Status: New => 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/2047630 Title: Add quirk to disable i915 fastboot on B PC Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] Some displays connect to the B PC device got the garbled display [Fix] The issue will disappear after commit 5ac860cc52540df8bca27e0bb25b6744df67e8f0, but these patches cannot be backported from 5.19 to 5.15. So add quirk to force disable the i915 fastboot on the device to fix the abnormal display [Test Case] 1. Connect the display and power on the B PC device 2. Check the display for boot up [Where problems could occur] Quirk only on the B PCs. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047630/+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 2055866] Re: Simplify kcontrol naming on Intel MTL platforms
** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2055866 Title: Simplify kcontrol naming on Intel MTL platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] We found some laptops from Lenovo and HP with Intel MTL platform suffer the same MIC-Mute led not working problem just like lp:2049569. [Fix] lp:2049569 adds switch/enum type of control on IPC4 to communicate correctly with MTL SoF FW. However, Lenovo and HP machines requires the additional patches from https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/ to fix the kcontrol naming problem to align with the MTL SoF FW. [Test Case] 1. Make sure the latest firmware-sof is installed. 2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 3. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only required for new sof-audio-pci-intel-mtl driver. The impact should be restricting. We may need more MTL machines to make sure the behavior is the aligned. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055866/+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 2048735] Re: Disable keyboard wakeup for Framework 13
** Tags added: amd oem-priority originate-from-2046275 ** Changed in: hwe-next Status: New => Fix Released ** Tags removed: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048735 Title: Disable keyboard wakeup for Framework 13 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: Framework 13" AMD version has an unexpected behavior that EC triggers a keyboard wakeup event every time the system exits s0i3. This EC keyboard wakeup event is to workaround a different bug. Because of this, the following series is sent to mailing list to disable wakeup from keyboard when on latest BIOS for Framework 13 AMD. https://lore.kernel.org/platform-driver-x86/20231212045006.97581-1-mario.limoncie...@amd.com/T/#mca26ce4d4358b188fc61e8b32c27d62410780c5a 85980669a863 platform/x86/amd/pmc: Move platform defines to header 2d53c0ab61e6 platform/x86/amd/pmc: Only run IRQ1 firmware version check on Cezanne b614a4bd73ef platform/x86/amd/pmc: Move keyboard wakeup disablement detection to pmc-quirks a55bdad5dfd1 platform/x86/amd/pmc: Disable keyboard wakeup on AMD Framework 13 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2048735/+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 2029281] Re: Soundwire support for Dell SKU0C87 devices
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2029281
Title:
Soundwire support for Dell SKU0C87 devices
Status in HWE Next:
Fix Released
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Released
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Fix Released
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2029281
== firmware-sof ==
[Impact]
Missing soundwire firmware support for Intel MTL deivces.
[Fix]
Depends on sof-bin v2.7.1 release from
https://github.com/thesofproject/sof-bin/tree/v2023.09.1. Two commits
specifically:
*
https://github.com/thesofproject/sof-bin/commit/ad8dfcc182d3e0a5ce06a7fe9ed7717a04cad06b
("Add sof-v2.7 for Intel Meteor Lake hardware")
*
https://github.com/thesofproject/sof-bin/commit/5f010669084d64df29d77a436b6ffa0095565668
("Add more sof-v2.7.1 Intel MTL binaries")
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so oem-6.5/jammy is the target
series, and Mantic for best effort MTL support. Noble is also
nominated of course.
== linux ==
[Impact]
Missing soundwire support for Dell SKU0C87 deivces.
[Fix]
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so only OEM-6.5, Mantic, and
Unstable are nominated for fix.
== original bug description ==
kernel: sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4
kernel: sof-audio-pci-intel-mtl :00:1f.3: Direct firmware load for
intel/sof-ipc4/mtl/sof-mtl.ri failed with error -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof firmware file is
missing, you might need to
kernel: sof-audio-pci-intel-mtl :00:1f.3: download it from
https://github.com/thesofproject/sof-bin/
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: failed to load DSP
firmware -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof_probe_work failed
err: -2
kernel: kauditd_printk_skb: 33 callbacks suppressed
Required fixes:
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2029281/+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 2045385] Re: Add ODM driver rtc-pcf85263
@Luca In your case, since you're using the generic kernel, you can ignore the messages for the others. -- 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/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+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 2045386] Re: Add ODM driver gpio-m058ssan
@Luca In your case, since you're using the generic kernel, you can ignore the messages for the others. -- 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/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+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 2045387] Re: Add ODM driver f81604 usb-can
@Luca In your case, since you're using the generic kernel, you can ignore the messages for the others. -- 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/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+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 1996609] Re: AX210 (8086:6020) WLAN init failed ucode -5 on 5.15 intel IoTG kernel
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1996609 Title: AX210 (8086:6020) WLAN init failed ucode -5 on 5.15 intel IoTG kernel Status in HWE Next: Fix Released Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg-5.15 package in Ubuntu: Invalid Status in linux-intel-iotg source package in Focal: Invalid Status in linux-intel-iotg-5.15 source package in Focal: Fix Released Status in linux-intel-iotg source package in Jammy: Fix Released Status in linux-intel-iotg-5.15 source package in Jammy: Invalid Bug description: [Summary] AX210 (8086:6020) WLAN init failed ucode -5 on 5.15 Intel IoTG kernel. [Steps to reproduce] install 5.15 Intel IoTG kernel. [Expected result] WLAN works with no problem. [Actual result] Can't detect WLAN. [Failure rate] 100% The ucode version 66 would not be loaded successfully on this particular model with the folloing error messages: [ 13.231830] kernel: iwlwifi :02:00.0: Detected RF GF, rfid=0x10d000 [ 13.232964] kernel: iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x0. [ 13.233061] kernel: iwlwifi :02:00.0: Start IWL Error Log Dump: [ 13.233062] kernel: iwlwifi :02:00.0: Transport status: 0x004A, valid: 6 [ 13.233064] kernel: iwlwifi :02:00.0: Loaded firmware version: 66.f1c864e0.0 ty-a0-gf-a0-66.ucode [ 13.233065] kernel: iwlwifi :02:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [ 13.233066] kernel: iwlwifi :02:00.0: 0x002002F0 | trm_hw_status0 [ 13.233067] kernel: iwlwifi :02:00.0: 0x | trm_hw_status1 [ 13.233068] kernel: iwlwifi :02:00.0: 0x004DA722 | branchlink2 ... [ 14.094020] kernel: iwlwifi :02:00.0: Failed to run INIT ucode: -5 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996609/+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 2051846] Re: Mute/mic LEDs no function on HP ZBook Power
** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Medium Assignee: Andy Chi (andch) Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051846 Title: Mute/mic LEDs no function on HP ZBook Power Status in OEM Priority Project: Fix Committed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ZBook Power [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2051846/+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 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings
Same as LP#2042500 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: In Progress => 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/1980829 Title: System freeze after resuming from suspend due to PCI ASPM settings 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-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 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-oem-6.0 source package in Focal: Invalid Status in linux-oem-6.1 source package in Focal: Invalid Status in linux-oem-6.5 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-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux-oem-6.5 source package in Kinetic: Invalid Bug description: For OEM-6.1 [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] Below commit fixed the issue, but not going to be merged into mainline. The patch is still under discussion and have other variance, and we already merged the origin patch into oem-6.0 and 5.15/5.19 for a year, so could consider it's safer for us. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ I also created a DMI quirk to make the patches only affects on listed platforms. [Test] The affected machines could suspend/resume well. [Where problems could occur] The patches only affects on the listed platforms, and won't affect other platforms. == For Jammy/Kinetic SRU [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ So, I created a DMI quirk to make the patches only affects on listed platforms. [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The patches only affects on the listed platforms, and won't affect other platforms. == For OEM-6.0 [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The 2 patches look pretty safe to me, they try to preserve the ASPM state of devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980829/+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 2049838] Re: Mute/mic LEDs no function on HP ZBook
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Medium Status: Invalid ** Changed in: linux (Ubuntu Noble) Status: Invalid => Fix Released ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Leo Lin (0xff07) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049838 Title: Mute/mic LEDs no function on HP ZBook Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The mute LEDS are not work properly on some newer HP ZBooks. [Fix] It needs the specific quirk for the hardware layout. Add it accordingly. [Test] Install the patched kernel and click the mute button. Confirm that the LED on the mute key turns on an off according to mute status. [Where problems could occur] This quirk only works if design of the board w.r.t. the same subsystem ID is unchanged. Otherwise the quirk will not work (the mute LEDs won't function normally). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2049838/+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 2045387] Re: Add ODM driver f81604 usb-can
@Luca You can ignore the message about testing linux-ibm-gt-fips. -- 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/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+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 1989046] Re: support independent clock and LED GPIOs for Intel IPU6 platforms
** Tags added: fixed-linux-oem-6.5 -- 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/1989046 Title: support independent clock and LED GPIOs for Intel IPU6 platforms Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] When migrated from power_ctrl_logic driver to int3472, two additional independent CLK/LED GPIOs other than powerdown/reset must be probed exceptionally. [Fix] Vendor provided patch in https://github.com/intel/ipu6-drivers/blob/2b8a592dc63e117d8f5af5f32a10d7e0651832d2/patch/int3472-support-independent-clock-and-LED-gpios-5.17+.patch. [Test Case] Tested on both TGL/ADL platforms against nominated kernels. [Where problems could occur] This adds exceptional cases with fallbacks to the original function. No one else is affected. [Other Info] This is an essential part for switching from power_ctrl_logic based GPIO control mechanism to the generic, upstreamed int3472 driver. Affects all IPU6 platforms that are to run new IPU6 driver dump in 202208. == original bug report == Per https://github.com/intel/ipu6-drivers/commit/f771bd3cb9f324a393a75e068a039bd1f9611026 and https://github.com/intel/ipu6-drivers/commit/2b8a592dc63e117d8f5af5f32a10d7e0651832d2, additional fix for INT3472 is necessary to probe camera sensor GPIOs on Intel IPU6 platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1989046/+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 2029372] Re: Remove force_probe for i915 on MTL platforms to ease the development process
** Tags added: fixed-noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2029372 Title: Remove force_probe for i915 on MTL platforms to ease the development process Status in HWE Next: Fix Released Status in linux package in Ubuntu: Won't Fix Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] [Impact] To remove force_probe for i915 on MTL platforms to ease the development process. [Fix] Sauced fix to remove force_probe flag. [Test Case] i915 should then be enabled automatically without the need of i915.force_probe= in boot parameters. [Where problems could occur] This is for the convenience of early development. i915 may not be stable/fully functional on MTL platforms. [Other Info] While this is only meant for kernel >= 6.5, only oem-6.5 is nominated for fix so far. == original bug report == i915 on MTL platforms still takes an additional boot parameter i915.force_probe= to drive the graphic device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2029372/+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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
Upstream bug: https://gitlab.freedesktop.org/drm/intel/-/issues/9739 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #9739 https://gitlab.freedesktop.org/drm/intel/-/issues/9739 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2039925] Re: Realtek RTS5264 SD 7.0 cardreader support
** Also affects: linux (Ubuntu Noble)
Importance: High
Assignee: You-Sheng Yang (vicamo)
Status: In Progress
** Also affects: linux-oem-6.5 (Ubuntu Noble)
Importance: Undecided
Status: Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2035299] Re: dell-uart-backlight fails to communicate with the scalar IC somtimes.
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Also affects: linux-oem-6.5 (Ubuntu Noble)
Importance: Undecided
Status: Invalid
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2035299
Title:
dell-uart-backlight fails to communicate with the scalar IC somtimes.
Status in HWE Next:
New
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux source package in Noble:
Triaged
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[Impact]
Boots up the system and sometimes we can see below messages and that leads to
backlight driver doesn't get loaded.
[ 86.424880] dell_uart_backlight:dell_uart_get_display_mode:tx: 6a 10 85
[ 86.603936] [7439] dell_uart_backlight:dell_uart_get_display_mode:rx: NULL
[ 87.596047] dell_uart_backlight:dell_uart_get_display_mode:tx: 6a 10 85
[ 87.775209] [7439] dell_uart_backlight:dell_uart_get_display_mode:rx: NULL
[Fix]
After applying the patch below, it seems that the read() command may fail to
receive a response, even when increasing the retry times. It never gets a
response when it fails.
fbf84fb368923 ("UBUNTU: SAUCE: platform/x86: dell-uart-backlight:
replace chars_in_buffer() with flush_chars()")
To fix this, try adding a small delay after the write() function as a
workaround.
[Test case]
1. Add dell_uart_backlight.dyndbg="+pt" to the kernel cmdline
2. Boots up the system and check dmesg
3. Make sure there is no dell_uart_backlight rx NULL message in dmesg
4. Try to unload/reload dell_uart_backlight couple times and check dmesg again
[Where problems could occur]
sleep for 1ms is pretty short that it's not possible to lead to messages loss.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2035299/+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 1999556] Re: commit cf58599cded35cf4affed1e659c0e2c742d3fda7 seems to be missing in kinetic master to remove "hio" reference from Makefile
** Tags added: fixed-linux-oem-6.5
--
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/1999556
Title:
commit cf58599cded35cf4affed1e659c0e2c742d3fda7 seems to be missing in
kinetic master to remove "hio" reference from Makefile
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
Added Linux kernel remote branch for Kinetic raspi to test with 22.04
install (both master and master-next branches). When running "make
clean" noticed error referencing "hio" driver that's been removed from
Jammy kernels:
$ make clean
scripts/Makefile.clean:15: ubuntu/hio/Makefile: No such file or directory
make[2]: *** No rule to make target 'ubuntu/hio/Makefile'. Stop.
make[1]: *** [scripts/Makefile.clean:62: ubuntu/hio] Error 2
make: *** [Makefile:1858: _clean_ubuntu] Error 2
Found that commit cf58599cded35cf4affed1e659c0e2c742d3fda7 missing:
commit cf58599cded35cf4affed1e659c0e2c742d3fda7
Author: Thomas Lamprecht
Date: Sat Mar 12 16:19:10 2022 +0100
Ubuntu: remove leftover reference to ubuntu/hio driver
A single reference to the hio driver was forgotten when it was removed
recently. While this reference is not a problem for the build itself, it
breaks the __clean target from 'scripts/Makefile.clean' here, as make
cannot enter the "ubuntu/hio" folder for cleaning due to ENOENT.
Fixes: 4ea6dd9afa0a0d ("UBUNTU: Remove ubuntu/hio driver")
Signed-off-by: Thomas Lamprecht
Acked-by: Tim Gardner
Signed-off-by: Paolo Pisati
Here's some additional information for code repositories (didn't know
if this was helpful),
remote.kinetic-raspi.url=https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/kinetic
remote.kinetic-raspi.fetch=+refs/heads/*:refs/remotes/kinetic-raspi/*
branch.kinetic-master-next.remote=kinetic-raspi
branch.kinetic-master-next.merge=refs/heads/master-next
branch.kinetic-master.remote=kinetic-raspi
branch.kinetic-master.merge=refs/heads/master
[Test Case]
See above.
[Fix]
Pick commit cf58599cded35cf4affed1e659c0e2c742d3fda7 from jammy.
[Where Problems Could Occur]
Build failures.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999556/+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 1946433] Re: Fix only reach PC3 when ethernet is plugged r8169
** Changed in: hwe-next Status: Confirmed => Fix Released ** Tags added: fixed-linux-oem-6.5 -- 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/1946433 Title: Fix only reach PC3 when ethernet is plugged r8169 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released 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-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.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 Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux-oem-5.13 source package in Kinetic: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.13 source package in Lunar: Invalid Status in linux-oem-5.14 source package in Lunar: Invalid Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-5.13 source package in Mantic: Invalid Status in linux-oem-5.14 source package in Mantic: Invalid Status in linux-oem-5.17 source package in Mantic: Invalid Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] System only can reach PC3, and it affects power consumption alot. [Fix] Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state issue, but also fixes network speed issue. V7: https://patchwork.kernel.org/project/netdevbpf/patch/20211016075442.650311-5-kai.heng.f...@canonical.com/ V6: https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/ [Test] Verified on 2 different systems which has PC state issue and has network speed issue, these patches fix both issues. [Where problems could occur] It toggles ASPM on and off depends on the network traffic during runtime, I don't think it'll lead to any regressions. Some potential issues have been addressed during the patch submitting. It's v6 now and accepted by upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946433/+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 2002089] Re: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1
** Tags added: fixed-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2002089
Title:
Mediatek FM350-GL wwan module failed to init: Invalid device status
0x1
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Won't Fix
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
[SRU Justification]
[Impact]
Mediatek FM350-GL wwan module failed to init: Invalid device status
0x1:
[ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002)
[ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1
[Fix]
The t7xx driver once received following fixes to complete its functions in
v6.1-rc1:
d20ef656f994 net: wwan: t7xx: Add AP CLDMA
007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration
140424d90165 net: wwan: t7xx: PCIe reset rescan
87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and coredump
collection
b0bc1709b768 net: wwan: t7xx: Devlink documentation
However it was soon reverted for a second revision. Before that, in bug
1990700
we need the first (reverted) patch "net: wwan: t7xx: Add AP CLDMA" to fix
device
suspend in a minimum level for development. Then, in this bug 2002089, a fully
revised resubmission is now available.
An additional patch from v6.1, commit bb67012331f7 ("net: devlink:
extend info_get() version put to indicate a flash component"), is
necessary for oem-6.0 backport.
[Test Case]
Modprobe on new platforms that suffers this invalid device status issue,
and run suspend/resume tests to ensure bug 1990700 is still in a good
state.
[Where problems could occur]
This re-introduce the device firmware update support via devlink, so far
it has been tested many times from 3rd party/vendor, but might still
bump into platform compatibility issue as we have here.
[Other Info]
While this is only planned for oem-6.0/oem-6.1 and on, only U/L/OEM-6.x
are nominated for fix.
== original bug report ==
[ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002)
[ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: u 1216 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-01-05 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enp0s31f6 no wireless extensions.
wwan0 no wireless extensions.
MachineType: Dell Inc. Precision 3480
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem
root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.0.0-1010-oem N/A
linux-backports-modules-6.0.0-1010-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.7
Tags: jammy
Uname: Linux 6.0.0-1010-oem x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: False
dmi.bios.date: 12/22/2022
dmi.bios.release: 0.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.6.55
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02:
dmi.product.family: Latitude
dmi.product.name: Precision 3480
[Kernel-packages] [Bug 2002601] Re: Wireless: Enable RTL8852BE wifi driver
** Tags added: fixed-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2002601 Title: Wireless: Enable RTL8852BE wifi driver 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-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+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 2009014] Re: Some QHD panels fail to refresh when PSR2 enabled
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009014 Title: Some QHD panels fail to refresh when PSR2 enabled Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] Some QHD (2560x1440) panels which support PSR2 refresh the display abnormally. The display frequently stop responding for few seconds on all user interactions, ex. mouse movement, TTY and any APP GUI. There's no problem on the external monitor. After disabling PSR, the problem will be gone. [Fix] Intel release a fix to calculate the wake up line count and configure them into PSR2_CTL accordingly. [Test] Verified on the problematic panels to check if the display responds smoothly to mouse movement. [Where problems could occur] Only affects the panels on some particular panels which supports PSR2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009014/+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 2007516] Re: screen flicker after PSR2 enabled
** Tags added: fixed-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007516 Title: screen flicker after PSR2 enabled Status in HWE Next: Fix Released Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007516/+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 2007516] Re: screen flicker after PSR2 enabled
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007516 Title: screen flicker after PSR2 enabled Status in HWE Next: Fix Released Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007516/+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 2009065] Re: overlayfs mounts as R/O over idmapped mount
** Tags added: fixed-linux-oem-6.5
--
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/2009065
Title:
overlayfs mounts as R/O over idmapped mount
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-5.19 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.19 source package in Kinetic:
Invalid
Bug description:
Reproducer:
create unprivileged LXC container
$ lxc launch ubuntu:22.04 idmap-test
$ lxc exec idmap-test bash
check that root is idmapped by:
$ cat /proc/self/mountinfo | grep idmap
780 675 8:1 /var/snap/lxd/common/lxd/storage-
pools/default/containers/idmap-test/rootfs / rw,relatime,idmapped
shared:323 master:319 - ext4 /dev/sda1 rw,discard,errors=remount-ro
$ mkdir {work,upper,lower,ovl}
$ mount -t overlay overlay -o lowerdir=lower,upperdir=upper,workdir=work ovl
$ touch ovl/test
touch: cannot touch 'ovl/test': Read-only file system
The problem is in __vfs_removexattr_noperm() function that called from
ovl_workdir_create().
In dmesg I can see an error:
overlayfs: failed to create directory work/work (errno: 1); mounting read-only
Reproducible on:
# uname -a
Linux ubuntu 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan
30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
Suspicious commit:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/fs/overlayfs/overlayfs.h?h=Ubuntu-hwe-5.19-5.19.0-32.33_22.04.1=3418435738af5730918fafbdfe2905a98ce2ef05
Chunk:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(_user_ns, dentry, name, value, size,
flags);
+ inode_unlock(inode);
should be:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(ovl_upper_mnt_userns(ofs), dentry, name,
value, size, flags);
+ inode_unlock(inode);
I'll send a patch soon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009065/+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 1987998] Re: LSM: Configuring Too Many LSMs Causes Kernel Panic on Boot
** Tags added: fixed-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1987998
Title:
LSM: Configuring Too Many LSMs Causes Kernel Panic on Boot
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Bug description:
BugLink: https://bugs.launchpad.net/bugs/1987998
[Impact]
The Ubuntu kernel carries an out of tree patchet, known as "LSM:
Module stacking for AppArmor" upstream, to enable stackable LSMs for
containers. The revision the Ubuntu kernel carries is an older one,
from 2020, and has some slight divergences from the latest revision in
development.
One such divergence, is support for Landlock as a stackable LSM. When
the stackable LSM patchset was applied, Landlock was still in
development and not mainlined yet, and wasn't present in the earlier
revision of the "LSM: Module stacking for AppArmor" patchset. Support
for this was added by us.
There was a minor omission made during enabling support for Landlock.
The LSM slot type was marked as LSMBLOB_NEEDED, when it should have
been LSMBLOB_NOT_NEEDED.
Landlock itself does not provide any of the hooks that use a struct
lsmblob, such as secid_to_secctx, secctx_to_secid, inode_getsecid,
cred_getsecid, kernel_act_as task_getsecid_subj task_getsecid_obj and
ipc_getsecid.
When we set .slot = LSMBLOB_NEEDED, this indicates that we need an
entry in struct lsmblob, and we need to increment LSMBLOB_ENTRIES by
one to fit the entry into the secid array:
#define LSMBLOB_ENTRIES ( \
(IS_ENABLED(CONFIG_SECURITY_SELINUX) ? 1 : 0) + \
(IS_ENABLED(CONFIG_SECURITY_SMACK) ? 1 : 0) + \
(IS_ENABLED(CONFIG_SECURITY_APPARMOR) ? 1 : 0) + \
(IS_ENABLED(CONFIG_BPF_LSM) ? 1 : 0))
struct lsmblob {
u32 secid[LSMBLOB_ENTRIES];
};
Currently, we don't increment LSMBLOB_ENTRIES by one to make an entry
for Landlock, so for the Ubuntu kernel, we can fit a maximum of two
entries, one for Apparmor and one for bpf.
If you try and configure three LSMs like so and reboot:
GRUB_CMDLINE_LINUX_DEFAULT="lsm=landlock,bpf,apparmor"
You will receive the following panic:
LSM: Security Framework initializing
landlock: Up and running.
LSM support for eBPF active
Kernel panic - not syncing: security_add_hooks Too many LSMs registered.
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-46-generic #49-Ubuntu
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
Call Trace:
show_stack+0x52/0x5c
dump_stack_lvl+0x4a/0x63
dump_stack+0x10/0x16
panic+0x149/0x321
security_add_hooks+0x45/0x13a
apparmor_init+0x189/0x1ef
initialize_lsm+0x54/0x74
ordered_lsm_init+0x379/0x392
security_init+0x40/0x49
start_kernel+0x466/0x4dc
x86_64_start_reservations+0x24/0x2a
x86_64_start_kernel+0xe4/0xef
secondary_startup_64_no_verify+0xc2/0xcb
---[ end Kernel panic - not syncing: security_add_hooks Too many LSMs
registered. ]---
There is a check added in security_add_hooks() that makes sure that
you cannot configure too many LSMs:
if (lsmid->slot == LSMBLOB_NEEDED) {
if (lsm_slot >= LSMBLOB_ENTRIES)
panic("%s Too many LSMs registered.\n", __func__);
lsmid->slot = lsm_slot++;
init_debug("%s assigned lsmblob slot %d\n", lsmid->lsm,
lsmid->slot);
}
A workaround is to enable no more than 2 LSMs until this is fixed.
[Fix]
If you read the following mailing list thread on linux-security-
modules from May 2021:
https://lore.kernel.org/selinux/202105141224.942DE93@keescook/T/
It is explained that Landlock does not provide any of the hooks that
use a struct lsmblob, such as secid_to_secctx, secctx_to_secid,
inode_getsecid, cred_getsecid, kernel_act_as task_getsecid_subj
task_getsecid_obj and ipc_getsecid.
I verified this with:
ubuntu-jammy$ grep -Rin "secid_to_secctx" security/landlock/
ubuntu-jammy$ grep -Rin "secctx_to_secid" security/landlock/
ubuntu-jammy$ grep -Rin "inode_getsecid" security/landlock/
ubuntu-jammy$ grep -Rin "cred_getsecid" security/landlock/
ubuntu-jammy$ grep -Rin "kernel_act_as" security/landlock/
ubuntu-jammy$ grep -Rin "task_getsecid_subj" security/landlock/
ubuntu-jammy$ grep -Rin "task_getsecid_obj" security/landlock/
ubuntu-jammy$ grep -Rin "ipc_getsecid" security/landlock/
The fix is to change Landlock from LSMBLOB_NEEDED to
[Kernel-packages] [Bug 2038981] Re: No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038981 Title: No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] With ADM 6300 GPU, there is no external output when plug in a DP monitor after the monitor went to sleep [Fix] Mario provides a patch to fix the issue https://patchwork.kernel.org/project/linux-usb/list/?series=790399 And also below commit is required 134b8c5d8674 drm/amd: Fix detection of _PR3 on the PCIe root port [Test case] 1. Boot up the system with AMD 6300 GPU and plug DP monitor on the card 2. Unplug the DP cable and wait the monitor sleeps 3. Plug in the DP cable again and it should wake up the monitor correctly and output the screen to the monitor [Where problems could occur] The PR3 patch only affects AMD dGPU and should fix AMD BOCO detection logic, and UCSI patch try to set the correct power supply scope which should do no harm to the existing systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038981/+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 2044150] Re: Missing CS35L41 firmware for HP G11 mWS models
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2044150
Title:
Missing CS35L41 firmware for HP G11 mWS models
Status in HWE Next:
Fix Released
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for HP G11 mWS models. In dmesg output it
has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit 980373f58747 ("cirrus: Add CS35L41 firmware for HP G11
models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-103c8c71.wmfw: Fri 31 Mar 2023 10:42:49 W. Europe
Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.65.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.85.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-103c8c71.bin: v0.65.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\gchen\Desktop\HP_Proj\HP_Warg14_103C8B45_220930_exported_tuning\6.61.1\tuning\230609\103C8C47_2306
09_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
Upstream linux-firmware commit:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=980373f5874787b7d98a204feabdccc971c42dc0
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: u 1580 F pulseaudio
/dev/snd/controlC0: u 1580 F pulseaudio
CasperMD5CheckMismatches: ./.disk/casper-uuid-oem ./boot/grub/efi.img
./boot/grub/grub.cfg ./casper/initrd
CasperMD5CheckResult: fail
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin:
LP-PPA-canonical-hwe-team-linux-firmware-staging]
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-stella-jammy-amd64-20230925-542
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-08 (34 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
pc-stella-jammy-amd64-20230925-542
IwConfig:
lono wireless extensions.
enx00e04c6801ec no wireless extensions.
[Kernel-packages] [Bug 2031882] Re: Missing firmware for Intel VPU on Intel Meteor Lake platforms
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2031882 Title: Missing firmware for Intel VPU on Intel Meteor Lake platforms Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Mantic: Fix Released Bug description: [SRU Justification] [Impact] Missing firmware blobs for Intel VPU support on Intel Meteor Lake platform. intel_vpu :00:0b.0: enabling device ( -> 0002) intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 intel_vpu :00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2 intel_vpu :00:0b.0: Failed to initialize VPU device: -2 intel_vpu: probe of :00:0b.0 failed with error -2 [Fix] Upstream Intel VPU linux driver project https://github.com/intel/linux-vpu-driver stores firmware blob in git- lfs. [Test Case] Intel VPU support on Intel Meteor Lake platform is part of the OpenVino framework. It takes many more other components to be installed before VPU on MTL may release its power. Here we simply test the firwmare can be found and loaded. [Where problems could occur] Intel VPU firmware is to be loaded by kernel but used by user land frameworks. While OpenVino is not (yet?) supported natively, this firmware blob alone has no observerible effect yet. [Other Info] While MTL is supported by v6.5 kernel or above, only oem-6.5 and Mantic are nominated by default. == original bug report == Intel Meteor Lake platform supports VPU natively and the driver has been upstreamed in v6.3. A few more steps to enable VPU support in https://github.com/intel/linux-vpu-driver, and firmware is the first one missing. [ 68.602028] intel_vpu :00:0b.0: enabling device ( -> 0002) [ 68.604010] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 [ 68.604013] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2 [ 68.604263] intel_vpu :00:0b.0: Failed to initialize VPU device: -2 [ 68.604272] intel_vpu: probe of :00:0b.0 failed with error -2 The firmware blob can be retrieved by `git lfs pull` from a clone of aforementioned driver repository. The install path would be /lib/firmware/intel/vpu. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2031882/+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 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings
** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress -- 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/1980829 Title: System freeze after resuming from suspend due to PCI ASPM settings 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-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 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-oem-6.0 source package in Focal: Invalid Status in linux-oem-6.1 source package in Focal: Invalid Status in linux-oem-6.5 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-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux-oem-6.5 source package in Kinetic: Invalid Bug description: For OEM-6.1 [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] Below commit fixed the issue, but not going to be merged into mainline. The patch is still under discussion and have other variance, and we already merged the origin patch into oem-6.0 and 5.15/5.19 for a year, so could consider it's safer for us. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ I also created a DMI quirk to make the patches only affects on listed platforms. [Test] The affected machines could suspend/resume well. [Where problems could occur] The patches only affects on the listed platforms, and won't affect other platforms. == For Jammy/Kinetic SRU [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ So, I created a DMI quirk to make the patches only affects on listed platforms. [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The patches only affects on the listed platforms, and won't affect other platforms. == For OEM-6.0 [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The 2 patches look pretty safe to me, they try to preserve the ASPM state of devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980829/+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 2018566] Re: A deadlock issue in scsi rescan task while resuming from S3
** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2018566 Title: A deadlock issue in scsi rescan task while resuming from S3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] During the S3 stress test, the system sometimes hangs when resuming. This is due to the SCSI rescan task being unable to acquire the mutex lock during the resumption from S3. The mutex lock has already been acquired by EH and is waiting for the device to be ready for a rescan. Unfortunately, the mutex lock is never released by either party, leading to a deadlock. [Fix] Kaiheng submitted a patch to fix this issue which defers the rescan if the disk is still suspended so the resume process of the disk device can proceed. https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/ Since the patch has not been accepted by the upstream yet, so submit it to the OEM kernel for now. The similiar patch has been included in v6.4-rc7 6aa0365a3c85 ata: libata-scsi: Avoid deadlock on rescan after device resume [Test] Verified on the machines by me and ODM. [Where problems could occur] It only defers the rescan task, and should not have any impact to current systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2018566/+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 2011389] Re: vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan
** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-oem-6.5 (Ubuntu Lunar) Status: New => Invalid ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2011389 Title: vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] With wwan t7xx driver patched, vmd may fail the probe process because it does not lock properly. [Fix] https://lore.kernel.org/linux- pci/20230313173733.1815277-1-vicamo.y...@canonical.com/T/#u [Test Case] Verify on platforms with FM350 wwan module with prebuilt oem-6.1 or above kernels. No vmd probe error should be found in dmesg. [Where problems could occur] This is the way it should have been done. [Other Info] This is not reproducible with v6.0 or older kernels, so only Lunar and oem-6.1 are nominated for fix. OEM-6.0 patch goes to Gerrit instead. == original bug report == vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan. This happens after bug 2002089 re-added pci rescan feature back to wwan t7xx driver to support firmware updates via devlink. t7xx may call `pci_rescan_bus()` with proper locks, but vmd doesn't. sysfs: cannot create duplicate filename '/devices/.../resource0' Call Trace: sysfs_warn_dup.cold+0x17/0x34 sysfs_add_bin_file_mode_ns+0xc0/0xf0 sysfs_create_bin_file+0x6d/0xb0 pci_create_attr+0x117/0x260 pci_create_resource_files+0x6b/0x150 pci_create_sysfs_dev_files+0x18/0x30 pci_bus_add_device+0x30/0x80 pci_bus_add_devices+0x31/0x80 pci_bus_add_devices+0x5b/0x80 vmd_enable_domain.constprop.0+0x6b7/0x880 [vmd] vmd_probe+0x16d/0x193 [vmd] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011389/+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 2034491] Re: Fix blank display when Thunderbolt monitor is plugged second time
** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-oem-6.5 (Ubuntu Lunar) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034491 Title: Fix blank display when Thunderbolt monitor is plugged second time Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Bug description: [Impact] When a Thunderbolt monitor gets plugged to an AMD laptop for second time, the Thunderbolt monitor remains blank. [Fix] Reinitialize TMU and perform proper Time Synchronization Handshake every time. [Test] The Thunderbolt monitor still has image after many replugging. [Where problems could occur] This change the flow on disabling TMU, which is responsible for time synchronization, so behavior of Thunderbolt docking might be affected. Per my limited test no issue has been observed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034491/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
** Changed in: linux (Ubuntu Noble) Status: New => 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: New Status in linux source package in Noble: Fix Released Bug description: [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2047504] Re: Mute/mic LEDs and speaker no function on some HP platforms
** Changed in: linux-oem-6.5 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047504 Title: Mute/mic LEDs and speaker no function on some HP platforms Status in OEM Priority Project: Fix Committed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: Confirmed Bug description: [Impact] The mic mute/audio mute LEDS and speaker are not work on some HP platforms. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs and speaker are working good. Applied on oem-6.5 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047504/+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 2046681] Re: jammy-oem-6.5: one more pannel needs to disable psr2
** Tags added: somerville ** Summary changed: - jammy-oem-6.5: one more pannel needs to disable psr2 + jammy-oem-6.5: one more panel needs to disable psr2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046681 Title: jammy-oem-6.5: one more panel needs to disable psr2 Status in HWE Next: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2046681 [Impact] The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046681/+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 2025672] Re: Support Realtek RTL8852CE WiFi 6E/BT Combo
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2025672 Title: Support Realtek RTL8852CE WiFi 6E/BT Combo 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-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Invalid Status in linux-firmware source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2025672 [Impact] Realtek RTL8852CE WiFi 6E/BT Combo takes new firmware to enable 6E features. [Fix] * Bluetooth - kernel + 8b1d66b50437 Bluetooth: btrtl: Add support for RTL8852C (v5.19-rc1) + 9a24ce5e29b1 Bluetooth: btrtl: Firmware format v2 support (v6.4-rc1) + bd003fb338af Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C (linux-next) - firmware + 8a2d81176 rtl_bt: Add firmware and config files for RTL8852C (jammy) + d3c922805 rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33 (jammy) + cfbd66816 rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A (jammy) + c51488ffb rtl_bt: Update RTL8852C BT USB firmware to 0xD7B8_FABF (lunar) + 55e744853 rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225 (mantic, change binary format) + 7ed62638b Revert "rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225" (mantic) + 42d31f8f6 rtl_bt: Add firmware v2 file for RTL8852C (mantic) * WiFi - kernel + 59b4cc439f18 wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() (linux-next) - firmware + d2aac63b8 rtw89: 8852c: update fw to v0.27.56.1 (jammy) + 9e91f0ce6 rtw89: 8852c: update fw to v0.27.56.8 (lunar) + c9c19583f rtw89: 8852c: update fw to v0.27.56.9 (lunar) + fc5a25fa0 rtw89: 8852c: update fw to v0.27.56.10 (lunar) + b9c8e9f70 rtw89: 8852c: update fw to v0.27.56.13 (mantic) [Test Case] Basic bluetooth, wifi operations. This is verified with all related kernel/series combinations: * linux-hwe5.19/jammy * linux-hwe-6.2/jammy * linux-oem-6.0/jammy * linux-oem-6.1/jammy * linux-oem-6.5/jammy * ilnux/mantic [Where problems could occur] New device firmware blob, even blob format changes. Expect bugs, power consumption issues, etc. [Other Info] Bluetooth V2 firmware support was first landed to v6.4, and the binary rename in linux-next now. To preserve consistency, Unstable, Mantic and OEM-6.5 kernels are nominated for fix. As for linux-firmware, the only target is Jammy. == original bug description == Support Realtek RTL8852CE WiFi 6E/BT Combo * Bluetooth - kernel + 8b1d66b50437 Bluetooth: btrtl: Add support for RTL8852C (v5.19-rc1) + 9a24ce5e29b1 Bluetooth: btrtl: Firmware format v2 support (v6.4-rc1) + bd003fb338af Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C (linux-next) - firmware + 8a2d81176 rtl_bt: Add firmware and config files for RTL8852C (jammy) + d3c922805 rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33 (jammy) + cfbd66816 rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A (jammy) + c51488ffb rtl_bt: Update RTL8852C BT USB firmware to 0xD7B8_FABF (lunar) + 55e744853 rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225 (mantic, change binary format) + 7ed62638b Revert "rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225" (mantic) + 42d31f8f6 rtl_bt: Add firmware v2 file for RTL8852C (mantic) * WiFi - kernel + 59b4cc439f18 wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() (linux-next) - firmware + d2aac63b8 rtw89: 8852c: update fw to v0.27.56.1 (jammy) + 9e91f0ce6 rtw89: 8852c: update fw to v0.27.56.8 (lunar) + c9c19583f rtw89: 8852c: update fw to v0.27.56.9 (lunar) + fc5a25fa0 rtw89: 8852c: update fw to v0.27.56.10 (lunar) + b9c8e9f70 rtw89: 8852c: update fw to v0.27.56.13 (mantic) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025672/+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 2020627] Re: upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia and Morocco
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2020627
Title:
upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia
and Morocco
Status in HWE Next:
Fix Released
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Jammy:
Fix Released
Bug description:
[SRU Justification]
[Impact]
iwlwifi takes firmware updates to support WiFi 6E in Malaysia and
Morocco. The models in concern are AX210 (iwlwifi-ty-a0-gf-a0-*),
AX211 (iwlwifi-so-a0-gf-a0-*) and AX411 (iwlwifi-so-a0-gf4-a0-*).
[Fix]
pnvm along with the ucode firmware from upstream commit 5bc279fb161d
("iwlwifi: update core69 and core72 firmwares for So device") are
required. While the pnvm and ucode blobs may not be upgraded
simultaneously in one single commit, those involved in the upgrade
path are also pulled.
[Test Case]
Use `iw` to enumerate supported WiFi 6E band:
$ iw reg get
global
country : DFS-FCC
...
(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
[Where problems could occur]
Currently linux-5.15 has FW API 66, linux-hwe-5.19 or above has 72,
linux-6.3 has 74, and linux-unstable (v6.4) or above has 78, so this
will update iwlwifi firmware usage for kernels <= 6.2 in Jammy, e.g.
linux-oem-6.1, linux-5.15.
[Other Info]
Blobs with FW APIs >= 72 do no harm to jammy kernels, but will be
referenced in oem-6.5 if planned.
These commits have been included in linux-firmware/lunar, so only
Jammy is nominated for fix.
== original bug report ==
AX210:
-72 ucode:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0-72.ucode?id=4309412c0d872897dc913c7d2797bb5ce05893ad
pnvm:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81
AX211:
-72 ucode:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f
pnvm:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81
AX411:
-72 ucode:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f
pnvm:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0.pnvm?id=78a8782a9e51e502a6ed267d270c6925fb738805
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2020627/+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 2033452] Re: Enable D3cold at s2idle for Intel DG2 GPU
** Changed in: hwe-next Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033452 Title: Enable D3cold at s2idle for Intel DG2 GPU Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The system wakes up during s2idle with Intel DG2 GPU. It causes high power consumption during suspend. [Fix] Enable D3cold at s2idle. [Test] Tested on hardware, the system sleeps as long as expected, the power consumption is lower. [Where problems could occur] It may break i915 driver. It's a fix of regression in v6.1, no need for jammy and already in 6.5. SRU for lunar and oem-6.1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033452/+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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
** Changed in: thermald (Ubuntu) Status: In Progress => Confirmed ** Changed in: thermald (Ubuntu) Assignee: koba (kobako) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: Confirmed Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │ POWER_LIMITS.long_term_enabled = True 11 │
[Kernel-packages] [Bug 2011768] Re: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2011768 Title: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] NVME storage disappeared under Dell factory WINPE environment with RAID ON mode when this WINPE boot entry touched by efibootmgr [Fix] Reset the VMD msi remapping during shutdown. [Test Case] 1. Install Ubuntu 2. Then, system will reboot to WINPE to do some cleanup work. 3. in WINPE, the NVME storage could be listed. [Where problems could occur] Low, the issue may be observed on VMD MSI remapping. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011768/+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 2027957] Re: Fix AMDGPU: the screen freeze with W7500
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Bug description: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. [Misc] 1. jammy, amdgpu isn't loaded on this platform with 5.15-73-generic. 2. kinetic, amdgpu failed to probe the vga controller with 5.19-46-generic. 3. Passed cbd build against Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027957/+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 2015972] Re: Dell: Enable speaker mute hotkey LED indicator
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2015972 Title: Dell: Enable speaker mute hotkey LED indicator Status in HWE Next: Fix Released Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in alsa-ucm-conf source package in Kinetic: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in alsa-ucm-conf source package in Lunar: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2015972/+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 1993566] Re: dbus-daemon: Unknown group "power" in message bus configuration file
** Changed in: thermald (Ubuntu) Assignee: koba (kobako) => (unassigned) ** Changed in: thermald (Ubuntu) Status: In Progress => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1993566 Title: dbus-daemon: Unknown group "power" in message bus configuration file Status in thermald package in Ubuntu: New Bug description: Hi, I see the following error message in the logs: # journalctl | grep 'Unknown group "power"' Oct 19 18:41:35 jophur dbus-daemon[630]: dbus[630]: Unknown group "power" in message bus configuration file Oct 19 18:46:35 jophur dbus-daemon[630]: Unknown group "power" in message bus configuration file Oct 19 18:46:36 jophur dbus-daemon[630]: Unknown group "power" in message bus configuration file The problem comes from this file: # grep -r power /etc/dbus-1/ /etc/dbus-1/system.d/org.freedesktop.thermald.conf:
[Kernel-packages] [Bug 2012830] Re: Audio speed up on HDMI, with 4K resolution and refresh rate 60Hz
** Changed in: linux (Ubuntu)
Assignee: koba (kobako) => (unassigned)
--
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/2012830
Title:
Audio speed up on HDMI, with 4K resolution and refresh rate 60Hz
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 22.10
Release: 22.10
Wayland
5.19.9000-37-generic
(please refer to bug-report
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136. My
installed SW is the result of the fixed Problem by Koba, No HDMI audio
if e.g. RX560 will be used, since 5.19.0-35)
The audio speed up does mean, that the audio will be played with
"speed=2x" (or something like that)
5.19.9000-37-generic, 3840x2180, refresh rate 60Hz, audio speed up issue
5.19.9000-37-generic, 1920x1080, refresh rate 60Hz, no audio speed up issue
5.19.9000-37-generic, 3840x2180, refresh rate 30Hz, no audio speed up issue
But I did test it on different releases :
5.19.0-21-generic, 3840x2180, refresh rate 60Hz, audio speed up issue
5.19.0-21-generic, 1920x1080, refresh rate 60Hz, no audio speed up issue
5.19.0-21-generic, 3840x2180, refresh rate 30Hz, no audio speed up issue
5.19.0-32-generic, 3840x2180, refresh rate 60Hz, audio speed up issue
5.19.0-32-generic, 1920x1080, refresh rate 60Hz, no audio speed up issue
5.19.0-32-generic, 3840x2180, refresh rate 30Hz, no audio speed up issue
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin
HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] [1002:aae0]
Subsystem: ASUSTeK Computer Inc. Baffin HDMI/DP Audio [Radeon RX 550 640SP /
RX 560/560X] [1043:aae0]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
For more detailed information about my system (please refer to bug-
report : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009815
("Ubuntu-bug linux" didn't work with the following message : "The
problem can not be reported : This report is about a package that is
not installed)
What I expect :
Normal understandable audio if Resolution=3840x2180 and refresh rate=60Hz,
What happened instead :
Audio speed up, it sounds like chirps.
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard1516 F wireplumber
/dev/snd/controlC1: richard1516 F wireplumber
/dev/snd/seq:richard1513 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2023-03-04 (22 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
IwConfig:
lono wireless extensions.
enp3s0no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.9000-37-generic
root=UUID=df59b1c2-c5b9-483d-b033-7c6b2264dc75 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.9000-37.38~22.04.1-generic 5.19.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.19.9000-37-generic N/A
linux-backports-modules-5.19.9000-37-generic N/A
linux-firmware20220923.gitf09bebf3-0ubuntu1.4
RfKill:
Tags: wayland-session kinetic
Uname: Linux 5.19.9000-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/18/2013
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4802
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev x.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4802:bd09/18/2013:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MPRO:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012830/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 2042385] Re: Fix RPL-U CPU C-state always keep at C3 when system run PHM with idle screen on
** Summary changed: - Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on + Fix RPL-U CPU C-state always keep at C3 when system run PHM with idle screen on -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042385 Title: Fix RPL-U CPU C-state always keep at C3 when system run PHM with idle screen on Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814 [where the issue could happen] Medium, may have the regression but the risk is limited in some Dell platforms. we will ask Realtek's effort once the regression is observed. [Misc] For Unstable, built with mantic configuration ~~~ $ git push m_cbd remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_unstable_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-mantic-c281d2b48f02-DyYx remote: * 1/9 workers busy, 0 builds queued remote: 2023-11-20 16:19:03 kobako-mantic-c281d2b48f02-DyYx/amd64/BUILD-OK remote: 2023-11-20 16:21:38 kobako-mantic-c281d2b48f02-DyYx/arm64/BUILD-OK remote: 2023-11-20 16:18:54 kobako-mantic-c281d2b48f02-DyYx/armhf/BUILD-OK remote: 2023-11-20 16:22:08 kobako-mantic-c281d2b48f02-DyYx/ppc64el/BUILD-OK remote: 2023-11-20 16:14:16 kobako-mantic-c281d2b48f02-DyYx/s390x/BUILD-OK remote: To cbd.kernel:mantic.git * [new branch]ubuntu_unstable_next -> ubuntu_unstable_next ~~~ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042385/+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 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.1 (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.5 (Ubuntu Mantic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
New
Status in linux-oem-6.5 package in Ubuntu:
New
Status in linux source package in Jammy:
New
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
New
Status in linux-oem-6.1 source package in Mantic:
New
Status in linux-oem-6.5 source package in Mantic:
New
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
New
Status in linux-oem-6.5 source package in Noble:
New
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+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 2036577] Re: [Mediatek] mt8195-demo: Fix hardware watchdog reset at boot time around 10 sec.
Closing lunar as invalid. This has nothing to do with the 'lunar' package, and if the intention is to fix in the Lunar series, it should no longer be needed and we should target for newer releases. ** Changed in: lunar (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036577 Title: [Mediatek] mt8195-demo: Fix hardware watchdog reset at boot time around 10 sec. Status in linux package in Ubuntu: Incomplete Status in lunar package in Ubuntu: Invalid Bug description: [Impact] hardware reset during boot time. [Fix] Compare to generic kernel config for arm64 file: arch/arm64/configs/defconfig The CONFIG_MEDIATEK_WATCHDOG should be enabled "built-in" in generic kernel settings. CONFIG_MEDIATEK_WATCHDOG=y I've discovered that the module mtk_wdt.ko (CONFIG_MEDIATEK_WATCHDOG) must be set as built-in to prevent the system from encountering a hardware reset during the boot process. I've tried building it as a module and installing it into initrd, and I've also attempted to set softdep for it. However, I still can't find it being probed in the initcall debug dump. The system also reboots around 10 seconds into the boot time. After setting CONFIG_MEDIATEK_WATCHDOG=y, the hardware reset issue was resolved and the system was able to boot into the console. [Other info] effected kernel (5.19~latest) ubuntu kernel for lunar, Kinetic, and Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036577/+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 2024273] Re: Fix eDP only displays 3/4 area after switching to mirror mode with external HDMI 4K monitor
** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Chris Chiu (mschiu77) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2024273 Title: Fix eDP only displays 3/4 area after switching to mirror mode with external HDMI 4K monitor Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Panel on laptops connect to some 4K monitors via HDMI only display 3/4 area on eDP after switching to mirror mode. [Fix] Backport a fix from Intel on https://cgit.freedesktop.org/drm-tip/commit/?id=a2da67028cd05516343533c1609fcaf037237fed. [Test] 1. Power on the laptop 2. Connect a 4K monitor (4k Benq EL2870U, 4k HP z27Kg3, 2k ASUS PA27AC) to the laptop with HDMI cable. 3. Switch to mirror mode from default Joint Mode 4. Verify there's no obvious blank space on the leftmost/rightmost side of the laptop's panel. [Where problems could occur] Only observed after connecting with some particular 4K monitors. It's a generic fix to accept arbitrary refresh rate for more advanced panels. Should be low risk to old machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024273/+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 2028122] Re: Fix unreliable ethernet cable detection on I219 NIC
** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2028122 Title: Fix unreliable ethernet cable detection on I219 NIC Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: New Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Hotplugging RJ45 ethernet cable only works for one time because ACPI GPE wake doesn't working properly anymore. [Fix] Always use PME poll to read PCI PME to know if there's wake event. [Test] With the patch applied, ethernet cable can always be detected. [Where problems could occur] PME poll mechanism periodically reads the PMCTRL register, so the power consumption can be slightly higher. The increase will be very low, probably won't be noticeable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028122/+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 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
Change status to 'in progress' as the package has been uploaded, and Acelan has updated the bug description. ** Changed in: firmware-sof (Ubuntu Jammy) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: In Progress Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: SRU Jusitification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] The new firmware has been verified by our SWE team. [Where problems could occur] Those are new firmware, so it's not possible to introduce any regressions. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+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 2027804] Re: Fix GUI hang in login menu on Intel GPU
** Changed in: linux-oem-6.1 (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027804 Title: Fix GUI hang in login menu on Intel GPU Status in HWE Next: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Bug description: [Impact] Intel GPU hang on 6.1 stable kernel in login menu after boot. [Fix] Add missing DC_OFF power domain for GPU. [Test] Tested on Intel RPL iGPU and DG2 GPU. [Where problems could occur] Low risk, the fix is in 6.2-rc1, the issue is only reproduced on oem-6.1 kernel, not reproduced on jammy kernel. So SRU for oem-6.1 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027804/+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 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
@Andreas firmware-sof in Mantic is 2.2.6, which already has everything in Acelan's merge proposal. @Steve Acelan's merge proposal indeed pulls in 16 new binaries from upstream's firmware-sof 2.2.5 and 2.2.6, more than this bug originally need. It's because when we roll out a new HWE kernel in the future, some users will eventually need the other firmwares. Do you advise us to: 1. update the bug description, or 2. submit a new MR with only the firmwares we need for this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Incomplete Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Mantic: New Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+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
