[Kernel-packages] [Bug 2049603] Re: nvidia-dkms-535 FTBS on noble with the latest 6.7 kernel on arm64
The same problem happens also with nvidia-dkms-545 (still on arm64
only).
** Also affects: nvidia-graphics-drivers-545 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2049603
Title:
nvidia-dkms-535 FTBS on noble with the latest 6.7 kernel on arm64
Status in nvidia-graphics-drivers-535 package in Ubuntu:
New
Status in nvidia-graphics-drivers-545 package in Ubuntu:
New
Status in nvidia-graphics-drivers-535 source package in Noble:
New
Status in nvidia-graphics-drivers-545 source package in Noble:
New
Bug description:
[Impact]
It looks like nvidia-dkms-535 is using a symbol that became GPL-only
in the latest 6.7 kernel, causing the following build error:
# MODPOST <>/build/nvidia/535.146.02/build/Module.symvers
scripts/mod/modpost -M -m -a -o
<>/build/nvidia/535.146.02/build/Module.symvers -T
<>/build/nvidia/535.146.02/build/modules.order -i Module.symvers -e
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'screen_info'
This change was introduced by: b8466fe82b79 ("efi: move screen_info
into efi init code")
This happens only on arm64, where the symbol is defined.
[Fix]
Avoid using screen_info in the nvidia-dkms-535 driver.
[Regression potential]
We may disable certain features in the 535 driver, or even have an
unusable driver, unless a proper workaround/solution is provided.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2049603/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049634] Re: SMB 1 broken in kernel 6.5.0.14.14~22.04.7
Today I temporarily reverted back to Kernel 6.2.0-39-generic, by choosing it from the Grub bootloader, and the SMB 1.0 network shares started working correctly again. I think it is clear that Kernel 6.5 is broken in this respect. Fortunately, package linux-image-6.2.0-39-generic is still installed. Package linux-image-5.15.0-91-generic is also there. I am worried that the 6.2 Kernel version will get kicked out on the next system update. I am guessing that the system will automatically keep the original 5.15 kernel series and the new 6.5, but not the 6.2 series. In the past years, updating the system failed a couple of times because the /boot partition was full, which I guess it is some kind of Ubuntu shortcoming, as my installation was nothing out of the ordinary. I had to manually delete some kernel-related packages. These memories reminded me that the space for old kernels is limited, so that the 6.2 version may get automatically kicked out the next time around. And version 5.15 is too old, I wonder what kind of problems that might cause in my system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049634 Title: SMB 1 broken in kernel 6.5.0.14.14~22.04.7 Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Hi all: I upgraded my Ubuntu yesterday and automatically got the newer Linux Kernel version 6.5.0-14-generic #14~22.04.1-Ubuntu. Previously, I was running kernel version 6.2 . I still have a legacy system on the network using SMB protocol version 1.0. With the new kernel version, copying files does not work reliably anymore. Some random byte blocks in the destination files are overwritten with binary zeros. It happens quite often. This is not the first time the Linux guys temporarily break SMB protocol version 1.0, see for example this bug report of mine: https://bugs.launchpad.net/ubuntu/+bug/2033732 I checked package linux-image-generic-hwe-22.04 with Synaptic, and now it lists just 2 versions: 6.5.0.14.14~22.04.7 (jammy-updates) 5.15.0.25.27 (jammy) Is there a way to go back to the latest 6.2 kernel version? How do I prevent Ubuntu from upgrading to 6.5 next time around? I have searched the Internet, but I haven't found yet a usable answer. I don't want to go back all the way to Kernel 5.15 if I can avoid it. Thanks in advance, rdiez To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2049634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049579] Re: package linux-lowlatency-tools-6.6.0-14 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in package
*** This bug is a duplicate of bug 2035971 *** https://bugs.launchpad.net/bugs/2035971 ** This bug has been marked a duplicate of bug 2035971 linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2049579 Title: package linux-lowlatency-tools-6.6.0-14 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in package linux- tools-6.6.0-14 6.6.0-14.14 Status in linux-lowlatency package in Ubuntu: New Bug description: aptitude -> update -> upgrade all upgradable packages -> dpkg fails because of conflict with linux-tools-generic ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-lowlatency-tools-6.6.0-14 (not installed) ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu6 AptOrdering: linux-lowlatency-tools-6.6.0-14:amd64: Install linux-tools-6.6.0-14-lowlatency:amd64: Install linux-tools-lowlatency:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Jan 17 00:18:22 2024 DpkgTerminalLog: Preparing to unpack .../linux-lowlatency-tools-6.6.0-14_6.6.0-14.14.1_amd64.deb ... Unpacking linux-lowlatency-tools-6.6.0-14 (6.6.0-14.14.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-lowlatency-tools-6.6.0-14_6.6.0-14.14.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in package linux-tools-6.6.0-14 6.6.0-14.14 DuplicateSignature: package:linux-lowlatency-tools-6.6.0-14:(not installed) Unpacking linux-lowlatency-tools-6.6.0-14 (6.6.0-14.14.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-lowlatency-tools-6.6.0-14_6.6.0-14.14.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in package linux-tools-6.6.0-14 6.6.0-14.14 ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in package linux-tools-6.6.0-14 6.6.0-14.14 InstallationDate: Installed on 2023-11-18 (60 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.2ubuntu2 apt 2.7.6 SourcePackage: linux-lowlatency Title: package linux-lowlatency-tools-6.6.0-14 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in package linux-tools-6.6.0-14 6.6.0-14.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/2049579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043905] Re: VT6307 IEEE1394 card causes reboot loop
** Changed in: linux Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043905 Title: VT6307 IEEE1394 card causes reboot loop Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Committed Bug description: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2043905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043905]
A solution has been committed for this: https://github.com/torvalds/linux/commit/ac9184fbb8478dab4a0724b279f94956b69be827 -- 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/2043905 Title: VT6307 IEEE1394 card causes reboot loop Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Committed Bug description: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2043905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049184] Re: iwlwifi leads to system randomly hangs after suspend
** Tags added: originate-from-2047019 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049184 Title: iwlwifi leads to system randomly hangs after suspend Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The system randomly hangs while doing s2idle test. [Fix] Intel found the issue and provided a fix. https://patchwork.kernel.org/project/linux-wireless/patch/2024045954.2d2b8b870194.I14ed76505a5cf87304e0c9cc05cc0ae85ed3bf91@changeid/ [Test case] Boot up the system and run the s2idle test around 1000 times sudo fwts s3 --s3-multiple=1000 [Where problems could occur] The fix is trivial and should no introduce any issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049708] Re: bluez bluetoothd unable to locate executable
Perhaps try a recursive grep for '/usr/lib/bluetooth/bluetoothd' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049708 Title: bluez bluetoothd unable to locate executable Status in bluez package in Ubuntu: New Bug description: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049676] Re: `iwlist scan` crashes iwlwifi with a "Microcode SW error detected. Restarting 0x0." message
** Tags added: kern-8933 -- 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/2049676 Title: `iwlist scan` crashes iwlwifi with a "Microcode SW error detected. Restarting 0x0." message Status in linux-firmware package in Ubuntu: New Bug description: Ubuntu 22.04.3 on a Lenovo ThinkPad X1 Carbon Gen 11 Kernel: 6.5 (official), 6.6 and 6.7 (mainline) Running `iwlist scan` as root produces an error message like: wlp0s20f3 Interface doesn't support scanning : Input/output error while the crash can be seen in the dmesg output below. The network card is: 00:14.3 Network controller [0280]: Intel Corporation Device [8086:51f1] (rev 01) Subsystem: Intel Corporation Device [8086:0090] Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 10 Memory at 603d1d4000 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Latency Tolerance Reporting Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0 Len=014 Kernel driver in use: iwlwifi Kernel modules: iwlwifi dmesg output: [ 23.883032] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 23.883184] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 23.883189] iwlwifi :00:14.3: Transport status: 0x004B, valid: 6 [ 23.883195] iwlwifi :00:14.3: Loaded firmware version: 83.e8f84e98.0 so-a0-gf-a0-83.ucode [ 23.883200] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [ 23.883205] iwlwifi :00:14.3: 0x02F0 | trm_hw_status0 [ 23.883209] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 23.883212] iwlwifi :00:14.3: 0x004DB338 | branchlink2 [ 23.883215] iwlwifi :00:14.3: 0x004DA866 | interruptlink1 [ 23.883219] iwlwifi :00:14.3: 0x004DA866 | interruptlink2 [ 23.883221] iwlwifi :00:14.3: 0x000157E2 | data1 [ 23.883225] iwlwifi :00:14.3: 0x0010 | data2 [ 23.883228] iwlwifi :00:14.3: 0x | data3 [ 23.883231] iwlwifi :00:14.3: 0x1F409941 | beacon time [ 23.883234] iwlwifi :00:14.3: 0x7ACBC6C4 | tsf low [ 23.883237] iwlwifi :00:14.3: 0x034B | tsf hi [ 23.883240] iwlwifi :00:14.3: 0x | time gp1 [ 23.883243] iwlwifi :00:14.3: 0x0112D254 | time gp2 [ 23.883247] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 23.883250] iwlwifi :00:14.3: 0x0053 | uCode version major [ 23.883253] iwlwifi :00:14.3: 0xE8F84E98 | uCode version minor [ 23.883256] iwlwifi :00:14.3: 0x0370 | hw version [ 23.883259] iwlwifi :00:14.3: 0x00480002 | board version [ 23.883262] iwlwifi :00:14.3: 0x8076FF00 | hcmd [ 23.883265] iwlwifi :00:14.3: 0x0002 | isr0 [ 23.883268] iwlwifi :00:14.3: 0x | isr1 [ 23.883270] iwlwifi :00:14.3: 0x48F04002 | isr2 [ 23.883274] iwlwifi :00:14.3: 0x00C3008C | isr3 [ 23.883276] iwlwifi :00:14.3: 0x | isr4 [ 23.883279] iwlwifi :00:14.3: 0x0518001C | last cmd Id [ 23.883282] iwlwifi :00:14.3: 0x000157E2 | wait_event [ 23.883285] iwlwifi :00:14.3: 0x | l2p_control [ 23.883288] iwlwifi :00:14.3: 0x | l2p_duration [ 23.883291] iwlwifi :00:14.3: 0x | l2p_mhvalid [ 23.883294] iwlwifi :00:14.3: 0x | l2p_addr_match [ 23.883297] iwlwifi :00:14.3: 0x0018 | lmpm_pmg_sel [ 23.883300] iwlwifi :00:14.3: 0x | timestamp [ 23.883303] iwlwifi :00:14.3: 0xF0B4 | flow_handler [ 23.883386] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 23.883389] iwlwifi :00:14.3: Transport status: 0x004B, valid: 7 [ 23.883393] iwlwifi :00:14.3: 0x20103609 | ADVANCED_SYSASSERT [ 23.883397] iwlwifi :00:14.3: 0x | umac branchlink1 [ 23.883400] iwlwifi :00:14.3: 0x80471ABC | umac branchlink2 [ 23.883403] iwlwifi :00:14.3: 0xC0081892 | umac interruptlink1 [ 23.883406] iwlwifi :00:14.3: 0x | umac interruptlink2 [ 23.883409] iwlwifi :00:14.3: 0x0027 | umac data1 [ 23.883412] iwlwifi :00:14.3: 0x0001 | umac data2 [ 23.883414] iwlwifi :00:14.3: 0x | umac data3 [ 23.883417] iwlwifi :00:14.3: 0x0053 | umac major [ 23.883420] iwlwifi :00:14.3: 0xE8F84E98 | umac minor [ 23.883423] iwlwifi :00:14.3: 0x0112D24E | frame pointer [ 23.883426] iwlwifi :00:14.3: 0xC0886C08 | stack pointer [ 23.883429] iwlwifi :00:14.3: 0x0085010D | last host cmd [ 23.883432] iwlwifi
[Kernel-packages] [Bug 2049708] Re: bluez bluetoothd unable to locate executable
You are not. I have rebooted multiple times and continue to get this message in journalctl (yes it's a new entry on each boot). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049708 Title: bluez bluetoothd unable to locate executable Status in bluez package in Ubuntu: New Bug description: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049358] Re: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1
** Tags added: originate-from-2047612 -- 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/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049184] Re: iwlwifi leads to system randomly hangs after suspend
** Tags added: originate-from-2047368 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049184 Title: iwlwifi leads to system randomly hangs after suspend Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The system randomly hangs while doing s2idle test. [Fix] Intel found the issue and provided a fix. https://patchwork.kernel.org/project/linux-wireless/patch/2024045954.2d2b8b870194.I14ed76505a5cf87304e0c9cc05cc0ae85ed3bf91@changeid/ [Test case] Boot up the system and run the s2idle test around 1000 times sudo fwts s3 --s3-multiple=1000 [Where problems could occur] The fix is trivial and should no introduce any issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047184] Re: Audio device is not available, instead it shows dummy output in the settings
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047184 Title: Audio device is not available, instead it shows dummy output in the settings Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Audio device is not available, instead it shows dummy output in the settings [Fix] SOF driver looks for a config which both sample width and valid bits are both 32 bits. However, the config in NHLT table is 32-bit sample width and 24-bit valid bits. Should ignore the valid bits in NHLT when the sample width is 32 bits. Confirmed the below commit in v6.7-rc4 fix the issue 7b4c93a50a2e ALSA: hda: intel-nhlt: Ignore vbps when looking for DMIC 32 bps format [Test case] 1. check audio input/output on the system 2. System can play and record audio normally [Where problems could occur] When the samples assumed to be vbps=32 then the 'noise' introduced by the lower two bits (channel number) have no real life implication on audio quality. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047398] Re: Add missing RPL P/U CPU IDs
** Tags removed: verification-needed-jammy-linux-oem-6.5 verification-needed-mantic-linux ** Tags added: verification-done-jammy-linux-oem-6.5 verification-done-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047398 Title: Add missing RPL P/U CPU IDs Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Without the correct GPU ID in the driver, the system will default to framebuffer mode, and some graphics functions may not work properly. [Fix] Below commit included in v6.7-rc1 adds the missing IDs 5d5fea7c79a7 drm/i915/rpl: Update pci ids for RPL P/U [Test case] 1. check the system with GPU ID A7AC or A7AD 2. boot the system into desktop and connecting a monior by HDMI cable with HDMI port or Type-C port 3. make sure the external monitor works [Where problems could occur] Add only IDs; there is no potential for regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047461] Re: drm: Update file owner during use
** Tags removed: verification-needed-jammy-linux-oem-6.5 verification-needed-mantic-linux ** Tags added: verification-done-jammy-linux-oem-6.5 verification-done-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047461 Title: drm: Update file owner during use Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Our testing tools need to check the app runs on which GPU, and now it only shows the processes as Xorg or XWayland $ cat /sys/kernel/debug/dri/0/clients command pid dev master a uid magic Xorg 2344 0 yy 0 0 Xorg 2344 0 ny 0 2 Xorg 2344 0 ny 0 3 Xorg 2344 0 ny 0 4 [Fix] The commit from v6.7-rc1 fixes the issue $ cat /sys/kernel/debug/dri/0/clients command tgid dev master a uid magic Xorg 830 0 yy 0 0 xfce4-session 880 0 ny 0 1 xfwm4 943 0 ny 0 2 neverball 1095 0 ny 0 3 [Test case] 1. check processes by 'cat /sys/kernel/debug/dri/0/clients' 2. runs glxgears(specify the GPU if needed) 3. check the precesses again and there should be a 'glxgears' process [Where problems could occur] This commit added some protections on read/write and only changes the process' pid, the worst case is that the process got the wrong pid as its owner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049184] Re: iwlwifi leads to system randomly hangs after suspend
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049184 Title: iwlwifi leads to system randomly hangs after suspend Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The system randomly hangs while doing s2idle test. [Fix] Intel found the issue and provided a fix. https://patchwork.kernel.org/project/linux-wireless/patch/2024045954.2d2b8b870194.I14ed76505a5cf87304e0c9cc05cc0ae85ed3bf91@changeid/ [Test case] Boot up the system and run the s2idle test around 1000 times sudo fwts s3 --s3-multiple=1000 [Where problems could occur] The fix is trivial and should no introduce any issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049327] Re: `alsactl init` unable to initialze audio device on G700
Thank you @seb128 . We don't currently have an explicit need to SRU to Lunar. And I think skip '.10' is a mistake. :) -- 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/2049327 Title: `alsactl init` unable to initialze audio device on G700 Status in alsa-ucm-conf package in Ubuntu: Fix Released Bug description: [Impact] This bug cause "alsactl init" command unable to initialize mt8390-evk correctly and print these error message: ``` ceqa@ubuntu:/home/ceqa$ alsactl init alsa-lib main.c:761:(execute_sequence) unable to execute cset 'name='DP_OUT_MUX' Disconnect' alsa-lib main.c:2373:(set_boot_user) Unable to execute boot sequence Found hardware: "mt8390-evk" "" "" "" "" Hardware is initialized using a generic method ``` Thus, the audio devices on MediaTek G700 do not work. This patch fix this bug by correcting 'DP_OUT_MUX' to 'DPTX_OUT_MUX'. [ Test Plan ] Reproduce: 1. Install Ubuntu 22.04 (jammy) on a MediaTek G700 device 2. Run `alsactl init` on MediaTek G700 device 3. alsactl print error message "unable to execute cset 'name='DP_OUT_MUX' Disconnect'" and audio devices do not work. Verify: By applying this patch, alsactl does not print this error message and audio devices work. [Where problems could occur] This patch fix the typo in ucm files, and it affects the device init process on Mediatek Genio boards. [ Other Info ] There is a typo in 'd/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch'. The name of the flag that controls the audio output of the DP port is not 'DP_OUT_MUX'. It is 'DPTX_OUT_MUX'. MediaTek fix this issue in the PR in upstream: https://github.com/alsa-project/alsa-ucm-conf/compare/243f2d60740e41a0cfb7779388c17e4a00e1bfe9..a55f840ab2b13f32cb55cd1730933ef0f5a96079 mt8390-evk (G700) Pull Request: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2049327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049708] Re: bluez bluetoothd unable to locate executable
Am I correct in assuming the problem goes away after a reboot? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049708 Title: bluez bluetoothd unable to locate executable Status in bluez package in Ubuntu: New Bug description: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049708] Re: bluez bluetoothd unable to locate executable
5.71-1ubuntu3: Binary: /usr/libexec/bluetooth/bluetoothd SystemD: system/bluetooth.service:ExecStart=/usr/libexec/bluetooth/bluetoothd So that's consistent, but it sounds like you might have encountered an upgrade bug and your systemd was looking in the old path? I'm guessing there should be a systemd mechanism for refreshing bluetooth.service contents that doesn't require a full system reboot, but also I never encountered this bug in testing recent bluez updates. ** Tags added: noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049708 Title: bluez bluetoothd unable to locate executable Status in bluez package in Ubuntu: New Bug description: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
Hi... could you provide a patch to backport 65248a9a9ee1 perf/x86/uncore: Add a quirk for UPI on SPR To 5.15? I started and it became a bit of a rabbit hole trying to figure out the prerequisite patches for that one which has merge conflicts when trying to cherry pick it. ** Changed in: intel Assignee: Jeff Lane (bladernr) => (unassigned) ** Changed in: linux (Ubuntu) Assignee: Jeff Lane (bladernr) => (unassigned) ** Changed in: linux (Ubuntu Jammy) Assignee: Jeff Lane (bladernr) => (unassigned) ** Changed in: intel Status: In Progress => Confirmed ** Changed in: linux (Ubuntu) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049637 Title: Some SPR systems throw kernel warnings from uncore_discovery.c Status in intel: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Bug description: [Impact] On some Sapphire Rapids CPUs we are seeing Kernel warnings in the kern.log: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] Code: c2 01 48 83 c0 04 39 d1 0f 8e c6 01 00 00 49 8b 4c 24 38 8b 0c 01 41 89 0c 07 49 8b 74 24 40 8b 34 06 41 89 34 06 39 f9 75 cf <0f> 0b 4c 89 ff e8 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ?
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) -- 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/2049637 Title: Some SPR systems throw kernel warnings from uncore_discovery.c Status in intel: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] On some Sapphire Rapids CPUs we are seeing Kernel warnings in the kern.log: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] Code: c2 01 48 83 c0 04 39 d1 0f 8e c6 01 00 00 49 8b 4c 24 38 8b 0c 01 41 89 0c 07 49 8b 74 24 40 8b 34 06 41 89 34 06 39 f9 75 cf <0f> 0b 4c 89 ff e8 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ? type_pmu_register+0x42/0x42 Oct 31 03:35:55 N8 kernel: [ 95.500506] do_one_initcall+0x46/0x1e0 Oct 31 03:35:55 N8 kernel: [ 95.546475] do_initcalls+0x12f/0x159 Oct 31 03:35:55 N8 kernel: [ 95.590372] kernel_init_freeable+0x162/0x1b5 Oct 31 03:35:55 N8 kernel: [ 95.642556] ? rest_init+0x100/0x100 Oct 31 03:35:55 N8 kernel: [ 95.685405] kernel_init+0x1b/0x150 Oct 31 03:35:55 N8 kernel: [ 95.727228] ? rest_init+0x100/0x100 Oct 31
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- 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/2049637 Title: Some SPR systems throw kernel warnings from uncore_discovery.c Status in intel: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] On some Sapphire Rapids CPUs we are seeing Kernel warnings in the kern.log: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] Code: c2 01 48 83 c0 04 39 d1 0f 8e c6 01 00 00 49 8b 4c 24 38 8b 0c 01 41 89 0c 07 49 8b 74 24 40 8b 34 06 41 89 34 06 39 f9 75 cf <0f> 0b 4c 89 ff e8 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ? type_pmu_register+0x42/0x42 Oct 31 03:35:55 N8 kernel: [ 95.500506] do_one_initcall+0x46/0x1e0 Oct 31 03:35:55 N8 kernel: [ 95.546475] do_initcalls+0x12f/0x159 Oct 31 03:35:55 N8 kernel: [ 95.590372] kernel_init_freeable+0x162/0x1b5 Oct 31 03:35:55 N8 kernel:
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
** Changed in: intel Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: intel Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: intel Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049637 Title: Some SPR systems throw kernel warnings from uncore_discovery.c Status in intel: In Progress Status in linux package in Ubuntu: In Progress Bug description: [Impact] On some Sapphire Rapids CPUs we are seeing Kernel warnings in the kern.log: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] Code: c2 01 48 83 c0 04 39 d1 0f 8e c6 01 00 00 49 8b 4c 24 38 8b 0c 01 41 89 0c 07 49 8b 74 24 40 8b 34 06 41 89 34 06 39 f9 75 cf <0f> 0b 4c 89 ff e8 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ? type_pmu_register+0x42/0x42 Oct 31 03:35:55 N8 kernel: [ 95.500506] do_one_initcall+0x46/0x1e0 Oct 31 03:35:55 N8 kernel: [ 95.546475] do_initcalls+0x12f/0x159 Oct 31 03:35:55 N8 kernel: [ 95.590372]
[Kernel-packages] [Bug 2045622] Re: RTL8852CE WIFI read country list supporting 6 GHz from BIOS
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2045622 Title: RTL8852CE WIFI read country list supporting 6 GHz from BIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] Realtek provides a patchset to enable this feature https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t The patchset has been included in linux-next/master c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] Run `iw list` should see the available frequency above 6Ghz, even it's disabled Frequencies: ... * 6835 MHz [177] (disabled) * 6855 MHz [181] (disabled) * 6875 MHz [185] (disabled) * 6895 MHz [189] (disabled) * 6915 MHz [193] (disabled) * 6935 MHz [197] (disabled) * 6955 MHz [201] (disabled) * 6975 MHz [205] (disabled) * 6995 MHz [209] (disabled) * 7015 MHz [213] (disabled) * 7035 MHz [217] (disabled) * 7055 MHz [221] (disabled) * 7075 MHz [225] (disabled) * 7095 MHz [229] (disabled) * 7115 MHz [233] (disabled) [Where problems could occur] Should have some impact to current RTL devices, but didn't see any fix patches for the 3 commits now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049697] Re: GPU not being detected when I try to run any game
Thanks for the bug report. It looks like the i915 kernel graphics driver is crashing a lot, which may or may not be related. Please run these commands in a Terminal: sudo apt install mesa-utils glxinfo > glxinfo.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu) ** Summary changed: - GPU not being detected when I try to run any game + [i915] GPU not being detected when I try to run any game ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Incomplete -- 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/2049697 Title: [i915] GPU not being detected when I try to run any game Status in linux-hwe-6.2 package in Ubuntu: Incomplete Bug description: I ran ran apport-bug xorg and it took me here. Trying to figure out an issue where any time I open a game, it crashes and gives the error message "GPU not detected". From everything I've tried it seems like the computer has no problem detecting the GPU and it seems to be working fine, but games are still not working. Any help is appreciated! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 18:34:19 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.2.0-35-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:0d22] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:0122] InstallationDate: Installed on 2023-10-25 (84 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. iMac14,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic root=UUID=773b635d-a617-4aa4-8333-273b3ed7b502 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 146.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-031B6874CF7F642A dmi.board.vendor: Apple Inc. dmi.board.version: iMac14,1 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-031B6874CF7F642A dmi.modalias: dmi:bvnAppleInc.:bvr146.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pniMac14,1:pvr1.0:rvnAppleInc.:rnMac-031B6874CF7F642A:rvriMac14,1:cvnAppleInc.:ct13:cvrMac-031B6874CF7F642A:skuSystemSKU#: dmi.product.family: iMac dmi.product.name: iMac14,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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-hwe-6.2/+bug/2049697/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 41624] Re: Replaying journals of other OS's filesystems, by mounting them, is unsafe
** Merge proposal linked: https://code.launchpad.net/~crass/casper/+git/casper/+merge/453083 -- 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/41624 Title: Replaying journals of other OS's filesystems, by mounting them, is unsafe Status in iso-scan package in Ubuntu: Triaged Status in linux package in Ubuntu: Won't Fix Status in lupin package in Ubuntu: Triaged Status in partman-basicfilesystems package in Ubuntu: Fix Released Status in os-prober package in Debian: Fix Released Bug description: I have just done a clean install of recent dapper (20060426.1 live i386) on my main testbed machine. The automatic volume discovery system has not only found the filesystems from various of the other installations (which is not quite so bad) but has dug into my LVM system and found the fs for a frozen Xen image ! This kind of thing can cause serious data loss. Modern journalling filesystems go even more badly wrong than traditional fs's if they are accessed by two running systems in an interleaved fashion, which is what results if Dapper automatically finds and mounts these filesystems, replaying the journal, while a frozen (whether by a VM like Xen or by ordinary hibernation) image has them mounted. In the current setup I think it would be easy to cause disaster simply by installing dapper twice on the same machine and then continuously hibernating one while using the other. More complex schemes are also possible. All of these filesystems discovered in this way should be made read- only unless it can be somehow known that it's safe to make them r/w. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iso-scan/+bug/41624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049697] [NEW] GPU not being detected when I try to run any game
You have been subscribed to a public bug: I ran ran apport-bug xorg and it took me here. Trying to figure out an issue where any time I open a game, it crashes and gives the error message "GPU not detected". From everything I've tried it seems like the computer has no problem detecting the GPU and it seems to be working fine, but games are still not working. Any help is appreciated! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 18:34:19 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.2.0-35-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:0d22] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:0122] InstallationDate: Installed on 2023-10-25 (84 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. iMac14,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic root=UUID=773b635d-a617-4aa4-8333-273b3ed7b502 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 146.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-031B6874CF7F642A dmi.board.vendor: Apple Inc. dmi.board.version: iMac14,1 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-031B6874CF7F642A dmi.modalias: dmi:bvnAppleInc.:bvr146.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pniMac14,1:pvr1.0:rvnAppleInc.:rnMac-031B6874CF7F642A:rvriMac14,1:cvnAppleInc.:ct13:cvrMac-031B6874CF7F642A:skuSystemSKU#: dmi.product.family: iMac dmi.product.name: iMac14,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 ** Affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- GPU not being detected when I try to run any game https://bugs.launchpad.net/bugs/2049697 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 2049665] Re: A recent Ubuntu update broke GPU processing in Folding@Home (nVidia GPU)
Thanks for the bug report. It appears you no longer have an nvidia kernel driver for the current kernel version. I'm also not sure if such a newer kernel can be supported by the old nvidia 390 driver. This might just be bug 1975650 so please try reinstalling the driver using the 'Additional Drivers' app or: sudo apt install --reinstall nvidia-driver-390 and reboot. If reinstalling the driver doesn't solve the problem then I wonder if nvidia-390 requires sticking to an older kernel? ** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu) ** Tags added: nvidia ** Tags added: regression-update ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049665 Title: A recent Ubuntu update broke GPU processing in Folding@Home (nVidia GPU) Status in linux-hwe-6.5 package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: A recent Ubuntu update is keeping the GPU software of Folding at Home (Folding@Home) from working. Past updates have not interfered with it. Expected result: An updated nvidia (proprietary) driver would be installed with the update that continues to work smoothly, provides OpenCL, etc. Actual result: The update caused FAH to disable its GPU processing capabilities. OpenCL is mentioned in the error message, so there may be something wrong with the OpenCL installation in the nVidia v390 package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 12:18:33 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.5.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] [10de:0fe9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 750M Mac Edition] [106b:011e] InstallationDate: Installed on 2024-01-16 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05ac:828d Apple, Inc. Bluetooth USB Host Controller Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 002: ID 05ac:8511 Apple, Inc. FaceTime HD Camera (Built-in) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. iMac14,3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=567a07dc-70f9-441e-a456-151c0da1e7ea ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 433.140.2.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-77EB7D7DAF985301 dmi.board.vendor: Apple Inc. dmi.board.version: iMac14,3 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-77EB7D7DAF985301 dmi.modalias: dmi:bvnAppleInc.:bvr433.140.2.0.0:bd04/18/2022:br0.1:svnAppleInc.:pniMac14,3:pvr1.0:rvnAppleInc.:rnMac-77EB7D7DAF985301:rvriMac14,3:cvnAppleInc.:ct13:cvrMac-77EB7D7DAF985301:skuSystemSKU#: dmi.product.family: iMac dmi.product.name: iMac14,3 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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-hwe-6.5/+bug/2049665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 2049665] [NEW] A recent Ubuntu update broke GPU processing in Folding@Home (nVidia GPU)
You have been subscribed to a public bug: A recent Ubuntu update is keeping the GPU software of Folding at Home (Folding@Home) from working. Past updates have not interfered with it. Expected result: An updated nvidia (proprietary) driver would be installed with the update that continues to work smoothly, provides OpenCL, etc. Actual result: The update caused FAH to disable its GPU processing capabilities. OpenCL is mentioned in the error message, so there may be something wrong with the OpenCL installation in the nVidia v390 package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 12:18:33 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.5.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] [10de:0fe9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 750M Mac Edition] [106b:011e] InstallationDate: Installed on 2024-01-16 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05ac:828d Apple, Inc. Bluetooth USB Host Controller Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 002: ID 05ac:8511 Apple, Inc. FaceTime HD Camera (Built-in) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. iMac14,3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=567a07dc-70f9-441e-a456-151c0da1e7ea ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 433.140.2.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-77EB7D7DAF985301 dmi.board.vendor: Apple Inc. dmi.board.version: iMac14,3 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-77EB7D7DAF985301 dmi.modalias: dmi:bvnAppleInc.:bvr433.140.2.0.0:bd04/18/2022:br0.1:svnAppleInc.:pniMac14,3:pvr1.0:rvnAppleInc.:rnMac-77EB7D7DAF985301:rvriMac14,3:cvnAppleInc.:ct13:cvrMac-77EB7D7DAF985301:skuSystemSKU#: dmi.product.family: iMac dmi.product.name: iMac14,3 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 ** Affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- A recent Ubuntu update broke GPU processing in Folding@Home (nVidia GPU) https://bugs.launchpad.net/bugs/2049665 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 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 2049569] Re: Enable the mic-mute led on Dell MTL laptops
** Also affects: firmware-sof (Ubuntu) Importance: Undecided Status: New ** Description changed: + [Kernel SRU] [Impact] On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is working but the LED(on F4) state is not changed accordingly. [Fix] There's no problem on the same series on RPL platform. It needs MTL specific SoF driver and controls to support the registered mixer switch. [Test Case] 1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only required for new sof-audio-pci-intel-mtl driver. The impact should be restricting. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049569 Title: Enable the mic-mute led on Dell MTL laptops Status in HWE Next: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in firmware-sof source package in Jammy: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in firmware-sof source package in Noble: New Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: [Kernel SRU] [Impact] On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is working but the LED(on F4) state is not changed accordingly. [Fix] There's no problem on the same series on RPL platform. It needs MTL specific SoF driver and controls to support the registered mixer switch. [Test Case] 1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only required for new sof-audio-pci-intel-mtl driver. The impact should be restricting. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049711] [NEW] Kernels 6.2 and 6.5: cannot adjust screen brightness
Public bug reported: After upgrading to LM 21.3 I could no longer adjust screen brightness. Reverted to kernel 6.2 but the problem remained. Reverted to kernel 5.15.0-91 generic and that solved the problem. mel@Schmetterling:~$ inxi -Fxxxrz System: Kernel: 6.5.0-14-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy Machine: Type: Laptop System: HP product: HP Laptop 14-dq2xxx v: N/A serial: Chassis: type: 10 serial: Mobo: HP model: 87FD v: 57.20 serial: UEFI: AMI v: F.21 date: 03/21/2022 Battery: ID-1: BAT0 charge: 40.5 Wh (100.0%) condition: 40.5/41.0 Wh (98.7%) volts: 12.9 min: 11.4 model: HP Primary type: Li-ion serial: status: Full cycles: 28 CPU: Info: quad core model: 11th Gen Intel Core i3-1125G4 bits: 64 type: MT MCP smt: enabled arch: Tiger Lake rev: 1 cache: L1: 320 KiB L2: 5 MiB L3: 8 MiB Speed (MHz): avg: 838 high: 1255 min/max: 400/3700 cores: 1: 963 2: 400 3: 400 4: 1137 5: 1255 6: 1021 7: 733 8: 802 bogomips: 31948 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel vendor: Hewlett-Packard driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1 bus-ID: :00:02.0 chip-ID: 8086:9a78 class-ID: 0300 Device-2: Chicony HP TrueVision HD Camera type: USB driver: uvcvideo bus-ID: 1-3:3 chip-ID: 04f2:b6f1 class-ID: 0e02 serial: Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9") Monitor-1: eDP-1 model: BOE Display res: 1920x1080 hz: 60 dpi: 158 size: 309x174mm (12.2x6.9") diag: 355mm (14") modes: 1920x1080 OpenGL: renderer: Mesa Intel UHD Graphics (TGL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: Hewlett-Packard driver: sof-audio-pci-intel-tgl bus-ID: :00:1f.3 chip-ID: 8086:a0c8 class-ID: 0401 Sound Server-1: ALSA v: k6.5.0-14-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter vendor: Hewlett-Packard driver: rtw_8822ce v: N/A port: 3000 bus-ID: :01:00.0 chip-ID: 10ec:c822 class-ID: 0280 IF: wlo1 state: up mac: Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-10:5 chip-ID: 0bda:b00c class-ID: e001 serial: Report: hciconfig ID: hci0 rfk-id: 0 state: up address: bt-v: 3.0 lmp-v: 5.1 sub-v: 6d7d hci-v: 5.1 rev: 19b7 RAID: Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd v: 0.6 port: N/A bus-ID: :00:0e.0 chip-ID: 8086:9a0b rev: class-ID: 0104 Drives: Local Storage: total: 238.47 GiB used: 100.77 GiB (42.3%) ID-1: /dev/nvme0n1 vendor: SK Hynix model: BC711 HFM256GD3JX013N size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 type: SSD serial: rev: HPS1 temp: 28.9 C scheme: GPT Partition: ID-1: / size: 232.47 GiB used: 100.77 GiB (43.3%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile Sensors: System Temperatures: cpu: 48.0 C mobo: N/A Fan Speeds (RPM): cpu: 0 fan-2: 0 Repos: Packages: 2736 apt: 2701 flatpak: 35 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/1password.list 1: deb [arch=amd64 signed-by=/usr/share/keyrings/1password-archive-keyring.gpg] https://downloads.1password.com/linux/debian/amd64 stable main Active apt repos in: /etc/apt/sources.list.d/apandada1-brightness-controller-jammy.list 1: deb [signed-by=/etc/apt/keyrings/apandada1-brightness-controller-jammy.gpg] https://ppa.launchpadcontent.net/apandada1/brightness-controller/ubuntu jammy main Active apt repos in: /etc/apt/sources.list.d/chrome-remote-desktop.list 1: deb [arch=amd64] http://dl.google.com/linux/chrome-remote-desktop/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http://packages.linuxmint.com virginia main upstream import backport 2: deb http://archive.ubuntu.com/ubuntu jammy main restricted universe multiverse 3: deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse 4: deb http://archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse 5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse No active apt repos in: /etc/apt/sources.list.d/surfshark.list Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 1:
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
It seems like the uncore warning that triggered by broken UPI discovery table on some SPR MCC. Link for fix patches: https://lore.kernel.org/lkml/20221129191023.936738-1-kan.li...@linux.intel.com/ To fix it, the commits below from mainline kernel v6.3-rc1 should be backported to the kernel being used: 5d515ee40cb5 perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table 65248a9a9ee1 perf/x86/uncore: Add a quirk for UPI on SPR bd9514a4d5ec perf/x86/uncore: Ignore broken units in discovery table 3af548f23610 perf/x86/uncore: Fix potential NULL pointer in uncore_get_alias_name dbf061b26221 perf/x86/uncore: Factor out uncore_device_to_die() -- 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/2049637 Title: Some SPR systems throw kernel warnings from uncore_discovery.c Status in intel: New Status in linux package in Ubuntu: New Bug description: [Impact] On some Sapphire Rapids CPUs we are seeing Kernel warnings in the kern.log: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] Code: c2 01 48 83 c0 04 39 d1 0f 8e c6 01 00 00 49 8b 4c 24 38 8b 0c 01 41 89 0c 07 49 8b 74 24 40 8b 34 06 41 89 34 06 39 f9 75 cf <0f> 0b 4c 89 ff e8 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ?
[Kernel-packages] [Bug 2038492] Re: workqueue: inode_switch_wbs_work_fn hogged CPU for >10000us 16 times, consider switching to WQ_UNBOUND
*** This bug is a duplicate of bug 2037214 *** https://bugs.launchpad.net/bugs/2037214 ** This bug has been marked a duplicate of bug 2037214 evict_inodes inode xxx, i_count = 1, was skipped! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038492 Title: workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 16 times, consider switching to WQ_UNBOUND Status in linux-oem-6.5 package in Ubuntu: Confirmed Bug description: dmesg has multiple messages: [ 852.580542] evict_inodes inode be24a21a, i_count = 1, was skipped! [ 852.580543] evict_inodes inode 2aea522e, i_count = 1, was skipped! [ 852.580544] evict_inodes inode 48d75a5c, i_count = 1, was skipped! [ 852.580545] evict_inodes inode d8a9e4c2, i_count = 1, was skipped! [ 852.580546] evict_inodes inode 3d2c905c, i_count = 1, was skipped! [ 852.580547] evict_inodes inode e5b1b232, i_count = 1, was skipped! [ 852.580548] evict_inodes inode 97383a6b, i_count = 1, was skipped! [ 852.580549] evict_inodes inode ca8e2b44, i_count = 1, was skipped! [ 1751.869281] workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND [ 1781.467278] workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 8 times, consider switching to WQ_UNBOUND [ 1806.065364] workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 16 times, consider switching to WQ_UNBOUND [ 1901.993975] evict_inodes inode abaa740e, i_count = 1, was skipped! [ 1901.993981] evict_inodes inode 515b9bf8, i_count = 1, was skipped! [ 1901.993983] evict_inodes inode 1a69d536, i_count = 1, was skipped! [ 1901.993984] evict_inodes inode 1403f675, i_count = 1, was skipped! [ 1901.993985] evict_inodes inode 757de21a, i_count = 1, was skipped! [ 1901.993986] evict_inodes inode 0cee9028, i_count = 1, was skipped! [ 1901.993987] evict_inodes inode d2827e77, i_count = 1, was skipped! Description:Ubuntu 22.04.3 LTS Release:22.04 linux-oem-22.04d: Installed: 6.5.0.1004.4 Candidate: 6.5.0.1004.4 Seems related to #2037214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2038492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038492] Re: workqueue: inode_switch_wbs_work_fn hogged CPU for >10000us 16 times, consider switching to WQ_UNBOUND
*** This bug is a duplicate of bug 2037214 *** https://bugs.launchpad.net/bugs/2037214 see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038492 Title: workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 16 times, consider switching to WQ_UNBOUND Status in linux-oem-6.5 package in Ubuntu: Confirmed Bug description: dmesg has multiple messages: [ 852.580542] evict_inodes inode be24a21a, i_count = 1, was skipped! [ 852.580543] evict_inodes inode 2aea522e, i_count = 1, was skipped! [ 852.580544] evict_inodes inode 48d75a5c, i_count = 1, was skipped! [ 852.580545] evict_inodes inode d8a9e4c2, i_count = 1, was skipped! [ 852.580546] evict_inodes inode 3d2c905c, i_count = 1, was skipped! [ 852.580547] evict_inodes inode e5b1b232, i_count = 1, was skipped! [ 852.580548] evict_inodes inode 97383a6b, i_count = 1, was skipped! [ 852.580549] evict_inodes inode ca8e2b44, i_count = 1, was skipped! [ 1751.869281] workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND [ 1781.467278] workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 8 times, consider switching to WQ_UNBOUND [ 1806.065364] workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 16 times, consider switching to WQ_UNBOUND [ 1901.993975] evict_inodes inode abaa740e, i_count = 1, was skipped! [ 1901.993981] evict_inodes inode 515b9bf8, i_count = 1, was skipped! [ 1901.993983] evict_inodes inode 1a69d536, i_count = 1, was skipped! [ 1901.993984] evict_inodes inode 1403f675, i_count = 1, was skipped! [ 1901.993985] evict_inodes inode 757de21a, i_count = 1, was skipped! [ 1901.993986] evict_inodes inode 0cee9028, i_count = 1, was skipped! [ 1901.993987] evict_inodes inode d2827e77, i_count = 1, was skipped! Description:Ubuntu 22.04.3 LTS Release:22.04 linux-oem-22.04d: Installed: 6.5.0.1004.4 Candidate: 6.5.0.1004.4 Seems related to #2037214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2038492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048729] Re: Mute/mic LEDs no function on HP ZBook
Install 6.5.0-1013.14-oem from ppa:canonical-kernel-team/proposed2 on OWLZZ-PV-SKU3_202401-33383 mic mute/speaker mute leds work well. ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 ** Changed in: oem-priority Status: Confirmed => Fix Committed ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048729 Title: Mute/mic LEDs no function on HP ZBook Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ZBook [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. Applied on oem-6.5 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2048729/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042568] Re: Azure - Kernel crashes when removing gpu from pci
This bug is awaiting verification that the linux-azure/5.15.0-1055.63 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-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/2042568 Title: Azure - Kernel crashes when removing gpu from pci Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Bug description: [Description] On a VM on Azure with a Tesla gpu it was noticed that when removing the gpu from the pci the vm would crash. In case the nvidia drivers are loaded, the machine won't crash. Instead the removing process will hang and the machine will crash on reboot. This is related to bug [1]. The bug reported in [1] regards another driver but the root cause is the same. It is still investigated whether this is a bug in pci, or it is a bug of various drivers on how they use pci. For this case we have identified that removing commit [2] prevents the kernel crashes. Azure has requested to revert this commit, at least for the time being. This commit is not in upstream, so it just need to be reverted from Ubuntu kernels. [Test Case] On an Azure vm with a gpu : # echo '1' > /sys/bus/pci/devices/0001:00:00.0/remove where '0001:00:00.0' the pci address of the gpu. The vm will crash. [Where things could go wrong] The commit to be reverted was included in a patchset to address lp bugs https://bugs.launchpad.net/bugs/2023071 and https://bugs.launchpad.net/bugs/2023594 However this commit just reduces boot time and removing shall not introduce any regressions. Side effects will be increase in the boot time. [Other] Only Ubuntu azure kernels are affected : - Jammy 5.15 - Lunar 6.2 Focal is also affected since it's using 5.15 kernel. This commit does not appear in Mantic 6.5 kernel. [1] https://bugzilla.kernel.org/show_bug.cgi?id=215515 [2] https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/jammy/commit/?h=Ubuntu-azure-5.15.0-1043.50=75af0c10b3703400890d314d1d91d25294234a81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2042568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045069] Re: Azure: Deprecate Netvsc and implement MANA direct
This bug is awaiting verification that the linux-azure/5.15.0-1055.63 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-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/2045069 Title: Azure: Deprecate Netvsc and implement MANA direct Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] Microsoft has asked for the inclusion of 3 patches that deprecate the use of netvsc in favor of MANA direct. hv_netvsc: Mark VF as slave before exposing it to user-mode: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=c807d6cd089d2f4951baa838081ec5ae3e2360f8 hv_netvsc: Fix race of register_netdevice_notifier and VF register: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=85520856466ed6bc3b1ccb013cddac70ceb437db hv_netvsc: fix race of netvsc and VF register_netdevice: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=d30fb712e52964f2cf9a9c14cf67078394044837 [Test Plan] Microsoft tested [Regression potential] User space that relies on netvsc will likely fail [Other Info] SF: #00374570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2045069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039208] Re: Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance
This bug is awaiting verification that the linux-azure/5.15.0-1055.63 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-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/2039208 Title: Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance Status in linux-azure package in Ubuntu: Fix Released 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] On Azure, the VM SKU Standard_NC64as_T4_v3's bandwidth is 30 Gbps, but we can only reach 15~20 Gbps with the 5.15.0-1049-azure kernel in Ubuntu 20.04 or the 6.2.0-1014-azure kernel in Ubuntu 22.04. After I pick up the upstream patch(es) to enable PCI relaxed ordering (RO) for the Mellanox VF NIC, the throughput goes up to 30.4 Gbps. [Fix] [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17347d5430c4e4e1a3c58ffa2732746bd26a9c02 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2351e517068718724f1d3b4010e2a41ec91fa76 [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77528e2aed9246cf8017b8a6f1b658a264d6f2b2 [4] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed4b0661cce119870edb1994fd06c9cbc1dc05c3 [Test Plan] Microsoft tested [Regression Potential] Mellanox connections could be corrupted or run slower. [Other Info] SF: #00370735 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2039208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043542] Re: Support Mediatek MT7925 WiFi/BT
kernel SRU:
* https://kernel.ubuntu.com/gitea/kernel/jammy-linux-oem/pulls/128 (oem-6.5)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2043542
Title:
Support Mediatek MT7925 WiFi/BT
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Noble:
Fix Released
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[kernel SRU Justification]
[Impact]
Mediatek MT7925 WiFi/Bluetooth not supported yet.
[Fix]
For WiFi, there are tons of patches to be backported from upstream
kernel v6.7 due to a massive refactoring was done to integrate
multiple mt79xx drivers into one before landing support for mt7925.
While these changes, mostly clean cherry-picks, are tied to each
other, and separating them may cause more efforts in the future, a
huge patchset of total number 144 is proposed.
For Bluetooth, upstream commit 4c92ae75ea7d ("Bluetooth: btusb: Add
support Mediatek MT7925") is required.
[Test Case]
Initial hardware support. One should be able to find WiFi/BT
interfaces up available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect
more fixes for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well.
Nominate for Jammy and Noble.
[linux-firmware SRU Justification]
[Impact]
Missing firmware for Mediatek MT7925 WiFi/BT.
[Fix]
Upstream firmware commits:
- WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
- Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek
bluetooth
chip (MT7925)")
[Test Case]
Initial hardware support. One should be able to find WiFi/BT interfaces up
available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect more
fixes
for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
for Jammy and Noble.
== original bug report ==
* WiFi
- kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
* ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
* 3c1199134874 wifi: mt76: connac: add more unified command IDs
* 473f26fb167e wifi: mt76: connac: add data field in struct tlv
* 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
* e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
* d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
* 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
* 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
* Bluetooth
- kernel:
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043542/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047504] Re: Mute/mic LEDs and speaker no function on some HP platforms
Install 6.5.0-1013.14-oem from ppa:canonical-kernel-team/proposed2 both BRCO-PV-SKU5_202312-33268 and BRCOR-PV-SKU1_202312-33263s' mic mute/speaker mute and speaker work well. ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047504 Title: Mute/mic LEDs and speaker no function on some HP platforms Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Bug description: [Impact] The mic mute/audio mute LEDS and speaker are not work on some HP platforms. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs and speaker are working good. Applied on oem-6.5 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049708] Re: bluez bluetoothd unable to locate executable
** Description changed: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support - ░░ + ░░ ░░ A start job for unit bluetooth.service has begun execution. - ░░ + ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support - ░░ + ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. - ░░ + ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory + + the system service ExecStart location was correctly updated so not sure + what still has the old location + + cat /lib/systemd/system/bluetooth.service + [Unit] + Description=Bluetooth service + Documentation=man:bluetoothd(8) + ConditionPathIsDirectory=/sys/class/bluetooth + + [Service] + Type=dbus + BusName=org.bluez + ExecStart=/usr/libexec/bluetooth/bluetoothd -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049708 Title: bluez bluetoothd unable to locate executable Status in bluez package in Ubuntu: New Bug description: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049708] [NEW] bluez bluetoothd unable to locate executable
Public bug reported: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049708 Title: bluez bluetoothd unable to locate executable Status in bluez package in Ubuntu: New Bug description: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049660] Re: [amdgpu][HP Pavilion Plus Laptop 14] Screen artifacts especially when changing workspaces
Please also try kernel parameter amdgpu.dcdebugmask=0x10 to disable panel self-refresh. ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049660 Title: [amdgpu][HP Pavilion Plus Laptop 14] Screen artifacts especially when changing workspaces Status in linux-hwe-6.5 package in Ubuntu: Incomplete Bug description: Installed fresh, artifacts started after update. Happens when interacting gnome; menus, changing workspaces, etc. Attached screencast ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 17:55:34 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8c21] InstallationDate: Installed on 2024-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: HP HP Pavilion Plus Laptop 14-ey0xxx ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7trxt5@/vmlinuz-6.5.0-14-generic root=ZFS=rpool/ROOT/ubuntu_7trxt5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2023 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8C21 dmi.board.vendor: HP dmi.board.version: 87.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.27 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd08/10/2023:br15.2:efr87.27:svnHP:pnHPPavilionPlusLaptop14-ey0xxx:pvrType1ProductConfigId:rvnHP:rn8C21:rvr87.27:cvnHP:ct10:cvrChassisVersion:sku8Y7M1EA#ABH: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Plus Laptop 14-ey0xxx dmi.product.sku: 8Y7M1EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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-hwe-6.5/+bug/2049660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049660] Re: screen artifacts especially when changing workspaces
Thanks for the bug report. I've watched the attached screencast a few times and can't see any artifacts in it. This is unsurprising given how screen recording works. You will probably need to take a video of the screen externally, like with a phone. ** Summary changed: - screen artifacts especially when changing workspaces + [HP Pavilion Plus Laptop 14] Screen artifacts especially when changing workspaces ** Summary changed: - [HP Pavilion Plus Laptop 14] Screen artifacts especially when changing workspaces + [amdgpu][HP Pavilion Plus Laptop 14] Screen artifacts especially when changing workspaces ** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu) ** Tags added: amdgpu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049660 Title: [amdgpu][HP Pavilion Plus Laptop 14] Screen artifacts especially when changing workspaces Status in linux-hwe-6.5 package in Ubuntu: Incomplete Bug description: Installed fresh, artifacts started after update. Happens when interacting gnome; menus, changing workspaces, etc. Attached screencast ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 17:55:34 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8c21] InstallationDate: Installed on 2024-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: HP HP Pavilion Plus Laptop 14-ey0xxx ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7trxt5@/vmlinuz-6.5.0-14-generic root=ZFS=rpool/ROOT/ubuntu_7trxt5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2023 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8C21 dmi.board.vendor: HP dmi.board.version: 87.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.27 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd08/10/2023:br15.2:efr87.27:svnHP:pnHPPavilionPlusLaptop14-ey0xxx:pvrType1ProductConfigId:rvnHP:rn8C21:rvr87.27:cvnHP:ct10:cvrChassisVersion:sku8Y7M1EA#ABH: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Plus Laptop 14-ey0xxx dmi.product.sku: 8Y7M1EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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-hwe-6.5/+bug/2049660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044427] Re: Kernel panic in restart driver after configuring IPsec full offload
This bug is awaiting verification that the linux- bluefield/5.15.0-1034.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2044427 Title: Kernel panic in restart driver after configuring IPsec full offload Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: Bug description: Restarting the driver with IPsec full offload transparent mode configuration causes kernel panic. Kernel version is linux-bluefield 5.15 Test step: 1) configure xfrm rules 2) configure VF 3) configure FW steering mode 4) restart driver 5) check dmesg Test result: [ 937.989359] [ cut here ] [ 937.989786] WARNING: CPU: 11 PID: 60463 at /tmp/23.10-0.1.8/6.5.0-rc6_mlnx/fedora_32/mlnx-ofa_kernel/BUILD/mlnx-ofa_kernel-23.10/obj/default/drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec_fs.c:1828 mlx5e_accel_ipsec_fs_cleanup+0x298/0x2b0 [mlx5_core] [ 937.991650] Modules linked in: esp4_offload esp4 esp6_offload esp6 act_tunnel_key vxlan act_mirred act_skbedit cls_matchall act_gact cls_flower sch_ingress vringh vhost_iotlb udp_diag tcp_diag inet_diag iptable_raw mst_pciconf(OE) bonding ip6_gre ip6_tunnel tunnel6 vfio_pci vfio_pci_core vfio_iommu_type1 vfio ipip tunnel4 geneve ip6_udp_tunnel udp_tunnel ip_gre ip_tunnel gre rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) ib_uverbs(OE) mlx5_core(OE-) mlxdevm(OE) ib_core(OE) mlx_compat(OE) mlxfw(OE) memtrack(OE) pci_hyperv_intf openvswitch nsh nf_conncount nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_filter iptable_nat nf_nat br_netfilter bridge stp llc rfkill overlay kvm_intel sch_fq_codel kvm iTCO_wdt irqbypass iTCO_vendor_support crc32_pclmul pcspkr ghash_clmulni_intel i2c_i801 lpc_ich sha512_ssse3 i2c_smbus mfd_core sunrpc drm i2c_ core ip_tables crc32c_intel serio_raw [ 937.991698] fuse virtio_net net_failover failover [last unloaded: vdpa] [ 937.999155] CPU: 11 PID: 60463 Comm: modprobe Tainted: G OE 6.5.0-rc6_mlnx #1 [ 937.999891] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 [ 938.000823] RIP: 0010:mlx5e_accel_ipsec_fs_cleanup+0x298/0x2b0 [mlx5_core] [ 938.001459] Code: f6 45 31 c0 48 89 ea 31 ff e8 d4 d5 df ff 59 e9 8c fe ff ff c3 0f 0b e9 3b fe ff ff 0f 0b e9 e8 fd ff ff 0f 0b e9 07 fe ff ff <0f> 0b e9 65 fe ff ff 0f 0b e9 82 fe ff ff 66 2e 0f 1f 84 00 00 00 [ 938.002949] RSP: 0018:c90001183c08 EFLAGS: 00010202 [ 938.003418] RAX: RBX: 8882f3869c00 RCX: 0001 [ 938.004024] RDX: 82a305c0 RSI: 0002 RDI: 888103aa2b30 [ 938.004624] RBP: 888103aa2d80 R08: 0001 R09: 888100042800 [ 938.005238] R10: 0002 R11: c90001183ba8 R12: 8881312e6800 [ 938.005836] R13: 8881127401a0 R14: 8881312e6800 R15: 888148bbd160 [ 938.006444] FS: 7fd22b82c740() GS:5fac() knlGS: [ 938.009456] CS: 0010 DS: ES: CR0: 80050033 [ 938.009970] CR2: 7f26ca697000 CR3: 00012e73f003 CR4: 00770ee0 [ 938.010568] DR0: DR1: DR2: [ 938.011173] DR3: DR6: fffe0ff0 DR7: 0400 [ 938.011772] PKRU: 5554 [ 938.012065] Call Trace: [ 938.012333] [ 938.012583] ? __warn+0x7d/0x120 [ 938.012921] ? mlx5e_accel_ipsec_fs_cleanup+0x298/0x2b0 [mlx5_core] [ 938.013494] ? report_bug+0xf1/0x1c0 [ 938.013850] ? handle_bug+0x44/0x70 [ 938.014201] ? exc_invalid_op+0x13/0x60 [ 938.014568] ? asm_exc_invalid_op+0x16/0x20 [ 938.014970] ? mlx5e_accel_ipsec_fs_cleanup+0x298/0x2b0 [mlx5_core] [ 938.015532] ? mlx5e_accel_ipsec_fs_cleanup+0xf2/0x2b0 [mlx5_core] [ 938.016093] mlx5e_ipsec_cleanup+0x1e/0x100 [mlx5_core] [ 938.016594]
[Kernel-packages] [Bug 2046657] Re: mmc: sdhci-of-dwcmshc: Replace sauce patches with upstream commits
This bug is awaiting verification that the linux- bluefield/5.15.0-1034.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2046657 Title: mmc: sdhci-of-dwcmshc: Replace sauce patches with upstream commits Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The msdhci-of-dwcmshc driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. [Test Case] * Boot BF3 platform, verify no new errors [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2046657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045919] Re: mlxbf-bootctl: fails to report info about cards using dev keys
This bug is awaiting verification that the linux- bluefield/5.15.0-1034.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2045919 Title: mlxbf-bootctl: fails to report info about cards using dev keys Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] There is a gap in the mlxbf-bootctl driver logic, resulting in failure to report when a secure boot enabled card is using development keys. The program will instead report lifecycle state as "GA Secured" which is misleading. [Fix] Bring in the following upstream commit from linux-next: "mlxbf-bootctl: correctly identify secure boot with development keys" [Test Case] Enable secure boot on a BF3 card that is using development keys Login as root on BF3 Run the command "mlxbf-bootctl" Verify that the "lifecycle state" row shows "Secured (development)" [Regression Potential] Low risk change, cherry pick of upstream approved commit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2045919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047853] Re: mlxbf_gige: replace SAUCE patch for RX race condition
This bug is awaiting verification that the linux- bluefield/5.15.0-1034.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2047853 Title: mlxbf_gige: replace SAUCE patch for RX race condition Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] There is a SAUCE patch that addresses a mlxbf-gige RX race condition "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic" This SAUCE patch should be reverted and replaced with upstream content. [Fix] Bring in the following upstream commit from linux-next: "mlxbf_gige: fix receive packet race condition" [Test Case] Boot BF3 platform and ensure oob_net0 interface is up and has IP address Send heavy level of traffic into the BF3 oob_net0 and make sure no stalls occur [Regression Potential] Low risk change, cherry pick of upstream approved commit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2047853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049660] [NEW] [amdgpu][HP Pavilion Plus Laptop 14] Screen artifacts especially when changing workspaces
You have been subscribed to a public bug: Installed fresh, artifacts started after update. Happens when interacting gnome; menus, changing workspaces, etc. Attached screencast ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 17:55:34 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8c21] InstallationDate: Installed on 2024-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: HP HP Pavilion Plus Laptop 14-ey0xxx ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7trxt5@/vmlinuz-6.5.0-14-generic root=ZFS=rpool/ROOT/ubuntu_7trxt5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2023 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8C21 dmi.board.vendor: HP dmi.board.version: 87.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.27 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd08/10/2023:br15.2:efr87.27:svnHP:pnHPPavilionPlusLaptop14-ey0xxx:pvrType1ProductConfigId:rvnHP:rn8C21:rvr87.27:cvnHP:ct10:cvrChassisVersion:sku8Y7M1EA#ABH: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Plus Laptop 14-ey0xxx dmi.product.sku: 8Y7M1EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 ** Affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption jammy ubuntu wayland-session -- [amdgpu][HP Pavilion Plus Laptop 14] Screen artifacts especially when changing workspaces https://bugs.launchpad.net/bugs/2049660 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 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 2048729] Re: Mute/mic LEDs no function on HP ZBook
** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048729 Title: Mute/mic LEDs no function on HP ZBook Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Confirmed Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ZBook [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. Applied on oem-6.5 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2048729/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041668] Re: Memory leak in 23.10 kernel (6.5.0-10)
Hi Craig. Excellent work tracking down the mailing list discussion. From what I can see is that actual memory allocation and free still works as intended, it is just accounting that becomes incorrect, making your system work correctly, just with wrong numbers displayed in your metrics. Regardless, this is currently queued up for 6.5.0-17-generic, and it contains the commit: commit 3cec50490969afd4a76ccee441f747d869ccff77 Author: Linus Torvalds Date: Sat Sep 16 12:31:42 2023 -0700 Subject: vm: fix move_vma() memory accounting being off Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3cec50490969afd4a76ccee441f747d869ccff77 In Mantic's kernel it is 1f48faf4d74ee05aafbf406d6274727afc62a61f. $ git describe --contains 1f48faf4d74ee05aafbf406d6274727afc62a61f Ubuntu-6.5.0-16.16~1071 6.5.0-17-generic is currently in -proposed. If you would like to test it you can follow the instructions below: Instructions to install (On a Mantic system): 1) cat << EOF | sudo tee /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list # Enable Ubuntu proposed archive deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed main universe EOF 2) sudo apt update 3) sudo apt install linux-image-6.5.0-17-generic linux-modules-6.5.0-17-generic linux-modules-extra-6.5.0-17-generic linux-headers-6.5.0-17-generic 4) sudo reboot 5) uname -rv 6.5.0-17-generic #17-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 11 14:01:59 UTC 2024 You probably want to remove the -proposed repository afterward. 6) sudo rm ubuntu-$(lsb_release -cs)-proposed.list 7) sudo apt update This should be released in the first week of February, somewhere around the 5th give or take a couple days if any CVEs come up. https://kernel.ubuntu.com/ Thanks, Matthew ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2041668 Title: Memory leak in 23.10 kernel (6.5.0-10) Status in linux package in Ubuntu: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: There appears to be a memory 'leak' in the kernel of the latest Ubuntu release (Mantic Minotaur, kernel version 6.5.0-10). I put 'leak' in quotes because this memory appears to be allocated but never used. The kernel's memory over-commit mechanism seems to prevent this leak from manifesting in OOM killer triggers or other failures. The primary symptom is a steady increase in the value reported as 'Committed_AS' in '/proc/meminfo'. The other memory stats reported there remain reasonable, though. I've observed this problem on a fairly diverse set of machines (both VMs and physical machines) with a variety of workloads. Busier machines seem to have a faster leak rate. I've tried to narrow down the issue by rebooting into single user mode, killing all userspace processes (except the systemd processes) and removing as many kernel models as possible. The problem continues in that state. I didn't see any obvious culprits in /proc/slabinfo nor /proc/vmallocinfo. So far, the only way I've been able to remediate this issue is to reboot back into the Lunar Lobster kernel (6.2.0-35). I think this fact alone rules out any triggers that may be part of the 23.10 userspace environment. I've attached the generic debug info requested by this component's bug template from an example machine. Please let me know if there is any more information I can provide. It seems to be pretty trivial to reproduce though, and I'm guessing it has not been reported yet because the leak doesn't actually manifest in an out-of-memory situation. At least, I haven't observed that yet. The worst case I've observed was 150 GB of memory committed on a machine with 16 GB of physical RAM after about 24 hours. Moving back to the previous kernel version, the committed memory statistic holds fairly steady around 7 GB on that machine and workload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045517] Re: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S
Yes. They are all in the v6.7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2045517 Title: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] To support HP stella's latest machine, we need to backport some new PCIIDs and corresponding drivers to our OEM kernel, the requirement is here: https://docs.google.com/spreadsheets/d/1_usKzZDxjtqlUzdOUPXvzNzSzhjRqcaV/edit#gid=1748766508 This pull-request is to unitfy and add some audio controller's ID, but to do so, need to apply some depending patches otherwise it will have conflict to introduce the new ID and new driver to OEM kernel. unified PCIIDs: PCI_DEVICE_ID_INTEL_HDA_ADL_N PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 PCI_DEVICE_ID_INTEL_HDA_ADL_P PCI_DEVICE_ID_INTEL_HDA_RPL_S PCI_DEVICE_ID_INTEL_HDA_MTL new added PCIID: PCI_DEVICE_ID_INTEL_HDA_ARL_S [Fix] This add the audio driver for machines with Intel Arrowlake. [Test case] Boot the patched kernel on a Arrowlake machine, the audio function could work. Boot the patches kernel on non-Arrowlake machines, the audio function could work as well as before. [Where problems could occur] Could lose some pciids and make the auido driver not work on those machines, and could not play sound or record sound. But this possibility is very low, I checked each patch carefully and I verify the patcheset on some lenovo an dell machines. From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based on it, added new PCIID and audio support for arrowlake-s, need to backport them to oem-6.5, this is a preparation for supporting HP latest laptops: unified PCIIDs: PCI_DEVICE_ID_INTEL_HDA_ADL_N PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 PCI_DEVICE_ID_INTEL_HDA_ADL_P PCI_DEVICE_ID_INTEL_HDA_RPL_S PCI_DEVICE_ID_INTEL_HDA_MTL new added PCIID: PCI_DEVICE_ID_INTEL_HDA_ARL_S To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041668] Re: Memory leak in 23.10 kernel (6.5.0-10)
** No longer affects: linux-meta (Ubuntu) ** No longer affects: linux-meta-hwe-6.5 (Ubuntu) ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Mantic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium -- 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/2041668 Title: Memory leak in 23.10 kernel (6.5.0-10) Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Fix Committed Bug description: There appears to be a memory 'leak' in the kernel of the latest Ubuntu release (Mantic Minotaur, kernel version 6.5.0-10). I put 'leak' in quotes because this memory appears to be allocated but never used. The kernel's memory over-commit mechanism seems to prevent this leak from manifesting in OOM killer triggers or other failures. The primary symptom is a steady increase in the value reported as 'Committed_AS' in '/proc/meminfo'. The other memory stats reported there remain reasonable, though. I've observed this problem on a fairly diverse set of machines (both VMs and physical machines) with a variety of workloads. Busier machines seem to have a faster leak rate. I've tried to narrow down the issue by rebooting into single user mode, killing all userspace processes (except the systemd processes) and removing as many kernel models as possible. The problem continues in that state. I didn't see any obvious culprits in /proc/slabinfo nor /proc/vmallocinfo. So far, the only way I've been able to remediate this issue is to reboot back into the Lunar Lobster kernel (6.2.0-35). I think this fact alone rules out any triggers that may be part of the 23.10 userspace environment. I've attached the generic debug info requested by this component's bug template from an example machine. Please let me know if there is any more information I can provide. It seems to be pretty trivial to reproduce though, and I'm guessing it has not been reported yet because the leak doesn't actually manifest in an out-of-memory situation. At least, I haven't observed that yet. The worst case I've observed was 150 GB of memory committed on a machine with 16 GB of physical RAM after about 24 hours. Moving back to the previous kernel version, the committed memory statistic holds fairly steady around 7 GB on that machine and workload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033732] Re: SMB 1 broken in kernel linux-generic-hwe-22.04 (version 6.2.0-31)
Hi rdiez,
Yes, this was fixed in 6.2.0-32-generic, as it included the commit you
mentioned in your description.
commit e5e1411ee7e612335d8e9d6fd7379401dee54f28
Author: Paulo Alcantara
Date: Tue May 23 17:38:38 2023 -0300
cifs: fix smb1 mount regression
BugLink: https://bugs.launchpad.net/bugs/2028979
commit 72a7804a667eeac9610521179f0418883158 upstream.
cifs.ko maps NT_STATUS_NOT_FOUND to -EIO when SMB1 servers couldn't
resolve referral paths. Proceed to tree connect when we get -EIO from
dfs_get_referral() as well.
Reported-by: Kris Karas (Bug Reporting)
Tested-by: Woody Suwalski
Fixes: 8e3554150d6c ("cifs: fix sharing of DFS connections")
Cc: sta...@vger.kernel.org # v6.2+
Signed-off-by: Paulo Alcantara (SUSE)
Signed-off-by: Steve French
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Kamal Mostafa
Signed-off-by: Stefan Bader
$ git describe --contains e5e1411ee7e612335d8e9d6fd7379401dee54f28
Ubuntu-hwe-6.2-6.2.0-32.32_22.04.1~173
I'll take a look at your 6.5 issues now.
Thanks,
Matthew
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: Confirmed => Fix Released
--
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/2033732
Title:
SMB 1 broken in kernel linux-generic-hwe-22.04 (version 6.2.0-31)
Status in linux-hwe-6.2 package in Ubuntu:
Fix Released
Bug description:
I was running Ubuntu 22.04.3 on kernel version 5.15.0-82-generic, and
I installed package linux-generic-hwe-22.04 in order to upgrade to
kernel version 6.2.0-31.
That upgrade broke the SMB version 1 protocol. I know that it is an
old, deprecated protocol, but I still have to access some legacy
systems and devices in a local network.
This breakage has been discussed on the Internet. It is a Linux kernel
regression.
This is the commit that fixes it. It is a very small change:
2f6f19c7aaad "cifs: fix regression in very old smb1 mounts"
https://github.com/torvalds/linux/commit/2f6f19c7aaad5005dc75298a413eb0243c5d312d
I am no Linux kernel expert. Could you please backport that fix to the
kernel versions that linux-generic-hwe-22.04 installs?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2033732/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034033] Re: Ubuntu 22.04 update to 6.2.0-31 kernel version breaks mount.cifs to vers=1.0 server cifs_mount failed w/return code = -5
*** This bug is a duplicate of bug 2033732 *** https://bugs.launchpad.net/bugs/2033732 ** This bug has been marked a duplicate of bug 2033732 SMB 1 broken in kernel linux-generic-hwe-22.04 (version 6.2.0-31) -- 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/2034033 Title: Ubuntu 22.04 update to 6.2.0-31 kernel version breaks mount.cifs to vers=1.0 server cifs_mount failed w/return code = -5 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: My Xubuntu system this weekend alerted me to a new kernel update being available. The following versions are the existing/working version: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 And the updated/not working version: linux-image-6.2.0-31-generic 6.2.0-31.31~22.04.1 And yes I run my system with: linux-image-generic-hwe-22.04 6.2.0.31.31~22.04.8 Booted to the 6.2.0-31 kernel version, attempting to do a mount.cifs operation to our Samba NT4 PDC, results in the following output into syslog: Sep 4 08:03:24 jaakob kernel: [ 107.703886] FS-Cache: Loaded Sep 4 08:03:24 jaakob kernel: [ 107.824160] Key type cifs.spnego registered Sep 4 08:03:24 jaakob kernel: [ 107.824169] Key type cifs.idmap registered Sep 4 08:03:24 jaakob kernel: [ 107.824454] Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Sep 4 08:03:24 jaakob kernel: [ 107.824454] Sep 4 08:03:24 jaakob kernel: [ 107.824457] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Sep 4 08:03:24 jaakob kernel: [ 107.824460] CIFS: Attempting to mount \\ldslnx01\data Sep 4 08:03:24 jaakob kernel: [ 107.859554] CIFS: VFS: cifs_mount failed w/return code = -5 And none of the Samba mounts will establish. Booting back to the prior 6.2.0-26 kernel version, Samba mounts work just fine. I use the following switches to the mount.cifs command in order to establish connections to our Samba NT4 PDC: "-o credentials=/home/mdlueck/.smbcredentials,uid=mdlueck,gid=mdlueck,dir_mode=0777,file_mode=0666,nobrl,vers=1.0" That last vers= option was the last that needed to be added to continue making use of our Samba NT4 style PDC. Since it is a version upgrade of only the kernel, not Samba package, I would not think that yet another switch to mount.cifs was needed in order to continue connecting successfully. So did the latest Kernel update suddenly break Samba's mount.cifs vers=1.0 support? Nothing gets logged to our Samba server for the failed mount attempt. Booting for not back to the working 6.2.0-26 kernel version. Please kindly advise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.4.0.1102.132)
All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1102.132) for focal have finished running. The following regressions have been reported in tests triggered by the package: acpi-call/unknown (arm64) dm-writeboost/unknown (arm64) jool/unknown (arm64) lime-forensics/unknown (arm64) lttng-modules/unknown (arm64) lxc/unknown (arm64) nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (armhf) openrazer/unknown (arm64) rtl8812au/unknown (arm64) v4l2loopback/unknown (arm64) west-chamber/unknown (arm64) wireguard/unknown (arm64) xtables-addons/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-raspi [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049689] [NEW] linux-image-5.15.0-94-generic breaks partprobe on empty loopback device
Public bug reported:
This is with the kernel from jammy-proposed (linux-
image-5.15.0-94-generic 5.15.0-94.104).
Do this:
# dd if=/dev/zero of=/tmp/file bs=1M count=50
# partprobe "$(losetup --show --find /tmp/file)"
Notice this very odd error message:
Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33,
34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51,
52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/loop2 have
been written, but we have been unable to inform the kernel of the
change, probably because it/they are in use. As a result, the old
partition(s) will remain in use. You should reboot now before making
further changes.
That's a result of an ioctl changing its error code in an incompatible
way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
partprobe.
5.15.0.91.88:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or
address)
5.15.0.94.91:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)
This is a userspace API break which impacts GNU parted and util-linux
(as confirmed by the util-linux maintainer).
This issue was discovered as part of Cockpit CI here:
https://github.com/cockpit-project/bots/pull/5793
This issue is being discussed on LKML here (with a patch likely to land
soon): https://lkml.org/lkml/2024/1/15/147
lsb_release -rd:
Description:Ubuntu 22.04.3 LTS
Release:22.04
** Affects: linux-signed (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2049689
Title:
linux-image-5.15.0-94-generic breaks partprobe on empty loopback
device
Status in linux-signed package in Ubuntu:
New
Bug description:
This is with the kernel from jammy-proposed (linux-
image-5.15.0-94-generic 5.15.0-94.104).
Do this:
# dd if=/dev/zero of=/tmp/file bs=1M count=50
# partprobe "$(losetup --show --find /tmp/file)"
Notice this very odd error message:
Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
/dev/loop2 have been written, but we have been unable to inform the
kernel of the change, probably because it/they are in use. As a
result, the old partition(s) will remain in use. You should reboot
now before making further changes.
That's a result of an ioctl changing its error code in an incompatible
way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
partprobe.
5.15.0.91.88:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or
address)
5.15.0.94.91:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)
This is a userspace API break which impacts GNU parted and util-linux
(as confirmed by the util-linux maintainer).
This issue was discovered as part of Cockpit CI here:
https://github.com/cockpit-project/bots/pull/5793
This issue is being discussed on LKML here (with a patch likely to
land soon): https://lkml.org/lkml/2024/1/15/147
lsb_release -rd:
Description: Ubuntu 22.04.3 LTS
Release: 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2049689/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049688] [NEW] nvidia stoped working, , package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script su
Public bug reported: after latest update on 22.04 nvidia driver stoped working, gpu not found, cannot reinstall, even after upgrade I get : package nvidia- dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10. I also had errors with dependencies, when trying to reinstall and with kernel headers. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: nvidia-dkms-390 390.157-0ubuntu5.23.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 17 22:54:39 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-11-28 (50 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to lunar on 2024-01-17 (0 days ago) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049688 Title: nvidia stoped working,, package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia- dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: after latest update on 22.04 nvidia driver stoped working, gpu not found, cannot reinstall, even after upgrade I get : package nvidia- dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10. I also had errors with dependencies, when trying to reinstall and with kernel headers. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: nvidia-dkms-390 390.157-0ubuntu5.23.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 17 22:54:39 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-11-28 (50 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to lunar on 2024-01-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049680] [NEW] trackpad not detected/ not working
Public bug reported: I have just connected a usb keyboard and soon i just removed it, after that my trackpad stopped working. Also in the setting, there is no option given under mouse & trackpad setting. I have to use external usb mouse for the use ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-91.101~20.04.1-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 18 01:35:07 2024 InstallationDate: Installed on 2023-04-15 (277 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2049680 Title: trackpad not detected/ not working Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: I have just connected a usb keyboard and soon i just removed it, after that my trackpad stopped working. Also in the setting, there is no option given under mouse & trackpad setting. I have to use external usb mouse for the use ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-91.101~20.04.1-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 18 01:35:07 2024 InstallationDate: Installed on 2023-04-15 (277 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2049680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049666] Re: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
** Package changed: ubuntu => dkms (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2049666 Title: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: anil 1418 F wireplumber /dev/snd/controlC1: anil 1418 F wireplumber /dev/snd/controlC0: anil 1418 F wireplumber /dev/snd/seq:anil 1405 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed Jan 17 20:17:47 2024 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2022-07-16 (549 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp12s0 no wireless extensions. docker0 no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic root=UUID=7d0201f7-e7d8-4247-8f8c-d9bd80ffb976 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: dkms Title: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-07-15 (185 days ago) dmi.bios.date: 04/08/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX/GEN3 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX/GEN3R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2049666/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049666] [NEW] package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
You have been subscribed to a public bug: . ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: anil 1418 F wireplumber /dev/snd/controlC1: anil 1418 F wireplumber /dev/snd/controlC0: anil 1418 F wireplumber /dev/snd/seq:anil 1405 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed Jan 17 20:17:47 2024 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2022-07-16 (549 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp12s0 no wireless extensions. docker0 no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic root=UUID=7d0201f7-e7d8-4247-8f8c-d9bd80ffb976 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: dkms Title: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-07-15 (185 days ago) dmi.bios.date: 04/08/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX/GEN3 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX/GEN3R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar need-duplicate-check -- package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 https://bugs.launchpad.net/bugs/2049666 You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms 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 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
Since the PPA failed would you be able to manually build 6.5.13 to see
if it's fixed there?
--
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/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042713] Re: Pale Green blank screen after login
Boot a bad kernel, reboot the system, boot a good kernel. >From the good kernel: journalctl -k -b0 > good_kernel.txt journalctl -k -b-1 > bad_kernel.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/2042713 Title: Pale Green blank screen after login Status in linux package in Ubuntu: Incomplete Bug description: Since linux Kernel 5.15.0-86, when I only get a pale green blank screen after login Linux Mint 21.2 Victoria / Cinnamon so I got to use 5.15.0-84. N.B. I'm using a Graphic AMD processor with unconventional screens resolutions (1280x1025 (5/4) & 1360x768 (16:9)) inxi : CPU: dual core AMD A6-9500 RADEON R5 8 COMPUTE CORES 2C+6G (-MT MCP-) speed/min/max: 3594/1400/3500 MHz Kernel: 5.15.0-84-generic x86_64 Up: 12h 9m Mem: 1946.1/15413.6 MiB (12.6%) Storage: 7.04 TiB (38.5% used) Procs: 256 Shell: Bash inxi: 3.3.13 inxi -S : System: Host: linuxmint Kernel: 5.15.0-84-generic x86_64 bits: 64 Desktop: Cinnamon 5.8.4 Distro: Linux Mint 21.2 Victoria To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049676] [NEW] `iwlist scan` crashes iwlwifi with a "Microcode SW error detected. Restarting 0x0." message
Public bug reported: Ubuntu 22.04.3 on a Lenovo ThinkPad X1 Carbon Gen 11 Kernel: 6.5 (official), 6.6 and 6.7 (mainline) Running `iwlist scan` as root produces an error message like: wlp0s20f3 Interface doesn't support scanning : Input/output error while the crash can be seen in the dmesg output below. The network card is: 00:14.3 Network controller [0280]: Intel Corporation Device [8086:51f1] (rev 01) Subsystem: Intel Corporation Device [8086:0090] Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 10 Memory at 603d1d4000 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Latency Tolerance Reporting Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0 Len=014 Kernel driver in use: iwlwifi Kernel modules: iwlwifi dmesg output: [ 23.883032] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 23.883184] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 23.883189] iwlwifi :00:14.3: Transport status: 0x004B, valid: 6 [ 23.883195] iwlwifi :00:14.3: Loaded firmware version: 83.e8f84e98.0 so-a0-gf-a0-83.ucode [ 23.883200] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [ 23.883205] iwlwifi :00:14.3: 0x02F0 | trm_hw_status0 [ 23.883209] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 23.883212] iwlwifi :00:14.3: 0x004DB338 | branchlink2 [ 23.883215] iwlwifi :00:14.3: 0x004DA866 | interruptlink1 [ 23.883219] iwlwifi :00:14.3: 0x004DA866 | interruptlink2 [ 23.883221] iwlwifi :00:14.3: 0x000157E2 | data1 [ 23.883225] iwlwifi :00:14.3: 0x0010 | data2 [ 23.883228] iwlwifi :00:14.3: 0x | data3 [ 23.883231] iwlwifi :00:14.3: 0x1F409941 | beacon time [ 23.883234] iwlwifi :00:14.3: 0x7ACBC6C4 | tsf low [ 23.883237] iwlwifi :00:14.3: 0x034B | tsf hi [ 23.883240] iwlwifi :00:14.3: 0x | time gp1 [ 23.883243] iwlwifi :00:14.3: 0x0112D254 | time gp2 [ 23.883247] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 23.883250] iwlwifi :00:14.3: 0x0053 | uCode version major [ 23.883253] iwlwifi :00:14.3: 0xE8F84E98 | uCode version minor [ 23.883256] iwlwifi :00:14.3: 0x0370 | hw version [ 23.883259] iwlwifi :00:14.3: 0x00480002 | board version [ 23.883262] iwlwifi :00:14.3: 0x8076FF00 | hcmd [ 23.883265] iwlwifi :00:14.3: 0x0002 | isr0 [ 23.883268] iwlwifi :00:14.3: 0x | isr1 [ 23.883270] iwlwifi :00:14.3: 0x48F04002 | isr2 [ 23.883274] iwlwifi :00:14.3: 0x00C3008C | isr3 [ 23.883276] iwlwifi :00:14.3: 0x | isr4 [ 23.883279] iwlwifi :00:14.3: 0x0518001C | last cmd Id [ 23.883282] iwlwifi :00:14.3: 0x000157E2 | wait_event [ 23.883285] iwlwifi :00:14.3: 0x | l2p_control [ 23.883288] iwlwifi :00:14.3: 0x | l2p_duration [ 23.883291] iwlwifi :00:14.3: 0x | l2p_mhvalid [ 23.883294] iwlwifi :00:14.3: 0x | l2p_addr_match [ 23.883297] iwlwifi :00:14.3: 0x0018 | lmpm_pmg_sel [ 23.883300] iwlwifi :00:14.3: 0x | timestamp [ 23.883303] iwlwifi :00:14.3: 0xF0B4 | flow_handler [ 23.883386] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 23.883389] iwlwifi :00:14.3: Transport status: 0x004B, valid: 7 [ 23.883393] iwlwifi :00:14.3: 0x20103609 | ADVANCED_SYSASSERT [ 23.883397] iwlwifi :00:14.3: 0x | umac branchlink1 [ 23.883400] iwlwifi :00:14.3: 0x80471ABC | umac branchlink2 [ 23.883403] iwlwifi :00:14.3: 0xC0081892 | umac interruptlink1 [ 23.883406] iwlwifi :00:14.3: 0x | umac interruptlink2 [ 23.883409] iwlwifi :00:14.3: 0x0027 | umac data1 [ 23.883412] iwlwifi :00:14.3: 0x0001 | umac data2 [ 23.883414] iwlwifi :00:14.3: 0x | umac data3 [ 23.883417] iwlwifi :00:14.3: 0x0053 | umac major [ 23.883420] iwlwifi :00:14.3: 0xE8F84E98 | umac minor [ 23.883423] iwlwifi :00:14.3: 0x0112D24E | frame pointer [ 23.883426] iwlwifi :00:14.3: 0xC0886C08 | stack pointer [ 23.883429] iwlwifi :00:14.3: 0x0085010D | last host cmd [ 23.883432] iwlwifi :00:14.3: 0x | isr status reg [ 23.883491] iwlwifi :00:14.3: IML/ROM dump: [ 23.883494] iwlwifi :00:14.3: 0x0B03 | IML/ROM error/state [ 23.883553] iwlwifi :00:14.3: 0x8105 | IML/ROM data1 [ 23.883616] iwlwifi :00:14.3: 0x0090 | IML/ROM WFPM_AUTH_KEY_0 [ 23.883673] iwlwifi :00:14.3: Fseq Registers: [ 23.883726] iwlwifi :00:14.3: 0x6000 | FSEQ_ERROR_CODE [ 23.883779] iwlwifi :00:14.3: 0x003E0003 | FSEQ_TOP_INIT_VERSION [
[Kernel-packages] [Bug 2041668] Re: Memory leak in 23.10 kernel (6.5.0-10)
** Also affects: linux-meta-hwe-6.5 (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/2041668 Title: Memory leak in 23.10 kernel (6.5.0-10) Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: Confirmed Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: There appears to be a memory 'leak' in the kernel of the latest Ubuntu release (Mantic Minotaur, kernel version 6.5.0-10). I put 'leak' in quotes because this memory appears to be allocated but never used. The kernel's memory over-commit mechanism seems to prevent this leak from manifesting in OOM killer triggers or other failures. The primary symptom is a steady increase in the value reported as 'Committed_AS' in '/proc/meminfo'. The other memory stats reported there remain reasonable, though. I've observed this problem on a fairly diverse set of machines (both VMs and physical machines) with a variety of workloads. Busier machines seem to have a faster leak rate. I've tried to narrow down the issue by rebooting into single user mode, killing all userspace processes (except the systemd processes) and removing as many kernel models as possible. The problem continues in that state. I didn't see any obvious culprits in /proc/slabinfo nor /proc/vmallocinfo. So far, the only way I've been able to remediate this issue is to reboot back into the Lunar Lobster kernel (6.2.0-35). I think this fact alone rules out any triggers that may be part of the 23.10 userspace environment. I've attached the generic debug info requested by this component's bug template from an example machine. Please let me know if there is any more information I can provide. It seems to be pretty trivial to reproduce though, and I'm guessing it has not been reported yet because the leak doesn't actually manifest in an out-of-memory situation. At least, I haven't observed that yet. The worst case I've observed was 150 GB of memory committed on a machine with 16 GB of physical RAM after about 24 hours. Moving back to the previous kernel version, the committed memory statistic holds fairly steady around 7 GB on that machine and workload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040106] Autopkgtest regression report (linux-meta/6.5.0.17.19)
All autopkgtests for the newly accepted linux-meta (6.5.0.17.19) for mantic
have finished running.
The following regressions have been reported in tests triggered by the package:
initramfs-tools/0.142ubuntu15.1 (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#linux-meta
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2040106
Title:
firmware broken after upgrade to Ubuntu 23.10
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-meta package in Ubuntu:
Fix Released
Bug description:
[ Impact ]
* Focal preinstalled systems with OEM kernel, if force upgraded to
interim releases, before transitional packages have been made
available resulted in systems having been stuck on focal oem kernel
and not getting any kernel updates.
* Reintroduce all focal oem kernel transitionals to trigger upgrade
to hwe kernel in all stable releases for the oem-20.04* kernels
[ Test Plan ]
* Starting with focal, install linux-image-oem-20.04*
linux-headers-oem-20.04* metapackages
* Force upgrade to mantic
* Observe that all oem-20.04 meta packages got upgraded and rolled to
generic hwe kernel (of appropriate version for jammy & mantic)
[ Where problems could occur ]
* This may trigger dkms package recompilation, and nvidia driver missmatches
* Likely users will have to rerun `ubuntu-drivers` or use additional drivers
GUI to reinstall nvidia drivers
* Users may experience jump from v5.10 kernel to v6.5 kernel
[ Other Info ]
* Original bug report
After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and
bluetooth did not work anymore.
Looking at the dmesg output I saw this:
Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
..
Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
no suitable firmware found!
minimum version required: iwlwifi-QuZ-a0-hr-b0-39
minimum version required: iwlwifi-QuZ-a0-hr-b0-59
These files did seem to exist in /lib/firmware.
I did sudo apt install linux-firmware/mantic --reinstall
Which did not fix it.
I manually overwrote the iwlwifi... files with the corresponding files from
linux-firmware-20230804.tar.gz and this did fix the issue.
I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.
So my best guess is that something is wrong in the latest firmware
package.
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic
apt-cache policy linux-firmware
linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
*** 20230919.git3672ccab-0ubuntu2.1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
Uname: Linux 5.10.0-1053-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: joep 2545 F wireplumber
/dev/snd/controlC0: joep 2545 F wireplumber
/dev/snd/seq:joep 2537 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 15:19:18 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85
InstallationDate: Installed on 2021-10-16 (736 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.10.0-1053-oem N/A
linux-backports-modules-5.10.0-1053-oem N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
dmi.bios.date: 07/13/2023
dmi.bios.release: 1.22
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.22.0
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/6.5.0.17.19)
All autopkgtests for the newly accepted linux-meta (6.5.0.17.19) for mantic have finished running. The following regressions have been reported in tests triggered by the package: initramfs-tools/0.142ubuntu15.1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049674] [NEW] package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from othe
Public bug reported: I tried to switch from nouveau to nvdidia-390 (in Additional Drivers) and got the above error message. The proprietary driver will not install. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 17 14:30:02 2024 DuplicateSignature: package:libnvidia-compute-390:(not installed) Unpacking libnvidia-compute-390:amd64 (390.157-0ubuntu0.22.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-QgW0Up/63-libnvidia-compute-390_390.157-0ubuntu0.22.04.2_amd64.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 ErrorMessage: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 InstallationDate: Installed on 2024-01-16 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049674 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I tried to switch from nouveau to nvdidia-390 (in Additional Drivers) and got the above error message. The proprietary driver will not install. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 17 14:30:02 2024 DuplicateSignature: package:libnvidia-compute-390:(not installed) Unpacking libnvidia-compute-390:amd64 (390.157-0ubuntu0.22.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-QgW0Up/63-libnvidia-compute-390_390.157-0ubuntu0.22.04.2_amd64.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 ErrorMessage: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 InstallationDate: Installed on 2024-01-16 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
This issue appears on my Thinkpad T-series as well when saving or
removing a state with zsysd. In my case on a LUKS-encrypted (not sure if
it matters) drive with kernel linux-image-6.5.0-14-generic.
```# zsysctl save --system
ZSys is adding automatic system snapshot to GRUB menu
Successfully saved as "autozsys_xnh1ue"
```
```journalctl -f
Jan 17 18:48:41 kernel: evict_inodes inode 6a2639d6, i_count
= 1, was skipped!
Jan 17 18:48:41 kernel: evict_inodes inode 6a2639d6, i_count
= 1, was skipped!```
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to :
[Kernel-packages] [Bug 2045622] Re: RTL8852CE WIFI read country list supporting 6 GHz from BIOS
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2045622 Title: RTL8852CE WIFI read country list supporting 6 GHz from BIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] Realtek provides a patchset to enable this feature https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t The patchset has been included in linux-next/master c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] Run `iw list` should see the available frequency above 6Ghz, even it's disabled Frequencies: ... * 6835 MHz [177] (disabled) * 6855 MHz [181] (disabled) * 6875 MHz [185] (disabled) * 6895 MHz [189] (disabled) * 6915 MHz [193] (disabled) * 6935 MHz [197] (disabled) * 6955 MHz [201] (disabled) * 6975 MHz [205] (disabled) * 6995 MHz [209] (disabled) * 7015 MHz [213] (disabled) * 7035 MHz [217] (disabled) * 7055 MHz [221] (disabled) * 7075 MHz [225] (disabled) * 7095 MHz [229] (disabled) * 7115 MHz [233] (disabled) [Where problems could occur] Should have some impact to current RTL devices, but didn't see any fix patches for the 3 commits now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047398] Re: Add missing RPL P/U CPU IDs
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047398 Title: Add missing RPL P/U CPU IDs Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Without the correct GPU ID in the driver, the system will default to framebuffer mode, and some graphics functions may not work properly. [Fix] Below commit included in v6.7-rc1 adds the missing IDs 5d5fea7c79a7 drm/i915/rpl: Update pci ids for RPL P/U [Test case] 1. check the system with GPU ID A7AC or A7AD 2. boot the system into desktop and connecting a monior by HDMI cable with HDMI port or Type-C port 3. make sure the external monitor works [Where problems could occur] Add only IDs; there is no potential for regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047184] Re: Audio device is not available, instead it shows dummy output in the settings
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047184 Title: Audio device is not available, instead it shows dummy output in the settings Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Audio device is not available, instead it shows dummy output in the settings [Fix] SOF driver looks for a config which both sample width and valid bits are both 32 bits. However, the config in NHLT table is 32-bit sample width and 24-bit valid bits. Should ignore the valid bits in NHLT when the sample width is 32 bits. Confirmed the below commit in v6.7-rc4 fix the issue 7b4c93a50a2e ALSA: hda: intel-nhlt: Ignore vbps when looking for DMIC 32 bps format [Test case] 1. check audio input/output on the system 2. System can play and record audio normally [Where problems could occur] When the samples assumed to be vbps=32 then the 'noise' introduced by the lower two bits (channel number) have no real life implication on audio quality. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047518] Re: Fix BCM57416 lost after resume
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047518 Title: Fix BCM57416 lost after resume Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] BCM57416 is lost after resume. Error log: [ 1261.429834] bnxt_en :82:00.1 enp130s0f1np1: hwrm req_type 0x50 seq id 0x125d error 0x4 [ 1261.429843] bnxt_en :82:00.1 enp130s0f1np1: hwrm_ring_alloc type 1 failed. rc:ffe4 err:4 [ 1261.429846] bnxt_en :82:00.1 enp130s0f1np1: hwrm ring alloc failure rc: fffb [ 1261.437389] bnxt_en :82:00.1 enp130s0f1np1: bnxt_init_nic err: fffb [Fix] Clear the reservations in driver after reset the ethernet card. [Test] Tested on hardware, after 10 times of suspend/resume, bnxt ethernet works fine. [Where problems could occur] It may break broadcom bnxt driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046504] Re: Fix AMDGPU display on lower resolution modes
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046504 Title: Fix AMDGPU display on lower resolution modes Status in HWE Next: In Progress Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Bug description: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes are set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. This issue is not reproduced on v6.2- kernel versions, so SRU for oem-6.5 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047389] Re: Fix AMDGPU crash on 6.5 kernel
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047389 Title: Fix AMDGPU crash on 6.5 kernel Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] AMD GPU crash with a message: " cp queue preemption timeout". [Fix] Disable MCBP(mid command buffer preemption) by default as old Mesa hangs with it. [Test] Tested on hardware, play web video for more than 1 hour OK. [Where problems could occur] It may break AMD GPU. This issue is only reproduced on v6.5+ kernel versions and fixes in v6.6, so SRU for oem-6.5, mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
** Description changed: - 5.15 Kernel Warnings with some Sapphire Rapids CPUs - - On some Sapphire Rapids CPUs we are seeing Kernel warnings in the syslog: + [Impact] + On some Sapphire Rapids CPUs we are seeing Kernel warnings in the kern.log: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] Code: c2 01 48 83 c0 04 39 d1 0f 8e c6 01 00 00 49 8b 4c 24 38 8b 0c 01 41 89 0c 07 49 8b 74 24 40 8b 34 06 41 89 34 06 39 f9 75 cf <0f> 0b 4c 89 ff e8 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ? type_pmu_register+0x42/0x42 Oct 31 03:35:55 N8 kernel: [ 95.500506] do_one_initcall+0x46/0x1e0 Oct 31 03:35:55 N8 kernel: [ 95.546475] do_initcalls+0x12f/0x159 Oct 31 03:35:55 N8 kernel: [ 95.590372] kernel_init_freeable+0x162/0x1b5 Oct 31 03:35:55 N8 kernel: [ 95.642556] ? rest_init+0x100/0x100 Oct 31 03:35:55 N8 kernel: [ 95.685405] kernel_init+0x1b/0x150 Oct 31 03:35:55 N8 kernel: [ 95.727228] ? rest_init+0x100/0x100 Oct 31 03:35:55 N8 kernel: [ 95.770054] ret_from_fork+0x1f/0x30 Oct 31 03:35:55 N8 kernel: [ 95.812906] Oct 31 03:35:55 N8 kernel: [ 95.839108] ---[ end trace 2d0c57130f45fd62 ]--- https://certification.canonical.com/hardware/202305-31570/submission/312593/ Intel(R) Xeon(R) Gold 6426Y Apr 14 17:29:28 ML110Gen11 kernel: [2.135184]
[Kernel-packages] [Bug 2047504] Re: Mute/mic LEDs and speaker no function on some HP platforms
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047504 Title: Mute/mic LEDs and speaker no function on some HP platforms Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Bug description: [Impact] The mic mute/audio mute LEDS and speaker are not work on some HP platforms. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs and speaker are working good. Applied on oem-6.5 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047461] Re: drm: Update file owner during use
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047461 Title: drm: Update file owner during use Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Our testing tools need to check the app runs on which GPU, and now it only shows the processes as Xorg or XWayland $ cat /sys/kernel/debug/dri/0/clients command pid dev master a uid magic Xorg 2344 0 yy 0 0 Xorg 2344 0 ny 0 2 Xorg 2344 0 ny 0 3 Xorg 2344 0 ny 0 4 [Fix] The commit from v6.7-rc1 fixes the issue $ cat /sys/kernel/debug/dri/0/clients command tgid dev master a uid magic Xorg 830 0 yy 0 0 xfce4-session 880 0 ny 0 1 xfwm4 943 0 ny 0 2 neverball 1095 0 ny 0 3 [Test case] 1. check processes by 'cat /sys/kernel/debug/dri/0/clients' 2. runs glxgears(specify the GPU if needed) 3. check the precesses again and there should be a 'glxgears' process [Where problems could occur] This commit added some protections on read/write and only changes the process' pid, the worst case is that the process got the wrong pid as its owner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048729] Re: Mute/mic LEDs no function on HP ZBook
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048729 Title: Mute/mic LEDs no function on HP ZBook Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Confirmed Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ZBook [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. Applied on oem-6.5 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2048729/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049184] Re: iwlwifi leads to system randomly hangs after suspend
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049184 Title: iwlwifi leads to system randomly hangs after suspend Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The system randomly hangs while doing s2idle test. [Fix] Intel found the issue and provided a fix. https://patchwork.kernel.org/project/linux-wireless/patch/2024045954.2d2b8b870194.I14ed76505a5cf87304e0c9cc05cc0ae85ed3bf91@changeid/ [Test case] Boot up the system and run the s2idle test around 1000 times sudo fwts s3 --s3-multiple=1000 [Where problems could occur] The fix is trivial and should no introduce any issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049537] Re: Pull request for: peer-memory, ACPI thermal issues and coresight etm4x issues
** Changed in: linux-nvidia-6.5 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049537 Title: Pull request for: peer-memory, ACPI thermal issues and coresight etm4x issues Status in linux-nvidia-6.5 package in Ubuntu: Fix Committed Bug description: * Add support of "Thermal fast Sampling Period (_TFP)" for passive cooling. * Finer grained CPU throttling * The peer_memory_client scheme allows a driver to register with the ib_umem system that it has the ability to understand user virtual address ranges that are not compatible with get_user_pages(). For instance VMAs created with io_remap_pfn_range(), or other driver special VMA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2049537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
Found this commit in mainline and our 6.5 HWE kernel. Checking now to see if there are any prerequisites as well. commit 5d515ee40cb57ea5331998f27df7946a69f14dc3 Author: Kan Liang Date: Thu Jan 12 12:01:05 2023 -0800 perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table -- 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/2049637 Title: Some SPR systems throw kernel warnings from uncore_discovery.c Status in intel: New Status in linux package in Ubuntu: New Bug description: 5.15 Kernel Warnings with some Sapphire Rapids CPUs On some Sapphire Rapids CPUs we are seeing Kernel warnings in the syslog: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] Code: c2 01 48 83 c0 04 39 d1 0f 8e c6 01 00 00 49 8b 4c 24 38 8b 0c 01 41 89 0c 07 49 8b 74 24 40 8b 34 06 41 89 34 06 39 f9 75 cf <0f> 0b 4c 89 ff e8 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ? type_pmu_register+0x42/0x42 Oct 31 03:35:55 N8 kernel: [ 95.500506] do_one_initcall+0x46/0x1e0 Oct 31 03:35:55 N8 kernel: [ 95.546475] do_initcalls+0x12f/0x159 Oct 31 03:35:55 N8 kernel: [ 95.590372] kernel_init_freeable+0x162/0x1b5 Oct 31 03:35:55 N8 kernel: [ 95.642556] ? rest_init+0x100/0x100 Oct 31 03:35:55
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@Giuliano Still in progress ... 1. Installed: sudo apt install gcc-12 2. Then: sudo apt install dwarves 3. Then: cp /sys/kernel/btf/vmlinux /usr/lib/modules/$(uname -r)/build/ 4. Made reinstall kernell: sudo apt-get install --reinstall linux-image-6.5.0-14-generic 5. Deleted all version "linux" in home directory And now have Error: Failed to parse base BTF 'vmlinux': -22 Could you give me some more ideas to fix this? Below Error from terminal after started "make" make: Entering directory '/usr/src/linux-headers-6.5.0-14-generic' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0 You are using: gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0 CC [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvc_driver.o CC [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvc_queue.o CC [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvc_v4l2.o CC [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvc_video.o CC [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvc_ctrl.o CC [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvc_status.o CC [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvc_isight.o CC [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvc_debugfs.o CC [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvc_metadata.o CC [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvc_entity.o LD [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvcvideo.o MODPOST /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/Module.symvers CC [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvcvideo.mod.o LD [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvcvideo.ko BTF [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvcvideo.ko Failed to parse base BTF 'vmlinux': -22 make[2]: *** [scripts/Makefile.modfinal:60: /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvcvideo.ko] Error 1 make[2]: *** Deleting file '/home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvcvideo.ko' make[1]: *** [/usr/src/linux-headers-6.5.0-14-generic/Makefile:1957: modules] Error 2 make: *** [Makefile:234: __sub-make] Error 2 make: Leaving directory '/usr/src/linux-headers-6.5.0-14-generic' cp: cannot stat 'uvcvideo.ko': No such file or directory rmmod: ERROR: Module uvcvideo is not currently loaded *** -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules
[Kernel-packages] [Bug 2045517] Re: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S
are these all in 6.7? ** Changed in: linux (Ubuntu Mantic) Status: New => Won't Fix ** 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-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2045517 Title: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] To support HP stella's latest machine, we need to backport some new PCIIDs and corresponding drivers to our OEM kernel, the requirement is here: https://docs.google.com/spreadsheets/d/1_usKzZDxjtqlUzdOUPXvzNzSzhjRqcaV/edit#gid=1748766508 This pull-request is to unitfy and add some audio controller's ID, but to do so, need to apply some depending patches otherwise it will have conflict to introduce the new ID and new driver to OEM kernel. unified PCIIDs: PCI_DEVICE_ID_INTEL_HDA_ADL_N PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 PCI_DEVICE_ID_INTEL_HDA_ADL_P PCI_DEVICE_ID_INTEL_HDA_RPL_S PCI_DEVICE_ID_INTEL_HDA_MTL new added PCIID: PCI_DEVICE_ID_INTEL_HDA_ARL_S [Fix] This add the audio driver for machines with Intel Arrowlake. [Test case] Boot the patched kernel on a Arrowlake machine, the audio function could work. Boot the patches kernel on non-Arrowlake machines, the audio function could work as well as before. [Where problems could occur] Could lose some pciids and make the auido driver not work on those machines, and could not play sound or record sound. But this possibility is very low, I checked each patch carefully and I verify the patcheset on some lenovo an dell machines. From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based on it, added new PCIID and audio support for arrowlake-s, need to backport them to oem-6.5, this is a preparation for supporting HP latest laptops: unified PCIIDs: PCI_DEVICE_ID_INTEL_HDA_ADL_N PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 PCI_DEVICE_ID_INTEL_HDA_ADL_P PCI_DEVICE_ID_INTEL_HDA_RPL_S PCI_DEVICE_ID_INTEL_HDA_MTL new added PCIID: PCI_DEVICE_ID_INTEL_HDA_ARL_S To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
** Also affects: intel 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/2049637 Title: Some SPR systems throw kernel warnings from uncore_discovery.c Status in intel: New Status in linux package in Ubuntu: New Bug description: 5.15 Kernel Warnings with some Sapphire Rapids CPUs On some Sapphire Rapids CPUs we are seeing Kernel warnings in the syslog: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] Code: c2 01 48 83 c0 04 39 d1 0f 8e c6 01 00 00 49 8b 4c 24 38 8b 0c 01 41 89 0c 07 49 8b 74 24 40 8b 34 06 41 89 34 06 39 f9 75 cf <0f> 0b 4c 89 ff e8 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ? type_pmu_register+0x42/0x42 Oct 31 03:35:55 N8 kernel: [ 95.500506] do_one_initcall+0x46/0x1e0 Oct 31 03:35:55 N8 kernel: [ 95.546475] do_initcalls+0x12f/0x159 Oct 31 03:35:55 N8 kernel: [ 95.590372] kernel_init_freeable+0x162/0x1b5 Oct 31 03:35:55 N8 kernel: [ 95.642556] ? rest_init+0x100/0x100 Oct 31 03:35:55 N8 kernel: [ 95.685405] kernel_init+0x1b/0x150 Oct 31 03:35:55 N8 kernel: [ 95.727228] ? rest_init+0x100/0x100 Oct 31 03:35:55 N8 kernel: [ 95.770054] ret_from_fork+0x1f/0x30 Oct 31 03:35:55 N8 kernel: [
[Kernel-packages] [Bug 2049390] Re: Please change CONFIG_CONSOLE_LOGLEVEL_QUIET to 3
I am not sure, which will need to be doublechecked but this may affect boot testing, regression testing, device cert testing that do look for these messages. Hopefully they all know how to hunt for these messages elsehow, rather than via the graphical console log capture. -- 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/2049390 Title: Please change CONFIG_CONSOLE_LOGLEVEL_QUIET to 3 Status in linux package in Ubuntu: Confirmed Bug description: The Ubuntu Desktop boot isn't flickerfree today as reported on bug #1970069 , one of the reason is that kernel error messages are often being logged and not filtered out by our default loglevel (one example with usb messages on https://launchpadlibrarian.net/598152686/20220422_014058.jpg) Fedora is using CONFIG_CONSOLE_LOGLEVEL_QUIET=3 (instead of 4 which is the default), they change it 5 years ago (https://src.fedoraproject.org/rpms/kernel/c/838818e5), the rational is in the commit message that added the configuration option to the kernel > This for example will allow distros which want quiet to really mean quiet to set > CONSOLE_LOGLEVEL_QUIET so that only messages with a higher severity then KERN_ERR (CRIT, ALERT, EMERG) > get printed, avoiding an endless game of whack-a-mole silencing harmless error messages. ' Could we also get the default change to 3 in Ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049637] [NEW] Some SPR systems throw kernel warnings from uncore_discovery.c
Public bug reported: 5.15 Kernel Warnings with some Sapphire Rapids CPUs On some Sapphire Rapids CPUs we are seeing Kernel warnings in the syslog: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] Code: c2 01 48 83 c0 04 39 d1 0f 8e c6 01 00 00 49 8b 4c 24 38 8b 0c 01 41 89 0c 07 49 8b 74 24 40 8b 34 06 41 89 34 06 39 f9 75 cf <0f> 0b 4c 89 ff e8 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ? type_pmu_register+0x42/0x42 Oct 31 03:35:55 N8 kernel: [ 95.500506] do_one_initcall+0x46/0x1e0 Oct 31 03:35:55 N8 kernel: [ 95.546475] do_initcalls+0x12f/0x159 Oct 31 03:35:55 N8 kernel: [ 95.590372] kernel_init_freeable+0x162/0x1b5 Oct 31 03:35:55 N8 kernel: [ 95.642556] ? rest_init+0x100/0x100 Oct 31 03:35:55 N8 kernel: [ 95.685405] kernel_init+0x1b/0x150 Oct 31 03:35:55 N8 kernel: [ 95.727228] ? rest_init+0x100/0x100 Oct 31 03:35:55 N8 kernel: [ 95.770054] ret_from_fork+0x1f/0x30 Oct 31 03:35:55 N8 kernel: [ 95.812906] Oct 31 03:35:55 N8 kernel: [ 95.839108] ---[ end trace 2d0c57130f45fd62 ]--- https://certification.canonical.com/hardware/202305-31570/submission/312593/ Intel(R) Xeon(R) Gold 6426Y Apr 14 17:29:28 ML110Gen11 kernel: [2.135184] [ cut here ] Apr 14 17:29:28 ML110Gen11 kernel: [2.135185] WARNING: CPU: 0 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Apr 14 17:29:28 ML110Gen11
[Kernel-packages] [Bug 2049635] [NEW] Roll UDA & ERD drivers from 525 to 535
Public bug reported: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. ** Affects: fabric-manager-535 (Ubuntu) Importance: Undecided Status: New ** Affects: libnvidia-nscq-535 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Also affects: fabric-manager-535 (Ubuntu) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-535 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-535 package in Ubuntu: New Status in libnvidia-nscq-535 package in Ubuntu: New Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2049635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032672] Re: Update the 535 UDA and 535 ERD NVIDIA driver series in Bionic, Focal, and Jammy, Lunar
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: In Progress => Fix Released
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
Status: In Progress => Fix Released
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Focal)
Status: In Progress => Fix Released
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Jammy)
Status: In Progress => Fix Released
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Lunar)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2032672
Title:
Update the 535 UDA and 535 ERD NVIDIA driver series in Bionic, Focal,
and Jammy, Lunar
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-535 source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-535-server source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-535 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-535 source package in Lunar:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Lunar:
Fix Released
Bug description:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
[Discussion]
[Changelog]
[ Alberto Milone ]
* New upstream release (LP: #2025243).
* debian/rules{.defs}:
- Adjust to the changes on the Nvidia servers.
* debian/rules:
- Do not start the systemd services on installation or upgrade, as this
can
lead to a black screen.
[ Dimitri John Ledkov ]
* debian/templates/control.in:
- Add breaks on identical firmware files from other flavour.
When 535 & 535-server driver versions happen to be at an identical
upstream version, they both ship identical firmware files on disk at
the same path. When a user attempts to install two drivers at the same
time, this results in dpkg file conflict. Allow replacing one firmware
with another (LP: #2026622).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2032672/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027746] Re: package libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2027746 Title: package libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux- gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Released Bug description: It occurs on start up[ ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 13 16:04:37 2023 DpkgTerminalLog: Preparing to unpack .../libnvidia-compute-535-server_535.54.03-0ubuntu0.22.04.1_amd64.deb ... Unpacking libnvidia-compute-535-server:amd64 (535.54.03-0ubuntu0.22.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libnvidia-compute-535-server_535.54.03-0ubuntu0.22.04.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 InstallationDate: Installed on 2023-06-23 (20 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: nvidia-graphics-drivers-535-server Title: package libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2027746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049634] [NEW] SMB 1 broken in kernel 6.5.0.14.14~22.04.7
Public bug reported: Hi all: I upgraded my Ubuntu yesterday and automatically got the newer Linux Kernel version 6.5.0-14-generic #14~22.04.1-Ubuntu. Previously, I was running kernel version 6.2 . I still have a legacy system on the network using SMB protocol version 1.0. With the new kernel version, copying files does not work reliably anymore. Some random byte blocks in the destination files are overwritten with binary zeros. It happens quite often. This is not the first time the Linux guys temporarily break SMB protocol version 1.0, see for example this bug report of mine: https://bugs.launchpad.net/ubuntu/+bug/2033732 I checked package linux-image-generic-hwe-22.04 with Synaptic, and now it lists just 2 versions: 6.5.0.14.14~22.04.7 (jammy-updates) 5.15.0.25.27 (jammy) Is there a way to go back to the latest 6.2 kernel version? How do I prevent Ubuntu from upgrading to 6.5 next time around? I have searched the Internet, but I haven't found yet a usable answer. I don't want to go back all the way to Kernel 5.15 if I can avoid it. Thanks in advance, rdiez ** Affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049634 Title: SMB 1 broken in kernel 6.5.0.14.14~22.04.7 Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Hi all: I upgraded my Ubuntu yesterday and automatically got the newer Linux Kernel version 6.5.0-14-generic #14~22.04.1-Ubuntu. Previously, I was running kernel version 6.2 . I still have a legacy system on the network using SMB protocol version 1.0. With the new kernel version, copying files does not work reliably anymore. Some random byte blocks in the destination files are overwritten with binary zeros. It happens quite often. This is not the first time the Linux guys temporarily break SMB protocol version 1.0, see for example this bug report of mine: https://bugs.launchpad.net/ubuntu/+bug/2033732 I checked package linux-image-generic-hwe-22.04 with Synaptic, and now it lists just 2 versions: 6.5.0.14.14~22.04.7 (jammy-updates) 5.15.0.25.27 (jammy) Is there a way to go back to the latest 6.2 kernel version? How do I prevent Ubuntu from upgrading to 6.5 next time around? I have searched the Internet, but I haven't found yet a usable answer. I don't want to go back all the way to Kernel 5.15 if I can avoid it. Thanks in advance, rdiez To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2049634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038583] Re: Turning COMPAT_32BIT_TIME off on s390x
Thx Andreas for your +1 -- 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/2038583 Title: Turning COMPAT_32BIT_TIME off on s390x Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This will prevent existing s390 binaries to operate correctly, if they are still using 32bit time. 24.04 LTS is likely to be used for 10 years. And if allowed to overrun and remain active in the field in 2038 can lead to catastrophic failure in the field due to these syscalls enabled and used. I would like to request if we can turn off COMPAT_32BIT_TIME on every architecture, thus this will be arch by arch bug report, and arch by arch decision. This needs to be a per-arch decision, potentially taking into consideration bi-arch userspace support. config COMPAT_32BIT_TIME bool "Provide system calls for 32-bit time_t" default !64BIT || COMPAT help This enables 32 bit time_t support in addition to 64 bit time_t support. This is relevant on all 32-bit architectures, and 64-bit architectures as part of compat syscall handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2038583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044427] Re: Kernel panic in restart driver after configuring IPsec full offload
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2044427 Title: Kernel panic in restart driver after configuring IPsec full offload Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: Bug description: Restarting the driver with IPsec full offload transparent mode configuration causes kernel panic. Kernel version is linux-bluefield 5.15 Test step: 1) configure xfrm rules 2) configure VF 3) configure FW steering mode 4) restart driver 5) check dmesg Test result: [ 937.989359] [ cut here ] [ 937.989786] WARNING: CPU: 11 PID: 60463 at /tmp/23.10-0.1.8/6.5.0-rc6_mlnx/fedora_32/mlnx-ofa_kernel/BUILD/mlnx-ofa_kernel-23.10/obj/default/drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec_fs.c:1828 mlx5e_accel_ipsec_fs_cleanup+0x298/0x2b0 [mlx5_core] [ 937.991650] Modules linked in: esp4_offload esp4 esp6_offload esp6 act_tunnel_key vxlan act_mirred act_skbedit cls_matchall act_gact cls_flower sch_ingress vringh vhost_iotlb udp_diag tcp_diag inet_diag iptable_raw mst_pciconf(OE) bonding ip6_gre ip6_tunnel tunnel6 vfio_pci vfio_pci_core vfio_iommu_type1 vfio ipip tunnel4 geneve ip6_udp_tunnel udp_tunnel ip_gre ip_tunnel gre rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) ib_uverbs(OE) mlx5_core(OE-) mlxdevm(OE) ib_core(OE) mlx_compat(OE) mlxfw(OE) memtrack(OE) pci_hyperv_intf openvswitch nsh nf_conncount nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_filter iptable_nat nf_nat br_netfilter bridge stp llc rfkill overlay kvm_intel sch_fq_codel kvm iTCO_wdt irqbypass iTCO_vendor_support crc32_pclmul pcspkr ghash_clmulni_intel i2c_i801 lpc_ich sha512_ssse3 i2c_smbus mfd_core sunrpc drm i2c_ core ip_tables crc32c_intel serio_raw [ 937.991698] fuse virtio_net net_failover failover [last unloaded: vdpa] [ 937.999155] CPU: 11 PID: 60463 Comm: modprobe Tainted: G OE 6.5.0-rc6_mlnx #1 [ 937.999891] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 [ 938.000823] RIP: 0010:mlx5e_accel_ipsec_fs_cleanup+0x298/0x2b0 [mlx5_core] [ 938.001459] Code: f6 45 31 c0 48 89 ea 31 ff e8 d4 d5 df ff 59 e9 8c fe ff ff c3 0f 0b e9 3b fe ff ff 0f 0b e9 e8 fd ff ff 0f 0b e9 07 fe ff ff <0f> 0b e9 65 fe ff ff 0f 0b e9 82 fe ff ff 66 2e 0f 1f 84 00 00 00 [ 938.002949] RSP: 0018:c90001183c08 EFLAGS: 00010202 [ 938.003418] RAX: RBX: 8882f3869c00 RCX: 0001 [ 938.004024] RDX: 82a305c0 RSI: 0002 RDI: 888103aa2b30 [ 938.004624] RBP: 888103aa2d80 R08: 0001 R09: 888100042800 [ 938.005238] R10: 0002 R11: c90001183ba8 R12: 8881312e6800 [ 938.005836] R13: 8881127401a0 R14: 8881312e6800 R15: 888148bbd160 [ 938.006444] FS: 7fd22b82c740() GS:5fac() knlGS: [ 938.009456] CS: 0010 DS: ES: CR0: 80050033 [ 938.009970] CR2: 7f26ca697000 CR3: 00012e73f003 CR4: 00770ee0 [ 938.010568] DR0: DR1: DR2: [ 938.011173] DR3: DR6: fffe0ff0 DR7: 0400 [ 938.011772] PKRU: 5554 [ 938.012065] Call Trace: [ 938.012333] [ 938.012583] ? __warn+0x7d/0x120 [ 938.012921] ? mlx5e_accel_ipsec_fs_cleanup+0x298/0x2b0 [mlx5_core] [ 938.013494] ? report_bug+0xf1/0x1c0 [ 938.013850] ? handle_bug+0x44/0x70 [ 938.014201] ? exc_invalid_op+0x13/0x60 [ 938.014568] ? asm_exc_invalid_op+0x16/0x20 [ 938.014970] ? mlx5e_accel_ipsec_fs_cleanup+0x298/0x2b0 [mlx5_core] [ 938.015532] ? mlx5e_accel_ipsec_fs_cleanup+0xf2/0x2b0 [mlx5_core] [ 938.016093] mlx5e_ipsec_cleanup+0x1e/0x100 [mlx5_core] [ 938.016594] mlx5e_detach_netdev+0x46/0x80 [mlx5_core] [ 938.017098] mlx5e_vport_rep_unload+0x147/0x1a0 [mlx5_core] [ 938.017623] mlx5_eswitch_unregister_vport_reps+0x13e/0x190 [mlx5_core] [ 938.018221] auxiliary_bus_remove+0x18/0x30 [ 938.018616] device_release_driver_internal+0xaa/0x130 [ 938.019076] bus_remove_device+0xc3/0x130 [ 938.019451] device_del+0x157/0x380 [ 938.019792] ? kobject_put+0xb3/0x200 [ 938.020153] delete_drivers+0x72/0xa0 [mlx5_core] [ 938.020608] mlx5_unregister_device+0x34/0x70 [mlx5_core] [ 938.021113] mlx5_uninit_one+0x25/0x130 [mlx5_core] [ 938.021572] remove_one+0x72/0xc0 [mlx5_core] [ 938.022002] pci_device_remove+0x31/0xb0 [
[Kernel-packages] [Bug 2045919] Re: mlxbf-bootctl: fails to report info about cards using dev keys
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2045919 Title: mlxbf-bootctl: fails to report info about cards using dev keys Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] There is a gap in the mlxbf-bootctl driver logic, resulting in failure to report when a secure boot enabled card is using development keys. The program will instead report lifecycle state as "GA Secured" which is misleading. [Fix] Bring in the following upstream commit from linux-next: "mlxbf-bootctl: correctly identify secure boot with development keys" [Test Case] Enable secure boot on a BF3 card that is using development keys Login as root on BF3 Run the command "mlxbf-bootctl" Verify that the "lifecycle state" row shows "Secured (development)" [Regression Potential] Low risk change, cherry pick of upstream approved commit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2045919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047853] Re: mlxbf_gige: replace SAUCE patch for RX race condition
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2047853 Title: mlxbf_gige: replace SAUCE patch for RX race condition Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] There is a SAUCE patch that addresses a mlxbf-gige RX race condition "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic" This SAUCE patch should be reverted and replaced with upstream content. [Fix] Bring in the following upstream commit from linux-next: "mlxbf_gige: fix receive packet race condition" [Test Case] Boot BF3 platform and ensure oob_net0 interface is up and has IP address Send heavy level of traffic into the BF3 oob_net0 and make sure no stalls occur [Regression Potential] Low risk change, cherry pick of upstream approved commit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2047853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046657] Re: mmc: sdhci-of-dwcmshc: Replace sauce patches with upstream commits
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2046657 Title: mmc: sdhci-of-dwcmshc: Replace sauce patches with upstream commits Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The msdhci-of-dwcmshc driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. [Test Case] * Boot BF3 platform, verify no new errors [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2046657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038583] Comment bridged from LTC Bugzilla
--- Comment From andreas.kreb...@de.ibm.com 2024-01-17 07:24 EDT--- In the development team we agreed on disabling the 32 bit compat syscall layer in the kernel for IBM Z with Ubuntu 24.04. -- 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/2038583 Title: Turning COMPAT_32BIT_TIME off on s390x Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This will prevent existing s390 binaries to operate correctly, if they are still using 32bit time. 24.04 LTS is likely to be used for 10 years. And if allowed to overrun and remain active in the field in 2038 can lead to catastrophic failure in the field due to these syscalls enabled and used. I would like to request if we can turn off COMPAT_32BIT_TIME on every architecture, thus this will be arch by arch bug report, and arch by arch decision. This needs to be a per-arch decision, potentially taking into consideration bi-arch userspace support. config COMPAT_32BIT_TIME bool "Provide system calls for 32-bit time_t" default !64BIT || COMPAT help This enables 32 bit time_t support in addition to 64 bit time_t support. This is relevant on all 32-bit architectures, and 64-bit architectures as part of compat syscall handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2038583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049592] Re: [UBUNTU 22.04] createrepo_c not working under 22.04.3
** Package changed: linux (Ubuntu) => createrepo-c (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049592 Title: [UBUNTU 22.04] createrepo_c not working under 22.04.3 Status in createrepo-c package in Ubuntu: New Bug description: === Provided by Thorsten 2024-01-16 == We are running Ubuntu 22.04.3 on IBM Z. createrepo_c is not working and responds: createrepo_c: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory I seems that it is linked against openssl-1.1, but jammy provide openssl-3.0.2. Here is the output of ldd: ldd /usr/bin/createrepo_c linux-vdso64.so.1 (0x03ff85afe000) libcreaterepo_c.so.0 => /usr/local/lib/libcreaterepo_c.so.0 (0x03ff8590) libglib-2.0.so.0 => /lib/s390x-linux-gnu/libglib-2.0.so.0 (0x03ff8578) libmodulemd.so.2 => /usr/local/lib/libmodulemd.so.2 (0x03ff8570) libgobject-2.0.so.0 => /lib/s390x-linux-gnu/libgobject-2.0.so.0 (0x03ff8568) libc.so.6 => /lib/s390x-linux-gnu/libc.so.6 (0x03ff8548) libbz2.so.1.0 => /lib/s390x-linux-gnu/libbz2.so.1.0 (0x03ff8540) libcurl-gnutls.so.4 => /lib/s390x-linux-gnu/libcurl-gnutls.so.4 (0x03ff8530) libmagic.so.1 => /lib/s390x-linux-gnu/libmagic.so.1 (0x03ff8528) libxml2.so.2 => /lib/s390x-linux-gnu/libxml2.so.2 (0x03ff8508) liblzma.so.5 => /lib/s390x-linux-gnu/liblzma.so.5 (0x03ff8500) libcrypto.so.1.1 => not found librpm.so.8 => not found librpmio.so.8 => not found libsqlite3.so.0 => /lib/s390x-linux-gnu/libsqlite3.so.0 (0x03ff84e8) libz.so.1 => /lib/s390x-linux-gnu/libz.so.1 (0x03ff84e0) libzck.so.1 => /usr/local/lib/libzck.so.1 (0x03ff84d8) libpcre.so.3 => /lib/s390x-linux-gnu/libpcre.so.3 (0x03ff84d0) libm.so.6 => /lib/s390x-linux-gnu/libm.so.6 (0x03ff84c0) librpmio.so.8 => not found libyaml-0.so.2 => /lib/s390x-linux-gnu/libyaml-0.so.2 (0x03ff84b8) libffi.so.8 => /lib/s390x-linux-gnu/libffi.so.8 (0x03ff84b0) /lib/ld64.so.1 (0x03ff85a8) libnghttp2.so.14 => /lib/s390x-linux-gnu/libnghttp2.so.14 (0x03ff84a8) libidn2.so.0 => /lib/s390x-linux-gnu/libidn2.so.0 (0x03ff84a0) librtmp.so.1 => /lib/s390x-linux-gnu/librtmp.so.1 (0x03ff8498) libssh.so.4 => /lib/s390x-linux-gnu/libssh.so.4 (0x03ff8490) libpsl.so.5 => /lib/s390x-linux-gnu/libpsl.so.5 (0x03ff8488) libnettle.so.8 => /lib/s390x-linux-gnu/libnettle.so.8 (0x03ff8480) libgnutls.so.30 => /lib/s390x-linux-gnu/libgnutls.so.30 (0x03ff8460) libgssapi_krb5.so.2 => /lib/s390x-linux-gnu/libgssapi_krb5.so.2 (0x03ff8458) libldap-2.5.so.0 => /lib/s390x-linux-gnu/libldap-2.5.so.0 (0x03ff8450) liblber-2.5.so.0 => /lib/s390x-linux-gnu/liblber-2.5.so.0 (0x03ff8448) libzstd.so.1 => /lib/s390x-linux-gnu/libzstd.so.1 (0x03ff8438) libbrotlidec.so.1 => /lib/s390x-linux-gnu/libbrotlidec.so.1 (0x03ff8430) libicuuc.so.70 => /lib/s390x-linux-gnu/libicuuc.so.70 (0x03ff8408) libcrypto.so.1.1 => not found libunistring.so.2 => /lib/s390x-linux-gnu/libunistring.so.2 (0x03ff83e8) libhogweed.so.6 => /lib/s390x-linux-gnu/libhogweed.so.6 (0x03ff83e0) libgmp.so.10 => /lib/s390x-linux-gnu/libgmp.so.10 (0x03ff83d0) libcrypto.so.3 => /lib/s390x-linux-gnu/libcrypto.so.3 (0x03ff8390) libp11-kit.so.0 => /lib/s390x-linux-gnu/libp11-kit.so.0 (0x03ff8378) libtasn1.so.6 => /lib/s390x-linux-gnu/libtasn1.so.6 (0x03ff8370) libkrb5.so.3 => /lib/s390x-linux-gnu/libkrb5.so.3 (0x03ff8360) libk5crypto.so.3 => /lib/s390x-linux-gnu/libk5crypto.so.3 (0x03ff8358) libcom_err.so.2 => /lib/s390x-linux-gnu/libcom_err.so.2 (0x03ff8350) libkrb5support.so.0 => /lib/s390x-linux-gnu/libkrb5support.so.0 (0x03ff8348) libsasl2.so.2 => /lib/s390x-linux-gnu/libsasl2.so.2 (0x03ff8340) libbrotlicommon.so.1 => /lib/s390x-linux-gnu/libbrotlicommon.so.1 (0x03ff8338) libicudata.so.70 => /lib/s390x-linux-gnu/libicudata.so.70 (0x03ff8170) libstdc++.so.6 => /lib/s390x-linux-gnu/libstdc++.so.6 (0x03ff8148) libgcc_s.so.1 => /lib/s390x-linux-gnu/libgcc_s.so.1 (0x03ff8140) libkeyutils.so.1 => /lib/s390x-linux-gnu/libkeyutils.so.1 (0x03ff8138) libresolv.so.2 => /lib/s390x-linux-gnu/libresolv.so.2 (0x03ff8130)
[Kernel-packages] [Bug 2008522] Re: Intel_powerclamp use powercap/idle-inject and allow cpumask to inject idle
Commit acbc661032b8,bbfc3349c4e7,c7cd6f04c0df,98e596fc85fe,ebf519710218,966d0ab67350,621084965459,8526eb7fc75a,8e4736358837 were all part of v6.3-rc1, thus shipped with 23.10 GA kernel. While the last mentioned commit (c4e927da893b68b99e94a4a2) is nowhere to be found, can you double check the SHA? -- 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/2008522 Title: Intel_powerclamp use powercap/idle-inject and allow cpumask to inject idle Status in intel: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: [Feature Description] Use the powercap/idle-inject framework for intel Power clamp driver. Allow CPU mask and max idle percent as module parameter. This way way driver can be used for LPM mode in MTL. Target Kernel: 6.3 Target Release: 23.10 [HW/SW Information] Meteor Lake [Business Justification] Platform enabling Upstream: Merged 6.3 Commit ID: acbc661032b8,bbfc3349c4e7,c7cd6f04c0df,98e596fc85fe,ebf519710218,966d0ab67350,621084965459,8526eb7fc75a,8e4736358837,c4e927da893b68b99e94a4a2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2008522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049603] [NEW] nvidia-dkms-535 FTBS on noble with the latest 6.7 kernel on arm64
Public bug reported:
[Impact]
It looks like nvidia-dkms-535 is using a symbol that became GPL-only in
the latest 6.7 kernel, causing the following build error:
# MODPOST <>/build/nvidia/535.146.02/build/Module.symvers
scripts/mod/modpost -M -m -a -o
<>/build/nvidia/535.146.02/build/Module.symvers -T
<>/build/nvidia/535.146.02/build/modules.order -i Module.symvers -e
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'screen_info'
This change was introduced by: b8466fe82b79 ("efi: move screen_info into
efi init code")
This happens only on arm64, where the symbol is defined.
[Fix]
Avoid using screen_info in the nvidia-dkms-535 driver.
[Regression potential]
We may disable certain features in the 535 driver, or even have an
unusable driver, unless a proper workaround/solution is provided.
** Affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Affects: nvidia-graphics-drivers-535 (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-535 (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2049603
Title:
nvidia-dkms-535 FTBS on noble with the latest 6.7 kernel on arm64
Status in nvidia-graphics-drivers-535 package in Ubuntu:
New
Status in nvidia-graphics-drivers-535 source package in Noble:
New
Bug description:
[Impact]
It looks like nvidia-dkms-535 is using a symbol that became GPL-only
in the latest 6.7 kernel, causing the following build error:
# MODPOST <>/build/nvidia/535.146.02/build/Module.symvers
scripts/mod/modpost -M -m -a -o
<>/build/nvidia/535.146.02/build/Module.symvers -T
<>/build/nvidia/535.146.02/build/modules.order -i Module.symvers -e
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'screen_info'
This change was introduced by: b8466fe82b79 ("efi: move screen_info
into efi init code")
This happens only on arm64, where the symbol is defined.
[Fix]
Avoid using screen_info in the nvidia-dkms-535 driver.
[Regression potential]
We may disable certain features in the 535 driver, or even have an
unusable driver, unless a proper workaround/solution is provided.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2049603/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64
The same problem was reported on Arch and they could confirm it started due to changes in the kernel related to ASLR. https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/20 Relevant changed from kernel 6.5 to 6.6 on Ubuntu: -CONFIG_ARCH_MMAP_RND_BITS=28 +CONFIG_ARCH_MMAP_RND_BITS=32 CONFIG_HAVE_ARCH_MMAP_RND_COMPAT_BITS=y -CONFIG_ARCH_MMAP_RND_COMPAT_BITS=8 +CONFIG_ARCH_MMAP_RND_COMPAT_BITS=16 Setting vm.mmap_rnd_bits to 28 bits seems to be enough to workaround the problem. ** Bug watch added: gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues #20 https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/20 -- 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/2048768 Title: Autopkgtest failures on amd64 Status in linux package in Ubuntu: New Status in llvm-toolchain-14 package in Ubuntu: New Status in linux source package in Noble: New Status in llvm-toolchain-14 source package in Noble: New Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5e9c3445acb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8634==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5f19be5f6d12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5f19be632cb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x77c7d3c280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp Segmentation fault (core dumped) After some investigation I found that it will not fail with ASLR disabled: sudo sysctl kernel.randomize_va_space=0 while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done If you enable ASLR it will start to crash: $ sudo sysctl kernel.randomize_va_space=2 $ while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done Segmentation fault (core dumped) crashed Segmentation fault (core dumped) crashed Segmentation fault (core dumped) crashed Segmentation fault (core dumped) crashed Segmentation fault (core
