The task "linux-restricted-modules (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Changed in: linux-restricted-modules (Ubuntu) Status: Triaged => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1933980 Title: NVIDIA CVE-2021-{1093|1094|1094} Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Expired Status in linux-restricted-modules package in Ubuntu: Expired Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-465 package in Ubuntu: In Progress Status in nvidia-settings package in Ubuntu: Fix Released Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-460 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in linux source package in Bionic: Expired Status in linux-restricted-modules source package in Bionic: Expired Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: Fix Released Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-460 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-restricted-modules source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: Won't Fix Status in nvidia-settings source package in Focal: Fix Released Status in fabric-manager-450 source package in Groovy: Fix Released Status in fabric-manager-460 source package in Groovy: Fix Released Status in libnvidia-nscq-450 source package in Groovy: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux-restricted-modules source package in Groovy: Won't Fix Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Won't Fix Status in nvidia-settings source package in Groovy: Fix Released Status in fabric-manager-450 source package in Hirsute: Fix Released Status in fabric-manager-460 source package in Hirsute: Fix Released Status in libnvidia-nscq-450 source package in Hirsute: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux-restricted-modules source package in Hirsute: Won't Fix Status in nvidia-graphics-drivers-390 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: Won't Fix Status in nvidia-settings source package in Hirsute: Fix Released Bug description: As per the subject, the update includes fixes for the following CVEs: CVE-2021-1093 CVE-2021-1094 CVE-2021-1095 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1933980/+subscriptions
четверг
[Bug 2141276] Re: efi: Fix swapped arguments to bsearch() in efi_status_to_*() SAUCE patch
This bug is awaiting verification that the linux- nvidia-6.17/6.17.0-1017.17 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- nvidia-6.17' to 'verification-done-noble-linux-nvidia-6.17'. If the problem still exists, change the tag 'verification-needed-noble-linux- nvidia-6.17' to 'verification-failed-noble-linux-nvidia-6.17'. 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-nvidia-6.17-v2 verification-needed-noble-linux-nvidia-6.17 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2141276 Title: efi: Fix swapped arguments to bsearch() in efi_status_to_*() SAUCE patch Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux source package in Questing: Fix Released Status in linux source package in Resolute: Fix Released Bug description: [Impact] The swapped bsearch() arguments cause the function to calculate incorrect element offsets when searching the efi_error_codes array: - Buggy behavior: bsearch thinks there are 24 elements of 12 bytes each - Correct behavior: 12 elements of 24 bytes each (on 64-bit systems) This causes efi_status_to_err() and efi_status_to_str() to read at wrong memory offsets (every 12 bytes instead of every 24 bytes), potentially: - Returning incorrect errno values for EFI status codes - Returning wrong error description strings - Failing to find valid status codes and returning default error values These functions are used to translate EFI firmware error codes to Linux errno values and human-readable strings, affecting error reporting for EFI-related operations including secure boot and firmware variable access. [Test Plan] 1. Build kernel with the fix applied 2. Boot system with UEFI firmware 3. Trigger EFI error conditions that exercise efi_status_to_err() and efi_status_to_str(), such as: - Secure boot signature verification failures - EFI variable access errors - MOK (Machine Owner Key) operations 4. Verify dmesg shows correct EFI error messages 5. Compare error messages before and after the fix to confirm correct status code translation Alternatively, a unit test can verify the bsearch returns correct results: - Call efi_status_to_err() with known EFI status codes (e.g., EFI_SUCCESS, EFI_INVALID_PARAMETER, EFI_SECURITY_VIOLATION) - Verify correct errno values are returned (-EINVAL, -EACCES, etc.) [Where problems could occur] The fix swaps two adjacent function arguments. Potential issues: 1. The fix changes the search behavior, which could theoretically expose latent bugs in code that was accidentally working due to the incorrect search. For example, if code was relying on the -EINVAL fallback when bsearch failed to find a match, it might now receive a different (correct) errno value. 2. Since this affects EFI error reporting, any issues would manifest as incorrect error messages in dmesg or wrong return values from EFI operations. This could affect debugging but should not cause system instability. [Other Info] - Root cause: The bug was introduced in the SAUCE patch cherry-picked from kernel-ark commit 2ae9082db0b5: https://gitlab.com/cki-project/kernel-ark/-/commit/2ae9082db0b5 - Upstream fix: https://gitlab.com/cki-project/kernel-ark/-/commit/49bcc48074ba - bsearch(3) man page: https://man7.org/linux/man-pages/man3/bsearch.3.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141276/+subscriptions
[Bug 2149762] Re: Revert "netfilter: conntrack: fix erronous removal of offload bit"
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149762 Title: Revert "netfilter: conntrack: fix erronous removal of offload bit" Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: In Progress Bug description: [Impact] With this commit: netfilter: conntrack: fix erronous removal of offload bit We hit the regression on PS6/7, all the nodes with this commit hit soft lockup every 1-2 days and need to reboot the nodes to recover, e.g.: [1022567.831263] watchdog: BUG: soft lockup - CPU#352 stuck for 26s! [kworker/u789:13:1036823] [1022567.831271] Modules linked in: scsi_transport_iscsi mlx5_vfio_pci vfio_pci_core vfio_iommu_type1 vfio iommufd vhost_net tap xfs act_csum act_pedit act_ct nf_flow_table act_tunnel_key xt_CT xt_tcpudp nft_compat dm_crypt ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat iptable_filter nf_tables veth nf_conntrack_netlink vhost_vsock vmw_vsock_virtio_transport_common vhost vsock nvme_fabrics nvme_keyring act_mirred act_skbedit act_vlan cls_matchall 8021q garp mrp geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink act_gact cls_flower sch_ingress openvswitch nsh nf_conncount nf_nat bridge stp llc bonding sunrpc binfmt_misc intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd kvm_amd kvm irqbypass rapl ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf k10temp ccp ipmi_msghandler mac_hid mlx5_vdpa vringh vhost_iotlb vdpa dm_service_time sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua nf_conntrack [1022567.831352] nf_defrag_ipv6 nf_defrag_ipv4 efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 mlx5_ib ib_uverbs macsec ib_core raid10 hid_generic usbhid ses hid enclosure dax_hmem mlx5_core crct10dif_pclmul crc32_pclmul cxl_acpi polyval_clmulni cxl_port mlxfw polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 cxl_core psample nvme mpt3sas ahci raid_class nvme_core tls ast tg3 scsi_transport_sas libahci pci_hyperv_intf nvme_auth i2c_algo_bit xhci_pci xhci_pci_renesas i2c_piix4 aesni_intel crypto_simd cryptd [1022567.831407] CPU: 352 PID: 1036823 Comm: kworker/u789:13 Kdump: loaded Tainted: G L 6.8.0-106-generic #106~22.04.1+hf399032v20260316b0-Ubuntu [1022567.831411] Hardware name: Lenovo ThinkSystem SR665 V3/SB27B75430, BIOS KAE140F-5.70 09/03/2025 [1022567.831413] Workqueue: events_power_efficient nf_flow_offload_work_gc [nf_flow_table] [1022567.831425] RIP: 0010:rhashtable_walk_next+0x17/0xd0 [1022567.831433] Code: 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 55 48 89 e5 41 57 41 56 41 55 41 54 53 4c 8b 37 48 89 fb 4c 8b 7f 10 <4c> 8b 6f 08 45 0f b6 66 38 41 80 fc 01 0f 87 e4 b1 98 00 41 83 e4 [1022567.831435] RSP: 0018:ff732ea21e2cbda8 EFLAGS: 00000202 [1022567.831438] RAX: ff2b1e3b98ea4058 RBX: ff732ea21e2cbde0 RCX: 0000000000000000 [1022567.831440] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ff732ea21e2cbde0 [1022567.831441] RBP: ff732ea21e2cbdd0 R08: 0000000000000000 R09: 0000000000000000 [1022567.831442] R10: 0000000000000000 R11: 0000000000000000 R12: ff2b1cb8611cbee8 [1022567.831444] R13: ff2b1cb8611cbe40 R14: ff2b1cb8611cbe48 R15: ff2b1e3b98ea4058 [1022567.831445] FS: 0000000000000000(0000) GS:ff2b1fb3bb000000(0000) knlGS:0000000000000000 [1022567.831447] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [1022567.831449] CR2: 0000775a42eee000 CR3: 0000019530ce8003 CR4: 0000000000f71ef0 [1022567.831450] PKRU: 55555554 [1022567.831452] Call Trace: [1022567.831454] <TASK> [1022567.831461] nf_flow_offload_work_gc+0x5a/0xf0 [nf_flow_table] [1022567.831468] process_one_work+0x181/0x3a0 [1022567.831475] worker_thread+0x306/0x440 [1022567.831479] ? __pfx_worker_thread+0x10/0x10 [1022567.831481] kthread+0xef/0x120 [1022567.831485] ? __pfx_kthread+0x10/0x10 [1022567.831487] ret_from_fork+0x44/0x70 [1022567.831492] ? __pfx_kthread+0x10/0x10 [1022567.831494] ret_from_fork_asm+0x1b/0x30 [1022567.831502] </TASK> [1022568.208115] R13: 0000000000000002 R14: 0000000000000002 R15: 0003a1fef9c1d979 [1022568.216666] ? cpuidle_enter_state+0xca/0x720 [1022568.222092] ? tick_nohz_stop_tick+0x70/0x210 [1022568.227521] cpuidle_enter+0x2e/0x50 [1022568.232060] call_cpuidle+0x23/0x60 [1022568.236472] cpuidle_idle_call+0x11d/0x190 [1022568.241562] do_idle+0x87/0xf0 [1022568.245472] cpu_startup_entry+0x2a/0x30 [1022568.250357] start_secondary+0x129/0x160 [1022568.255243] secondary_startup_64_no_verify+0x184/0x18b [1022568.261586] </TASK> [Fix] Without this commit, we spent few weeks to confirm PS6/7 nodes running without any lockup. This commit is a follow-up fix for: netfilter: conntrack: rework offload nf_conn timeout extension logic But the call path and logic starting from flow_offload_fixup_ct changed between these 2 commits. Only manually backport this commit without all the changes in the middle causes issue, and the commit message also says what it fixes is harmless. [Test Plan] We have run a test kernel without this commit on PS6/7 for almost 2 weeks without hitting any soft lockup. [Where problems could occur] The commit we revert, its commit message says what it fixes is harmless, and we have already run the kernel without it for almost 2 weeks without any issue, the risk is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149762/+subscriptions
[Bug 2148636] Re: backport Intel iwlwifi core102 support from linux-next to linux/resolute 7.0.
* 6a584e336cefb ("wifi: cfg80211: add support to handle incumbent signal detected event from mac80211/driver") - added an additional API cfg80211_incumbent_signal_notify but is never used. But since a latter commit e4b993f2bca78 ("wifi: nl80211: split out UHR operation information") added another nl80211 command NL80211_ATTR_UHR_OPERATION, commit 6a584e336cefb should stay to keep ABI compatible. * 92fecd2744552 ("wifi: cfg80211: fix background CAC") * d69cb039ab193 ("wifi: cfg80211: set and report chandef CAC ongoing") * 68b908b3c83b2 ("wifi: cfg80211: events, report background radar") - These three commits add `cfg80211_set_cac_state` that is never used, as well as two enum nl80211_frequency_attr, NL80211_FREQUENCY_ATTR_CAC_START_TIME and NL80211_FREQUENCY_ATTR_PAD. Should be safe to skip them. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148636 Title: backport Intel iwlwifi core102 support from linux-next to linux/resolute 7.0. Status in linux package in Ubuntu: Incomplete Status in linux source package in Resolute: Incomplete Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148636/+subscriptions
[Bug 2142389] Re: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot
Hi @agd5f and @Venemo, I appreciate the technical feedback, but I must respectfully disagree with the "normal behavior" assessment for one simple, documented reason: The 6.1.169 LTS Baseline. I have performed a controlled test using the same hardware, same OS, and same logging levels. The "Logging Enabled" Argument: If the flood of amdgpu_dm_atomic_commit_tail messages were merely due to logging being enabled, they should appear in the Kernel 6.1 logs as well. They do not. On Kernel 6.1, the driver is silent and efficient after resume. On 6.4+, it enters a frantic infinite loop. Why does "normal compositor behavior" only become "spammy" from 6.4 onwards? The "Monitor Specific" Argument: If the HDMI signal drop were a hardware or monitor issue, it would manifest regardless of the kernel version. The signal is rock solid on Kernel 6.1. It only drops on kernels that exhibit the 200MB/min log flooding. This is a software- induced signal failure, not a hardware defect. The Challenge: I am more than willing to perform a bisect to find the exact commit that broke Tonga, but I am blocked by the infrastructure. The Ubuntu Mainline servers return 404 Not Found for the 6.4-rc series. Since you requested a bisect: Can you provide a valid, working link to the 6.4-rc1 (and subsequent RCs) binaries compatible with Ubuntu/Zorin? Or, can you point to the specific changes in DC/Atomic State handling for Volcanic Islands that landed in 6.4? I have the data. I have the "Good" (6.1) and the "Bad" (6.4+). I am ready to test, but I need valid tools. Until then, the logs clearly show a regression that started in the 6.4 cycle. Best regards, Danilo (The Tonga Guy) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2142389 Title: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot Status in linux package in Ubuntu: New Bug description: AMDGPU suspend → display black / no video after resume on Radeon R9 380 (No EDID read) Summary: After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video. Steps to reproduce: Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17). Suspend system (e.g., via GNOME “Suspend”). Wait short period. Attempt to resume (mouse/keyboard). System wakes but display either shows garbled video or no output. Observed behavior: System appears not crashed (fans/LEDs/keyboard continue). Screen stays black or displays remnants but no usable video. Sometimes resume works, sometimes fails. Relevant log excerpt: amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read. Hardware: Motherboard: Gigabyte B450 AORUS PRO WIFI CPU: AMD Ryzen 5 5500 GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver) Software environment: Zorin OS 18 Core (Ubuntu 24.10 base) kernel: 6.17.0-14-generic X11 session Workaround currently applied: Suspend disabled. System remains stable without suspend. Note: Bug appears related to video resume rather than system freeze; display subsystem (EDID handshake) may fail after suspend. Additional info: Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+subscriptions
[Bug 2147081] [NEW] Cannot install displaylink-driver because of missing kernel headers
You have been subscribed to a public bug: I am running Ubuntu 25.10 on a Lenovo X1 Gen13 and ran into the problem that the external display doesn't work with a connected Lenovo docking station. This is a well-known problem and the solution is to manually install the synaptics DisplayLink driver. The laptop came preinstalled with kernel 6.17.0-1012-oem. However, I cannot manually install because the corresponding kernel headers are not available and they are also nowhere to be found. I followed the instructions on the synaptics website (adding the apt repository): https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu But I see the following error: =========================================================== root@laptop:/home/andreas# apt install displaylink-driver Installing: displaylink-driver Installing dependencies: dkms evdi Suggested packages: xmlstarlet menu Summary: Upgrading: 0, Installing: 3, Removing: 0, Not Upgrading: 0 Download size: 0 B / 7,128 kB Space needed: 245 kB / 614 GB available Continue? [Y/n] Y Selecting previously unselected package dkms. (Reading database ... 315615 files and directories currently installed.) Preparing to unpack .../dkms_3.2.0-1ubuntu1_all.deb ... Unpacking dkms (3.2.0-1ubuntu1) ... Selecting previously unselected package evdi. Preparing to unpack .../evdi_1.14.15-181_amd64.deb ... Unpacking evdi (1.14.15-181) ... Selecting previously unselected package displaylink-driver. Preparing to unpack .../displaylink-driver_6.2.0-30_amd64.deb ... Unpacking displaylink-driver (6.2.0-30) ... Setting up dkms (3.2.0-1ubuntu1) ... Setting up evdi (1.14.15-181) ... Creating symlink /var/lib/dkms/evdi/1.14.15/source -> /usr/src/evdi-1.14.15 Error! Your kernel headers for kernel 6.17.0-1012-oem cannot be found at /lib/modules/6.17.0-1012-oem/build or /lib/modules/6.17.0-1012-oem/source. Please install the linux-headers-6.17.0-1012-oem package or use the --kernelsourcedir option to tell DKMS where it's located. dpkg: error processing package evdi (--configure): installed evdi package post-installation script subprocess returned error exit status 21 dpkg: dependency problems prevent configuration of displaylink-driver: displaylink-driver depends on evdi (>= 1.12.0) | evdi-dkms (>= 1.12.0); however: Package evdi is not configured yet. Package evdi-dkms is not installed. Package evdi which provides evdi-dkms is not configured yet. displaylink-driver depends on evdi (>= 1.12.0) | libevdi1 (>= 1.12.0); however: Package evdi is not configured yet. Package libevdi1 is not installed. Package evdi which provides libevdi1 is not configured yet. dpkg: error processing package displaylink-driver (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.13.1-1) ... Errors were encountered while processing: evdi displaylink-driver Error: Sub-process /usr/bin/dpkg returned an error code (1) ============================================================== root@laptop:/home/andreas# dpkg -l | grep oem ii linux-image-6.17.0-1012-oem 6.17.0-1012.12 amd64 Signed kernel image oem ii linux-modules-6.17.0-1012-oem 6.17.0-1012.12 amd64 Linux kernel modules for version 6.17.0 ii linux-modules-ipu6-6.17.0-1012-oem 6.17.0-1012.12 amd64 Linux kernel ipu6 modules for version 6.17.0-1012 ii linux-modules-ipu7-6.17.0-1012-oem 6.17.0-1012.12 amd64 Linux kernel ipu7 modules for version 6.17.0-1012 ii linux-modules-usbio-6.17.0-1012-oem 6.17.0-1012.12 amd64 Linux kernel usbio modules for version 6.17.0-1012 ii linux-modules-vision-6.17.0-1012-oem 6.17.0-1012.12 amd64 Linux kernel vision modules for version6.17.0-1012 ii linux-oem-6.17-tools-6.17.0-1012 6.17.0-1012.12 amd64 Linux kernel version specific tools forversion 6.17.0-1012 ii linux-tools-6.17.0-1012-oem 6.17.0-1012.12 amd64 Linux kernel version specific tools forversion 6.17.0-1012 ii oem-hwe-meta 24.04ubuntu3 all hardware support for hwe project ii oem-nantou-meta 24.04ubuntu3 all hardware support for Nantou project ii oem-sutton-factory-dacia-meta 24.04ubuntu7 all hardware support for Lenovo ThinkPad X12-in-1 G10, X1 Carbon G13 (factory) ii oem-sutton-factory-meta 24.04ubuntu3 amd64 factory meta package for Sutton ii ubuntu-oem-keyring 2023.11.28.1 all GnuPG keys of the Ubuntu OEM Vendor Archive ====================================== root@laptop:/home/andreas# lsb_release -rd Description: Ubuntu 25.10 Release: 25.10 ====================================== root@laptop:/home/andreas# apt-cache policy displaylink-driver displaylink-driver: Installed: (none) Candidate: 6.2.0-30 Version table: 6.2.0-30 500 500 https://www.synaptics.com/sites/default/files/Ubuntu stable/non-free amd64 Packages 100 /var/lib/dpkg/status 6.1.1-17 500 500 https://www.synaptics.com/sites/default/files/Ubuntu stable/non-free amd64 Packages 6.1.0-17 500 500 https://www.synaptics.com/sites/default/files/Ubuntu stable/non-free amd64 Packages 6.0.0-24 500 500 https://www.synaptics.com/sites/default/files/Ubuntu stable/non-free amd64 Packages 5.8.0-33 500 500 https://www.synaptics.com/sites/default/files/Ubuntu stable/non-free amd64 Packages 5.7.0-129 500 500 https://www.synaptics.com/sites/default/files/Ubuntu stable/non-free amd64 Packages =============================================== ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-daily-bug -- Cannot install displaylink-driver because of missing kernel headers https://bugs.launchpad.net/bugs/2147081 You received this bug notification because you are subscribed to linux in Ubuntu.
[Bug 1982483]
Well, except for those involved in circuits, it seems that users can only guess at the moment. snd-hda-intel.model=103c:86c7 Try adding this after the grub line and vmLinux line. See if it has the same effect as your command. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1982483 Title: No sound from built-in speakers HP Pavilion All-in-One Desktop 27-ca1xxx (ALC274) Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I have tried: options snd-hda-intel model=alc285-hp-amp-init options snd-hda-intel model=alc274-dell-aio and newer kernels up to 5.19-rc6. 21: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.2CriaNVEdN5 SysFS ID: /devices/pci0000:00/0000:00:1f.3 SysFS BusID: 0000:00:1f.3 Hardware Class: sound Device Name: "Onboard - Sound" Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x7ad0 SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x89e9 Revision: 0x11 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x6105238000-0x610523bfff (rw,non-prefetchable) Memory Range: 0x6105000000-0x61050fffff (rw,non-prefetchable) IRQ: 161 (1098 events) Module Alias: "pci:v00008086d00007AD0sv0000103Csd000089E9bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_tgl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_tgl" Config Status: cfg=new, avail=yes, need=no, active=unknown <6>[ 3.582352] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC274: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker <6>[ 3.582359] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <6>[ 3.582362] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) <6>[ 3.582364] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0 <6>[ 3.582366] snd_hda_codec_realtek hdaudioC0D0: inputs: <6>[ 3.582367] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 <6>[ 3.582369] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 Alsa-info: https://alsa- project.org/db/?f=ed6190cfc9d9eb1c758c6c3106dd236b150f5b31 Here is a kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=216139 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: ernst 1560 F.... pulseaudio /dev/snd/controlC0: ernst 1560 F.... pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (143 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP Pavilion All-in-One Desktop 27-ca1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1006-oem root=UUID=72ea78e1-7744-4fcc-b63c-3aa577c86a80 ro quiet splash ibt=off mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1006.6-oem 6.0.0 RelatedPackageVersions: linux-restricted-modules-6.0.0-1006-oem N/A linux-backports-modules-6.0.0-1006-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy wayland-session Uname: Linux 6.0.0-1006-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/09/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.name: 89E9 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnAMI:bvrF.02:bd02/09/2022:br15.2:efr1.16:svnHP:pnHPPavilionAll-in-OneDesktop27-ca1xxx:pvr:rvnHP:rn89E9:rvr0100:cvnHP:ct13:cvr:sku661Q7EA#UUW: dmi.product.family: 103C_53311M HP Pavilion dmi.product.name: HP Pavilion All-in-One Desktop 27-ca1xxx dmi.product.sku: 661Q7EA#UUW dmi.sys.vendor: HP modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-06-15T22:28:44.879144 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1982483/+subscriptions
[Bug 2148686] Re: FrameworkDesktop: System randomly hangs / freezes after using Chrome (Youtube or Screen-Sharing)
The "workaround" to stop the freeze / crashing, is to disable hardware accel. in Chrome. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148686 Title: FrameworkDesktop: System randomly hangs / freezes after using Chrome (Youtube or Screen-Sharing) Status in linux package in Ubuntu: New Bug description: Quite recently (last week) my system started to hang/freeze randomly when using Chrome and browsing youtube or when having a Video Call. The system either hangs completely or stops working and blanking the displays. Sometimes it recovers from this state. The usage pattern is always the same * Chrome * Video Quite interestingly during gaming via Steam I did not experience any hang/freeze. It seems to be related to Video handling in Chrome. > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 25.10 Release: 25.10 Codename: questing Hardware: Framework Desktop _AMD Ryzen AI Max 300 Series Processor: AMD RYZEN AI MAX+ 395 w/ Radeon™ 8060S × 32 dmesg gives plenty of information pointing to amdgpu: [ 3536.625642] amdgpu 0000:c2:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 [ 3536.625654] amdgpu 0000:c2:00.0: amdgpu: Failed to power gate VPE! [ 3536.625658] [drm:amdgpu_dpm_enable_vpe [amdgpu]] *ERROR* Dpm disable vpe failed, ret = -62. [ 3541.439018] amdgpu 0000:c2:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 [ 3541.439025] amdgpu 0000:c2:00.0: amdgpu: Failed to power gate VCN instance 1! [ 3541.439027] [drm:amdgpu_dpm_enable_vcn [amdgpu]] *ERROR* Dpm disable uvd failed, ret = -62. [ 3544.902422] amdgpu 0000:c2:00.0: amdgpu: Dumping IP State [ 3549.702445] amdgpu 0000:c2:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 [ 3549.702453] amdgpu 0000:c2:00.0: amdgpu: Failed to disable gfxoff! [ 3554.505681] amdgpu 0000:c2:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 [ 3554.505693] amdgpu 0000:c2:00.0: amdgpu: Failed to disable gfxoff! [ 3559.308523] amdgpu 0000:c2:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 [ 3559.308535] amdgpu 0000:c2:00.0: amdgpu: Failed to disable gfxoff! [ 3564.111256] amdgpu 0000:c2:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 [ 3564.111268] amdgpu 0000:c2:00.0: amdgpu: Failed to disable gfxoff! [ 3564.111361] amdgpu 0000:c2:00.0: amdgpu: Dumping IP State Completed [ 3564.111451] amdgpu 0000:c2:00.0: amdgpu: [drm] AMDGPU device coredump file has been created [ 3564.111458] amdgpu 0000:c2:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data [ 3564.111461] amdgpu 0000:c2:00.0: amdgpu: ring sdma0 timeout, signaled seq=74533, emitted seq=74537 [ 3564.111465] amdgpu 0000:c2:00.0: amdgpu: GPU reset begin! [ 3568.703656] amdgpu 0000:c2:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 [ 3568.703665] amdgpu 0000:c2:00.0: amdgpu: Failed to disable gfxoff! [ 3687.240764] INFO: task kworker/16:1:46905 blocked for more than 122 seconds. [ 3687.240765] Tainted: G W L 6.17.0-22-generic #22-Ubuntu [ 3687.240765] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3687.240766] task:kworker/16:1 state:D stack:0 pid:46905 tgid:46905 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 3687.240767] Workqueue: events amdgpu_tlb_fence_work [amdgpu] [ 3687.240846] Call Trace: [ 3687.240847] <TASK> [ 3687.240847] __schedule+0x2ed/0x7c0 [ 3687.240848] ? __pick_eevdf+0x150/0x280 [ 3687.240851] schedule+0x27/0x90 [ 3687.240852] schedule_timeout+0xcf/0x110 [ 3687.240853] dma_fence_default_wait+0x1be/0x240 [ 3687.240855] ? __pfx_dma_fence_default_wait_cb+0x10/0x10 [ 3687.240856] dma_fence_wait_timeout+0x13a/0x170 [ 3687.240857] amdgpu_tlb_fence_work+0x2d/0x110 [amdgpu] [ 3687.240941] process_one_work+0x18b/0x370 [ 3687.240942] worker_thread+0x317/0x450 [ 3687.240943] ? __pfx_worker_thread+0x10/0x10 [ 3687.240944] kthread+0x108/0x220 [ 3687.240945] ? __pfx_kthread+0x10/0x10 [ 3687.240946] ret_from_fork+0x131/0x150 [ 3687.240947] ? __pfx_kthread+0x10/0x10 [ 3687.240948] ret_from_fork_asm+0x1a/0x30 [ 3687.240949] </TASK> [ 3710.568331] amdgpu 0000:c2:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE [ 3710.568342] amdgpu 0000:c2:00.0: amdgpu: failed to unmap legacy queue [ 3710.784931] [drm:gfx_v11_0_cp_gfx_enable.isra.0 [amdgpu]] *ERROR* failed to halt cp gfx ProblemType: Bug DistroRelease: Ubuntu 25.10 Package: xserver-xorg-video-amdgpu (not installed) ProcVersionSignature: Ubuntu 6.17.0-22.22-generic 6.17.13 Uname: Linux 6.17.0-22-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 17:49:22 2026 InstallationDate: Installed on 2025-10-10 (189 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148686/+subscriptions
[Bug 2149762] Re: Revert "netfilter: conntrack: fix erronous removal of offload bit"
** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149762 Title: Revert "netfilter: conntrack: fix erronous removal of offload bit" Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Committed Bug description: [Impact] With this commit: netfilter: conntrack: fix erronous removal of offload bit We hit the regression on PS6/7, all the nodes with this commit hit soft lockup every 1-2 days and need to reboot the nodes to recover, e.g.: [1022567.831263] watchdog: BUG: soft lockup - CPU#352 stuck for 26s! [kworker/u789:13:1036823] [1022567.831271] Modules linked in: scsi_transport_iscsi mlx5_vfio_pci vfio_pci_core vfio_iommu_type1 vfio iommufd vhost_net tap xfs act_csum act_pedit act_ct nf_flow_table act_tunnel_key xt_CT xt_tcpudp nft_compat dm_crypt ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat iptable_filter nf_tables veth nf_conntrack_netlink vhost_vsock vmw_vsock_virtio_transport_common vhost vsock nvme_fabrics nvme_keyring act_mirred act_skbedit act_vlan cls_matchall 8021q garp mrp geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink act_gact cls_flower sch_ingress openvswitch nsh nf_conncount nf_nat bridge stp llc bonding sunrpc binfmt_misc intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd kvm_amd kvm irqbypass rapl ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf k10temp ccp ipmi_msghandler mac_hid mlx5_vdpa vringh vhost_iotlb vdpa dm_service_time sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua nf_conntrack [1022567.831352] nf_defrag_ipv6 nf_defrag_ipv4 efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 mlx5_ib ib_uverbs macsec ib_core raid10 hid_generic usbhid ses hid enclosure dax_hmem mlx5_core crct10dif_pclmul crc32_pclmul cxl_acpi polyval_clmulni cxl_port mlxfw polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 cxl_core psample nvme mpt3sas ahci raid_class nvme_core tls ast tg3 scsi_transport_sas libahci pci_hyperv_intf nvme_auth i2c_algo_bit xhci_pci xhci_pci_renesas i2c_piix4 aesni_intel crypto_simd cryptd [1022567.831407] CPU: 352 PID: 1036823 Comm: kworker/u789:13 Kdump: loaded Tainted: G L 6.8.0-106-generic #106~22.04.1+hf399032v20260316b0-Ubuntu [1022567.831411] Hardware name: Lenovo ThinkSystem SR665 V3/SB27B75430, BIOS KAE140F-5.70 09/03/2025 [1022567.831413] Workqueue: events_power_efficient nf_flow_offload_work_gc [nf_flow_table] [1022567.831425] RIP: 0010:rhashtable_walk_next+0x17/0xd0 [1022567.831433] Code: 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 55 48 89 e5 41 57 41 56 41 55 41 54 53 4c 8b 37 48 89 fb 4c 8b 7f 10 <4c> 8b 6f 08 45 0f b6 66 38 41 80 fc 01 0f 87 e4 b1 98 00 41 83 e4 [1022567.831435] RSP: 0018:ff732ea21e2cbda8 EFLAGS: 00000202 [1022567.831438] RAX: ff2b1e3b98ea4058 RBX: ff732ea21e2cbde0 RCX: 0000000000000000 [1022567.831440] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ff732ea21e2cbde0 [1022567.831441] RBP: ff732ea21e2cbdd0 R08: 0000000000000000 R09: 0000000000000000 [1022567.831442] R10: 0000000000000000 R11: 0000000000000000 R12: ff2b1cb8611cbee8 [1022567.831444] R13: ff2b1cb8611cbe40 R14: ff2b1cb8611cbe48 R15: ff2b1e3b98ea4058 [1022567.831445] FS: 0000000000000000(0000) GS:ff2b1fb3bb000000(0000) knlGS:0000000000000000 [1022567.831447] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [1022567.831449] CR2: 0000775a42eee000 CR3: 0000019530ce8003 CR4: 0000000000f71ef0 [1022567.831450] PKRU: 55555554 [1022567.831452] Call Trace: [1022567.831454] <TASK> [1022567.831461] nf_flow_offload_work_gc+0x5a/0xf0 [nf_flow_table] [1022567.831468] process_one_work+0x181/0x3a0 [1022567.831475] worker_thread+0x306/0x440 [1022567.831479] ? __pfx_worker_thread+0x10/0x10 [1022567.831481] kthread+0xef/0x120 [1022567.831485] ? __pfx_kthread+0x10/0x10 [1022567.831487] ret_from_fork+0x44/0x70 [1022567.831492] ? __pfx_kthread+0x10/0x10 [1022567.831494] ret_from_fork_asm+0x1b/0x30 [1022567.831502] </TASK> [1022568.208115] R13: 0000000000000002 R14: 0000000000000002 R15: 0003a1fef9c1d979 [1022568.216666] ? cpuidle_enter_state+0xca/0x720 [1022568.222092] ? tick_nohz_stop_tick+0x70/0x210 [1022568.227521] cpuidle_enter+0x2e/0x50 [1022568.232060] call_cpuidle+0x23/0x60 [1022568.236472] cpuidle_idle_call+0x11d/0x190 [1022568.241562] do_idle+0x87/0xf0 [1022568.245472] cpu_startup_entry+0x2a/0x30 [1022568.250357] start_secondary+0x129/0x160 [1022568.255243] secondary_startup_64_no_verify+0x184/0x18b [1022568.261586] </TASK> [Fix] Without this commit, we spent few weeks to confirm PS6/7 nodes running without any lockup. This commit is a follow-up fix for: netfilter: conntrack: rework offload nf_conn timeout extension logic But the call path and logic starting from flow_offload_fixup_ct changed between these 2 commits. Only manually backport this commit without all the changes in the middle causes issue, and the commit message also says what it fixes is harmless. [Test Plan] We have run a test kernel without this commit on PS6/7 for almost 2 weeks without hitting any soft lockup. [Where problems could occur] The commit we revert, its commit message says what it fixes is harmless, and we have already run the kernel without it for almost 2 weeks without any issue, the risk is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149762/+subscriptions
[Bug 2149872] [NEW] iptables connlimit traffic loss
Public bug reported: There seems to be a bug related to the iptables connlimit module in the latest Ubuntu 24.04.4 LTS kernel 6.8.0-110. I use the following iptables rule to limit the connections per IPv4 address to a webserver: iptables -I INPUT -p tcp --syn -m multiport --dports 80,443 -m connlimit --connlimit-above 200 -j DROP With this firewall rule installed, network traffic to the webserver is randomly dropped or delayed despite being well below the intended connection limit. It seems that the localhost address range is particularly affected, the first request from a local IP usually works, follwing requests are dropped or delayed. The problem also occurs if I choose ACCEPT instead of DROP as the target: iptables -I INPUT -p tcp --syn -m multiport --dports 80,443 -m connlimit --connlimit-above 200 -j ACCEPT The problem also occurs with the latest Ubuntu 24.04 proposed kernel 6.8.0-114, it does not occur with the previous kernel 6.8.0-107. It also occurs with Ubuntu 22.04.5 LTS kernel 5.15.0-174 and 5.15.0-176, I have not tested other kernel versions. This issue could be related to recent changes in the netfilter code regarding CVE-2026-23111. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149872 Title: iptables connlimit traffic loss Status in linux package in Ubuntu: New Bug description: There seems to be a bug related to the iptables connlimit module in the latest Ubuntu 24.04.4 LTS kernel 6.8.0-110. I use the following iptables rule to limit the connections per IPv4 address to a webserver: iptables -I INPUT -p tcp --syn -m multiport --dports 80,443 -m connlimit --connlimit-above 200 -j DROP With this firewall rule installed, network traffic to the webserver is randomly dropped or delayed despite being well below the intended connection limit. It seems that the localhost address range is particularly affected, the first request from a local IP usually works, follwing requests are dropped or delayed. The problem also occurs if I choose ACCEPT instead of DROP as the target: iptables -I INPUT -p tcp --syn -m multiport --dports 80,443 -m connlimit --connlimit-above 200 -j ACCEPT The problem also occurs with the latest Ubuntu 24.04 proposed kernel 6.8.0-114, it does not occur with the previous kernel 6.8.0-107. It also occurs with Ubuntu 22.04.5 LTS kernel 5.15.0-174 and 5.15.0-176, I have not tested other kernel versions. This issue could be related to recent changes in the netfilter code regarding CVE-2026-23111. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149872/+subscriptions
среда
[Bug 2149877] Re: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system
** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149877 Title: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system Status in linux package in Ubuntu: Confirmed Bug description: For the past few days I have been experiencing intermittent micro‑stutters in Ubuntu 26.04. The mouse cursor freezes for about half a second, and occasionally the system audio also cuts out briefly. This happens irregularly but repeatedly. The issue started after updating to Linux 7.0.0‑14‑generic. Around the same time, linux‑firmware was also updated, so I cannot determine which change might be responsible. On my laptop (Intel + Nvidia) I cannot reproduce the issue, but another user with AMD hardware reported similar symptoms on Discourse. Affected hardware: · CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz · GPU: AMD Radeon RX 9060 XT · OS: Ubuntu 26.04 Observed behaviour: · Mouse cursor freezes for ~0.5 seconds (“micro‑stutter”). · Occasional short audio dropouts. · I have not noticed the issue while gaming, although another user claims it also happens there. I would appreciate guidance on additional tools or diagnostics that could help identify the root cause. At the moment, the only evidence I can provide is the observed behaviour described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149877/+subscriptions
[Bug 2149766] Re: Linux kernel 6.17.0-22.22 breaks amdxdna
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alice C. Munduruca (cremfuelled) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149766 Title: Linux kernel 6.17.0-22.22 breaks amdxdna Status in linux package in Ubuntu: New Status in linux-hwe-6.17 package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Bug description: The kernel update causes amdxdna to no longer load. [ 30.859857] amdxdna 0000:c7:00.1: [drm] *ERROR* amdxdna_drm_open: SVA bind device failed, ret -95 It works fine on 6.17.0-20. This is caused by this stable update: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142250 Specifically this commit: " iommu: disable SVA when CONFIG_X86 is set" It was also reported in 6.18.y upstream. https://lore.kernel.org/stable/870872aa-28e9-412a-bac6-8020bf560e4f@amd.com/ These commits are needed to fix it. commit 27bfafac65d8 ("mm: add a ptdesc flag to mark kernel page tables") commit 977870522af3 ("mm: actually mark kernel page table pages") commit 412d000346ea ("x86/mm: use 'ptdesc' when freeing PMD pages") commit 018942956723 ("mm: introduce pure page table freeing function") commit bf9e4e30f353 ("x86/mm: use pagetable_free()") commit 5ba2f0a15564 ("mm: introduce deferred freeing for kernel page tables") commit e37d5a2d60a3 ("iommu/sva: invalidate stale IOTLB entries for kernel address space") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149766/+subscriptions
[Bug 2077257] Re: dev-tpmrm0.device failed -> slow boot
** Tags added: systemd-boot ** Tags added: resolute -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2077257 Title: dev-tpmrm0.device failed -> slow boot Status in linux package in Ubuntu: Confirmed Bug description: Hello, I tried the actual daily of Ubuntu 24.10. And the boot hang at job dev_tpm for 1:30min. sudo dmesg | grep tpm [ 1.193715] tpm_tis_remove+0xaa/0x100 [ 1.193719] tpm_tis_core_init+0x235/0x850 [ 1.193722] tpm_tis_init.part.0+0xc1/0x140 [ 1.193726] tpm_tis_plat_probe+0xc6/0x110 [ 1.194019] tpm_tis: probe of MSFT0101:00 failed with error -1 [ 3.906777] systemd[1]: Expecting device dev-tpmrm0.device - /dev/tpmrm0... This is the workaround: systemctl mask dev-tpmrm0.device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077257/+subscriptions