Hi Alexander, Could you please try the following command? It may help us identify the issue. After running it and reboot, please check whether the issue is gone. ``` echo "options snd-usb-audio quirk_alias=0b0e24ca:0b0e0349,0b0e24ba:0b0e0349" | \ sudo tee /etc/modprobe.d/jabra-fix.conf ``` Thanks BR An ** Changed in: linux (Ubuntu) Assignee: (unassigned) => ChunAnWu (kiya956) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155161 Title: Jabra Evolve 2 85 headset keeps reconnecting via usb Status in linux package in Ubuntu: New Bug description: As soon as i want to use any kind of usb connection with the headset the usb connects and reconnects over and over again. I made sure its not an issue of cable used or the usb hub in the docking station. by connecting it directly to the laptop. Although i could use usb with this headset on ubuntu lts 24 without any issues since i reinstalled with kubuntu 26 this occurs (guess it would happen in ubuntu 26 too) I gladly provide more info if needed. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 3 16:10:16 2026 InstallationDate: Installed on 2026-05-12 (22 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) IwDevWlp0s20f3Link: Not connected. MachineType: Dell Inc. Precision 3581 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic root=UUID=e1d7f812-2942-4efe-80f9-510636bb0378 ro quiet cryptdevice=UUID=24e90ca6-128d-41d3-be29-328e50acf97d:luks-24e90ca6-128d-41d3-be29-328e50acf97d root=/dev/mapper/luks-24e90ca6-128d-41d3-be29-328e50acf97d splash nvidia-drm.modeset=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2025 dmi.bios.release: 1.27 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.27.1 dmi.board.name: 0V8YXF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnDellInc.:bvr1.27.1:bd12/12/2025:br1.27:efr1.25:svnDellInc.:pnPrecision3581:pvr:rvnDellInc.:rn0V8YXF:rvrA00:cvnDellInc.:ct10:cvr:sku0C07:pfaPrecision: dmi.product.family: Precision dmi.product.name: Precision 3581 dmi.product.sku: 0C07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155161/+subscriptions
среда
[Bug 2148534] Re: [Ubuntu 26.04] Failed install OS onto JBOD disk on B540d-2HS M.2 controller
this commit exists in the following ubuntu kernel tags. $ g tag --contains 9b8b84879d4ad Ubuntu-6.17.0-2.2 .... Ubuntu-7.0.0-10.10 Ubuntu-7.0.0-11.11 Ubuntu-7.0.0-12.12 Ubuntu-7.0.0-13.13 Ubuntu-7.0.0-14.14 Ubuntu-7.0.0-15.15 Ubuntu-7.0.0-16.16 Ubuntu-7.0.0-17.17 Ubuntu-7.0.0-18.18 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148534 Title: [Ubuntu 26.04] Failed install OS onto JBOD disk on B540d-2HS M.2 controller Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: The system hangs during storage initialization when using a B540 RAID Kit with a single Micron 7450 Pro NVMe SSD configured in JBOD mode. Environment: Hardware: Lenovo ThinkSystem SR650 V4 Controller: B540d-2HS M.2 controller Disk: ThinkSystem M.2 7450 PRO 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD Kernel (broken): 7.0.0-13-generic (Ubuntu) Kernel (working): 6.8.x (Ubuntu 24.04 LTS) Reproduce steps: 1. Set the B540 RAID controller to allow JBOD or configure the Micron 7450P as a JBOD drive. 2. Start Ubuntu 26.04 installation. 3. The installer/kernel attempts to scan scsi0. 4. The driver hangs at "waiting for commands" and eventually triggers a firmware reset loop. The megaraid_sas driver reports multiple command timeouts followed by a controller firmware crash. Even though the logs show Secure JBOD support-: Yes and NVMe passthru support-: Yes, It seems like kernel oops in megasas_make_prp_nvme due to a page fault on an unmapped virtual address while building the NVMe, which can be refered in logs below with Call Trace. [ 271.793726] #PF: supervisor write access in kernel mode [ 271.794694] #PF: error_code(0x0002) - not-present page [ 271.795648] PGD 100000067 P4D 101b42067 PUD 101b43067 PMD 10219a067 PTE 0 [ 271.796887] Oops: Oops: 0002 [#1] SMP NOPTI [ 271.797675] CPU: 1 UID: 0 PID: 1905 Comm: kworker/u1025:3 Tainted: P S O 7.0.0-13-generic #13-Ubuntu PREEMPT(lazy) [ 271.799778] Tainted: [P]=PROPRIETARY_MODULE, [S]=CPU_OUT_OF_SPEC, [O]=OOT_MODULE [ 271.801123] Hardware name: Lenovo ThinkSystem SR650 V4/SB27B70076, BIOS IHE111A-1.21 03/28/2025 [ 271.801140] sd 0:0:2:0: [sda] tag#244 page boundary ptr_sgl: 0x0000000040507511 [ 271.802682] Workqueue: writeback wb_workfn [ 271.802733] sd 0:0:2:0: [sda] tag#245 page boundary ptr_sgl: 0x000000004c4d3310 [ 271.806138] (flush-8:0) [ 271.806643] RIP: 0010:megasas_make_prp_nvme.isra.0+0x12f/0x220 [megaraid_sas] [ 271.807955] Code: 20 49 83 c7 20 48 89 d1 48 83 e1 fc 83 e2 01 4c 0f 45 f9 49 8b 5f 10 45 8b 67 18 4c 89 e9 4c 8d 69 08 45 85 eb 74 52 45 29 ce <48> 89 19 83 c0 01 45 85 f6 7f af 4c 8b 7d c8 c1 e0 03 b9 01 00 00 [ 271.811246] RSP: 0018:ff50bfb988f8b298 EFLAGS: 00010206 [ 271.812215] RAX: 0000000000000200 RBX: 00000000f6a00000 RCX: ff50bfb983b9a000 [ 271.813520] RDX: ff50bfb983b9a008 RSI: 0000000000000000 RDI: 0000000000000000 [ 271.814822] RBP: ff50bfb988f8b2f8 R08: 00000000ffbb0000 R09: 0000000000001000 [ 271.816365] R10: 0000000000001000 R11: 0000000000000fff R12: 0000000000200000 [ 271.817860] R13: ff50bfb983b9a008 R14: 00000000001ff000 R15: ff2b1ee1e1f2cb08 [ 271.819321] FS: 0000000000000000(0000) GS:ff2b1ee542880000(0000) knlGS:0000000000000000 [ 271.820923] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 271.822134] CR2: ff50bfb983b9a000 CR3: 0000060144844004 CR4: 0000000000f73ef0 [ 271.823587] PKRU: 55555554 [ 271.824274] Call Trace: [ 271.824920] <TASK> [ 271.825514] megasas_build_io_fusion+0x2e2/0x330 [megaraid_sas] [ 271.826772] megasas_build_and_issue_cmd_fusion+0xa3/0x280 [megaraid_sas] [ 271.828168] ? sd_init_command+0x138/0x4a0 [ 271.829110] megasas_queue_command+0x11b/0x200 [megaraid_sas] [ 271.830347] ? scsi_init_command+0x74/0xc0 [ 271.831291] ? __rq_qos_issue+0x29/0x50 [ 271.832199] scsi_dispatch_cmd+0x95/0x290 [ 271.833129] scsi_queue_rq+0x62e/0x8e0 [ 271.834017] blk_mq_dispatch_rq_list+0x131/0x510 [ 271.835064] __blk_mq_do_dispatch_sched+0x2d9/0x360 [ 271.836154] ? mod_memcg_lruvec_state+0x101/0x2f0 [ 271.837206] __blk_mq_sched_dispatch_requests+0x157/0x1a0 [ 271.838369] ? elv_rb_add+0x70/0x90 [ 271.839210] blk_mq_sched_dispatch_requests+0x2d/0x80 [ 271.840316] blk_mq_run_hw_queue+0x2c0/0x330 [ 271.841295] blk_mq_dispatch_list+0x159/0x350 [ 271.842319] blk_mq_flush_plug_list+0x59/0x1e0 [ 271.843328] blk_add_rq_to_plug+0xe7/0x220 [ 271.844262] ? blk_account_io_start+0xd2/0x210 [ 271.845258] blk_mq_submit_bio+0x677/0x920 [ 271.846182] __submit_bio+0xad/0x250 [ 271.847022] submit_bio_noacct_nocheck+0x102/0x1d0 [ 271.848068] submit_bio_noacct+0x131/0x430 [ 271.848982] submit_bio+0xb3/0x110 [ 271.849782] ext4_io_submit+0x40/0x70 [ 271.850624] ext4_do_writepages+0x60a/0x970 [ 271.851546] ? psi_group_change+0x195/0x460 [ 271.852466] ext4_writepages+0xc8/0x1b0 [ 271.853325] ? ext4_writepages+0xc8/0x1b0 [ 271.854209] do_writepages+0xcb/0x180 [ 271.855038] ? write_inode+0x78/0x150 [ 271.855863] __writeback_single_inode+0x45/0x270 [ 271.856852] ? wbc_detach_inode+0x115/0x2c0 [ 271.857756] writeback_sb_inodes+0x25e/0x5e0 [ 271.858685] __writeback_inodes_wb+0x54/0x100 [ 271.859621] ? queue_io+0x13b/0x150 [ 271.860416] wb_writeback+0x2e0/0x370 [ 271.861223] wb_workfn+0x39e/0x470 [ 271.861987] process_one_work+0x1ac/0x3d0 [ 271.862851] worker_thread+0x1b8/0x360 [ 271.863671] ? __pfx_worker_thread+0x10/0x10 [ 271.864586] kthread+0xf7/0x130 [ 271.865304] ? __pfx_kthread+0x10/0x10 [ 271.866118] ret_from_fork+0x195/0x2a0 [ 271.866934] ? __pfx_kthread+0x10/0x10 [ 271.867743] ? __pfx_kthread+0x10/0x10 [ 271.868551] ret_from_fork_asm+0x1a/0x30 [ 271.869394] </TASK> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148534/+subscriptions
[Bug 2153412] Re: Boot failure in 24.04.4 LTS after 6.8.0-117-generic upgrade
** Changed in: linux (Ubuntu) Status: New => 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/2153412 Title: Boot failure in 24.04.4 LTS after 6.8.0-117-generic upgrade Status in linux package in Ubuntu: Fix Committed Bug description: Failure to boot system with three monitors and NVIDIA driver. Freezes at black screen or screen with Ubuntu text. Diagnostics (ChatGPT assisted) included this conclusion: +++Diagnostic+++ The failed boot’s journal simply stops abruptly at 09:25:12, while systemd is still in very early boot, just after starting Plymouth and flushing the journal to disk. There is no later evidence of reaching normal multi-user startup, let alone GDM. That makes this look like a hard freeze during early boot: The NVIDIA 470 modules do load. The machine then continues briefly through early device and systemd initialization. Logging stops suddenly before the display manager starts. (A separate user with Ubuntu 24.04.4, kernel 6.8.0-117, and an older NVIDIA GT 710 reports a strikingly similar failure, with 6.8.0-111 still working.) Kernel 6.8.0-117 is likely triggering a low-level regression on older NVIDIA 470-series systems, causing a freeze during early graphics- related boot initialization. ++++++++++summary+++++++++++++ Regression: 6.8.0-111-generic boots; 6.8.0-117-generic hard-freezes. GPU/driver: GeForce GT 730 GK208B, nvidia-driver-470 470.256.02. Symptoms: DP screens black/frozen splash, DVI screen multicolored stripes. Logs: NVIDIA module loads successfully; journal stops abruptly during early boot before GDM. Topology test: unplugging DVI or DisplayPort did not change the failure. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-111-generic 6.8.0-111.111 ProcVersionSignature: Ubuntu 6.8.0-111.111-generic 6.8.12 Uname: Linux 6.8.0-111-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: rae 3431 F.... wireplumber /dev/snd/controlC0: rae 3431 F.... wireplumber /dev/snd/controlC1: rae 3431 F.... wireplumber /dev/snd/seq: rae 3429 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 20 12:08:11 2026 InstallationDate: Installed on 2019-11-08 (2385 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lo no wireless extensions. eno1 no wireless extensions. MachineType: HP HP EliteDesk 800 G5 TWR ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-111-generic root=UUID=f85bdd6e-e36e-4cc1-a8a1-0063ccb67b0d 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-111-generic N/A linux-backports-modules-6.8.0-111-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/28/2021 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: R01 Ver. 02.12.00 dmi.board.name: 8591 dmi.board.vendor: HP dmi.board.version: KBC Version 08.98.00 dmi.chassis.asset.tag: CZC939FL6Q dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 8.152 dmi.modalias: dmi:bvnHP:bvrR01Ver.02.12.00:bd12/28/2021:br12.0:efr8.152:svnHP:pnHPEliteDesk800G5TWR:pvr:rvnHP:rn8591:rvrKBCVersion08.98.00:cvnHP:ct3:cvr:sku6BD61AV: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G5 TWR dmi.product.sku: 6BD61AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2153412/+subscriptions
[Bug 2149766] Re: Linux kernel 6.17.0-22.22 breaks amdxdna
This bug is awaiting verification that the linux-xilinx/6.8.0-1030.31 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-xilinx' to 'verification-done- noble-linux-xilinx'. If the problem still exists, change the tag 'verification-needed-noble-linux-xilinx' to 'verification-failed-noble- linux-xilinx'. 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-xilinx-v2 verification-needed-noble-linux-xilinx -- 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: Fix Committed Status in linux-hwe-6.17 package in Ubuntu: Confirmed Status in linux-oem-6.17 package in Ubuntu: Confirmed Status in linux source package in Noble: Fix Released Status in linux-hwe-6.17 source package in Noble: Fix Released Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Questing: Fix Released Status in linux-hwe-6.17 source package in Questing: Invalid Status in linux-oem-6.17 source package in Questing: Invalid 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 2155198] Re: Jammy update: v5.15.201 upstream stable release
** 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/2155198 Title: Jammy update: v5.15.201 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.201 upstream stable release from git://git.kernel.org/ crypto: octeontx - Fix length check to avoid truncation in ucode_load_store crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly crypto: virtio - Add spinlock protection with virtqueue notification nilfs2: Fix potential block overflow that cause system hang scsi: qla2xxx: Validate sp before freeing associated memory scsi: qla2xxx: Delay module unload while fabric scan in progress scsi: qla2xxx: Query FW again before proceeding with login gpio: omap: do not register driver in probe() ALSA: hda/realtek: Fix headset mic for TongFang X6AR55xU gpio: sprd: Change sprd_gpio lock to raw_spin_lock romfs: check sb_set_blocksize() return value drm/tegra: hdmi: sor: Fix error: variable ‘j’ set but not used platform/x86: classmate-laptop: Add missing NULL pointer checks platform/x86: panasonic-laptop: Fix sysfs group leak in error path gpiolib: acpi: Fix gpio count with string references Revert "wireguard: device: enable threaded NAPI" btrfs: fix racy bitfield write in btrfs_clear_space_info_full() net: dsa: free routing table on probe failure selftests: mptcp: pm: ensure unknown flags are ignored mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() crypto: virtio - Remove duplicated virtqueue_kick in virtio_crypto_skcipher_crypt_req smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection() bus: fsl-mc: Replace snprintf and sprintf with sysfs_emit in sysfs show functions bus: fsl-mc: fix use-after-free in driver_override_show() scsi: qla2xxx: Fix bsg_done() causing double free scsi: qla2xxx: Use named initializers for port_[d]state_str scsi: qla2xxx: Remove dead code (GNN ID) scsi: qla2xxx: Reduce fabric scan duplicate code scsi: qla2xxx: Free sp in error path to fix system crash PCI: endpoint: Automatically create a function specific attributes group PCI: endpoint: Remove unused field in struct pci_epf_group PCI: endpoint: Avoid creating sub-groups asynchronously fbdev: rivafb: fix divide error in nv3_arb() fbdev: smscufx: properly copy ioctl memory to kernelspace f2fs: fix to avoid UAF in f2fs_write_end_io() f2fs: fix out-of-bounds access in sysfs attribute read/write USB: serial: option: add Telit FN920C04 RNDIS compositions Linux 5.15.201 UBUNTU: Upstream stable to v5.15.201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155198/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-ibm-6.8/6.8.0-1058.59~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-ibm-6.8 (6.8.0-1058.59~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-ibm-6.8 [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
вторник
[Bug 2155117] [NEW] Hibernation fail
Public bug reported: I need to hard stop the computer to restart. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Jun 3 08:43:20 2026 HibernationDevice: RESUME=UUID=de72cf33-6e73-400a-a963-810f483fe78a InstallationDate: Installed on 2025-04-19 (410 days ago) InstallationMedia: Ubuntu-Studio 25.04 "Plucky Puffin" - Release amd64 (20250415.2) MachineType: ASUSTeK COMPUTER INC. ASUS Vivobook S 15 M5506WA_M5506WA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=de72cf33-6e73-400a-a963-810f483fe78a ro quiet splash resume=UUID=de72cf33-6e73-400a-a963-810f483fe78a resume_offset=6623232 preempt=full threadirqs rcu_nocbs=all usbcore.autosuspend=-1 amd_pmc.disable_ps0_barrier=1 preempt=full threadirqs rcu_nocbs=all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-14 (20 days ago) dmi.bios.date: 01/05/2026 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: M5506WA.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M5506WA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.10 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrM5506WA.316:bd01/05/2026:br5.35:efr3.10:svnASUSTeKCOMPUTERINC.:pnASUSVivobookS15M5506WA_M5506WA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5506WA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSVivobookS15: dmi.product.family: ASUS Vivobook S 15 dmi.product.name: ASUS Vivobook S 15 M5506WA_M5506WA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155117 Title: Hibernation fail Status in linux package in Ubuntu: New Bug description: I need to hard stop the computer to restart. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Jun 3 08:43:20 2026 HibernationDevice: RESUME=UUID=de72cf33-6e73-400a-a963-810f483fe78a InstallationDate: Installed on 2025-04-19 (410 days ago) InstallationMedia: Ubuntu-Studio 25.04 "Plucky Puffin" - Release amd64 (20250415.2) MachineType: ASUSTeK COMPUTER INC. ASUS Vivobook S 15 M5506WA_M5506WA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=de72cf33-6e73-400a-a963-810f483fe78a ro quiet splash resume=UUID=de72cf33-6e73-400a-a963-810f483fe78a resume_offset=6623232 preempt=full threadirqs rcu_nocbs=all usbcore.autosuspend=-1 amd_pmc.disable_ps0_barrier=1 preempt=full threadirqs rcu_nocbs=all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-14 (20 days ago) dmi.bios.date: 01/05/2026 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: M5506WA.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M5506WA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.10 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrM5506WA.316:bd01/05/2026:br5.35:efr3.10:svnASUSTeKCOMPUTERINC.:pnASUSVivobookS15M5506WA_M5506WA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5506WA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSVivobookS15: dmi.product.family: ASUS Vivobook S 15 dmi.product.name: ASUS Vivobook S 15 M5506WA_M5506WA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155117/+subscriptions
[Bug 2154418] Re: Backport ASoC SDCA, AMD SoundWire, and RT722 audio fixes
** Changed in: linux (Ubuntu Questing) Status: In Progress => Won't Fix -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154418 Title: Backport ASoC SDCA, AMD SoundWire, and RT722 audio fixes Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.17 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Noble: In Progress Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: In Progress Status in alsa-ucm-conf source package in Questing: In Progress Status in linux source package in Questing: Won't Fix Status in linux-oem-6.17 source package in Questing: Invalid Status in alsa-ucm-conf source package in Resolute: In Progress Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: SRU Justification: [ Impact ] Some newer audio configurations require SoundWire/SDCA updates for companion amplifier handling, AMD ACP7.0 Realtek match entries, Lenovo AMD SoundWire DMIC quirks, combined speaker component naming, and RT722 speaker mute control. Without these fixes, affected systems may fail to expose the expected audio topology, DMIC component naming, PCM numbering, or speaker mute switch needed by userspace/UCM. [ Fix ] Backport upstream commits: - f5cb3ee251b4 ("ASoC: SDCA: Add companion amp Function") - 7869f1c1123c ("ASoC: amd: acp: Add ACP7.0 match entries for Realtek parts") - 3acf517e1ae0 ("ASoC: amd: amd_sdw: add machine driver quirk for Lenovo models") - 68130eef1e0d ("ASoC: soc-component: re-add pcm_new()/pcm_free()") - fe33a69681e3 ("ASoC: amd: name back to pcm_new()/pcm_free()") - 5902e1f3c501 ("ASoC: amd: acp: update dmic_num logic for acp pdm dmic") - 371f6a1d2a97 ("ASoC: amd: acp-sdw-legacy: rename the dmic component name") - 3666dc0c47c3 ("ASoC: amd: ps: fix the pcm device numbering for acp pdm dmic") - 80a7916ca2d9 ("ASoC: amd: acp: add Lenovo P16s G5 AMD quirk for legacy SDW machine") - 6b6f7263d626 ("ASoC: amd: acp: update DMI quirk and add ACP DMIC for Lenovo platforms") - 87a3f5c8ac20 ("ASoC: sdw_utils: cs42l43: allow spk component names to be combined") - bda41dd5e1dd ("ASoC: rt722-sdca: add FU06 Playback Switch for speaker mute control") [ Test Plan ] Boot affected hardware and verify: 1. Sound card probes successfully. 2. Expected ALSA PCMs and controls are present. 3. DMIC capture works on affected AMD SoundWire platforms. 4. Speaker playback works. 5. Speaker mute control is exposed and can be toggled by userspace. [ Where problems could occur ] The changes affect ASoC SoundWire/SDCA machine matching, component naming, PCM setup, and RT722 codec mute handling. Regressions could appear as sound card probe failures, changed component strings affecting UCM matching, missing or renumbered PCM devices, or incorrect speaker mute behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2154418/+subscriptions
[Bug 2150196] Re: [SRU] ASoC: enable rt1320 speaker amp and DMIC on PTL SoundWire platforms
For resolute this fix is merged at kernel 7.0.0-26.26, currently it's not in proposed yet. linux (7.0.0-26.26) resolute; urgency=medium * resolute/linux: 7.0.0-26.26 -proposed tracker (LP: #2154530) * Packaging resync (LP: #1786013) - Revert "UBUNTU: SAUCE: import Huawei ES3000_V2 (2.1.0.23)" - [Packaging] debian.master/dkms-versions -- remove dkms-versions (main/2026.05.18) * Fix mic mute led on a HP EliteBook 6 G2a platform (LP: #2150065) - ALSA: hda/realtek: Add LED fixup for HP EliteBook 6 G2a Laptops * ov08x40 module mounted upside down on a certain DELL platforms (LP: #2146517) - SAUCE: media: ipu-bridge: Add DMI quirk for new Dell XPS laptops with upside down sensors - SAUCE: media: ipu-bridge: Add DMI quirk for Dell 14 laptops with upside down sensors * Support additional 2888x1808@30fps 900MHz for OVTI05C1 camera sensor (LP: #2147409) - SAUCE: media: ipu-bridge: Add 900MHz for OV05C10 - SAUCE: platform/x86: int3472: increase handshake delay to 50ms for OV05C10 * Support Samsung S5K3J1 sensor for Intel MIPI camera (LP: #2121852) - SAUCE: media: ipu-bridge: Support s5k3j1 sensor * [SRU] ASoC: enable rt1320 speaker amp and DMIC on PTL SoundWire platforms (LP: #2150196) - ASoC: Intel: soc-acpi-intel-ptl-match: drop rt722 monolithic match tables - ASoC: SOF: Intel: Add a is_amp flag to fix the wrong name prefix - ASoC: sdw_utils: add rt1320 and rt1321 dmic dai in codec_info_list -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150196 Title: [SRU] ASoC: enable rt1320 speaker amp and DMIC on PTL SoundWire platforms Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.17 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Noble: Fix Committed Status in linux source package in Noble: Won't Fix Status in linux-oem-6.17 source package in Noble: Fix Released Status in alsa-ucm-conf source package in Questing: Fix Committed Status in linux source package in Questing: New Status in linux-oem-6.17 source package in Questing: New Status in alsa-ucm-conf source package in Resolute: Fix Committed Status in linux source package in Resolute: Fix Committed Status in linux-oem-6.17 source package in Resolute: Invalid Status in alsa-ucm-conf source package in Stonking: Fix Released Status in linux source package in Stonking: Fix Committed Status in linux-oem-6.17 source package in Stonking: Invalid Bug description: SRU Justification: [ Impact ] Lenovo PTL systems with rt722 headset codec + rt1320 speaker amp over SoundWire have no speaker audio and no DMIC. The kernel's PTL match table lacks the rt722_l0_rt1320_l23 topology, the rt1320 codec_info_list is missing its DMIC dai, and the is_amp flag is absent -- so the machine driver never matches and the wrong name prefix is assigned. [ Fix ] Seven upstream commits from Linus's mainline, applied in topological order: 1. 38ecd1384079 (v6.19) -- add ptl_rt722_l0_rt1320_l23 match table entry 2. 4fbd3b2ec04d (v7.0) -- use aggregated endpoints for rt722 in that entry 3. 403a0591be68 (v6.19) -- fix name_prefix of second rt1320 (rt1320-2) 4. 754b3dade5dd (v7.0) -- drop rt721 monolithic match tables (prerequisite for 5) 5. 9033f7b7f27d (linux/master, not yet tagged) -- drop rt722 monolithic match tables 6. dd4a1963ddf0 (linux/master, not yet tagged) -- add is_amp flag to fix wrong name prefix 7. ae2cb3384337 (linux/master, not yet tagged) -- add rt1320/rt1321 DMIC dai in codec_info_list All cherry-pick cleanly with zero conflicts. Diffs are byte-identical to upstream (only hunk offsets and context lines differ due to different base tree). [ Test Plan ] On a Lenovo PTL system with spk:rt1320 + hs:rt722: 1. Boot without patches: no speaker sound card components, no DMIC 2. Boot with patches: - Speaker playback: aplay -D hw:0,2 tone.wav - DMIC loopback: play 1kHz tone through speaker, record from DMIC, FFT confirms peak at 1000 Hz - WirePlumber sees all devices - Mute LEDs functional (speaker and mic) - Suspend/resume: full status diff pre vs post identical, loopback and LEDs work after resume [ Where problems could occur ] Patches touch PTL match tables, SoundWire codec_info_list, and SOF HDA codec matching. A wrong match table entry could cause a different PTL topology to break (wrong codec matched). The is_amp flag override in find_acpi_adr_device() runs for all SoundWire codecs on Intel SOF platforms -- if the flag logic is wrong, non-amp codecs could get misidentified, breaking name prefixes and DAI routing. Commits 4-5 remove rt721/rt722 monolithic match tables; any PTL machine still relying on monolithic matching (rather than function topologies) would lose its match entry. [ Other Info ] Commits 5-7 are merged on linux/master but not yet in a tagged release. Tested on two Lenovo PTL machines -- full audio pass including loopback and suspend/resume. Target: oem-6.17 and resolute only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2150196/+subscriptions
[Bug 2150196] Re: [SRU] ASoC: enable rt1320 speaker amp and DMIC on PTL SoundWire platforms
Installed the 26.04 and enabled the proposed channel, but the speaker is Dummy and no mic device. $ uname -an Linux Bowser-SIT-S11 7.0.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Mon May 25 15:54:34 UTC 2026 x86_64 GNU/Linux $ apt-cache policy alsa-ucm-conf alsa-ucm-conf: Installed: 1.2.15.3-1ubuntu1.2 Candidate: 1.2.15.3-1ubuntu1.2 Version table: *** 1.2.15.3-1ubuntu1.2 100 100 http://archive.ubuntu.com/ubuntu resolute-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.2.15.3-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu resolute/main amd64 Packages -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150196 Title: [SRU] ASoC: enable rt1320 speaker amp and DMIC on PTL SoundWire platforms Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.17 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Noble: Fix Committed Status in linux source package in Noble: Won't Fix Status in linux-oem-6.17 source package in Noble: Fix Released Status in alsa-ucm-conf source package in Questing: Fix Committed Status in linux source package in Questing: New Status in linux-oem-6.17 source package in Questing: New Status in alsa-ucm-conf source package in Resolute: Fix Committed Status in linux source package in Resolute: Fix Committed Status in linux-oem-6.17 source package in Resolute: Invalid Status in alsa-ucm-conf source package in Stonking: Fix Released Status in linux source package in Stonking: Fix Committed Status in linux-oem-6.17 source package in Stonking: Invalid Bug description: SRU Justification: [ Impact ] Lenovo PTL systems with rt722 headset codec + rt1320 speaker amp over SoundWire have no speaker audio and no DMIC. The kernel's PTL match table lacks the rt722_l0_rt1320_l23 topology, the rt1320 codec_info_list is missing its DMIC dai, and the is_amp flag is absent -- so the machine driver never matches and the wrong name prefix is assigned. [ Fix ] Seven upstream commits from Linus's mainline, applied in topological order: 1. 38ecd1384079 (v6.19) -- add ptl_rt722_l0_rt1320_l23 match table entry 2. 4fbd3b2ec04d (v7.0) -- use aggregated endpoints for rt722 in that entry 3. 403a0591be68 (v6.19) -- fix name_prefix of second rt1320 (rt1320-2) 4. 754b3dade5dd (v7.0) -- drop rt721 monolithic match tables (prerequisite for 5) 5. 9033f7b7f27d (linux/master, not yet tagged) -- drop rt722 monolithic match tables 6. dd4a1963ddf0 (linux/master, not yet tagged) -- add is_amp flag to fix wrong name prefix 7. ae2cb3384337 (linux/master, not yet tagged) -- add rt1320/rt1321 DMIC dai in codec_info_list All cherry-pick cleanly with zero conflicts. Diffs are byte-identical to upstream (only hunk offsets and context lines differ due to different base tree). [ Test Plan ] On a Lenovo PTL system with spk:rt1320 + hs:rt722: 1. Boot without patches: no speaker sound card components, no DMIC 2. Boot with patches: - Speaker playback: aplay -D hw:0,2 tone.wav - DMIC loopback: play 1kHz tone through speaker, record from DMIC, FFT confirms peak at 1000 Hz - WirePlumber sees all devices - Mute LEDs functional (speaker and mic) - Suspend/resume: full status diff pre vs post identical, loopback and LEDs work after resume [ Where problems could occur ] Patches touch PTL match tables, SoundWire codec_info_list, and SOF HDA codec matching. A wrong match table entry could cause a different PTL topology to break (wrong codec matched). The is_amp flag override in find_acpi_adr_device() runs for all SoundWire codecs on Intel SOF platforms -- if the flag logic is wrong, non-amp codecs could get misidentified, breaking name prefixes and DAI routing. Commits 4-5 remove rt721/rt722 monolithic match tables; any PTL machine still relying on monolithic matching (rather than function topologies) would lose its match entry. [ Other Info ] Commits 5-7 are merged on linux/master but not yet in a tagged release. Tested on two Lenovo PTL machines -- full audio pass including loopback and suspend/resume. Target: oem-6.17 and resolute only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2150196/+subscriptions
[Bug 2154418] Re: Backport ASoC SDCA, AMD SoundWire, and RT722 audio fixes
** Merge proposal linked: https://code.launchpad.net/~mapengyu/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/505879 ** Merge proposal linked: https://code.launchpad.net/~mapengyu/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/505880 ** Merge proposal linked: https://code.launchpad.net/~mapengyu/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/505881 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154418 Title: Backport ASoC SDCA, AMD SoundWire, and RT722 audio fixes Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.17 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Noble: In Progress Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: In Progress Status in alsa-ucm-conf source package in Questing: In Progress Status in linux source package in Questing: In Progress Status in linux-oem-6.17 source package in Questing: Invalid Status in alsa-ucm-conf source package in Resolute: In Progress Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: SRU Justification: [ Impact ] Some newer audio configurations require SoundWire/SDCA updates for companion amplifier handling, AMD ACP7.0 Realtek match entries, Lenovo AMD SoundWire DMIC quirks, combined speaker component naming, and RT722 speaker mute control. Without these fixes, affected systems may fail to expose the expected audio topology, DMIC component naming, PCM numbering, or speaker mute switch needed by userspace/UCM. [ Fix ] Backport upstream commits: - f5cb3ee251b4 ("ASoC: SDCA: Add companion amp Function") - 7869f1c1123c ("ASoC: amd: acp: Add ACP7.0 match entries for Realtek parts") - 3acf517e1ae0 ("ASoC: amd: amd_sdw: add machine driver quirk for Lenovo models") - 68130eef1e0d ("ASoC: soc-component: re-add pcm_new()/pcm_free()") - fe33a69681e3 ("ASoC: amd: name back to pcm_new()/pcm_free()") - 5902e1f3c501 ("ASoC: amd: acp: update dmic_num logic for acp pdm dmic") - 371f6a1d2a97 ("ASoC: amd: acp-sdw-legacy: rename the dmic component name") - 3666dc0c47c3 ("ASoC: amd: ps: fix the pcm device numbering for acp pdm dmic") - 80a7916ca2d9 ("ASoC: amd: acp: add Lenovo P16s G5 AMD quirk for legacy SDW machine") - 6b6f7263d626 ("ASoC: amd: acp: update DMI quirk and add ACP DMIC for Lenovo platforms") - 87a3f5c8ac20 ("ASoC: sdw_utils: cs42l43: allow spk component names to be combined") - bda41dd5e1dd ("ASoC: rt722-sdca: add FU06 Playback Switch for speaker mute control") [ Test Plan ] Boot affected hardware and verify: 1. Sound card probes successfully. 2. Expected ALSA PCMs and controls are present. 3. DMIC capture works on affected AMD SoundWire platforms. 4. Speaker playback works. 5. Speaker mute control is exposed and can be toggled by userspace. [ Where problems could occur ] The changes affect ASoC SoundWire/SDCA machine matching, component naming, PCM setup, and RT722 codec mute handling. Regressions could appear as sound card probe failures, changed component strings affecting UCM matching, missing or renumbered PCM devices, or incorrect speaker mute behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2154418/+subscriptions
[Bug 2154785] Re: Enable device tree overlay configs for PCIe based devices
** 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/2154785 Title: Enable device tree overlay configs for PCIe based devices Status in linux package in Ubuntu: New Status in linux source package in Noble: New Status in linux source package in Questing: New Status in linux source package in Resolute: New Status in linux source package in Stonking: New Bug description: The following configuration options will allow PCIe FPGA devices to provide memory mapped access to IP cores in the same manner as FPGA- ARM based SoC solutions using existing drivers. - CONFIG_OF=y - CONFIG_OF_OVERLAY=y - CONFIG_DTC=y - CONFIG_PCI_DYNAMIC_OF_NODES=y This has been requested by AMD. Without these options enabled new drivers will need to be written just for the x86 platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154785/+subscriptions
[Bug 2149877] Re: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system
~sholeh-feathermoon Install 7.0.0-17 using this command: sudo apt install linux-generic/resolute-proposed And make sure to select the -17 kernel in your bootloader -- 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: Triaged Status in linux source package in Resolute: Triaged 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