[Bug 2148638] Re: ubuntu 26.04 - When the NVME hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized.

Could you please help test two kernels and compare the behavior? 1. Ubuntu mainline v7.1-rc3: https://kernel.ubuntu.com/mainline/v7.1-rc3/ Please check whether the NVMe hot-swap issue still reproduces there. 2. Our locally built test kernel with the proposed PCI hotplug fix [1]. The goal is to distinguish: - whether the issue is already fixed by upstream changes present in v7.1-rc3, or - whether the test kernel fixed it. If v7.1-rc3 still reproduces the issue, but the test kernel does not, that would strongly confirm the proposed fix is addressing the regression. [1] https://drive.google.com/file/d/1P2dOpqIVFteossNZhgWdzOO4zmBPsdoY/view?usp=sharing -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148638 Title: ubuntu 26.04 - When the NVME hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized. Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: When the CD8P NVMe hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized. This issue happens on CD8P NVMe disk and does not happens on bm1743 NVMe disk. CD8P drives are Kaoxia drives The BM1743 drives that work are Samsung devices. Nvme disk detail: CD8P https://lenovopress.lenovo.com/lp1904-thinksystem-cd8p-read-intensive-nvme-pcie-50-ssd bm1743 https://lenovopress.lenovo.com/lp2156-thinksystem-bm1743-read-intensive-nvme-pcie-50-x4-ssd Steps to reproduce: 1.In the UEFI, enable VMD without created RAID disk. 2.Install ubuntu26.04 on M.2 sata disk. 3.use command lsblk to check all NVMEe disk 4.Unplug all NVMe device, then check NVMe device information again via lsblk. 5.plug all NVMe SSD 6.OS reported an error and some of the drives were not recognized. Compare with Ubuntu 24.04: There is no errors messages and all NVMe disks can be recognized after re-plug all NVMe SSD Info: The issue also happens on latest daily build: 0415 This issue only happens on VMD enabled, there is no this issue when vmd feature disable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148638/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-lowlatency/5.15.0-178.188+2)

All autopkgtests for the newly accepted linux-restricted-modules-lowlatency (5.15.0-178.188+2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf) nvidia-graphics-drivers-390/unknown (i386) nvidia-graphics-drivers-470/unknown (amd64) nvidia-graphics-drivers-470-server/unknown (amd64) nvidia-graphics-drivers-525-server/unknown (amd64, arm64) 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-lowlatency [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 2152924] [NEW] Intermittent system freezes - unsure if kernel-related

You have been subscribed to a public bug: I have been experiencing intermittent system freezes on my Ubuntu installation. I'm not entirely sure if this is a Linux kernel issue or hardware-related, especially since I recently had my computer cleaned. About me: I've been using Ubuntu for 15 years and I'm a programmer, though I primarily use the system as a regular user and work with my own programming languages rather than deep Linux scripting. I want to help improve Ubuntu by reporting issues, but I'm not entirely sure if I'm following the correct procedure. I used AI assistance to help me write this bug report as I want to contribute properly to the community. I apologize if this report is not in the correct format or if this is not a kernel issue. I'm Brazilian and don't speak English fluently, so this report was translated. I hope this information can help identify the issue. Any guidance on proper bug reporting would be appreciated. Best regards. This ZIP file only contains screenshots related to the freezes and crashes I experienced on Ubuntu. Screenshot 1: Browser/system freeze while using Google Calendar. The system became unresponsive even though only about 17% of the 48 GB RAM was being used. Screenshot 2: Ubuntu session crash message appearing after the freeze, asking to close the session automatically. Screenshot 3: Black screen with multiple SQUASHFS and read errors displayed after the crash. None of the screenshots contain sensitive information and they may be used for troubleshooting or debugging purposes. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: joh 6442 F.... wireplumber /dev/snd/controlC0: joh 6442 F.... wireplumber /dev/snd/controlC2: joh 6442 F.... wireplumber /dev/snd/seq: joh 6420 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 18 13:25:10 2026 InstallationDate: Installed on 2026-05-03 (15 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS System Product Name ProcEnviron: LANG=pt_BR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=7e6dc25f-8a2d-437b-acfb-95edbb86efd4 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2020 dmi.bios.release: 10.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1003 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B460-G GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1003:bd11/30/2020:br10.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB460-GGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- Intermittent system freezes - unsure if kernel-related https://bugs.launchpad.net/bugs/2152924 You received this bug notification because you are subscribed to linux in Ubuntu.

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-hwe-7.0/7.0.0-14.14~24.04.3+3)

All autopkgtests for the newly accepted linux-restricted-modules-hwe-7.0 (7.0.0-14.14~24.04.3+3) for noble have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-470/unknown (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/noble/update_excuses.html#linux-restricted-modules-hwe-7.0 [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 2153155] Re: Fix bad audio record quality when volume above 50% on Framework PTL

** Summary changed: - Fix bad audio record quality when volume above 50% on Framwork PTL + Fix bad audio record quality when volume above 50% on Framework PTL -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2153155 Title: Fix bad audio record quality when volume above 50% on Framework PTL Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: In Progress Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Framework PTL platform with Realtek ALC295 audio solution will have audio recording quality when the input volume is configure > 50%. [Fix] Fix by backporting the commit: 67c738152207 ("67c738152207") which fix mic boost on particular SSIDs of the Framework machines [Test Case] 1. Boot up the machine of new Framework PTL platforms with Realtek ALC295 audio solution 2. Go to g-s-d and select sound --> input (Internal Microphone) --> Adjust the input volume > 50% 3. Do `arecord` with the internal microphone and play the recorded clips. [Where problems could occur] It only limit the mic boost based on particular SSIDs. The risk of regression is limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2153155/+subscriptions

[Bug 2149770] Re: ALSA: hda/tas2781 Audio Fix for the front-right speacker

** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Assignee: AceLan Kao (acelankao) => (unassigned) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149770 Title: ALSA: hda/tas2781 Audio Fix for the front-right speacker Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Audio is still wrong on some HP systems with TAS2781 SPI audio. LP#2141639 fixed the earlier case where the front-right speaker had no audio because firmware download was skipped during SPI probe. That fix is already in linux-oem-6.17. But the same TAS2781 SPI path still has problems on other HP systems. After the earlier fix, the right speaker may work but sound is still abnormal, unclear, or lower than the left speaker. This hits multiple HP systems and shows 100% repro with: $ speaker-test -c 2 -l 1 -t wav The issue is in TAS2781 SPI calibration and firmware handling, not only the old reset check from LP#2141639. [Fix] Backport the upstream TAS2781 follow-up fixes needed for HP SPI systems. The branch contains these 7 commits: - dcc0899e6b8e9 ASoC: tas2781: Put three different calibrated data solution into the same data structure upstream: 55137f5a68b5e888504ad36d07221cd749bb8956 upstream version: v7.0 - 9dfa6c7d268c8 ALSA: hda/tas2781: A workaround solution to lower-vol issue among lower calibrated-impedance micro-speaker on TAS2781 upstream: 05ac3846ffe53fc63e454eb195ce8a6bab7a6a88 upstream version: v7.0 - 1550e33f1018b ASoC: tas2781: Add null check for calibration data upstream: a437601a0a1383260222223440a95dd4322eb7fa upstream version: v7.0 - 44024094a8751 PM: runtime: Add auto-cleanup macros for "resume and get" operations upstream: 9a0abc39450a3123fd52533a662fbd37e0d1508c upstream version: v6.18 - 03c1a0855d20b ALSA: hda/tas2781: Clean up runtime PM with guard() upstream: 4a91da4afc7db944d17234e4ecc164df8252b23b upstream version: v7.0 - e17bde0ac6f53 ALSA: hda/tas2781: Add tas2781hda::catlogid init upstream: e4808c60b1b1548631041c7db60da06b7d3a3662 upstream version: v7.0 - 94b777bf01bad ALSA: hda/tas2781: Fix sound abnormal issue on some SPI device upstream: 055e3fcc66caee8ae470c98e06120b494c95525b upstream version: not tagged yet in this tree, merged in linux-next These patches extend the earlier LP#2141639 fix. They initialize the SPI TAS2781 path correctly for HP systems, fix catalog/chip setup, use the right bulk read path for SPI calibration data, add missing safety checks, and include the calibration update used to avoid low or unclear right-speaker output. Together they address the remaining TAS2781 SPI issues seen on HP systems after LP#2141639. [Test Plan] On an affected HP system with TAS2781 SPI audio: 1. Boot the patched kernel. 2. Run: $ speaker-test -c 2 -l 1 -t wav 3. Listen to left and right speakers separately. 4. Check kernel log for TAS2781 errors: $ dmesg | grep -i tas2781 Without these patches: - the old LP#2141639 fix may restore audio on some systems only - on other systems the right speaker may still sound unclear, abnormal, or lower than the left one With these patches: - both speakers produce audio - the right speaker no longer shows the abnormal SPI calibration behavior reported in STELLA-3075 - no new TAS2781 firmware or calibration errors show up in dmesg [Where problems could occur] These changes touch the TAS2781 HDA/SPI path, TAS2781 calibration handling, and runtime PM helpers. If the SPI calibration path is wrong, HP systems with TAS2781 could still get bad speaker balance, distorted output, or no audio on one channel. If the chipid or catlogid setup is wrong, firmware or calibration data may not be loaded correctly for SPI devices. If the runtime PM related changes are wrong, audio init or resume could fail and the codec may not be available after boot or resume. Regression would show up as TAS2781 probe failures, missing firmware/calibration behavior, no sound from one speaker, or lower/unclear output from one side. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2149770/+subscriptions

[Bug 2150730] Re: kernel null pointer BUG in 5.15 when disconnecting from cifs share

** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Importance: High => Undecided ** Changed in: linux (Ubuntu) Assignee: Ghadi Rahme (ghadi-rahme) => (unassigned) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Ghadi Rahme (ghadi-rahme) ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150730 Title: kernel null pointer BUG in 5.15 when disconnecting from cifs share Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Bug description: [Impact] There is currently a bug in the 5.15 jammy kernel that causes a system crash and has a chance to occur when the connection to a CIFS share drops. The stack trace can be seen below: BUG: kernel NULL pointer dereference, address: 0000000000000050 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 1013dc64067 P4D 10125f65067 PUD 10125f64067 PMD 0 Oops: 0000 [#1] SMP NOPTI CPU: 80 PID: 3913754 Comm: kworker/u256:1 Kdump: loaded Not tainted 5.15.0-143-generic #153-Ubuntu Hardware name: Dell Inc. PowerEdge R760/09XV41, BIOS 2.3.5 09/10/2024 Workqueue: cifs-dfscache refresh_cache_worker [cifs] RIP: 0010:strcasecmp+0x19/0x50 Code: 01 84 c9 75 f1 c3 cc cc cc cc 0f 1f 80 00 00 00 00 49 89 f9 31 ff 41 0f b6 04 39 0f b6 c8 89 c2 83 c2 20 f6 81 e0 39 89 85 01 <0f> b6 0c 3e 0f b6 d2 0f 45 c2 89 ca 44 0f b6 c1 83 c2 20 41 f6 80 RSP: 0018:ff4043e68aadb900 EFLAGS: 00010246 RAX: 000000000000005c RBX: ff4043e68aadbc68 RCX: 000000000000005c RDX: 000000000000007c RSI: 0000000000000050 RDI: 0000000000000000 RBP: ff4043e68aadb990 R08: 0000000000000064 R09: ff4043e68aadb91f R10: 0000000000000012 R11: 0000000000000000 R12: ff210c171f193c00 R13: 0000000000000009 R14: 0000000000000008 R15: ff210d1d3f19a7c0 FS: 0000000000000000(0000) GS:ff210d127fc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000050 CR3: 0000011f2cc38005 CR4: 0000000000771ee0 PKRU: 55555554 Call Trace: <TASK> ? find_ipc_from_server_path+0xd9/0x110 [cifs] refresh_cache+0xf1/0x470 [cifs] ? in4_pton+0x7a/0x160 ? kfree+0x1f7/0x250 ? target_share_equal+0x198/0x210 [cifs] ? __refresh_tcon.isra.0+0x242/0x670 [cifs] ? kfree+0x1f7/0x250 ? __refresh_tcon.isra.0+0x242/0x670 [cifs] ? cifs_put_tcon.part.0+0x39/0x220 [cifs] ? cifs_put_tcon+0x1c/0x30 [cifs] ? refresh_mounts+0x147/0x210 [cifs] refresh_cache_worker+0x1ac/0x300 [cifs] ? lock_timer_base+0x3b/0xd0 process_one_work+0x228/0x3d0 worker_thread+0x53/0x420 ? process_one_work+0x3d0/0x3d0 kthread+0x127/0x150 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x1f/0x30 </TASK> The issue only affects the 5.15 kernel and not latest upstream since it has been indirectly resolved as part of a refactor in commit [6916881f443f cifs: fix refresh of cached referrals]. However backporting this patch to 5.15 is not feasible due to how complicated it is and it also requires extra commits to be backported to apply cleanly. The regression potential is also high. I have tested two different patches to resolve the issue. One that narrows down the BUG occurrence to a window so small that it becomes extremely hard to hit. And another that completely resolves it using spin_locks. I prefer the first solution since it strikes balance of being good enough with extremely low regression potential. It is also minimizes deviation from upstream. After sending the original patch to the linux stable mailing list, it was put on hold to wait on a response from the CIFS maintainers: https://lore.kernel.org/stable/20260319144929.455978-1-ghadi.rahme@canonical.com/ However they never answered and I sent another email to CIFS mailing list which also saw no activity: https://lore.kernel.org/linux- cifs/119442fa-7630-482f-ad0a-83c7f61f8786@canonical.com/ This is why I have decided to go with the Ubuntu SAUCE patch to resolve this issue in Ubuntu. The way the patch works is simple, it will make sure that a tcon is actually still available and being held by the session before accessing it in strcasecmp. [ Test Plan ] 1. Connect to a CIFS share on jammy using kernel 5.15. 2. Cause network disruption that would make the CIFS share connect and disconnect often 3. With the current kernel the machine will eventually crash, however if the patch fixes the problem the machine should remain up and running. [ Where problems could occur ] The regression potential is low since the code path would crash in a scenario where the tcon is null. The function does handle the error scenario where no entry is found correctly. This means that there is a chance of another bug or crash being hit in the calling function if it does not handle this error code appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150730/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-lowlatency/5.15.0-178.188+1)

All autopkgtests for the newly accepted linux-restricted-modules-lowlatency (5.15.0-178.188+1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf) 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-lowlatency [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 2153431] Re: xhci_hcd: continuous SuperSpeed USB resets with ASMedia 174c:235c (TerraMaster D4-320) on 6.8.0-117, regression from 6.8.0-111

** 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/2153431 Title: xhci_hcd: continuous SuperSpeed USB resets with ASMedia 174c:235c (TerraMaster D4-320) on 6.8.0-117, regression from 6.8.0-111 Status in linux package in Ubuntu: New Bug description: Summary ------- After a kernel update from 6.8.0-111-generic to 6.8.0-117-generic on Ubuntu 24.04 (noble), a USB-attached 4-bay DAS enclosure (TerraMaster D4-320, ASMedia 174c:235c bridges behind a Realtek 0bda:0423 hub) entered a continuous xhci_hcd reset loop. Booting back into 6.8.0-111-generic on identical hardware completely resolves the issue. This appears to be a regression introduced somewhere in the 6.8.0-112/-114/-116/-117 range. Impact ------ On 6.8.0-117, one downstream bay resets roughly 1.5 times per second continuously, even with the array idle and no I/O queued. Under write load the resets cause I/O timeouts (-110/DID_ERROR), failed writes (-28 / ENOSPC in the write path due to stalled drains), and XFS writeback errors. Left running, this risks filesystem corruption. The drives themselves are healthy (SMART PASSED, zero reallocated/pending/uncorrectable sectors, zero UDMA CRC errors). Reproducibility --------------- 100% reproducible across multiple cold boots: - 6.8.0-117-generic: ~280-600 reset events within the first few minutes of uptime, drives idle, array deactivated. Reset count climbs continuously. - 6.8.0-111-generic: zero reset events. Bus completely stable, including under sustained heavy write load (24/7 NVR workload, ~14 video streams). Same enclosure, same USB-C cable, same drives, same port. Only the kernel version differs. Hardware -------- Host USB: xHCI (Bus 004, 10 Gbit root hub) Enclosure: TerraMaster D4-320 - Internal hub: Realtek 0bda:0423 (4-Port USB 3.2 Hub) - 4x bridge: ASMedia Technology Inc. TDAS, 174c:235c, bcdDevice 1.00 Kernel applies these quirks automatically for 174c:235c: "UAS is ignored for this device, using usb-storage instead" "Quirks match for vid 174c pid 235c: 800000" (US_FL_NO_REPORT_OPCODES) Drives: 2x Seagate Exos 22TB + 2x 12TB, LVM RAID1, XFS. Representative dmesg (6.8.0-117, drives idle) --------------------------------------------- usb 4-2.1: reset SuperSpeed Plus Gen 2x1 USB device number 4 using xhci_hcd usb 4-2.1: reset SuperSpeed Plus Gen 2x1 USB device number 4 using xhci_hcd (repeating ~1.5x/sec continuously) Under load it escalates to: sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK I/O error, dev sdc, sector ... op 0x1:(WRITE) dm-5: writeback error on inode ... Workaround ---------- Boot 6.8.0-111-generic and pin it (apt-mark hold). Stable indefinitely. Notes for triage ---------------- The reset loop occurs at the xhci_hcd layer with the device on the conservative usb-storage driver (UAS already disabled by quirk), so this is not a UAS-path issue. The regression window is 6.8.0-112 through -117. Suspect area: xHCI transfer-event / endpoint-reset handling or link power management changes backported into the noble 6.8 tree in that window. Happy to bisect or test candidate kernels if useful. 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 AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-111-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed May 20 09:20:05 2026 InstallationDate: Installed on 2026-03-01 (80 days ago) InstallationMedia: Ubuntu-Server 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: AZW EQ ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-111-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro usb-storage.quirks=174c:235c:u 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: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 07/21/2025 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: EQI12D405 dmi.board.asset.tag: Default string dmi.board.name: EQ dmi.board.vendor: AZW dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrEQI12D405:bd07/21/2025:br5.27:svnAZW:pnEQ:pvrDefaultstring:rvnAZW:rnEQ:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: EQ dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: AZW To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2153431/+subscriptions

[Bug 2137457] Re: system runs out of memory after loading many corrupt apparmor profiles

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2137457 Title: system runs out of memory after loading many corrupt apparmor profiles Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu questing AMD64, 8GB memory with 6.17.0-8-generic run stress-ng with AppArmor stressor for ~5-10 mins, system runs out of memory. How to reproduce issue: use latest stress-ng from https://launchpad.net/~colin- king/+archive/ubuntu/stress-ng sudo add-apt-repository ppa:colin-king/stress-ng sudo apt-get update sudo apt-get install stress-ng sudo stress-ng --klog-check -v --apparmor 1 after a while one gets: stress-ng: debug: [1628] invoked with './stress-ng --klog-check -v --apparmor 1' by user 0 'root' stress-ng: debug: [1628] stress-ng 0.20.00 gf9ac1ba95c22 stress-ng: debug: [1628] system: Linux questing-amd64 6.17.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 14 21:44:46 UTC 2025 x86_64, gcc 15.2.0, glibc 2.42, little endian stress-ng: debug: [1628] RAM total: 7.3G, RAM free: 6.2G, swap free: 2.8G stress-ng: debug: [1628] temporary file path: '/home/cking/stress-ng', filesystem type: ext4 (892311 blocks available, /dev/dm-0) stress-ng: debug: [1628] 8 processors online, 8 processors configured stress-ng: info: [1628] defaulting to a 1 day run per stressor stress-ng: debug: [1628] CPU data cache: L1: 32K, L2: 4096K, L3: 16384K stress-ng: debug: [1628] cache allocate: shared cache buffer size: 16384K stress-ng: info: [1628] dispatching hogs: 1 apparmor stress-ng: debug: [1628] starting stressor stress-ng: debug: [1628] 1 stressor started stress-ng: debug: [1630] apparmor: [1630] started (instance 0 on CPU 4) stress-ng: info: [1629] klog-check: kernel cmdline: 'BOOT_IMAGE=/vmlinuz-6.17.0-8-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M' stress-ng: info: [1629] klog-check: warning: [104.610917] 'stress-ng-appar invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=-1000' stress-ng: info: [1629] klog-check: warning: [104.610923] 'CPU: 2 UID: 0 PID: 1634 Comm: stress-ng-appar Not tainted 6.17.0-8-generic #8-Ubuntu PREEMPT(voluntary) ' stress-ng: info: [1629] klog-check: warning: [104.610925] 'Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014' stress-ng: info: [1629] klog-check: warning: [104.610926] 'Call Trace:' stress-ng: info: [1629] klog-check: warning: [104.610927] ' <TASK>' stress-ng: info: [1629] klog-check: warning: [104.610930] ' show_stack+0x49/0x60' stress-ng: info: [1629] klog-check: warning: [104.610934] ' dump_stack_lvl+0x5f/0x90' stress-ng: info: [1629] klog-check: warning: [104.610937] ' dump_stack+0x10/0x18' stress-ng: info: [1629] klog-check: warning: [104.610949] ' dump_header+0x48/0x1be' stress-ng: info: [1629] klog-check: warning: [104.610950] ' oom_kill_process.cold+0x8/0xac' stress-ng: info: [1629] klog-check: warning: [104.610951] ' out_of_memory+0xff/0x2b0' stress-ng: info: [1629] klog-check: warning: [104.610954] ' __alloc_pages_may_oom+0x10a/0x1d0' stress-ng: info: [1629] klog-check: warning: [104.610956] ' __alloc_pages_slowpath.constprop.0+0x40e/0x990' stress-ng: info: [1629] klog-check: warning: [104.610957] ' __alloc_frozen_pages_noprof+0x341/0x360' stress-ng: info: [1629] klog-check: warning: [104.610958] ' alloc_pages_mpol+0x88/0x1b0' stress-ng: info: [1629] klog-check: warning: [104.610960] ' folio_alloc_mpol_noprof+0x14/0x40' stress-ng: info: [1629] klog-check: warning: [104.610961] ' __read_swap_cache_async+0x16c/0x260' stress-ng: info: [1629] klog-check: warning: [104.610963] ' swap_cluster_readahead+0x20a/0x310' stress-ng: info: [1629] klog-check: warning: [104.610963] ' swapin_readahead+0x75/0x100' stress-ng: info: [1629] klog-check: warning: [104.610964] ' do_swap_page+0x227/0x1010' stress-ng: info: [1629] klog-check: warning: [104.610966] ' ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0' stress-ng: info: [1629] klog-check: warning: [104.610967] ' ? do_syscall_64+0xb9/0xc90' stress-ng: info: [1629] klog-check: warning: [104.610970] ' ? __pfx_default_wake_function+0x10/0x10' stress-ng: info: [1629] klog-check: warning: [104.610971] ' handle_pte_fault+0x1b9/0x1f0' stress-ng: info: [1629] klog-check: warning: [104.610972] ' __handle_mm_fault+0x59d/0x720' stress-ng: info: [1629] klog-check: warning: [104.610974] ' handle_mm_fault+0xe7/0x2f0' stress-ng: info: [1629] klog-check: warning: [104.610975] ' do_user_addr_fault+0x22b/0x6c0' stress-ng: info: [1629] klog-check: warning: [104.610977] ' exc_page_fault+0x7f/0x1b0' stress-ng: info: [1629] klog-check: warning: [104.610978] ' asm_exc_page_fault+0x27/0x30' stress-ng: info: [1629] klog-check: warning: [104.610979] 'RIP: 0033:0x750ea1eb137f' stress-ng: info: [1629] klog-check: warning: [104.610981] 'Code: 9d 38 ee ff ff e9 9c fc ff ff e8 cc 3c 09 00 90 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 8b 4f 08 48 89 c8 48 83 e0 f8 48 89 e5 <48> 3b 04 07 0f 85 9e 00 00 00 48 8b 47 10 48 3b 78 18 75 75 48 8b' stress-ng: info: [1629] klog-check: warning: [104.610981] 'RSP: 002b:00007ffdd4d66fd0 EFLAGS: 00010206' stress-ng: info: [1629] klog-check: warning: [104.610983] 'RAX: 00000000000002f0 RBX: 0000750ea2034fc0 RCX: 00000000000002f1' stress-ng: info: [1629] klog-check: warning: [104.610983] 'RDX: 0000750ea2034e00 RSI: 0000000000408000 RDI: 0000596c2fa8fd60' stress-ng: info: [1629] klog-check: warning: [104.610984] 'RBP: 00007ffdd4d66fd0 R08: 0000000000000118 R09: 0000750ea2034b20' stress-ng: info: [1629] klog-check: warning: [104.610984] 'R10: 0000000000000120 R11: 0000750ea2034ac0 R12: 00000000000002f0' Looks like the apparmor profiles being loaded/unloaded eat up memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2137457/+subscriptions

[Bug 2153143] Re: No internal audio on ASUS FA401EA with AMD ACP70; only HDMI/Dummy Output

*** This bug is a duplicate of bug 2147585 *** https://bugs.launchpad.net/bugs/2147585 ** This bug has been marked a duplicate of bug 2147585 No sound from AMD ACP70 audio on ASUS TUF Gaming A14 FA401EA (Ryzen AI MAX+) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2153143 Title: No internal audio on ASUS FA401EA with AMD ACP70; only HDMI/Dummy Output Status in linux package in Ubuntu: New Bug description: Internal speakers and headphone jack are not detected on ASUS FA401EA. Hardware: - Laptop: ASUS FA401EA - AMD Audio Coprocessor / ACP70: 1022:15e2 - ASUS subsystem: 1043:1724 - Kernel: 7.0.0-15-generic - Ubuntu: 26.04 LTS Symptoms: - PipeWire shows only Dummy Output - ALSA only lists HDMI audio - Internal speaker/headphone device is missing - `aplay -l` only shows: card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] - `lspci -nn -s 64:00.5 -v` shows: Advanced Micro Devices, Inc. [AMD] Audio Coprocessor [1022:15e2] (rev 70) Subsystem: ASUSTeK Computer Inc. Device [1043:1724] Kernel driver in use: snd_acp_pci Expected result: Internal speakers and headphone jack should appear as an ALSA/PipeWire audio output. Actual result: Only HDMI audio is detected, and PipeWire falls back to Dummy Output. This appears related to existing bug 2147585: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147585 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: michal 5932 F.... wireplumber /dev/snd/seq: michal 5913 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 19 13:48:48 2026 InstallationDate: Installed on 2026-05-15 (4 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS TUF Gaming A14 FA401EA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=cc038677-d8bf-442c-972a-ebd7c63e618c ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2026 dmi.bios.release: 5.36 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FA401EA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA401EA 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.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFA401EA.304:bd01/28/2026:br5.36:efr3.3:svnASUS:pnTUFGamingA14FA401EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA401EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaTUFGamingA14: dmi.product.family: TUF Gaming A14 dmi.product.name: TUF Gaming A14 FA401EA dmi.product.version: 1.0 dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2153143/+subscriptions

[Bug 2153112] Re: Suspend crash on Lenovo Legion with NVIDIA: kernel BUG in nvidia_modeset nvkms_kthread_q_callback on 7.0.0-15-generic

** Changed in: linux (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** 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/2153112 Title: Suspend crash on Lenovo Legion with NVIDIA: kernel BUG in nvidia_modeset nvkms_kthread_q_callback on 7.0.0-15-generic Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 26.04, my Lenovo Legion laptop crashes when entering suspend, especially when closing the lid. The crash also appears reproducible via systemd-sleep / suspend, so this does not seem to be only a lid-switch issue. The kernel log shows the crash happens immediately after suspend begins: PM: suspend entry (deep) Filesystems sync: 0.008 seconds jump_label: Fatal kernel bug, unexpected op at nvkms_kthread_q_callback+0x8e/0x1a0 [nvidia_modeset] kernel BUG at arch/x86/kernel/jump_label.c:73! Oops: invalid opcode: 0000 [#1] SMP NOPTI Relevant system information from the log: Kernel: 7.0.0-15-generic #15-Ubuntu PREEMPT(lazy) Hardware: LENOVO 83DG/LNVNB161216 BIOS: NMCN29WW 12/18/2024 Process: systemd-sleep Sleep mode: deep NVIDIA modules loaded: nvidia, nvidia_modeset, nvidia_drm, nvidia_uvm The crash occurs in the proprietary NVIDIA kernel module path: nvkms_kthread_q_callback+0x8e/0x1a0 [nvidia_modeset] __jump_label_patch.cold+0x24/0x26 arch_jump_label_transform_queue+0x37/0x90 __jump_label_update+0x47/0x100 jump_label_update+0x5c/0x110 static_key_slow_inc_cpuslocked+0x53/0xa0 freeze_processes+0xd1/0xe0 enter_state+0xe0/0x610 pm_suspend+0x49/0x90 state_store+0x2e/0x60 What I expected to happen: The laptop should suspend normally when I close the lid or run systemctl suspend, and should resume normally when opened or woken. What happened instead: The system crashes / becomes unusable during suspend. The kernel reports a BUG in arch/x86/kernel/jump_label.c while inside nvidia_modeset. Steps to reproduce: 1. Boot Ubuntu 26.04 on this Lenovo Legion laptop. 2. Use the proprietary NVIDIA driver. 3. Trigger suspend, either by closing the lid or running: systemctl suspend 4. The system crashes during suspend entry. Additional observations: - The log contains AppArmor audit messages from snap/Discord and snap-confine, but these appear unrelated. - The kernel is tainted due to proprietary/out-of-tree NVIDIA modules: Tainted: P W OE Complete log: May 18 22:08:39 [HOST] kernel: Filesystems sync: 0.008 seconds May 18 22:08:39 [HOST] kernel: jump_label: Fatal kernel bug, unexpected op at nvkms_kthread_q_callback+0x8e/0x1a0 [nvidia_modeset] [0000000088049e86] (e9 9b 00 00 00 != 0f 1f 44 00 00)) size:5 type:1 May 18 22:08:39 [HOST] kernel: fbcon: Taking over console May 18 22:08:39 [HOST] kernel: ------------[ cut here ]------------ May 18 22:08:39 [HOST] kernel: kernel BUG at arch/x86/kernel/jump_label.c:73! May 18 22:08:39 [HOST] kernel: Oops: invalid opcode: 0000 [#1] SMP NOPTI May 18 22:08:39 [HOST] kernel: CPU: 2 UID: 0 PID: 8570 Comm: systemd-sleep Tainted: P W OE 7.0.0-15-generic #15-Ubuntu PREEMPT(lazy) May 18 22:08:39 [HOST] kernel: Tainted: [P]=PROPRIETARY_MODULE, [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE May 18 22:08:39 [HOST] kernel: Hardware name: LENOVO 83DG/LNVNB161216, BIOS NMCN29WW 12/18/2024 May 18 22:08:39 [HOST] kernel: RIP: 0010:__jump_label_patch.cold+0x24/0x26 May 18 22:08:39 [HOST] kernel: Code: f8 e9 44 f7 19 00 48 c7 c3 b8 89 45 94 41 56 45 89 e1 49 89 d8 4c 89 e9 4c 89 ea 4c 89 ee 48 c7 c7 58 9e ed 92 e8 64 90 01 00 <0f> 0b 0f b6 f0 48 c7 c7 20 02 a5 93 88 45 f7 e8 10 9f bc 00 0f b6 May 18 22:08:39 [HOST] kernel: RSP: 0018:ffffd18b4fcd7ba0 EFLAGS: 00010246 May 18 22:08:39 [HOST] kernel: RAX: 00000000000000a8 RBX: ffffffff928068ca RCX: 0000000000000000 May 18 22:08:39 [HOST] kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 May 18 22:08:39 [HOST] kernel: RBP: ffffd18b4fcd7bd0 R08: 0000000000000000 R09: 0000000000000000 May 18 22:08:39 [HOST] kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000005 May 18 22:08:39 [HOST] kernel: R13: ffffffffc8a009ae R14: 0000000000000001 R15: 0000000000000000 May 18 22:08:39 [HOST] kernel: FS: 00007ac3916e6c80(0000) GS:ffff8e066a900000(0000) knlGS:0000000000000000 May 18 22:08:39 [HOST] kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 18 22:08:39 [HOST] kernel: CR2: 0000624f69d86780 CR3: 00000001122f0001 CR4: 0000000000f72ef0 May 18 22:08:39 [HOST] kernel: PKRU: 55555554 May 18 22:08:39 [HOST] kernel: Call Trace: May 18 22:08:39 [HOST] kernel: <TASK> May 18 22:08:39 [HOST] kernel: arch_jump_label_transform_queue+0x37/0x90 May 18 22:08:39 [HOST] kernel: __jump_label_update+0x47/0x100 May 18 22:08:39 [HOST] kernel: jump_label_update+0x5c/0x110 May 18 22:08:39 [HOST] kernel: static_key_slow_inc_cpuslocked+0x53/0xa0 May 18 22:08:39 [HOST] kernel: static_key_slow_inc+0x1f/0x40 May 18 22:08:39 [HOST] kernel: freeze_processes+0xd1/0xe0 May 18 22:08:39 [HOST] kernel: enter_state+0xe0/0x610 May 18 22:08:39 [HOST] kernel: pm_suspend+0x49/0x90 May 18 22:08:39 [HOST] kernel: state_store+0x2e/0x60 May 18 22:08:39 [HOST] kernel: kobj_attr_store+0x12/0x40 May 18 22:08:39 [HOST] kernel: sysfs_kf_write+0x74/0x90 May 18 22:08:39 [HOST] kernel: kernfs_fop_write_iter+0x161/0x210 May 18 22:08:39 [HOST] kernel: vfs_write+0x25b/0x490 May 18 22:08:39 [HOST] kernel: ksys_write+0x71/0xf0 May 18 22:08:39 [HOST] kernel: __x64_sys_write+0x19/0x30 May 18 22:08:39 [HOST] kernel: x64_sys_call+0x22f/0x2390 May 18 22:08:39 [HOST] kernel: do_syscall_64+0x115/0x5a0 May 18 22:08:39 [HOST] kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100 May 18 22:08:39 [HOST] kernel: ? irqentry_exit+0x97/0x5a0 May 18 22:08:39 [HOST] kernel: ? exc_page_fault+0x94/0x1e0 May 18 22:08:39 [HOST] kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e May 18 22:08:39 [HOST] kernel: RIP: 0033:0x7ac390ea06c6 May 18 22:08:39 [HOST] kernel: Code: 47 ba 04 00 00 00 48 8b 05 3f 17 17 00 64 89 10 48 c7 c2 ff ff ff ff c9 48 89 d0 c3 0f 1f 84 00 00 00 00 00 48 8b 45 10 0f 05 <48> 89 c2 48 3d 00 f0 ff ff 77 0f c9 48 89 d0 c3 66 2e 0f 1f 84 00 May 18 22:08:39 [HOST] kernel: RSP: 002b:00007ffd907f5850 EFLAGS: 00000202 ORIG_RAX: 0000000000000001 May 18 22:08:39 [HOST] kernel: RAX: ffffffffffffffda RBX: 0000624f69d81010 RCX: 00007ac390ea06c6 May 18 22:08:39 [HOST] kernel: RDX: 0000000000000004 RSI: 0000624f69d85770 RDI: 0000000000000005 May 18 22:08:39 [HOST] kernel: RBP: 00007ffd907f5860 R08: 0000000000000000 R09: 0000000000000000 May 18 22:08:39 [HOST] kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000004 May 18 22:08:39 [HOST] kernel: R13: 0000000000000004 R14: 0000624f69d85770 R15: 0000000000000000 May 18 22:08:39 [HOST] kernel: </TASK> May 18 22:08:39 [HOST] kernel: Modules linked in: rfcomm snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bridge stp llc ccm xt_comment nft_compat x_tables nvidia_uvm(POE) qrtr snd_hda_codec_intelhdmi cmac algif_hash algif_skcipher af_alg snd_ctl_led overlay nf_tables bnep snd_hda_codec_alc269 snd_hda_codec_realtek_lib snd_hda_scodec_component snd_hda_codec_generic xe binfmt_misc drm_gpusvm_helper gpu_sched drm_gpuvm drm_exec drm_suballoc_helper nls_iso8859_1 nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) intel_uncore_frequency intel_uncore_frequency_common intel_tcc_cooling lenovo_wmi_gamezone x86_pkg_temp_thermal lenovo_wmi_other intel_powerclamp lenovo_wmi_helpers coretemp snd_sof_pci_intel_tgl snd_sof_pci_intel_cnl snd_sof_intel_hda_generic soundwire_intel snd_sof_intel_hda_sdw_bpt snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda_mlink snd_sof_intel_hda soundwire_cadence snd_sof_pci snd_sof_xtensa_dsp May 18 22:08:39 [HOST] kernel: snd_sof snd_sof_utils snd_soc_acpi_intel_match snd_soc_acpi_intel_sdca_quirks soundwire_generic_allocation snd_soc_sdw_utils snd_soc_acpi soundwire_bus snd_hda_codec_nvhdmi snd_soc_sdca snd_hda_codec_hdmi crc8 snd_soc_avs snd_soc_hda_codec rtw89_8852ce snd_hda_intel snd_hda_ext_core rtw89_8852c snd_hda_codec snd_soc_core snd_hda_core rtw89_pci snd_intel_dspcfg snd_compress snd_intel_sdw_acpi ac97_bus snd_pcm_dmaengine snd_hwdep snd_pcm rtw89_core kvm_intel uvcvideo snd_seq_midi snd_seq_midi_event videobuf2_vmalloc kvm snd_rawmidi uvc btusb videobuf2_memops btmtk videobuf2_v4l2 irqbypass mac80211 snd_seq btrtl ghash_clmulni_intel videobuf2_common cmdlinepart aesni_intel btbcm videodev spi_nor btintel snd_seq_device rapl intel_cstate mtd mei_hdcp mei_pxp intel_rapl_msr i915 bluetooth lenovo_wmi_events mc snd_timer firmware_attributes_class lenovo_wmi_capdata cfg80211 i2c_i801 snd spi_intel_pci processor_thermal_device_pci wmi_bmof i2c_smbus processor_thermal_device lenovo_wmi_hotkey_utilities May 18 22:08:39 [HOST] kernel: nvidia_wmi_ec_backlight spi_intel libarc4 i2c_mux drm_ttm_helper soundcore drm_buddy ideapad_laptop processor_thermal_wt_hint ttm platform_temperature_control sparse_keymap processor_thermal_soc_slider drm_display_helper intel_pmc_core processor_thermal_rfim processor_thermal_rapl pmt_telemetry cec intel_rapl_common pmt_discovery processor_thermal_wt_req pmt_class processor_thermal_power_floor rc_core processor_thermal_mbox int3400_thermal intel_pmc_ssram_telemetry platform_profile i2c_algo_bit int3403_thermal intel_vsec acpi_thermal_rel int340x_thermal_zone acpi_pad joydev input_leds mei_me mac_hid mei sch_fq_codel parport_pc lp ppdev parport msr efi_pstore nfnetlink dmi_sysfs autofs4 btrfs libblake2b raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 linear hid_multitouch hid_generic usbhid i2c_hid_acpi ucsi_acpi i2c_hid serio_raw hid nvme typec_ucsi nvme_core r8169 typec nvme_keyring video ahci intel_lpss_pci thunderbolt realtek nvme_auth intel_lpss hkdf May 18 22:08:39 [HOST] kernel: libahci pinctrl_alderlake idma64 wmi May 18 22:08:39 [HOST] kernel: ---[ end trace 0000000000000000 ]--- May 18 22:08:41 [HOST] kernel: RIP: 0010:__jump_label_patch.cold+0x24/0x26 May 18 22:08:41 [HOST] kernel: Code: f8 e9 44 f7 19 00 48 c7 c3 b8 89 45 94 41 56 45 89 e1 49 89 d8 4c 89 e9 4c 89 ea 4c 89 ee 48 c7 c7 58 9e ed 92 e8 64 90 01 00 <0f> 0b 0f b6 f0 48 c7 c7 20 02 a5 93 88 45 f7 e8 10 9f bc 00 0f b6 May 18 22:08:41 [HOST] kernel: RSP: 0018:ffffd18b4fcd7ba0 EFLAGS: 00010246 May 18 22:08:41 [HOST] kernel: RAX: 00000000000000a8 RBX: ffffffff928068ca RCX: 0000000000000000 May 18 22:08:41 [HOST] kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 May 18 22:08:41 [HOST] kernel: RBP: ffffd18b4fcd7bd0 R08: 0000000000000000 R09: 0000000000000000 May 18 22:08:41 [HOST] kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000005 May 18 22:08:41 [HOST] kernel: R13: ffffffffc8a009ae R14: 0000000000000001 R15: 0000000000000000 May 18 22:08:41 [HOST] kernel: FS: 00007ac3916e6c80(0000) GS:ffff8e066af00000(0000) knlGS:0000000000000000 May 18 22:08:41 [HOST] kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 18 22:08:41 [HOST] kernel: CR2: 00005608d72752e0 CR3: 00000001122f0004 CR4: 0000000000f72ef0 May 18 22:08:41 [HOST] kernel: PKRU: 55555554 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: pavel 7833 F.... wireplumber /dev/snd/controlC0: pavel 7833 F.... wireplumber /dev/snd/seq: pavel 7797 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 19 08:00:57 2026 InstallationDate: Installed on 2025-02-22 (451 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 04f2:b7b6 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 048d:c992 Integrated Technology Express, Inc. ITE Device(8176) Bus 001 Device 004: ID 0bda:5852 Realtek Semiconductor Corp. Bluetooth Radio Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: LENOVO 83DG ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=197794af-2d92-46dc-9acf-5ff51af5a2c7 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-16 (2 days ago) dmi.bios.date: 12/18/2024 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: NMCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 5 16IRX9 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrNMCN29WW:bd12/18/2024:br1.29:efr1.29:svnLENOVO:pn83DG:pvrLegion516IRX9:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion516IRX9:skuLENOVO_MT_83DG_BU_idea_FM_Legion516IRX9:pfaLegion516IRX9: dmi.product.family: Legion 5 16IRX9 dmi.product.name: 83DG dmi.product.sku: LENOVO_MT_83DG_BU_idea_FM_Legion 5 16IRX9 dmi.product.version: Legion 5 16IRX9 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2153112/+subscriptions

[Bug 2153155] Re: Fix bad audio record quality when volume above 50% on Framwork PTL

** Tags added: jira-burlingame-74 oem-priority -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2153155 Title: Fix bad audio record quality when volume above 50% on Framwork PTL Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: In Progress Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Framework PTL platform with Realtek ALC295 audio solution will have audio recording quality when the input volume is configure > 50%. [Fix] Fix by backporting the commit: 67c738152207 ("67c738152207") which fix mic boost on particular SSIDs of the Framework machines [Test Case] 1. Boot up the machine of new Framework PTL platforms with Realtek ALC295 audio solution 2. Go to g-s-d and select sound --> input (Internal Microphone) --> Adjust the input volume > 50% 3. Do `arecord` with the internal microphone and play the recorded clips. [Where problems could occur] It only limit the mic boost based on particular SSIDs. The risk of regression is limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2153155/+subscriptions