[Kernel-packages] [Bug 2072973] Re: Primary screen goes crazy since Ubuntu 24.04 update (6.8 fails but 6.5 works)
Experiencing the same issue on a new XPS 9640. Downgrading to a known kernel as pointed by others (linux- image-6.8.0-36-generic) has problems with other areas like WiFi and soundcard. The solution was to upgrade the kernel to mainline 6.9.1 onwards up to 6.9.12. (6.9 still gives mouse cursor glitches) -- 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/2072973 Title: Primary screen goes crazy since Ubuntu 24.04 update (6.8 fails but 6.5 works) Status in linux package in Ubuntu: Confirmed Bug description: Hi, I often run into a severe display issue since my update to the latest LTS release. In fact, my primary screen glitches, like it alternates every other frame between a stretched and a still image. Moving my cursor back to it stops the bug. It only happend when focused on one of my 2 secondary screens, particularily when moving the cursor above a dropdown menu in my browser, IDE etc (weird enough!) I've attached a short video to help you comprehend what is happening. The day I thought about booting up using an older kernel (...6.5 I think? I should be using now 6.8 iirc) I did not ran into this issue. ❯ lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04 LTS Release: 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 12 15:08:49 2024 DistUpgraded: 2024-06-04 14:32:37,945 DEBUG icon theme changed, re-reading DistroCodename: noble DistroVariant: ubuntu DkmsStatus: ovpn-dco/0.0+git20231103, 6.8.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0a5c] InstallationDate: Installed on 2023-02-17 (511 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 13 9305 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-38-generic root=/dev/mapper/vgubuntu-root ro quiet splash loglevel=3 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-06-04 (38 days ago) dmi.bios.date: 04/15/2024 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.0 dmi.board.name: 0PPYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.0:bd04/15/2024:br1.22:svnDellInc.:pnXPS139305:pvr:rvnDellInc.:rn0PPYW4:rvrA03:cvnDellInc.:ct10:cvr:sku0A5C: dmi.product.family: XPS dmi.product.name: XPS 13 9305 dmi.product.sku: 0A5C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
I confirm that kernel 5.15.0-119 from the proposed2 PPA fixes this issue on Jammy. Thank you, Matthew, for your kind explanation, and to all the developers who worked on this! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-hwe-6.8 source package in Jammy: Fix Committed Status in linux-signed-hwe-5.15 source package in Jammy: Invalid Status in virtualbox source package in Jammy: Confirmed Bug description: BugLink: https://bugs.launchpad.net/bugs/2073267 SRU Justification: [Impact] Commit "randomize_kstack: Improve entropy diffusion" changed the kernel stack for entropy to 1KiB, limiting the thread kernel stack to 15Kib. This impacts virtualbox 6.1.50 on jammy, that is no longer maintained upstream. The issue does not persist on version 7.0.20 due to a code refactoring that probably resulted in less stack usage. Fixing it on the jammy virtualbox package side is not straightfoward because the fix is not easy to backport to 6.x and upgrading the jammy package to 7.x breaks current users machines that run Windows, but not only. Users need to uninstall the Guest additions drivers, migrate the virtualbox package to 7.x, boot each VMs and install the Guest additions drivers in each VM. This impacts: 1. jammy:linux 2. jammy:linux-hwe-6.8 3. focal:linux-hwe-5.15 [Fix] Revert commit "randomize_kstack: Improve entropy diffusion" [Test Plan] Without this fix, a VM would crash, showing with "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". After the kernel upgrade, all VMs should run with no problem. [Where problems could occur] This may have an impact on security. The commit is a fix to improve the stack entropy. Original description: It worked yesterday, but today I get a Guru Meditation trying to start some of my virtual machines. This shows up in VBox.log as "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". I suspect this may have started due to a Linux kernel upgrade I installed this morning. A fresh VM with no disk shows the issue. Sometimes turning off the I/O APIC makes the issue go away, sometimes not. Turning off nested paging sometimes lets VirtualBox make a little bit of progress w.r.t. booting VMs, but that usually still crashes before the VM finishes starting. This may be related to this bug reported on the VirtualBox forums: https://forums.virtualbox.org/viewtopic.php?t=111889&sid=5cd33c0872a03b689e7e9f84d850f538 https://forums.virtualbox.org/viewtopic.php?t=111918 Ubuntu is 22.04.4 LTS, kernel is 5.15.0-116-generic, VirtualBox is 6.1.50-dfsg-1~ubuntu1.22.04.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018303] Re: move sev-guest module from linux-modules-extra to linux-modules
This isn't fixed in the jammy 6.5.0-1024-aws kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2018303 Title: move sev-guest module from linux-modules-extra to linux-modules Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Kinetic: Won't Fix Status in linux-aws source package in Lunar: Fix Released Status in linux-aws source package in Mantic: Fix Released Bug description: AWS did recently announce AMD SEV-SNP support (see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sev-snp.html. To have that working in the ubuntu AWS images, the module needs to be available (linux-modules-extra is not installed by default). So please move the module to linux-modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2018303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913350]
I'm just adding here that this is still a problem with 6.1.0 and my Intel 7260 wireless device. Adding my log in case it helps somehow. - [ 75.351025] [ cut here ] [ 75.351028] Timeout waiting for hardware access (CSR_GP_CNTRL 0x) [ 75.351056] WARNING: CPU: 7 PID: 1205 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2129 __iwl_trans_pcie_grab_nic_access+0x1ef/0x220 [iwlwifi] [ 75.351079] Modules linked in: xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc ccm overlay qrtr cmac algif_hash algif_skcipher af_alg bnep binfmt_misc intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp nls_ascii nls_cp437 vfat kvm_intel fat btusb btrtl btbcm iwlmvm btintel btmtk kvm bluetooth mac80211 irqbypass snd_hda_codec_realtek ghash_clmulni_intel snd_hda_codec_generic snd_hda_codec_hdmi libarc4 sha256_ssse3 sha1_ssse3 snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec jitterentropy_rng pn544_mei mei_phy sha512_ssse3 pn544 aesni_intel uvcvideo hci sha512_generic snd_hda_core videobuf2_vmalloc nfc videobuf2_memops iwlwifi videobuf2_v4l2 snd_hwdep ctr crypto_simd mei_hdcp snd_pcm drbg videobuf2_common cryptd dell_laptop iTCO_wdt ansi_cprng ledtrig_audio dell_wmi intel_pmc_bxt rapl videodev [ 75.351122] ecdh_generic intel_cstate snd_timer dell_smm_hwmon mei_me ecc iTCO_vendor_support sparse_keymap cfg80211 intel_uncore dell_smbios watchdog at24 crc16 hid_multitouch mc joydev snd sg mei dcdbas soundcore acpi_als serio_raw pcspkr intel_pch_thermal dell_wmi_descriptor industrialio_triggered_buffer wmi_bmof kfifo_buf industrialio evdev ac int3403_thermal int3400_thermal dell_rbtn acpi_thermal_rel rfkill dell_smo8800 int3402_thermal int340x_thermal_zone parport_pc ppdev lp parport dm_mod fuse loop efi_pstore configfs efivarfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq zstd_compress libcrc32c crc32c_generic sd_mod t10_pi hid_generic crc64_rocksoft crc64 crc_t10dif usbhid crct10dif_generic hid i915 nouveau ahci libahci drm_buddy i2c_algo_bit drm_display_helper libata cec rc_core drm_ttm_helper ttm rtsx_pci_sdmmc xhci_pci ehci_pci mmc_core xhci_hcd scsi_mod drm_kms_helper crct10dif_pclmul ehci_hcd i2c_i801 crct10dif_common mxm_wmi crc32_pclmul drm psmouse [ 75.351173] usbcore crc32c_intel rtsx_pci i2c_smbus scsi_common lpc_ich usb_common fan video battery wmi button [ 75.351180] CPU: 7 PID: 1205 Comm: i3status Not tainted 6.1.0-23-amd64 #1 Debian 6.1.99-1 [ 75.351183] Hardware name: Dell Inc. Dell Precision M3800/Dell Precision M3800, BIOS A14 07/02/2020 [ 75.351184] RIP: 0010:__iwl_trans_pcie_grab_nic_access+0x1ef/0x220 [iwlwifi] [ 75.351200] Code: 48 89 df e8 33 db fe ff 4c 89 f7 e8 1b b4 b2 eb e9 e3 fe ff ff 89 c6 48 c7 c7 58 db 33 c1 c6 05 7d 67 03 00 01 e8 21 91 18 eb <0f> 0b e9 01 ff ff ff 48 8b 7b 40 48 c7 c2 c0 db 33 c1 31 f6 e8 e8 [ 75.351202] RSP: 0018:ae044149f578 EFLAGS: 00010086 [ 75.351204] RAX: RBX: 896b08198028 RCX: 0027 [ 75.351205] RDX: 896e2fbe03a8 RSI: 0001 RDI: 896e2fbe03a0 [ 75.351206] RBP: R08: R09: ae044149f3f0 [ 75.351207] R10: 0003 R11: aded4448 R12: 0001 [ 75.351208] R13: R14: 896b0819a934 R15: 0011 [ 75.351210] FS: 7f247faa17c0() GS:896e2fbc() knlGS: [ 75.351211] CS: 0010 DS: ES: CR0: 80050033 [ 75.351213] CR2: 7f0913fda810 CR3: 00010400c001 CR4: 001706e0 [ 75.351214] Call Trace: [ 75.351216] [ 75.351218] ? __warn+0x7d/0xc0 [ 75.351221] ? __iwl_trans_pcie_grab_nic_access+0x1ef/0x220 [iwlwifi] [ 75.351236] ? report_bug+0xe2/0x150 [ 75.351239] ? handle_bug+0x41/0x70 [ 75.351243] ? exc_invalid_op+0x13/0x60 [ 75.351244] ? asm_exc_invalid_op+0x16/0x20 [ 75.351248] ? __iwl_trans_pcie_grab_nic_access+0x1ef/0x220 [iwlwifi] [ 75.351261] ? __iwl_trans_pcie_grab_nic_access+0x1ef/0x220 [iwlwifi] [ 75.351274] iwl_pcie_enqueue_hcmd+0x53b/0x8e0 [iwlwifi] [ 75.351286] iwl_trans_txq_send_hcmd+0xee/0x380 [iwlwifi] [ 75.351301] ? __nla_validate_parse+0x61/0xc00 [ 75.351304] iwl_trans_send_cmd+0x94/0xf0 [iwlwifi] [ 75.351317] iwl_mvm_request_statistics+0x91/0x1f0 [iwlmvm] [ 75.351331] iwl_mvm_mac_sta_statistics+0x1d9/0x350 [iwlmvm] [ 75.351341] sta_set_sinfo+0xbf/0xba0 [mac80211] [ 75.351382] ieee80211_dump_station+0x6b/0x90 [mac80211] [ 75.351415] nl80211_dump_station+0x13e/0x280 [cfg80211] [ 75.351459] ? __alloc_pages+0x1dc/0x330 [ 75.351464] netlink_dump+0x123/0x310 [ 75.351467] __netlink_dump_start+0x1bf/0x2f0 [ 75.351470] genl_family_rcv_msg_dumpit+0xc5/0x150 [ 75.351472] ? genl_family_rc
[Kernel-packages] [Bug 2073676] Re: after update of kernel HDMI audio is not working
I put them at the same location https://people.canonical.com/~mschiu77/lp2073676/ for acp test. If it's not working, we will have to do bisect. It might need 10~13 test kernels to find out. -- 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/2073676 Title: after update of kernel HDMI audio is not working Status in linux package in Ubuntu: New Bug description: after update of kernel the Audio output via dock - HDMI is no longer working. the display is showing that the audio i receving but there is no audio. If I switch to normal speakers on the laptop the audio is working. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-38-generic 6.8.0-38.38 ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 20 18:45:44 2024 InstallationDate: Installed on 2024-03-11 (131 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: LENOVO 20XK007DMX ProcEnviron: LANG=da_DK.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic root=UUID=735a8489-6e61-48ac-a281-46d43115ef53 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-38-generic N/A linux-backports-modules-6.8.0-38-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-05-22 (59 days ago) dmi.bios.date: 10/30/2023 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET55W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XK007DMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR1MET55W(1.25):bd10/30/2023:br1.25:efr1.25:svnLENOVO:pn20XK007DMX:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XK007DMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XK_BU_Think_FM_ThinkPadT14Gen2a: dmi.product.family: ThinkPad T14 Gen 2a dmi.product.name: 20XK007DMX dmi.product.sku: LENOVO_MT_20XK_BU_Think_FM_ThinkPad T14 Gen 2a dmi.product.version: ThinkPad T14 Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064539] Re: Revert back frame pointers for ppc64el (remove -fno-omit-frame-pointer)
Many thanks doko, the debdiff looks reasonable and good. I did a test build (based on v1.22.6ubuntu6.1 https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+sourcepub/16274696/+listing-archive-extra) and wasn't able to find an indication of FBs (in the debug symbols) anymore (using readelf -wi grep-ping for DW_AT_produce). Same for LP#2064538. -- 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/2064539 Title: Revert back frame pointers for ppc64el (remove -fno-omit-frame- pointer) Status in The Ubuntu-power-systems project: New Status in dpkg package in Ubuntu: Fix Released Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Status in dpkg source package in Noble: New Status in glibc source package in Noble: New Status in linux source package in Noble: New Status in dpkg source package in Oracular: Fix Released Status in glibc source package in Oracular: New Status in linux source package in Oracular: New Bug description: Power's Linux ABIs all require an explicit call chain be stored on the call stack frames which are all accessible via the stack pointer. Therefore, having a (soft/simulated) frame pointer does not improve backtraces at all on Power. However, forcing a frame pointer via the -fno-omit-frame-pointer option negatively affects performance for multiple reasons: extra prologue/epilogue overhead and fewer shrink-wrapping opportunities. Given -fno-omit-frame-pointer does not provide any improvements (backtraces or otherwise) and only reduces performance, -fno-omit-frame-pointers should not be used on Power. SRU: these changes were implemented during the opening of the oracular series. The very same changes are backported to 24.04 LTS. These only affect the ppc64el and s390x architectures, for other architectures it's a no-change upload. We didn't see any fallout for these changes during the development on the oracular series, and therefore don't expect any fallout or regressions in 24.04 LTS either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064539] Please test proposed package
Hello Frank, or anyone else affected, Accepted dpkg into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dpkg/1.22.6ubuntu6.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2064539 Title: Revert back frame pointers for ppc64el (remove -fno-omit-frame- pointer) Status in The Ubuntu-power-systems project: New Status in dpkg package in Ubuntu: Fix Released Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Status in dpkg source package in Noble: Fix Committed Status in glibc source package in Noble: New Status in linux source package in Noble: New Status in dpkg source package in Oracular: Fix Released Status in glibc source package in Oracular: New Status in linux source package in Oracular: New Bug description: Power's Linux ABIs all require an explicit call chain be stored on the call stack frames which are all accessible via the stack pointer. Therefore, having a (soft/simulated) frame pointer does not improve backtraces at all on Power. However, forcing a frame pointer via the -fno-omit-frame-pointer option negatively affects performance for multiple reasons: extra prologue/epilogue overhead and fewer shrink-wrapping opportunities. Given -fno-omit-frame-pointer does not provide any improvements (backtraces or otherwise) and only reduces performance, -fno-omit-frame-pointers should not be used on Power. SRU: these changes were implemented during the opening of the oracular series. The very same changes are backported to 24.04 LTS. These only affect the ppc64el and s390x architectures, for other architectures it's a no-change upload. We didn't see any fallout for these changes during the development on the oracular series, and therefore don't expect any fallout or regressions in 24.04 LTS either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064539] Re: Revert back frame pointers for ppc64el (remove -fno-omit-frame-pointer)
Frank, can you help me in writing up some test cases for both of these bugs? SO that we have formally a test case someone can follow or at least understand. Thanks! ** Changed in: dpkg (Ubuntu Noble) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-noble -- 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/2064539 Title: Revert back frame pointers for ppc64el (remove -fno-omit-frame- pointer) Status in The Ubuntu-power-systems project: New Status in dpkg package in Ubuntu: Fix Released Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Status in dpkg source package in Noble: Fix Committed Status in glibc source package in Noble: New Status in linux source package in Noble: New Status in dpkg source package in Oracular: Fix Released Status in glibc source package in Oracular: New Status in linux source package in Oracular: New Bug description: Power's Linux ABIs all require an explicit call chain be stored on the call stack frames which are all accessible via the stack pointer. Therefore, having a (soft/simulated) frame pointer does not improve backtraces at all on Power. However, forcing a frame pointer via the -fno-omit-frame-pointer option negatively affects performance for multiple reasons: extra prologue/epilogue overhead and fewer shrink-wrapping opportunities. Given -fno-omit-frame-pointer does not provide any improvements (backtraces or otherwise) and only reduces performance, -fno-omit-frame-pointers should not be used on Power. SRU: these changes were implemented during the opening of the oracular series. The very same changes are backported to 24.04 LTS. These only affect the ppc64el and s390x architectures, for other architectures it's a no-change upload. We didn't see any fallout for these changes during the development on the oracular series, and therefore don't expect any fallout or regressions in 24.04 LTS either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064538] Re: Revert back frame pointers for s390x (remove -fno-omit-frame-pointer but use -mbackchain)
Frank, can you help me in writing up some test cases for both of these bugs? SO that we have formally a test case someone can follow or at least understand. Thanks! ** Changed in: dpkg (Ubuntu Noble) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-noble -- 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/2064538 Title: Revert back frame pointers for s390x (remove -fno-omit-frame-pointer but use -mbackchain) Status in Ubuntu on IBM z Systems: New Status in dpkg package in Ubuntu: Fix Released Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Status in dpkg source package in Noble: Fix Committed Status in glibc source package in Noble: New Status in linux source package in Noble: New Status in dpkg source package in Oracular: Fix Released Status in glibc source package in Oracular: New Status in linux source package in Oracular: New Bug description: The preferred way of doing stack unwinding on Linux on Z is via dwarf call frame information. In absence of a dwarf unwinder (as in the Linux kernel) a stack chain can be maintained at runtime in addition to the dwarf unwinding information. This allows for simple backtrace implementations, but imposes a small runtime overhead. For this to work, all code that might be part of backtrace must be built with the -mbackchain GCC option. The -fno-omit-framepointer switch is neither necessary nor helpful in this context. Having a (soft/simulated) frame pointer does not improve backtraces at all on IBM Z. However, forcing a frame pointer via the -fno-omit-frame-pointer option negatively affects performance for multiple reasons: extra prologue/epilogue overhead and fewer shrink-wrapping opportunities. Given -fno-omit-frame-pointer does not provide any improvements (backtraces or otherwise) and only reduces performance, -fno-omit-frame-pointers should not be used on IBM Z. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2064538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064538] Please test proposed package
Hello Frank, or anyone else affected, Accepted dpkg into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dpkg/1.22.6ubuntu6.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2064538 Title: Revert back frame pointers for s390x (remove -fno-omit-frame-pointer but use -mbackchain) Status in Ubuntu on IBM z Systems: New Status in dpkg package in Ubuntu: Fix Released Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Status in dpkg source package in Noble: Fix Committed Status in glibc source package in Noble: New Status in linux source package in Noble: New Status in dpkg source package in Oracular: Fix Released Status in glibc source package in Oracular: New Status in linux source package in Oracular: New Bug description: The preferred way of doing stack unwinding on Linux on Z is via dwarf call frame information. In absence of a dwarf unwinder (as in the Linux kernel) a stack chain can be maintained at runtime in addition to the dwarf unwinding information. This allows for simple backtrace implementations, but imposes a small runtime overhead. For this to work, all code that might be part of backtrace must be built with the -mbackchain GCC option. The -fno-omit-framepointer switch is neither necessary nor helpful in this context. Having a (soft/simulated) frame pointer does not improve backtraces at all on IBM Z. However, forcing a frame pointer via the -fno-omit-frame-pointer option negatively affects performance for multiple reasons: extra prologue/epilogue overhead and fewer shrink-wrapping opportunities. Given -fno-omit-frame-pointer does not provide any improvements (backtraces or otherwise) and only reduces performance, -fno-omit-frame-pointers should not be used on IBM Z. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2064538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2070028] Re: Jammy update: v5.15.159 upstream stable release
This bug was fixed in the package linux - 5.15.0-118.128
---
linux (5.15.0-118.128) jammy; urgency=medium
* jammy/linux: 5.15.0-118.128 -proposed tracker (LP: #2072255)
* Jammy update: v5.15.160 upstream stable release (LP: #2070292)
- drm/amd/display: Fix division by zero in setup_dsc_config
- pinctrl: core: handle radix_tree_insert() errors in
pinctrl_register_one_pin()
- nfsd: don't allow nfsd threads to be signalled.
- KEYS: trusted: Fix memory leak in tpm2_key_encode()
- Revert "selftests: mm: fix map_hugetlb failure on 64K page size systems"
- net: bcmgenet: synchronize EXT_RGMII_OOB_CTRL access
- net: bcmgenet: synchronize UMAC_CMD access
- netlink: annotate lockless accesses to nlk->max_recvmsg_len
- netlink: annotate data-races around sk->sk_err
- KVM: x86: Clear "has_error_code", not "error_code", for RM exception
injection
- drm/amdgpu: Fix possible NULL dereference in
amdgpu_ras_query_error_status_helper()
- binder: fix max_thread type inconsistency
- usb: typec: ucsi: displayport: Fix potential deadlock
- serial: kgdboc: Fix NMI-safety problems from keyboard reset code
- remoteproc: mediatek: Make sure IPI buffer fits in L2TCM
- KEYS: trusted: Do not use WARN when encode fails
- admin-guide/hw-vuln/core-scheduling: fix return type of PR_SCHED_CORE_GET
- docs: kernel_include.py: Cope with docutils 0.21
- Linux 5.15.160
* Jammy update: v5.15.159 upstream stable release (LP: #2070028)
- dmaengine: pl330: issue_pending waits until WFP state
- dmaengine: Revert "dmaengine: pl330: issue_pending waits until WFP state"
- wifi: nl80211: don't free NULL coalescing rule
- ksmbd: fix slab-out-of-bounds in smb2_allocate_rsp_buf
- ksmbd: validate request buffer size in smb2_allocate_rsp_buf()
- ksmbd: clear RENAME_NOREPLACE before calling vfs_rename
- eeprom: at24: Use dev_err_probe for nvmem register failure
- eeprom: at24: Probe for DDR3 thermal sensor in the SPD case
- eeprom: at24: fix memory corruption race condition
- pinctrl: pinctrl-aspeed-g6: Fix register offset for pinconf of GPIOR-T
- pinctrl/meson: fix typo in PDM's pin name
- pinctrl: core: delete incorrect free in pinctrl_enable()
- pinctrl: mediatek: paris: Rework mtk_pinconf_{get,set} switch/case logic
- pinctrl: mediatek: paris: Fix PIN_CONFIG_INPUT_SCHMITT_ENABLE readback
- pinctrl: mediatek: paris: Rework support for
PIN_CONFIG_{INPUT,OUTPUT}_ENABLE
- sunrpc: add a struct rpc_stats arg to rpc_create_args
- nfs: expose /proc/net/sunrpc/nfs in net namespaces
- nfs: make the rpc_stat per net namespace
- nfs: Handle error of rpc_proc_register() in nfs_net_init().
- power: rt9455: hide unused rt9455_boost_voltage_values
- power: supply: mt6360_charger: Fix of_match for usb-otg-vbus regulator
- pinctrl: devicetree: fix refcount leak in pinctrl_dt_to_map()
- regulator: mt6360: De-capitalize devicetree regulator subnodes
- bpf, kconfig: Fix DEBUG_INFO_BTF_MODULES Kconfig definition
- bpf, skmsg: Fix NULL pointer dereference in sk_psock_skb_ingress_enqueue
- bpf: Fix a verifier verbose message
- spi: hisi-kunpeng: Delete the dump interface of data registers in debugfs
- s390/mm: Fix storage key clearing for guest huge pages
- s390/mm: Fix clearing storage keys for huge pages
- xdp: Move conversion to xdp_frame out of map functions
- xdp: Add xdp_do_redirect_frame() for pre-computed xdp_frames
- xdp: use flags field to disambiguate broadcast redirect
- bna: ensure the copied buf is NUL terminated
- octeontx2-af: avoid off-by-one read from userspace
- nsh: Restore skb->{protocol,data,mac_header} for outer header in
nsh_gso_segment().
- net l2tp: drop flow hash on forward
- s390/vdso: Add CFI for RA register to asm macro vdso_func
- net: qede: sanitize 'rc' in qede_add_tc_flower_fltr()
- net: qede: use return from qede_parse_flow_attr() for flower
- net: qede: use return from qede_parse_flow_attr() for flow_spec
- net: qede: use return from qede_parse_actions()
- ASoC: meson: axg-fifo: use FIELD helpers
- ASoC: meson: axg-fifo: use threaded irq to check periods
- ASoC: meson: axg-card: make links nonatomic
- ASoC: meson: axg-tdm-interface: manage formatters in trigger
- ASoC: meson: cards: select SND_DYNAMIC_MINORS
- ALSA: hda: intel-sdw-acpi: fix usage of device_get_named_child_node()
- s390/cio: Ensure the copied buf is NUL terminated
- cxgb4: Properly lock TX queue for the selftest.
- net: dsa: mv88e6xxx: Fix number of databases for 88E6141 / 88E6341
- net: bridge: fix multicast-to-unicast with fraglist GSO
- net: core: reject skb_copy(_expand) for fraglist GSO skbs
- tipc: fix a possible memleak in tipc_buf_append
- s390/qeth: don't keep track of Input Queue count
- s390/qeth: Fix kernel panic after setti
[Kernel-packages] [Bug 2070292] Re: Jammy update: v5.15.160 upstream stable release
This bug was fixed in the package linux - 5.15.0-118.128
---
linux (5.15.0-118.128) jammy; urgency=medium
* jammy/linux: 5.15.0-118.128 -proposed tracker (LP: #2072255)
* Jammy update: v5.15.160 upstream stable release (LP: #2070292)
- drm/amd/display: Fix division by zero in setup_dsc_config
- pinctrl: core: handle radix_tree_insert() errors in
pinctrl_register_one_pin()
- nfsd: don't allow nfsd threads to be signalled.
- KEYS: trusted: Fix memory leak in tpm2_key_encode()
- Revert "selftests: mm: fix map_hugetlb failure on 64K page size systems"
- net: bcmgenet: synchronize EXT_RGMII_OOB_CTRL access
- net: bcmgenet: synchronize UMAC_CMD access
- netlink: annotate lockless accesses to nlk->max_recvmsg_len
- netlink: annotate data-races around sk->sk_err
- KVM: x86: Clear "has_error_code", not "error_code", for RM exception
injection
- drm/amdgpu: Fix possible NULL dereference in
amdgpu_ras_query_error_status_helper()
- binder: fix max_thread type inconsistency
- usb: typec: ucsi: displayport: Fix potential deadlock
- serial: kgdboc: Fix NMI-safety problems from keyboard reset code
- remoteproc: mediatek: Make sure IPI buffer fits in L2TCM
- KEYS: trusted: Do not use WARN when encode fails
- admin-guide/hw-vuln/core-scheduling: fix return type of PR_SCHED_CORE_GET
- docs: kernel_include.py: Cope with docutils 0.21
- Linux 5.15.160
* Jammy update: v5.15.159 upstream stable release (LP: #2070028)
- dmaengine: pl330: issue_pending waits until WFP state
- dmaengine: Revert "dmaengine: pl330: issue_pending waits until WFP state"
- wifi: nl80211: don't free NULL coalescing rule
- ksmbd: fix slab-out-of-bounds in smb2_allocate_rsp_buf
- ksmbd: validate request buffer size in smb2_allocate_rsp_buf()
- ksmbd: clear RENAME_NOREPLACE before calling vfs_rename
- eeprom: at24: Use dev_err_probe for nvmem register failure
- eeprom: at24: Probe for DDR3 thermal sensor in the SPD case
- eeprom: at24: fix memory corruption race condition
- pinctrl: pinctrl-aspeed-g6: Fix register offset for pinconf of GPIOR-T
- pinctrl/meson: fix typo in PDM's pin name
- pinctrl: core: delete incorrect free in pinctrl_enable()
- pinctrl: mediatek: paris: Rework mtk_pinconf_{get,set} switch/case logic
- pinctrl: mediatek: paris: Fix PIN_CONFIG_INPUT_SCHMITT_ENABLE readback
- pinctrl: mediatek: paris: Rework support for
PIN_CONFIG_{INPUT,OUTPUT}_ENABLE
- sunrpc: add a struct rpc_stats arg to rpc_create_args
- nfs: expose /proc/net/sunrpc/nfs in net namespaces
- nfs: make the rpc_stat per net namespace
- nfs: Handle error of rpc_proc_register() in nfs_net_init().
- power: rt9455: hide unused rt9455_boost_voltage_values
- power: supply: mt6360_charger: Fix of_match for usb-otg-vbus regulator
- pinctrl: devicetree: fix refcount leak in pinctrl_dt_to_map()
- regulator: mt6360: De-capitalize devicetree regulator subnodes
- bpf, kconfig: Fix DEBUG_INFO_BTF_MODULES Kconfig definition
- bpf, skmsg: Fix NULL pointer dereference in sk_psock_skb_ingress_enqueue
- bpf: Fix a verifier verbose message
- spi: hisi-kunpeng: Delete the dump interface of data registers in debugfs
- s390/mm: Fix storage key clearing for guest huge pages
- s390/mm: Fix clearing storage keys for huge pages
- xdp: Move conversion to xdp_frame out of map functions
- xdp: Add xdp_do_redirect_frame() for pre-computed xdp_frames
- xdp: use flags field to disambiguate broadcast redirect
- bna: ensure the copied buf is NUL terminated
- octeontx2-af: avoid off-by-one read from userspace
- nsh: Restore skb->{protocol,data,mac_header} for outer header in
nsh_gso_segment().
- net l2tp: drop flow hash on forward
- s390/vdso: Add CFI for RA register to asm macro vdso_func
- net: qede: sanitize 'rc' in qede_add_tc_flower_fltr()
- net: qede: use return from qede_parse_flow_attr() for flower
- net: qede: use return from qede_parse_flow_attr() for flow_spec
- net: qede: use return from qede_parse_actions()
- ASoC: meson: axg-fifo: use FIELD helpers
- ASoC: meson: axg-fifo: use threaded irq to check periods
- ASoC: meson: axg-card: make links nonatomic
- ASoC: meson: axg-tdm-interface: manage formatters in trigger
- ASoC: meson: cards: select SND_DYNAMIC_MINORS
- ALSA: hda: intel-sdw-acpi: fix usage of device_get_named_child_node()
- s390/cio: Ensure the copied buf is NUL terminated
- cxgb4: Properly lock TX queue for the selftest.
- net: dsa: mv88e6xxx: Fix number of databases for 88E6141 / 88E6341
- net: bridge: fix multicast-to-unicast with fraglist GSO
- net: core: reject skb_copy(_expand) for fraglist GSO skbs
- tipc: fix a possible memleak in tipc_buf_append
- s390/qeth: don't keep track of Input Queue count
- s390/qeth: Fix kernel panic after setti
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
This bug is awaiting verification that the linux-azure/5.15.0-1070.79 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-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 source package in Focal: Fix Committed Status in linux-signed-hwe-6.5 source package in Jammy: Fix Committed Status in linux-signed-hwe-6.5 source package in Mantic: Won't Fix Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
This bug is awaiting verification that the linux-ibm/5.15.0-1060.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-ibm' to 'verification-done-jammy- linux-ibm'. If the problem still exists, change the tag 'verification- needed-jammy-linux-ibm' to 'verification-failed-jammy-linux-ibm'. 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-ibm-v2 verification-needed-jammy-linux-ibm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 source package in Focal: Fix Committed Status in linux-signed-hwe-6.5 source package in Jammy: Fix Committed Status in linux-signed-hwe-6.5 source package in Mantic: Won't Fix Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1067.73~20.04.1 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-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-5.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 source package in Focal: Fix Committed Status in linux-signed-hwe-6.5 source package in Jammy: Fix Committed Status in linux-signed-hwe-6.5 source package in Mantic: Won't Fix Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass C
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
This bug is awaiting verification that the linux-oracle/5.15.0-1065.71 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-oracle' to 'verification-done- jammy-linux-oracle'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oracle' to 'verification-failed-jammy- linux-oracle'. 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-oracle-v2 verification-needed-jammy-linux-oracle -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 source package in Focal: Fix Committed Status in linux-signed-hwe-6.5 source package in Jammy: Fix Committed Status in linux-signed-hwe-6.5 source package in Mantic: Won't Fix Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
This bug is awaiting verification that the linux-raspi/5.15.0-1060.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-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. 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-raspi-v2 verification-needed-jammy-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 source package in Focal: Fix Committed Status in linux-signed-hwe-6.5 source package in Jammy: Fix Committed Status in linux-signed-hwe-6.5 source package in Mantic: Won't Fix Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-118.128~20.04.1 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-focal-linux- hwe-5.15' to 'verification-done-focal-linux-hwe-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-hwe-5.15' to 'verification-failed-focal-linux-hwe-5.15'. 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-focal-linux-hwe-5.15-v2 verification-needed-focal-linux-hwe-5.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 source package in Focal: Fix Committed Status in linux-signed-hwe-6.5 source package in Jammy: Fix Committed Status in linux-signed-hwe-6.5 source package in Mantic: Won't Fix Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass C
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1018.18 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-focal-linux-gcp-tcpx' to 'verification-done- focal-linux-gcp-tcpx'. If the problem still exists, change the tag 'verification-needed-focal-linux-gcp-tcpx' to 'verification-failed- focal-linux-gcp-tcpx'. 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-focal-linux-gcp-tcpx-v2 verification-needed-focal-linux-gcp-tcpx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 source package in Focal: Fix Committed Status in linux-signed-hwe-6.5 source package in Jammy: Fix Committed Status in linux-signed-hwe-6.5 source package in Mantic: Won't Fix Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDe
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1050.57~20.04.1 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-focal-linux- gkeop-5.15' to 'verification-done-focal-linux-gkeop-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux- gkeop-5.15' to 'verification-failed-focal-linux-gkeop-5.15'. 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-focal-linux-gkeop-5.15-v2 verification-needed-focal-linux-gkeop-5.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 source package in Focal: Fix Committed Status in linux-signed-hwe-6.5 source package in Jammy: Fix Committed Status in linux-signed-hwe-6.5 source package in Mantic: Won't Fix Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckR
[Kernel-packages] [Bug 2071889] Re: a critical typo in the code managing the ASPM settings for PCI Express devices
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2071621] Re: Noble update: v6.8.12 upstream stable release
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2070158] Re: RFIM and SAGV Linux Support for G10 models
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2070349] Re: Noble update: v6.8.10 upstream stable release
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2070042] Re: noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2069231] Re: [MTL] ACPI: PM: s2idle: Backport Linux ACPI s2idle patches to fix suspend/resume issue
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2067669] Re: Mute/mic LEDs no function on ProBook 440/460 G11
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2070251] Re: failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2067862] Re: Removing legacy virtio-pci devices causes kernel panic
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2069380] Re: FPS of glxgear with fullscreen is too low on MTL platform
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2058331] Re: Update amd_sfh for AMD strix series
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2065128] Re: rtw89_8852ce - Lost WIFI connection after suspend
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2067364] Re: failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2070355] Re: Noble update: v6.8.11 upstream stable release
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2058330] Re: Update amd-pmf for AMD strix series
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2039368] Re: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2069664] Re: Mute/mic LEDs no function on ProBook 445/465 G11
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2071296] Re: Mute/mic LEDs and speaker no function on EliteBook 645/665 G11
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2067516] Re: [aws] Backport CMA pool per numa functionality for 22.04 and 20.04
This bug was fixed in the package linux-aws - 6.8.0-1013.14 --- linux-aws (6.8.0-1013.14) noble; urgency=medium * noble/linux-aws: 6.8.0-1013.14 -proposed tracker (LP: #2072173) * [aws] Backport CMA pool per numa functionality for 22.04 and 20.04 (LP: #2067516) - net: ena: Fix redundant device NUMA node override [ Ubuntu: 6.8.0-40.40 ] * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero
[Kernel-packages] [Bug 2066233] Re: amdgpu hangs on DCN 3.5 at bootup: RIP: 0010:dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu]
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2071471] Re: [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads
This bug was fixed in the package linux - 6.8.0-40.40 --- linux (6.8.0-40.40) noble; urgency=medium * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_uring: fail NOP if non-zero op flags is passed in - Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" - r8169: Fix possible ring buffer corruption on fragmented Tx packets. - ring-buffer: Fix a race between readers and resiz
[Kernel-packages] [Bug 2070179] Re: Focal update: v5.4.277 upstream stable release
This bug was fixed in the package linux - 5.4.0-192.212 --- linux (5.4.0-192.212) focal; urgency=medium * focal/linux: 5.4.0-192.212 -proposed tracker (LP: #2072305) * Focal update: v5.4.278 upstream stable release (LP: #2071668) - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - speakup: Fix sizeof() vs ARRAY_SIZE() bug - ring-buffer: Fix a race between readers and resize checks - net: smc91x: Fix m68k kernel compilation for ColdFire CPU - nilfs2: fix unexpected freezing of nilfs_segctor_sync() - nilfs2: fix potential hang in nilfs_detach_log_writer() - wifi: cfg80211: fix the order of arguments for trace events of the tx_rx_evt class - net: usb: qmi_wwan: add Telit FN920C04 compositions - drm/amd/display: Set color_mgmt_changed to true on unsuspend - ASoC: rt5645: Fix the electric noise due to the CBJ contacts floating - ASoC: dt-bindings: rt5645: add cbj sleeve gpio property - ASoC: da7219-aad: fix usage of device_get_named_child_node() - drm/amdkfd: Flush the process wq before creating a kfd_process - nvme: find numa distance only if controller has valid numa id - openpromfs: finish conversion to the new mount API - crypto: bcm - Fix pointer arithmetic - firmware: raspberrypi: Use correct device for DMA mappings - ecryptfs: Fix buffer size for tag 66 packet - nilfs2: fix out-of-range warning - parisc: add missing export of __cmpxchg_u8() - crypto: ccp - drop platform ifdef checks - s390/cio: fix tracepoint subchannel type field - jffs2: prevent xattr node from overflowing the eraseblock - null_blk: Fix missing mutex_destroy() at module removal - md: fix resync softlockup when bitmap size is less than array size - wifi: ath10k: poll service ready message before failing - x86/boot: Ignore relocations in .notes sections in walk_relocs() too - qed: avoid truncating work queue length - scsi: ufs: qcom: Perform read back after writing reset bit - scsi: ufs: cdns-pltfrm: Perform read back after writing HCLKDIV - scsi: ufs: core: Perform read back after disabling interrupts - scsi: ufs: core: Perform read back after disabling UIC_COMMAND_COMPL - irqchip/alpine-msi: Fix off-by-one in allocation error path - ACPI: disable -Wstringop-truncation - cpufreq: Reorganize checks in cpufreq_offline() - cpufreq: Split cpufreq_offline() - cpufreq: Rearrange locking in cpufreq_remove_dev() - cpufreq: exit() callback is optional - scsi: libsas: Fix the failure of adding phy with zero-address to port - scsi: hpsa: Fix allocation size for Scsi_Host private data - x86/purgatory: Switch to the position-independent small code model - wifi: ath10k: Fix an error code problem in ath10k_dbg_sta_write_peer_debug_trigger() - wifi: ath10k: populate board data for WCN3990 - tcp: minor optimization in tcp_add_backlog() - tcp: fix a signed-integer-overflow bug in tcp_add_backlog() - tcp: avoid premature drops in tcp_add_backlog() - macintosh/via-macii: Fix "BUG: sleeping function called from invalid context" - wifi: carl9170: add a proper sanity check for endpoints - wifi: ar5523: enable proper endpoint verification - sh: kprobes: Merge arch_copy_kprobe() into arch_prepare_kprobe() - Revert "sh: Handle calling csum_partial with misaligned data" - HID: intel-ish-hid: ipc: Add check for pci_alloc_irq_vectors - scsi: bfa: Ensure the copied buf is NUL terminated - scsi: qedf: Ensure the copied buf is NUL terminated - wifi: mwl8k: initialize cmd->addr[] properly - usb: aqc111: stop lying about skb->truesize - net: usb: sr9700: stop lying about skb->truesize - m68k: Fix spinlock race in kernel thread creation - m68k: mac: Fix reboot hang on Mac IIci - net: ethernet: cortina: Locking fixes - af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg - net: usb: smsc95xx: stop lying about skb->truesize - net: openvswitch: fix overwriting ct original tuple for ICMPv6 - ipv6: sr: add missing seg6_local_exit - ipv6: sr: fix incorrect unregister order - ipv6: sr: fix invalid unregister error path - drm/amd/display: Fix potential index out of bounds in color transformation function - mtd: rawnand: hynix: fixed typo - fbdev: shmobile: fix snprintf truncation - drm/mediatek: Add 0 size check to mtk_drm_gem_obj - powerpc/fsl-soc: hide unused const variable - fbdev: sisfb: hide unused variables - media: ngene: Add dvb_ca_en50221_init return value check - media: radio-shark2: Avoid led_names truncations - platform/x86: wmi: Make two functions static - fbdev: sh7760fb: allow modular build - drm/arm/malidp: fix a possible null pointer dereference - ASoC: tracing: Export SND_SOC_DAPM_DIR_OUT to its value - drm/panel: simple: Add missing Innolux G121X1-L03 format, flags, connector
[Kernel-packages] [Bug 2071668] Re: Focal update: v5.4.278 upstream stable release
This bug was fixed in the package linux - 5.4.0-192.212 --- linux (5.4.0-192.212) focal; urgency=medium * focal/linux: 5.4.0-192.212 -proposed tracker (LP: #2072305) * Focal update: v5.4.278 upstream stable release (LP: #2071668) - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - speakup: Fix sizeof() vs ARRAY_SIZE() bug - ring-buffer: Fix a race between readers and resize checks - net: smc91x: Fix m68k kernel compilation for ColdFire CPU - nilfs2: fix unexpected freezing of nilfs_segctor_sync() - nilfs2: fix potential hang in nilfs_detach_log_writer() - wifi: cfg80211: fix the order of arguments for trace events of the tx_rx_evt class - net: usb: qmi_wwan: add Telit FN920C04 compositions - drm/amd/display: Set color_mgmt_changed to true on unsuspend - ASoC: rt5645: Fix the electric noise due to the CBJ contacts floating - ASoC: dt-bindings: rt5645: add cbj sleeve gpio property - ASoC: da7219-aad: fix usage of device_get_named_child_node() - drm/amdkfd: Flush the process wq before creating a kfd_process - nvme: find numa distance only if controller has valid numa id - openpromfs: finish conversion to the new mount API - crypto: bcm - Fix pointer arithmetic - firmware: raspberrypi: Use correct device for DMA mappings - ecryptfs: Fix buffer size for tag 66 packet - nilfs2: fix out-of-range warning - parisc: add missing export of __cmpxchg_u8() - crypto: ccp - drop platform ifdef checks - s390/cio: fix tracepoint subchannel type field - jffs2: prevent xattr node from overflowing the eraseblock - null_blk: Fix missing mutex_destroy() at module removal - md: fix resync softlockup when bitmap size is less than array size - wifi: ath10k: poll service ready message before failing - x86/boot: Ignore relocations in .notes sections in walk_relocs() too - qed: avoid truncating work queue length - scsi: ufs: qcom: Perform read back after writing reset bit - scsi: ufs: cdns-pltfrm: Perform read back after writing HCLKDIV - scsi: ufs: core: Perform read back after disabling interrupts - scsi: ufs: core: Perform read back after disabling UIC_COMMAND_COMPL - irqchip/alpine-msi: Fix off-by-one in allocation error path - ACPI: disable -Wstringop-truncation - cpufreq: Reorganize checks in cpufreq_offline() - cpufreq: Split cpufreq_offline() - cpufreq: Rearrange locking in cpufreq_remove_dev() - cpufreq: exit() callback is optional - scsi: libsas: Fix the failure of adding phy with zero-address to port - scsi: hpsa: Fix allocation size for Scsi_Host private data - x86/purgatory: Switch to the position-independent small code model - wifi: ath10k: Fix an error code problem in ath10k_dbg_sta_write_peer_debug_trigger() - wifi: ath10k: populate board data for WCN3990 - tcp: minor optimization in tcp_add_backlog() - tcp: fix a signed-integer-overflow bug in tcp_add_backlog() - tcp: avoid premature drops in tcp_add_backlog() - macintosh/via-macii: Fix "BUG: sleeping function called from invalid context" - wifi: carl9170: add a proper sanity check for endpoints - wifi: ar5523: enable proper endpoint verification - sh: kprobes: Merge arch_copy_kprobe() into arch_prepare_kprobe() - Revert "sh: Handle calling csum_partial with misaligned data" - HID: intel-ish-hid: ipc: Add check for pci_alloc_irq_vectors - scsi: bfa: Ensure the copied buf is NUL terminated - scsi: qedf: Ensure the copied buf is NUL terminated - wifi: mwl8k: initialize cmd->addr[] properly - usb: aqc111: stop lying about skb->truesize - net: usb: sr9700: stop lying about skb->truesize - m68k: Fix spinlock race in kernel thread creation - m68k: mac: Fix reboot hang on Mac IIci - net: ethernet: cortina: Locking fixes - af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg - net: usb: smsc95xx: stop lying about skb->truesize - net: openvswitch: fix overwriting ct original tuple for ICMPv6 - ipv6: sr: add missing seg6_local_exit - ipv6: sr: fix incorrect unregister order - ipv6: sr: fix invalid unregister error path - drm/amd/display: Fix potential index out of bounds in color transformation function - mtd: rawnand: hynix: fixed typo - fbdev: shmobile: fix snprintf truncation - drm/mediatek: Add 0 size check to mtk_drm_gem_obj - powerpc/fsl-soc: hide unused const variable - fbdev: sisfb: hide unused variables - media: ngene: Add dvb_ca_en50221_init return value check - media: radio-shark2: Avoid led_names truncations - platform/x86: wmi: Make two functions static - fbdev: sh7760fb: allow modular build - drm/arm/malidp: fix a possible null pointer dereference - ASoC: tracing: Export SND_SOC_DAPM_DIR_OUT to its value - drm/panel: simple: Add missing Innolux G121X1-L03 format, flags, connector
[Kernel-packages] [Bug 2069758] Re: Focal update: v5.4.276 upstream stable release
This bug was fixed in the package linux - 5.4.0-192.212 --- linux (5.4.0-192.212) focal; urgency=medium * focal/linux: 5.4.0-192.212 -proposed tracker (LP: #2072305) * Focal update: v5.4.278 upstream stable release (LP: #2071668) - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - speakup: Fix sizeof() vs ARRAY_SIZE() bug - ring-buffer: Fix a race between readers and resize checks - net: smc91x: Fix m68k kernel compilation for ColdFire CPU - nilfs2: fix unexpected freezing of nilfs_segctor_sync() - nilfs2: fix potential hang in nilfs_detach_log_writer() - wifi: cfg80211: fix the order of arguments for trace events of the tx_rx_evt class - net: usb: qmi_wwan: add Telit FN920C04 compositions - drm/amd/display: Set color_mgmt_changed to true on unsuspend - ASoC: rt5645: Fix the electric noise due to the CBJ contacts floating - ASoC: dt-bindings: rt5645: add cbj sleeve gpio property - ASoC: da7219-aad: fix usage of device_get_named_child_node() - drm/amdkfd: Flush the process wq before creating a kfd_process - nvme: find numa distance only if controller has valid numa id - openpromfs: finish conversion to the new mount API - crypto: bcm - Fix pointer arithmetic - firmware: raspberrypi: Use correct device for DMA mappings - ecryptfs: Fix buffer size for tag 66 packet - nilfs2: fix out-of-range warning - parisc: add missing export of __cmpxchg_u8() - crypto: ccp - drop platform ifdef checks - s390/cio: fix tracepoint subchannel type field - jffs2: prevent xattr node from overflowing the eraseblock - null_blk: Fix missing mutex_destroy() at module removal - md: fix resync softlockup when bitmap size is less than array size - wifi: ath10k: poll service ready message before failing - x86/boot: Ignore relocations in .notes sections in walk_relocs() too - qed: avoid truncating work queue length - scsi: ufs: qcom: Perform read back after writing reset bit - scsi: ufs: cdns-pltfrm: Perform read back after writing HCLKDIV - scsi: ufs: core: Perform read back after disabling interrupts - scsi: ufs: core: Perform read back after disabling UIC_COMMAND_COMPL - irqchip/alpine-msi: Fix off-by-one in allocation error path - ACPI: disable -Wstringop-truncation - cpufreq: Reorganize checks in cpufreq_offline() - cpufreq: Split cpufreq_offline() - cpufreq: Rearrange locking in cpufreq_remove_dev() - cpufreq: exit() callback is optional - scsi: libsas: Fix the failure of adding phy with zero-address to port - scsi: hpsa: Fix allocation size for Scsi_Host private data - x86/purgatory: Switch to the position-independent small code model - wifi: ath10k: Fix an error code problem in ath10k_dbg_sta_write_peer_debug_trigger() - wifi: ath10k: populate board data for WCN3990 - tcp: minor optimization in tcp_add_backlog() - tcp: fix a signed-integer-overflow bug in tcp_add_backlog() - tcp: avoid premature drops in tcp_add_backlog() - macintosh/via-macii: Fix "BUG: sleeping function called from invalid context" - wifi: carl9170: add a proper sanity check for endpoints - wifi: ar5523: enable proper endpoint verification - sh: kprobes: Merge arch_copy_kprobe() into arch_prepare_kprobe() - Revert "sh: Handle calling csum_partial with misaligned data" - HID: intel-ish-hid: ipc: Add check for pci_alloc_irq_vectors - scsi: bfa: Ensure the copied buf is NUL terminated - scsi: qedf: Ensure the copied buf is NUL terminated - wifi: mwl8k: initialize cmd->addr[] properly - usb: aqc111: stop lying about skb->truesize - net: usb: sr9700: stop lying about skb->truesize - m68k: Fix spinlock race in kernel thread creation - m68k: mac: Fix reboot hang on Mac IIci - net: ethernet: cortina: Locking fixes - af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg - net: usb: smsc95xx: stop lying about skb->truesize - net: openvswitch: fix overwriting ct original tuple for ICMPv6 - ipv6: sr: add missing seg6_local_exit - ipv6: sr: fix incorrect unregister order - ipv6: sr: fix invalid unregister error path - drm/amd/display: Fix potential index out of bounds in color transformation function - mtd: rawnand: hynix: fixed typo - fbdev: shmobile: fix snprintf truncation - drm/mediatek: Add 0 size check to mtk_drm_gem_obj - powerpc/fsl-soc: hide unused const variable - fbdev: sisfb: hide unused variables - media: ngene: Add dvb_ca_en50221_init return value check - media: radio-shark2: Avoid led_names truncations - platform/x86: wmi: Make two functions static - fbdev: sh7760fb: allow modular build - drm/arm/malidp: fix a possible null pointer dereference - ASoC: tracing: Export SND_SOC_DAPM_DIR_OUT to its value - drm/panel: simple: Add missing Innolux G121X1-L03 format, flags, connector
[Kernel-packages] [Bug 2073049] Re: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
This bug was fixed in the package linux-oem-6.8 - 6.8.0-1010.10 --- linux-oem-6.8 (6.8.0-1010.10) noble; urgency=medium * noble/linux-oem-6.8: 6.8.0-1010.10 -proposed tracker (LP: #2072187) * No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression] (LP: #2073049) - ASoC: amd: acp: fix for acp platform device creation failure [ Ubuntu: 6.8.0-40.40 ] * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs - selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly - ftrace: Fix possible use-after-free issue in ftrace_location() - Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - arm64/fpsimd: Avoid erroneous elide of user state reload - Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" - tty: n_gsm: fix missing receive state reset after mode switch - speakup: Fix sizeof() vs ARRAY_SIZE() bug - serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler - serial: 8250_bcm7271: use default_mux_rate if possible - serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup - Input: try trimming too long modalias strings - io_
[Kernel-packages] [Bug 2074082] Re: Enable Microchip PIC64GX Curiosity Kit
This bug was fixed in the package linux-riscv - 6.8.0-40.40.1 --- linux-riscv (6.8.0-40.40.1) noble; urgency=medium * noble/linux-riscv: 6.8.0-40.40.1 -proposed tracker (LP: #2072197) * Noble update: v6.8.12 upstream stable release (LP: #2071621) - SAUCE: pwm: opencores: drop use of deprecated member .of_pwm_n_cells * Enable Microchip PIC64GX Curiosity Kit (LP: #2074082) - dt-bindings: gpio: mpfs: add coreGPIO support - dt-bindings: gpio: mpfs: allow gpio-line-names - SAUCE: dt-bindings: can: mpfs: add PIC64GX CAN compatibility - SAUCE: dt-bindings: usb: add PIC64GX compatibility to mpfs-musb driver - SAUCE: dt-bindings: mbox: add PIC64GX mailbox compatibility to MPFS mailbox - SAUCE: dt-bindings: spi: add PIC64GX SPI/QSPI compatibility to MPFS SPI/QSPI bindings - SAUCE: dt-bindings: gpio: mpfs-gpio: Add PIC64GX GPIO compatibility - SAUCE: dt-bindings: riscv: sifive-l2: add a PIC64GX compatible - SAUCE: dt-bindings: clock: mpfs-ccc: Add PIC64GX compatibility - SAUCE: dt-bindings: clock: mpfs-clkcfg: Add PIC64GX compatibility - SAUCE: dt-bindings: dma: sifive pdma: Add PIC64GX to compatibles - SAUCE: dt-bindings: i2c: microchip: corei2c: Add PIC64GX as compatible with driver - SAUCE: dt-bindings: mmc: cdns: document Microchip PIC64GX MMC/SDHCI controller - SAUCE: dt-bindings: net: cdns,macb: Add PIC64GX compatibility - SAUCE: dt-bindings: rtc: mfps-rtc: Add PIC64GX compatibility - SAUCE: dt-bindings: soc: microchip: mpfs-sys-controller: Add PIC64GX compatibility - SAUCE: dt-bindings: clk: microchip: Add Microchip PIC64GX host binding - SAUCE: dt-bindings: riscv: microchip: document the PIC64GX curiosity kit - SAUCE: riscv: dts: microchip: add PIC64GX Curiosity Kit dts * Enable StarFive VisionFive 2 board (LP: #2013232) - riscv: dts: starfive: Update flash partition layout [ Ubuntu: 6.8.0-40.40 ] * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI version
[Kernel-packages] [Bug 2071655] Re: PR for: "IB/mlx5: Use __iowrite64_copy() for write combining stores"
This bug was fixed in the package linux-nvidia - 6.8.0-1011.11 --- linux-nvidia (6.8.0-1011.11) noble; urgency=medium * noble/linux-nvidia: 6.8.0-1011.11 -proposed tracker (LP: #2072186) * PR for: "IB/mlx5: Use __iowrite64_copy() for write combining stores" (LP: #2071655) - x86: Stop using weak symbols for __iowrite32_copy() - s390: Implement __iowrite32_copy() - s390: Stop using weak symbols for __iowrite64_copy() - arm64/io: Provide a WC friendly __iowriteXX_copy() - net: hns3: Remove io_stop_wc() calls after __iowrite64_copy() * PR for: "PCI: Clear Secondary Status errors after enumeration" (LP: #2071654) - PCI: Clear Secondary Status errors after enumeration * mlxbf_pmc: bring in latest 6.8 upstream commits (LP: #2069777) - platform/mellanox: mlxbf-pmc: Replace uintN_t with kernel-style types - platform/mellanox: mlxbf-pmc: Cleanup signed/unsigned mix-up - platform/mellanox: mlxbf-pmc: mlxbf_pmc_event_list(): make size ptr optional - platform/mellanox: mlxbf-pmc: Ignore unsupported performance blocks - platform/mellanox: mlxbf-pmc: fix signedness bugs [ Ubuntu: 6.8.0-40.40 ] * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offs
[Kernel-packages] [Bug 2071654] Re: PR for: "PCI: Clear Secondary Status errors after enumeration"
This bug was fixed in the package linux-nvidia - 6.8.0-1011.11 --- linux-nvidia (6.8.0-1011.11) noble; urgency=medium * noble/linux-nvidia: 6.8.0-1011.11 -proposed tracker (LP: #2072186) * PR for: "IB/mlx5: Use __iowrite64_copy() for write combining stores" (LP: #2071655) - x86: Stop using weak symbols for __iowrite32_copy() - s390: Implement __iowrite32_copy() - s390: Stop using weak symbols for __iowrite64_copy() - arm64/io: Provide a WC friendly __iowriteXX_copy() - net: hns3: Remove io_stop_wc() calls after __iowrite64_copy() * PR for: "PCI: Clear Secondary Status errors after enumeration" (LP: #2071654) - PCI: Clear Secondary Status errors after enumeration * mlxbf_pmc: bring in latest 6.8 upstream commits (LP: #2069777) - platform/mellanox: mlxbf-pmc: Replace uintN_t with kernel-style types - platform/mellanox: mlxbf-pmc: Cleanup signed/unsigned mix-up - platform/mellanox: mlxbf-pmc: mlxbf_pmc_event_list(): make size ptr optional - platform/mellanox: mlxbf-pmc: Ignore unsupported performance blocks - platform/mellanox: mlxbf-pmc: fix signedness bugs [ Ubuntu: 6.8.0-40.40 ] * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offs
[Kernel-packages] [Bug 2069777] Re: mlxbf_pmc: bring in latest 6.8 upstream commits
This bug was fixed in the package linux-nvidia - 6.8.0-1011.11 --- linux-nvidia (6.8.0-1011.11) noble; urgency=medium * noble/linux-nvidia: 6.8.0-1011.11 -proposed tracker (LP: #2072186) * PR for: "IB/mlx5: Use __iowrite64_copy() for write combining stores" (LP: #2071655) - x86: Stop using weak symbols for __iowrite32_copy() - s390: Implement __iowrite32_copy() - s390: Stop using weak symbols for __iowrite64_copy() - arm64/io: Provide a WC friendly __iowriteXX_copy() - net: hns3: Remove io_stop_wc() calls after __iowrite64_copy() * PR for: "PCI: Clear Secondary Status errors after enumeration" (LP: #2071654) - PCI: Clear Secondary Status errors after enumeration * mlxbf_pmc: bring in latest 6.8 upstream commits (LP: #2069777) - platform/mellanox: mlxbf-pmc: Replace uintN_t with kernel-style types - platform/mellanox: mlxbf-pmc: Cleanup signed/unsigned mix-up - platform/mellanox: mlxbf-pmc: mlxbf_pmc_event_list(): make size ptr optional - platform/mellanox: mlxbf-pmc: Ignore unsupported performance blocks - platform/mellanox: mlxbf-pmc: fix signedness bugs [ Ubuntu: 6.8.0-40.40 ] * noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201) * FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380) - drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access * a critical typo in the code managing the ASPM settings for PCI Express devices (LP: #2071889) - PCI/ASPM: Restore parent state to parent, child state to child * [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads (LP: #2071471) - [Config] Set IOMMU_DEFAULT_DMA_STRICT=n and IOMMU_DEFAULT_DMA_LAZY=yes for s390x * UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 (LP: #2039368) - bcache: fix variable length array abuse in btree_iter * Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 (LP: #2071296) - ALSA: hda/realtek: fix mute/micmute LEDs don't work for EliteBook 645/665 G11. * failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 (LP: #2067364) - mei: vsc: Don't stop/restart mei device during system suspend/resume - SAUCE: media: ivsc: csi: don't count privacy on as error - SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler - SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi - SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot - SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom - SAUCE: mei: vsc: Utilize the appropriate byte order swap function - SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download * failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22 (LP: #2070251) - ACPI: utils: Make acpi_handle_path() not static - ACPI: property: Ignore bad graph port nodes on Dell XPS 9315 - ACPI: property: Polish ignoring bad data nodes - ACPI: scan: Ignore camera graph port nodes on all Dell Tiger, Alder and Raptor Lake models * Update amd_sfh for AMD strix series (LP: #2058331) - HID: amd_sfh: Increase sensor command timeout - HID: amd_sfh: Improve boot time when SFH is available - HID: amd_sfh: Extend MP2 register access to SFH - HID: amd_sfh: Set the AMD SFH driver to depend on x86 * RFIM and SAGV Linux Support for G10 models (LP: #2070158) - drm/i915/display: Add meaningful traces for QGV point info error handling - drm/i915/display: Extract code required to calculate max qgv/psf gv point - drm/i915/display: extract code to prepare qgv points mask - drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation - drm/i915/display: handle systems with duplicate psf gv points - drm/i915/display: force qgv check after the hw state readout * Update amd-pmf for AMD strix series (LP: #2058330) - platform/x86/amd/pmf: Differentiate PMF ACPI versions - platform/x86/amd/pmf: Disable debugfs support for querying power thermals - platform/x86/amd/pmf: Add support to get sbios requests in PMF driver - platform/x86/amd/pmf: Add support to notify sbios heart beat event - platform/x86/amd/pmf: Add support to get APTS index numbers for static slider - platform/x86/amd/pmf: Add support to get sps default APTS index values - platform/x86/amd/pmf: Update sps power thermals according to the platform- profiles * noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency (LP: #2070042) - [DEP-8] Add missing fakeroot dependency * Noble update: v6.8.12 upstream stable release (LP: #2071621) - sunrpc: use the struct net as the svc proc private - x86/tsc: Trust initial offs
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
This bug is awaiting verification that the linux-bluefield/5.4.0-1090.97 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-focal-linux-bluefield' to 'verification-done- focal-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-focal-linux-bluefield' to 'verification-failed- focal-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-focal-linux-bluefield-v2 verification-needed-focal-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 source package in Focal: Fix Committed Status in linux-signed-hwe-6.5 source package in Jammy: Fix Committed Status in linux-signed-hwe-6.5 source package in Mantic: Won't Fix Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Cur
[Kernel-packages] [Bug 2071889] Re: a critical typo in the code managing the ASPM settings for PCI Express devices
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2 verification-needed-noble-linux-azure -- 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/2071889 Title: a critical typo in the code managing the ASPM settings for PCI Express devices Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: Fix Released Bug description: [Impact] The typo in the original code led to the PCI_EXP_LNKCTL register values being swapped between the parent PCI device and its child device. It may lead to incorrect power state, device malfunction on system resume, or potential data loss or system stability issues. [Fix] Kaiheng submitted a patch to fix the issue and has been included in v6.9 mainline kernel. f3d049b35b01 PCI/ASPM: Restore parent state to parent, child state to child [Test] There is no test cases for the issue now. [Where problems may occur] It fixes the typo and should not introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2071889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2074082] Re: Enable Microchip PIC64GX Curiosity Kit
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-40.40.1~22.04.1 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- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2074082 Title: Enable Microchip PIC64GX Curiosity Kit Status in linux-riscv package in Ubuntu: Fix Released Bug description: Apply patches from the PIC64GX kernel repository on GitHub to support the Microchip PIC64GX Curiosity Kit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2074082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2071889] Re: a critical typo in the code managing the ASPM settings for PCI Express devices
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2071889 Title: a critical typo in the code managing the ASPM settings for PCI Express devices Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: Fix Released Bug description: [Impact] The typo in the original code led to the PCI_EXP_LNKCTL register values being swapped between the parent PCI device and its child device. It may lead to incorrect power state, device malfunction on system resume, or potential data loss or system stability issues. [Fix] Kaiheng submitted a patch to fix the issue and has been included in v6.9 mainline kernel. f3d049b35b01 PCI/ASPM: Restore parent state to parent, child state to child [Test] There is no test cases for the issue now. [Where problems may occur] It fixes the typo and should not introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2071889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2071889] Re: a critical typo in the code managing the ASPM settings for PCI Express devices
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-40.40.1~22.04.1 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- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2071889 Title: a critical typo in the code managing the ASPM settings for PCI Express devices Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: Fix Released Bug description: [Impact] The typo in the original code led to the PCI_EXP_LNKCTL register values being swapped between the parent PCI device and its child device. It may lead to incorrect power state, device malfunction on system resume, or potential data loss or system stability issues. [Fix] Kaiheng submitted a patch to fix the issue and has been included in v6.9 mainline kernel. f3d049b35b01 PCI/ASPM: Restore parent state to parent, child state to child [Test] There is no test cases for the issue now. [Where problems may occur] It fixes the typo and should not introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2071889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2071471] Re: [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2 verification-needed-noble-linux-azure -- 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/2071471 Title: [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: Fix Committed Bug description: SRU Justification: [Impact] * With the introduction of c76c067e488c "s390/pci: Use dma-iommu layer" (upstream with since kernel v6.7-rc1) there was a move (on s390x only) to a different dma-iommu implementation. * And with 92bce97f0c34 "s390/pci: Fix reset of IOMMU software counters" (again upstream since 6.7(rc-1) the IOMMU_DEFAULT_DMA_LAZY kernel config option should now be set to 'yes' by default for s390x. * Since CONFIG_IOMMU_DEFAULT_DMA_STRICT and IOMMU_DEFAULT_DMA_LAZY are related to each other CONFIG_IOMMU_DEFAULT_DMA_STRICT needs to be set to "no" by default, which was upstream done by b2b97a62f055 "Revert "s390: update defconfigs"". * These changes are all upstream, but were not picked up by the Ubuntu kernel config. * And not having these config options set properly is causing significant PCI-related network throughput degradation (up to -72%). * This shows for almost all workloads and numbers of connections, deteriorating with the number of connections increasing. * Especially drastic is the drop for a high number of parallel connections (50 and 250) and for small and medium-size transactional workloads. However, also for streaming-type workloads the degradation is clearly visible (up to 48% degradation). [Fix] * The (upstream accepted) fix is to set IOMMU_DEFAULT_DMA_STRICT=no and IOMMU_DEFAULT_DMA_LAZY=y (which is needed for the changed DAM IOMMU implementation since v6.7). [Test Case] * Setup two Ubuntu Server 24.04 systems (with kernel 6.8) (one acting as server and as client) that have (PCIe attached) RoCE Express devices attached and that are connected to each other. * Verify if the the iommu_group type of the used PCI device is DMA-FQ: cat /sys/bus/pci/devices/\:00\:00.0/iommu_group/type DMA-FQ * Sample workload rr1c-200x1000-250 with rr1c-200x1000-250.xml: * Install uperf on both systems, client and server. * Start uperf at server: uperf -s * Start uperf at client: uperf -vai 5 -m uperf-profile.xml * Switch from strict to lazy mode either using the new kernel (or the test build below) or using kernel cmd-line parameter iommu.strict=0. * Restart uperf on server and client, like before. * Verification will be performed by IBM. [Regression Potential] * The is a certain regression potential, since the behavior with the two modified kernel config options will change significantly. * This may solve the (network) throughput issue with PCI devices, but may also come with side-effects on other PCIe based devices (the old compression adapters or the new NVMe carrier cards). [Other] * CCW devices are not affected. * This is s390x-specific only, hence will not affect any other architecture. __ Symptom: Comparing Ubuntu 24.04 (kernelversion: 6.8.0-31-generic) against Ubuntu 22.04, all of our PCI-related network measurements on LPAR show massive throughput degradations (up to -72%). This shows for almost all workloads and numbers of connections, detereorating with the number of connections increasing. Especially drastic is the drop for a high number of parallel connections (50 and 250) and for small and medium-size transactional workloads. However, also for streaming-type
[Kernel-packages] [Bug 2071471] Re: [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2071471 Title: [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: Fix Committed Bug description: SRU Justification: [Impact] * With the introduction of c76c067e488c "s390/pci: Use dma-iommu layer" (upstream with since kernel v6.7-rc1) there was a move (on s390x only) to a different dma-iommu implementation. * And with 92bce97f0c34 "s390/pci: Fix reset of IOMMU software counters" (again upstream since 6.7(rc-1) the IOMMU_DEFAULT_DMA_LAZY kernel config option should now be set to 'yes' by default for s390x. * Since CONFIG_IOMMU_DEFAULT_DMA_STRICT and IOMMU_DEFAULT_DMA_LAZY are related to each other CONFIG_IOMMU_DEFAULT_DMA_STRICT needs to be set to "no" by default, which was upstream done by b2b97a62f055 "Revert "s390: update defconfigs"". * These changes are all upstream, but were not picked up by the Ubuntu kernel config. * And not having these config options set properly is causing significant PCI-related network throughput degradation (up to -72%). * This shows for almost all workloads and numbers of connections, deteriorating with the number of connections increasing. * Especially drastic is the drop for a high number of parallel connections (50 and 250) and for small and medium-size transactional workloads. However, also for streaming-type workloads the degradation is clearly visible (up to 48% degradation). [Fix] * The (upstream accepted) fix is to set IOMMU_DEFAULT_DMA_STRICT=no and IOMMU_DEFAULT_DMA_LAZY=y (which is needed for the changed DAM IOMMU implementation since v6.7). [Test Case] * Setup two Ubuntu Server 24.04 systems (with kernel 6.8) (one acting as server and as client) that have (PCIe attached) RoCE Express devices attached and that are connected to each other. * Verify if the the iommu_group type of the used PCI device is DMA-FQ: cat /sys/bus/pci/devices/\:00\:00.0/iommu_group/type DMA-FQ * Sample workload rr1c-200x1000-250 with rr1c-200x1000-250.xml: * Install uperf on both systems, client and server. * Start uperf at server: uperf -s * Start uperf at client: uperf -vai 5 -m uperf-profile.xml * Switch from strict to lazy mode either using the new kernel (or the test build below) or using kernel cmd-line parameter iommu.strict=0. * Restart uperf on server and client, like before. * Verification will be performed by IBM. [Regression Potential] * The is a certain regression potential, since the behavior with the two modified kernel config options will change significantly. * This may solve the (network) throughput issue with PCI devices, but may also come with side-effects on other PCIe based devices (the old compression adapters or the new NVMe carrier cards). [Other] * CCW devices are not affected. * This is s390x-specific only, hence will not affect any other architecture. __ Symptom: Comparing Ubuntu 24.04 (kernelversion: 6.8.0-31-generic) against Ubuntu 22.04, all of our PCI-related network measurements on LPAR show massive throughput degradations (up to -72%). This shows for almost all workloads and numbers of connections, detereorating with the number of connections increasing. Especially drastic is the drop for a high number of parallel connections (50 and 250) and for small and medium-size transactional workloads. However, also for streaming-type
[Kernel-packages] [Bug 2071471] Re: [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-40.40.1~22.04.1 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- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2071471 Title: [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: Fix Committed Bug description: SRU Justification: [Impact] * With the introduction of c76c067e488c "s390/pci: Use dma-iommu layer" (upstream with since kernel v6.7-rc1) there was a move (on s390x only) to a different dma-iommu implementation. * And with 92bce97f0c34 "s390/pci: Fix reset of IOMMU software counters" (again upstream since 6.7(rc-1) the IOMMU_DEFAULT_DMA_LAZY kernel config option should now be set to 'yes' by default for s390x. * Since CONFIG_IOMMU_DEFAULT_DMA_STRICT and IOMMU_DEFAULT_DMA_LAZY are related to each other CONFIG_IOMMU_DEFAULT_DMA_STRICT needs to be set to "no" by default, which was upstream done by b2b97a62f055 "Revert "s390: update defconfigs"". * These changes are all upstream, but were not picked up by the Ubuntu kernel config. * And not having these config options set properly is causing significant PCI-related network throughput degradation (up to -72%). * This shows for almost all workloads and numbers of connections, deteriorating with the number of connections increasing. * Especially drastic is the drop for a high number of parallel connections (50 and 250) and for small and medium-size transactional workloads. However, also for streaming-type workloads the degradation is clearly visible (up to 48% degradation). [Fix] * The (upstream accepted) fix is to set IOMMU_DEFAULT_DMA_STRICT=no and IOMMU_DEFAULT_DMA_LAZY=y (which is needed for the changed DAM IOMMU implementation since v6.7). [Test Case] * Setup two Ubuntu Server 24.04 systems (with kernel 6.8) (one acting as server and as client) that have (PCIe attached) RoCE Express devices attached and that are connected to each other. * Verify if the the iommu_group type of the used PCI device is DMA-FQ: cat /sys/bus/pci/devices/\:00\:00.0/iommu_group/type DMA-FQ * Sample workload rr1c-200x1000-250 with rr1c-200x1000-250.xml: * Install uperf on both systems, client and server. * Start uperf at server: uperf -s * Start uperf at client: uperf -vai 5 -m uperf-profile.xml * Switch from strict to lazy mode either using the new kernel (or the test build below) or using kernel cmd-line parameter iommu.strict=0. * Restart uperf on server and client, like before. * Verification will be performed by IBM. [Regression Potential] * The is a certain regression potential, since the behavior with the two modified kernel config options will change significantly. * This may solve the (network) throughput issue with PCI devices, but may also come with side-effects on other PCIe based devices (the old compression adapters or the new NVMe carrier cards). [Other] * CCW devices are not affected. * This is s390x-specific only, hence will not affect any other architecture. __ Symptom: Comparing Ubuntu 24.04 (kernelversion: 6.8.0-31-generic) against Ubuntu 22.04, all of our PCI-related network measurements on LPAR show massive throughput degradations (up to -72%). This shows for almost all workloads and numbers of connections, detereorating with the number of connections increasing. Especially drastic is the drop for a high number of parallel connections (50 and 250) and for small and medium-size transactional workload
[Kernel-packages] [Bug 2071296] Re: Mute/mic LEDs and speaker no function on EliteBook 645/665 G11
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2 verification-needed-noble-linux-azure -- 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/2071296 Title: Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on EliteBook 645/665 G11 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2071296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2071296] Re: Mute/mic LEDs and speaker no function on EliteBook 645/665 G11
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2071296 Title: Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on EliteBook 645/665 G11 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2071296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2071296] Re: Mute/mic LEDs and speaker no function on EliteBook 645/665 G11
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-40.40.1~22.04.1 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- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2071296 Title: Mute/mic LEDs and speaker no function on EliteBook 645/665 G11 Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on EliteBook 645/665 G11 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2071296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2070251] Re: failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2
verification-needed-noble-linux-azure
--
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/2070251
Title:
failed to probe camera sensor on Dell XPS 9315: ov01a10
i2c-OVTI01A0:00: failed to check hwcfg: -22
Status in ipu6-drivers package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-6.10 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in ipu6-drivers source package in Jammy:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.10 source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Invalid
Status in linux-oem-6.8 source package in Jammy:
Invalid
Status in ipu6-drivers source package in Noble:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.10 source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Status in linux-oem-6.8 source package in Noble:
Fix Released
Status in ipu6-drivers source package in Oracular:
Fix Released
Status in linux source package in Oracular:
Triaged
Status in linux-oem-6.10 source package in Oracular:
Invalid
Status in linux-oem-6.5 source package in Oracular:
Invalid
Status in linux-oem-6.8 source package in Oracular:
Invalid
Bug description:
[SRU Justification]
[Impact]
Multiple early IPU6 platforms may not have formal MIPI DisCo data
embedded in ACPI, and they may confuse latter driver and fail device
probing:
ov01a10 i2c-OVTI01A0:00: can't get clock frequency
ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22
ov01a10: probe of i2c-OVTI01A0:00 failed with error -22
[Fix]
A few commits from mainline kernel up to v6.10-rc5.
[Test Case]
Camera sensor device should then be probed correctly.
[Where problems could occur]
These fixes are based on MIPI DisCo support that is only available since
v6.8. For older kernels, the ipu6-drivers either has no hwcfg checking
implemented, or patched with DMI info to skip it.
[Other Info]
While the patches are from v6.10-rc5, only Noble and OEM-6.8 will be
nominated for fixing.
== original bug report ==
[5.630239] ov01a10 i2c-OVTI01A0:00: can't get clock frequency
[5.630248] ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22
[5.631760] ov01a10: probe of i2c-OVTI01A0:00 failed with error -22
Supposed to be fixed in upstream v6.9 commit 5bd4edbbf920 ("ACPI: property:
Ignore bad graph port nodes on Dell XPS 9315").
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-edge-alloem-init+X34
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-10-23 (245 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220425-25
IwConfig:
lono wireless extensions.
enxa0cec8d68afe no wireless extensions.
MachineType: Dell Inc. XPS 9315
Package: linux-oem-6.8
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9024-oem
root=UUID=739f24ca-e488-4c9b-86e1-73d3ab581bcb ro nomodeset
automatic-oem-config quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9024.25+exp.46-oem 6.5.13
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-9024-oem N/A
linux-backports-modules-6.5.0-9024-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.31
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 6.5.0-9024-oem x8
[Kernel-packages] [Bug 2070251] Re: failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10
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-noble-linux-raspi' to 'verification-done-noble-
linux-raspi'. If the problem still exists, change the tag 'verification-
needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'.
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-noble-linux-raspi-v2
verification-needed-noble-linux-raspi
--
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/2070251
Title:
failed to probe camera sensor on Dell XPS 9315: ov01a10
i2c-OVTI01A0:00: failed to check hwcfg: -22
Status in ipu6-drivers package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-6.10 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in ipu6-drivers source package in Jammy:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.10 source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Invalid
Status in linux-oem-6.8 source package in Jammy:
Invalid
Status in ipu6-drivers source package in Noble:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.10 source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Status in linux-oem-6.8 source package in Noble:
Fix Released
Status in ipu6-drivers source package in Oracular:
Fix Released
Status in linux source package in Oracular:
Triaged
Status in linux-oem-6.10 source package in Oracular:
Invalid
Status in linux-oem-6.5 source package in Oracular:
Invalid
Status in linux-oem-6.8 source package in Oracular:
Invalid
Bug description:
[SRU Justification]
[Impact]
Multiple early IPU6 platforms may not have formal MIPI DisCo data
embedded in ACPI, and they may confuse latter driver and fail device
probing:
ov01a10 i2c-OVTI01A0:00: can't get clock frequency
ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22
ov01a10: probe of i2c-OVTI01A0:00 failed with error -22
[Fix]
A few commits from mainline kernel up to v6.10-rc5.
[Test Case]
Camera sensor device should then be probed correctly.
[Where problems could occur]
These fixes are based on MIPI DisCo support that is only available since
v6.8. For older kernels, the ipu6-drivers either has no hwcfg checking
implemented, or patched with DMI info to skip it.
[Other Info]
While the patches are from v6.10-rc5, only Noble and OEM-6.8 will be
nominated for fixing.
== original bug report ==
[5.630239] ov01a10 i2c-OVTI01A0:00: can't get clock frequency
[5.630248] ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22
[5.631760] ov01a10: probe of i2c-OVTI01A0:00 failed with error -22
Supposed to be fixed in upstream v6.9 commit 5bd4edbbf920 ("ACPI: property:
Ignore bad graph port nodes on Dell XPS 9315").
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-edge-alloem-init+X34
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-10-23 (245 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220425-25
IwConfig:
lono wireless extensions.
enxa0cec8d68afe no wireless extensions.
MachineType: Dell Inc. XPS 9315
Package: linux-oem-6.8
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9024-oem
root=UUID=739f24ca-e488-4c9b-86e1-73d3ab581bcb ro nomodeset
automatic-oem-config quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9024.25+exp.46-oem 6.5.13
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-9024-oem N/A
linux-backports-modules-6.5.0-9024-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.31
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 6.5.0-9024-oem x8
[Kernel-packages] [Bug 2070158] Re: RFIM and SAGV Linux Support for G10 models
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2070158 Title: RFIM and SAGV Linux Support for G10 models Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2070158 [Impact] This is a feature request from HP, RFIM is for frequency, SAGV is for voltage. They are used as dynamic switching to reduce RF noise. RFIM is already supported in the kernel, this patchset adds the SAGV feature. [Fix] Cherry-pick 6 commits from mainline kernel [Test] Enable the SAGV from the BIOS, booting with the patched kernel, after booting up, run 'systemctl status dtt.service', we will get: service is enabled and service is running run 'cat /sys/kernel/debug/dri/:00:02.0/i915_sagv_status', we will get: SAGV available: Yes SAGV status: enabled [Where problems could occur] Because the fix is for i915, it is likely introduce regression on graphic, but this possibility is very low. These 6 commits are merged to mainline kernel from v6.10-rc1, so far there is no regression reported on them. And we tested the patched kernel on different Intel machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2070158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2070158] Re: RFIM and SAGV Linux Support for G10 models
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2 verification-needed-noble-linux-azure -- 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/2070158 Title: RFIM and SAGV Linux Support for G10 models Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2070158 [Impact] This is a feature request from HP, RFIM is for frequency, SAGV is for voltage. They are used as dynamic switching to reduce RF noise. RFIM is already supported in the kernel, this patchset adds the SAGV feature. [Fix] Cherry-pick 6 commits from mainline kernel [Test] Enable the SAGV from the BIOS, booting with the patched kernel, after booting up, run 'systemctl status dtt.service', we will get: service is enabled and service is running run 'cat /sys/kernel/debug/dri/:00:02.0/i915_sagv_status', we will get: SAGV available: Yes SAGV status: enabled [Where problems could occur] Because the fix is for i915, it is likely introduce regression on graphic, but this possibility is very low. These 6 commits are merged to mainline kernel from v6.10-rc1, so far there is no regression reported on them. And we tested the patched kernel on different Intel machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2070158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2070042] Re: noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2 verification-needed-noble-linux-azure -- 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/2070042 Title: noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Released Bug description: The DEP-8 ubuntu-regression-suite of tests is failing in setup because fakeroot is not installed. This likely was previously included in build-essential. autotest.client.shared.error.CmdError: Command failed, rc=127, Command returned non-zero exit status * Command: fakeroot debian/rules clean Exit status: 127 Duration: 0.0017809867858886719 stderr: /bin/bash: line 1: fakeroot: command not found Fix will be to update the dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2070251] Re: failed to probe camera sensor on Dell XPS 9315: ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-40.40.1~22.04.1 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-
riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8'
to 'verification-failed-jammy-linux-riscv-6.8'.
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-riscv-6.8-v2
verification-needed-jammy-linux-riscv-6.8
--
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/2070251
Title:
failed to probe camera sensor on Dell XPS 9315: ov01a10
i2c-OVTI01A0:00: failed to check hwcfg: -22
Status in ipu6-drivers package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-6.10 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in ipu6-drivers source package in Jammy:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.10 source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Invalid
Status in linux-oem-6.8 source package in Jammy:
Invalid
Status in ipu6-drivers source package in Noble:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.10 source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Status in linux-oem-6.8 source package in Noble:
Fix Released
Status in ipu6-drivers source package in Oracular:
Fix Released
Status in linux source package in Oracular:
Triaged
Status in linux-oem-6.10 source package in Oracular:
Invalid
Status in linux-oem-6.5 source package in Oracular:
Invalid
Status in linux-oem-6.8 source package in Oracular:
Invalid
Bug description:
[SRU Justification]
[Impact]
Multiple early IPU6 platforms may not have formal MIPI DisCo data
embedded in ACPI, and they may confuse latter driver and fail device
probing:
ov01a10 i2c-OVTI01A0:00: can't get clock frequency
ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22
ov01a10: probe of i2c-OVTI01A0:00 failed with error -22
[Fix]
A few commits from mainline kernel up to v6.10-rc5.
[Test Case]
Camera sensor device should then be probed correctly.
[Where problems could occur]
These fixes are based on MIPI DisCo support that is only available since
v6.8. For older kernels, the ipu6-drivers either has no hwcfg checking
implemented, or patched with DMI info to skip it.
[Other Info]
While the patches are from v6.10-rc5, only Noble and OEM-6.8 will be
nominated for fixing.
== original bug report ==
[5.630239] ov01a10 i2c-OVTI01A0:00: can't get clock frequency
[5.630248] ov01a10 i2c-OVTI01A0:00: failed to check hwcfg: -22
[5.631760] ov01a10: probe of i2c-OVTI01A0:00 failed with error -22
Supposed to be fixed in upstream v6.9 commit 5bd4edbbf920 ("ACPI: property:
Ignore bad graph port nodes on Dell XPS 9315").
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-edge-alloem-init+X34
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-10-23 (245 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220425-25
IwConfig:
lono wireless extensions.
enxa0cec8d68afe no wireless extensions.
MachineType: Dell Inc. XPS 9315
Package: linux-oem-6.8
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9024-oem
root=UUID=739f24ca-e488-4c9b-86e1-73d3ab581bcb ro nomodeset
automatic-oem-config quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9024.25+exp.46-oem 6.5.13
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-9024-oem N/A
linux-backports-modules-6.5.0-9024-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.31
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: ja
[Kernel-packages] [Bug 2069664] Re: Mute/mic LEDs no function on ProBook 445/465 G11
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2 verification-needed-noble-linux-azure -- 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/2069664 Title: Mute/mic LEDs no function on ProBook 445/465 G11 Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Confirmed Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook 445/465 G11 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2069664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2070042] Re: noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2070042 Title: noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Released Bug description: The DEP-8 ubuntu-regression-suite of tests is failing in setup because fakeroot is not installed. This likely was previously included in build-essential. autotest.client.shared.error.CmdError: Command failed, rc=127, Command returned non-zero exit status * Command: fakeroot debian/rules clean Exit status: 127 Duration: 0.0017809867858886719 stderr: /bin/bash: line 1: fakeroot: command not found Fix will be to update the dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069664] Re: Mute/mic LEDs no function on ProBook 445/465 G11
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2069664 Title: Mute/mic LEDs no function on ProBook 445/465 G11 Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Confirmed Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook 445/465 G11 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2069664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069664] Re: Mute/mic LEDs no function on ProBook 445/465 G11
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-40.40.1~22.04.1 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- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2069664 Title: Mute/mic LEDs no function on ProBook 445/465 G11 Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Confirmed Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook 445/465 G11 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2069664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069380] Re: FPS of glxgear with fullscreen is too low on MTL platform
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2069380 Title: FPS of glxgear with fullscreen is too low on MTL platform Status in linux package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: [Impact] Run `glxgears -fullscreen` and the FPS can't stay at 60 FPS 298 frames in 5.0 seconds = 59.465 FPS 241 frames in 5.0 seconds = 48.193 FPS 261 frames in 5.0 seconds = 52.030 FPS 268 frames in 5.0 seconds = 53.596 FPS [Fix] Bisect the kernel and found a commit in v6.9-rc1 fixes the issue c08c364102d0 drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access [Test] 1. Run `glxgears -fullscreen` on MTL platforms 2. The FPS should be always around 60 [Where problems could occur] It's a workaround only affects MTL platforms, and there is no "fixed commit" for this patch after v6.9-rc1. So, it should be safe and essential for MTL platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069380] Re: FPS of glxgear with fullscreen is too low on MTL platform
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-40.40.1~22.04.1 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- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2069380 Title: FPS of glxgear with fullscreen is too low on MTL platform Status in linux package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: [Impact] Run `glxgears -fullscreen` and the FPS can't stay at 60 FPS 298 frames in 5.0 seconds = 59.465 FPS 241 frames in 5.0 seconds = 48.193 FPS 261 frames in 5.0 seconds = 52.030 FPS 268 frames in 5.0 seconds = 53.596 FPS [Fix] Bisect the kernel and found a commit in v6.9-rc1 fixes the issue c08c364102d0 drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access [Test] 1. Run `glxgears -fullscreen` on MTL platforms 2. The FPS should be always around 60 [Where problems could occur] It's a workaround only affects MTL platforms, and there is no "fixed commit" for this patch after v6.9-rc1. So, it should be safe and essential for MTL platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069231] Re: [MTL] ACPI: PM: s2idle: Backport Linux ACPI s2idle patches to fix suspend/resume issue
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2 verification-needed-noble-linux-azure -- 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/2069231 Title: [MTL] ACPI: PM: s2idle: Backport Linux ACPI s2idle patches to fix suspend/resume issue Status in intel: Fix Released Status in Ubuntu: Confirmed Status in linux package in Ubuntu: New Status in The Noble Numbat: Fix Committed Status in linux source package in Noble: Fix Released Bug description: [Description] Framework (https://frame.work/) has root cause an artifact with their MTL laptops being unable to suspend and the reason is similar to many other MTL systems, their ACPI tables use the modern Microsoft UUIDs for Modern Standby. These patches (merged in 6.9) revolve this issue: - https://github.com/torvalds/linux/commit/073237281a508ac80ec025872ad7de50cfb5a28a - https://github.com/torvalds/linux/commit/68301ef471b63f25d6e6144a0820fea52257a34a Please backport them to Noble 6.8 kernel. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): MTL Date HW is expected at Canonical: Component(s): x86 [Software Information] Target Version: 24.04 Target Kernel: 6.8 Commit IDs: 073237281a508ac80ec025872ad7de50cfb5a28a 68301ef471b63f25d6e6144a0820fea52257a34a External Links: [Business Justification] OEM launch readiness and competitiveness [Testing guidance] NA [External ID] To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2069231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069231] Re: [MTL] ACPI: PM: s2idle: Backport Linux ACPI s2idle patches to fix suspend/resume issue
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2069231 Title: [MTL] ACPI: PM: s2idle: Backport Linux ACPI s2idle patches to fix suspend/resume issue Status in intel: Fix Released Status in Ubuntu: Confirmed Status in linux package in Ubuntu: New Status in The Noble Numbat: Fix Committed Status in linux source package in Noble: Fix Released Bug description: [Description] Framework (https://frame.work/) has root cause an artifact with their MTL laptops being unable to suspend and the reason is similar to many other MTL systems, their ACPI tables use the modern Microsoft UUIDs for Modern Standby. These patches (merged in 6.9) revolve this issue: - https://github.com/torvalds/linux/commit/073237281a508ac80ec025872ad7de50cfb5a28a - https://github.com/torvalds/linux/commit/68301ef471b63f25d6e6144a0820fea52257a34a Please backport them to Noble 6.8 kernel. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): MTL Date HW is expected at Canonical: Component(s): x86 [Software Information] Target Version: 24.04 Target Kernel: 6.8 Commit IDs: 073237281a508ac80ec025872ad7de50cfb5a28a 68301ef471b63f25d6e6144a0820fea52257a34a External Links: [Business Justification] OEM launch readiness and competitiveness [Testing guidance] NA [External ID] To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2069231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069231] Re: [MTL] ACPI: PM: s2idle: Backport Linux ACPI s2idle patches to fix suspend/resume issue
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-40.40.1~22.04.1 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- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2069231 Title: [MTL] ACPI: PM: s2idle: Backport Linux ACPI s2idle patches to fix suspend/resume issue Status in intel: Fix Released Status in Ubuntu: Confirmed Status in linux package in Ubuntu: New Status in The Noble Numbat: Fix Committed Status in linux source package in Noble: Fix Released Bug description: [Description] Framework (https://frame.work/) has root cause an artifact with their MTL laptops being unable to suspend and the reason is similar to many other MTL systems, their ACPI tables use the modern Microsoft UUIDs for Modern Standby. These patches (merged in 6.9) revolve this issue: - https://github.com/torvalds/linux/commit/073237281a508ac80ec025872ad7de50cfb5a28a - https://github.com/torvalds/linux/commit/68301ef471b63f25d6e6144a0820fea52257a34a Please backport them to Noble 6.8 kernel. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): MTL Date HW is expected at Canonical: Component(s): x86 [Software Information] Target Version: 24.04 Target Kernel: 6.8 Commit IDs: 073237281a508ac80ec025872ad7de50cfb5a28a 68301ef471b63f25d6e6144a0820fea52257a34a External Links: [Business Justification] OEM launch readiness and competitiveness [Testing guidance] NA [External ID] To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2069231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2067862] Re: Removing legacy virtio-pci devices causes kernel panic
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2067862 Title: Removing legacy virtio-pci devices causes kernel panic Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2067862 [Impact] If you detach a legacy virtio-pci device from a current Noble system, it will cause a null pointer dereference, and panic the system. This is an issue if you force noble to use legacy virtio-pci devices, or run noble on very old hypervisors that only support legacy virtio-pci devices, e.g. trusty and older. BUG: kernel NULL pointer dereference, address: ... CPU: 2 PID: 358 Comm: kworker/u8:3 Kdump: loaded Not tainted 6.8.0-31-generic #31-Ubuntu Workqueue: kacpi_hotplug acpi_hotplug_work_fn RIP: 0010:0x0 ... Call Trace: ? show_regs+0x6d/0x80 ? __die+0x24/0x80 ? page_fault_oops+0x99/0x1b0 ? do_user_addr_fault+0x2ee/0x6b0 ? exc_page_fault+0x83/0x1b0 ? asm_exc_page_fault+0x27/0x30 vp_del_vqs+0x6e/0x2a0 remove_vq_common+0x166/0x1a0 virtnet_remove+0x61/0x80 virtio_dev_remove+0x3f/0xc0 device_remove+0x40/0x80 device_release_driver_internal+0x20b/0x270 device_release_driver+0x12/0x20 bus_remove_device+0xcb/0x140 device_del+0x161/0x3e0 ? pci_bus_generic_read_dev_vendor_id+0x2c/0x1a0 device_unregister+0x17/0x60 unregister_virtio_device+0x16/0x40 virtio_pci_remove+0x43/0xa0 pci_device_remove+0x36/0xb0 device_remove+0x40/0x80 device_release_driver_internal+0x20b/0x270 device_release_driver+0x12/0x20 pci_stop_bus_device+0x7a/0xb0 pci_stop_and_remove_bus_device+0x12/0x30 disable_slot+0x4f/0xa0 acpiphp_disable_and_eject_slot+0x1c/0xa0 hotplug_event+0x11b/0x280 ? __pfx_acpiphp_hotplug_notify+0x10/0x10 acpiphp_hotplug_notify+0x27/0x70 acpi_device_hotplug+0xb6/0x300 acpi_hotplug_work_fn+0x1e/0x40 process_one_work+0x16c/0x350 worker_thread+0x306/0x440 ? _raw_spin_lock_irqsave+0xe/0x20 ? __pfx_worker_thread+0x10/0x10 kthread+0xef/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x44/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 The issue was introduced in: commit fd27ef6b44bec26915c5b2b22c13856d9f0ba17a Author: Feng Liu Date: Tue Dec 19 11:32:40 2023 +0200 Subject: virtio-pci: Introduce admin virtqueue Link: https://github.com/torvalds/linux/commit/fd27ef6b44bec26915c5b2b22c13856d9f0ba17a Modern virtio-pci devices are not affected. If the device is a legacy virtio device, the is_avq function pointer is not assigned in the virtio_pci_device structure of the legacy virtio device, resulting in a NULL pointer dereference when the code calls if (vp_dev->is_avq(vdev, vq->index)). There is no workaround. If you are affected, then not detaching devices for the time being is the only solution. [Fix] This was fixed in 6.9-rc1 by: commit c8fae27d141a32a1624d0d0d5419d94252824498 From: Li Zhang Date: Sat, 16 Mar 2024 13:25:54 +0800 Subject: virtio-pci: Check if is_avq is NULL Link: https://github.com/torvalds/linux/commit/c8fae27d141a32a1624d0d0d5419d94252824498 This is a clean cherry pick to noble. The commit just adds a basic NULL pointer check before it dereferences the pointer. [Testcase] Start a fresh Noble VM. Edit the grub kernel command line: 1) sudo vim /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="virtio_pci.force_legacy=1" 2) sudo update-grub 3) sudo reboot Outside the VM, on the host: $ qemu-img create -f qcow2 /root/share-device.qcow2 2G $ cat >> share-device.xml << EOF disk type='file' device='disk'> EOF $ sudo -s # virsh attach-device noble-test share-device.xml --config --live # virsh detach-device noble-test share-device.xml --config --live A kernel panic should occur. There is a test kernel available in: https://launchpad.net/~mruffell/+archive/ubuntu/lp2067862-test If you install it, the panic should no longer occur. [Where problems could occur]
[Kernel-packages] [Bug 2067862] Re: Removing legacy virtio-pci devices causes kernel panic
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2 verification-needed-noble-linux-azure -- 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/2067862 Title: Removing legacy virtio-pci devices causes kernel panic Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2067862 [Impact] If you detach a legacy virtio-pci device from a current Noble system, it will cause a null pointer dereference, and panic the system. This is an issue if you force noble to use legacy virtio-pci devices, or run noble on very old hypervisors that only support legacy virtio-pci devices, e.g. trusty and older. BUG: kernel NULL pointer dereference, address: ... CPU: 2 PID: 358 Comm: kworker/u8:3 Kdump: loaded Not tainted 6.8.0-31-generic #31-Ubuntu Workqueue: kacpi_hotplug acpi_hotplug_work_fn RIP: 0010:0x0 ... Call Trace: ? show_regs+0x6d/0x80 ? __die+0x24/0x80 ? page_fault_oops+0x99/0x1b0 ? do_user_addr_fault+0x2ee/0x6b0 ? exc_page_fault+0x83/0x1b0 ? asm_exc_page_fault+0x27/0x30 vp_del_vqs+0x6e/0x2a0 remove_vq_common+0x166/0x1a0 virtnet_remove+0x61/0x80 virtio_dev_remove+0x3f/0xc0 device_remove+0x40/0x80 device_release_driver_internal+0x20b/0x270 device_release_driver+0x12/0x20 bus_remove_device+0xcb/0x140 device_del+0x161/0x3e0 ? pci_bus_generic_read_dev_vendor_id+0x2c/0x1a0 device_unregister+0x17/0x60 unregister_virtio_device+0x16/0x40 virtio_pci_remove+0x43/0xa0 pci_device_remove+0x36/0xb0 device_remove+0x40/0x80 device_release_driver_internal+0x20b/0x270 device_release_driver+0x12/0x20 pci_stop_bus_device+0x7a/0xb0 pci_stop_and_remove_bus_device+0x12/0x30 disable_slot+0x4f/0xa0 acpiphp_disable_and_eject_slot+0x1c/0xa0 hotplug_event+0x11b/0x280 ? __pfx_acpiphp_hotplug_notify+0x10/0x10 acpiphp_hotplug_notify+0x27/0x70 acpi_device_hotplug+0xb6/0x300 acpi_hotplug_work_fn+0x1e/0x40 process_one_work+0x16c/0x350 worker_thread+0x306/0x440 ? _raw_spin_lock_irqsave+0xe/0x20 ? __pfx_worker_thread+0x10/0x10 kthread+0xef/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x44/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 The issue was introduced in: commit fd27ef6b44bec26915c5b2b22c13856d9f0ba17a Author: Feng Liu Date: Tue Dec 19 11:32:40 2023 +0200 Subject: virtio-pci: Introduce admin virtqueue Link: https://github.com/torvalds/linux/commit/fd27ef6b44bec26915c5b2b22c13856d9f0ba17a Modern virtio-pci devices are not affected. If the device is a legacy virtio device, the is_avq function pointer is not assigned in the virtio_pci_device structure of the legacy virtio device, resulting in a NULL pointer dereference when the code calls if (vp_dev->is_avq(vdev, vq->index)). There is no workaround. If you are affected, then not detaching devices for the time being is the only solution. [Fix] This was fixed in 6.9-rc1 by: commit c8fae27d141a32a1624d0d0d5419d94252824498 From: Li Zhang Date: Sat, 16 Mar 2024 13:25:54 +0800 Subject: virtio-pci: Check if is_avq is NULL Link: https://github.com/torvalds/linux/commit/c8fae27d141a32a1624d0d0d5419d94252824498 This is a clean cherry pick to noble. The commit just adds a basic NULL pointer check before it dereferences the pointer. [Testcase] Start a fresh Noble VM. Edit the grub kernel command line: 1) sudo vim /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="virtio_pci.force_legacy=1" 2) sudo update-grub 3) sudo reboot Outside the VM, on the host: $ qemu-img create -f qcow2 /root/share-device.qcow2 2G $ cat >> share-device.xml << EOF disk type='file' device='disk'> EOF $ sudo -s # virsh attach-device noble-test share-device.xml --config --live # virsh detach-device noble-test share-device.xml --config --live A kernel panic should occur. There is a test kernel available in: https://launchpad.net/~mruffell/+archive/ubuntu/lp2067862-test If you install it, the panic should no longer occur. [Where problems could occur]
[Kernel-packages] [Bug 2067862] Re: Removing legacy virtio-pci devices causes kernel panic
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-40.40.1~22.04.1 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- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2067862 Title: Removing legacy virtio-pci devices causes kernel panic Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2067862 [Impact] If you detach a legacy virtio-pci device from a current Noble system, it will cause a null pointer dereference, and panic the system. This is an issue if you force noble to use legacy virtio-pci devices, or run noble on very old hypervisors that only support legacy virtio-pci devices, e.g. trusty and older. BUG: kernel NULL pointer dereference, address: ... CPU: 2 PID: 358 Comm: kworker/u8:3 Kdump: loaded Not tainted 6.8.0-31-generic #31-Ubuntu Workqueue: kacpi_hotplug acpi_hotplug_work_fn RIP: 0010:0x0 ... Call Trace: ? show_regs+0x6d/0x80 ? __die+0x24/0x80 ? page_fault_oops+0x99/0x1b0 ? do_user_addr_fault+0x2ee/0x6b0 ? exc_page_fault+0x83/0x1b0 ? asm_exc_page_fault+0x27/0x30 vp_del_vqs+0x6e/0x2a0 remove_vq_common+0x166/0x1a0 virtnet_remove+0x61/0x80 virtio_dev_remove+0x3f/0xc0 device_remove+0x40/0x80 device_release_driver_internal+0x20b/0x270 device_release_driver+0x12/0x20 bus_remove_device+0xcb/0x140 device_del+0x161/0x3e0 ? pci_bus_generic_read_dev_vendor_id+0x2c/0x1a0 device_unregister+0x17/0x60 unregister_virtio_device+0x16/0x40 virtio_pci_remove+0x43/0xa0 pci_device_remove+0x36/0xb0 device_remove+0x40/0x80 device_release_driver_internal+0x20b/0x270 device_release_driver+0x12/0x20 pci_stop_bus_device+0x7a/0xb0 pci_stop_and_remove_bus_device+0x12/0x30 disable_slot+0x4f/0xa0 acpiphp_disable_and_eject_slot+0x1c/0xa0 hotplug_event+0x11b/0x280 ? __pfx_acpiphp_hotplug_notify+0x10/0x10 acpiphp_hotplug_notify+0x27/0x70 acpi_device_hotplug+0xb6/0x300 acpi_hotplug_work_fn+0x1e/0x40 process_one_work+0x16c/0x350 worker_thread+0x306/0x440 ? _raw_spin_lock_irqsave+0xe/0x20 ? __pfx_worker_thread+0x10/0x10 kthread+0xef/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x44/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 The issue was introduced in: commit fd27ef6b44bec26915c5b2b22c13856d9f0ba17a Author: Feng Liu Date: Tue Dec 19 11:32:40 2023 +0200 Subject: virtio-pci: Introduce admin virtqueue Link: https://github.com/torvalds/linux/commit/fd27ef6b44bec26915c5b2b22c13856d9f0ba17a Modern virtio-pci devices are not affected. If the device is a legacy virtio device, the is_avq function pointer is not assigned in the virtio_pci_device structure of the legacy virtio device, resulting in a NULL pointer dereference when the code calls if (vp_dev->is_avq(vdev, vq->index)). There is no workaround. If you are affected, then not detaching devices for the time being is the only solution. [Fix] This was fixed in 6.9-rc1 by: commit c8fae27d141a32a1624d0d0d5419d94252824498 From: Li Zhang Date: Sat, 16 Mar 2024 13:25:54 +0800 Subject: virtio-pci: Check if is_avq is NULL Link: https://github.com/torvalds/linux/commit/c8fae27d141a32a1624d0d0d5419d94252824498 This is a clean cherry pick to noble. The commit just adds a basic NULL pointer check before it dereferences the pointer. [Testcase] Start a fresh Noble VM. Edit the grub kernel command line: 1) sudo vim /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="virtio_pci.force_legacy=1" 2) sudo update-grub 3) sudo reboot Outside the VM, on the host: $ qemu-img create -f qcow2 /root/share-device.qcow2 2G $ cat >> share-device.xml << EOF disk type='file' device='disk'> EOF $ sudo -s # virsh attach-device noble-test share-device.xml --config --live # virsh detach-device noble-test share-device.xml --config --live A kernel panic should occur. There is a test kernel available in: https://launchpad.net/~mruffell/+archive/ubuntu/lp2067862-test If you install it, the panic should no longer occur
[Kernel-packages] [Bug 2067669] Re: Mute/mic LEDs no function on ProBook 440/460 G11
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2 verification-needed-noble-linux-azure -- 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/2067669 Title: Mute/mic LEDs no function on ProBook 440/460 G11 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 Released Status in linux source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Won't Fix Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Won't Fix Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook 440/460 G11 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2067669] Re: Mute/mic LEDs no function on ProBook 440/460 G11
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2067669 Title: Mute/mic LEDs no function on ProBook 440/460 G11 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 Released Status in linux source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Won't Fix Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Won't Fix Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook 440/460 G11 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2070158] Re: RFIM and SAGV Linux Support for G10 models
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-40.40.1~22.04.1 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- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2070158 Title: RFIM and SAGV Linux Support for G10 models Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2070158 [Impact] This is a feature request from HP, RFIM is for frequency, SAGV is for voltage. They are used as dynamic switching to reduce RF noise. RFIM is already supported in the kernel, this patchset adds the SAGV feature. [Fix] Cherry-pick 6 commits from mainline kernel [Test] Enable the SAGV from the BIOS, booting with the patched kernel, after booting up, run 'systemctl status dtt.service', we will get: service is enabled and service is running run 'cat /sys/kernel/debug/dri/:00:02.0/i915_sagv_status', we will get: SAGV available: Yes SAGV status: enabled [Where problems could occur] Because the fix is for i915, it is likely introduce regression on graphic, but this possibility is very low. These 6 commits are merged to mainline kernel from v6.10-rc1, so far there is no regression reported on them. And we tested the patched kernel on different Intel machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2070158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069380] Re: FPS of glxgear with fullscreen is too low on MTL platform
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2 verification-needed-noble-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2069380 Title: FPS of glxgear with fullscreen is too low on MTL platform Status in linux package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: [Impact] Run `glxgears -fullscreen` and the FPS can't stay at 60 FPS 298 frames in 5.0 seconds = 59.465 FPS 241 frames in 5.0 seconds = 48.193 FPS 261 frames in 5.0 seconds = 52.030 FPS 268 frames in 5.0 seconds = 53.596 FPS [Fix] Bisect the kernel and found a commit in v6.9-rc1 fixes the issue c08c364102d0 drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access [Test] 1. Run `glxgears -fullscreen` on MTL platforms 2. The FPS should be always around 60 [Where problems could occur] It's a workaround only affects MTL platforms, and there is no "fixed commit" for this patch after v6.9-rc1. So, it should be safe and essential for MTL platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2067669] Re: Mute/mic LEDs no function on ProBook 440/460 G11
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-40.40.1~22.04.1 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- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2067669 Title: Mute/mic LEDs no function on ProBook 440/460 G11 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 Released Status in linux source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Won't Fix Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Won't Fix Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook 440/460 G11 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2070042] Re: noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-40.40.1~22.04.1 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- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2070042 Title: noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Released Bug description: The DEP-8 ubuntu-regression-suite of tests is failing in setup because fakeroot is not installed. This likely was previously included in build-essential. autotest.client.shared.error.CmdError: Command failed, rc=127, Command returned non-zero exit status * Command: fakeroot debian/rules clean Exit status: 127 Duration: 0.0017809867858886719 stderr: /bin/bash: line 1: fakeroot: command not found Fix will be to update the dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2067364] Re: failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10
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-noble-linux-raspi' to 'verification-done-noble-
linux-raspi'. If the problem still exists, change the tag 'verification-
needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'.
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-noble-linux-raspi-v2
verification-needed-noble-linux-raspi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2067364
Title:
failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace
intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host
failed: -110
Status in ipu6-drivers package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-6.10 package in Ubuntu:
Invalid
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in ipu6-drivers source package in Noble:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.10 source package in Noble:
In Progress
Status in linux-oem-6.8 source package in Noble:
Fix Released
Status in ipu6-drivers source package in Oracular:
Fix Released
Status in linux source package in Oracular:
Triaged
Status in linux-oem-6.10 source package in Oracular:
Invalid
Status in linux-oem-6.8 source package in Oracular:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2067364
[Impact]
With IVSC switched to in-tree driver since 6.8 kernels in bug 2061747,
it's still suffering from various problems that blocks camera driver
stack being loaded correctly.
The ivsc-ace driver may fail to communicate with the underlying firmware with
error messages:
```
ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to
host failed: -110
```
This happens after warm reboots. In addition, ivs may block suspend resume,
too.
[Fix]
These symptoms are to be addressed by upstream reviewing patchsets:
* https://lore.kernel.org/all/20240624014223.4171341-1-wentong...@intel.com/
* https://lore.kernel.org/all/20240607132547.2820515-1-wentong...@intel.com/
* commit 9b5e045029d8 ("mei: vsc: Don't stop/restart mei device during system
suspend/resume") from v6.10-rc4
[Test Case]
The proposed kernel should have been built along with the updated
ipu6-drivers dkms. To verify ipu6-drivers alone, one will need
experimental kernels from https://launchpad.net/~canonical-hwe-
team/+archive/ubuntu/intermediate-kernel.
Here are steps for verifying kernels from -proposed pocket:
1. test camera after rebooting into a proposed kernel,
2. run suspend/resume stress test plan.
3. verify camera still working
[Where problems could occur]
These fixes are quite limited to ipu6/ivsc platforms, and affected no
power-consumption or other notisible problem.
[Other Info]
While some of the fixes are still under upstream review, meaning
they're not yet available in any kernel release, linux-
unstable/oracular/noble and oem-6.8/6.1x will be nominated for fix.
== original bug report ==
With IVSC switched to in-tree driver since 6.8 kernels in bug 2061747,
it's still suffering from various problems that blocks camera driver
stack being loaded correctly.
The ivsc-ace driver may fail to communicate with the underlying
firmware with error messages:
ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch
camera to host failed: -110
This happens after warm reboots. In addition, ivs may block suspend
resume, too.
These symptoms are to be addressed by upstream reviewing patchsets:
* https://lore.kernel.org/all/20240624014223.4171341-1-wentong...@intel.com/
* https://lore.kernel.org/all/20240607132547.2820515-1-wentong...@intel.com/
* commit 9b5e045029d8 ("mei: vsc: Don't stop/restart mei device during system
suspend/resume") from v6.10-rc4
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:ubuntu 1798 F pipewire
/dev/snd/controlC0: ubuntu 1798 F pipewire
ubuntu 1801 F wireplumber
CasperMD5CheckMismatches: ./.disk/casper-uuid-generic ./casper/initrd
./casper/minimal.standard.live.hotfix.squashfs
./casper/minimal.standard.hotfix.squashfs ./casper/minimal.hotfix.squashfs
./boot/grub/grub.cfg
CasperMD5CheckResult: fail
DistributionChannelDescriptor:
# This is the di
[Kernel-packages] [Bug 2067364] Re: failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2
verification-needed-noble-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2067364
Title:
failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace
intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host
failed: -110
Status in ipu6-drivers package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-6.10 package in Ubuntu:
Invalid
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in ipu6-drivers source package in Noble:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.10 source package in Noble:
In Progress
Status in linux-oem-6.8 source package in Noble:
Fix Released
Status in ipu6-drivers source package in Oracular:
Fix Released
Status in linux source package in Oracular:
Triaged
Status in linux-oem-6.10 source package in Oracular:
Invalid
Status in linux-oem-6.8 source package in Oracular:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2067364
[Impact]
With IVSC switched to in-tree driver since 6.8 kernels in bug 2061747,
it's still suffering from various problems that blocks camera driver
stack being loaded correctly.
The ivsc-ace driver may fail to communicate with the underlying firmware with
error messages:
```
ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to
host failed: -110
```
This happens after warm reboots. In addition, ivs may block suspend resume,
too.
[Fix]
These symptoms are to be addressed by upstream reviewing patchsets:
* https://lore.kernel.org/all/20240624014223.4171341-1-wentong...@intel.com/
* https://lore.kernel.org/all/20240607132547.2820515-1-wentong...@intel.com/
* commit 9b5e045029d8 ("mei: vsc: Don't stop/restart mei device during system
suspend/resume") from v6.10-rc4
[Test Case]
The proposed kernel should have been built along with the updated
ipu6-drivers dkms. To verify ipu6-drivers alone, one will need
experimental kernels from https://launchpad.net/~canonical-hwe-
team/+archive/ubuntu/intermediate-kernel.
Here are steps for verifying kernels from -proposed pocket:
1. test camera after rebooting into a proposed kernel,
2. run suspend/resume stress test plan.
3. verify camera still working
[Where problems could occur]
These fixes are quite limited to ipu6/ivsc platforms, and affected no
power-consumption or other notisible problem.
[Other Info]
While some of the fixes are still under upstream review, meaning
they're not yet available in any kernel release, linux-
unstable/oracular/noble and oem-6.8/6.1x will be nominated for fix.
== original bug report ==
With IVSC switched to in-tree driver since 6.8 kernels in bug 2061747,
it's still suffering from various problems that blocks camera driver
stack being loaded correctly.
The ivsc-ace driver may fail to communicate with the underlying
firmware with error messages:
ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch
camera to host failed: -110
This happens after warm reboots. In addition, ivs may block suspend
resume, too.
These symptoms are to be addressed by upstream reviewing patchsets:
* https://lore.kernel.org/all/20240624014223.4171341-1-wentong...@intel.com/
* https://lore.kernel.org/all/20240607132547.2820515-1-wentong...@intel.com/
* commit 9b5e045029d8 ("mei: vsc: Don't stop/restart mei device during system
suspend/resume") from v6.10-rc4
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:ubuntu 1798 F pipewire
/dev/snd/controlC0: ubuntu 1798 F pipewire
ubuntu 1801 F wireplumber
CasperMD5CheckMismatches: ./.disk/casper-uuid-generic ./casper/initrd
./casper/minimal.standard.live.hotfix.squashfs
./casper/minimal.standard.hotfix.squashfs ./casper/minimal.hotfix.squashfs
./boot/grub/grub.cfg
CasperMD5CheckResult: fail
DistributionChannelDescriptor:
# This is the di
[Kernel-packages] [Bug 2067364] Re: failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-40.40.1~22.04.1 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-
riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8'
to 'verification-failed-jammy-linux-riscv-6.8'.
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-riscv-6.8-v2
verification-needed-jammy-linux-riscv-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2067364
Title:
failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace
intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host
failed: -110
Status in ipu6-drivers package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-6.10 package in Ubuntu:
Invalid
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in ipu6-drivers source package in Noble:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.10 source package in Noble:
In Progress
Status in linux-oem-6.8 source package in Noble:
Fix Released
Status in ipu6-drivers source package in Oracular:
Fix Released
Status in linux source package in Oracular:
Triaged
Status in linux-oem-6.10 source package in Oracular:
Invalid
Status in linux-oem-6.8 source package in Oracular:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2067364
[Impact]
With IVSC switched to in-tree driver since 6.8 kernels in bug 2061747,
it's still suffering from various problems that blocks camera driver
stack being loaded correctly.
The ivsc-ace driver may fail to communicate with the underlying firmware with
error messages:
```
ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to
host failed: -110
```
This happens after warm reboots. In addition, ivs may block suspend resume,
too.
[Fix]
These symptoms are to be addressed by upstream reviewing patchsets:
* https://lore.kernel.org/all/20240624014223.4171341-1-wentong...@intel.com/
* https://lore.kernel.org/all/20240607132547.2820515-1-wentong...@intel.com/
* commit 9b5e045029d8 ("mei: vsc: Don't stop/restart mei device during system
suspend/resume") from v6.10-rc4
[Test Case]
The proposed kernel should have been built along with the updated
ipu6-drivers dkms. To verify ipu6-drivers alone, one will need
experimental kernels from https://launchpad.net/~canonical-hwe-
team/+archive/ubuntu/intermediate-kernel.
Here are steps for verifying kernels from -proposed pocket:
1. test camera after rebooting into a proposed kernel,
2. run suspend/resume stress test plan.
3. verify camera still working
[Where problems could occur]
These fixes are quite limited to ipu6/ivsc platforms, and affected no
power-consumption or other notisible problem.
[Other Info]
While some of the fixes are still under upstream review, meaning
they're not yet available in any kernel release, linux-
unstable/oracular/noble and oem-6.8/6.1x will be nominated for fix.
== original bug report ==
With IVSC switched to in-tree driver since 6.8 kernels in bug 2061747,
it's still suffering from various problems that blocks camera driver
stack being loaded correctly.
The ivsc-ace driver may fail to communicate with the underlying
firmware with error messages:
ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch
camera to host failed: -110
This happens after warm reboots. In addition, ivs may block suspend
resume, too.
These symptoms are to be addressed by upstream reviewing patchsets:
* https://lore.kernel.org/all/20240624014223.4171341-1-wentong...@intel.com/
* https://lore.kernel.org/all/20240607132547.2820515-1-wentong...@intel.com/
* commit 9b5e045029d8 ("mei: vsc: Don't stop/restart mei device during system
suspend/resume") from v6.10-rc4
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:ubuntu 1798 F pipewire
/dev/snd/controlC0: ubuntu 1798 F pipewire
ubuntu 1801 F wireplumber
CasperMD5CheckMismatches: ./.disk/casper-uuid-generic ./casper/initrd
./casper/minimal.standard.live.hotfix.squashfs
./casper/minimal.standard.hotfix.squashfs ./casper/minimal.hotfix.squashfs
./boot/grub/grub.cfg
CasperMD5CheckResult: fail
DistributionCh
[Kernel-packages] [Bug 2066233] Re: amdgpu hangs on DCN 3.5 at bootup: RIP: 0010:dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu]
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2
verification-needed-noble-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2066233
Title:
amdgpu hangs on DCN 3.5 at bootup: RIP:
0010:dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu]
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.8 source package in Noble:
Fix Released
Status in linux source package in Oracular:
Fix Released
Status in linux-oem-6.8 source package in Oracular:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2066233
[Impact]
Newer VBIOS on DCN 3.5 bumped the version of IntegratedInfo table from
2.2 to 2.3. This version uses same structure. Version 2.3 is missing
from the construct_integrated_info() parser, so it leads to NULL
pointer dereference.
```
Call Trace:
? show_regs+0x72/0x90
? __die+0x25/0x80
? page_fault_oops+0x154/0x4c0
? ttm_bo_kmap+0x11d/0x310 [ttm]
? dma_resv_wait_timeout+0x48/0xe0
? do_user_addr_fault+0x30e/0x6e0
? exc_page_fault+0x84/0x1b0
? asm_exc_page_fault+0x27/0x30
? dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu]
? dcn35_clk_mgr_construct+0x15a/0x2210 [amdgpu]
? dcn35_hwseq_create+0x23/0x470 [amdgpu]
```
[Fix]
Fix landed to upstream v6.9-rc7: 9a35d205f466 ("drm/amd/display: Atom
Integrated System Info v2_2 for DCN35")
[Test Case]
AMDGPU should then be initialized successfully without NULL pointer
deref dump at boot.
[Where problems could occur]
No. New hardware revision with same data only.
[Other Info]
While this has been landed to v6.9-rc7, expect every kernel version
older than that with planned support to the new VBIOS update should be
fixed. So far linux/noble and linux-oem-6.8/noble are nominated by
chip vendor.
== original bug report ==
Newer VBIOS on DCN 3.5 bumped the version of IntegratedInfo table from
2.2 to 2.3. This version uses same structure. Version 2.3 is missing
from the construct_integrated_info() parser, so it leads to NULL
pointer dereference.
[Thu May 9 18:02:38 2024] Call Trace:
[Thu May 9 18:02:38 2024]
[Thu May 9 18:02:38 2024] ? show_regs+0x72/0x90
[Thu May 9 18:02:38 2024] ? __die+0x25/0x80
[Thu May 9 18:02:38 2024] ? page_fault_oops+0x154/0x4c0
[Thu May 9 18:02:38 2024] ? ttm_bo_kmap+0x11d/0x310 [ttm]
[Thu May 9 18:02:38 2024] ? dma_resv_wait_timeout+0x48/0xe0
[Thu May 9 18:02:38 2024] ? do_user_addr_fault+0x30e/0x6e0
[Thu May 9 18:02:38 2024] ? exc_page_fault+0x84/0x1b0
[Thu May 9 18:02:38 2024] ? asm_exc_page_fault+0x27/0x30
[Thu May 9 18:02:38 2024] ? dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu]
[Thu May 9 18:02:38 2024] ? dcn35_clk_mgr_construct+0x15a/0x2210 [amdgpu]
[Thu May 9 18:02:38 2024] ? dcn35_hwseq_create+0x23/0x470 [amdgpu]
...
Fix landed to upstream v6.9-rc7: 9a35d205f466 ("drm/amd/display: Atom
Integrated System Info v2_2 for DCN35")
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2066233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2066233] Re: amdgpu hangs on DCN 3.5 at bootup: RIP: 0010:dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu]
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10
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-noble-linux-raspi' to 'verification-done-noble-
linux-raspi'. If the problem still exists, change the tag 'verification-
needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'.
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-noble-linux-raspi-v2
verification-needed-noble-linux-raspi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2066233
Title:
amdgpu hangs on DCN 3.5 at bootup: RIP:
0010:dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu]
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.8 source package in Noble:
Fix Released
Status in linux source package in Oracular:
Fix Released
Status in linux-oem-6.8 source package in Oracular:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2066233
[Impact]
Newer VBIOS on DCN 3.5 bumped the version of IntegratedInfo table from
2.2 to 2.3. This version uses same structure. Version 2.3 is missing
from the construct_integrated_info() parser, so it leads to NULL
pointer dereference.
```
Call Trace:
? show_regs+0x72/0x90
? __die+0x25/0x80
? page_fault_oops+0x154/0x4c0
? ttm_bo_kmap+0x11d/0x310 [ttm]
? dma_resv_wait_timeout+0x48/0xe0
? do_user_addr_fault+0x30e/0x6e0
? exc_page_fault+0x84/0x1b0
? asm_exc_page_fault+0x27/0x30
? dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu]
? dcn35_clk_mgr_construct+0x15a/0x2210 [amdgpu]
? dcn35_hwseq_create+0x23/0x470 [amdgpu]
```
[Fix]
Fix landed to upstream v6.9-rc7: 9a35d205f466 ("drm/amd/display: Atom
Integrated System Info v2_2 for DCN35")
[Test Case]
AMDGPU should then be initialized successfully without NULL pointer
deref dump at boot.
[Where problems could occur]
No. New hardware revision with same data only.
[Other Info]
While this has been landed to v6.9-rc7, expect every kernel version
older than that with planned support to the new VBIOS update should be
fixed. So far linux/noble and linux-oem-6.8/noble are nominated by
chip vendor.
== original bug report ==
Newer VBIOS on DCN 3.5 bumped the version of IntegratedInfo table from
2.2 to 2.3. This version uses same structure. Version 2.3 is missing
from the construct_integrated_info() parser, so it leads to NULL
pointer dereference.
[Thu May 9 18:02:38 2024] Call Trace:
[Thu May 9 18:02:38 2024]
[Thu May 9 18:02:38 2024] ? show_regs+0x72/0x90
[Thu May 9 18:02:38 2024] ? __die+0x25/0x80
[Thu May 9 18:02:38 2024] ? page_fault_oops+0x154/0x4c0
[Thu May 9 18:02:38 2024] ? ttm_bo_kmap+0x11d/0x310 [ttm]
[Thu May 9 18:02:38 2024] ? dma_resv_wait_timeout+0x48/0xe0
[Thu May 9 18:02:38 2024] ? do_user_addr_fault+0x30e/0x6e0
[Thu May 9 18:02:38 2024] ? exc_page_fault+0x84/0x1b0
[Thu May 9 18:02:38 2024] ? asm_exc_page_fault+0x27/0x30
[Thu May 9 18:02:38 2024] ? dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu]
[Thu May 9 18:02:38 2024] ? dcn35_clk_mgr_construct+0x15a/0x2210 [amdgpu]
[Thu May 9 18:02:38 2024] ? dcn35_hwseq_create+0x23/0x470 [amdgpu]
...
Fix landed to upstream v6.9-rc7: 9a35d205f466 ("drm/amd/display: Atom
Integrated System Info v2_2 for DCN35")
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2066233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2066233] Re: amdgpu hangs on DCN 3.5 at bootup: RIP: 0010:dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu]
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-40.40.1~22.04.1 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-
riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8'
to 'verification-failed-jammy-linux-riscv-6.8'.
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-riscv-6.8-v2
verification-needed-jammy-linux-riscv-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2066233
Title:
amdgpu hangs on DCN 3.5 at bootup: RIP:
0010:dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu]
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.8 source package in Noble:
Fix Released
Status in linux source package in Oracular:
Fix Released
Status in linux-oem-6.8 source package in Oracular:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2066233
[Impact]
Newer VBIOS on DCN 3.5 bumped the version of IntegratedInfo table from
2.2 to 2.3. This version uses same structure. Version 2.3 is missing
from the construct_integrated_info() parser, so it leads to NULL
pointer dereference.
```
Call Trace:
? show_regs+0x72/0x90
? __die+0x25/0x80
? page_fault_oops+0x154/0x4c0
? ttm_bo_kmap+0x11d/0x310 [ttm]
? dma_resv_wait_timeout+0x48/0xe0
? do_user_addr_fault+0x30e/0x6e0
? exc_page_fault+0x84/0x1b0
? asm_exc_page_fault+0x27/0x30
? dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu]
? dcn35_clk_mgr_construct+0x15a/0x2210 [amdgpu]
? dcn35_hwseq_create+0x23/0x470 [amdgpu]
```
[Fix]
Fix landed to upstream v6.9-rc7: 9a35d205f466 ("drm/amd/display: Atom
Integrated System Info v2_2 for DCN35")
[Test Case]
AMDGPU should then be initialized successfully without NULL pointer
deref dump at boot.
[Where problems could occur]
No. New hardware revision with same data only.
[Other Info]
While this has been landed to v6.9-rc7, expect every kernel version
older than that with planned support to the new VBIOS update should be
fixed. So far linux/noble and linux-oem-6.8/noble are nominated by
chip vendor.
== original bug report ==
Newer VBIOS on DCN 3.5 bumped the version of IntegratedInfo table from
2.2 to 2.3. This version uses same structure. Version 2.3 is missing
from the construct_integrated_info() parser, so it leads to NULL
pointer dereference.
[Thu May 9 18:02:38 2024] Call Trace:
[Thu May 9 18:02:38 2024]
[Thu May 9 18:02:38 2024] ? show_regs+0x72/0x90
[Thu May 9 18:02:38 2024] ? __die+0x25/0x80
[Thu May 9 18:02:38 2024] ? page_fault_oops+0x154/0x4c0
[Thu May 9 18:02:38 2024] ? ttm_bo_kmap+0x11d/0x310 [ttm]
[Thu May 9 18:02:38 2024] ? dma_resv_wait_timeout+0x48/0xe0
[Thu May 9 18:02:38 2024] ? do_user_addr_fault+0x30e/0x6e0
[Thu May 9 18:02:38 2024] ? exc_page_fault+0x84/0x1b0
[Thu May 9 18:02:38 2024] ? asm_exc_page_fault+0x27/0x30
[Thu May 9 18:02:38 2024] ? dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu]
[Thu May 9 18:02:38 2024] ? dcn35_clk_mgr_construct+0x15a/0x2210 [amdgpu]
[Thu May 9 18:02:38 2024] ? dcn35_hwseq_create+0x23/0x470 [amdgpu]
...
Fix landed to upstream v6.9-rc7: 9a35d205f466 ("drm/amd/display: Atom
Integrated System Info v2_2 for DCN35")
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2066233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2065128] Re: rtw89_8852ce - Lost WIFI connection after suspend
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2 verification-needed-noble-linux-azure -- 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/2065128 Title: rtw89_8852ce - Lost WIFI connection after suspend Status in HWE Next: New 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 Released Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Status in linux source package in Oracular: Fix Released Status in linux-oem-6.5 source package in Oracular: Invalid Bug description: [Impact] Lost WIFI connection after suspend. While this happen, the WIFI module couldn't detect any AP, re-enable module and reboot OS without any help. There only way to get it back is cold boot. [Fix] Realtek provides a fix which has been included in rtw maintainer's tree https://lore.kernel.org/linux-wireless/20240426061200.44262-1-pks...@realtek.com/T/#mbfcb37c2fdc85ba280743f2b07fbf1fa8719eb79 The commits has been included in v6.10-rc1 4e5957101d42 wifi: rtw89: 8852c: refine power sequence to imporve power consumption 535c045da60f wifi: rtw89: reset AFEDIG register in power off sequence [Test case] 1. Boot into OS 2. open terminal to keep checking dmesg or check the wifi connection from GUI 3. suspend/resume multiple times 4. check the wifi connection [Where problems could occur] What the 2 commits should be safe and won't introduce any regression. 1. Reset AFEDIG register before BB reset in power off sequence 2. Adjust power and clock parameters To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2065128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2065128] Re: rtw89_8852ce - Lost WIFI connection after suspend
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2065128 Title: rtw89_8852ce - Lost WIFI connection after suspend Status in HWE Next: New 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 Released Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Status in linux source package in Oracular: Fix Released Status in linux-oem-6.5 source package in Oracular: Invalid Bug description: [Impact] Lost WIFI connection after suspend. While this happen, the WIFI module couldn't detect any AP, re-enable module and reboot OS without any help. There only way to get it back is cold boot. [Fix] Realtek provides a fix which has been included in rtw maintainer's tree https://lore.kernel.org/linux-wireless/20240426061200.44262-1-pks...@realtek.com/T/#mbfcb37c2fdc85ba280743f2b07fbf1fa8719eb79 The commits has been included in v6.10-rc1 4e5957101d42 wifi: rtw89: 8852c: refine power sequence to imporve power consumption 535c045da60f wifi: rtw89: reset AFEDIG register in power off sequence [Test case] 1. Boot into OS 2. open terminal to keep checking dmesg or check the wifi connection from GUI 3. suspend/resume multiple times 4. check the wifi connection [Where problems could occur] What the 2 commits should be safe and won't introduce any regression. 1. Reset AFEDIG register before BB reset in power off sequence 2. Adjust power and clock parameters To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2065128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2065128] Re: rtw89_8852ce - Lost WIFI connection after suspend
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-40.40.1~22.04.1 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- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2065128 Title: rtw89_8852ce - Lost WIFI connection after suspend Status in HWE Next: New 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 Released Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Status in linux source package in Oracular: Fix Released Status in linux-oem-6.5 source package in Oracular: Invalid Bug description: [Impact] Lost WIFI connection after suspend. While this happen, the WIFI module couldn't detect any AP, re-enable module and reboot OS without any help. There only way to get it back is cold boot. [Fix] Realtek provides a fix which has been included in rtw maintainer's tree https://lore.kernel.org/linux-wireless/20240426061200.44262-1-pks...@realtek.com/T/#mbfcb37c2fdc85ba280743f2b07fbf1fa8719eb79 The commits has been included in v6.10-rc1 4e5957101d42 wifi: rtw89: 8852c: refine power sequence to imporve power consumption 535c045da60f wifi: rtw89: reset AFEDIG register in power off sequence [Test case] 1. Boot into OS 2. open terminal to keep checking dmesg or check the wifi connection from GUI 3. suspend/resume multiple times 4. check the wifi connection [Where problems could occur] What the 2 commits should be safe and won't introduce any regression. 1. Reset AFEDIG register before BB reset in power off sequence 2. Adjust power and clock parameters To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2065128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
This bug is awaiting verification that the linux-azure/5.4.0-1135.142 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-focal-linux-azure' to 'verification-done-focal- linux-azure'. If the problem still exists, change the tag 'verification- needed-focal-linux-azure' to 'verification-failed-focal-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-focal-linux-azure-v2 verification-needed-focal-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 source package in Focal: Fix Committed Status in linux-signed-hwe-6.5 source package in Jammy: Fix Committed Status in linux-signed-hwe-6.5 source package in Mantic: Won't Fix Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
This bug is awaiting verification that the linux- raspi-5.4/5.4.0-1114.126~18.04.1 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-bionic-linux- raspi-5.4' to 'verification-done-bionic-linux-raspi-5.4'. If the problem still exists, change the tag 'verification-needed-bionic-linux- raspi-5.4' to 'verification-failed-bionic-linux-raspi-5.4'. 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-bionic-linux-raspi-5.4-v2 verification-needed-bionic-linux-raspi-5.4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 source package in Focal: Fix Committed Status in linux-signed-hwe-6.5 source package in Jammy: Fix Committed Status in linux-signed-hwe-6.5 source package in Mantic: Won't Fix Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckRe
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
This bug is awaiting verification that the linux- gcp-5.4/5.4.0-1134.143~18.04.1 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-bionic-linux- gcp-5.4' to 'verification-done-bionic-linux-gcp-5.4'. If the problem still exists, change the tag 'verification-needed-bionic-linux-gcp-5.4' to 'verification-failed-bionic-linux-gcp-5.4'. 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-bionic-linux-gcp-5.4-v2 verification-needed-bionic-linux-gcp-5.4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 source package in Focal: Fix Committed Status in linux-signed-hwe-6.5 source package in Jammy: Fix Committed Status in linux-signed-hwe-6.5 source package in Mantic: Won't Fix Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Cu
[Kernel-packages] [Bug 2058331] Re: Update amd_sfh for AMD strix series
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-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-noble-linux-azure-v2 verification-needed-noble-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2058331 Title: Update amd_sfh for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: [SRU Justification] [Impact] AMD MP2 controller not correctly enabled on new processors and thus the associated sensors. [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 [Fix] 6 upstream commits from v6.9-rc1. [Test Case] The MP2 shall ben enabled correctly with: c4:00.7 MP2 I2C controller: Advanced Micro Devices, Inc. [AMD] Device 15e6 [Where problems could occur] No. This enables MP2 on new processor families with backward support. [Other Info] While this is on v6.9-rc1 only, Noble and oem-6.8 will be nominated for fix. == original bug report = Extend MP2 register region to enable family 1AH based family on the supported OEM platforms, needs to be backported into oem-6.8. [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 Following fixes applied to linus tree: * 90184f90c9ac5 HID: amd_sfh: Set the AMD SFH driver to depend on x86 * 6296562f30b1c HID: amd_sfh: Extend MP2 register access to SFH * 2105e8e00da46 HID: amd_sfh: Improve boot time when SFH is available * c1db0073212ef HID: amd_sfh: Avoid disabling the interrupt * bbf0dec306966 HID: amd_sfh: Update HPD sensor structure elements * 333861f4cca6d HID: amd_sfh: Increase sensor command timeout To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058331] Re: Update amd_sfh for AMD strix series
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2058331 Title: Update amd_sfh for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: [SRU Justification] [Impact] AMD MP2 controller not correctly enabled on new processors and thus the associated sensors. [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 [Fix] 6 upstream commits from v6.9-rc1. [Test Case] The MP2 shall ben enabled correctly with: c4:00.7 MP2 I2C controller: Advanced Micro Devices, Inc. [AMD] Device 15e6 [Where problems could occur] No. This enables MP2 on new processor families with backward support. [Other Info] While this is on v6.9-rc1 only, Noble and oem-6.8 will be nominated for fix. == original bug report = Extend MP2 register region to enable family 1AH based family on the supported OEM platforms, needs to be backported into oem-6.8. [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 Following fixes applied to linus tree: * 90184f90c9ac5 HID: amd_sfh: Set the AMD SFH driver to depend on x86 * 6296562f30b1c HID: amd_sfh: Extend MP2 register access to SFH * 2105e8e00da46 HID: amd_sfh: Improve boot time when SFH is available * c1db0073212ef HID: amd_sfh: Avoid disabling the interrupt * bbf0dec306966 HID: amd_sfh: Update HPD sensor structure elements * 333861f4cca6d HID: amd_sfh: Increase sensor command timeout To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058331] Re: Update amd_sfh for AMD strix series
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-40.40.1~22.04.1 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- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2058331 Title: Update amd_sfh for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: [SRU Justification] [Impact] AMD MP2 controller not correctly enabled on new processors and thus the associated sensors. [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 [Fix] 6 upstream commits from v6.9-rc1. [Test Case] The MP2 shall ben enabled correctly with: c4:00.7 MP2 I2C controller: Advanced Micro Devices, Inc. [AMD] Device 15e6 [Where problems could occur] No. This enables MP2 on new processor families with backward support. [Other Info] While this is on v6.9-rc1 only, Noble and oem-6.8 will be nominated for fix. == original bug report = Extend MP2 register region to enable family 1AH based family on the supported OEM platforms, needs to be backported into oem-6.8. [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 Following fixes applied to linus tree: * 90184f90c9ac5 HID: amd_sfh: Set the AMD SFH driver to depend on x86 * 6296562f30b1c HID: amd_sfh: Extend MP2 register access to SFH * 2105e8e00da46 HID: amd_sfh: Improve boot time when SFH is available * c1db0073212ef HID: amd_sfh: Avoid disabling the interrupt * bbf0dec306966 HID: amd_sfh: Update HPD sensor structure elements * 333861f4cca6d HID: amd_sfh: Increase sensor command timeout To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058330] Re: Update amd-pmf for AMD strix series
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2058330 Title: Update amd-pmf for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Status in linux-oem-6.8 source package in Oracular: Invalid Bug description: [SRU Justfication] [Impact] Missing AMD-PMF support for AMD Strix platforms. [Fix] A few commits from v6.9-rc1. [Test Case] And feature enabled message should appear in dmesg: [ 3.203628] amd-pmf AMDI0103:00: registered PMF device successfully Access via sysfs: root@test:/sys/devices/platform/AMDI0103:00# cat cnqf_enable on [Where problems could occur] PMF once caused cpufreq locks or other unexpected behaviors in the past and may take additional fix to address. [Other Info] While this is in v6.9-rc-1 now, Noble and OEM-6.8 will be nominated for fix. == original bug report == These updates will be enhanced amd-pmf for family 1AH on the supported OEM platforms, including enabling new revision for BIOS notify events, support static slider by APTS (AMD Performance and Thermal State)...etc. Needs to be backported into oem-6.8. Following are commits merged to linus tree for v6.9-rc1: * 8362e862fb879 platform/x86/amd/pmf: Update sps power thermals according to the platform-profiles * 3eecb434d7f21 platform/x86/amd/pmf: Add support to get sps default APTS index values * 48d38f569261b platform/x86/amd/pmf: Add support to get APTS index numbers for static slider * 6262938eef282 platform/x86/amd/pmf: Add support to notify sbios heart beat event * 5fdc8b82aab4c platform/x86/amd/pmf: Add support to get sbios requests in PMF driver * 233f78e11e1fa platform/x86/amd/pmf: Disable debugfs support for querying power thermals * a33e9e106601b platform/x86/amd/pmf: Differentiate PMF ACPI versions To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
