[Bug 2154166] [NEW] Periodic screen blanking with Linux kernel 7.x

Public bug reported: Screen periodically turns off for ~1 second, then returns. Repeats indefinitely and happens on clean install of newer kernel (7.x series). Does NOT happen on 6.8 kernel, nomodeset stops issue but then you can't use normal display resolutions (only 800x600 available). 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 AlsaVersion: Advanced Linux Sound Architecture Driver Version k7.0.0-15-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: softpos 1477 F.... pipewire softpos 1484 F.... wireplumber /dev/snd/pcmC0D0p: softpos 1477 F...m pipewire /dev/snd/seq: softpos 1477 F.... pipewire 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: unknown CurrentDesktop: LXQt Date: Mon May 25 11:01:14 2026 MachineType: FIRICH J1900 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=8f2803ea-e42b-403b-8124-7888d3c92b77 ro RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: J1900 dmi.board.vendor: FIRICH dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: FIRICH dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd01/18/2017:br5.6:svnFIRICH:pnJ1900:pvr1.x:rvnFIRICH:rnJ1900:rvr1.x:cvnFIRICH:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: J1900 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: FIRICH ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154166 Title: Periodic screen blanking with Linux kernel 7.x Status in linux package in Ubuntu: New Bug description: Screen periodically turns off for ~1 second, then returns. Repeats indefinitely and happens on clean install of newer kernel (7.x series). Does NOT happen on 6.8 kernel, nomodeset stops issue but then you can't use normal display resolutions (only 800x600 available). 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 AlsaVersion: Advanced Linux Sound Architecture Driver Version k7.0.0-15-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: softpos 1477 F.... pipewire softpos 1484 F.... wireplumber /dev/snd/pcmC0D0p: softpos 1477 F...m pipewire /dev/snd/seq: softpos 1477 F.... pipewire 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: unknown CurrentDesktop: LXQt Date: Mon May 25 11:01:14 2026 MachineType: FIRICH J1900 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=8f2803ea-e42b-403b-8124-7888d3c92b77 ro RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: J1900 dmi.board.vendor: FIRICH dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: FIRICH dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd01/18/2017:br5.6:svnFIRICH:pnJ1900:pvr1.x:rvnFIRICH:rnJ1900:rvr1.x:cvnFIRICH:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: J1900 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: FIRICH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154166/+subscriptions

[Bug 2154162] [NEW] Ubuntu 24.04.3 HWE kernel fails to install and displays stdin: Invalid argument

Public bug reported: Ubuntu 24.04.3 HWE kernel fails to install and displays stdin: Invalid argument The issue also happens with 24.04.4 HWE kernel installation. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154162 Title: Ubuntu 24.04.3 HWE kernel fails to install and displays stdin: Invalid argument Status in linux package in Ubuntu: New Bug description: Ubuntu 24.04.3 HWE kernel fails to install and displays stdin: Invalid argument The issue also happens with 24.04.4 HWE kernel installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154162/+subscriptions

[Bug 2154125] Re: ubuntu desktop issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154125 Title: ubuntu desktop issue Status in linux package in Ubuntu: New Bug description: settings > ubuntu desktop : not working and get this issue "Oops, something has gone wrong. Please report a bug in Launchpad." 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: hossien 5010 F.... wireplumber /dev/snd/controlC0: hossien 5010 F.... wireplumber /dev/snd/seq: hossien 4996 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun May 24 15:52:41 2026 MachineType: ASUS System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=d821b6cc-1c4e-476d-89e5-ebcf09449dfb ro quiet splash SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-24 (0 days ago) dmi.bios.date: 10/27/2021 dmi.bios.release: 12.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1203 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING Z590-PLUS WIFI 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.:bvr1203:bd10/27/2021:br12.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGZ590-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154125/+subscriptions

[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.

Thanks Aaron and Jeff, We are setting up the environment to test both the "Ubuntu mainline v7.1-rc4" and "locally built test kernel" and hopefully will update you the results soon. -- 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 2150636] Re: overlayfs crash while network install

Here is the test kernel, how could we verify it? https://people.canonical.com/~acelan/bugs/SOMERVILLE-4644/ -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150636 Title: overlayfs crash while network install Status in subiquity: New Status in linux package in Ubuntu: Confirmed Bug description: Hallo Ubuntu team: We found some issue while trying to install New resolute over the network. We have exact same setup for Noble and Jammy and those works without any issues, issue seems to be isolated to new Resolute version. How to reproduce: Perform an unattended installation over the network like: ```   linux /images/resolute_install.vmlinuz console=tty0 console=ttyS1,115200n8 ip=dhcp cloud-config-url=/dev/null url=http://myhttpserver.net/images/ubuntu-resolute-live-server-amd64.iso autoinstall ds="nocloud-net;s=http://myhttpserver.net/cloud-init/resolute/" interface=$net_default_mac systemdisk=$instdev modprobe.blacklist=cdc_ether   initrd /images/resolute_install.initrd } ``` One the installation start, the installer give up due the following crash: ``` RIP: 0010:ovl_iterate_merged+0x1d8/0x2b0 [overlay] ``` ``` [ 199.877233] BUG: unable to handle page fault for address: ffffffffc58efed0 [ 199.885471] #PF: supervisor read access in kernel mode [ 199.891591] #PF: error_code(0x0000) - not-present page [ 199.897673] PGD 12f3646067 P4D 12f3647067 PUD 12f3649067 PMD 0 [ 199.904629] Oops: Oops: 0000 [#2] SMP NOPTI [ 199.909631] CPU: 4 UID: 0 PID: 5833 Comm: rsync Tainted: P S D O 7.0.0-14-generic #14-Ubuntu PREEMPT(lazy) [ 199.922141] Tainted: [P]=PROPRIETARY_MODULE, [S]=CPU_OUT_OF_SPEC, [D]=DIE, [O]=OOT_MODULE [ 199.931623] Hardware name: Lenovo ThinkSystem SR630 V3/XXXXXXX, BIOS ESE138F-3.80 11/12/2025 [ 199.941687] RIP: 0010:ovl_iterate_merged+0x1d8/0x2b0 [overlay] [ 199.948544] Code: 41 08 48 89 ce e8 28 49 ff ff 48 8b 4d d0 41 89 ce 48 81 f9 00 f0 ff ff 0f 87 f5 fe ff ff 48 89 4b 08 49 8b 55 08 48 83 c1 10 <4c> 8b 39 48 85 d2 7e 21 49 39 cf 74 1c 31 c0 eb 0c 0f 1f 80 00 00 [ 199.970203] RSP: 0018:ff75651c6a9f7c58 EFLAGS: 00010282 [ 199.976365] RAX: 0000000000000000 RBX: ff3f74fac56b4bc0 RCX: ffffffffc58efed0 [ 199.984669] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 [ 199.992969] RBP: ff75651c6a9f7c98 R08: 0000000000000000 R09: 0000000000000000 [ 200.001261] R10: 0000000000000000 R11: 0000000000000000 R12: ff3f74fac6c820c0 [ 200.009552] R13: ff75651c6a9f7d70 R14: 00000000c58efec0 R15: ff3f74fb249bb2b8 [ 200.017839] FS: 0000730fb2f91100(0000) GS:ff3f750a6d800000(0000) knlGS:0000000000000000 [ 200.027199] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 200.033925] CR2: ffffffffc58efed0 CR3: 0000000155cee003 CR4: 0000000000f73ef0 [ 200.042213] PKRU: 55555554 [ 200.045525] Call Trace: [ 200.048539] <TASK> [ 200.051160] ovl_iterate+0xd3/0x120 [overlay] [ 200.056318] ? __pfx_ovl_iterate+0x10/0x10 [overlay] [ 200.062154] wrap_directory_iterator+0x4f/0x80 [ 200.067399] shared_ovl_iterate+0x15/0x30 [overlay] [ 200.073126] iterate_dir+0xc1/0x2a0 [ 200.077288] __x64_sys_getdents64+0x76/0x140 [ 200.082321] ? __pfx_filldir64+0x10/0x10 [ 200.086959] x64_sys_call+0x100b/0x2390 [ 200.091498] do_syscall_64+0x115/0x5a0 [ 200.095936] ? count_memcg_events+0x103/0x250 [ 200.101051] ? handle_mm_fault+0x1c0/0x2e0 [ 200.105867] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100 [ 200.112632] ? irqentry_exit+0x97/0x5a0 [ 200.117138] ? exc_page_fault+0x94/0x1e0 [ 200.121745] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 200.127616] RIP: 0033:0x730fb30887d7 [ 200.131825] Code: 11 00 64 c7 00 16 00 00 00 31 c0 eb 9f e8 61 ec 04 00 90 f3 0f 1e fa b8 ff ff ff 7f 48 39 c2 48 0f 47 d0 b8 d9 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 01 b6 11 00 f7 d8 64 89 02 48 [ 200.153288] RSP: 002b:00007ffcd0778138 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 [ 200.161982] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000730fb30887d7 [ 200.170185] RDX: 0000000000008000 RSI: 00005a7baefe4060 RDI: 0000000000000003 [ 200.178384] RBP: 00007ffcd0778170 R08: 00005a7baefe4034 R09: 0000730fb31a4ac8 [ 200.186582] R10: 0000000000008040 R11: 0000000000000293 R12: 0000000000000001 [ 200.194775] R13: 00005a7baefe4030 R14: 00007ffcd0778270 R15: 0000730fb2f910b0 start: subiqu[ 200.202972] </TASK> [ 200.202973] Modules linked in: nls_iso8859_1 xfs zfs(PO) spl(O) bcache qrtr cfg80211 intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common intel_ifs i10nm_edac skx_edac_common nfit x86_pkg_temp_thermal coretemp kvm_intel kvm irqbypass ghash_clmulni_intel rapl intel_cstate cmdlinepart spi_nor pmt_telemetry mtd iaa_crypto pmt_discovery pmt_class intel_sdsi dax_hmem binfmt_misc cxl_acpi cxl_port cxl_pmem ses cxl_core einj ast enclosure mlx5_fwctl fwctl isst_if_mbox_pci i2c_algo_bit ipmi_ssif joydev input_leds acpi_power_meter ipmi_si isst_if_mmio acpi_ipmi mei_me ipmi_devintf spi_intel_pci idxd isst_if_common intel_vsec ipmi_msghandler mei spi_intel idxd_bus mac_hid sch_fq_codel msr nvme_fabrics nvme_core nvme_keyring nvme_auth hkdf efi_pstore nfnetlink dmi_sysfs autofs4 overlay isofs 8021q garp mrp stp llc raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 linear mlx5_ib ib_uverbs macsec ib_core hid_generic usbhid hid wmi mlx5_core mpt3sas [ 200.207023] mlxfw psample raid_class tls pinctrl_emmitsburg scsi_transport_sas pci_hyperv_intf ahci libahci scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath aesni_intel [ 200.207035] CR2: ffffffffc58efed0 [ 200.207037] ---[ end trace 0000000000000000 ]--- [ 201.117859] RIP: 0010:ovl_iterate_merged+0x1d8/0x2b0 [overlay] [ 201.249949] Code: 41 08 48 89 ce e8 28 49 ff ff 48 8b 4d d0 41 89 ce 48 81 f9 00 f0 ff ff 0f 87 f5 fe ff ff 48 89 4b 08 49 8b 55 08 48 83 c1 10 <4c> 8b 39 48 85 d2 7e 21 49 39 cf 74 1c 31 c0 eb 0c 0f 1f 80 00 00 ity/Install/inst[ 201.249950] RSP: 0018:ff75651c494d3d18 EFLAGS: 00010282 all/curtin_insta[ 201.249952] RAX: 0000000000000000 RBX: ff3f750a4bf28040 RCX: ffffffffc58efed0 ll/run_curtin_st[ 201.249953] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 ep/cmd-install: [ 201.249954] RBP: ff75651c494d3d58 R08: 0000000000000000 R09: 0000000000000000 curtin command i[ 201.249955] R10: 0000000000000000 R11: 0000000000000000 R12: ff3f750a4d3569c0 nstall start: [ 201.249955] R13: ff75651c494d3e30 R14: 00000000c58efec0 R15: ff3f750a6286acb8    subiquity/Ins[ 201.249956] FS: 0000730fb2f91100(0000) GS:ff3f750a6d800000(0000) knlGS:0000000000000000 tall/install/cur[ 201.249957] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 tin_install/run_[ 201.249958] CR2: ffffffffc58efed0 CR3: 0000000155cee003 CR4: 0000000000f73ef0 curtin_step/cmd-[ 201.249959] PKRU: 55555554 install/stage-ex[ 201.249960] note: rsync[5833] exited with irqs disabled ``` So far we believe this issue is kinda related with these links: Some google bot also found the issue: https://syzkaller.appspot.com/bug?extid=a16fb0cce329a320661c Reported in January 2026 to Overlay FS maintainers https://lore.kernel.org/all/697a03f6.a00a0220.35f26.0000.GAE@google.com/T/ It seems like the (ovl_iterate_merged) function was introduced here: (Kernel 6.19) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d0deeb803cd65c41c37ac106063c46c51d5d43ab ### We also notice that if we add `modprobe.blacklist=zfs` to our boot parameters will help a little bit to mitigate the issue, but the installation still fails time to time, but less frequently. When booting with: `modprobe.blacklist=zfs` : ``` [ 197.829405] Tainted: [S]=CPU_OUT_OF_SPEC, [D]=DIE [ 197.835674] Hardware name: Lenovo ThinkSystem SR630 V3/XXXXXX, BIOS ESE138F-3.80 11/12/2025 [ 197.845738] RIP: 0010:ovl_iterate_merged+0x1d8/0x2b0 [overlay] [ 197.852592] Code: 41 08 48 89 ce e8 28 49 ff ff 48 8b 4d d0 41 89 ce 48 81 f9 00 f0 ff ff 0f 87 f5 fe ff ff 48 89 4b 08 49 8b 55 08 48 83 c1 10 <4c> 8b 39 48 85 d2 7e 21 49 39 cf 74 1c 31 c0 eb 0c 0f 1f 80 00 00 [ 197.874250] RSP: 0018:ff75adff62803a08 EFLAGS: 00010286 [ 197.880407] RAX: 0000000000000000 RBX: ff21db08a8775cc0 RCX: ffffffff85acb050 [ 197.888708] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 [ 197.897006] RBP: ff75adff62803a48 R08: 0000000000000000 R09: 0000000000000000 [ 197.905302] R10: 0000000000000000 R11: 0000000000000000 R12: ff21db0886b3cfc0 [ 197.913596] R13: ff75adff62803b20 R14: 0000000085acb040 R15: ff21db08efb224b8 [ 197.921891] FS: 00007a1db9f93100(0000) GS:ff21db1825600000(0000) knlGS:0000000000000000 [ 197.931261] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 197.937984] CR2: ffffffff85acb050 CR3: 000000015cd01006 CR4: 0000000000f73ef0 [ 197.946273] PKRU: 55555554 [ 197.949582] Call Trace: [ 197.952595] <TASK> [ 197.955215] ovl_iterate+0xd3/0x120 [overlay] [ 197.960373] ? __pfx_ovl_iterate+0x10/0x10 [overlay] [ 197.966207] wrap_directory_iterator+0x4f/0x80 [ 197.971449] shared_ovl_iterate+0x15/0x30 [overlay] [ 197.977175] iterate_dir+0xc1/0x2a0 [ 197.981334] __x64_sys_getdents64+0x76/0x140 [ 197.986364] ? __pfx_filldir64+0x10/0x10 [ 197.991001] x64_sys_call+0x100b/0x2390 [ 197.995537] do_syscall_64+0x115/0x5a0 [ 197.999971] ? __alloc_frozen_pages_noprof+0x187/0x360 [ 198.005954] ? mod_memcg_lruvec_state+0x101/0x2f0 [ 198.011452] ? lruvec_stat_mod_folio+0x8d/0x100 [ 198.016741] ? set_ptes.isra.0+0x3b/0x90 [ 198.021353] ? do_anonymous_page+0x105/0x4d0 [ 198.026348] ? handle_pte_fault+0x1cb/0x1f0 [ 198.031241] ? __handle_mm_fault+0x493/0x720 [ 198.036228] ? count_memcg_events+0x103/0x250 [ 198.041300] ? handle_mm_fault+0x1c0/0x2e0 [ 198.046082] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100 [ 198.052813] ? irqentry_exit+0x97/0x5a0 [ 198.057300] ? exc_page_fault+0x94/0x1e0 [ 198.061879] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 198.067721] RIP: 0033:0x7a1dba08a7d7 [ 198.071902] Code: 11 00 64 c7 00 16 00 00 00 31 c0 eb 9f e8 61 ec 04 00 90 f3 0f 1e fa b8 ff ff ff 7f 48 39 c2 48 0f 47 d0 b8 d9 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 01 b6 11 00 f7 d8 64 89 02 48 [ 198.093310] RSP: 002b:00007ffc13ab5908 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 [ 198.101982] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007a1dba08a7d7 [ 198.110165] RDX: 0000000000008000 RSI: 000058c315bca060 RDI: 0000000000000003 [ 198.118347] RBP: 00007ffc13ab5940 R08: 000058c315bca034 R09: 00007a1dba1a6ac8 [ 198.126529] R10: 0000000000008040 R11: 0000000000000293 R12: 0000000000000001 [ 198.134708] R13: 000058c315bca030 R14: 00007ffc13ab5a40 R15: 00007a1db9f930b0 [ 198.142889] </TASK> [ 198.145506] Modules linked in: nls_iso8859_1 xfs bcache qrtr cfg80211 binfmt_misc intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common intel_ifs i10nm_edac skx_edac_common nfit x86_pkg_temp_thermal coretemp kvm_intel kvm irqbypass ghash_clmulni_intel rapl intel_cstate cmdlinepart dax_hmem cxl_acpi spi_nor pmt_telemetry cxl_port iaa_crypto pmt_discovery mtd pmt_class cxl_pmem intel_sdsi cxl_core ses einj enclosure mlx5_fwctl fwctl ast acpi_power_meter isst_if_mbox_pci i2c_algo_bit ipmi_ssif input_leds joydev isst_if_mmio ipmi_si acpi_ipmi ipmi_devintf isst_if_common mei_me spi_intel_pci ipmi_msghandler idxd intel_vsec spi_intel mei idxd_bus mac_hid sch_fq_codel msr nvme_fabrics nvme_core nvme_keyring nvme_auth hkdf efi_pstore nfnetlink dmi_sysfs autofs4 overlay isofs 8021q garp mrp stp llc raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 linear mlx5_ib ib_uverbs macsec ib_core mlx5_core hid_generic usbhid hid mlxfw mpt3sas psample tls [ 198.145576] raid_class scsi_transport_sas pci_hyperv_intf ahci libahci wmi pinctrl_emmitsburg scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath aesni_intel [ 198.264212] CR2: ffffffff85acb050 [ 198.268126] ---[ end trace 0000000000000000 ]--- start: subiquity/Install/i[ 199.157669] RIP: 0010:ovl_iterate_merged+0x1d8/0x2b0 [overlay] nstall/curtin_in[ 199.164461] Code: 41 08 48 89 ce e8 28 49 ff ff 48 8b 4d d0 41 89 ce 48 81 f9 00 f0 ff ff 0f 87 f5 fe ff ff 48 89 4b 08 49 8b 55 08 48 83 c1 10 <4c> 8b 39 48 85 d2 7e 21 49 39 cf 74 1c 31 c0 eb 0c 0f 1f 80 00 00 stall/run_curtin[ 199.187319] RSP: 0018:ff75adff70b67be8 EFLAGS: 00010286 _step/cmd-instal[ 199.194535] RAX: 0000000000000000 RBX: ff21db08a59c5480 RCX: ffffffff85acb050 l/stage-extract/[ 199.204115] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 builtin/cmd-extr[ 199.213707] RBP: ff75adff70b67c28 R08: 0000000000000000 R09: 0000000000000000 act: curtin comm[ 199.223298] R10: 0000000000000000 R11: 0000000000000000 R12: ff21db088bb2f140 and extract sta[ 199.232876] R13: ff75adff70b67d00 R14: 0000000085acb040 R15: ff21db08a4679d78 rt: subiq[ 199.242467] FS: 00007a1db9f93100(0000) GS:ff21db1825600000(0000) knlGS:0000000000000000 uity/Install/ins[ 199.253132] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 tall/curtin_inst[ 199.261165] CR2: ffffffff85acb050 CR3: 000000015cd01006 CR4: 0000000000f73ef0 all/run_curtin_s[ 199.270760] PKRU: 55555554 tep/cmd-install/[ 199.275378] note: rsync[5810] exited with irqs disabled stage-extract/builtin/cmd-extract/: acquiring and extracting image from cp:///tmp/tmpdd344ar8/mount ``` To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2150636/+subscriptions

[Bug 2152714] Re: Kernel 6.19-rc8 does not include GPIB driver

** Also affects: linux (Ubuntu Stonking) Importance: Undecided Status: 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/2152714 Title: Kernel 6.19-rc8 does not include GPIB driver Status in linux package in Ubuntu: In Progress Status in linux source package in Stonking: In Progress Bug description: The gpib kernel driver, promoted in 6.19 (previously it was in the staging area) was included in Ubuntu mainline v6.19-rc5, but not in v6.19-rc8 onward. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/gpib?h=v6.19.6 Having the kernel driver makes it easier for the user to use the GPIB library to control GPIB devices. Without the driver, a DKMS module is required to build and install the driver which is not ideal. Reproducible: Always To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152714/+subscriptions

[Bug 2154154] [NEW] r8169 RTL8168h/8111h NETDEV WATCHDOG transmit queue timeout

Public bug reported: System experiences repeated network transmit queue timeouts using the r8169 driver with a Realtek RTL8168h/8111h NIC. Kernel messages: r8169 0000:04:00.0 enp4s0: NETDEV WATCHDOG: transmit queue 0 timed out r8169 0000:04:00.0 enp4s0: ASPM disabled on Tx timeout r8169 0000:04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 Hardware: Realtek RTL8168h/8111h Driver: r8169 Observed behavior: - periodic network stalls/freezes - watchdog timeout repeats every few minutes - interface remains up but connectivity becomes unstable The issue appears related to ASPM/power management because the driver logs: "ASPM disabled on Tx timeout" Please investigate possible regressions or ASPM interactions in r8169. 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: safia 4940 F.... wireplumber /dev/snd/controlC0: safia 4940 F.... wireplumber /dev/snd/seq: safia 4923 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 25 11:21:49 2026 InstallationDate: Installed on 2026-01-12 (133 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: Gigabyte Technology Co., Ltd. B550M AORUS ELITE ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=414b02b6-610f-4cb2-83c5-dd44bea4485f ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-18 (6 days ago) dmi.bios.date: 10/28/2025 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F21 dmi.board.asset.tag: Default string dmi.board.name: B550M AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. 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.:bvrF21:bd10/28/2025:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550MAORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550MAORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaB550MB: dmi.product.family: B550 MB dmi.product.name: B550M AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** 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/2154154 Title: r8169 RTL8168h/8111h NETDEV WATCHDOG transmit queue timeout Status in linux package in Ubuntu: New Bug description: System experiences repeated network transmit queue timeouts using the r8169 driver with a Realtek RTL8168h/8111h NIC. Kernel messages: r8169 0000:04:00.0 enp4s0: NETDEV WATCHDOG: transmit queue 0 timed out r8169 0000:04:00.0 enp4s0: ASPM disabled on Tx timeout r8169 0000:04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 Hardware: Realtek RTL8168h/8111h Driver: r8169 Observed behavior: - periodic network stalls/freezes - watchdog timeout repeats every few minutes - interface remains up but connectivity becomes unstable The issue appears related to ASPM/power management because the driver logs: "ASPM disabled on Tx timeout" Please investigate possible regressions or ASPM interactions in r8169. 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: safia 4940 F.... wireplumber /dev/snd/controlC0: safia 4940 F.... wireplumber /dev/snd/seq: safia 4923 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 25 11:21:49 2026 InstallationDate: Installed on 2026-01-12 (133 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: Gigabyte Technology Co., Ltd. B550M AORUS ELITE ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=414b02b6-610f-4cb2-83c5-dd44bea4485f ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-18 (6 days ago) dmi.bios.date: 10/28/2025 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F21 dmi.board.asset.tag: Default string dmi.board.name: B550M AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. 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.:bvrF21:bd10/28/2025:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550MAORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550MAORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaB550MB: dmi.product.family: B550 MB dmi.product.name: B550M AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154154/+subscriptions

[Bug 2150605] Re: `i915 Arrow Lake-S: PHY A / C10 DPLL state mismatch on resume from long s2idle dwell — slow wake (5-10s) with retry storm`

This appears to affect Meteor Lake as well, not just Arrow Lake-S; I'm seeing the same issue on a Dell Pro Max 16. It appears to be a regression since I didn't see this issue on 6.17.0-29, but I do see it on 7.0.0-15-generic. ## System - **Device**: Dell Pro Max 16 Premium MA16250 - **Motherboard**: Dell 085XPR - **CPU/iGPU**: Intel Core Ultra 7 265H (Meteor Lake) - **BIOS**: 1.9.0 (2026-03-31) - **Kernel**: 7.0.0-15-generic (Ubuntu 26.04) - **Display**: Internal eDP panel (DDI A / pipe A) ## Hardware IDs ``` DMI: Dell Inc. Dell Pro Max 16 Premium MA16250/085XPR, BIOS 1.9.0 03/31/2026 SMBIOS 3.8 present iGPU: pci 0000:00:02.0 [8086:7d51] - Meteor Lake integrated display version 14.00 stepping D0 dGPU: pci 0000:01:00.0 [10de:2d39] - NVIDIA (hybrid graphics, PCIe x8 @ 32 GT/s) ``` ## i915 Driver & Firmware ``` i915 version: 1.6.0 DMC firmware: i915/mtl_dmc.bin v2.23 GuC firmware: i915/mtl_guc_70.bin v70.53.0 HuC firmware: i915/mtl_huc_gsc.bin v8.5.4 GSC firmware: i915/mtl_gsc_1.bin (cv1.0, r102.1.15.1926) ``` ## Symptoms Appear to match the reported issue very closely: - Short s2idle dwells (minutes): instant wake, no errors - Long s2idle dwells (4+ hours): ~30-60 second resume delay with PHY/DPLL error storm - Display eventually recovers - Appeared to be a hard hang on display powersave before setting i915.enable_psr=0 ## Timing ``` [65004.726228] PM: suspend entry (s2idle) [80437.248708] PM: suspend exit ``` Sleep duration: ~4.3 hours Resume delay: ~57 seconds (from first resume activity at 80380 to PM: suspend exit) ## Log Excerpt (resume sequence) ``` [80392.232107] i915 0000:00:02.0: [drm] *ERROR* Failed to bring PHY A to idle. [80392.240108] i915 0000:00:02.0: [drm] *ERROR* PHY A Read 0c70 failed after 3 retries. [80392.249106] i915 0000:00:02.0: [drm] *ERROR* PHY A Write 0c70 failed after 3 retries. [80392.474869] i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active [80393.428861] i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns [80403.757549] i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] flip_done timed out [80403.967091] i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in pixel_rate (expected 317492, found 36124) [80403.967102] i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in dpll_hw_state [80403.967106] i915 0000:00:02.0: [drm] *ERROR* cx0pll_hw_state: lane_count: 2, ssc_enabled: no, use_c10: yes, tbt_mode: no [80403.967109] i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 540000, fracen: yes, [80403.967111] i915 0000:00:02.0: [drm] *ERROR* quot: 40960, rem: 0, den: 1, [80403.967112] i915 0000:00:02.0: [drm] *ERROR* multiplier: 140, tx_clk_div: 0. [80403.967127] i915 0000:00:02.0: [drm] *ERROR* found: [80403.967128] i915 0000:00:02.0: [drm] *ERROR* cx0pll_hw_state: lane_count: 2, ssc_enabled: no, use_c10: yes, tbt_mode: no [80403.967130] i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 61440, fracen: no, [80403.967132] i915 0000:00:02.0: [drm] *ERROR* multiplier: 16, tx_clk_div: 0. [80403.967146] i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in port_clock (expected 540000, found 61440) [80403.967159] i915 0000:00:02.0: [drm] pipe state doesn't match! [80404.177686] i915 0000:00:02.0: [drm] DPLL 0: pll hw state mismatch ``` Note the same C10 PLL state mismatch pattern: - **Expected**: clock 540000, multiplier 140, PLL registers populated - **Found**: clock 61440, multiplier 16, PLL registers all zeros The ~10 second gap between `[80393] Timed out waiting for DP idle patterns` and `[80403] flip_done timed out` matches the flip_done timeout constant. Issue reproduced on two separate occasions (2026-05-24 and 2026-05-25) with identical symptoms. ## Kernel Command Line ``` BOOT_IMAGE=/vmlinuz-7.0.0-15-generic root=/dev/mapper/vgubuntu-root ro quiet splash intel_iommu=on iommu=pt i915.enable_psr=0 ``` PSR is already disabled (`i915.enable_psr=0`), so this is not a PSR- related issue. Before disabling PSR I was seeing failure to recover from display suspend, another regression since 6.17.0-29. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150605 Title: `i915 Arrow Lake-S: PHY A / C10 DPLL state mismatch on resume from long s2idle dwell — slow wake (5-10s) with retry storm` Status in linux package in Ubuntu: Confirmed Bug description: This is what an investigation using claude code yielded regarding a wake-up from sleep issue: On HP ZBook Fury G1i 16 (Arrow Lake-S, integrated display engine identifying as meteorlake D0, PCI 8086:7d67), every resume from s2idle after a multi-hour dwell produces a stack of i915 *ERROR* messages from the C10 PHY / DPLL state-restore path. The driver retries and eventually recovers, so the display *does* come back, but the retry loop takes ~5-10 seconds — long enough that users report "the display didn't wake up." Short cycles (seconds-to-minutes of dwell) wake instantly with no errors. The error stack is byte-for-byte identical across two reproductions and across `i915.enable_psr=0`, `i915.enable_dc=0`, and `i915.enable_fbc=0`. Those flags do not reach the code path that's racing. Earlier, before `i915.enable_psr=0` was applied, the same regime caused hard hangs (`Atomic update failure on pipe A`) requiring power-cycle. PSR-disable converted the failure mode from "hang" to "slow recover" but did not eliminate it. `xe.force_probe=7d67` was also tested as a workaround. xe binds cleanly on this device but suffers a different bug: `Tile0: GT0: Engine reset engine_class=rcs guc_id=48 state=0x289` repeating across each suspend cycle (`drm_WARN_ON_ONCE(ret == -110)`), eventually wedging the display. Not viable as a workaround on this kernel. NVIDIA dGPU is fully exonerated: `nvidia-suspend.service` and `nvidia-resume.service` `Finished` cleanly across every cycle. ## System * Distro: Ubuntu 26.04 LTS (resolute) * Kernel: 7.0.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Mon Apr 13 11:09:53 UTC 2026 x86_64 * Package: linux-image-7.0.0-14-generic 7.0.0-14.14 * Firmware pkg: linux-firmware 20260319.git217ca6e4.1ubuntu * HW: HP ZBook Fury G1i 16 inch Mobile Workstation PC, BIOS X96 Ver. 01.01.19 (2025-11-22) (latest per fwupdmgr) * iGPU: Intel Corporation Arrow Lake-S [Intel Graphics] [8086:7d67] (rev 06), driver: i915 * dGPU: NVIDIA Corporation GB205GLM [RTX PRO 3000 Blackwell Generation Laptop GPU] [10de:2f38] (rev a1), driver: nvidia 580.142 (open kernel modules) * Loaded i915 firmware: mtl_dmc.bin (v2.23), mtl_guc_70.bin v70.53.0, mtl_huc_gsc.bin v8.5.4 * Sleep mode: s2idle only (`ACPI: PM: (supports S0 S4 S5)` — firmware does not expose S3) * Kernel cmdline (current):   `quiet splash i915.enable_psr=0 i915.enable_dc=0 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=20 i915.enable_fbc=0` * Session: KDE Plasma on Wayland (sddm) ## Reproduction 1. Boot, log in, do normal work (browser, IDE, terminals). 2. Close laptop lid (or `systemctl suspend`) for ≥2 hours. 3. Open lid / press a key. Expected: panel relights within ~500 ms, no kernel ERRORs. Actual: panel relights after ~5-10 s, journal contains the error stack below. ## Journal trace (boot 2026-04-29 05:48, dwell 05:51:11 → 07:59:21 = 2 h 8 min) ``` PM: suspend entry (s2idle) PM: Some devices failed to suspend, or early wake event detected PM: suspend exit PM: suspend entry (s2idle) [2 h 8 min later] PM: suspend exit i915 0000:00:02.0: [drm] *ERROR* Failed to bring PHY A to idle. i915 0000:00:02.0: [drm] *ERROR* PHY A Read 0c70 failed after 3 retries. i915 0000:00:02.0: [drm] *ERROR* PHY A Write 0c70 failed after 3 retries. i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] flip_done timed out i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in pixel_rate                        (expected 1220171, found 92553) i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in dpll_hw_state i915 0000:00:02.0: [drm] *ERROR* expected: i915 0000:00:02.0: [drm] *ERROR* cx0pll_hw_state: lane_count: 4, ssc_enabled: no,                                    use_c10: yes, tbt_mode: no i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 810000, fracen: yes, i915 0000:00:02.0: [drm] *ERROR* quot: 61440, rem: 0, den: 1, i915 0000:00:02.0: [drm] *ERROR* multiplier: 210, tx_clk_div: 0. i915 0000:00:02.0: [drm] *ERROR* found: i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 61440, fracen: no, i915 0000:00:02.0: [drm] *ERROR* multiplier: 16, tx_clk_div: 0. ``` The expected vs found C10 PLL clock (810 MHz HBR3 vs 61 MHz fallback) is the key signal: the panel's eDP link comes back at the wrong rate, the driver retries and eventually re-locks at the correct rate. This is in `drivers/gpu/drm/i915/display/intel_cx0_phy.c` / DPLL state restore — below the layers reachable by `enable_psr` / `enable_dc` / `enable_fbc`. ## What I have already tried | change | wake outcome on long dwell | |---|---| | (default) | hard hang, `Atomic update failure on pipe A`, requires power-cycle | | `i915.enable_psr=0` (only) | clean wake on short cycles, untested at long dwell | | `i915.enable_psr=0 i915.enable_dc=0` | slow recover (~5-10 s) at 6 h 41 min dwell, full error stack | | `... i915.enable_fbc=0` (added) | same: slow recover, identical error stack at 2 h 8 min dwell | | `i915.force_probe=!7d67 xe.force_probe=7d67` | xe binds cleanly, but `GT0: Engine reset` storm during cycles, eventual wedge | linux-firmware is at the latest candidate for 26.04 (20260319.git217ca6e4.1ubuntu). linux-image-oem-26.04 does not exist yet. ## Why this matters This is a clean reproduction of a likely-upstream Arrow Lake-S regression in the cx0/c10pll DPLL state-restore path during s2idle resume. The error signature is highly diagnostic and consistent across runs. Fix has not landed in 7.0.0-14.14; would benefit from being picked into the 26.04 kernel from upstream once available. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Wed Apr 29 08:18:09 2026 InstallationDate: Installed on 2026-03-27 (33 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260325) MachineType: HP HP ZBook Fury G1i 16 inch Mobile Workstation PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-14-generic root=UUID=2b2b39cc-2151-49f5-9205-74e3f9f1f999 ro quiet splash i915.enable_psr=0 i915.enable_dc=0 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=20 i915.enable_fbc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 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: 11/22/2025 dmi.bios.release: 1.19 dmi.bios.vendor: HP dmi.bios.version: X96 Ver. 01.01.19 dmi.board.name: 8DE2 dmi.board.vendor: HP dmi.board.version: KBC Version 55.35.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 85.53 dmi.modalias: dmi:bvnHP:bvrX96Ver.01.01.19:bd11/22/2025:br1.19:efr85.53:svnHP:pnHPZBookFuryG1i16inchMobileWorkstationPC:pvrSBKPFV3:rvnHP:rn8DE2:rvrKBCVersion55.35.00:cvnHP:ct10:cvr:skuB14E7AV:pfa103C_5336ANHPZBook: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Fury G1i 16 inch Mobile Workstation PC dmi.product.sku: B14E7AV dmi.product.version: SBKPFV3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150605/+subscriptions

[Bug 2154140] Re: USBIO MTL-CVF ACPI binding missing for Dell Latitude 7450 IPU6 camera

** 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/2154140 Title: USBIO MTL-CVF ACPI binding missing for Dell Latitude 7450 IPU6 camera Status in linux package in Ubuntu: New Bug description: On a Dell Latitude 7450, the internal IPU6 MIPI camera does not work with the Ubuntu `7.0.0-15-generic` USBIO module stack because the USBIO auxiliary GPIO and I2C devices are not associated with the platform's MTL-CVF ACPI nodes: - USBIO GPIO provider: `INTC10D1` / `_UID VGPO` - USBIO I2C adapters: `INTC10D2` / `_UID VIC0` and `INTC10D2` / `_UID VIC1` Without that binding, `int3472-discrete` cannot resolve the GPIO provider for the camera power resources and the OV02E10 sensor path does not probe correctly. ## Affected System - Hardware: Dell Latitude 7450 - OS: Ubuntu 26.04 LTS - Kernel tested: `7.0.0-15-generic` - USBIO bridge: `2ac1:20c9 SLS Lattice AI USB 2.0` - Sensor path: `OVTI02E1:00` / `ov02e10` - ACPI nodes observed: - `/sys/bus/acpi/devices/INTC10D1:00` - `/sys/bus/acpi/devices/INTC10D2:00` - `/sys/bus/acpi/devices/INTC10D2:01` ## Failure Mode Before the USBIO binding fix, the kernel logs contained: ```text intel-ipu6 0000:00:05.0: Found supported sensor OVTI02E1:00 intel-ipu6 0000:00:05.0: Connected 1 cameras int3472-discrete INT3472:01: cannot find GPIO chip INTC10D1:00, deferring int3472-discrete INT3472:0c: cannot find GPIO chip INTC10D1:00, deferring ``` After partial USBIO I2C work, the OV02E10 client existed but probe still failed without the complete binding/power path: ```text ov02e10 i2c-OVTI02E1:00: Error writing reg 0x00fd: -6 ov02e10 i2c-OVTI02E1:00: failed to find sensor: -6 ``` The media graph lacked an `ov02e10` entity and `/dev/video0` did not produce usable frames. ## Fix The attached patch is a reduced USBIO backport candidate for Ubuntu's `intel-usbio-dkms_0~git202510282139.ee221eca-0ubuntu1` source. It does the following: - adds `INTC10D1` to the USBIO GPIO ACPI HID table, - adds `INTC10D2` to the USBIO I2C ACPI HID table, - sets `gpio_chip.fwnode = dev_fwnode(dev)` for ACPI GPIO lookup, - changes `usbio_client_acpi_bind()` to search ACPI children under the USBIO auxiliary device's parent device chain, so matching remains scoped to this physical USBIO bridge rather than using a global HID lookup. The patch intentionally excludes local debug instrumentation and dead-end experiments. ## Test Case 1. Boot the affected kernel without the patch. 2. Check: ```bash sudo journalctl -b -k --no-pager -g 'INTC10D1|INTC10D2|INT3472|OVTI02E1|ov02e10|usbio|ipu' tools/v4l-utils/usr/bin/media-ctl -p timeout 20s gst-launch-1.0 -v v4l2src device=/dev/video0 num-buffers=30 ! fakesink ``` Expected broken result: - `int3472-discrete` cannot find GPIO chip `INTC10D1:00`, or - `ov02e10` fails probing with `failed to find sensor: -6`, and - no usable video stream from `/dev/video0`. 3. Build and boot with the attached USBIO patch. 4. Check the same commands. Expected fixed result: - USBIO GPIO chip is associated with `INTC10D1:00`, - `OVTI02E1:00` binds to `ov02e10`, - media graph contains an `ov02e10` entity linked to `Intel IPU6 CSI2 1`, - `/dev/video0` streams successfully. Validated locally after the reduced binding and related already-upstream power support were present: ```text ov02e10 16-0010 media entity present gst-device-monitor-1.0 Video/Source reports Intel MIPI Camera (V4L2) gst-launch-1.0 -v v4l2src device=/dev/video0 num-buffers=30 ! fakesink completes captured frames at 1280x960 show usable video once the physical shutter is open ``` ## Regression Potential Low to moderate. The patch adds new ACPI HIDs for MTL-CVF USBIO GPIO/I2C devices and adjusts the existing USBIO ACPI binding helper to search ACPI companions up the current USB device's parent chain. It deliberately avoids a global `acpi_dev_get_first_match_dev()` fallback, so systems with multiple USBIO bridges or multiple `INTC10D2` islands should not bind to an unrelated ACPI node. The GPIO fwnode assignment is required for ACPI GPIO lookup by consumers such as INT3472. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154140/+subscriptions

[Bug 2149877] Re: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system

I also confirm that 7.0.0-17 from proposed solves the random ~1 second freezes - mostly happening in games, but not exclusively - which started after the migration from 25.10 to 26.04 / 7.0.0.14. I have an AMD Ryzen 7 8700F and a RX 9060 XT. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149877 Title: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: For the past few days I have been experiencing intermittent micro‑stutters in Ubuntu 26.04. The mouse cursor freezes for about half a second, and occasionally the system audio also cuts out briefly. This happens irregularly but repeatedly. The issue started after updating to Linux 7.0.0‑14‑generic. Around the same time, linux‑firmware was also updated, so I cannot determine which change might be responsible. On my laptop (Intel + Nvidia) I cannot reproduce the issue, but another user with AMD hardware reported similar symptoms on Discourse. Affected hardware: · CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz · GPU: AMD Radeon RX 9060 XT · OS: Ubuntu 26.04 Observed behaviour: · Mouse cursor freezes for ~0.5 seconds (“micro‑stutter”). · Occasional short audio dropouts. · I have not noticed the issue while gaming, although another user claims it also happens there. I would appreciate guidance on additional tools or diagnostics that could help identify the root cause. At the moment, the only evidence I can provide is the observed behaviour described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149877/+subscriptions

[Bug 2148630] Re: Brightness control does not work at all on ROG Zephyrus G14 GA403WP laptop

Thanks for confirming that brightness dimming works again on kernel 7.0.0-15-generic — that's great news. I'll go ahead and mark this bug as Fix Released. One quick note: you mentioned concern about Ubuntu potentially missing the pixel-shifting anti-burning feature that Asus provides on Windows. That's a separate (and valid) concern from the brightness-control fix we just confirmed. If you'd like, feel free to file a new bug specifically about OLED pixel shifting support — that would be best tracked as its own issue rather than folded into this resolved report. Thanks again for your help testing and closing this out. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** No longer affects: linux (Ubuntu Resolute) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148630 Title: Brightness control does not work at all on ROG Zephyrus G14 GA403WP laptop Status in linux package in Ubuntu: Fix Released Bug description: I am not sure if this is the right package to raise this bug on. The brightness control for the built in display on this laptop does not work at all, booted into the Resolute daily live distro. Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260415) Happy to pull logs once I can work out which package is actually responsible for display control. This is an OLED so it's pretty critical for dimming to work. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: gnome-control-center 1:50.0-0ubuntu4 ProcVersionSignature: Ubuntu 7.0.0-13.13-generic 7.0.0-rc7 Uname: Linux 7.0.0-13-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 26.04.2 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 01:20:53 2026 LiveMediaBuild: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260415) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148630/+subscriptions

[Bug 2148630] Re: Brightness control does not work at all on ROG Zephyrus G14 GA403WP laptop

Thanks Roy. I don't use Ubuntu full time on this, I have the release version of 26.04 installed on an external drive for now. I think this can be closed, dimming works as of 7.0.0-15-generic. (although I would be concerned Ubuntu is missing the pixel-shifting anti-burning stuff that Asus apparently has on Windows) For others, I will add that there's now two backlight devices in /sys # ls /sys/class/backlight/ amdgpu_bl2 nvidia_0 Maybe I managed to grab a daily just before support was added? -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148630 Title: Brightness control does not work at all on ROG Zephyrus G14 GA403WP laptop Status in linux package in Ubuntu: Incomplete Status in linux source package in Resolute: New Bug description: I am not sure if this is the right package to raise this bug on. The brightness control for the built in display on this laptop does not work at all, booted into the Resolute daily live distro. Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260415) Happy to pull logs once I can work out which package is actually responsible for display control. This is an OLED so it's pretty critical for dimming to work. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: gnome-control-center 1:50.0-0ubuntu4 ProcVersionSignature: Ubuntu 7.0.0-13.13-generic 7.0.0-rc7 Uname: Linux 7.0.0-13-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 26.04.2 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 01:20:53 2026 LiveMediaBuild: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260415) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148630/+subscriptions

[Bug 2143301] Re: Enable new Intel WCL soundwire support

@anthonywong Just would like to check, is this SRU blocked on something else? -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2143301 Title: Enable new Intel WCL soundwire support Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.17 package in Ubuntu: Invalid Status in firmware-sof source package in Noble: Fix Committed Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Released Status in firmware-sof source package in Questing: Fix Committed Status in linux source package in Questing: New Status in linux-oem-6.17 source package in Questing: Invalid Status in firmware-sof source package in Resolute: Fix Released Status in linux source package in Resolute: Fix Released Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] New Dell Slate-1-Piece and Congo platform powered by Intel WildcatLake will have no basic audio functions w/o new firmware-sof which has the new DSP firmware and TPLG files ================ kernel ============================== Realtek on WCL: (Congo WCL) https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/sound/soc/codecs/rt722-sdca.c?id=a27539810e1e61efcfdeb51777ed875dc61e9d49 [git.kernel.org] CirrusLogic on WCL: (Slate-1-Piece WCL) https://lore.kernel.org/linux-sound/aYMpbnzi%2FUTO5Fqs@opensource.cirrus.com/T/#t <=============== firmware-sof ======================== [Fix] c78aea2df366275fed6c7b090bae3575951de57f Add 2.14.1 signed firmware binaries for Intel MTL+ targets f3e02da867b54e6061190d7ff1549e4f00bba17c Add 2.14.1 firmware binaries for Intel MTL and newer targets cdd3c8f9dd879a51dc8ed3c9aa0b7b0a49c108d8 Add 2.14 tools and topology binaries for Intel MTL and newer targets 11fc822288122b83296e634e8508f483c289d565 v2.14.x: add topologies for v2.14.2 e65a0d4f3ffceaf8a01df7f519707ffaf69746ef v2.14.x: add topologies for v2.14.3 [Test Case] 1. Boot up the machine of new Dell Intel WCL Congo and Slate-1-Piece platform powered by Intel WCL 2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices 3. Click test icon for basic audio output functions 4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions. 5. Test on machines of Intel ARL/LNL/MTL/PTL platforms for possible regression [Where problems could occur] Per comment from Intel, the primary requirement is that the topology file (sof-ptl-foo.tplg) and DSP firmware (sof-ptl.ri) are a pair and need to be from the same major version. If we upgrade of FW for only a single generation (e.g. only for WCL) This will be problematic. The main problem is that you may have two platforms (let’s say PTL and ARL) using same topology files. If you update FW for only PTL, you should also update the topology files used by PTL (FW+tplg always a pair!), but then if one of the topology files is used by some ARL products you may have problems (-> scenario 2 problem on ARL then). So we need to upgrade the DSP FW and the TPLG both for all MTL+ platforms (include ARL/LNL/MTL/PTL/WCL) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2143301/+subscriptions