[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
It looks like mutter is *asking* to be killed if any system calls take too long: setrlimit (RLIMIT_RTTIME... and that only seems to happen on some Ryzen systems. Still, I'm not so sure the default limit of 200ms (inherited from rtkit) is sensible if the machine would otherwise recover. It's not like the problem is happening on every frame. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in X.Org X server: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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.
** Attachment added: "ubuntu_genio_1200_evk_6.2_initcall.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036577/+attachment/5702213/+files/ubuntu_genio_1200_evk_6.2_initcall.log -- 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: New 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 2000228] Re: Add initial support for Mediatek Genio boards
Verified the package on Mantic. It works as expected. I can hear sound from headphone, Speark, and HDMI monitor. $ apt-cache policy alsa-ucm-conf | grep Installed Installed: 1.2.9-1ubuntu2 Here is the test result: mt8390-evk (G700): Pass mt8395-evk (G1200): Pass ** Description changed: [Impact] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk) mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 - mt8390-evk: (Still under review) + mt8390-evk (G700): (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 - mt8395-evk: (Still under review) + mt8395-evk (G1200): (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/322 [Where problems could occur] Audio function doesn't work on Mediatek Genio boards. mantic: mt8390-evk, and mt8395-evk lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk [Test Case] Verify audio function on Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. HDMI Playback Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] Add initial support for Mediatek Genio boards. There should be no risk. mantic: mt8390-evk, and mt8395-evk lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk ** Summary changed: - Add initial support for Mediatek Genio boards + [SRU] Add initial support for Mediatek Genio boards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2000228 Title: [SRU] Add initial support for Mediatek Genio boards Status in alsa-ucm-conf package in Ubuntu: Fix Released Bug description: [Impact] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk) mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 mt8390-evk (G700): (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 mt8395-evk (G1200): (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/322 [Where problems could occur] Audio function doesn't work on Mediatek Genio boards. mantic: mt8390-evk, and mt8395-evk lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk [Test Case] Verify audio function on Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. HDMI Playback Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] Add initial support for Mediatek Genio boards. There should be no risk. mantic: mt8390-evk, and mt8395-evk lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028205] Re: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: underprocessen dpkg-deb --fsys-tarfile gav felkod 2 vid avslut
[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2028205 Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: underprocessen dpkg-deb --fsys-tarfile gav felkod 2 vid avslut Status in linux-firmware package in Ubuntu: Expired Bug description: Fresh install, first login. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hackan 1964 F wireplumber /dev/snd/seq:hackan 1952 F pipewire CRDA: N/A CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Jul 19 23:10:46 2023 Dependencies: firmware-sof-signed 2.2.4-1 ErrorMessage: underprocessen dpkg-deb --fsys-tarfile gav felkod 2 vid avslut InstallationDate: Installed on 2023-07-19 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) IwConfig: lono wireless extensions. enp2s0f0 no wireless extensions. MachineType: Apple Inc. Macmini5,1 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-25-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux-firmware Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: underprocessen dpkg-deb --fsys-tarfile gav felkod 2 vid avslut UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 135.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvr135.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:skuSystemSKU#: dmi.product.family: Macmini dmi.product.name: Macmini5,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2028205/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
linux-firmware SRU: * https://lists.ubuntu.com/archives/kernel-team/2023-September/143027.html (mantic, V2, rebase only) -- 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/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: New Status in ivsc-driver package in Ubuntu: New Status in linux-firmware package in Ubuntu: In Progress Status in ipu6-drivers source package in Jammy: New Status in ivsc-driver source package in Jammy: New Status in linux-firmware source package in Jammy: In Progress Status in ipu6-drivers source package in Mantic: New Status in ivsc-driver source package in Mantic: New Status in linux-firmware source package in Mantic: In Progress Bug description: [SRU Justification] [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Firmware blobs from upstream ipu6-camera-bins repository. [Test Case] With firmware loaded correctly, there should be firmware version printed: intel-ipu6 intel-ipu: FW version: 20220510 For camera functions, we'll need also updates in the ipu6-drivers, ivsc-drivers dkms as well. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic, so only Jammy/Mantic are nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2031412/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032176] Re: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1
Hi, is there a timeline on when this patch will reach the general availability kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032176 Title: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: Impact: We had reports of VM setups which would show intermediate crashes and after that locking up completely. This could be reproduced with large memory setups. The problem seems to be that fixes to performance regressions caused more problems in 5.15 kernels and the full fixes are too intrusive to be backported. Fix: The following patch was recently sent to the upstream stable mailing list and looks to be making its way into linux-5.15.y. This changes the default value of kvm.tdp_mmu to off (if anyone is willing to take the risks, this can be changed back in config). Regression potential: VM hosts with many large memory tennants might see a performance impact which the TDP MMU approach tried to solve. If those did not see other problems they might turn this on again. Testcase: Large openstack instance (64GB memory, AMD CPU (using SVM)) with a large second level guest (32GB memory). Repeatedly starting and stopping the 2nd level guest. --- original description --- The crash occurred on a juju machine, and the juju agent was lost. The juju machine is on an openstack instance provision by juju. The openstack console log indicts the it is related to spin_lock and KVM MMU: [418200.348830] ? _raw_spin_lock+0x22/0x30 [418200.349588] _raw_write_lock+0x20/0x30 [418200.350196] kvm_tdp_mmu_map+0x2b1/0x490 [kvm] [418200.351014] kvm_mmu_notifier_invalidate_range_start+0x1ad/0x300 [kvm] [418200.351796] direct_page_fault+0x206/0x310 [kvm] [418200.352667] __mmu_notifier_invalidate_range_start+0x91/0x1b0 [418200.353624] kvm_tdp_page_fault+0x72/0x90 [kvm] [418200.354496] try_to_migrate_one+0x691/0x730 [418200.355436] kvm_mmu_page_fault+0x73/0x1c0 [kvm] openstack console log: https://pastebin.canonical.com/p/spmH8r3crQ/ syslog: https://pastebin.canonical.com/p/wFPsFD8G9n/ The syslog was rotated after the crash occurred, so the syslog at the time of the initial crash was lost. Other juju machine with 5.15.0.79.76 kernel seems to have the same issues. We previously have a similar issue with 5.15.0-73. The juju machine crashed with raw_spin_lock and kvm mmu in the logs as well: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Aug 21 08:59:46 2023 Ec2AMI: ami-0c61 Ec2AMIManifest: FIXME Ec2AvailabilityZone: availability-zone-1 Ec2InstanceType: builder-cpu4-ram72-disk20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 23 03:23 seq crw-rw 1 root audio 116, 33 Aug 23 03:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) DistroRelease: Ubuntu 22.04 Ec2AMI: ami-0fbb Ec2AMIManifest: FIXME Ec2AvailabilityZone: availability-zone-2 Ec2InstanceType: builder-cpu2-ram44-disk20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: OpenStack Foundation OpenStack Nova NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no
[Kernel-packages] [Bug 2000228] Re: Add initial support for Mediatek Genio boards
** Description changed: [Impact] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk) mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 mt8390-evk: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 mt8395-evk: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/322 [Where problems could occur] Audio function doesn't work on Mediatek Genio boards. mantic: mt8390-evk, and mt8395-evk lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk [Test Case] Verify audio function on Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. HDMI Playback Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] - Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). There should be no risk. + Add initial support for Mediatek Genio boards. There should be no risk. + mantic: mt8390-evk, and mt8395-evk + lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2000228 Title: Add initial support for Mediatek Genio boards Status in alsa-ucm-conf package in Ubuntu: Fix Released Bug description: [Impact] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk) mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 mt8390-evk: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 mt8395-evk: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/322 [Where problems could occur] Audio function doesn't work on Mediatek Genio boards. mantic: mt8390-evk, and mt8395-evk lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk [Test Case] Verify audio function on Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. HDMI Playback Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] Add initial support for Mediatek Genio boards. There should be no risk. mantic: mt8390-evk, and mt8395-evk lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033025] Re: Fix numerous AER related issues
** Tags added: originate-from-2034495 -- 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/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: 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 Committed 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.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870554] Re: ip-netns(8) unmounts /sys filesystem hierarchy within namespace
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: iproute2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1870554 Title: ip-netns(8) unmounts /sys filesystem hierarchy within namespace Status in iproute2 package in Ubuntu: Confirmed Bug description: Filesystems ordinarily mounted beneath /sys, particularly /sys/fs/cgroup, are not mounted within network namespaces created by ip-netns(8), as lib/namespace.c:netns_switch() explicitly remounts /sys. The patch enclosed removes the offending calls to umount2(2) and mount(2), leaving the /sys hierarchy intact within network namespaces. $ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 $ apt-cache policy iproute2 iproute2: Installed: 4.15.0-2ubuntu1 Candidate: 4.15.0-2ubuntu1 Version table: *** 4.15.0-2ubuntu1 500 500 http://fr2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Nota bene: this bug was reported in [1] (unresolved) and, on Arch Linux, [2]. References: [1] https://answers.launchpad.net/ubuntu/+source/iproute2/+question/659146 [2] https://bugs.archlinux.org/task/33328 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1870554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete
do you know what __percpu_counter_sum does? I am wondering why it has been sampled a lot of times. -- 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/2021571 Title: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete Status in linux-meta package in Ubuntu: Confirmed Bug description: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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.
According to the log: 1. By searching "wdt|watchdog", 'mtk-wdt' cannot be found even we've installed 'mtk_wdt.ko' into initrd.img. 2. The system will always hardware reset around 9~11 seconds. 3. BL2: TFA will show the "WDT: Last reset was hardware watchdog". 989: WDT: Started watchdog@10007000 with servicing (60s timeout) 2434: [0.191906] calling gtdt_sbsa_gwdt_init+0x0/0x128 @ 1 2435: [0.191915] initcall gtdt_sbsa_gwdt_init+0x0/0x128 returned 0 after 0 usecs 4657: NOTICE: WDT: Status = 0x8000 4658: NOTICE: WDT: Last reset was hardware watchdog 4784: [PMIC] [pmic_check_rst] AP Watchdog 4787: [PMIC] [pmic_wdt_set] TOP_RST_MISC=0x225 -- 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: New 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 2036675] Re: 5.15.0-85 live migration regression
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Chengen Du (chengendu) -- 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/2036675 Title: 5.15.0-85 live migration regression Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: In Progress Bug description: Fixes added for LP 2032164 [0] to resolve an issue in live migration have unfortunately introduced a regression, causing a previously working live migration pattern to fail when tested with the 5.15.0-85 kernel from -proposed. Specifically, live migration from a PKRU-enabled host running a kernel older than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail. The destination can be either with or without PKRU; both cases fail, although in different ways (one hangs, the other fails due to a PCID flag issue). The commits in question are commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0 Author: Dr. David Alan Gilbert Date: Mon Aug 21 14:47:28 2023 +0800 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES commit 27a189b881278c8ad9c16b0ee05668d724352733 Author: Leonardo Bras Date: Mon Aug 21 14:47:27 2023 +0800 x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 [0] https://bugs.launchpad.net/bugs/2032164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036682] [NEW] High battery drain during suspend on Kernel 6.2
Public bug reported: I have high battery drain during sleep with my Dell XPS 9320. It drains fast when I boot into kernel 6.2 (linux-image-6.2.0-32-generic) but not when I boot into kernel 6.0 (linux-image-6.0.0-1020-oem). I took these measurements: - Kernel 6.0: suspended for 11 hours from a full charge - 6% battery drain - Kernel 6.2: suspended for 6.5 hours from a full charge - 27% battery drain I'm using the latest BIOS version for my laptop (2.5.0). I'm on Ubuntu 22.04. I'm attaching two syslog excerpts of suspend/resume cycles on both kernels (they are from the suspend/resume when I took the measurements). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1020.20-oem 6.0.9 Uname: Linux 6.0.0-1020-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 05:10:19 2023 InstallationDate: Installed on 2022-11-29 (295 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "suspend_logs.zip" https://bugs.launchpad.net/bugs/2036682/+attachment/5702195/+files/suspend_logs.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036682 Title: High battery drain during suspend on Kernel 6.2 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: I have high battery drain during sleep with my Dell XPS 9320. It drains fast when I boot into kernel 6.2 (linux-image-6.2.0-32-generic) but not when I boot into kernel 6.0 (linux-image-6.0.0-1020-oem). I took these measurements: - Kernel 6.0: suspended for 11 hours from a full charge - 6% battery drain - Kernel 6.2: suspended for 6.5 hours from a full charge - 27% battery drain I'm using the latest BIOS version for my laptop (2.5.0). I'm on Ubuntu 22.04. I'm attaching two syslog excerpts of suspend/resume cycles on both kernels (they are from the suspend/resume when I took the measurements). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1020.20-oem 6.0.9 Uname: Linux 6.0.0-1020-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 05:10:19 2023 InstallationDate: Installed on 2022-11-29 (295 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 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.2/+bug/2036682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000228] Re: Add initial support for Mediatek Genio boards
** Description changed: [Impact] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk) mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 mt8390-evk: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 mt8395-evk: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/322 [Where problems could occur] - Audio function doesn't work on Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). + Audio function doesn't work on Mediatek Genio boards. + mantic: mt8390-evk, and mt8395-evk + lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk [Test Case] Verify audio function on Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. HDMI Playback Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). There should be no risk. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2000228 Title: Add initial support for Mediatek Genio boards Status in alsa-ucm-conf package in Ubuntu: Fix Released Bug description: [Impact] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk) mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 mt8390-evk: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 mt8395-evk: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/322 [Where problems could occur] Audio function doesn't work on Mediatek Genio boards. mantic: mt8390-evk, and mt8395-evk lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk [Test Case] Verify audio function on Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. HDMI Playback Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). There should be no risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
Yeah I think the major kernel upgrade (or something around the same time) caused one boot to be very slow. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in X.Org X server: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030815] Re: apply nvidia igx patches for Aug 1-7
** Tags removed: verification-needed-jammy-linux-nvidia-tegra-igx ** Tags added: verification-done-jammy-linux-nvidia-tegra-igx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2030815 Title: apply nvidia igx patches for Aug 1-7 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Set of 7 patches for igx kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2030815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033315] Re: apply nvidia igx patches for Aug 22-28
** Tags removed: verification-needed-jammy-linux-nvidia-tegra-igx ** Tags added: verification-done-jammy-linux-nvidia-tegra-igx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2033315 Title: apply nvidia igx patches for Aug 22-28 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: 2 patches for Aug 22-28, 2023 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2033315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036678] [NEW] Ethernet driver not detected
Public bug reported: Hi Sorry I reported this with kernel 6.2.0-32 because my Internet not working with 6.2.0-33. So my network lshw -c network says my *-network is UNCLAIMED. Network setting on ubuntu not detecting my Ethernet at all. So I rollback to 6.2.0-32 then it working fine again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 08:23:41 2023 InstallationDate: Installed on 2023-09-17 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: - Hi Sorry I reported this with kernel 6.2 because my Internet not working - with 6.3. + Hi Sorry I reported this with kernel 6.2.0-32 because my Internet not + working with 6.2.0-33. So my network lshw -c network says my *-network is UNCLAIMED. Network setting on ubuntu not detecting my Ethernet at all. - So I rollback to 6.2 then it working fine again. + So I rollback to 6.2.0-32 then it working fine again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 08:23:41 2023 InstallationDate: Installed on 2023-09-17 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036678 Title: Ethernet driver not detected Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Hi Sorry I reported this with kernel 6.2.0-32 because my Internet not working with 6.2.0-33. So my network lshw -c network says my *-network is UNCLAIMED. Network setting on ubuntu not detecting my Ethernet at all. So I rollback to 6.2.0-32 then it working fine again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 08:23:41 2023 InstallationDate: Installed on 2023-09-17 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: linux-signed-hwe-6.2 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.2/+bug/2036678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036675] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2036675 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036675 Title: 5.15.0-85 live migration regression Status in linux package in Ubuntu: Incomplete Bug description: Fixes added for LP 2032164 [0] to resolve an issue in live migration have unfortunately introduced a regression, causing a previously working live migration pattern to fail when tested with the 5.15.0-85 kernel from -proposed. Specifically, live migration from a PKRU-enabled host running a kernel older than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail. The destination can be either with or without PKRU; both cases fail, although in different ways (one hangs, the other fails due to a PCID flag issue). The commits in question are commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0 Author: Dr. David Alan Gilbert Date: Mon Aug 21 14:47:28 2023 +0800 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES commit 27a189b881278c8ad9c16b0ee05668d724352733 Author: Leonardo Bras Date: Mon Aug 21 14:47:27 2023 +0800 x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 [0] https://bugs.launchpad.net/bugs/2032164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete
I have no idea what racadm is .. -- 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/2021571 Title: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete Status in linux-meta package in Ubuntu: Confirmed Bug description: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036675] [NEW] 5.15.0-85 live migration regression
Public bug reported: Fixes added for LP 2032164 [0] to resolve an issue in live migration have unfortunately introduced a regression, causing a previously working live migration pattern to fail when tested with the 5.15.0-85 kernel from -proposed. Specifically, live migration from a PKRU-enabled host running a kernel older than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail. The destination can be either with or without PKRU; both cases fail, although in different ways (one hangs, the other fails due to a PCID flag issue). The commits in question are commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0 Author: Dr. David Alan Gilbert Date: Mon Aug 21 14:47:28 2023 +0800 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES commit 27a189b881278c8ad9c16b0ee05668d724352733 Author: Leonardo Bras Date: Mon Aug 21 14:47:27 2023 +0800 x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 [0] https://bugs.launchpad.net/bugs/2032164 ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/2036675 Title: 5.15.0-85 live migration regression Status in linux package in Ubuntu: New Bug description: Fixes added for LP 2032164 [0] to resolve an issue in live migration have unfortunately introduced a regression, causing a previously working live migration pattern to fail when tested with the 5.15.0-85 kernel from -proposed. Specifically, live migration from a PKRU-enabled host running a kernel older than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail. The destination can be either with or without PKRU; both cases fail, although in different ways (one hangs, the other fails due to a PCID flag issue). The commits in question are commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0 Author: Dr. David Alan Gilbert Date: Mon Aug 21 14:47:28 2023 +0800 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES commit 27a189b881278c8ad9c16b0ee05668d724352733 Author: Leonardo Bras Date: Mon Aug 21 14:47:27 2023 +0800 x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 [0] https://bugs.launchpad.net/bugs/2032164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036672] [NEW] apply nvidia igx patches for Aug 29 - Sep 19
Public bug reported: Patches to apply on top of the new 1004.4 tag. ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2036672 Title: apply nvidia igx patches for Aug 29 - Sep 19 Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Patches to apply on top of the new 1004.4 tag. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2036672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929444] Re: SD card initialization on insertion fails
I've just tested the laptop where this problem was originally seen and
it's still OK there.
That is now running 23.04 (Lunar) with kernel 6.2.0-33-generic.
So may be similar, but is not the same.
--
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/1929444
Title:
SD card initialization on insertion fails
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in linux source package in Impish:
Fix Released
Bug description:
[SRU Justification]
[Impact]
The memory card can be detected and mount correctly when the system starts
with the card inserted. But it will fail to be detected at the subsequent
re-plug. It only happens on particular Realtek older PCI interfaced card
readers. The RTL8411B (10ec:5287) is reported problematic for this issue.
[Fix]
Found the commit 121e9c6b5c4c ("misc: rtsx: modify and fix init_hw function")
in 5.11.0-rc1 introduces this regression. The fix from upstream use the old
ASPM control for particular realtek card reader models: 8411 5209 5227 5229
5249 5250.
[Test]
Verified on the Realtek PCI interfaced card reader RTL8411B and verify
whether the memory card can be detected for each re-plug.
[Where problem could occur]
The regression can be considered as low since the fix has specified separate
ASPM control for particular Realtek Card Readers.
== Original Bug Description ==
If I boot my laptop with an SD card (actually SDXC) in the MMC slot
the system sees it and I can mount and use it.
If I then unmount it, remove it then re-insert it I get this in the
system ,og:
[ 194.673108] mmc0: card e624 removed
[ 205.462065] mmc0: cannot verify signal voltage switch
[ 205.567479] mmc0: error -84 whilst initialising SD card
and the card cannot then be used.
It was OK in groovy. It's failing in hirsute.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-generic 5.11.0.17.18
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gml44104153 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Mon May 24 17:36:49 2021
HibernationDevice: RESUME=UUID=03dec042-8ba2-48a8-8d19-373ca2e0829c
InstallationDate: Installed on 2020-08-13 (284 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
(20200731)
MachineType: PC Specialist LTD N150CU
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic
root=UUID=b21720c3-60bf-4298-9d73-743672f89216 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.11.0-17-generic N/A
linux-backports-modules-5.11.0-17-generic N/A
linux-firmware 1.197
SourcePackage: linux
UpgradeStatus: Upgraded to hirsute on 2021-05-13 (11 days ago)
dmi.bios.date: 11/15/2019
dmi.bios.release: 7.7
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.07TPCS2
dmi.board.asset.tag: Tag 12345
dmi.board.name: N151CU
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: N150CU
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: PC Specialist LTD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration.
list of 5.15 kernels available in the repo root@compute81:~# apt search linux-image-5.15.*-generic linux-image-5.15.0-25-generic/now 5.15.0-25.25 amd64 [installed,local] <--- everything works linux-image-5.15.0-33-generic/focal-updates,focal-security,now 5.15.0-33.34~20.04.1 amd64 [installed] <-- VM hangs linux-image-5.15.0-41-generic/focal-updates,focal-security,now 5.15.0-41.44~20.04.1 amd64 [installed] <-- VM hangs here's a diff of the kernel config files root@compute81:~# diff -Naur /boot/config-5.15.0-25-generic /boot/config-5.15.0-33-generic --- /boot/config-5.15.0-25-generic 2022-03-30 15:28:11.0 + +++ /boot/config-5.15.0-33-generic 2022-05-19 14:04:01.0 + @@ -1,23 +1,22 @@ # # Automatically generated file; DO NOT EDIT. -# Linux/x86 5.15.0-25-generic Kernel Configuration +# Linux/x86 5.15.0-33-generic Kernel Configuration # -CONFIG_CC_VERSION_TEXT="gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0" +CONFIG_CC_VERSION_TEXT="gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0" CONFIG_CC_IS_GCC=y -CONFIG_GCC_VERSION=110200 +CONFIG_GCC_VERSION=90400 CONFIG_CLANG_VERSION=0 CONFIG_AS_IS_GNU=y -CONFIG_AS_VERSION=23800 +CONFIG_AS_VERSION=23400 CONFIG_LD_IS_BFD=y -CONFIG_LD_VERSION=23800 +CONFIG_LD_VERSION=23400 CONFIG_LLD_VERSION=0 CONFIG_CC_CAN_LINK=y CONFIG_CC_CAN_LINK_STATIC=y CONFIG_CC_HAS_ASM_GOTO=y -CONFIG_CC_HAS_ASM_GOTO_OUTPUT=y CONFIG_CC_HAS_ASM_INLINE=y CONFIG_CC_HAS_NO_PROFILE_FN_ATTR=y -CONFIG_PAHOLE_VERSION=122 +CONFIG_PAHOLE_VERSION=121 CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_TABLE_SORT=y CONFIG_THREAD_INFO_IN_TASK=y @@ -47,7 +46,7 @@ CONFIG_KERNEL_ZSTD=y CONFIG_DEFAULT_INIT="" CONFIG_DEFAULT_HOSTNAME="(none)" -CONFIG_VERSION_SIGNATURE="Ubuntu 5.15.0-25.25-generic 5.15.30" +CONFIG_VERSION_SIGNATURE="Ubuntu 5.15.0-33.34~20.04.1-generic 5.15.30" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y @@ -508,6 +507,7 @@ # CONFIG_LEGACY_VSYSCALL_NONE is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_MODIFY_LDT_SYSCALL=y +# CONFIG_STRICT_SIGALTSTACK_SIZE is not set CONFIG_HAVE_LIVEPATCH=y CONFIG_LIVEPATCH=y # end of Processor type and features @@ -841,6 +841,7 @@ CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_ARCH_HAS_ELFCORE_COMPAT=y CONFIG_ARCH_HAS_PARANOID_L1D_FLUSH=y +CONFIG_DYNAMIC_SIGFRAME=y # # GCOV-based kernel profiling @@ -10282,7 +10283,25 @@ CONFIG_EROFS_FS_SECURITY=y CONFIG_EROFS_FS_ZIP=y CONFIG_VBOXSF_FS=m -# CONFIG_AUFS_FS is not set +CONFIG_AUFS_FS=m +CONFIG_AUFS_BRANCH_MAX_127=y +# CONFIG_AUFS_BRANCH_MAX_511 is not set +# CONFIG_AUFS_BRANCH_MAX_1023 is not set +# CONFIG_AUFS_BRANCH_MAX_32767 is not set +CONFIG_AUFS_SBILIST=y +# CONFIG_AUFS_HNOTIFY is not set +CONFIG_AUFS_EXPORT=y +CONFIG_AUFS_INO_T_64=y +CONFIG_AUFS_XATTR=y +# CONFIG_AUFS_FHSM is not set +# CONFIG_AUFS_RDU is not set +CONFIG_AUFS_DIRREN=y +# CONFIG_AUFS_SHWH is not set +# CONFIG_AUFS_BR_RAMFS is not set +# CONFIG_AUFS_BR_FUSE is not set +CONFIG_AUFS_BR_HFSPLUS=y +CONFIG_AUFS_BDEV_LOOP=y +# CONFIG_AUFS_DEBUG is not set CONFIG_NETWORK_FILESYSTEMS=y CONFIG_NFS_FS=m CONFIG_NFS_V2=m @@ -10428,7 +10447,7 @@ CONFIG_ENCRYPTED_KEYS=y CONFIG_KEY_DH_OPERATIONS=y CONFIG_KEY_NOTIFICATIONS=y -CONFIG_SECURITY_DMESG_RESTRICT=y +# CONFIG_SECURITY_DMESG_RESTRICT is not set CONFIG_SECURITY_PERF_EVENTS_RESTRICT=y CONFIG_SECURITY=y CONFIG_SECURITYFS=y @@ -10533,8 +10552,6 @@ CONFIG_INIT_STACK_NONE=y CONFIG_INIT_ON_ALLOC_DEFAULT_ON=y # CONFIG_INIT_ON_FREE_DEFAULT_ON is not set -CONFIG_CC_HAS_ZERO_CALL_USED_REGS=y -# CONFIG_ZERO_CALL_USED_REGS is not set # end of Memory initialization # end of Kernel hardening options # end of Security options @@ -10974,9 +10991,9 @@ # CONFIG_DEBUG_INFO_REDUCED is not set # CONFIG_DEBUG_INFO_COMPRESSED is not set # CONFIG_DEBUG_INFO_SPLIT is not set -# CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT is not set +CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT=y # CONFIG_DEBUG_INFO_DWARF4 is not set -CONFIG_DEBUG_INFO_DWARF5=y +# CONFIG_DEBUG_INFO_DWARF5 is not set CONFIG_DEBUG_INFO_BTF=y CONFIG_PAHOLE_HAS_SPLIT_BTF=y CONFIG_DEBUG_INFO_BTF_MODULES=y @@ -11030,8 +11047,6 @@ CONFIG_UBSAN_SANITIZE_ALL=y # CONFIG_TEST_UBSAN is not set CONFIG_HAVE_ARCH_KCSAN=y -CONFIG_HAVE_KCSAN_COMPILER=y -# CONFIG_KCSAN is not set # end of Generic Kernel Debugging Instruments CONFIG_DEBUG_KERNEL=y root@compute81:~# -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023
[Kernel-packages] [Bug 2029332] Re: Reboot command powers off the system
sudo apt-cache search linux-generic-hwe linux-generic-hwe-20.04 - Complete Generic Linux kernel and headers (dummy transitional package) linux-generic-hwe-20.04-edge - Complete Generic Linux kernel and headers (dummy transitional package) linux-generic-hwe-22.04 - Complete Generic Linux kernel and headers linux-generic-hwe-22.04-edge - Complete Generic Linux kernel and headers Try installing the latest 6.2 sudo apt install linux-generic-hwe-22.04-edge uname -a Linux 6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2029332 Title: Reboot command powers off the system Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.2 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: [Impact] Issue: When a reboot (or init 6) command is issued the server shuts down instead. Expected behaviour: To reboot and NOT shutdown Impacted HW: HPE DL 380 OR Synergy 480 Gen 10 Plus Server 2P core count greater than 16 (like 24,28 or 32) Impacted OS: Ubuntu 22.04.2 kernel higher than 15.17.15 When the CPU count is 1, issue is not observed. When core count is less than 24 (like 16) issue not observed. [Fix] Problem introduced in v5.18 with commit: 08f253ec3767 x86/cpu: Clear SME feature flag when not in use Fixes for the above:0 9b040453d444 x86/smp: Dont access non-existing CPUID leaf 1f5e7eb7868e x86/smp: Make stop_other_cpus() more robust [Test Case] $ sudo reboot Server should reboot and not power off. [Where Problems Could Occur] The fixes modify x86 stop-CPU code so reboot/poweroff of x86 machines could be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929444] Re: SD card initialization on insertion fails
I've got a similar problem with Ubuntu 22.04.3 LTS and kernel
6.2.0-31-generic -> https://bugs.launchpad.net/ubuntu/+source/linux-
signed-hwe-6.2/+bug/2033553
--
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/1929444
Title:
SD card initialization on insertion fails
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in linux source package in Impish:
Fix Released
Bug description:
[SRU Justification]
[Impact]
The memory card can be detected and mount correctly when the system starts
with the card inserted. But it will fail to be detected at the subsequent
re-plug. It only happens on particular Realtek older PCI interfaced card
readers. The RTL8411B (10ec:5287) is reported problematic for this issue.
[Fix]
Found the commit 121e9c6b5c4c ("misc: rtsx: modify and fix init_hw function")
in 5.11.0-rc1 introduces this regression. The fix from upstream use the old
ASPM control for particular realtek card reader models: 8411 5209 5227 5229
5249 5250.
[Test]
Verified on the Realtek PCI interfaced card reader RTL8411B and verify
whether the memory card can be detected for each re-plug.
[Where problem could occur]
The regression can be considered as low since the fix has specified separate
ASPM control for particular Realtek Card Readers.
== Original Bug Description ==
If I boot my laptop with an SD card (actually SDXC) in the MMC slot
the system sees it and I can mount and use it.
If I then unmount it, remove it then re-insert it I get this in the
system ,og:
[ 194.673108] mmc0: card e624 removed
[ 205.462065] mmc0: cannot verify signal voltage switch
[ 205.567479] mmc0: error -84 whilst initialising SD card
and the card cannot then be used.
It was OK in groovy. It's failing in hirsute.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-generic 5.11.0.17.18
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gml44104153 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Mon May 24 17:36:49 2021
HibernationDevice: RESUME=UUID=03dec042-8ba2-48a8-8d19-373ca2e0829c
InstallationDate: Installed on 2020-08-13 (284 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
(20200731)
MachineType: PC Specialist LTD N150CU
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic
root=UUID=b21720c3-60bf-4298-9d73-743672f89216 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.11.0-17-generic N/A
linux-backports-modules-5.11.0-17-generic N/A
linux-firmware 1.197
SourcePackage: linux
UpgradeStatus: Upgraded to hirsute on 2021-05-13 (11 days ago)
dmi.bios.date: 11/15/2019
dmi.bios.release: 7.7
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.07TPCS2
dmi.board.asset.tag: Tag 12345
dmi.board.name: N151CU
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: N150CU
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: PC Specialist LTD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028830] Re: [mpt3sas, UBSAN] ]linux 6.5-rc won't boot
@Koba, As just reported on kernel-t...@lists.ubuntu.com, the "for waiting the udev"[sic!] matter was completely unrelated. With the patch set, the UBSAN messages are completely gone, and with the workaround reported to the list, the system boots normally. Having learned a bit more about UBSAN, it would seem that the system would still have booted despite the messages, so I shall try to see if I can alter the heading of this report. ** Summary changed: - [mpt3sas, UBSAN] ]linux 6.5-rc won't boot + [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot ** Description changed: Ubuntu release: sune@jekaterina:~/src/deb$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 - sune@jekaterina:~/src/deb$ + sune@jekaterina:~/src/deb$ Package: linux-image- unsigned-6.5.0-060500rc1-generic_6.5.0-060500rc1.202307232333_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline (rc2 and rc3 also affected) Expectation: System boots normally Actual results: See below On the request of Koba Ko on the kernel-t...@lists.ubuntu.com mailing list, I hereby submit the following: Do note that two "types" are mentioned, and that I am willing the assist in testing, as, obviously, I have a system with a controller covered by the mpt3sas driver. This is output from attempted boot of 6.5-rc3 from kernel-ppa, but it is similar to rcs 1 and 2: UBSAN: array-index-out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/npt3sas/mpt3sas_scsih.c:4667:12 index 1 is out of range for type ’MPI12_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih-c:4023:12 index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6810:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6598:38 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6602:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux-drivers/scsi/mpt3sas/mpt3sas_scsih.c:6619:7 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c::21 index 1 is out of range for type ’MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7649:32 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7651:23 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' - Timed out for waiting the udey queue being empty. + [EDIT] the next error, repeating for ~1½ hours before finishing boot, + was unrelated to mpt2sas and UBSAN. + + That error was "Timed out for waiting the udey queue being empty." + + Bug subject altered to reflect this. -- 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/2028830 Title: [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot Status in linux package in Ubuntu: In Progress Bug description: Ubuntu release: sune@jekaterina:~/src/deb$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 sune@jekaterina:~/src/deb$ Package: linux-image- unsigned-6.5.0-060500rc1-generic_6.5.0-060500rc1.202307232333_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline (rc2 and rc3 also affected) Expectation: System boots normally Actual results: See below On the request of Koba Ko on the kernel-t...@lists.ubuntu.com mailing list, I hereby submit the following: Do note that two "types" are mentioned, and that I am willing the assist in testing, as, obviously, I have a system with a controller covered by the mpt3sas driver. This is output from attempted boot of 6.5-rc3 from kernel-ppa, but it is similar to rcs 1 and 2: UBSAN: array-index-out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/npt3sas/mpt3sas_scsih.c:4667:12 index 1 is out of range for type ’MPI12_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih-c:4023:12 index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY
[Kernel-packages] [Bug 2036646] [NEW] missing iwlwifi firmware file
Public bug reported: In dmesg I am getting Direct firmware load for iwlwifi-QuZ-a0-hr-b0-56.ucode failed with error -2 [2.468104] iwlwifi :00:14.3: api flags index 2 larger than supported by driver [2.468118] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 65.3.35.22 [2.468121] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM [2.468122] iwlwifi :00:14.3: Found debug configuration: 0 [2.468377] iwlwifi :00:14.3: loaded firmware version 55.d9698065.0 QuZ-a0-hr-b0-55.ucode op_mode iwlmvm during boot. The file does not exist in /lib/firmware and I can't find it on github. If it's not important please ignore. thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 19 16:33:13 2023 InstallationDate: Installed on 2020-08-17 (1128 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/2036646 Title: missing iwlwifi firmware file Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: In dmesg I am getting Direct firmware load for iwlwifi-QuZ-a0-hr-b0-56.ucode failed with error -2 [2.468104] iwlwifi :00:14.3: api flags index 2 larger than supported by driver [2.468118] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 65.3.35.22 [2.468121] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM [2.468122] iwlwifi :00:14.3: Found debug configuration: 0 [2.468377] iwlwifi :00:14.3: loaded firmware version 55.d9698065.0 QuZ-a0-hr-b0-55.ucode op_mode iwlmvm during boot. The file does not exist in /lib/firmware and I can't find it on github. If it's not important please ignore. thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 19 16:33:13 2023 InstallationDate: Installed on 2020-08-17 (1128 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/2036646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration.
@kmously - I'll do my test again and get back with results -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM hangs No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 I'm able to reproduce the issue using the following kernels: linux-image-5.15.0-67-generic_5.15.0-67.74_amd64.deb linux-image-5.15.0-68-generic_5.15.0-68.75_amd64.deb linux-image-5.15.0-69-generic_5.15.0-69.76_amd64.deb linux-image-5.15.0-70-generic_5.15.0-70.77_amd64.deb linux-image-5.15.0-72-generic_5.15.0-72.79_amd64.deb linux-image-5.15.0-73-generic_5.15.0-73.80_amd64.deb linux-image-5.15.0-74-generic_5.15.0-74.81_amd64.deb linux-image-5.15.0-75-generic_5.15.0-75.82_amd64.deb linux-image-5.15.0-77-generic_5.15.0-77.84_amd64.deb --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029138] Re: cifs: fix mid leak during reconnection after timeout threshold
** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux verification-needed-jammy-linux-aws-6.2 verification-needed-jammy-linux-azure verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-6.2 verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-nvidia-tegra-igx verification-needed-jammy-linux-raspi verification-needed-lunar-linux verification-needed-lunar-linux-azure verification-needed-lunar-linux-starfive ** Tags added: verification-done-focal-linux-nvidia-tegra-5.15 verification-done-focal-linux-riscv-5.15 verification-done-jammy-linux verification-done-jammy-linux-aws-6.2 verification-done-jammy-linux-azure verification-done-jammy-linux-intel-iotg verification-done-jammy-linux-nvidia-6.2 verification-done-jammy-linux-nvidia-tegra verification-done-jammy-linux-nvidia-tegra-igx verification-done-jammy-linux-raspi verification-done-lunar-linux verification-done-lunar-linux-azure verification-done-lunar-linux-starfive -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2029138 Title: cifs: fix mid leak during reconnection after timeout threshold Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-azure source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-azure source package in Lunar: Fix Released Bug description: SRU Justification [Impact] A regression in the Ubuntu 5.15 kernel has been causing problems for multiple customers on Azure. This bug has been fixed in the mainline kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69cba9d3c1284e0838ae408830a02c4a063104bc [Test Plan] Microsoft tested [Regression Potential] Reconnections could fail. [Other Info] SF: #00365185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036630] [NEW] Disks Crashed; package linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-33-generic package post-installatio
Public bug reported: I formatted a new Flash Drive and the process hung. So I unplugged the drive. Disks App crashed when I did. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 18 17:01:28 2023 Df: ErrorMessage: installed linux-image-6.2.0-33-generic package post-installation script subprocess returned error exit status 143 InstallationDate: Installed on 2023-09-16 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) 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.2 apt 2.4.10 SourcePackage: linux-signed-hwe-6.2 Title: package linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-33-generic package post-installation script subprocess returned error exit status 143 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036630 Title: Disks Crashed; package linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 failed to install/upgrade: installed linux- image-6.2.0-33-generic package post-installation script subprocess returned error exit status 143 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: I formatted a new Flash Drive and the process hung. So I unplugged the drive. Disks App crashed when I did. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 18 17:01:28 2023 Df: ErrorMessage: installed linux-image-6.2.0-33-generic package post-installation script subprocess returned error exit status 143 InstallationDate: Installed on 2023-09-16 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) 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.2 apt 2.4.10 SourcePackage: linux-signed-hwe-6.2 Title: package linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-33-generic package post-installation script subprocess returned error exit status 143 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.2/+bug/2036630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034894] Re: Fix requested for SEV live-migration
** Changed in: linux-gcp (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2034894 Title: Fix requested for SEV live-migration Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-gcp source package in Focal: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: The following upstream fix is requested to resolve issues with SEV live-migration: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=ac3f9c9f1b37edaa7d1a9b908bc79d843955a1a2 More details in: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNdQ8AAL/view Testing: - Boot-tested each of f/gcp, j/gcp and l/gcp - GCP has tested each of them as well and reported that the live-migration issue under SEV gets resolved. Regression potential: - The change affects arch/x86/kernel/kvm.c so KVM on x86 can be impacted. It is a minimalistic change though, and regression risk is considered low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2034894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035163] Re: Avoid address overwrite in kernel_connect
** Changed in: linux-gcp (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: linux-gke (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2035163 Title: Avoid address overwrite in kernel_connect Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: Invalid Status in linux-gcp source package in Focal: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gke source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-gcp source package in Mantic: New Bug description: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 Testing: - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. Regression potenial: - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2035163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete
the hardware does not seem to be relevant. Do you have anything calling "racadm lclog" on fairly regular basis? it creates and destroys a usb device over and over. -- 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/2021571 Title: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete Status in linux-meta package in Ubuntu: Confirmed Bug description: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036599] Re: Missing Bluetooth firmwares
I downloaded the previous version from Sep 15th and I could confirm the
firmware my chipset needs is not present, so that was the problem.
--
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/2036599
Title:
Missing Bluetooth firmwares
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
The latest linux-firmware package version
20230919.git3672ccab-0ubuntu1 is missing some Intel Bluetooth
firmwares, in my case the firmware
/lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
0040, etc. are missing too. I had to install an old version so my
Bluetooth mouse could work.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230815.git0e048b06-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
Uname: Linux 6.5.0-6-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 19 09:42:39 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
InstallationDate: Installed on 2021-11-26 (662 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-6-generic N/A
linux-backports-modules-6.5.0-6-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
dmi.bios.date: 08/07/2023
dmi.bios.release: 1.23
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.23.0
dmi.board.name: 0836K6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
dmi.product.family: GSeries
dmi.product.name: Dell G15 5511
dmi.product.sku: 0A70
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036599/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036627] Re: Azure: net: mana: Configure hwc timeout from hardware
Patch submitted for review: https://lists.ubuntu.com/archives/kernel- team/2023-September/143017.html ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Lunar) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Mantic) Status: Fix Released => In Progress ** Changed in: linux-azure (Ubuntu Mantic) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2036627 Title: Azure: net: mana: Configure hwc timeout from hardware Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Lunar: In Progress Status in linux-azure source package in Mantic: In Progress Bug description: SRU Justification [Impact] At present hwc timeout value is a fixed value. This patch sets the hwc timeout from the hardware. It now uses a new hardware capability GDMA_DRV_CAP_FLAG_1_HWC_TIMEOUT_RECONFIG to query and set the value in hwc_timeout. [Test Plan] Microsoft tested and approved. [Regression Potential] Timeouts could get mis-configured. [Other Info] SF: #00365762 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036600] Re: Azure: Fix Azure vendor ID
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux (Ubuntu Lunar)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Mantic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036600
Title:
Azure: Fix Azure vendor ID
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux source package in Mantic:
In Progress
Bug description:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit
(https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
:
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open Source
* 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
I'll post a patch to LKML to fix this typo.
* 55:48 - Distro specific identification
* 47:16 - Linux kernel version number
* 15:0 - Distro specific identification
See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)
As a result, the host thinks that the VM is not an open-source OS, and
it's not Linux. Consequently, the "VM Availability" fron Azure portal
is 0 (unhealthy): some users rely on the info to manage their VMs,
e.g. if the VM is erroneously reported "unhealthy", the VM may be
killed and re-created, and the new VM is still "unhealthy", and the VM
may be killed and re-created again...
Please consider integrating the below fix ASAP. This affects regular
VMs, and I think this affects CVMs as well.
The fix should be:
diff --git a/include/asm-generic/hyperv-tlfs.h
b/include/asm-generic/hyperv-tlfs.h
@@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
*
*/
-#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
+#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */
[Test Plan]
Microsoft tested
[Regression Potential]
This (incorrect) patch has been in place for 10 years. Its possible
that some consumers have come to rely on this VM identifier.
[Other Info]
SF: #00368936
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036600/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036599] Re: Missing Bluetooth firmwares
Nice to know that was a real problem, not my incompetence. :) Yes, with
the latest package is working as intended. Thank you.
--
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/2036599
Title:
Missing Bluetooth firmwares
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
The latest linux-firmware package version
20230919.git3672ccab-0ubuntu1 is missing some Intel Bluetooth
firmwares, in my case the firmware
/lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
0040, etc. are missing too. I had to install an old version so my
Bluetooth mouse could work.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230815.git0e048b06-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
Uname: Linux 6.5.0-6-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 19 09:42:39 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
InstallationDate: Installed on 2021-11-26 (662 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-6-generic N/A
linux-backports-modules-6.5.0-6-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
dmi.bios.date: 08/07/2023
dmi.bios.release: 1.23
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.23.0
dmi.board.name: 0836K6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
dmi.product.family: GSeries
dmi.product.name: Dell G15 5511
dmi.product.sku: 0A70
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036599/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036627] [NEW] Azure: net: mana: Configure hwc timeout from hardware
Public bug reported: SRU Justification [Impact] At present hwc timeout value is a fixed value. This patch sets the hwc timeout from the hardware. It now uses a new hardware capability GDMA_DRV_CAP_FLAG_1_HWC_TIMEOUT_RECONFIG to query and set the value in hwc_timeout. [Test Plan] Microsoft tested and approved. [Regression Potential] Timeouts could get mis-configured. [Other Info] SF: #00365762 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Also affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Also affects: linux-azure (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2036627 Title: Azure: net: mana: Configure hwc timeout from hardware Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Lunar: New Status in linux-azure source package in Mantic: Fix Released Bug description: SRU Justification [Impact] At present hwc timeout value is a fixed value. This patch sets the hwc timeout from the hardware. It now uses a new hardware capability GDMA_DRV_CAP_FLAG_1_HWC_TIMEOUT_RECONFIG to query and set the value in hwc_timeout. [Test Plan] Microsoft tested and approved. [Regression Potential] Timeouts could get mis-configured. [Other Info] SF: #00365762 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036587] Re: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals
The attachment "0001-UBUNTU-Config-Enable-CONFIG_MTK_IOMMU.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036587 Title: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals Status in linux package in Ubuntu: Incomplete Status in lunar package in Ubuntu: New Bug description: [Impact] IOMMU related peripherals cannot work. [Fix] The CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. CONFIG_MTK_IOMMU=m [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/2036587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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.
The attachment "patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: New 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 2000228] Re: Add initial support for Mediatek Genio boards
This bug was fixed in the package alsa-ucm-conf - 1.2.9-1ubuntu2 --- alsa-ucm-conf (1.2.9-1ubuntu2) mantic; urgency=medium * d/p/0001-Add-initial-support-for-MediaTek-mt8390-evk-and-mt83.patch - add initial support for MediaTek mt8390-evk and mt8395-evk (LP: #2000228) -- Ethan Hsieh Mon, 18 Sep 2023 16:13:56 +0800 ** Changed in: alsa-ucm-conf (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2000228 Title: Add initial support for Mediatek Genio boards Status in alsa-ucm-conf package in Ubuntu: Fix Released Bug description: [Impact] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk) mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 mt8390-evk: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 mt8395-evk: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/322 [Where problems could occur] Audio function doesn't work on Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). [Test Case] Verify audio function on Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. HDMI Playback Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). There should be no risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028065] Re: Support for Intel Discrete Gale Peak2/BE200
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/2028065
Title:
Support for Intel Discrete Gale Peak2/BE200
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Incomplete
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:
Incomplete
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
In Progress
Status in linux-firmware source package in Mantic:
Incomplete
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Intel Gale Peak WiFi/Bluetooth support.
[Fix]
WIFI:
a. kernel driver :
- commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
crash") [v6.5-rc2]
b. firmware (to be released):
- iwlwifi-gl-b0-fm-b0-83.ucode
- iwlwifi-gl-b0-fm-b0.pnvm
Bluetooth:
a. kernel driver:
- commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
- commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
b. firmware (to be released):
- intel/ibt-0191-0191.sfi
- intel/ibt-0191-0191.ddc
[Test Case]
To boot with patched kernel and prereleased firmware blob and check basic
WiFi/Bluetooth functions.
[Where problems could occur]
New device. Expect incomplete functions and bugs.
[Other Info]
Targets 6.5 kernels, so only nominated for Mantic and oem-6.5.
= original bug report ==
WIFI:
a. kernel driver :
- commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
crash") [v6.5-rc2]
b. firmware (to be released):
- iwlwifi-gl-b0-fm-b0-83.ucode
- iwlwifi-gl-b0-fm-b0.pnvm
Bluetooth:
a. kernel driver:
- commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
- commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
b. firmware (to be released):
- intel/ibt-0191-0191.sfi
- intel/ibt-0191-0191.ddc
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2028065/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008882] Re: Make backlight module auto detect dell_uart_backlight
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/2008882
Title:
Make backlight module auto detect dell_uart_backlight
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-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 Committed
Status in linux source package in Lunar:
Won't Fix
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:
In Progress
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]
There are acpi_video* sysfs backlight interface in the system which are not
working.
For Dell AIO platforms, we use dell_uart_backlight to control the display
brightness.
The old way to fix this is to unregister acpi backlight interfaces in the
backlight driver, but it may lead to some issues and the unregister function
has been removed since v6.1-rc1
77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")
[Fix]
The new way to do this is to collect all the quirk and auto detection method
in video_detect.c
I added an audo detection for the Dell AIO platoform to the driver which
should do the same thing as the old way.
[Test]
Verified on the Dell AIO platform and confirmed there is only on
dell_uart_backlight in the sysfs, and no acpi_video* interface.
[Where problems could occur]
There should be no regression potential, it uses different way to do the same
thing, should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2008882/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033455] Re: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/2033455 Title: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Incomplete 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: Incomplete Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-firmware source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2033455 [Impact] Missing BT IDs for support for Intel Discrete Misty Peak2/BE202. [Fix] Bluetooth: a. kernel driver: - https://lore.kernel.org/linux-bluetooth/20230829124024.40592-1-vijay.sat...@intel.com/T/#t - Also depends on patches for Gale Peak(BE200) from bug 2028065. b. firmware (shared with Gale Peak, to be released): - intel/ibt-0191-0191.sfi - intel/ibt-0191-0191.ddc [Test Case] To boot with patched kernel and prereleased firmware blob and check basic Bluetooth functions. [Where problems could occur] New device. Expect incomplete functions and bugs. [Other Info] Targets 6.5 kernels, so only nominated for Mantic and oem-6.5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029199] Re: NULL pointer dereference on CS35L41 HDA AMP
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Fix Committed -- 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/2029199 Title: NULL pointer dereference on CS35L41 HDA AMP Status in HWE Next: New Status in linux package in Ubuntu: Confirmed 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 Committed Status in linux source package in Lunar: Fix Committed 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] NULL pointer dereference happens because the HDA driver is trying to use CS35L41 HDA AMP before its probe routine is fully realized. [Fix] Use device link to enforce proper probe order. Since the fixing commit is part of a patch series, pull in the entire series which has several other important fixes too. [Test] Use dmesg to see if there's error. With the fix applied, no more kernel splat can be found. Hence the system can perform suspend, reboot and shutdown normally. [Where problems could occur] Though the entire series isn't trivia, it's not a major overhaul either. The entire changeset is limited to CS35L41 AMP, so the scope of regression risk is constrained. One possible risk factor is that it may require newer DSP firmware, and we'll monitor it closely on such scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2029199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034506] Re: Audio device fails to function randomly on Intel MTL platform: No CPC match in the firmware file's manifest
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2034506
Title:
Audio device fails to function randomly on Intel MTL platform: No CPC
match in the firmware file's manifest
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 Committed
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2034506
[Impact]
Audio device fails to function randomly on Intel MTL platform:
```
sof-audio-pci-intel-mtl :00:1f.3: no llp found, fall back to default HDA
path
sof-audio-pci-intel-mtl :00:1f.3: COPIER (UUID:
9BA00C83-CA12-4A83-943C-1FA2E82F9DDA): No CPC match in the firmware file's
manifest (ibs/obs: 384/192)
```
[Fix]
Proposed fix in upstream commit 26ef47e5ba60 ("ASoC: SOF:
ipc4-topology: Add module parameter to ignore the CPC value") that to
allow ignoring CPC validation for current fw release.
[Test Case]
1. Boot into OS
2. Check if the internal audio input & output devices work
3. Let system enter suspend, then wake system back up
4. Check if the audio input & output devices work
5. Connect an external audio device (e.g. bluetooth headset, external
monitor) and check if they work
6. Disconnect the external audio device
7. Check if the internal audio input & output devices work
8. Reboot system
9. Repeat above steps
[Where problems could occur]
While a 0 CPC value will force the DSP to run at full speed, this is
going to impact power consumption until further fix being released for
firmware.
[Other Info]
CPC checking landed to v6.5-rc1, so Mantic and oem-6.5 are nominated
for fix.
== original bug report ==
sof-audio-pci-intel-mtl :00:1f.3: no llp found, fall back to default HDA
path
sof-audio-pci-intel-mtl :00:1f.3: COPIER (UUID:
9BA00C83-CA12-4A83-943C-1FA2E82F9DDA): No CPC match in the firmware file's
manifest (ibs/obs: 384/192)
Proposed fix in upstream commit 26ef47e5ba60 ("ASoC: SOF:
ipc4-topology: Add module parameter to ignore the CPC value") that to
allow ignoring CPC validation for current fw release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2034506/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- 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/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed 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: New Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Confirmed 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: Confirmed 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035306] Re: Include QCA WWAN 5G Qualcomm SDX62/DW5932e support
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035306
Title:
Include QCA WWAN 5G Qualcomm SDX62/DW5932e 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 Committed
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
DW5932e is the new 5G QCA WWAN module for Dell platforms, it won't work
without the IDs in the table.
[Fix]
This commit adds the required IDs to the table
104a8c5dd943 ("bus: mhi: host: pci_generic: Add support for Dell DW5932e")
[Test case]
1. connect to the 5G WWAN through the GUI
2. make sure the network is working
[Where problems could occur]
It adds 2 IDs to the table, won't impact existing systems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2035306/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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.
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035299
Title:
dell-uart-backlight fails to communicate with the scalar IC somtimes.
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 Committed
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
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 2036184] Re: Infiniate systemd loop when power off the machine with multiple MD RAIDs
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036184
Title:
Infiniate systemd loop when power off the machine with multiple MD
RAIDs
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 Committed
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
The system with multiple MD RAIDs sometimes hangs while rebooting, that's
because of the systemd can't stop and close the MD disk.
[Fix]
This commit fixes the issue, and this issue has been introduced by
12a6caf27324 ("md: only delete entries from all_mddevs when the disk is freed")
after v6.0
https://patchwork.kernel.org/project/linux-
raid/patch/20230914152416.10819-1-mariusz.tkac...@linux.intel.com/
[Test case]
1. Reboot the system with multiple MD RAIDs at least 10 times.
2. Make sure the system can reboot successfully every time.
3. You should not see error messages like below.
[ 205.360738] systemd-shutdown[1]: Stopping MD devices.
[ 205.366384] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs
[ 205.373327] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus
[ 205.380427] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class
[ 205.388257] systemd-shutdown[1]: Stopping MD /dev/md127 (9:127).
[ 205.394880] systemd-shutdown[1]: Failed to sync MD block device /dev/md127,
ignoring: Input/output error
[ 205.404975] md: md127 stopped.
[ 205.470491] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126).
[ 205.770179] md: md126: resync interrupted.
[ 205.776258] md126: detected capacity change from 1900396544 to 0
[ 205.783349] md: md126 stopped.
[ 205.862258] systemd-shutdown[1]: Stopping MD /dev/md125 (9:125).
[ 205.862435] md: md126 stopped.
[ 205.868376] systemd-shutdown[1]: Failed to sync MD block device /dev/md125,
ignoring: Input/output error
[ 205.872845] block device autoloading is deprecated and will be removed.
[ 205.880955] md: md125 stopped.
[ 205.934349] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:7).
[ 205.947707] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or
resource busy
[ 205.957004] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:6).
[ 205.964177] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or
resource busy
[ 205.973155] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124).
[ 205.979789] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or
resource busy
[ 205.988475] systemd-shutdown[1]: Not all MD devices stopped, 4 left.
[Where problems could occur]
It fixes the data race issue, should not introduce any regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2036184/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036599] Re: Missing Bluetooth firmwares
Ok I think I know what's going on. linux-
firmware/20230915.gitdfa11466-0ubuntu1 was broken and didn't provide the
files. That's probably when you saw the above error. The new version
from today 20230919.git3672ccab-0ubuntu1 should fix this. Can you
confirm that it's working with linux-
firmware/20230919.git3672ccab-0ubuntu1?
--
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/2036599
Title:
Missing Bluetooth firmwares
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
The latest linux-firmware package version
20230919.git3672ccab-0ubuntu1 is missing some Intel Bluetooth
firmwares, in my case the firmware
/lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
0040, etc. are missing too. I had to install an old version so my
Bluetooth mouse could work.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230815.git0e048b06-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
Uname: Linux 6.5.0-6-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 19 09:42:39 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
InstallationDate: Installed on 2021-11-26 (662 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-6-generic N/A
linux-backports-modules-6.5.0-6-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
dmi.bios.date: 08/07/2023
dmi.bios.release: 1.23
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.23.0
dmi.board.name: 0836K6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
dmi.product.family: GSeries
dmi.product.name: Dell G15 5511
dmi.product.sku: 0A70
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036599/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036613] Re: BUG: kernel NULL pointer dereference
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2036613/+attachment/5702052/+files/syslog.txt ** Attachment removed: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2036613/+attachment/5702051/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2036613 Title: BUG: kernel NULL pointer dereference Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Machine reports BUG: kernel NULL pointer dereference and then stops responding to ping. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-83-generic 5.15.0-83.92~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 19 17:14:03 2023 InstallationDate: Installed on 2023-08-21 (29 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2036613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036613] [NEW] BUG: kernel NULL pointer dereference
Public bug reported: Machine reports BUG: kernel NULL pointer dereference and then stops responding to ping. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-83-generic 5.15.0-83.92~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 19 17:14:03 2023 InstallationDate: Installed on 2023-08-21 (29 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "lsb_release" https://bugs.launchpad.net/bugs/2036613/+attachment/5702047/+files/lsb_release.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2036613 Title: BUG: kernel NULL pointer dereference Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Machine reports BUG: kernel NULL pointer dereference and then stops responding to ping. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-83-generic 5.15.0-83.92~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 19 17:14:03 2023 InstallationDate: Installed on 2023-08-21 (29 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2036613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036613] Re: BUG: kernel NULL pointer dereference
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2036613/+attachment/5702051/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2036613 Title: BUG: kernel NULL pointer dereference Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Machine reports BUG: kernel NULL pointer dereference and then stops responding to ping. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-83-generic 5.15.0-83.92~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 19 17:14:03 2023 InstallationDate: Installed on 2023-08-21 (29 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2036613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036599] Re: Missing Bluetooth firmwares
@Juerg, no. I reinstalled the package and everything is working fine
now. Maybe some file system corruption? Anyway, I marked this issue as
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/2036599
Title:
Missing Bluetooth firmwares
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
The latest linux-firmware package version
20230919.git3672ccab-0ubuntu1 is missing some Intel Bluetooth
firmwares, in my case the firmware
/lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
0040, etc. are missing too. I had to install an old version so my
Bluetooth mouse could work.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230815.git0e048b06-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
Uname: Linux 6.5.0-6-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 19 09:42:39 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
InstallationDate: Installed on 2021-11-26 (662 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-6-generic N/A
linux-backports-modules-6.5.0-6-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
dmi.bios.date: 08/07/2023
dmi.bios.release: 1.23
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.23.0
dmi.board.name: 0836K6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
dmi.product.family: GSeries
dmi.product.name: Dell G15 5511
dmi.product.sku: 0A70
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036599/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035181] Re: Regression for ubuntu_bpf test build on Jammy 5.15.0-85.95
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035181
Title:
Regression for ubuntu_bpf test build on Jammy 5.15.0-85.95
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Bug description:
[Impact]
Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work
with CO-RE") from stable update breaks the ubuntu_bpf test build and
cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in
ubuntu_kernel_selftests stopped working, as they require bpf selftest
to be built first.
The following is extracted from the commit message:
The problem is the new offsetof() does not play nice with static asserts.
Given that the context is a static assert (and CO-RE relocation is not
needed at compile time), offsetof() usage can be replaced by restoring
the original offsetof() definition as __builtin_offsetof().
[Test Plan]
Build bpf selftest in tools/testing/selftests with the following command:
make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \
clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/
The build can finish successfully with patched kernel source code.
[Where problems could occur]
Fix limited to testing tool, if this fix is incorrect the bpf selftest
build will remain broken.
== Original bug report ==
Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04
This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
is a security cycle, in which the ubuntu_bpf test was not triggered
there)
Test build failed with:
CLNG-BPF [test_maps] test_btf_map_in_map.o
CLNG-BPF [test_maps] test_btf_newkv.o
CLNG-BPF [test_maps] test_btf_nokv.o
CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
CLNG-BPF [test_maps] test_cgroup_link.o
CLNG-BPF [test_maps] test_check_mtu.o
CLNG-BPF [test_maps] test_cls_redirect.o
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from
latest version at 'include/uapi/linux/bpf.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs
from latest version at 'include/uapi/linux/netlink.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at 'include/uapi/linux/if_link.h'
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
2 errors generated.
make[1]: *** [Makefile:470:
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_cls_redirect.o]
Error 1
make: *** [Makefile:171: all] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2035181/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034447] Re: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic
** Changed in: linux (Ubuntu Jammy) Status: Triaged => 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/2034447 Title: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: Seeing a panic on hidon (an Nvidia H100) after booting the 5.15.0-85-generic kernel: [ 58.935877] [ cut here ] [ 58.935893] refcount_t: underflow; use-after-free. [ 58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28 refcount_warn_saturate+0xf7/0x150 [ 58.935943] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp coretemp nls_iso8859_1 rapl irdma(+) i40e qat_4xxx(+) isst_if_mbox_pci intel_qat pmt_telemetry pmt_crashlog idxd(+) isst_if_mmio pmt_class isst_if_common authenc idxd_bus intel_th_gth mei_me intel_th_pci intel_th mei switchtec ipmi_ssif acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 multipath linear mlx5_ib ib_uverbs ib_core ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper raid0 mlx5_core syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ixgbe cec mlxfw ghash_clmulni_intel aesni_intel psample crypto_simd xfrm_algo ice rc_core cryptd tls nvme i2c_i801 dca xhci_pci intel_pmt drm [ 58.936077] pci_hyperv_intf i2c_ismt i2c_smbus [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936083] mdio [ 58.936096] xhci_pci_renesas nvme_core wmi pinctrl_emmitsburg [ 58.936106] CPU: 207 PID: 2985 Comm: systemd-udevd Not tainted 5.15.0-85-generic #95-Ubuntu [ 58.936115] Hardware name: NVIDIA DGXH100/DGXH100, BIOS 1.0.7 05/08/2023 [ 58.936119] RIP: 0010:refcount_warn_saturate+0xf7/0x150 [ 58.936130] Code: eb 9e 0f b6 1d 5e e6 b9 01 80 fb 01 0f 87 f4 63 6f 00 83 e3 01 75 89 48 c7 c7 88 c3 23 9e c6 05 42 e6 b9 01 01 e8 d8 e4 6b 00 <0f> 0b e9 6f ff ff ff 0f b6 1d 2d e6 b9 01 80 fb 01 0f 87 b1 63 6f [ 58.936135] RSP: 0018:ff4d5d94b2c7fa28 EFLAGS: 00010282 [ 58.936142] RAX: RBX: RCX: 0027 [ 58.936146] RDX: ff314dbbbf9e0588 RSI: 0001 RDI: ff314dbbbf9e0580 [ 58.936149] RBP: ff4d5d94b2c7fa30 R08: 0026 R09: ff4d5d94b2c7f9c0 [ 58.936153] R10: 0028 R11: 0001 R12: [ 58.936156] R13: ff314cbfdbcb6900 R14: ff314cbfdbcb67b8 R15: ff314cbfd24b4000 [ 58.936159] FS: 7fadd2f6c8c0() GS:ff314dbbbf9c() knlGS: [ 58.936163] CS: 0010 DS: ES: CR0: 80050033 [ 58.936167] CR2: 7fadd243b584 CR3: 00012972c006 CR4: 00771ee0 [ 58.936171] DR0: DR1: DR2: [ 58.936174] DR3: DR6: fffe07f0 DR7: 0400 [ 58.936177] PKRU: 5554 [ 58.936179] Call Trace: [ 58.936184] [ 58.936188] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936204] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936212] ? crypto_mod_put+0x6b/0x80 [ 58.936225] ? show_regs.part.0+0x23/0x29 [ 58.936232] ? show_regs.cold+0x8/0xd [ 58.936239] ? refcount_warn_saturate+0xf7/0x150 [ 58.936246] ? __warn+0x8c/0x100 [ 58.936255] ? refcount_warn_saturate+0xf7/0x150 [ 58.936263] ? report_bug+0xa4/0xd0 [ 58.936274] ? down_trylock+0x2e/0x40 [ 58.936285] ? handle_bug+0x39/0x90 [ 58.936296] ? exc_invalid_op+0x19/0x70 [ 58.936301] ? asm_exc_invalid_op+0x1b/0x20 [ 58.936310] ? refcount_warn_saturate+0xf7/0x150 [ 58.936317] ? refcount_warn_saturate+0xf7/0x150 [ 58.936323] crypto_mod_put+0x6b/0x80 [ 58.936329] crypto_destroy_tfm+0x4e/0xa0 [ 58.936336] pkcs1pad_exit_tfm+0x15/0x20 [ 58.936345] crypto_akcipher_exit_tfm+0x13/0x20 [ 58.936352] crypto_destroy_tfm+0x43/0xa0 [ 58.936358] public_key_verify_signature+0x2dc/0x3c0 [ 58.936366] ? find_asymmetric_key+0xd2/0x1d0 [ 58.936374] ? kfree+0x1f7/0x250 [ 58.936385] public_key_verify_signature_2+0x15/0x20 [ 58.936389] verify_signature+0x37/0x60 [ 58.936393] pkcs7_validate_trust_one.constprop.0+0x156/0x1e0 [ 58.936400] pkcs7_validate_trust+0x4a/0xa0 [
[Kernel-packages] [Bug 2036599] Re: Missing Bluetooth firmwares
Are you sure the files are missing?
--
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/2036599
Title:
Missing Bluetooth firmwares
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
The latest linux-firmware package version
20230919.git3672ccab-0ubuntu1 is missing some Intel Bluetooth
firmwares, in my case the firmware
/lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
0040, etc. are missing too. I had to install an old version so my
Bluetooth mouse could work.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230815.git0e048b06-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
Uname: Linux 6.5.0-6-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 19 09:42:39 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
InstallationDate: Installed on 2021-11-26 (662 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-6-generic N/A
linux-backports-modules-6.5.0-6-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
dmi.bios.date: 08/07/2023
dmi.bios.release: 1.23
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.23.0
dmi.board.name: 0836K6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
dmi.product.family: GSeries
dmi.product.name: Dell G15 5511
dmi.product.sku: 0A70
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036599/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034256] Re: package linux-image-6.2.0-32-generic 6.2.0-32.32 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Kernel -> 6.2.0-33-generic : same problem, same workaround. :D -- 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/2034256 Title: package linux-image-6.2.0-32-generic 6.2.0-32.32 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in linux package in Ubuntu: Confirmed Bug description: See also #2033371 = Kernel 6.2.0-27 running -- kernel 6.2.0-31 installed but inoperable Upgrading to kernel 6.2.0-32.32 fails: (Reading database ... 209096 files and directories currently installed.) Purging configuration files for linux-modules-6.2.0-31-generic (6.2.0-31.31) ... Purging configuration files for linux-modules-nvidia-535-6.2.0-31-generic (6.2.0-31.31) ... Purging configuration files for linux-image-6.2.0-31-generic (6.2.0-31.31) ... Purging configuration files for linux-objects-nvidia-535-6.2.0-31-generic (6.2.0-31.31) ... Purging configuration files for linux-modules-extra-6.2.0-31-generic (6.2.0-31.31) ... Processing triggers for linux-image-6.2.0-32-generic (6.2.0-32.32) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-32-generic Sign command: /lib/modules/6.2.0-32-generic/build/scripts/sign-file Binary /lib/modules/6.2.0-32-generic/build/scripts/sign-file not found, modules won't be signed Error! Your kernel headers for kernel 6.2.0-32-generic cannot be found at /lib/modules/6.2.0-32-generic/build or /lib/modules/6.2.0-32-generic/source. Please install the linux-headers-6.2.0-32-generic package or use the --kernelsourcedir option to tell DKMS where it's located. dkms autoinstall on 6.2.0-32-generic/x86_64 failed for zfs(1) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.2.0-32-generic ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-32-generic (--configure): installed linux-image-6.2.0-32-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-6.2.0-32-generic E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-6.2.0-32-generic (6.2.0-32.32) ... I: /boot/initrd.img.old is now a symlink to initrd.img-6.2.0-32-generic Processing triggers for linux-image-6.2.0-32-generic (6.2.0-32.32) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-32-generic Sign command: /lib/modules/6.2.0-32-generic/build/scripts/sign-file Binary /lib/modules/6.2.0-32-generic/build/scripts/sign-file not found, modules won't be signed Error! Your kernel headers for kernel 6.2.0-32-generic cannot be found at /lib/modules/6.2.0-32-generic/build or /lib/modules/6.2.0-32-generic/source. Please install the linux-headers-6.2.0-32-generic package or use the --kernelsourcedir option to tell DKMS where it's located. dkms autoinstall on 6.2.0-32-generic/x86_64 failed for zfs(1) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.2.0-32-generic ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-32-generic (--configure): installed linux-image-6.2.0-32-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-6.2.0-32-generic ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: burdi015159 F wireplumber /dev/snd/controlC0: burdi015159 F wireplumber /dev/snd/seq:burdi015157 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Sep 5 16:23:11 2023 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp39s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C35 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p10 ro pci=noaer PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 RfKill: 0:
[Kernel-packages] [Bug 2000228] Re: Add initial support for Mediatek Genio boards
Thanks, I've uploaded the changes to J/L/M now ** Changed in: alsa-ucm-conf (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2000228 Title: Add initial support for Mediatek Genio boards Status in alsa-ucm-conf package in Ubuntu: Fix Committed Bug description: [Impact] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk) mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 mt8390-evk: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 mt8395-evk: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/322 [Where problems could occur] Audio function doesn't work on Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). [Test Case] Verify audio function on Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. HDMI Playback Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). There should be no risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036600] Re: Azure: Fix Azure vendor ID
Patch submitted for review: https://lists.ubuntu.com/archives/kernel-
team/2023-September/143008.html
--
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/2036600
Title:
Azure: Fix Azure vendor ID
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
New
Status in linux source package in Jammy:
New
Status in linux source package in Lunar:
New
Status in linux source package in Mantic:
Incomplete
Bug description:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit
(https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
:
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open Source
* 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
I'll post a patch to LKML to fix this typo.
* 55:48 - Distro specific identification
* 47:16 - Linux kernel version number
* 15:0 - Distro specific identification
See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)
As a result, the host thinks that the VM is not an open-source OS, and
it's not Linux. Consequently, the "VM Availability" fron Azure portal
is 0 (unhealthy): some users rely on the info to manage their VMs,
e.g. if the VM is erroneously reported "unhealthy", the VM may be
killed and re-created, and the new VM is still "unhealthy", and the VM
may be killed and re-created again...
Please consider integrating the below fix ASAP. This affects regular
VMs, and I think this affects CVMs as well.
The fix should be:
diff --git a/include/asm-generic/hyperv-tlfs.h
b/include/asm-generic/hyperv-tlfs.h
@@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
*
*/
-#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
+#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */
[Test Plan]
Microsoft tested
[Regression Potential]
This (incorrect) patch has been in place for 10 years. Its possible
that some consumers have come to rely on this VM identifier.
[Other Info]
SF: #00368936
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036600/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036600] Re: Azure: Fix Azure vendor ID
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036600
Title:
Azure: Fix Azure vendor ID
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
New
Status in linux source package in Jammy:
New
Status in linux source package in Lunar:
New
Status in linux source package in Mantic:
Incomplete
Bug description:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit
(https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
:
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open Source
* 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
I'll post a patch to LKML to fix this typo.
* 55:48 - Distro specific identification
* 47:16 - Linux kernel version number
* 15:0 - Distro specific identification
See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)
As a result, the host thinks that the VM is not an open-source OS, and
it's not Linux. Consequently, the "VM Availability" fron Azure portal
is 0 (unhealthy): some users rely on the info to manage their VMs,
e.g. if the VM is erroneously reported "unhealthy", the VM may be
killed and re-created, and the new VM is still "unhealthy", and the VM
may be killed and re-created again...
Please consider integrating the below fix ASAP. This affects regular
VMs, and I think this affects CVMs as well.
The fix should be:
diff --git a/include/asm-generic/hyperv-tlfs.h
b/include/asm-generic/hyperv-tlfs.h
@@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
*
*/
-#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
+#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */
[Test Plan]
Microsoft tested
[Regression Potential]
This (incorrect) patch has been in place for 10 years. Its possible
that some consumers have come to rely on this VM identifier.
[Other Info]
SF: #00368936
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036600/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
Reposted the patch for all affected kernels: https://lists.ubuntu.com/archives/kernel-team/2023-September/142913.html -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036599] Re: Missing Bluetooth firmwares
Hmmm... Strange... I got this problem a boot earlier:
set 19 08:53:11 glados kernel: Bluetooth: hci0: Debug lock is disabled
set 19 08:53:11 glados kernel: Bluetooth: hci0: Minimum firmware build 1 week
10 2014
set 19 08:53:11 glados kernel: Bluetooth: hci0: Bootloader timestamp 2019.40
buildtype 1 build 38
set 19 08:53:11 glados kernel: Bluetooth: hci0: Failed to load Intel firmware
file intel/ibt-0041-0041.sfi (-2)
set 19 08:53:11 glados kernel: Bluetooth: hci0: Reading supported features
failed (-56)
set 19 08:53:11 glados kernel: Bluetooth: hci0: Error reading debug features
set 19 08:53:11 glados kernel: Bluetooth: hci0: Failed to read MSFT supported
features (-56)
And I checked and the firmware wasn't there, but I downgraded and upgraded
again and seems it's back. Very strange...
** 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/2036599
Title:
Missing Bluetooth firmwares
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
The latest linux-firmware package version
20230919.git3672ccab-0ubuntu1 is missing some Intel Bluetooth
firmwares, in my case the firmware
/lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
0040, etc. are missing too. I had to install an old version so my
Bluetooth mouse could work.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230815.git0e048b06-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
Uname: Linux 6.5.0-6-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 19 09:42:39 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
InstallationDate: Installed on 2021-11-26 (662 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-6-generic N/A
linux-backports-modules-6.5.0-6-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
dmi.bios.date: 08/07/2023
dmi.bios.release: 1.23
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.23.0
dmi.board.name: 0836K6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
dmi.product.family: GSeries
dmi.product.name: Dell G15 5511
dmi.product.sku: 0A70
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036599/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036599] Re: Missing Bluetooth firmwares
Hmmm... Strange... I got this problem a boot earlier:
set 19 08:53:11 glados kernel: Bluetooth: hci0: Debug lock is disabled
set 19 08:53:11 glados kernel: Bluetooth: hci0: Minimum firmware build 1 week
10 2014
set 19 08:53:11 glados kernel: Bluetooth: hci0: Bootloader timestamp 2019.40
buildtype 1 build 38
set 19 08:53:11 glados kernel: Bluetooth: hci0: Failed to load Intel firmware
file intel/ibt-0041-0041.sfi (-2)
set 19 08:53:11 glados kernel: Bluetooth: hci0: Reading supported features
failed (-56)
set 19 08:53:11 glados kernel: Bluetooth: hci0: Error reading debug features
set 19 08:53:11 glados kernel: Bluetooth: hci0: Failed to read MSFT supported
features (-56)
And I checked and the firmware wasn't there, but I downgraded and upgraded
again and seems it's back. Very strange...
--
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/2036599
Title:
Missing Bluetooth firmwares
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
The latest linux-firmware package version
20230919.git3672ccab-0ubuntu1 is missing some Intel Bluetooth
firmwares, in my case the firmware
/lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
0040, etc. are missing too. I had to install an old version so my
Bluetooth mouse could work.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230815.git0e048b06-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
Uname: Linux 6.5.0-6-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 19 09:42:39 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
InstallationDate: Installed on 2021-11-26 (662 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-6-generic N/A
linux-backports-modules-6.5.0-6-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
dmi.bios.date: 08/07/2023
dmi.bios.release: 1.23
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.23.0
dmi.board.name: 0836K6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
dmi.product.family: GSeries
dmi.product.name: Dell G15 5511
dmi.product.sku: 0A70
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036599/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036600] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2036600
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036600
Title:
Azure: Fix Azure vendor ID
Status in linux package in Ubuntu:
Incomplete
Bug description:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit
(https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
:
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open Source
* 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
I'll post a patch to LKML to fix this typo.
* 55:48 - Distro specific identification
* 47:16 - Linux kernel version number
* 15:0 - Distro specific identification
See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)
As a result, the host thinks that the VM is not an open-source OS, and
it's not Linux. Consequently, the "VM Availability" fron Azure portal
is 0 (unhealthy): some users rely on the info to manage their VMs,
e.g. if the VM is erroneously reported "unhealthy", the VM may be
killed and re-created, and the new VM is still "unhealthy", and the VM
may be killed and re-created again...
Please consider integrating the below fix ASAP. This affects regular
VMs, and I think this affects CVMs as well.
The fix should be:
diff --git a/include/asm-generic/hyperv-tlfs.h
b/include/asm-generic/hyperv-tlfs.h
@@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
*
*/
-#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
+#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */
[Test Plan]
Microsoft tested
[Regression Potential]
This (incorrect) patch has been in place for 10 years. Its possible
that some consumers have come to rely on this VM identifier.
[Other Info]
SF: #00368936
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036600/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036428] Re: Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1
I can confirm that the bug related to Intel AX201 Bluetooth not being available has been fixed with the latest release. -- 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/2036428 Title: Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1 Status in linux-firmware package in Ubuntu: Fix Released Bug description: After upgrading linux-firmware to 20230915.gitdfa11466-0ubuntu1, my Intel AX201 Bluetooth controller is not available post-reboot. The device itself shows up here: $ lsusb | grep -i blue Bus 003 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth But running e.g. `dmesg | grep -i bluetooth` returns no matches, and bluetoothctl finds no controllers. Reverting to the 20230323.gitbcdcfbcf-0ubuntu1.6 package restores full functionality. n.b. Possible duplicate of LP:2036348 - I am not in a position to confirm those symptoms yet, but will update later. Running mantic pre-release on amd64: $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036600] [NEW] Azure: Fix Azure vendor ID
Public bug reported:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit (https://git.launchpad.net/~canonical-
kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8) :
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open Source
* 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1. I'll
post a patch to LKML to fix this typo.
* 55:48 - Distro specific identification
* 47:16 - Linux kernel version number
* 15:0 - Distro specific identification
See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)
As a result, the host thinks that the VM is not an open-source OS, and
it's not Linux. Consequently, the "VM Availability" fron Azure portal is
0 (unhealthy): some users rely on the info to manage their VMs, e.g. if
the VM is erroneously reported "unhealthy", the VM may be killed and re-
created, and the new VM is still "unhealthy", and the VM may be killed
and re-created again...
Please consider integrating the below fix ASAP. This affects regular
VMs, and I think this affects CVMs as well.
The fix should be:
diff --git a/include/asm-generic/hyperv-tlfs.h
b/include/asm-generic/hyperv-tlfs.h
@@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
*
*/
-#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
+#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */
[Test Plan]
Microsoft tested
[Regression Potential]
This (incorrect) patch has been in place for 10 years. Its possible that
some consumers have come to rely on this VM identifier.
[Other Info]
SF: #00368936
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Description changed:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit (https://git.launchpad.net/~canonical-
kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8) :
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open Source
* 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1. I'll
post a patch to LKML to fix this typo.
* 55:48 - Distro specific identification
* 47:16 - Linux kernel version number
* 15:0 - Distro specific identification
See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)
As a result, the host thinks that the VM is not an open-source OS, and
it's not Linux. Consequently, the "VM Availability" fron Azure portal is
0 (unhealthy): some users rely on the info to manage their VMs, e.g. if
the VM is erroneously reported "unhealthy", the VM may be killed and re-
created, and the new VM is still "unhealthy", and the VM may be killed
and re-created again...
Please consider integrating the below fix ASAP. This affects regular
VMs, and I think this affects CVMs as well.
The fix should be:
diff --git a/include/asm-generic/hyperv-tlfs.h
b/include/asm-generic/hyperv-tlfs.h
@@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
*
*/
-#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
+#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */
+
+ [Test Plan]
+
+ Microsoft tested
+
+ [Regression Potential]
+
+ This (incorrect) patch has been in place for 10 years. Its possible that
+ some consumers have come to rely on this VM identifier.
+
+ [Other Info]
+
+ SF: #00368936
--
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/2036600
Title:
Azure: Fix Azure vendor ID
Status in linux package in Ubuntu:
Incomplete
Bug description:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit
(https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
:
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open
[Kernel-packages] [Bug 2036599] [NEW] Missing Bluetooth firmwares
Public bug reported:
The latest linux-firmware package version 20230919.git3672ccab-0ubuntu1
is missing some Intel Bluetooth firmwares, in my case the firmware
/lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
0040, etc. are missing too. I had to install an old version so my
Bluetooth mouse could work.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230815.git0e048b06-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
Uname: Linux 6.5.0-6-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 19 09:42:39 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
InstallationDate: Installed on 2021-11-26 (662 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-6-generic N/A
linux-backports-modules-6.5.0-6-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
dmi.bios.date: 08/07/2023
dmi.bios.release: 1.23
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.23.0
dmi.board.name: 0836K6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
dmi.product.family: GSeries
dmi.product.name: Dell G15 5511
dmi.product.sku: 0A70
dmi.sys.vendor: Dell Inc.
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
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/2036599
Title:
Missing Bluetooth firmwares
Status in linux-firmware package in Ubuntu:
New
Bug description:
The latest linux-firmware package version
20230919.git3672ccab-0ubuntu1 is missing some Intel Bluetooth
firmwares, in my case the firmware
/lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
0040, etc. are missing too. I had to install an old version so my
Bluetooth mouse could work.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230815.git0e048b06-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
Uname: Linux 6.5.0-6-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 19 09:42:39 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
InstallationDate: Installed on 2021-11-26 (662 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-6-generic N/A
linux-backports-modules-6.5.0-6-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
dmi.bios.date: 08/07/2023
dmi.bios.release: 1.23
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.23.0
dmi.board.name: 0836K6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
dmi.product.family: GSeries
dmi.product.name: Dell G15 5511
dmi.product.sku: 0A70
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036599/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
FWIW, this not only affects the 5.15/jammy kernel series, but also at least 6.2/lunar: https://github.com/openzfs/zfs/issues/15223 , and also affects non-SGX use cases like OpenZFS features that benefit from AVX support (raidz, encryption, ..) ** Bug watch added: github.com/openzfs/zfs/issues #15223 https://github.com/openzfs/zfs/issues/15223 -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
** Changed in: xorg-server Status: Unknown => 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in X.Org X server: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036428] Re: Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1
This bug was fixed in the package linux-firmware - 20230919.git3672ccab-0ubuntu1 --- linux-firmware (20230919.git3672ccab-0ubuntu1) mantic; urgency=medium * Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1 (LP: #2036428) * Miscellaneous Ubuntu changes - Rebase to upstream commit 3672ccab9237315db2f3a28a47f8ac1062a5a35e Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git - amdgpu: update DMCUB to 0.0.183.0 for various AMDGPU ASICs - i915: update MTL HuC to version 8.5.4 - linux-firmware: amd-ucode: Add note on fam19h warnings - Run merge request pipelines for pre-commit. -- Juerg Haefliger Tue, 19 Sep 2023 08:46:58 +0200 ** Changed in: linux-firmware (Ubuntu) Status: Confirmed => 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/2036428 Title: Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1 Status in linux-firmware package in Ubuntu: Fix Released Bug description: After upgrading linux-firmware to 20230915.gitdfa11466-0ubuntu1, my Intel AX201 Bluetooth controller is not available post-reboot. The device itself shows up here: $ lsusb | grep -i blue Bus 003 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth But running e.g. `dmesg | grep -i bluetooth` returns no matches, and bluetoothctl finds no controllers. Reverting to the 20230323.gitbcdcfbcf-0ubuntu1.6 package restores full functionality. n.b. Possible duplicate of LP:2036348 - I am not in a position to confirm those symptoms yet, but will update later. Running mantic pre-release on amd64: $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024443] Re: pi-kernel 5.15 on UC22 is missing most staging modules
** Description changed: - i recently recommended a TP-Link TL-WN722N to an UbuntuCore customer + [Impact] + + I recently recommended a TP-Link TL-WN722N to an UbuntuCore customer asking for a recommendation of a USB wifi adapter with external antenna for the RPi since i use this card in various RPi projects ... trying it on UC22 it turns out that the module driving this card is not included in the pi-kernel snap. in fact the staging dir seems to mostly be empty ... the same kernel on classic includes the needed r8188eu.ko module via the linux-modules-extra package. it seems like we do not include linux-modules-extra in the 5.15 pi- kernel snap at all which is a regression compared to former pi-kernel snaps where this wifi card works fine. + + [Fix] + + Move r8188eu module to linux-modules so that it ends up in the pi-kernel + snap. + + [Test Case] + + Check pi-kernel snap content. + + [Where Problems Could Occur] + + Machines that have a USB NIC that needs this driver -> kernel crashes, + stack traces, ... ** Also affects: linux-raspi (Ubuntu Mantic) Importance: Undecided Status: Confirmed ** Also affects: linux-raspi (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2024443 Title: pi-kernel 5.15 on UC22 is missing most staging modules Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Jammy: New Status in linux-raspi source package in Lunar: New Status in linux-raspi source package in Mantic: Confirmed Bug description: [Impact] I recently recommended a TP-Link TL-WN722N to an UbuntuCore customer asking for a recommendation of a USB wifi adapter with external antenna for the RPi since i use this card in various RPi projects ... trying it on UC22 it turns out that the module driving this card is not included in the pi-kernel snap. in fact the staging dir seems to mostly be empty ... the same kernel on classic includes the needed r8188eu.ko module via the linux-modules-extra package. it seems like we do not include linux-modules-extra in the 5.15 pi- kernel snap at all which is a regression compared to former pi-kernel snaps where this wifi card works fine. [Fix] Move r8188eu module to linux-modules so that it ends up in the pi- kernel snap. [Test Case] Check pi-kernel snap content. [Where Problems Could Occur] Machines that have a USB NIC that needs this driver -> kernel crashes, stack traces, ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2024443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035285] Re: nft cannot load certain rulesets after kernel upgrade
I have prepared an nftables upload for lunar in the ubuntu-security-
proposed ppa https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/ for people to test and confirm that it
addresses the issue; additional work needs to be done for jammy as
naively applying the commits results in an nft that segfaults on the
0041chain_binding_0 testcase.
--
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/2035285
Title:
nft cannot load certain rulesets after kernel upgrade
Status in linux package in Ubuntu:
Won't Fix
Status in nftables package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in nftables source package in Jammy:
New
Status in linux source package in Lunar:
Won't Fix
Status in nftables source package in Lunar:
New
Bug description:
[Impact]
After kernel fixes for CVE-2023-4147/CVE-2023-3995 were applied, the kernel
nftables module does not accept certain bogus rules that were built by the nft
tool. A fix for nft was provided to produce rules as now expected by the kernel.
[Test case]
Running nftables testcase 0041chain_binding_0 on linux-5.15.0-83-generic or
linux-6.2.0-32-generic will will show the following error:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
W: [FAILED] ./testcases/chains/0041chain_binding_0: got 1
/dev/stdin:5:25-95: Error: Could not process rule: Operation not supported
ip saddr { 127.0.0.0/8, 172.23.0.0/16,
192.168.13.0/24 } counter accept
^^^
/dev/stdin:6:25-56: Error: Could not process rule: Operation not supported
ip6 saddr ::1/128 counter accept
I: results: [OK] 0 [FAILED] 1 [TOTAL] 1
The expected result is:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
I: [OK] ./testcases/chains/0041chain_binding_0
I: results: [OK] 1 [FAILED] 0 [TOTAL] 1
Another test case is trying to run nft -f test.nft with the following
contents on test.nft:
#!/usr/sbin/nft -f
flush ruleset
table inet filter {
chain PREROUTING_RAW {
type filter hook prerouting priority raw;
tcp flags syn jump {
tcp option maxseg size 1-500 counter drop
tcp sport 0 counter drop
}
rt type 0 counter drop
}
}
A broken nft will produce:
./test.nft:10:4-44: Error: Could not process rule: Operation not supported
tcp option maxseg size 1-500 counter drop
^
./test.nft:11:4-27: Error: Could not process rule: Operation not supported
tcp sport 0 counter drop
A fixed nft will produce no output, but a following 'nft list ruleset'
command will show:
table inet filter {
chain PREROUTING_RAW {
type filter hook prerouting priority raw; policy accept;
tcp flags syn jump {
tcp option maxseg size 1-500 counter packets 0 bytes
0 drop
tcp sport 0 counter packets 0 bytes 0 drop
}
rt type 0 counter packets 0 bytes 0 drop
}
}
[Potential regressions]
Users rulesets may fail to load or produce incorrect results, like allowing
or denying certain packages in their firewall, for example.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035285/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
I can confirm that it works! <:D -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036587] Re: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals
** Patch added: "0001-UBUNTU-Config-Enable-CONFIG_MTK_IOMMU.patch" https://bugs.launchpad.net/ubuntu/+source/lunar/+bug/2036587/+attachment/5701966/+files/0001-UBUNTU-Config-Enable-CONFIG_MTK_IOMMU.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036587 Title: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals Status in linux package in Ubuntu: Incomplete Status in lunar package in Ubuntu: New Bug description: [Impact] IOMMU related peripherals cannot work. [Fix] The CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. CONFIG_MTK_IOMMU=m [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/2036587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032164] Re: A general-proteciton exception during guest migration to unsupported PKRU machine
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High -- 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/2032164 Title: A general-proteciton exception during guest migration to unsupported PKRU machine Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] When a host that supports PKRU initiates a guest that lacks PKRU support, the flag is enabled on the guest's fpstate. This information is then passed to userspace through the vcpu ioctl KVM_GET_XSAVE. However, a problem arises when the user opts to migrate the mentioned guest to another machine that does not support PKRU. In this scenario, the new host attempts to restore the guest's fpu registers. Nevertheless, due to the absence of PKRU support on the new host, a general-protection exception takes place, leading to a guest crash. [Fix] The problem is resolved by the following upstream commit: ad856280ddea x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 Additionally, a subsequent fix tackles the migration problem stemming from the earlier commit: a1020a25e697 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES [Test Plan] 1. Set up two machines: one with PKRU support and the other without. 2. Initiate a guest that lacks PKRU support on the machine with PKRU support. 3. Utilize libvirt to migrate the aforementioned guest to a different machine that lacks PKRU support. 4. The error emerges on the destination machine: KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=86cf7970 EBX= ECX=0001 EDX=005b0036 ESI=0087 EDI=0087 EBP=87c03e38 ESP=87c03e18 EIP=86cf7d5e EFL=0246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2023-07-09T03:03:14.911750Z qemu-system-x86_64: terminating on signal 15 from pid 4134 (/usr/sbin/libvirtd) 2023-07-09 03:03:15.312+: shutting down, reason=destroyed [Where problems could occur] The introduced commits will impact the guest migration process, potentially leading to failures and preventing the guest from operating successfully on the migration destination. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
Workaround proposed: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3291 -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036428] Re: Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1
** Tags added: mantic -- 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/2036428 Title: Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1 Status in linux-firmware package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware to 20230915.gitdfa11466-0ubuntu1, my Intel AX201 Bluetooth controller is not available post-reboot. The device itself shows up here: $ lsusb | grep -i blue Bus 003 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth But running e.g. `dmesg | grep -i bluetooth` returns no matches, and bluetoothctl finds no controllers. Reverting to the 20230323.gitbcdcfbcf-0ubuntu1.6 package restores full functionality. n.b. Possible duplicate of LP:2036348 - I am not in a position to confirm those symptoms yet, but will update later. Running mantic pre-release on amd64: $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036580] Re: [Lenovo ThinkPad X1 Carbon Gen 8] Bluetooth won't turn on after upgrade to 23.10
*** This bug is a duplicate of bug 2036428 ***
https://bugs.launchpad.net/bugs/2036428
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2036428, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** This bug has been marked a duplicate of bug 2036428
Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1
--
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/2036580
Title:
[Lenovo ThinkPad X1 Carbon Gen 8] Bluetooth won't turn on after
upgrade to 23.10
Status in linux package in Ubuntu:
New
Status in linux-firmware package in Ubuntu:
New
Bug description:
After upgrading from Ubuntu 23.04 to 23.10, Bluetooth won't turn on. I
click on the Unity gear wheel icon, then click on System Settings,
then on Bluetooth. The "Bluetooth" toggle is set to off, and the box
on the left says "Bluetooth is disabled". Clicking the toggle turns
the toggle on, but nothing else changes. The box on the left still
says that Bluetooth is disabled, and no Bluetooth icon shows on the
menu bar despite "Show Bluetooth status in the menu bar" being
enabled.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluetooth 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Sep 19 11:20:23 2023
InstallationDate: Installed on 2020-07-14 (1162 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro loglevel=4 splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to mantic on 2023-09-16 (3 days ago)
dmi.bios.date: 08/30/2022
dmi.bios.release: 1.28
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET38W (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 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.15
dmi.modalias:
dmi:bvnLENOVO:bvrN2WET38W(1.28):bd08/30/2022:br1.28:efr1.15:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:55 acl:0 sco:0 events:4 errors:0
TX bytes:15 acl:0 sco:0 commands:4 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036580/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036580] Re: Bluetooth won't turn on after upgrade to 23.10
*** This bug is a duplicate of bug 2036428 ***
https://bugs.launchpad.net/bugs/2036428
Looks like kernel 6.5 is missing required firmware?
[ 38.846558] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 38.846638] Bluetooth: hci0: Failed to load Intel firmware file
intel/ibt-19-0-4.sfi (-2)
[ 38.847516] Bluetooth: hci0: Reading supported features failed (-56)
[ 38.847533] Bluetooth: hci0: Error reading debug features
[ 38.848512] Bluetooth: hci0: Failed to read MSFT supported features (-56)
** Package changed: bluez (Ubuntu) => linux (Ubuntu)
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Bluetooth won't turn on after upgrade to 23.10
+ [Lenovo ThinkPad X1 Carbon Gen 8] Bluetooth won't turn on after upgrade to
23.10
--
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/2036580
Title:
[Lenovo ThinkPad X1 Carbon Gen 8] Bluetooth won't turn on after
upgrade to 23.10
Status in linux package in Ubuntu:
New
Status in linux-firmware package in Ubuntu:
New
Bug description:
After upgrading from Ubuntu 23.04 to 23.10, Bluetooth won't turn on. I
click on the Unity gear wheel icon, then click on System Settings,
then on Bluetooth. The "Bluetooth" toggle is set to off, and the box
on the left says "Bluetooth is disabled". Clicking the toggle turns
the toggle on, but nothing else changes. The box on the left still
says that Bluetooth is disabled, and no Bluetooth icon shows on the
menu bar despite "Show Bluetooth status in the menu bar" being
enabled.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluetooth 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Sep 19 11:20:23 2023
InstallationDate: Installed on 2020-07-14 (1162 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro loglevel=4 splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to mantic on 2023-09-16 (3 days ago)
dmi.bios.date: 08/30/2022
dmi.bios.release: 1.28
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET38W (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 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.15
dmi.modalias:
dmi:bvnLENOVO:bvrN2WET38W(1.28):bd08/30/2022:br1.28:efr1.15:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:55 acl:0 sco:0 events:4 errors:0
TX bytes:15 acl:0 sco:0 commands:4 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036580/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036587] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2036587 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036587 Title: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals Status in linux package in Ubuntu: Incomplete Status in lunar package in Ubuntu: New Bug description: [Impact] IOMMU related peripherals cannot work. [Fix] The CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. CONFIG_MTK_IOMMU=m [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/2036587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
** Changed in: xwayland (Ubuntu) Status: Confirmed => Opinion ** No longer affects: xwayland (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
450-server drop in mantic needs lrm respin to drop it ** Summary changed: - RM: mantic nvidia-graphics-drivers-390 - Remove from the archive, unmaintained upstream + RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers ** Description changed: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. + + Similarly 418-server and 450-server are also EOL and unsupported. ** Also affects: nvidia-graphics-drivers-418-server (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-450-server (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450-server package in Ubuntu: Incomplete Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2036577 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: New 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 2036577] Re: [Mediatek] mt8195-demo: Fix hardware watchdog reset at boot time around 10 sec.
** Patch added: "patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036577/+attachment/5701947/+files/0001-UBUNTU-Config-Enable-CONFIG_MEDIATEK_WATCHDOG.patch ** Description changed: + [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. -- 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: New 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 2036580] [NEW] Bluetooth won't turn on after upgrade to 23.10
Public bug reported:
After upgrading from Ubuntu 23.04 to 23.10, Bluetooth won't turn on. I
click on the Unity gear wheel icon, then click on System Settings, then
on Bluetooth. The "Bluetooth" toggle is set to off, and the box on the
left says "Bluetooth is disabled". Clicking the toggle turns the toggle
on, but nothing else changes. The box on the left still says that
Bluetooth is disabled, and no Bluetooth icon shows on the menu bar
despite "Show Bluetooth status in the menu bar" being enabled.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluetooth 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Sep 19 11:20:23 2023
InstallationDate: Installed on 2020-07-14 (1162 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro loglevel=4 splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to mantic on 2023-09-16 (3 days ago)
dmi.bios.date: 08/30/2022
dmi.bios.release: 1.28
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET38W (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 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.15
dmi.modalias:
dmi:bvnLENOVO:bvrN2WET38W(1.28):bd08/30/2022:br1.28:efr1.15:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:55 acl:0 sco:0 events:4 errors:0
TX bytes:15 acl:0 sco:0 commands:4 errors:0
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2036580
Title:
Bluetooth won't turn on after upgrade to 23.10
Status in bluez package in Ubuntu:
New
Bug description:
After upgrading from Ubuntu 23.04 to 23.10, Bluetooth won't turn on. I
click on the Unity gear wheel icon, then click on System Settings,
then on Bluetooth. The "Bluetooth" toggle is set to off, and the box
on the left says "Bluetooth is disabled". Clicking the toggle turns
the toggle on, but nothing else changes. The box on the left still
says that Bluetooth is disabled, and no Bluetooth icon shows on the
menu bar despite "Show Bluetooth status in the menu bar" being
enabled.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluetooth 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Sep 19 11:20:23 2023
InstallationDate: Installed on 2020-07-14 (1162 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro loglevel=4 splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to mantic on 2023-09-16 (3 days ago)
dmi.bios.date: 08/30/2022
dmi.bios.release: 1.28
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET38W (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 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.15
dmi.modalias:
dmi:bvnLENOVO:bvrN2WET38W(1.28):bd08/30/2022:br1.28:efr1.15:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
hciconfig:
hci0:
[Kernel-packages] [Bug 2036587] [NEW] [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals
Public bug reported: [Impact] IOMMU related peripherals cannot work. [Fix] The CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. CONFIG_MTK_IOMMU=m [Other info] effected kernel (5.19~latest) ubuntu kernel for lunar, Kinetic, and Mantic. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: lunar (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] IOMMU related peripherals cannot work. [Fix] - The CONFIG_MEDIATEK_IOMMU should be enabled as "module" in generic kernel settings. + The CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. - CONFIG_MEDIATEK_IOMMU=m + CONFIG_MTK_IOMMU=m [Other info] effected kernel (5.19~latest) ubuntu kernel for lunar, Kinetic, and Mantic. ** Also affects: lunar (Ubuntu) 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/2036587 Title: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals Status in linux package in Ubuntu: New Status in lunar package in Ubuntu: New Bug description: [Impact] IOMMU related peripherals cannot work. [Fix] The CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. CONFIG_MTK_IOMMU=m [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/2036587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/-/issues/1579 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035390] Re: kvm-amd crashes when loaded at svm_init
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035390 Title: kvm-amd crashes when loaded at svm_init Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Loading kvm-amd crashes at svm_init preventing the use of KVM on AMD systems. [Test case] Load kvm_amd and start a KVM guest. [Potential regression] KVM initialization may be broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036281] Re: activate bpf LSM by default
Adding BPF LSM by default will cause memory and CPU impact to all users. Right now, it is possible to add this by changing the kernel boot command line parameters. What is the justification to change the default? Another distro enabling it does not justify it. And one unknown software using it does not justify it. For this latter case, there is the command line option for the unknown number of users of that software. If there is a compelling reason to add it as a default, it will be evaluated, but I don't see that compelling reason now. Would you be able to share why you want the default to be changed? Thank you. Cascardo. -- 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/2036281 Title: activate bpf LSM by default Status in linux package in Ubuntu: Incomplete Bug description: in Fedora/RHEL if I want to see if the bpf LSM is active/available in the kernel I can go here: [root@virtualrocky]# cat /sys/kernel/security/lsm lockdown,capability,yama,selinux,bpf[root@virtualrocky]# but if I do the same thing in Ubuntu 22.0.4 bpf is NOT there: root@virtual-ubuntu2204:/# cat /sys/kernel/security/lsm lockdown,capability,landlock,yama,apparmorroot@virtual-ubuntu2204:/# Please add bpf LSM to the CONFIG_LSM See discourse for background info https://discourse.ubuntu.com/t/ask-us-anything-about-ubuntu- kernels/27664/127?u=why2jjj root@virtual-ubuntu2204:/opt/# cat /proc/version_signature Ubuntu 5.15.0-82.91-generic 5.15.111 THANK YOU! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfreyensee 2526 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-08-29 (17 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) MachineType: Parallels Software International Inc. Parallels Virtual Platform NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-82-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-82-generic N/A linux-backports-modules-5.15.0-82-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-82-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/03/2023 dmi.bios.release: 18.3 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 18.3.2 (53621) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 2 dmi.chassis.vendor: Parallels Software International Inc. dmi.ec.firmware.release: 18.3 dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr18.3.2(53621):bd07/03/2023:br18.3:efr18.3:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct2:cvr:skuUndefined: dmi.product.family: Parallels VM dmi.product.name: Parallels Virtual Platform dmi.product.sku: Undefined dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036281] Re: activate bpf LSM by default
> That is at least one less uncomfortable conversation a sw company has with a potential customer why their server needs to be rebooted for the company’s SW solution to use a Linux driver. What software is it? From which company? Is it proprietary or open source? Can we try and see if it works on Ubuntu? ** 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/2036281 Title: activate bpf LSM by default Status in linux package in Ubuntu: Incomplete Bug description: in Fedora/RHEL if I want to see if the bpf LSM is active/available in the kernel I can go here: [root@virtualrocky]# cat /sys/kernel/security/lsm lockdown,capability,yama,selinux,bpf[root@virtualrocky]# but if I do the same thing in Ubuntu 22.0.4 bpf is NOT there: root@virtual-ubuntu2204:/# cat /sys/kernel/security/lsm lockdown,capability,landlock,yama,apparmorroot@virtual-ubuntu2204:/# Please add bpf LSM to the CONFIG_LSM See discourse for background info https://discourse.ubuntu.com/t/ask-us-anything-about-ubuntu- kernels/27664/127?u=why2jjj root@virtual-ubuntu2204:/opt/# cat /proc/version_signature Ubuntu 5.15.0-82.91-generic 5.15.111 THANK YOU! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfreyensee 2526 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-08-29 (17 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) MachineType: Parallels Software International Inc. Parallels Virtual Platform NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-82-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-82-generic N/A linux-backports-modules-5.15.0-82-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-82-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/03/2023 dmi.bios.release: 18.3 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 18.3.2 (53621) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 2 dmi.chassis.vendor: Parallels Software International Inc. dmi.ec.firmware.release: 18.3 dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr18.3.2(53621):bd07/03/2023:br18.3:efr18.3:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct2:cvr:skuUndefined: dmi.product.family: Parallels VM dmi.product.name: Parallels Virtual Platform dmi.product.sku: Undefined dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036550] Re: ubantu 5.15.0-83 kernel version :smpboot:do_boot_cpu failed(-1) to wakeup cpu #1
log file ** Attachment added: "[Com COM4] (2023-08-29_142219).log" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2036550/+attachment/5701945/+files/%5BCom%20COM4%5D%20%282023-08-29_142219%29.log ** Description changed: - 1.update kernel to 5.15.0-83 + 1.update kernel to 5.15.0-83(hwe kernel) 2.do server ac reboot 500 times 3.issue reproduce the boot failed reason is as follows: [ 38.236757] smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 [ 38.664758]#2 [ 41.560757] [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 4 APIC: 2 [ 54.356758]#3 [ 60.884756] [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 6 APIC: 4 [ 73.704758]#4 [ 74.708757] [Firmware Bug]: CPU4: APIC id mismatch. Firmware: 8 APIC: 6 [ 87.880758]#5 [ 93.684757] [Firmware Bug]: CPU5: APIC id mismatch. Firmware: a APIC: 8 [ [ 105.476756] BUG: unable to handle page fault for address: 0011 ** Package changed: subiquity (Ubuntu) => linux-hwe (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/2036550 Title: ubantu 5.15.0-83 kernel version :smpboot:do_boot_cpu failed(-1) to wakeup cpu #1 Status in linux-hwe package in Ubuntu: New Bug description: 1.update kernel to 5.15.0-83(hwe kernel) 2.do server ac reboot 500 times 3.issue reproduce the boot failed reason is as follows: [ 38.236757] smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 [ 38.664758]#2 [ 41.560757] [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 4 APIC: 2 [ 54.356758]#3 [ 60.884756] [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 6 APIC: 4 [ 73.704758]#4 [ 74.708757] [Firmware Bug]: CPU4: APIC id mismatch. Firmware: 8 APIC: 6 [ 87.880758]#5 [ 93.684757] [Firmware Bug]: CPU5: APIC id mismatch. Firmware: a APIC: 8 [ [ 105.476756] BUG: unable to handle page fault for address: 0011 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2036550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] [NEW] [Mediatek] mt8195-demo: Fix hardware watchdog reset at boot time around 10 sec.
Public bug reported: 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. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: lunar (Ubuntu) Importance: Undecided Status: New ** Also affects: lunar (Ubuntu) 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/2036577 Title: [Mediatek] mt8195-demo: Fix hardware watchdog reset at boot time around 10 sec. Status in linux package in Ubuntu: New Status in lunar package in Ubuntu: New Bug description: 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. 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 2035189] Re: Remove from the archive, unmaintained upstream
No LRMs build this driver in mantic and it can be safely removed from the archive. ** Summary changed: - Remove from the archive, unmaintained upstream + RM: mantic nvidia-graphics-drivers-390 - Remove from the archive, unmaintained upstream ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: mantic nvidia-graphics-drivers-390 - Remove from the archive, unmaintained upstream Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in xwayland package in Ubuntu: Confirmed Bug description: I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: Remove from the archive, unmaintained upstream
I thought 390 is so obsolete, that everyone has migrated to newer ones if their card supports it. Thus simply removing it, is best. Upon upgrade it will be offered to be removed from disk as an obsolete package. Eventually 6.5+ based jammy kernels will not have it in lrm either. And we will only keep it against older kernels in bionic..jammy (ga only), if we can and stable updates don't conflict. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: mantic nvidia-graphics-drivers-390 - Remove from the archive, unmaintained upstream Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036550] [NEW] ubantu 5.15.0-83 kernel version :smpboot:do_boot_cpu failed(-1) to wakeup cpu #1
You have been subscribed to a public bug: 1.update kernel to 5.15.0-83(hwe kernel) 2.do server ac reboot 500 times 3.issue reproduce the boot failed reason is as follows: [ 38.236757] smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 [ 38.664758]#2 [ 41.560757] [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 4 APIC: 2 [ 54.356758]#3 [ 60.884756] [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 6 APIC: 4 [ 73.704758]#4 [ 74.708757] [Firmware Bug]: CPU4: APIC id mismatch. Firmware: 8 APIC: 6 [ 87.880758]#5 [ 93.684757] [Firmware Bug]: CPU5: APIC id mismatch. Firmware: a APIC: 8 [ [ 105.476756] BUG: unable to handle page fault for address: 0011 ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New -- ubantu 5.15.0-83 kernel version :smpboot:do_boot_cpu failed(-1) to wakeup cpu #1 https://bugs.launchpad.net/bugs/2036550 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032704] Re: Fix panel brightness issues on HP laptops
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1022.22 --- linux-oem-6.1 (6.1.0-1022.22) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1022.22 -proposed tracker (LP: #2034205) * amdgpu: Fixes for S0i3 resume on Phoenix (LP: #2033654) - drm/amd/pm: skip the RLC stop when S0i3 suspend for SMU v13.0.4/11 - drm/amdgpu: skip fence GFX interrupts disable/enable for S0ix - drm/amd: flush any delayed gfxoff on suspend entry * CVE-2023-20588 - x86/bugs: Increase the x86 bugs vector size to two u32s - x86/CPU/AMD: Do not leak quotient data after a division by 0 - x86/CPU/AMD: Fix the DIV(0) initial fix attempt * CVE-2023-4569 - netfilter: nf_tables: deactivate catchall elements in next generation * stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) (LP: #2016398) - SAUCE: overlayfs: fix reference count mismatch * Fix blank display when Thunderbolt monitor is plugged second time (LP: #2034491) - thunderbolt: Fix Thunderbolt 3 display flickering issue on 2nd hot plug onwards - thunderbolt: Fix a backport error for display flickering issue * Enable D3cold at s2idle for Intel DG2 GPU (LP: #2033452) - drm/i915/dgfx: Enable d3cold at s2idle * Fix numerous AER related issues (LP: #2033025) - SAUCE: PCI/AER: Disable AER service during suspend, again - SAUCE: PCI/DPC: Disable DPC service during suspend, again * Fix ACPI TAD on some Intel based systems (LP: #2032767) - ACPI: TAD: Install SystemCMOS address space handler for ACPI000E * Fix panel brightness issues on HP laptops (LP: #2032704) - ACPI: video: Put ACPI video and its child devices into D0 on boot * Resync CI Runner Configuration (LP: #2024199) - [CI] resync ci configuration -- Timo Aaltonen Wed, 06 Sep 2023 10:02:26 +0300 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-20588 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4569 -- 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/2032704 Title: Fix panel brightness issues on HP laptops 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 Committed 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.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Brightness can't be changed or can only be changed once on some modern HP laptops. [Fix] BIOS folks identified the issue where the ACPI _PS0 method isn't called for the panel device. On Windows the method is being invoked. This is due to missing _PSC, but since Windows is the de facto spec, we have to perform the same to make the device functional. [Test] Once the fix is applied, the brightness can be changed smoothly. [Where problems could occur] According to BIOS folks, Windows also invokes _PS3 for sleep and shutdown, we need to tackle that in the future. Right now not calling _PS3 has no ill-effect, per BIOS folks. X-HWE-Bug: Bug #2032704 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
