[Kernel-packages] [Bug 2031289] Re: amdgpu driver crash: ring gfx_0.0.0 timeout
Four days later, no crash yet. Left the machine on over the weekend, and I see no crashes in the amdgpu driver. So it looks like the newer firmware seems to be better for me. -- 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/2031289 Title: amdgpu driver crash: ring gfx_0.0.0 timeout Status in linux package in Ubuntu: Confirmed Bug description: ThinkPad Z13 with 3 displays connected. Using Ubuntu 23.04 with 6.2.0-26-generic, the graphical desktop locks or crashes. dmesg has the following error: [Mon Aug 14 08:06:06 2023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=5346515, emitted seq=5346517 [Mon Aug 14 08:06:06 2023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 3456 thread Xorg:cs0 pid 3464 [Mon Aug 14 08:06:06 2023] amdgpu :63:00.0: amdgpu: GPU reset begin! This happens every few days, and I either have to restart the desktop or the entire computer. Today it happened at 08:06 when I wasn't at the machine doing anything. But many applications were still running, as I left it on Friday. I have two external displays attached via a USB type C hub. alan@ziggy:~$ xrandr | grep -B2 "*" eDP connected 1920x1200+0+0 (normal left inverted right x axis y axis) 289mm x 186mm 2880x1800 60.00 + 1920x1200 60.00* -- DisplayPort-6 disconnected (normal left inverted right x axis y axis) DisplayPort-7 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 527mm x 296mm 1920x1080 60.00*+ 50.0059.94 -- 720x400 70.08 DisplayPort-8 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 527mm x 296mm 1920x1080 60.00*+ 50.0059.94 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 08:57:10 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (373 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 MachineType: LENOVO 21D2CTO1WW ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=96c77f27-d90f-4d14-a5d5-59ac57b3f6dc ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-01-02 (223 days ago) dmi.bios.date: 12/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: N3GET47W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D2CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.54 dmi.modalias: dmi:bvnLENOVO:bvrN3GET47W(1.27):bd12/08/2022:br1.27:efr1.54:svnLENOVO:pn21D2CTO1WW:pvrThinkPadZ13Gen1:rvnLENOVO:rn21D2CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21D2_BU_Think_FM_ThinkPadZ13Gen1: dmi.product.family: ThinkPad Z13 Gen 1 dmi.product.name: 21D2CTO1WW dmi.product.sku: LENOVO_MT_21D2_BU_Think_FM_ThinkPad Z13 Gen 1 dmi.product.version: ThinkPad Z13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Can you post the logs from a failed boot? $ sudo journalctl -l -b 0 -- 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 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
No its not new, its a 2022 model, 12 gen has been replaced by 13th gen. Its definitely a software issue introduced in a software update to either thermald or the layer in the kernel it interacts with directly. (There is the group that makes the Linux hardware drivers for Razer products - I think I mentioned that the issues occur whether those are present or not - that we could loop in. They might understand the power level interaction here?) It seems to me like a bug where thermald sets a low power target with whatever knobs it has, but then doesn't understand the system has recovered and it needs to reset. What data is it waiting on? Another value from the bios? Is it possible the "all good" signal came in/is-processed out-of-order? (is this even interrupt driven or does it periodically read values? Fwiw I would be interested diving into thermal myself, its just not my everyday language. (And I've not done this level of direct hardware work before.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running
[Kernel-packages] [Bug 2036368] Re: Machine is not shutting down due to a kernel issue
Co-worker of mine has the same machine running the same kernel (6.2.0-32-generic) and said everything is fine with his, so this will probably be difficult to replicate... -- 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/2036368 Title: Machine is not shutting down due to a kernel issue Status in linux-hwe-6.2 package in Ubuntu: New Bug description: My Dell Precision 5570 hangs on restart, shutdown, and hibernate. I'm running Ubuntu 22.04.3 LTS and have full disk encryption (not sure if that's relevant). I asked a couple of questions on Ask Ubuntu, but didn't get anything useful. Here they are: https://askubuntu.com/questions/1483865/suspend-not-working-ubuntu-22-04 https://askubuntu.com/questions/1484374/restarting-freezes-due-to-snap It seems related to https://bugs.launchpad.net/ubuntu/+source/finalrd/+bug/1905166 but after some digging around, I think it might be kernel related. 6.2.0-31-generic and 6.2.0-32-generic exhibit the problem, but 5.19.0-50-generic does not - when I load that version of the kernel the machine shuts down just fine. I haven't tried running a newer kernel yet. I was going to file a bug report on kernel.org but they advise to file it with the distro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036368/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036368] [NEW] Machine is not shutting down due to a kernel issue
You have been subscribed to a public bug: My Dell Precision 5570 hangs on restart, shutdown, and hibernate. I'm running Ubuntu 22.04.3 LTS and have full disk encryption (not sure if that's relevant). I asked a couple of questions on Ask Ubuntu, but didn't get anything useful. Here they are: https://askubuntu.com/questions/1483865/suspend-not-working-ubuntu-22-04 https://askubuntu.com/questions/1484374/restarting-freezes-due-to-snap It seems related to https://bugs.launchpad.net/ubuntu/+source/finalrd/+bug/1905166 but after some digging around, I think it might be kernel related. 6.2.0-31-generic and 6.2.0-32-generic exhibit the problem, but 5.19.0-50-generic does not - when I load that version of the kernel the machine shuts down just fine. I haven't tried running a newer kernel yet. I was going to file a bug report on kernel.org but they advise to file it with the distro. ** Affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Machine is not shutting down due to a kernel issue https://bugs.launchpad.net/bugs/2036368 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 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 2036339] Re: Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6)
dpkg -l | grep linux- ii binutils-x86-64-linux-gnu 2.40-2ubuntu4.1 amd64GNU binary utilities, for x86-64-linux-gnu target ii ladspa-sdk 1.17-1 amd64sample tools for linux-audio-dev plugin architecture ii linux-base 4.5ubuntu9 all Linux image base package iF linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.6 all Firmware for Linux kernel drivers ii linux-firmware-nonfree 1.16 all Non-free firmware for Linux kernel drivers ii linux-headers-6.2.0-31 6.2.0-31.31 all Header files related to Linux kernel version 6.2.0 ii linux-headers-6.2.0-31-generic 6.2.0-31.31 amd64Linux kernel headers for version 6.2.0 on 64 bit x86 SMP ii linux-headers-6.2.0-32 6.2.0-32.32 all Header files related to Linux kernel version 6.2.0 ii linux-headers-6.2.0-32-generic 6.2.0-32.32 amd64Linux kernel headers for version 6.2.0 on 64 bit x86 SMP ii linux-headers-generic 6.2.0.32.32 amd64Generic Linux kernel headers ic linux-image-6.2.0-25-generic6.2.0-25.25 amd64Signed kernel image generic ic linux-image-6.2.0-26-generic6.2.0-26.26 amd64Signed kernel image generic rc linux-image-6.2.0-27-generic6.2.0-27.28 amd64Signed kernel image generic ii linux-image-6.2.0-31-generic6.2.0-31.31 amd64Signed kernel image generic ii linux-image-6.2.0-32-generic6.2.0-32.32 amd64Signed kernel image generic ii linux-libc-dev:amd646.2.0-32.32 amd64Linux Kernel Headers for development ii linux-libc-dev:i386 6.2.0-32.32 i386 Linux Kernel Headers for development rc linux-modules-5.11.0-17-generic 5.11.0-17.18 amd64Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP rc linux-modules-5.11.0-18-generic 5.11.0-18.19 amd64Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP rc linux-modules-5.11.0-25-generic 5.11.0-25.27 amd64Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP rc linux-modules-5.11.0-31-generic 5.11.0-31.33 amd64Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP rc linux-modules-5.11.0-34-generic 5.11.0-34.36 amd64Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP rc linux-modules-5.11.0-36-generic 5.11.0-36.40 amd64Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP rc linux-modules-5.11.0-37-generic 5.11.0-37.41 amd64Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP rc linux-modules-5.13.0-19-generic 5.13.0-19.19 amd64Linux kernel extra modules for version 5.13.0 on 64 bit x86 SMP rc linux-modules-5.13.0-20-generic 5.13.0-20.20 amd64Linux kernel extra modules for version 5.13.0 on 64 bit x86 SMP rc linux-modules-5.13.0-21-generic 5.13.0-21.21 amd64Linux kernel extra modules for version 5.13.0 on 64 bit x86 SMP rc linux-modules-5.13.0-22-generic 5.13.0-22.22
[Kernel-packages] [Bug 2036339] Re: Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6) "SOLVED"
One more thing, what's the output of 'linux-version list'? ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Invalid -- 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/2036339 Title: Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6) "SOLVED" Status in linux-firmware package in Ubuntu: Invalid Bug description: O.S.: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.6 Trying to install the package above, I receive these errors: Configuring linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6)... update-initramfs: Generating /boot/initrd.img-6.2.0-32-generic update-initramfs: Generating /boot/initrd.img-6.2.0-31-generic update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic grep: /boot/config-6.2.0-24-generic: No such file or directory W: zstd compression (CONFIG_RD_ZSTD) not supported by the kernel, using gzip grep: /boot/config-6.2.0-24-generic: No such file or directory E: gzip compression (CONFIG_RD_GZIP) not supported by the kernel update-initramfs: failed for /boot/initrd.img-6.2.0-24-generic with exit code 1 dpkg: error processing package linux-firmware (--configure): subprocess installed linux-firmware package post-installation script returned error status 1 Errors were encountered while processing: linux-firmware E: Sub-process /usr/bin/dpkg returned an error code (1) I tried to uninstall the package with sudo apt remove --purge linux-firmware and then reinstall it, but without success. Same result when trying installing older packages 20230323.gitbcdcfbcf-0ubuntu1.2 and 20230323.gitbcdcfbcf-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] [NEW] Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1
Public bug reported: 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 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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: New 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 2036437] [NEW] switch selftest validation to kexec
Public bug reported: patch kexec code to validate the signature on the vmlinuz instead of using hmac. this will eliminate need for kcapi tools certification. ** 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/2036437 Title: switch selftest validation to kexec Status in linux package in Ubuntu: New Bug description: patch kexec code to validate the signature on the vmlinuz instead of using hmac. this will eliminate need for kcapi tools certification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036438] [NEW] fips certification support initrd less boot
Public bug reported: for fips in clouds it is desired to boot without initrd. add support for doing all the powerup selfchecks from rootfs instead of initrd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036438 Title: fips certification support initrd less boot Status in linux package in Ubuntu: New Bug description: for fips in clouds it is desired to boot without initrd. add support for doing all the powerup selfchecks from rootfs instead of initrd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036436] [NEW] make crypto modules built-in
Public bug reported: make all certified crypto modules built-in this will simplify our security policy by a lot, as well as self tests and validation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036436 Title: make crypto modules built-in Status in linux package in Ubuntu: New Bug description: make all certified crypto modules built-in this will simplify our security policy by a lot, as well as self tests and validation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036434] [NEW] make fips=1 default
Public bug reported: make fips=1 default for kernels built with config_fips ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: fips ** Tags added: fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036434 Title: make fips=1 default Status in linux package in Ubuntu: New Bug description: make fips=1 default for kernels built with config_fips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032535] Re: [Google_Puff] Screen blank crashes system
Hello again. Something strange happened today. The computer booted, and bingwall ran successfully. (normally it hangs from some new interaction with apparmor (I think). Also on this boot, the screen blank went directly from on to off. (Normally it slowly dims the screen before turning it off). In this state the computer did not lock up. I tried letting the screen blank several times and waited a longer time, and it was not locking up. The system was otherwise completely idle. So, I rebooted, and things went back to normal. Bingwall hung (and I killed that process to see if it was bingwall causing the crash) The screen dimmed before going to sleep, and the system crashed. However, before the crash I captured a prevboot-good file to attach along with a prevboot that crashed afterwards. ** Attachment added: "prevboot-good.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032535/+attachment/5701813/+files/prevboot-good.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032535 Title: [Google_Puff] Screen blank crashes system Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 23.04 screen blank crashes system. Not a sleep problem, I can enter and resume from S2idle, S2ram. (Using command line or Power/Suspend GUI) However, when screen blanks, computer has a hard crash. Just rebooting with power button may not work (operating system not found error) I have to unplug the computer and plug it back in again to reboot properly. I would just turn off screen sleep, but when the S2ram suspend mode engages it often, but not always, crashes as well. I've tried live disks with other OS, and this is not a problem on Linux Mint 21.2, nor on Xubuntu 23.04.Windows 10 works too. I tried Ubuntu 22.04 and it also crashed - using either gnome or wayland. I'm happy to help debug, but I'm not a developer. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 21 15:11:21 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] InstallationDate: Installed on 2023-06-13 (69 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Google Noibat ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=77b0ab13-596d-4e94-8648-e6aeda300b7a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2023 dmi.bios.release: 4.20 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.20.0 dmi.board.name: Noibat dmi.board.vendor: HP dmi.board.version: rev4 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.20.0:bd05/15/2023:br4.20:efr0.0:svnGoogle:pnNoibat:pvrrev4:rvnHP:rnNoibat:rvrrev4:cvnGoogle:ct3:cvr:skusku83886080: dmi.product.family: Google_Puff dmi.product.name: Noibat dmi.product.sku: sku83886080 dmi.product.version: rev4 dmi.sys.vendor: Google version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
I can confirm that switching nvidia to on-demand only has resolved all of the performance issues. nvidia being used though prime-run script linked above seems to be working. It is running hotter than I would like, but I have no reason to believe that is unexpected. There are some glitching issues that occur in this setup, specifically, the aspect ratio gets skewed on approximately 50% of the time any application is launched in full screen. When nvidia is set to be the primary GPU, performance is in the toilet. -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 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.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973434/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 2036437] 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 2036437 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/2036437 Title: switch selftest validation to kexec Status in linux package in Ubuntu: Incomplete Bug description: patch kexec code to validate the signature on the vmlinuz instead of using hmac. this will eliminate need for kcapi tools certification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036436] 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 2036436 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/2036436 Title: make crypto modules built-in Status in linux package in Ubuntu: Incomplete Bug description: make all certified crypto modules built-in this will simplify our security policy by a lot, as well as self tests and validation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036434] 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 2036434 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/2036434 Title: make fips=1 default Status in linux package in Ubuntu: Incomplete Bug description: make fips=1 default for kernels built with config_fips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036339] Re: Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6)
"I still don't understand why update-initramfs tries kernel 6.2.0-24 when you don't have that installed." So do I. However I run the command: dpkg --list |grep "^rc" | cut -d " " -f 3 | xargs sudo dpkg --purge purging the residual configurations of all removed packages. I will mark the bug as SOLVED Thank you very much for the support. ** Summary changed: - Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6) + Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6) "SOLVED" -- 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/2036339 Title: Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6) "SOLVED" Status in linux-firmware package in Ubuntu: Incomplete Bug description: O.S.: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.6 Trying to install the package above, I receive these errors: Configuring linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6)... update-initramfs: Generating /boot/initrd.img-6.2.0-32-generic update-initramfs: Generating /boot/initrd.img-6.2.0-31-generic update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic grep: /boot/config-6.2.0-24-generic: No such file or directory W: zstd compression (CONFIG_RD_ZSTD) not supported by the kernel, using gzip grep: /boot/config-6.2.0-24-generic: No such file or directory E: gzip compression (CONFIG_RD_GZIP) not supported by the kernel update-initramfs: failed for /boot/initrd.img-6.2.0-24-generic with exit code 1 dpkg: error processing package linux-firmware (--configure): subprocess installed linux-firmware package post-installation script returned error status 1 Errors were encountered while processing: linux-firmware E: Sub-process /usr/bin/dpkg returned an error code (1) I tried to uninstall the package with sudo apt remove --purge linux-firmware and then reinstall it, but without success. Same result when trying installing older packages 20230323.gitbcdcfbcf-0ubuntu1.2 and 20230323.gitbcdcfbcf-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036438] 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 2036438 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/2036438 Title: fips certification support initrd less boot Status in linux package in Ubuntu: Incomplete Bug description: for fips in clouds it is desired to boot without initrd. add support for doing all the powerup selfchecks from rootfs instead of initrd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032535] Re: [Google_Puff] Screen blank crashes system
Seems I can only attach one file per comment. Attached is the prevboot that crashed from my previous comment. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032535/+attachment/5701814/+files/prevboot.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032535 Title: [Google_Puff] Screen blank crashes system Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 23.04 screen blank crashes system. Not a sleep problem, I can enter and resume from S2idle, S2ram. (Using command line or Power/Suspend GUI) However, when screen blanks, computer has a hard crash. Just rebooting with power button may not work (operating system not found error) I have to unplug the computer and plug it back in again to reboot properly. I would just turn off screen sleep, but when the S2ram suspend mode engages it often, but not always, crashes as well. I've tried live disks with other OS, and this is not a problem on Linux Mint 21.2, nor on Xubuntu 23.04.Windows 10 works too. I tried Ubuntu 22.04 and it also crashed - using either gnome or wayland. I'm happy to help debug, but I'm not a developer. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 21 15:11:21 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] InstallationDate: Installed on 2023-06-13 (69 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Google Noibat ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=77b0ab13-596d-4e94-8648-e6aeda300b7a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2023 dmi.bios.release: 4.20 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.20.0 dmi.board.name: Noibat dmi.board.vendor: HP dmi.board.version: rev4 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.20.0:bd05/15/2023:br4.20:efr0.0:svnGoogle:pnNoibat:pvrrev4:rvnHP:rnNoibat:rvrrev4:cvnGoogle:ct3:cvr:skusku83886080: dmi.product.family: Google_Puff dmi.product.name: Noibat dmi.product.sku: sku83886080 dmi.product.version: rev4 dmi.sys.vendor: Google version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Likely unrelated, but just in case - I do have `COMPRESS=zstd` set in my /etc/initramfs-tools/initramfs.conf. -- 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 2033531] Re: Azure: net: mana: Fix MANA VF unload when hardware is unresponsive
** Tags removed: verification-needed-focal-linux-azure
verification-needed-jammy-linux-azure verification-needed-lunar-linux-azure
** Tags added: verification-done-focal-linux-azure
verification-done-jammy-linux-azure verification-done-lunar-linux-azure
--
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/2033531
Title:
Azure: net: mana: Fix MANA VF unload when hardware is unresponsive
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure source package in Jammy:
Fix Committed
Status in linux-azure source package in Lunar:
Fix Committed
Bug description:
SRU Justification
[Impact]
MSFT has requested to backport commit
a7dfeda6fdeccab4c7c3dce9a72c4262b9530c80 ('net: mana: Fix MANA VF
unload when hardware is unresponsive').
When unloading the MANA driver, mana_dealloc_queues() waits for the MANA
hardware to complete any inflight packets and set the pending send count
to zero. But if the hardware has failed, mana_dealloc_queues()
could wait forever.
[Test Plan]
Microsoft tested. Commit upstream since 6.5
[Regression Potential]
The MANA driver may not shut down correctly.
[Other Info]
SF: #00367140
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2033531/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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
Okay, this does seem to be the same issue as the linked bug. Contents of /lib/firmware/intel with the latest 20230915.gitdfa11466-0ubuntu1 package: https://paste.ubuntu.com/p/ztDgst7wR9/ So mostly .zst compressed files, plus symlinks. Vs this, with the previous 20230323.gitbcdcfbcf-0ubuntu1.6 package: https://paste.ubuntu.com/p/pZH8wFyvxQ/ -- 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 2036339] Re: Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6) "SOLVED"
linux-version list 6.2.0-31-generic 6.2.0-32-generic -- 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/2036339 Title: Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6) "SOLVED" Status in linux-firmware package in Ubuntu: Invalid Bug description: O.S.: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.6 Trying to install the package above, I receive these errors: Configuring linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6)... update-initramfs: Generating /boot/initrd.img-6.2.0-32-generic update-initramfs: Generating /boot/initrd.img-6.2.0-31-generic update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic grep: /boot/config-6.2.0-24-generic: No such file or directory W: zstd compression (CONFIG_RD_ZSTD) not supported by the kernel, using gzip grep: /boot/config-6.2.0-24-generic: No such file or directory E: gzip compression (CONFIG_RD_GZIP) not supported by the kernel update-initramfs: failed for /boot/initrd.img-6.2.0-24-generic with exit code 1 dpkg: error processing package linux-firmware (--configure): subprocess installed linux-firmware package post-installation script returned error status 1 Errors were encountered while processing: linux-firmware E: Sub-process /usr/bin/dpkg returned an error code (1) I tried to uninstall the package with sudo apt remove --purge linux-firmware and then reinstall it, but without success. Same result when trying installing older packages 20230323.gitbcdcfbcf-0ubuntu1.2 and 20230323.gitbcdcfbcf-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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 2034701] Re: unexpected system behaviour after kernel update
I did found a workaround, but iam still convinced that we have a kind of bug. I think i should explain our typical systemsetup, for better understandig. Typical field of application are failoversystems. overall we use very few software and systems have minimal load. we have 2 servers in a cluster realised with pacemaker/corosync. they manage a reource haproxy and a floating ip. We do this with different ubuntu OS, from 18.04 over 20.04 to 22.04 Our systems are bound to Windows Active Director with SSSD (System Security Services Daemon) (https://schroeffu.ch/2019/09/linux-active- directory-ldap-ssh-login-mit-sssd-und-realmd/) so it is possible to Login with our AD Credentials. last component is altiris server management suite agent (former symantec now broadcom) wich is running with root privileges and helps to manage our computerlandscape. And this is where i located the problem. every evening the agent runs a bash script which was wrote by me 3 years ago. it is a small script with 90 lines, it collects some data, mounts a windows fileshare and finally uploads some small files before unmounting the share. nothing special, it takes around 5 seconds to complete, but here seems to be the problem. As i can see every affected server shows in syslog this lines about kernel bug i uploaded on 2023-09-11 (#4) . In some cases there happens something unexpected and triggers this bug. this happens since 5.15.0-83-generic the system gets unstable, high load without running processes, every command takes forever to complete. mostly we had to do a vmware hardstop, because even "reboot -f" failed. i uploaded already some logs. I deactivated this job and the problems disappeared. i was not able to trigger this problem by manual run of the script. as the job was active, every morning we had a bunch of servers in this state between life and death. So i can not confirm a change on our site, i still think about a newly introduced kind of bug. I would like to hear from you, please tell me your opinion to this case. strange that i report a bug with documented kernel error and no one gets back to me. Thanks, Hajo -- 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/2034701 Title: unexpected system behaviour after kernel update Status in linux package in Ubuntu: Confirmed Bug description: Hello, since last kernel updates on ubuntu 20.04 and 22.04 we see lines like this in syslog after boot: Sep 7 13:10:53 myhost kernel: [1.202296] pci :00:15.4: BAR 13: no space for [io size 0x1000] Sep 7 13:10:53 myhost kernel: [1.202387] pci :00:15.4: BAR 13: failed to assign [io size 0x1000] We see this on Ubuntu 20.04 after installing kernel 5.4.0-162-generic and on ubuntu 22.04 after installing kernel 5.15.0-83-generic Since this time we notice some strange server behaviour. - unexpected reboots during workhours - systems hanging/freezing which requires a hardstop of the machine - systems with high load but no significant number of processes, even on non productive machines with usually zero load. We use most of our ubuntu servers as virtual machines in a VMWare Environment with VSphere and ESXi 7.0.3 There were no VMWare updates. I can say this with certainty because iam the responsible person for VMWare too and i did not install any ESXi Updates last days. Other OS not affected as i can see. Thank you, Hans p.s. i wanted to help and wanted to choose fitting package from dropdown " In what package did you find this bug?" above this Inputfield, but it seems that packages like linux-image-5.15.0-83-generic (or similiar i tried somethging...) are unknown and search respondes with improper suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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/142977.html (jammy) * https://lists.ubuntu.com/archives/kernel-team/2023-September/142978.html (mantic) ** Description changed: - TBD. + [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. ** Description changed: [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 + 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. -- 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 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1
By the way, this is fixed in zfs-2.1.7: $ git log -1 fa7d572a8a3298d446fc4f64a263c125c325b7c8 commit fa7d572a8a3298d446fc4f64a263c125c325b7c8 Author: Rich Ercolani <214141+rincebr...@users.noreply.github.com> Date: Tue Nov 15 17:44:12 2022 -0500 Handle and detect #13709's unlock regression (#14161) $ git tag --contains fa7d572a8a3298d446fc4f64a263c125c325b7c8 | sort -V | head -n1 zfs-2.1.7 Jammy is currently (still) at 2.1.5. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1987190 Title: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1 Status in zfs-linux package in Ubuntu: Confirmed Bug description: I have a server that has been running its data volume using ZFS in 20.04 without any problem. The volume is using ZFS encryption and a raidz1-0 configuration. I performed a scrub operations before the upgrade and it did not find any problem. After the reboot for the upgrade, I was welcomed with the following message: status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A The volumes still do not have any checksum error but there are 5 zvols that are not accessible. zpool status displays a line similar to the below for each of the five: errors: Permanent errors have been detected in the following files: tank/data/data:<0x0> I run a scrub and it has not identified any problem but the error messages are not there and the data is still not available. There are 10+ other zvols in the zpool that do not have any kind of problem. I have been unable to identify any correlation between the zvols that are failing. I have seen people reporting similar problems in github after the 20.04 to the 22.04 upgrade (see https://github.com/openzfs/zfs/issues/13763). I wonder how widespread the problem will be as more people upgrades to 22.04. I will try to downgrade the version of zfs in the system and report back ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.4-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Aug 20 22:24:54 2022 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
Some progress reported here: https://asus-linux.org/wiki/cirrus-amps/ -- 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/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all Status in Linux Firmware: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Sound/speakers don't work at all on Asus Zenbook 14 OLED and other similar models with Realtek ALC294. No solution works. Audio is not muted, tried adding snd-hda arguments - no dice. This has been reported numerous times, when will a fix finally be rolled out?! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1730 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 12 13:57:05 2022 InstallationDate: Installed on 2022-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/1981433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
@Eli, may i know it it a brand-new notebook? in the logs, there's one entry to limit your cpu. this is came from bios through ACPI. ~~~ 1694076246][INFO]index 2: type:passive temp:9 hyst:1000 zone id:6 sensor id:6 control_type:1 cdev size:4 ~~~ the cpu temperatrue is 93000 that exceed temp:9, so thermald try to cool the cpu, ~~~ [1694076254][DEBUG]pref 0 type 3 temp 91000 trip 9 [1694076254][DEBUG]Passive Trip point applicable [1694076254][DEBUG]Trip point applicable > 2:9 [1694076254][DEBUG]cdev size for this trippoint 4 [1694076254][DEBUG]cdev at index 27:rapl_controller [1694076254][DEBUG]>>thd_cdev_set_state temperature 9:91000 index:27 state:1 :zone:6 trip_id:2 target_state_valid:0 target_value :0 force:0 min_state:0 max_state:0 ~~~ if this's a brand-new notebook, you should contact the vendor first. if not, we need to investigate further. thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install
[Kernel-packages] [Bug 2036368] Re: Machine is not shutting down due to a kernel issue
** Package changed: ubuntu => linux-hwe-6.2 (Ubuntu) ** Tags added: jammy -- 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/2036368 Title: Machine is not shutting down due to a kernel issue Status in linux-hwe-6.2 package in Ubuntu: New Bug description: My Dell Precision 5570 hangs on restart, shutdown, and hibernate. I'm running Ubuntu 22.04.3 LTS and have full disk encryption (not sure if that's relevant). I asked a couple of questions on Ask Ubuntu, but didn't get anything useful. Here they are: https://askubuntu.com/questions/1483865/suspend-not-working-ubuntu-22-04 https://askubuntu.com/questions/1484374/restarting-freezes-due-to-snap It seems related to https://bugs.launchpad.net/ubuntu/+source/finalrd/+bug/1905166 but after some digging around, I think it might be kernel related. 6.2.0-31-generic and 6.2.0-32-generic exhibit the problem, but 5.19.0-50-generic does not - when I load that version of the kernel the machine shuts down just fine. I haven't tried running a newer kernel yet. I was going to file a bug report on kernel.org but they advise to file it with the distro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036368/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036339] Re: Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6)
You can purge all these: ic linux-image-6.2.0-25-generic ic linux-image-6.2.0-26-generic rc linux-image-6.2.0-27-generic rc linux-modules-5.11.0-17-generic rc linux-modules-5.11.0-18-generic I still don't understand why update-initramfs tries kernel 6.2.0-24 when you don't have that installed. -- 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/2036339 Title: Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6) Status in linux-firmware package in Ubuntu: Incomplete Bug description: O.S.: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.6 Trying to install the package above, I receive these errors: Configuring linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6)... update-initramfs: Generating /boot/initrd.img-6.2.0-32-generic update-initramfs: Generating /boot/initrd.img-6.2.0-31-generic update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic grep: /boot/config-6.2.0-24-generic: No such file or directory W: zstd compression (CONFIG_RD_ZSTD) not supported by the kernel, using gzip grep: /boot/config-6.2.0-24-generic: No such file or directory E: gzip compression (CONFIG_RD_GZIP) not supported by the kernel update-initramfs: failed for /boot/initrd.img-6.2.0-24-generic with exit code 1 dpkg: error processing package linux-firmware (--configure): subprocess installed linux-firmware package post-installation script returned error status 1 Errors were encountered while processing: linux-firmware E: Sub-process /usr/bin/dpkg returned an error code (1) I tried to uninstall the package with sudo apt remove --purge linux-firmware and then reinstall it, but without success. Same result when trying installing older packages 20230323.gitbcdcfbcf-0ubuntu1.2 and 20230323.gitbcdcfbcf-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030924] Re: [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in cpuinfo_min_freq and cpuino_max_freq sysfs files.
Hi, Verification done with Jammy Linux and got expected results. ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- 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/2030924 Title: [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in cpuinfo_min_freq and cpuino_max_freq sysfs files. Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Released Bug description: [Impact] On DELL EMC PowerEdge system when Ubuntu 22.04.1 OS is Installed, Unable to Interpret the values in cpuinfo_max_freq and cpuinfo_min_freq sysfs files as per the Intel specs document. Steps to Reproduce: 1. Install one CPU that supports DBS "Demand-Based Power Management". 2. Install Ubuntu 22.04.1 OS. 2. Enable "Logical Processor" under CPU Information menu from F2 setup. 3. Save changes and reboot to Ubuntu 22.04.1 OS. 4. Right click on "Computer" and select "File system" and check for the following CPU directories. /sys/devices/system/cpu/cpu0/cpufreq/cpu0 /sys/devices/system/cpu/cpu0/cpufreq/cpu1 5. View the Max Frequency and Min Frequency under CPU0 and CPU1 directory. 6. The Max and Min Frequency did not match as per the Intel specs datasheet. Actual results: /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 680 /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 80 /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 390 Expected results: As per Intel datasheet specification. /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 5300 MHz /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 800 MHz /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 3000 MHz [Fix] cpufreq: intel_pstate: Fix scaling for hybrid-capable systems with disabled E-cores https://github.com/torvalds/linux/commit/0fcfc9e51990246a9813475716746ff5eb98c6aa [github.com] [Test Plan] Same as steps to reproduce [ Where problems could occur ] This issue is seen on Intel based system under development which supports DBS "Demand-Based Power Management", then install Ubuntu-22.04 and boot into OS then check for the frequency values under /sys/devices/system/cpu/cpu0/cpufreq/cpu0 Regression risk = Low to medium [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/cpuinfo_freq lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/cpuinfo_freq_lunar_2 Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/cpuinfo_freq_mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031289] Re: amdgpu driver crash: ring gfx_0.0.0 timeout
Can I close the bug then? -- 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/2031289 Title: amdgpu driver crash: ring gfx_0.0.0 timeout Status in linux package in Ubuntu: Confirmed Bug description: ThinkPad Z13 with 3 displays connected. Using Ubuntu 23.04 with 6.2.0-26-generic, the graphical desktop locks or crashes. dmesg has the following error: [Mon Aug 14 08:06:06 2023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=5346515, emitted seq=5346517 [Mon Aug 14 08:06:06 2023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 3456 thread Xorg:cs0 pid 3464 [Mon Aug 14 08:06:06 2023] amdgpu :63:00.0: amdgpu: GPU reset begin! This happens every few days, and I either have to restart the desktop or the entire computer. Today it happened at 08:06 when I wasn't at the machine doing anything. But many applications were still running, as I left it on Friday. I have two external displays attached via a USB type C hub. alan@ziggy:~$ xrandr | grep -B2 "*" eDP connected 1920x1200+0+0 (normal left inverted right x axis y axis) 289mm x 186mm 2880x1800 60.00 + 1920x1200 60.00* -- DisplayPort-6 disconnected (normal left inverted right x axis y axis) DisplayPort-7 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 527mm x 296mm 1920x1080 60.00*+ 50.0059.94 -- 720x400 70.08 DisplayPort-8 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 527mm x 296mm 1920x1080 60.00*+ 50.0059.94 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 08:57:10 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (373 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 MachineType: LENOVO 21D2CTO1WW ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=96c77f27-d90f-4d14-a5d5-59ac57b3f6dc ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-01-02 (223 days ago) dmi.bios.date: 12/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: N3GET47W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D2CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.54 dmi.modalias: dmi:bvnLENOVO:bvrN3GET47W(1.27):bd12/08/2022:br1.27:efr1.54:svnLENOVO:pn21D2CTO1WW:pvrThinkPadZ13Gen1:rvnLENOVO:rn21D2CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21D2_BU_Think_FM_ThinkPadZ13Gen1: dmi.product.family: ThinkPad Z13 Gen 1 dmi.product.name: 21D2CTO1WW dmi.product.sku: LENOVO_MT_21D2_BU_Think_FM_ThinkPad Z13 Gen 1 dmi.product.version: ThinkPad Z13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036339] Re: Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6)
You have a somewhat broken system: grep: /boot/config-6.2.0-24-generic: No such file or directory What does 'dpkg -l | grep linux-' show? ** 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/2036339 Title: Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6) Status in linux-firmware package in Ubuntu: Incomplete Bug description: O.S.: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.6 Trying to install the package above, I receive these errors: Configuring linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6)... update-initramfs: Generating /boot/initrd.img-6.2.0-32-generic update-initramfs: Generating /boot/initrd.img-6.2.0-31-generic update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic grep: /boot/config-6.2.0-24-generic: No such file or directory W: zstd compression (CONFIG_RD_ZSTD) not supported by the kernel, using gzip grep: /boot/config-6.2.0-24-generic: No such file or directory E: gzip compression (CONFIG_RD_GZIP) not supported by the kernel update-initramfs: failed for /boot/initrd.img-6.2.0-24-generic with exit code 1 dpkg: error processing package linux-firmware (--configure): subprocess installed linux-firmware package post-installation script returned error status 1 Errors were encountered while processing: linux-firmware E: Sub-process /usr/bin/dpkg returned an error code (1) I tried to uninstall the package with sudo apt remove --purge linux-firmware and then reinstall it, but without success. Same result when trying installing older packages 20230323.gitbcdcfbcf-0ubuntu1.2 and 20230323.gitbcdcfbcf-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031057] Re: [EHL] Screen flickering when the setup is in multiple monitors with mirror mode output
This bug was fixed in the package linux-intel-iotg - 5.15.0-1039.45 --- linux-intel-iotg (5.15.0-1039.45) jammy; urgency=medium * jammy/linux-intel-iotg: 5.15.0-1039.45 -proposed tracker (LP: #2030409) * [EHL] Screen flickering when the setup is in multiple monitors with mirror mode output (LP: #2031057) - SAUCE: (no-up) drm/i915/display : Remove support for interlace mode * [ADL-N][RPL-S] support ISHTP module (LP: #2029328) - HID: intel-ish-hid: ipc: add ADL and RPL device id - HID: intel-ish-hid: ipc: Specify no cache snooping on TGL and ADL - HID: intel-ish-hid: ipc: use time_before to replace "jiffies < a" - HID: intel-ish-hid: Fix kernel panic during warm reset [ Ubuntu: 5.15.0-83.92 ] * jammy/linux: 5.15.0-83.92 -proposed tracker (LP: #2031132) * libgnutls report "trap invalid opcode" when trying to install packages over https (LP: #2031093) - [Config]: disable CONFIG_GDS_FORCE_MITIGATION [ Ubuntu: 5.15.0-81.90 ] * jammy/linux: 5.15.0-81.90 -proposed tracker (LP: #2030422) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] resync getabis - debian/dkms-versions -- update from kernel-versions (main/2023.08.07) * CVE-2022-40982 - x86/mm: Initialize text poking earlier - x86/mm: fix poking_init() for Xen PV guests - x86/mm: Use mm_alloc() in poking_init() - mm: Move mm_cachep initialization to mm_init() - init: Provide arch_cpu_finalize_init() - x86/cpu: Switch to arch_cpu_finalize_init() - ARM: cpu: Switch to arch_cpu_finalize_init() - sparc/cpu: Switch to arch_cpu_finalize_init() - um/cpu: Switch to arch_cpu_finalize_init() - init: Remove check_bugs() leftovers - init: Invoke arch_cpu_finalize_init() earlier - init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init() - x86/init: Initialize signal frame size late - x86/fpu: Remove cpuinfo argument from init functions - x86/fpu: Mark init functions __init - x86/fpu: Move FPU initialization into arch_cpu_finalize_init() - x86/xen: Fix secondary processors' FPU initialization - x86/speculation: Add Gather Data Sampling mitigation - x86/speculation: Add force option to GDS mitigation - x86/speculation: Add Kconfig option for GDS - KVM: Add GDS_NO support to KVM - Documentation/x86: Fix backwards on/off logic about YMM support - [Config]: Enable CONFIG_ARCH_HAS_CPU_FINALIZE_INIT and CONFIG_GDS_FORCE_MITIGATION * CVE-2023-3609 - net/sched: cls_u32: Fix reference counter leak leading to overflow * CVE-2023-21400 - io_uring: ensure IOPOLL locks around deferred work * CVE-2023-4015 - netfilter: nf_tables: add NFT_TRANS_PREPARE_ERROR to deal with bound set/chain - netfilter: nf_tables: unbind non-anonymous set if rule construction fails - netfilter: nf_tables: skip immediate deactivate in _PREPARE_ERROR * CVE-2023-3995 - netfilter: nf_tables: disallow rule addition to bound chain via NFTA_RULE_CHAIN_ID * CVE-2023-3777 - netfilter: nf_tables: skip bound chain on rule flush * losetup with mknod fails on jammy with kernel 5.15.0-69-generic (LP: #2015400) - loop: do not enforce max_loop hard limit by (new) default * Include the MAC address pass through function on RTL8153DD-CG (LP: #2020295) - r8152: add USB device driver for config selection * Jammy update: v5.15.116 upstream stable release (LP: #2029401) - RDMA/bnxt_re: Fix the page_size used during the MR creation - RDMA/efa: Fix unsupported page sizes in device - RDMA/hns: Fix base address table allocation - RDMA/hns: Modify the value of long message loopback slice - dmaengine: at_xdmac: Move the free desc to the tail of the desc list - dmaengine: at_xdmac: fix potential Oops in at_xdmac_prep_interleaved() - RDMA/bnxt_re: Fix a possible memory leak - RDMA/bnxt_re: Fix return value of bnxt_re_process_raw_qp_pkt_rx - iommu/rockchip: Fix unwind goto issue - iommu/amd: Don't block updates to GATag if guest mode is on - dmaengine: pl330: rename _start to prevent build error - riscv: Fix unused variable warning when BUILTIN_DTB is set - net/mlx5: fw_tracer, Fix event handling - net/mlx5e: Don't attach netdev profile while handling internal error - net: mellanox: mlxbf_gige: Fix skb_panic splat under memory pressure - netrom: fix info-leak in nr_write_internal() - af_packet: Fix data-races of pkt_sk(sk)->num. - amd-xgbe: fix the false linkup in xgbe_phy_status - mtd: rawnand: ingenic: fix empty stub helper definitions - RDMA/irdma: Add SW mechanism to generate completions on error - RDMA/irdma: Prevent QP use after free - RDMA/irdma: Fix Local Invalidate fencing - af_packet: do not use READ_ONCE() in packet_bind() - tcp: deny tcp_disconnect() when threads are waiting - tcp: Return user_mss for TCP_MAXSEG in CLOSE/LISTEN
[Kernel-packages] [Bug 2029328] Re: [ADL-N][RPL-S] support ISHTP module
This bug was fixed in the package linux-intel-iotg - 5.15.0-1039.45 --- linux-intel-iotg (5.15.0-1039.45) jammy; urgency=medium * jammy/linux-intel-iotg: 5.15.0-1039.45 -proposed tracker (LP: #2030409) * [EHL] Screen flickering when the setup is in multiple monitors with mirror mode output (LP: #2031057) - SAUCE: (no-up) drm/i915/display : Remove support for interlace mode * [ADL-N][RPL-S] support ISHTP module (LP: #2029328) - HID: intel-ish-hid: ipc: add ADL and RPL device id - HID: intel-ish-hid: ipc: Specify no cache snooping on TGL and ADL - HID: intel-ish-hid: ipc: use time_before to replace "jiffies < a" - HID: intel-ish-hid: Fix kernel panic during warm reset [ Ubuntu: 5.15.0-83.92 ] * jammy/linux: 5.15.0-83.92 -proposed tracker (LP: #2031132) * libgnutls report "trap invalid opcode" when trying to install packages over https (LP: #2031093) - [Config]: disable CONFIG_GDS_FORCE_MITIGATION [ Ubuntu: 5.15.0-81.90 ] * jammy/linux: 5.15.0-81.90 -proposed tracker (LP: #2030422) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] resync getabis - debian/dkms-versions -- update from kernel-versions (main/2023.08.07) * CVE-2022-40982 - x86/mm: Initialize text poking earlier - x86/mm: fix poking_init() for Xen PV guests - x86/mm: Use mm_alloc() in poking_init() - mm: Move mm_cachep initialization to mm_init() - init: Provide arch_cpu_finalize_init() - x86/cpu: Switch to arch_cpu_finalize_init() - ARM: cpu: Switch to arch_cpu_finalize_init() - sparc/cpu: Switch to arch_cpu_finalize_init() - um/cpu: Switch to arch_cpu_finalize_init() - init: Remove check_bugs() leftovers - init: Invoke arch_cpu_finalize_init() earlier - init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init() - x86/init: Initialize signal frame size late - x86/fpu: Remove cpuinfo argument from init functions - x86/fpu: Mark init functions __init - x86/fpu: Move FPU initialization into arch_cpu_finalize_init() - x86/xen: Fix secondary processors' FPU initialization - x86/speculation: Add Gather Data Sampling mitigation - x86/speculation: Add force option to GDS mitigation - x86/speculation: Add Kconfig option for GDS - KVM: Add GDS_NO support to KVM - Documentation/x86: Fix backwards on/off logic about YMM support - [Config]: Enable CONFIG_ARCH_HAS_CPU_FINALIZE_INIT and CONFIG_GDS_FORCE_MITIGATION * CVE-2023-3609 - net/sched: cls_u32: Fix reference counter leak leading to overflow * CVE-2023-21400 - io_uring: ensure IOPOLL locks around deferred work * CVE-2023-4015 - netfilter: nf_tables: add NFT_TRANS_PREPARE_ERROR to deal with bound set/chain - netfilter: nf_tables: unbind non-anonymous set if rule construction fails - netfilter: nf_tables: skip immediate deactivate in _PREPARE_ERROR * CVE-2023-3995 - netfilter: nf_tables: disallow rule addition to bound chain via NFTA_RULE_CHAIN_ID * CVE-2023-3777 - netfilter: nf_tables: skip bound chain on rule flush * losetup with mknod fails on jammy with kernel 5.15.0-69-generic (LP: #2015400) - loop: do not enforce max_loop hard limit by (new) default * Include the MAC address pass through function on RTL8153DD-CG (LP: #2020295) - r8152: add USB device driver for config selection * Jammy update: v5.15.116 upstream stable release (LP: #2029401) - RDMA/bnxt_re: Fix the page_size used during the MR creation - RDMA/efa: Fix unsupported page sizes in device - RDMA/hns: Fix base address table allocation - RDMA/hns: Modify the value of long message loopback slice - dmaengine: at_xdmac: Move the free desc to the tail of the desc list - dmaengine: at_xdmac: fix potential Oops in at_xdmac_prep_interleaved() - RDMA/bnxt_re: Fix a possible memory leak - RDMA/bnxt_re: Fix return value of bnxt_re_process_raw_qp_pkt_rx - iommu/rockchip: Fix unwind goto issue - iommu/amd: Don't block updates to GATag if guest mode is on - dmaengine: pl330: rename _start to prevent build error - riscv: Fix unused variable warning when BUILTIN_DTB is set - net/mlx5: fw_tracer, Fix event handling - net/mlx5e: Don't attach netdev profile while handling internal error - net: mellanox: mlxbf_gige: Fix skb_panic splat under memory pressure - netrom: fix info-leak in nr_write_internal() - af_packet: Fix data-races of pkt_sk(sk)->num. - amd-xgbe: fix the false linkup in xgbe_phy_status - mtd: rawnand: ingenic: fix empty stub helper definitions - RDMA/irdma: Add SW mechanism to generate completions on error - RDMA/irdma: Prevent QP use after free - RDMA/irdma: Fix Local Invalidate fencing - af_packet: do not use READ_ONCE() in packet_bind() - tcp: deny tcp_disconnect() when threads are waiting - tcp: Return user_mss for TCP_MAXSEG in CLOSE/LISTEN
[Kernel-packages] [Bug 2036339] Re: Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6)
Thank you https://launchpad.net/~juergh Since you pointed out the error relating to linux- firmware-6.2.0-24-generic, I tried reinstalling it (receiving new errors) and then doing a purge. The linux-firmware package now installs successfully I wonder if I can also purge all the packages reported in the output of the dpkg -l | command grep linux- which I posted above, with the acronym "rc" (they should be packages in broken state). Since they are referring to older firmware modules, there shouldn't be any problems, I think. Can anyone confirm this? After that I mark the bug as SOLVED. -- 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/2036339 Title: Unable to install linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6) Status in linux-firmware package in Ubuntu: Incomplete Bug description: O.S.: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.6 Trying to install the package above, I receive these errors: Configuring linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.6)... update-initramfs: Generating /boot/initrd.img-6.2.0-32-generic update-initramfs: Generating /boot/initrd.img-6.2.0-31-generic update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic grep: /boot/config-6.2.0-24-generic: No such file or directory W: zstd compression (CONFIG_RD_ZSTD) not supported by the kernel, using gzip grep: /boot/config-6.2.0-24-generic: No such file or directory E: gzip compression (CONFIG_RD_GZIP) not supported by the kernel update-initramfs: failed for /boot/initrd.img-6.2.0-24-generic with exit code 1 dpkg: error processing package linux-firmware (--configure): subprocess installed linux-firmware package post-installation script returned error status 1 Errors were encountered while processing: linux-firmware E: Sub-process /usr/bin/dpkg returned an error code (1) I tried to uninstall the package with sudo apt remove --purge linux-firmware and then reinstall it, but without success. Same result when trying installing older packages 20230323.gitbcdcfbcf-0ubuntu1.2 and 20230323.gitbcdcfbcf-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006797] Re: MT7922 firmware not working
6.5.0-1003 OEM fixed this bug. -- 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/2006797 Title: MT7922 firmware not working Status in linux package in Ubuntu: Confirmed Bug description: Hey I have a "ASUS ROG Strix B650-A Gaming WIFI" (https://rog.asus.com/motherboards/rog-strix/rog-strix-b650-a-gaming- wifi-model/) Motherboard and the WiFi/Bluetooth is not working. On windows, the module is working fine. Using "Kubuntu 22.10" with Kernel "5.19.0-35-generic" lshw -class network: *-network description: Network controller product: MT7922 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:0b:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list configuration: driver=mt7921e latency=0 resources: iomemory:fc0-fbf irq:119 memory:fc3030-fc303f memory:fc50-fc507fff #dmesg | grep mt7921e [ 17.001057] mt7921e :0b:00.0: enabling device ( -> 0002) [ 17.001199] mt7921e :0b:00.0: ASIC revision: 79220010 [ 20.247369] mt7921e :0b:00.0: Message 0004008a (seq 1) timeout [ 23.575534] mt7921e :0b:00.0: Message 0004008a (seq 2) timeout [ 26.907372] mt7921e :0b:00.0: Message 0004008a (seq 3) timeout [ 30.231376] mt7921e :0b:00.0: Message 0004008a (seq 4) timeout [ 33.559704] mt7921e :0b:00.0: Message 0004008a (seq 5) timeout [ 36.887365] mt7921e :0b:00.0: Message 0004008a (seq 6) timeout [ 40.215367] mt7921e :0b:00.0: Message 0004008a (seq 7) timeout [ 43.543670] mt7921e :0b:00.0: Message 0004008a (seq 8) timeout [ 46.871378] mt7921e :0b:00.0: Message 0004008a (seq 9) timeout [ 50.199714] mt7921e :0b:00.0: Message 0004008a (seq 10) timeout [ 50.280219] mt7921e :0b:00.0: hardware init failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Feb 10 03:33:02 2023 InstallationDate: Installed on 2023-02-09 (0 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: ASUS System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-35-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 8.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0823 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B650-A GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0823:bd11/21/2022:br8.23:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB650-AGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027983] Re: CONFIG_MPTCP_IPV6 is no longer enabled in Raspi Lunar in v6.2.0
This bug was fixed in the package linux-raspi - 6.5.0-1002.2 --- linux-raspi (6.5.0-1002.2) mantic; urgency=medium * mantic/linux-raspi: 6.5.0-1002.2 -proposed tracker (LP: #2033637) * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Miscellaneous Ubuntu changes - [Config] raspi: Add notes to configs that differ from master - [Config] raspi: Set CONFIG_ARM_ERRATA_=n - [Config] raspi: Set PREEMPT_DYNAMIC=y - [Config] raspi: Set STAGING_MEDIA_DEPRECATED=n - [Config] raspi: Set EFI=n - [Config] raspi: Set POWER_RESET_GPIO_RESTART=n - [Config] raspi: Set HID_BPF=n - [Config] raspi: Set COMMON_CLK_FIXED_MMIO=n - [Config] raspi: Set PWM_STMPE=n - [Config] raspi: Set LEDS_SYSCON=n - [Packaging] raspi: Include bcm2835_smi module in linux-modules - SAUCE: (no-up) Disable FIQ split-transaction FSM in dwc_otg * Miscellaneous upstream changes - drivers: media: imx296: Updated imx296 driver for external trigger - char: broadcom: vc_mem: Fix preprocessor conditional - drivers: dwc_otg: Fix fallthrough warnings - vc04_services/vc-sm-cma: Switch one-bit bitfields to bool - media: i2c: ov2311: Fix uninitialized variable usage - drm/panel: Fix default values for Waveshare 7.9 inch DSI touchscreen (#5565) - dtoverlays: Add i2c bus overrides to edt-ft5406 overlay - dtoverlays: Fix README text for i2c-fan - drivers: irqchip: irq-bcm2835: Concurrency fix - defconfigs: Add TINYDRM_ILI9486 to defconfigs - dtoverlays: Add drm option to piscreen overlay - drm/ili9486: Resolve clash in spi_device_id names - input: ads7846: Add missing spi_device_id strings - staging: bcm2835-codec: Downgrade the level for a debug message - configs: Raise 8250 UART limit to 5 on BCM2711 [ Ubuntu: 6.5.0-5.5 ] * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) [ Ubuntu: 6.5.0-4.4 ] * mantic/linux: 6.5.0-4.4 -proposed tracker (LP: #2034042) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) [ Ubuntu: 6.5.0-3.3 ] * mantic/linux: 6.5.0-3.3 -proposed tracker (LP: #2033904) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) * [23.10] Please test secure-boot and lockdown on the early 6.5 kernel (s390x) (LP: #2026833) - [Packaging] re-enable signing for s390x * Miscellaneous upstream changes - module/decompress: use vmalloc() for zstd decompression workspace [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * 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 * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME
[Kernel-packages] [Bug 2023359] Re: raspi-nolpae flavor is pointless nowadays
This bug was fixed in the package linux-raspi - 6.5.0-1002.2 --- linux-raspi (6.5.0-1002.2) mantic; urgency=medium * mantic/linux-raspi: 6.5.0-1002.2 -proposed tracker (LP: #2033637) * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Miscellaneous Ubuntu changes - [Config] raspi: Add notes to configs that differ from master - [Config] raspi: Set CONFIG_ARM_ERRATA_=n - [Config] raspi: Set PREEMPT_DYNAMIC=y - [Config] raspi: Set STAGING_MEDIA_DEPRECATED=n - [Config] raspi: Set EFI=n - [Config] raspi: Set POWER_RESET_GPIO_RESTART=n - [Config] raspi: Set HID_BPF=n - [Config] raspi: Set COMMON_CLK_FIXED_MMIO=n - [Config] raspi: Set PWM_STMPE=n - [Config] raspi: Set LEDS_SYSCON=n - [Packaging] raspi: Include bcm2835_smi module in linux-modules - SAUCE: (no-up) Disable FIQ split-transaction FSM in dwc_otg * Miscellaneous upstream changes - drivers: media: imx296: Updated imx296 driver for external trigger - char: broadcom: vc_mem: Fix preprocessor conditional - drivers: dwc_otg: Fix fallthrough warnings - vc04_services/vc-sm-cma: Switch one-bit bitfields to bool - media: i2c: ov2311: Fix uninitialized variable usage - drm/panel: Fix default values for Waveshare 7.9 inch DSI touchscreen (#5565) - dtoverlays: Add i2c bus overrides to edt-ft5406 overlay - dtoverlays: Fix README text for i2c-fan - drivers: irqchip: irq-bcm2835: Concurrency fix - defconfigs: Add TINYDRM_ILI9486 to defconfigs - dtoverlays: Add drm option to piscreen overlay - drm/ili9486: Resolve clash in spi_device_id names - input: ads7846: Add missing spi_device_id strings - staging: bcm2835-codec: Downgrade the level for a debug message - configs: Raise 8250 UART limit to 5 on BCM2711 [ Ubuntu: 6.5.0-5.5 ] * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) [ Ubuntu: 6.5.0-4.4 ] * mantic/linux: 6.5.0-4.4 -proposed tracker (LP: #2034042) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) [ Ubuntu: 6.5.0-3.3 ] * mantic/linux: 6.5.0-3.3 -proposed tracker (LP: #2033904) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) * [23.10] Please test secure-boot and lockdown on the early 6.5 kernel (s390x) (LP: #2026833) - [Packaging] re-enable signing for s390x * Miscellaneous upstream changes - module/decompress: use vmalloc() for zstd decompression workspace [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * 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 * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME
[Kernel-packages] [Bug 2017209] Re: [Raspberry Pi/lunar] systemd-oomd fails with "ConditionControlGroupController=memory was not met"
This bug was fixed in the package linux-raspi - 6.5.0-1002.2 --- linux-raspi (6.5.0-1002.2) mantic; urgency=medium * mantic/linux-raspi: 6.5.0-1002.2 -proposed tracker (LP: #2033637) * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Miscellaneous Ubuntu changes - [Config] raspi: Add notes to configs that differ from master - [Config] raspi: Set CONFIG_ARM_ERRATA_=n - [Config] raspi: Set PREEMPT_DYNAMIC=y - [Config] raspi: Set STAGING_MEDIA_DEPRECATED=n - [Config] raspi: Set EFI=n - [Config] raspi: Set POWER_RESET_GPIO_RESTART=n - [Config] raspi: Set HID_BPF=n - [Config] raspi: Set COMMON_CLK_FIXED_MMIO=n - [Config] raspi: Set PWM_STMPE=n - [Config] raspi: Set LEDS_SYSCON=n - [Packaging] raspi: Include bcm2835_smi module in linux-modules - SAUCE: (no-up) Disable FIQ split-transaction FSM in dwc_otg * Miscellaneous upstream changes - drivers: media: imx296: Updated imx296 driver for external trigger - char: broadcom: vc_mem: Fix preprocessor conditional - drivers: dwc_otg: Fix fallthrough warnings - vc04_services/vc-sm-cma: Switch one-bit bitfields to bool - media: i2c: ov2311: Fix uninitialized variable usage - drm/panel: Fix default values for Waveshare 7.9 inch DSI touchscreen (#5565) - dtoverlays: Add i2c bus overrides to edt-ft5406 overlay - dtoverlays: Fix README text for i2c-fan - drivers: irqchip: irq-bcm2835: Concurrency fix - defconfigs: Add TINYDRM_ILI9486 to defconfigs - dtoverlays: Add drm option to piscreen overlay - drm/ili9486: Resolve clash in spi_device_id names - input: ads7846: Add missing spi_device_id strings - staging: bcm2835-codec: Downgrade the level for a debug message - configs: Raise 8250 UART limit to 5 on BCM2711 [ Ubuntu: 6.5.0-5.5 ] * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) [ Ubuntu: 6.5.0-4.4 ] * mantic/linux: 6.5.0-4.4 -proposed tracker (LP: #2034042) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) [ Ubuntu: 6.5.0-3.3 ] * mantic/linux: 6.5.0-3.3 -proposed tracker (LP: #2033904) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) * [23.10] Please test secure-boot and lockdown on the early 6.5 kernel (s390x) (LP: #2026833) - [Packaging] re-enable signing for s390x * Miscellaneous upstream changes - module/decompress: use vmalloc() for zstd decompression workspace [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * 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 * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME
[Kernel-packages] [Bug 2036428] Re: Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1
Sure, here's an excerpt from boot to where the kernel lines tail off, I suspect the relevant lines are 1234-1242: https://paste.ubuntu.com/p/STWWJMn7zw/ -- 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 2029332] Re: Reboot command powers off the system
I have used the steps outlined in https://wiki.ubuntu.com/Testing/EnableProposed documentation how to enable and use -proposed however, the kernel is not getting updated and still see the reboot issue. Steps followed: 1) Took an HPE DL360 Gen 10 Plus system running 5.19 kernel (5.19.0-051900) where the issue is observed & confirmed the reboot issue. 2) Followed the instructions to enable the Jammy-proposed a) Verified using the GUI 'Software updater' in 'Developer Options' tab to ensure "Pre-released updates (jammy-proposed)" is checked. b) Made sure the /etc/opt/sources.list has "deb http://us.archive.ubuntu.com/ubuntu jammy-proposed main restricted universe multiverse" is added to the file 3) Performed an update using the following commands: sudo apt-get update sudo apt-get upgrade 4) Rebooted the system & tried to verify: a) the reboot problem still exists b) the kernel version is 5.19.0-051900-generic FYI - Normally the following steps are taken to update the kernel: Open Terminal cd ~/Downloads wget -c https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.19/amd64/linux- headers-5.19.0-051900_5.19.0-051900.202207312230_all.deb wget -c https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.19/amd64/linux- headers-5.19.0-051900-generic_5.19.0-051900.202207312230_amd64.deb wget -c https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.19/amd64/linux-image- unsigned-5.19.0-051900-generic_5.19.0-051900.202207312230_amd64.deb wget -c https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.19/amd64/linux- modules-5.19.0-051900-generic_5.19.0-051900.202207312230_amd64.deb sudo apt install ./linux-headers-5.19.0*.deb ./linux-image- unsigned-5.19.0*.deb ./linux-modules-5.19.0*.deb -- 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 2036456] [NEW] linux-firmware mantic missing intel/ibt-{19, 20}*
Public bug reported:
linux-firmware on mantic (20230915.gitdfa11466-0ubuntu1) is missing
/intel/ibt-{19,20}-*
firmwares. When booting I get the following error message:
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Bootloader revision 0.1
build 0 week 30 2018
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Device revision is 2
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Secure boot is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: OTP lock is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: API lock is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Debug lock is disabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Minimum firmware build 1
week 10 2014
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Failed to load Intel
firmware file intel/ibt-19-0-1.sfi (-2)
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Reading supported features
failed (-56)
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Error reading debug
features
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Failed to read MSFT
supported features (-56)
Hardware used is:
ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
--
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/2036456
Title:
linux-firmware mantic missing intel/ibt-{19,20}*
Status in linux-firmware package in Ubuntu:
New
Bug description:
linux-firmware on mantic (20230915.gitdfa11466-0ubuntu1) is missing
/intel/ibt-{19,20}-*
firmwares. When booting I get the following error message:
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Bootloader revision 0.1
build 0 week 30 2018
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Device revision is 2
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Secure boot is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: OTP lock is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: API lock is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Debug lock is disabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Minimum firmware build 1
week 10 2014
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Failed to load Intel
firmware file intel/ibt-19-0-1.sfi (-2)
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Reading supported
features failed (-56)
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Error reading debug
features
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Failed to read MSFT
supported features (-56)
Hardware used is:
ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036456/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035361] Re: [jammy:linux-intel-iot-realtime][TSN] Path delay in realtime kernel is not equal to 0
** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-intel-iotg (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2035361 Title: [jammy:linux-intel-iot-realtime][TSN] Path delay in realtime kernel is not equal to 0 Status in linux-intel-iotg package in Ubuntu: Fix Committed Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2030480 [Summary] The command `phc2sys` is to sync the system clock and PTP hardware clock on one machine. The output from `phc2sys` command indicate some information including the `delay`. The `delay` should be 0 if the device is using `hardware cross-timestamping`. In realtime kernel, the `delay` is never 0. But it is 0 in generic kernel (which is correct). This issue also happened on EHL and TGL, which means it may be an all-platform issue caused by realtime kernel. output from realtime kernel --- root@u-Alder-Lake-Client-Platform:/home/u# phc2sys -s "$interface" -O 0 -c CLOCK_REALTIME --step_threshold=1 --transportSpecific=1 -w -m --first_step_threshold=0.0 phc2sys[1021.560]: CLOCK_REALTIME phc offset 3251119 s0 freq -85311 delay 3107 phc2sys[1022.560]: CLOCK_REALTIME phc offset 3255144 s2 freq -81287 delay 2936 phc2sys[1023.560]: CLOCK_REALTIME phc offset 3255167 s2 freq +3173880 delay 2907 phc2sys[1024.560]: CLOCK_REALTIME phc offset -10828 s2 freq +884435 delay 2977 phc2sys[1025.561]: CLOCK_REALTIME phc offset -977556 s2 freq -85541 delay 3385 phc2sys[1026.561]: CLOCK_REALTIME phc offset -973361 s2 freq -374613 delay 2921 phc2sys[1027.561]: CLOCK_REALTIME phc offset -680002 s2 freq -373262 delay 2988 phc2sys[1028.561]: CLOCK_REALTIME phc offset -387940 s2 freq -285201 delay 3392 phc2sys[1029.562]: CLOCK_REALTIME phc offset -183974 s2 freq -197617 delay 3361 phc2sys[1030.562]: CLOCK_REALTIME phc offset -67676 s2 freq -136511 delay 2933 phc2sys[1031.562]: CLOCK_REALTIME phc offset -12389 s2 freq -101527 delay 2976 phc2sys[1032.562]: CLOCK_REALTIME phc offset 7914 s2 freq -84940 delay 2973 phc2sys[1033.563]: CLOCK_REALTIME phc offset 11594 s2 freq -78886 delay 2975 phc2sys[1034.563]: CLOCK_REALTIME phc offset 9221 s2 freq -77781 delay 2931 phc2sys[1035.563]: CLOCK_REALTIME phc offset 5824 s2 freq -78412 delay 2996 phc2sys[1036.563]: CLOCK_REALTIME phc offset 2980 s2 freq -79508 delay 3184 phc2sys[1037.564]: CLOCK_REALTIME phc offset 1216 s2 freq -80378 delay 2926 phc2sys[1038.564]: CLOCK_REALTIME phc offset 400 s2 freq -80830 delay 3126 phc2sys[1039.564]: CLOCK_REALTIME phc offset -29 s2 freq -81139 delay 2985 phc2sys[1040.565]: CLOCK_REALTIME phc offset -133 s2 freq -81251 delay 2991 phc2sys[1041.565]: CLOCK_REALTIME phc offset -135 s2 freq -81293 delay 2941 phc2sys[1042.565]: CLOCK_REALTIME phc offset -40 s2 freq -81239 delay 2952 phc2sys[1043.565]: CLOCK_REALTIME phc offset -43 s2 freq -81254 delay 2975 phc2sys[1044.566]: CLOCK_REALTIME phc offset 43 s2 freq -81181 delay 3306 phc2sys[1045.566]: CLOCK_REALTIME phc offset -105 s2 freq -81316 delay 2970 phc2sys[1046.566]: CLOCK_REALTIME phc offset -4 s2 freq -81246 delay 2944 phc2sys[1047.567]: CLOCK_REALTIME phc offset -14 s2 freq -81257 delay 3098 phc2sys[1048.567]: CLOCK_REALTIME phc offset 28 s2 freq -81220 delay 2944 phc2sys[1049.567]: CLOCK_REALTIME phc offset 64 s2 freq -81175 delay 3181 phc2sys[1050.568]: CLOCK_REALTIME phc offset -27 s2 freq -81247 delay 3027 phc2sys[1051.568]: CLOCK_REALTIME phc offset -19 s2 freq -81247 delay 2930 output from generic kernel (5.15.0-1036-intel-iotg) --- root@u-Alder-Lake-Client-Platform:/home/u# phc2sys -s "$interface" -O 0 -c CLOCK_REALTIME --step_threshold=1 --transportSpecific=1 -w -m --first_step_threshold=0.0 phc2sys[378.423]: CLOCK_REALTIME phc offset 266 s0 freq -96482 delay 0 phc2sys[379.423]: CLOCK_REALTIME phc offset 403 s2 freq -96345 delay 0 phc2sys[380.423]: CLOCK_REALTIME phc offset 380 s2 freq -95965 delay 0 phc2sys[381.424]: CLOCK_REALTIME phc offset -3 s2 freq -96234 delay 0 phc2sys[382.424]: CLOCK_REALTIME phc offset -108 s2 freq -96340 delay 0 phc2sys[383.424]: CLOCK_REALTIME phc offset -131 s2 freq -96395 delay 0 phc2sys[384.424]: CLOCK_REALTIME phc offset -73 s2 freq -96377 delay 0 phc2sys[385.424]: CLOCK_REALTIME phc offset -46 s2 freq -96372 delay 0 phc2sys[386.425]: CLOCK_REALTIME phc offset -27 s2 freq -96366 delay 0 phc2sys[387.425]: CLOCK_REALTIME phc offset 1 s2 freq -96346 delay 0 phc2sys[388.425]: CLOCK_REALTIME phc offset -10 s2 freq -96357 delay 0 phc2sys[389.425]: CLOCK_REALTIME phc offset 7 s2 freq -96343 delay 0 phc2sys[390.425]:
[Kernel-packages] [Bug 2031580] Re: 6.2 kernel on Ubuntu 22.04 causes wake from suspend failures on MacBook Pro (Retina, 13-inch, Early 2015) Model Identifier: MacBookPro12, 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Confirmed -- 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/2031580 Title: 6.2 kernel on Ubuntu 22.04 causes wake from suspend failures on MacBook Pro (Retina, 13-inch, Early 2015) Model Identifier: MacBookPro12,1 Status in intel-microcode package in Ubuntu: Invalid Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Disabling Wayland partially helps but eventually will cause the computer to not wake up. This occurs both when closing the lid and when leaving the computer idle for some time. Description: Ubuntu 22.04.3 LTS Release: 22.04 intel-microcode: Installed: 3.20230808.0ubuntu0.22.04.1 I expected resume from sleep/suspend to behave as it did prior. If I would open the lid or push any keys, the computer would wake up from sleep/suspend. Instead, the computer does not wake from sleep/suspend and I need to force the computer to shutdown using the power button and then turn it back on again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/2031580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032578] Re: apply nvidia igx patches for Aug 15-21
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- 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/2032578 Title: apply nvidia igx patches for Aug 15-21 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: 1 patch for the dates Aug 15-21, 2023 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2032578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- 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 2032954] Re: Re-enable CONFIG_MEMCG on the Tegra kernels
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2032954 Title: Re-enable CONFIG_MEMCG on the Tegra kernels Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: For a time, CONFIG_MEMCG had been disabled by the RT patchset to resolve a bug in its interaction with PREEMPT_RT. This has since been resolved and the Ubuntu RT kernel has re-enabled this configuration option, but this has not been reflected in the Tegra kernels. The Tegra kernels will be updated to have this configuration option enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2032954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- 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 2031344] Re: apply nvidia igx patches for Aug 8-14
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- 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/2031344 Title: apply nvidia igx patches for Aug 8-14 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: 2 patches to apply to IGX kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2031344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017135] Re: memcpy: detected field-spanning write (size 45) of single field
This bug was fixed in the package linux-raspi - 6.5.0-1002.2 --- linux-raspi (6.5.0-1002.2) mantic; urgency=medium * mantic/linux-raspi: 6.5.0-1002.2 -proposed tracker (LP: #2033637) * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Miscellaneous Ubuntu changes - [Config] raspi: Add notes to configs that differ from master - [Config] raspi: Set CONFIG_ARM_ERRATA_=n - [Config] raspi: Set PREEMPT_DYNAMIC=y - [Config] raspi: Set STAGING_MEDIA_DEPRECATED=n - [Config] raspi: Set EFI=n - [Config] raspi: Set POWER_RESET_GPIO_RESTART=n - [Config] raspi: Set HID_BPF=n - [Config] raspi: Set COMMON_CLK_FIXED_MMIO=n - [Config] raspi: Set PWM_STMPE=n - [Config] raspi: Set LEDS_SYSCON=n - [Packaging] raspi: Include bcm2835_smi module in linux-modules - SAUCE: (no-up) Disable FIQ split-transaction FSM in dwc_otg * Miscellaneous upstream changes - drivers: media: imx296: Updated imx296 driver for external trigger - char: broadcom: vc_mem: Fix preprocessor conditional - drivers: dwc_otg: Fix fallthrough warnings - vc04_services/vc-sm-cma: Switch one-bit bitfields to bool - media: i2c: ov2311: Fix uninitialized variable usage - drm/panel: Fix default values for Waveshare 7.9 inch DSI touchscreen (#5565) - dtoverlays: Add i2c bus overrides to edt-ft5406 overlay - dtoverlays: Fix README text for i2c-fan - drivers: irqchip: irq-bcm2835: Concurrency fix - defconfigs: Add TINYDRM_ILI9486 to defconfigs - dtoverlays: Add drm option to piscreen overlay - drm/ili9486: Resolve clash in spi_device_id names - input: ads7846: Add missing spi_device_id strings - staging: bcm2835-codec: Downgrade the level for a debug message - configs: Raise 8250 UART limit to 5 on BCM2711 [ Ubuntu: 6.5.0-5.5 ] * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) [ Ubuntu: 6.5.0-4.4 ] * mantic/linux: 6.5.0-4.4 -proposed tracker (LP: #2034042) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) [ Ubuntu: 6.5.0-3.3 ] * mantic/linux: 6.5.0-3.3 -proposed tracker (LP: #2033904) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) * [23.10] Please test secure-boot and lockdown on the early 6.5 kernel (s390x) (LP: #2026833) - [Packaging] re-enable signing for s390x * Miscellaneous upstream changes - module/decompress: use vmalloc() for zstd decompression workspace [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * 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 * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME
[Kernel-packages] [Bug 1954757] Re: Missing overlays/README
This bug was fixed in the package linux-raspi - 6.5.0-1002.2 --- linux-raspi (6.5.0-1002.2) mantic; urgency=medium * mantic/linux-raspi: 6.5.0-1002.2 -proposed tracker (LP: #2033637) * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Miscellaneous Ubuntu changes - [Config] raspi: Add notes to configs that differ from master - [Config] raspi: Set CONFIG_ARM_ERRATA_=n - [Config] raspi: Set PREEMPT_DYNAMIC=y - [Config] raspi: Set STAGING_MEDIA_DEPRECATED=n - [Config] raspi: Set EFI=n - [Config] raspi: Set POWER_RESET_GPIO_RESTART=n - [Config] raspi: Set HID_BPF=n - [Config] raspi: Set COMMON_CLK_FIXED_MMIO=n - [Config] raspi: Set PWM_STMPE=n - [Config] raspi: Set LEDS_SYSCON=n - [Packaging] raspi: Include bcm2835_smi module in linux-modules - SAUCE: (no-up) Disable FIQ split-transaction FSM in dwc_otg * Miscellaneous upstream changes - drivers: media: imx296: Updated imx296 driver for external trigger - char: broadcom: vc_mem: Fix preprocessor conditional - drivers: dwc_otg: Fix fallthrough warnings - vc04_services/vc-sm-cma: Switch one-bit bitfields to bool - media: i2c: ov2311: Fix uninitialized variable usage - drm/panel: Fix default values for Waveshare 7.9 inch DSI touchscreen (#5565) - dtoverlays: Add i2c bus overrides to edt-ft5406 overlay - dtoverlays: Fix README text for i2c-fan - drivers: irqchip: irq-bcm2835: Concurrency fix - defconfigs: Add TINYDRM_ILI9486 to defconfigs - dtoverlays: Add drm option to piscreen overlay - drm/ili9486: Resolve clash in spi_device_id names - input: ads7846: Add missing spi_device_id strings - staging: bcm2835-codec: Downgrade the level for a debug message - configs: Raise 8250 UART limit to 5 on BCM2711 [ Ubuntu: 6.5.0-5.5 ] * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) [ Ubuntu: 6.5.0-4.4 ] * mantic/linux: 6.5.0-4.4 -proposed tracker (LP: #2034042) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) [ Ubuntu: 6.5.0-3.3 ] * mantic/linux: 6.5.0-3.3 -proposed tracker (LP: #2033904) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) * [23.10] Please test secure-boot and lockdown on the early 6.5 kernel (s390x) (LP: #2026833) - [Packaging] re-enable signing for s390x * Miscellaneous upstream changes - module/decompress: use vmalloc() for zstd decompression workspace [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * 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 * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME
[Kernel-packages] [Bug 2036273] Re: 5.15+ GCE Instances are unable to create fb0 with virt mon attached
Hi Kyler Will you be able to let me know your few availability slots so that I can schedule/coordinate a call? -- 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/2036273 Title: 5.15+ GCE Instances are unable to create fb0 with virt mon attached Status in linux-gcp package in Ubuntu: New Bug description: This is a public facing LP issue to address the content in Canonical's SF#00366439. Summary: Post 18.04 ( or 20.04 prior to moving to 5.15 ), efifb fails to stand up fb0. It is assigned, but fb0 is never created, nor are there any errors that I noted. Here is an example from a focal using linux-gcp --- 5.15.0-1041-gcp #49~20.04.1-Ubuntu SMP kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb [0.925827] pci :00:05.0: BAR 0: assigned to efifb --- If you then install the generic HWE kernel and reboot, you can see that fb0 is successfully summoned: --- 5.15.0-83-generic #92~20.04.1-Ubuntu SMP kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb [2.128815] pci :00:05.0: BAR 0: assigned to efifb [3.021819] efifb: probing for efifb [3.022511] efifb: framebuffer at 0xc000, using 6076k, total 6075k [3.023925] efifb: mode is 1920x1080x24, linelength=5760, pages=1 [3.025382] efifb: scrolling: redraw [3.026347] efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0 --- and finally, using linux-gcp-lts on 20.04, it does work (as it's 5.4): --- 5.4.0-1112-gcp #121-Ubuntu SMP kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb [0.834541] pci :00:05.0: BAR 0: assigned to efifb [1.057258] efifb: probing for efifb [1.058182] efifb: framebuffer at 0xc000, using 6076k, total 6075k [1.059210] efifb: mode is 1920x1080x24, linelength=5760, pages=1 [1.060203] efifb: scrolling: redraw [1.060722] efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0 --- So some linux-gcp backport or config seems to be breaking this. Supplementary to this, the framebuffer can not be leveraged by X and throws a fatal error around the time shadow is loaded. This part is replicable on -generic, as well as on debian using gdm3/X, so this is likely an upstream problem. I tried disabling shadow with an X conf, but as it uses 24bppp, it forces it. For the scope of this LP, we need to figure out the -gcp specific breakage. I've reached out to google to see if we can get some contacts on the virt mon team to push the other aspect forward. Replication: Launch any ubuntu 20.04+ GCE instance with the "Display Device" option enabled. Expected Behavior: We should see the above output in dmesg and also observe /dev/fb0 being created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2036273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970603] Re: DSI touchscreen not working with KMS under 5.15
This bug was fixed in the package linux-raspi - 6.5.0-1002.2 --- linux-raspi (6.5.0-1002.2) mantic; urgency=medium * mantic/linux-raspi: 6.5.0-1002.2 -proposed tracker (LP: #2033637) * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Miscellaneous Ubuntu changes - [Config] raspi: Add notes to configs that differ from master - [Config] raspi: Set CONFIG_ARM_ERRATA_=n - [Config] raspi: Set PREEMPT_DYNAMIC=y - [Config] raspi: Set STAGING_MEDIA_DEPRECATED=n - [Config] raspi: Set EFI=n - [Config] raspi: Set POWER_RESET_GPIO_RESTART=n - [Config] raspi: Set HID_BPF=n - [Config] raspi: Set COMMON_CLK_FIXED_MMIO=n - [Config] raspi: Set PWM_STMPE=n - [Config] raspi: Set LEDS_SYSCON=n - [Packaging] raspi: Include bcm2835_smi module in linux-modules - SAUCE: (no-up) Disable FIQ split-transaction FSM in dwc_otg * Miscellaneous upstream changes - drivers: media: imx296: Updated imx296 driver for external trigger - char: broadcom: vc_mem: Fix preprocessor conditional - drivers: dwc_otg: Fix fallthrough warnings - vc04_services/vc-sm-cma: Switch one-bit bitfields to bool - media: i2c: ov2311: Fix uninitialized variable usage - drm/panel: Fix default values for Waveshare 7.9 inch DSI touchscreen (#5565) - dtoverlays: Add i2c bus overrides to edt-ft5406 overlay - dtoverlays: Fix README text for i2c-fan - drivers: irqchip: irq-bcm2835: Concurrency fix - defconfigs: Add TINYDRM_ILI9486 to defconfigs - dtoverlays: Add drm option to piscreen overlay - drm/ili9486: Resolve clash in spi_device_id names - input: ads7846: Add missing spi_device_id strings - staging: bcm2835-codec: Downgrade the level for a debug message - configs: Raise 8250 UART limit to 5 on BCM2711 [ Ubuntu: 6.5.0-5.5 ] * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) [ Ubuntu: 6.5.0-4.4 ] * mantic/linux: 6.5.0-4.4 -proposed tracker (LP: #2034042) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) [ Ubuntu: 6.5.0-3.3 ] * mantic/linux: 6.5.0-3.3 -proposed tracker (LP: #2033904) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) * [23.10] Please test secure-boot and lockdown on the early 6.5 kernel (s390x) (LP: #2026833) - [Packaging] re-enable signing for s390x * Miscellaneous upstream changes - module/decompress: use vmalloc() for zstd decompression workspace [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * 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 * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Idem -Lenovo V15 64 AMN rz7520u -- 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/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das 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 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN 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/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Idem -Lenovo V15 64 AMN rz7520u -- 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/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das 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 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN 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/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036450] [NEW] Azure: Update CIFS to v6.5
Public bug reported: SRU Justification [Impact] Microsoft has requested this patch set to update CIFS and smbfs to the Linux kernel version 6.5. [Test Plan] Microsoft has tested with positive results. [Regression Potential] This is a huge patch set. The potential exists for corruption, connection instabilities, or other cifs related maladies. [Other Info] SF: #00365185 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** 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) -- 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/2036450 Title: Azure: Update CIFS to v6.5 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] Microsoft has requested this patch set to update CIFS and smbfs to the Linux kernel version 6.5. [Test Plan] Microsoft has tested with positive results. [Regression Potential] This is a huge patch set. The potential exists for corruption, connection instabilities, or other cifs related maladies. [Other Info] SF: #00365185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036348] Re: Firmware: failed to load intel/ibt-19-0-4.[sfi|ddc] linux-firmware 20230915.gitdfa11466-0ubuntu1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/2036348 Title: Firmware: failed to load intel/ibt-19-0-4.[sfi|ddc] linux-firmware 20230915.gitdfa11466-0ubuntu1 Status in linux-firmware package in Ubuntu: Confirmed Bug description: There is no files like *.ddc and *.sfi in /lib/firmware/intel/ afrer instalation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033295] Re: AMDGPU: Screen frequently and suddenly freezes. Hard reboot necessary. AMD Ryzen
Kernel >6.3 and amd_pstate=active (not needed for kernel >6.5) solves the problem on my Thinkpad P14s gen 3. -- 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/2033295 Title: AMDGPU: Screen frequently and suddenly freezes. Hard reboot necessary. AMD Ryzen Status in linux package in Ubuntu: Confirmed Bug description: Frequently, when I just use the computer, the mouse cursor freezes, the screen starts to flicker and freezes (screen flickers between entirely black and desktop visible). No interaction possible. In most cases Ctrl-Alt-Prnt-REISUB works to hard reboot the system. Frequency: Freezes happen several times a day. Unsaved work is lost. I noticed that: * The freezes usually happen when an external display is connected (it does not matter whether USB-C or HDMI). The freezes rarely happen when no external display is connected. * The freezes happen with Wayland and X11, with Ubuntu UI and Gnome Shell. * The freezes happen randomly, but I have the feeling that they happen more often when "something graphical" happens, e.g. when I go to the Gnome Shell overview, desktop switching, or when I switch to/from full screen mode, click on an image to scale it, or when I use map services in the web browser like Google Maps or radio.garden. * The freezes even more often happened when WebGL is active in Firefox or Chomium. * I encounter these annoying freezes already for several weeks. Having looked at the log files, I assume that AMDGPU is at the core of the problem. System: Ubuntu 23.04 (up to date), Wayland (freezes also happen with X11), Gnome 44.3. Linux 6.2.0-31-generic Lenovo ThinkPad T14s Gen 1 (with most recent BIOS/UEFI 1.44), AMD Ryzen™ 7 PRO 4750U with Radeon™ Graphics × 16. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-06-06 (813 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20UJS00K00 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=9eae73b3-aab9-4f80-9203-01ac00f03c33 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-31-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-11 (110 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2023 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET75W(1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UJS00K00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrR1CET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UJS00K00:pvrThinkPadT14sGen1:rvnLENOVO:rn20UJS00K00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UJ_BU_Think_FM_ThinkPadT14sGen1: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UJS00K00 dmi.product.sku: LENOVO_MT_20UJ_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998285] Re: 5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
still the same 5.15.0-84-generic. I don't want to swap kernel tree, just
a patch back-port.
--
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/1998285
Title:
5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
Status in linux package in Ubuntu:
Confirmed
Bug description:
from dmesg
1.313665] UBSAN: shift-out-of-bounds in
/build/linux-JjvoxS/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32
[1.313668] shift exponent 64 is too large for 64-bit type 'long long
unsigned int'
there is also a crash but i don't know if it's related.
1.313671] Call Trace:
[1.313672]
[1.313673] show_stack+0x52/0x5c
[1.313676] dump_stack_lvl+0x4a/0x63
[1.313678] dump_stack+0x10/0x16
[1.313679] ubsan_epilogue+0x9/0x49
[1.313680] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
[1.313682] initialize_nocpsch.cold+0x15/0x59 [amdgpu]
[1.313841] device_queue_manager_init+0x208/0x3b0 [amdgpu]
[1.313946] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu]
[1.314079] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu]
[1.314178] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu]
[1.314323] amdgpu_device_init.cold+0x25b/0x7db [amdgpu]
[1.314463] ? do_pci_enable_device+0xdb/0x110
[1.314466] amdgpu_driver_load_kms+0x1e/0x270 [amdgpu]
[1.314556] amdgpu_pci_probe+0x1ce/0x260 [amdgpu]
[1.314642] local_pci_probe+0x48/0x90
[1.314644] pci_device_probe+0x119/0x1f0
[1.314645] really_probe+0x21f/0x420
[1.314647] __driver_probe_device+0x119/0x190
[1.314648] driver_probe_device+0x23/0xc0
[1.314650] __driver_attach+0xbd/0x1f0
[1.314651] ? __device_attach_driver+0x120/0x120
[1.314652] bus_for_each_dev+0x7c/0xd0
[1.314654] driver_attach+0x1e/0x30
[1.314655] bus_add_driver+0x148/0x220
[1.314656] driver_register+0x95/0x100
[1.314657] __pci_register_driver+0x68/0x70
[1.314659] amdgpu_init+0x7c/0x1000 [amdgpu]
[1.314747] ? 0xc0fc
[1.314748] do_one_initcall+0x46/0x1e0
[1.314750] ? kmem_cache_alloc_trace+0x19e/0x2e0
[1.314752] do_init_module+0x52/0x260
[1.314753] load_module+0xb2b/0xbc0
[1.314754] __do_sys_finit_module+0xbf/0x120
[1.314756] __x64_sys_finit_module+0x18/0x20
[1.314757] do_syscall_64+0x59/0xc0
[1.314758] ? ksys_lseek+0x85/0xc0
[1.314759] ? exit_to_user_mode_prepare+0x37/0xb0
[1.314761] ? syscall_exit_to_user_mode+0x27/0x50
[1.314762] ? __x64_sys_lseek+0x18/0x20
[1.314763] ? do_syscall_64+0x69/0xc0
[1.314764] entry_SYSCALL_64_after_hwframe+0x61/0xcb
[1.314766] RIP: 0033:0x7fef87ab8a3d
[1.314767] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48
[1.314768] RSP: 002b:7fffe67aa7c8 EFLAGS: 0246 ORIG_RAX:
0139
[1.314770] RAX: ffda RBX: 55d1d00078a0 RCX:
7fef87ab8a3d
[1.314771] RDX: RSI: 7fef87c4f441 RDI:
0018
[1.314772] RBP: 0002 R08: R09:
0002
[1.314772] R10: 0018 R11: 0246 R12:
7fef87c4f441
[1.314773] R13: 55d1d002ea30 R14: 55d1d0011600 R15:
55d1d002eb10
[1.314774]
[1.314778]
gpu is Amd r 380 tonga 4Gb.
I was adviced to try 6.0 series of kernel and I dont see the ubsan error
there but I would like to get the fixes backported 5.15 series.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarkko 1322 F pulseaudio
/dev/snd/controlC1: jarkko 1322 F pulseaudio
CasperMD5json: {
CurrentDesktop: MATE
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-09-19 (71 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
MachineType: ASUS System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1007-oem
root=UUID=62a471af-17fd-40e2-9304-b3e113e4f47f ro quiet splash
ProcVersionSignature: Ubuntu 6.0.0-1007.7-oem 6.0.3
RelatedPackageVersions:
linux-restricted-modules-6.0.0-1007-oem N/A
linux-backports-modules-6.0.0-1007-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.7
Tags: vanessa
Uname: Linux 6.0.0-1007-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip
[Kernel-packages] [Bug 2030891] Re: In normal PC use, Nvidia crashes, laptop locks up
I think this is better and I change the setting this way, because the first setting makes the screen refresh continuously, when we turn that setting off, it only refreshes the changing parts of the screen, but when we do it this way "GRUB_CMDLINE_LINUX_DEFAULT="-- quiet splash i915.enable_dc=0"", we turn off the compression of the screen data, only the data of the changing places will be less, so the uncompressed data will be less -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/2030891 Title: In normal PC use, Nvidia crashes, laptop locks up Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: It constantly gives this error, and the laptop freezes, it can be recovered when I restart it with a sudden shutdown from the shutdown key, it gives this error again after a period of use when it is turned on, and the same cycle defatul@oleymod:~$ sudo journalctl Ağu 09 17:01:29 oleymod kernel: NVRM: GPU at PCI::01:00: GPU-ca032ef4-f159-7933-e230-6d4c17459dc1 Ağu 09 17:01:29 oleymod kernel: NVRM: Xid (PCI::01:00): 13, Graphics Exception: Shader Program Header 1 Error Ağu 09 17:01:29 oleymod kernel: NVRM: Xid (PCI::01:00): 13, Graphics Exception: Shader Program Header 2 Error Ağu 09 17:01:29 oleymod kernel: NVRM: Xid (PCI::01:00): 13, Graphics Exception: Shader Program Header 3 Error Ağu 09 17:01:29 oleymod kernel: NVRM: Xid (PCI::01:00): 13, Graphics Exception: Shader Program Header 4 Error Ağu 09 17:01:29 oleymod kernel: NVRM: Xid (PCI::01:00): 13, Graphics Exception: Shader Program Header 9 Error Ağu 09 17:01:29 oleymod kernel: NVRM: Xid (PCI::01:00): 13, Graphics Exception: Shader Program Header 18 Error Ağu 09 17:01:29 oleymod kernel: NVRM: Xid (PCI::01:00): 13, Graphics Exception: ESR 0x405840=0xa004021e Ağu 09 17:01:29 oleymod kernel: NVRM: Xid (PCI::01:00): 13, Graphics Exception: ChID 0009, Class 9197, Offset 2480, Data 1000 Ağu 09 17:01:30 oleymod kernel: sched: RT throttling activated Ağu 09 17:01:33 oleymod kernel: NVRM: Xid (PCI::01:00): 39, CCMDs 000a 90b5 defatul@oleymod:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.6 LTS Release: 20.04 Codename: focal defatul@oleymod:~$ uname -r 5.15.0-78-generic defatul@oleymod:~$ LANG=C nvidia-smi Wed Aug 9 18:05:49 2023 +-+ | NVIDIA-SMI 390.157Driver Version: 390.157 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GT 520M Off | :01:00.0 N/A | N/A | | N/A 41CP0N/A / N/A |404MiB / 964MiB | N/A Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| |0Not Supported | +-+ defatul@oleymod:~$ inxi -Fxz System:Kernel: 5.15.0-78-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.9 Distro: Ubuntu 20.04.6 LTS (Focal Fossa) Machine: Type: Laptop System: Micro-Star product: FX720/FX720DX v: REV:1.0 serial: Mobo: Micro-Star model: MS-1754 v: REV:1.0 serial: BIOS: American Megatrends v: E1754IMS.10K date: 04/29/2011 Battery: ID-1: BAT1 charge: 0.0 Wh condition: 0.0/48.8 Wh model: MSI Corp. MS-1727 status: Full CPU: Topology: Dual Core model: Intel Core i5-2410M bits: 64 type: MT MCP arch: Sandy Bridge rev: 7 L2 cache: 3072 KiB flags: avx lm nx pae sse
[Kernel-packages] [Bug 2032164] Re: A general-proteciton exception during guest migration to unsupported PKRU machine
We have now confirmed at three different locations that Live-Migration from PKRU PRE-5.15.0-85.95 to PKRU 5.15.0-85.95 compute nodes breaks. -- 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 2036456] Re: linux-firmware mantic missing intel/ibt-{19, 20}*
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (Ubuntu)
Status: New => Confirmed
--
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/2036456
Title:
linux-firmware mantic missing intel/ibt-{19,20}*
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
linux-firmware on mantic (20230915.gitdfa11466-0ubuntu1) is missing
/intel/ibt-{19,20}-*
firmwares. When booting I get the following error message:
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Bootloader revision 0.1
build 0 week 30 2018
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Device revision is 2
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Secure boot is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: OTP lock is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: API lock is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Debug lock is disabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Minimum firmware build 1
week 10 2014
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Failed to load Intel
firmware file intel/ibt-19-0-1.sfi (-2)
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Reading supported
features failed (-56)
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Error reading debug
features
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Failed to read MSFT
supported features (-56)
Hardware used is:
ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036456/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
Hi @juergh, more and more users got affected, we step back to 6.1 as a workaround. What is the state of the patch we tested (see #24). Thanks! -- 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/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen 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: Confirmed Status in linux source package in Lunar: Confirmed Bug description: [Impact] After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. [Fix] Updated patch from linux-next: https://patchwork.freedesktop.org/patch/538562/ [Test Case] Suspend,resume,shutdown,reboot should all work correctly. No nouveau stack trace in the kernel log. [Where Problems Could Occur] Limited to nouveau driver that wants to load nonexistent ACR firmware. Only nvidia GPUs are affected. [Additional information] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036342] Re: no sound cards found afer kernel update from 6.2.0-26 to 6.2.0-32
Hm. Is this the only thing that's not working after the upgrade? What about bluetooth and wifi? ** Package changed: linux-signed-hwe-6.2 (Ubuntu) => linux-hwe-6.2 (Ubuntu) -- 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/2036342 Title: no sound cards found afer kernel update from 6.2.0-26 to 6.2.0-32 Status in linux-hwe-6.2 package in Ubuntu: New Bug description: After the update from kernel 6.2.0-26 to 6.2.0-32 under Ubuntu 22.04 LTS, there are no more sound cards found. I can reliably reproduce this by switching in the grub boot menu between the kernel versions. I used sound over HDMI of the NVIDIA Corporation GP108 [GeForce GT 1030] and it used to use the module snd_hda_intel. Now, a symptom is that `aplay -l` reports "no soundcards found", and neither does any other program. I had similar problems after the Ubuntu update from 5.19.0-43 to 5.19.0-45. I reported this to the offical linux kernel mailinglist yesterday ( https://bugzilla.kernel.org/show_bug.cgi?id=217917 ). They have sent me here. Indeed, I now tried the vanilla "mainline" kernels 6.2.0-rc8 and 6.5.3 - and there the sound cards are correctly found. I am attaching logfiles and info from /proc for the different tried kernel version that are hopefully useful. Please let me know if there is more info I can provide or things I could try to narrow down the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic (not installed) ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Sep 17 09:52:19 2023 InstallationDate: Installed on 2023-04-16 (153 days ago) InstallationMedia: Kubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) 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-hwe-6.2/+bug/2036342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Ok, skimmed through the changelog, and looks like the .zstd compression
is expected.
The issue seems to be that in my case, it's expecting to find
intel/ibt-19-0-4.sfi, but that's no longer included - with or without a
.zstd suffix. Seems we no longer include anything above ibt-18-{xxx}.
https://packages.ubuntu.com/mantic/amd64/linux-firmware/filelist (goes
from ibt-18-2 to ibt-hw)
vs
https://packages.ubuntu.com/lunar/amd64/linux-firmware/filelist (several
ibt-19-{xxx} and ibt-20-{xxx} files between ibt-18-2 and the ibt-hw
files)
--
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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
** Also affects: broadcom-sta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Confirmed Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032985] Re: Wifi works in kernel 5.19.0-46, but not in kernel 6.2.0-26 (Intel AX211)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-hwe-6.2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2032985 Title: Wifi works in kernel 5.19.0-46, but not in kernel 6.2.0-26 (Intel AX211) Status in linux-meta-hwe-6.2 package in Ubuntu: Confirmed Bug description: I am using Ubuntu 22.04.3 LTS When I updated my system and installed the new kernel (6.2.0-26), my wifi ceased to work at all, and I cannot find any way to solve this issue. I have tried the oem kernels to no avail (all versions were between 5.19.0-46 and 6.2.0-26) I have tried booting to the ubuntu 22.04.3 LTS livecd, and wifi did work in that. I even tried copying the firmware from that into my system, and that did not resolve the issue. Looking though the dmesg, I can see that when it would load cfg80211 on 5.19, it throws a trace on 6.2. the output of `dmesg` is attached. Also, in lspci, it does not say my wireless network controller has a driver in use, whereas it does on 5.19. It used to not even acknowledge the iwlwifi module, but after a purge and reinstall of all 6.2 packages, it does now show up. the output of `lspci -k` is also attached. I also included the output of `sudo journalctl -b` for completeness, and it contains the output of the service systemd-modules- load.service, which contains the line "systemd-modules-load[1404]: Failed to insert module 'iwlwifi': Invalid argument" I should also note that I have a friend who has the same laptop as I do, and was using the same version of Ubuntu, and they had faced this same problem as well due to the same causes. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-iwlwifi-generic-hwe-22.04 6.2.0.26.26~22.04.7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 24 16:17:33 2023 InstallationDate: Installed on 2022-11-29 (268 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-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-meta-hwe-6.2/+bug/2032985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015314] Re: Ubuntu 22.04 does not restore the screen on a KVM switch
I am experiencing the same issue. I have two laptops, one MacBook Air and one Dell Inspiron with Ubuntu 22.04. I constantly need to switch the monitor between these two. I have an HDMI switcher which used to work great on Ubuntu 20.04. But now with Ubuntu 22.04 it is not possible. Ubuntu is able to display the picture on the monitor only after plugging the HDMI in. After I switch to Mac, I am unable to switch back to Ubuntu. I guess this must have something to do with how KVM and HDMI switchers work. Maybe they don't disconnect the inactive device entirely and, as a result, switching back to Ubuntu does not trigger the same behavior that connecting the HDMI cable does? It's important to note that after switching the HDMI from Ubuntu to Mac, Ubuntu is fully aware that HDMI has been disconnected and the external monitor is not detected. But still it never gets detected again. -- 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/2015314 Title: Ubuntu 22.04 does not restore the screen on a KVM switch Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 on either of two HP small business PC. 1. an HP EliteDesk 800 G3 Mini PC with an i915 video controller using Displayport to HDMI. 2. an HP 600 G1 desktop SFF with an i915 video controller, also using Displayport to HDMI. Both are connected to a KVM switch. When I boot up I get a login and everything works fine, until I switch between them. No image appears. There is a slight brightening of the display after a few seconds, as if it's trying to enable video output, but I have to unplug and replug the displayport connector at the back of the computer to get the screen to come back. journalctl -k shows these lines logged on the HP 600 G1: Apr 04 20:55:42 demesne kernel: i915 :00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 20 Apr 04 20:55:42 demesne kernel: i915 :00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 20 on the EliteDesk 800 G3, the same message: Apr 04 20:55:58 haven kernel: i915 :00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 20 https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+filebug/e70d8b1a-d357-11ed-b7a8-d485646cd9a4? https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+filebug/26e2b774-d358-11ed-99a2-40a8f0305cb4? Both systems are Ubuntu 22.04.2 LTS --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1719 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-05 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP EliteDesk 800 G3 DM 35W Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=69e670cd-6996-4cc1-bdb0-bdc9e857503e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 Tags: wayland-session jammy Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/27/2020 dmi.bios.release: 2.34 dmi.bios.vendor: HP dmi.bios.version: P21 Ver. 02.34 dmi.board.name: 829A dmi.board.vendor: HP dmi.board.version: KBC Version 06.29 dmi.chassis.type: 35 dmi.chassis.vendor: HP dmi.ec.firmware.release: 6.41 dmi.modalias: dmi:bvnHP:bvrP21Ver.02.34:bd04/27/2020:br2.34:efr6.41:svnHP:pnHPEliteDesk800G3DM35W:pvr:rvnHP:rn829A:rvrKBCVersion06.29:cvnHP:ct35:cvr:sku4DS57UC#ABA: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G3 DM 35W dmi.product.sku: 4DS57UC#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
In Ubuntu we recommend to only install broadcom-sta-dkms. It ships modprobe.d snippet that does prevent automatic loading of b43 driver. # cat /etc/modprobe.d/broadcom-sta-dkms.conf # wl module from Broadcom conflicts with the following modules: blacklist b43 blacklist b43legacy blacklist b44 blacklist bcma blacklist brcm80211 blacklist brcmsmac blacklist ssb broadcom-sta-source doesn't do anything but does reocmmend module- assistant, if one uses that it probably is best to switch to the dkms package. Separately broadcom-sta-common is provided that could be installed together with boradcom-sta-source to also gain the blacklist modprobe.d. Not quite sure what is the point there, maybe we can make broadcom-sta-source depends on broadcom-sta-common, or simply remove it. My expectation was that this is all solved already back in lunar =/ Shall I ship modprobe.d snippet in more places? and have initramfs hook to ensure initramfs is regenerated with updated modprobe.d? What's wrong with the gui that seems to not show things correctly? ** Changed in: ubuntu-drivers-common (Ubuntu Lunar) Status: Confirmed => Incomplete ** Changed in: ubuntu-drivers-common (Ubuntu Mantic) Status: Confirmed => 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/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000228] Re: Add initial support for Mediatek Genio boards
** Patch added: "mantic.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+attachment/5701892/+files/mantic.debdiff -- 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: New 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 2000228] Re: Add initial support for Mediatek Genio boards
** Patch added: "lunar.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+attachment/5701894/+files/lunar.debdiff -- 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: New 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 2000228] Re: Add initial support for Mediatek Genio boards
Test builds for jammy, lunar, and mantic: https://launchpad.net/~ethan.hsieh/+archive/ubuntu/sru-test/+packages ** Patch added: "jammy.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+attachment/5701895/+files/jammy.debdiff -- 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: New 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
