rom1@rom1-M3800:~$ lsmod | grep dell dell_laptop 40960 0 dell_wmi 28672 1 dell_laptop dell_smbios 36864 2 dell_wmi,dell_laptop dell_smm_hwmon 36864 0 dcdbas 24576 1 dell_smbios sparse_keymap 12288 1 dell_wmi dell_wmi_descriptor 20480 2 dell_wmi,dell_smbios dell_lis3lv02d 16384 0 dell_smo8800 16384 0 dell_rbtn 20480 0 video 77824 3 dell_wmi,dell_laptop,i915 wmi 36864 7 video,dell_wmi,wmi_bmof,dell_smm_hwmon,dell_smbios,dell_wmi_descriptor,mxm_wmi -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150737 Title: M3800 keyboard backlight problem ubuntu 26.04 Status in linux package in Ubuntu: New Bug description: Hi, I have a bug related to the keyboard backlight of my DELL M3800. If I use FN + F10 key combinaison all is working good. If I try to use the gnome setting or kde setting, nothing happens. rom1@rom1-M3800:~$ ls /sys/class/leds dell::kbd_backlight input3::capslock input3::numlock input3::scrolllock phy0-led rom1@rom1-M3800:~$ cat /sys/class/leds/dell::kbd_backlight/brightness 0 rom1@rom1-M3800:~$ cat /sys/class/leds/dell::kbd_backlight/max_brightness 2 rom1@rom1-M3800:~$ cat /sys/class/leds/dell::kbd_backlight/trigger [none] usb-gadget usb-host rfkill-any rfkill-none kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock disk-activity disk-read disk-write mtd nand-disk cpu cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 panic ACAD-online BAT1-charging-or-full BAT1-charging BAT1-full BAT1-charging-blink-full-solid BAT1-charging-orange-full-green mmc0 rc-feedback bluetooth-power hci0-power rfkill0 rfkill1 phy0rx phy0tx phy0assoc phy0radio rfkill2 If I use the key combinaison I can see the value of brightness move from 0 to 2 or 1 and physically the keyboard backlight works well. If I try to force the value to 2 in the brightness using command line, nothing happens and the value foes back to 0. I tried with Ubuntu 26.04, Kubuntu 26.04 and Fedora 44 gnome + kde. All have the same behaviour. When writing to /sys/class/leds/dell::kbd_backlight/brightness via echo, the command returns without error but the value immediately reverts to 0. The file permission show -rw-r--r-- 1 root root. The driver appears to silently reject writes from userspace while accepting them from the ACPI firmware via FN + F10. Could you please fix this ? Best regards. 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: rom1 3768 F.... wireplumber /dev/snd/controlC0: rom1 3768 F.... wireplumber /dev/snd/seq: rom1 3749 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 13:07:07 2026 InstallationDate: Installed on 2026-04-24 (6 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. Dell Precision M3800 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=1e291b4f-afed-45e8-ab4d-25bdbd06707a 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: 07/02/2020 dmi.bios.release: 65.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/02/2020:br65.14:svnDellInc.:pnDellPrecisionM3800:pvrA14:rvnDellInc.:rnDellPrecisionM3800:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:skuDellPrecisionM3800:pfa: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150737/+subscriptions
пятница
[Bug 2112462] Re: Unexpected system reboot at loading GUI session on some AMD platforms
This bug is awaiting verification that the linux-azure- nvidia/6.8.0-1034.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-azure-nvidia-v2 verification-needed-noble-linux-azure-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2112462 Title: Unexpected system reboot at loading GUI session on some AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux-oem-6.14 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.11 source package in Noble: Fix Released Status in linux-oem-6.14 source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Status in linux source package in Oracular: Won't Fix Status in linux-oem-6.11 source package in Oracular: Invalid Status in linux-oem-6.14 source package in Oracular: Invalid Status in linux-oem-6.8 source package in Oracular: Invalid Status in linux source package in Plucky: Fix Released Status in linux-oem-6.11 source package in Plucky: Invalid Status in linux-oem-6.14 source package in Plucky: Invalid Status in linux-oem-6.8 source package in Plucky: Invalid Status in linux source package in Questing: Fix Released Status in linux-oem-6.11 source package in Questing: Invalid Status in linux-oem-6.14 source package in Questing: Invalid Status in linux-oem-6.8 source package in Questing: Invalid Bug description: [SRU Justification] [ Impact ] AMD Strix Halo devices experience unexpected reboots while starting GUI session every boot. This is caused by: * 689275140cb8e drm/amdgpu/hdp7.0: do a posting read when flushing HDP * abe1cbaec6cfe drm/amdgpu/hdp6.0: do a posting read when flushing HDP * f756dbac1ce1d drm/amdgpu/hdp5.2: do a posting read when flushing HDP * cf424020e040b drm/amdgpu/hdp5.0: do a posting read when flushing HDP * c9b8dcabb52af drm/amdgpu/hdp4.0: do a posting read when flushing HDP And fixed by: * 5a11a27677311 drm/amdgpu/hdp7: use memcfg register to post the write for HDP flush * ca28e80abe421 drm/amdgpu/hdp6: use memcfg register to post the write for HDP flush * dbc988c689333 drm/amdgpu/hdp5.2: use memcfg register to post the write for HDP flush * 0e33e0f339b91 drm/amdgpu/hdp5: use memcfg register to post the write for HDP flush * f690e3974755a drm/amdgpu/hdp4: use memcfg register to post the write for HDP flush [ Test Plan ] 1. Install -proposed kernel 2. Reboot to the installed kernel and check if the device may finish boot process to GUI session. [ Where problems could occur ] No. This fix a problem when reading back the whole mapped KFD_MMIO_REMAP_HDP_MEM_FLUSH_CNTL register by reading another register that also triggers the flush. [ Other Info ] The causing commits were first committed to v6.13-rc1 , and have also been backported to v6.12.5, v6.6.69, v6.1.120. The fixes are available in v6.15-rc6, also backported to v6.14.7, v6.12.29, v6.6.91, v6.1.139, therefore this affects following Ubuntu kernels: * linux/plucky: all (currently 6.14.0-22.22) * linux-oem-6.14/noble: all (currently 6.14.0-1005.5) * linux/oracular: 6.11.0-20.20 to latest (currently 6.11.0-28.28) * linux-oem-6.11/noble: 6.11.0-1017.17 to latest (currently 6.11.0-1024.24) * linux/noble: 6.8.0-58.60 to latest (currently 6.8.0-62.65) * linux-oem-6.8/noble: 6.8.0-1026.26 to latest (currently 6.8.0-1029.29) Nominate for linux/noble, linux-oem-6.8/noble, linux/oracular, linux- oem-6.11/noble, linux/plucky, and linux-oem-6.14/noble. ========== original bug report ========== With 5 v6.13-rc1 commits , also backported to v6.12.5, v6.6.69, v6.1.120, some (at least AMD Strix Halo) devices may experience unexpected reboots while starting GUI session every boot: * 689275140cb8e drm/amdgpu/hdp7.0: do a posting read when flushing HDP * abe1cbaec6cfe drm/amdgpu/hdp6.0: do a posting read when flushing HDP * f756dbac1ce1d drm/amdgpu/hdp5.2: do a posting read when flushing HDP * cf424020e040b drm/amdgpu/hdp5.0: do a posting read when flushing HDP * c9b8dcabb52af drm/amdgpu/hdp4.0: do a posting read when flushing HDP The fixes are available in v6.15-rc6, also backported to v6.14.7, v6.12.29, v6.6.91, v6.1.139: * 5a11a27677311 drm/amdgpu/hdp7: use memcfg register to post the write for HDP flush * ca28e80abe421 drm/amdgpu/hdp6: use memcfg register to post the write for HDP flush * dbc988c689333 drm/amdgpu/hdp5.2: use memcfg register to post the write for HDP flush * 0e33e0f339b91 drm/amdgpu/hdp5: use memcfg register to post the write for HDP flush * f690e3974755a drm/amdgpu/hdp4: use memcfg register to post the write for HDP flush This affects following Ubuntu kernels: * linux/plucky: all (currently 6.14.0-22.22) * linux-oem-6.14/noble: all (currently 6.14.0-1005.5) * linux/oracular: 6.11.0-20.20 to latest (currently 6.11.0-28.28) * linux-oem-6.11/noble: 6.11.0-1017.17 to latest (currently 6.11.0-1024.24) * linux/noble: 6.8.0-58.60 to latest (currently 6.8.0-62.65) * linux-oem-6.8/noble: 6.8.0-1026.26 to latest (currently 6.8.0-1029.29) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2112462/+subscriptions
[Bug 2055083] Re: Drop fips-checks script from trees
This bug is awaiting verification that the linux-azure- nvidia/6.8.0-1034.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-azure-nvidia-v2 verification-needed-noble-linux-azure-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2055083 Title: Drop fips-checks script from trees Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] When producing a new version of some kernels, we need to check for changes that might affect FIPS certs and justify why a commit was kept. For that, we have a fips-checks script that lives under debian/ in Focal, Jammy, Mantic and Noble. This script has been moved to `cranky`[1], so now there is no need to have this script in the kernel Git trees as well. [1] https://git.launchpad.net/~canonical-kernel/+git/kteam- tools/commit/?id=2ab9364d4b4c18bee7d835787d7dd11990103bca [Fix] Remove the fips-checks script and its calls. [Test Plan] Prepare a kernel and ensure that the `cranky close` step runs without any errors. [Where problems could occur] This only affects the preparation of FIPS kernels and not the kernel final binary. Moreover, I've prepared some FIPS kernels from the 2024.03.04 cycle relying on `cranky check-fips` to ensure that we have it working well on the cranky side too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055083/+subscriptions
[Bug 2103680] Re: System hangs when running the memory stress test
This bug is awaiting verification that the linux-azure- nvidia/6.8.0-1034.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-azure-nvidia-v2 verification-needed-noble-linux-azure-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2103680 Title: System hangs when running the memory stress test Status in HWE Next: Opinion Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux-oem-6.14 package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.11 source package in Noble: Fix Released Status in linux-oem-6.14 source package in Noble: Fix Released Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Plucky: Fix Released Status in linux-oem-6.11 source package in Plucky: Invalid Status in linux-oem-6.14 source package in Plucky: Invalid Status in linux-oem-6.17 source package in Plucky: Invalid Status in linux source package in Questing: Fix Released Status in linux-oem-6.11 source package in Questing: Invalid Status in linux-oem-6.14 source package in Questing: Invalid Status in linux-oem-6.17 source package in Questing: Invalid Bug description: [Impact] While running the memory stress test, the system becomes unresponsive. [Fix] The commit from linux-next fixes the issue 19c5fb83f2a4 mm: page_alloc: avoid kswapd thrashing due to NUMA restrictions [Test] Run the following command on the machine sudo stress-ng --aggressive --verify --timeout 300 --mmapmany 0 It should finish the test in 5mins. [Where problems could occur] Given that the patch was reviewed and tested by multiple experienced kernel developers, the likelihood of it causing a noticeable regression is very low. It is far more likely to improve performance and stability on NUMA systems under the conditions described in the commit message. ========================= For OEM-6.11 ============================ [Impact] While running the memory stress test, the system becomes unresponsive. [Fix] The commit in v6.11-rc1 introduce the issue. 4e63aeb5d010 blk-wbt: don't throttle swap writes in direct reclaim And we are seeking for help from the patch owner and other developers on the mailing list https://lkml.org/lkml/2025/3/20/90 Currently, we have to revert this commit, because this issue happens on many platforms. [Test] Run the following command on the machine with kernel version greater or equal to v6.11 sudo stress-ng --aggressive --verify --timeout 300 --mmapmany 0 It should finish the test in 5mins. [Where problems could occur] From the commit message reverts this commit may trigger a hang "When a process holds a lock to allocate a free page, and enters direct reclaim because there is no free memory, then it might trigger a hung due to the wbt throttling that causes other processes to fail to get the lock." To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2103680/+subscriptions
[Bug 2060130] Re: [SPR][EMR][GNR] TDX: efi: TD Measurement support for kernel cmdline/initrd sections from EFI stub
This bug is awaiting verification that the linux-azure- nvidia/6.8.0-1034.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-azure-nvidia-v2 verification-needed-noble-linux-azure-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2060130 Title: [SPR][EMR][GNR] TDX: efi: TD Measurement support for kernel cmdline/initrd sections from EFI stub Status in linux package in Ubuntu: Fix Released Status in linux-intel package in Ubuntu: New Status in linux source package in Noble: Fix Released Status in linux-intel source package in Noble: Fix Released Bug description: This is a public version of https://bugs.launchpad.net/bugs/2058835 [Description] When a TD is created, during the boot process, steps like loading the firmware, bootloader, kernel image, etc are measured and stored in RTMR registers to support the trusted boot model. After boot, this measured value is used to validate the integrity of the boot process. During the direct boot process, bootloader is responsible for measuring the kernel image before loading the kernel. But if the kernel is loaded from EFI bootstub, the related measurements needs to be owned by the EFI bootstub. This support needs to be added to Linux EFI boot stub code. Also, as per the following discussion, the kernel command line or initrd section measurements also needs be owned by the EFI bootsub. https://edk2.groups.io/g/devel/topic/93737108?p=Created%2C%2C%2C20%2C2%2C0%2C0%3A%3A%2C%2C%2C0%2C0%2C0%2C93737108 [Fix] Cherry pick cleanly: d228814b1913 efi/libstub: Add get_event_log() support for CC platforms ac93cbfc2a2c efi/libstub: Measure into CC protocol if TCG2 protocol is absent 0bbe5b0ea97a efi/libstub: Add Confidential Computing (CC) measurement typedefs 7a1381e8313f efi/tpm: Use symbolic GUID name from spec for final events table 3e0b0f880e9e efi/libstub: Use TPM event typedefs from the TCG PC Client spec External Links: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=70ef654469b371d0a71bcf967fa3dcbca05d4b25 Those are all merged into upstream. [Test Plan] Build/sign/boot with secure boot enabled. [Where problems could occur] At boot time, as this is modifying the efi libstub. Could be impacting secure boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060130/+subscriptions
[Bug 2008882] Re: Make backlight module auto detect dell_uart_backlight
This bug is awaiting verification that the linux-azure- nvidia/6.8.0-1034.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-azure-nvidia-v2 verification-needed-noble-linux-azure-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2008882 Title: Make backlight module auto detect dell_uart_backlight Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] There are acpi_video* sysfs backlight interface in the system which are not working. For Dell AIO platforms, we use dell_uart_backlight to control the display brightness. The old way to fix this is to unregister acpi backlight interfaces in the backlight driver, but it may lead to some issues and the unregister function has been removed since v6.1-rc1 77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()") [Fix] The new way to do this is to collect all the quirk and auto detection method in video_detect.c I added an audo detection for the Dell AIO platoform to the driver which should do the same thing as the old way. [Test] Verified on the Dell AIO platform and confirmed there is only on dell_uart_backlight in the sysfs, and no acpi_video* interface. [Where problems could occur] There should be no regression potential, it uses different way to do the same thing, should be pretty safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008882/+subscriptions
[Bug 2066233] Re: amdgpu hangs on DCN 3.5 at bootup: RIP: 0010:dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu]
This bug is awaiting verification that the linux-azure- nvidia/6.8.0-1034.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-azure-nvidia-v2 verification-needed-noble-linux-azure-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2066233 Title: amdgpu hangs on DCN 3.5 at bootup: RIP: 0010:dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu] Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Status in linux source package in Oracular: Fix Released Status in linux-oem-6.8 source package in Oracular: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2066233 [Impact] Newer VBIOS on DCN 3.5 bumped the version of IntegratedInfo table from 2.2 to 2.3. This version uses same structure. Version 2.3 is missing from the construct_integrated_info() parser, so it leads to NULL pointer dereference. ``` Call Trace: <TASK> ? show_regs+0x72/0x90 ? __die+0x25/0x80 ? page_fault_oops+0x154/0x4c0 ? ttm_bo_kmap+0x11d/0x310 [ttm] ? dma_resv_wait_timeout+0x48/0xe0 ? do_user_addr_fault+0x30e/0x6e0 ? exc_page_fault+0x84/0x1b0 ? asm_exc_page_fault+0x27/0x30 ? dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu] ? dcn35_clk_mgr_construct+0x15a/0x2210 [amdgpu] ? dcn35_hwseq_create+0x23/0x470 [amdgpu] ``` [Fix] Fix landed to upstream v6.9-rc7: 9a35d205f466 ("drm/amd/display: Atom Integrated System Info v2_2 for DCN35") [Test Case] AMDGPU should then be initialized successfully without NULL pointer deref dump at boot. [Where problems could occur] No. New hardware revision with same data only. [Other Info] While this has been landed to v6.9-rc7, expect every kernel version older than that with planned support to the new VBIOS update should be fixed. So far linux/noble and linux-oem-6.8/noble are nominated by chip vendor. ========== original bug report ========== Newer VBIOS on DCN 3.5 bumped the version of IntegratedInfo table from 2.2 to 2.3. This version uses same structure. Version 2.3 is missing from the construct_integrated_info() parser, so it leads to NULL pointer dereference. [Thu May 9 18:02:38 2024] Call Trace: [Thu May 9 18:02:38 2024] <TASK> [Thu May 9 18:02:38 2024] ? show_regs+0x72/0x90 [Thu May 9 18:02:38 2024] ? __die+0x25/0x80 [Thu May 9 18:02:38 2024] ? page_fault_oops+0x154/0x4c0 [Thu May 9 18:02:38 2024] ? ttm_bo_kmap+0x11d/0x310 [ttm] [Thu May 9 18:02:38 2024] ? dma_resv_wait_timeout+0x48/0xe0 [Thu May 9 18:02:38 2024] ? do_user_addr_fault+0x30e/0x6e0 [Thu May 9 18:02:38 2024] ? exc_page_fault+0x84/0x1b0 [Thu May 9 18:02:38 2024] ? asm_exc_page_fault+0x27/0x30 [Thu May 9 18:02:38 2024] ? dcn35_clk_mgr_construct+0x183/0x2210 [amdgpu] [Thu May 9 18:02:38 2024] ? dcn35_clk_mgr_construct+0x15a/0x2210 [amdgpu] [Thu May 9 18:02:38 2024] ? dcn35_hwseq_create+0x23/0x470 [amdgpu] ... Fix landed to upstream v6.9-rc7: 9a35d205f466 ("drm/amd/display: Atom Integrated System Info v2_2 for DCN35") To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2066233/+subscriptions
[Bug 2110090] Re: System will restart while resuming with SATA HDD or nvme installed with password set
This bug is awaiting verification that the linux-azure- nvidia/6.8.0-1034.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-azure-nvidia-v2 verification-needed-noble-linux-azure-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2110090 Title: System will restart while resuming with SATA HDD or nvme installed with password set Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux-oem-6.14 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.11 source package in Noble: Fix Released Status in linux-oem-6.14 source package in Noble: Fix Released Status in linux source package in Plucky: Fix Released Status in linux-oem-6.11 source package in Plucky: Invalid Status in linux-oem-6.14 source package in Plucky: Invalid Bug description: [Impact] The BIOS PCI device configuration and restoration during modern standby will check the ACPI function _REG value. It expects this value to be 0x2 (PCI_Config), and this value is returned by the operating system. Windows returns 0x2 (PCI_Config), which allows the PCI device configuration and restoration function to complete successfully. However, Ubuntu returns 0x3 (EmbeddedControl), which prevents the SATA HDD password unlock function from working during Modern Standby resume. [Fix] The commit which will be included in v6.16 explicitly set all devices into D0 during initialization, so that _REG method works as expected. https://lore.kernel.org/all/20250424043232.1848107-1-superm1@kernel.org/ 4d4c10f763d78 PCI: Explicitly put devices into D0 when initializing [Test] 1. Install ubuntu 2404 on any machine(the issue has been found on Dell Pro Micro Mini PC with AMD Ryzen Processors), and enabled SATA HDD password. 1.1 connect SATA HDD on system 1.2 press F2 enter BIOS menu 1.3 choose the menu “Passwords“ in the left side 1.4 setup passowrd in “Internal HDD Passward“ 1.5 save setting and boot into OS 2. After resume from suspend with w/ SATA HDD installed and hdd password set. 3. The machine should keep working and the SATA HDD could be accessed [Where problems could occur] It's trivial to set the device to D0 state while iniailizing, I don't see it could lead to any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2110090/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-nvidia/5.15.0-1102.103)
All autopkgtests for the newly accepted linux-restricted-modules-nvidia (5.15.0-1102.103) 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-450-server/unknown (amd64) nvidia-graphics-drivers-525-server/525.147.05-0ubuntu2.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-nvidia [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 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
This bug is awaiting verification that the linux-azure- nvidia/6.8.0-1034.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-azure-nvidia-v2 verification-needed-noble-linux-azure-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2042500 Title: Fix after-suspend-mediacard/sdhc-insert test failed Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux-oem-6.8 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: SRU Justification for Noble [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] The new series of the fix has been merged into v6.9 6d4266675279 PCI/ASPM: Update save_state when configuration changes 64dbb2d70744 PCI/ASPM: Disable L1 before configuring L1 Substates c198fafa0125 PCI/ASPM: Call pci_save_ltr_state() from pci_save_pcie_state() 17423360a27a PCI/ASPM: Save L1 PM Substates Capability for suspend/resume 1e11b5494c3d PCI/ASPM: Move pci_save_ltr_state() to aspm.c f3994bba8200 PCI/ASPM: Always build aspm.c fa84f4435a62 PCI/ASPM: Move pci_configure_ltr() to aspm.c [Test Case] 1. suspend and resume. 2. check if the error appears in dmesg ~~~ pcieport 0000:00:1c.0: pciehp: Slot(5): Card not present rtsx_pci 0000:05:00.0: Unable to change power state from D0 to D3hot, device inaccessible rtsx_pci 0000:05:00.0: Unable to change power state from D3cold to D0, device inaccessible ~~~ [Where the problems could occur] Hard to evaluate, these patches change the PCI/ASPM behavior and may lead to PCI devices work abnormal. ============================= [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability for suspend/resume"") reverted saving and restoring of ASPM L1 Substates due to a regression that caused resume from suspend to fail on certain systems. However, we never added this capability back and this is now causing systems fail to enter low power CPU states, drawing more power from the battery. The original revert mentioned that we restore L1 PM substate configuration even though ASPM L1 may already be enabled. This is due the fact that the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state(). Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4 more closely by: 1) Do not restore ASPM configuration in pci_restore_pcie_state() but do that after PCIe capability is restored in pci_restore_aspm_state() following PCIe r6.0, sec 5.5.4. 2) ASPM is first enabled on the upstream component and then downstream (this is already forced by the parent-child ordering of Linux Device Power Management framework). 3) Program ASPM L1 PM substate configuration before L1 enables. 4) Program ASPM L1 PM substate enables last after rest of the fields in the capability are programmed. 5) Add denylist that skips restoring on the ASUS and TUXEDO systems where these regressions happened, just in case. For the TUXEDO case we only skip restore if the BIOS is involved in system suspend (that's forcing "mem_sleep=deep" in the command line). This is to avoid possible power regression when the default suspend to idle is used, and at the same time make sure the devices continue working after resume when the BIOS is involved. [Test Case] 1. suspend and resume. 2. check if the error appears in dmesg ~~~ pcieport 0000:00:1c.0: pciehp: Slot(5): Card not present rtsx_pci 0000:05:00.0: Unable to change power state from D0 to D3hot, device inaccessible rtsx_pci 0000:05:00.0: Unable to change power state from D3cold to D0, device inaccessible ~~~ [where the issue could happen] low, the patch works well on the reported malfunctioned ASUS platform too. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042500/+subscriptions
[Bug 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore
This bug is awaiting verification that the linux-azure- nvidia/6.8.0-1034.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-azure-nvidia-v2 verification-needed-noble-linux-azure-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2048919 Title: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Released Bug description: ---Problem Description--- Regression: uvdevice at /dev/uv not compiled into kernel Machine Type = IBM z15, IBM z16 Contact Information = steffen.eiden@ibm.com ---uname output--- Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x s390x s390x GNU/Linux ---Debugger--- A debugger is not configured ---Additional Hardware Info--- Secure Execution feature code enabled (optional) ---Steps to Reproduce--- # working/ old behavior on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution available) > cat /dev/uv /dev/uv > cat /boot/config-$(uname -r) | grep UV_UAPI CONFIG_S390_UV_UAPI=y that's the expected state for Ubuntu. # current/ non expected behavior since Ubuntu 23.04 the following happens: stock kernel non-modified, latest available > cat /dev/uv cat: /dev/uv: No such file or directory COMMENT: this still can happen if the machine has no Secure Execution feature available However, the following should not be the case under any circumstances: > cat /boot/config-$(uname -r) | grep UV_UAPI # CONFIG_S390_UV_UAPI is not set Somehow that configuration got lost between 22.X and 23.X. Maybe, because IIRC that features got back-ported to 22.X # Proposed Solution: change the kernel config to CONFIG_S390_UV_UAPI=y (same as 22.X backport) or CONFIG_S390_UV_UAPI=m (same as upstream) and provide a new kernel binary Stack trace output: n/a System Dump Info: The system is not configured to capture a system dump. Oops output: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+subscriptions
четверг
[Bug 1918970] Re: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration
** Changed in: maas Status: Incomplete => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: Invalid Status in Ubuntu on IBM z Systems: Triaged Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions
[Bug 2150640] Re: Installer fails internally with a RSync error due to page fault
cat /proc/version_signature Ubuntu 7.0.0-14.14-generic 7.0.0 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150640 Title: Installer fails internally with a RSync error due to page fault Status in linux package in Ubuntu: New Bug description: During install, subiquity calls RSync. But sometimes, at random, RSync fails with a kernel page error: Apr 28 14:22:11 ubuntu subiquity_log.3304[7458]: Running command ['rsync', '-aXHAS', '--one-file-system', '/tmp/tmpmfrhpjlr/mount/', '.'] with allowed return codes [0] (capture=False) Apr 28 14:22:11 ubuntu kernel: BUG: unable to handle page fault for address: ffffffff825c9290 Apr 28 14:22:11 ubuntu kernel: #PF: supervisor read access in kernel mode Apr 28 14:22:11 ubuntu kernel: #PF: error_code(0x0000) - not-present page Apr 28 14:22:11 ubuntu kernel: PGD 1cfe47067 P4D 1cfe47067 PUD 1cfe48063 PMD 0 Apr 28 14:22:11 ubuntu kernel: Oops: Oops: 0000 [#2] SMP NOPTI Apr 28 14:22:11 ubuntu kernel: CPU: 8 UID: 0 PID: 7495 Comm: rsync Tainted: P D O 7.0.0-14-generic #14-Ubuntu PREEMPT(lazy) Apr 28 14:22:11 ubuntu kernel: Tainted: [P]=PROPRIETARY_MODULE, [D]=DIE, [O]=OOT_MODULE Apr 28 14:22:11 ubuntu kernel: Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 28 14:22:11 ubuntu kernel: RIP: 0010:ovl_iterate_merged+0x1d8/0x2b0 [overlay] Apr 28 14:22:11 ubuntu kernel: 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 Apr 28 14:22:11 ubuntu kernel: RSP: 0018:ffffd4ec8278bca8 EFLAGS: 00010286 Apr 28 14:22:11 ubuntu kernel: RAX: 0000000000000000 RBX: ffff8de0a4a7a780 RCX: ffffffff825c9290 Apr 28 14:22:11 ubuntu kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 Apr 28 14:22:11 ubuntu kernel: RBP: ffffd4ec8278bce8 R08: 0000000000000000 R09: 0000000000000000 Apr 28 14:22:11 ubuntu kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8de110301ec0 Apr 28 14:22:11 ubuntu kernel: R13: ffffd4ec8278bdc0 R14: 00000000825c9280 R15: ffff8de0821af238 Apr 28 14:22:11 ubuntu kernel: FS: 00007fe1b1fd9100(0000) GS:ffff8de224a00000(0000) knlGS:0000000000000000 Apr 28 14:22:11 ubuntu kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 28 14:22:11 ubuntu kernel: CR2: ffffffff825c9290 CR3: 00000001cb64f000 CR4: 0000000000750ef0 Apr 28 14:22:11 ubuntu kernel: PKRU: 55555554 Apr 28 14:22:11 ubuntu kernel: Call Trace: Apr 28 14:22:11 ubuntu kernel: <TASK> Apr 28 14:22:11 ubuntu kernel: ovl_iterate+0xd3/0x120 [overlay] Apr 28 14:22:11 ubuntu kernel: ? __pfx_ovl_iterate+0x10/0x10 [overlay] Apr 28 14:22:11 ubuntu kernel: wrap_directory_iterator+0x4f/0x80 Apr 28 14:22:11 ubuntu kernel: shared_ovl_iterate+0x15/0x30 [overlay] Apr 28 14:22:11 ubuntu kernel: iterate_dir+0xc1/0x2a0 Apr 28 14:22:11 ubuntu kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Apr 28 14:22:11 ubuntu kernel: __x64_sys_getdents64+0x76/0x140 Apr 28 14:22:11 ubuntu kernel: ? __pfx_filldir64+0x10/0x10 Apr 28 14:22:11 ubuntu kernel: x64_sys_call+0x100b/0x2390 Apr 28 14:22:11 ubuntu kernel: do_syscall_64+0x115/0x5a0 Apr 28 14:22:11 ubuntu kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Apr 28 14:22:11 ubuntu kernel: ? handle_mm_fault+0x1c0/0x2e0 Apr 28 14:22:11 ubuntu kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Apr 28 14:22:11 ubuntu kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Apr 28 14:22:11 ubuntu kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100 Apr 28 14:22:11 ubuntu kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Apr 28 14:22:11 ubuntu kernel: ? irqentry_exit+0x97/0x5a0 Apr 28 14:22:11 ubuntu subiquity_log.3304[7458]: rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] Apr 28 14:22:11 ubuntu kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Apr 28 14:22:11 ubuntu kernel: ? exc_page_fault+0x94/0x1e0 Apr 28 14:22:11 ubuntu kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e Apr 28 14:22:11 ubuntu kernel: RIP: 0033:0x7fe1b20d07d7 Apr 28 14:22:11 ubuntu kernel: 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 Apr 28 14:22:11 ubuntu kernel: RSP: 002b:00007ffc5f3161c8 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 Apr 28 14:22:11 ubuntu kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe1b20d07d7 Apr 28 14:22:11 ubuntu kernel: RDX: 0000000000008000 RSI: 00005d8aff7c8d80 RDI: 0000000000000003 Apr 28 14:22:11 ubuntu kernel: RBP: 00007ffc5f316200 R08: 00005d8aff7c8d54 R09: 00007fe1b21ecac8 Apr 28 14:22:11 ubuntu kernel: R10: 0000000000008040 R11: 0000000000000293 R12: 0000000000000001 Apr 28 14:22:11 ubuntu kernel: R13: 00005d8aff7c8d50 R14: 00007ffc5f316300 R15: 00007fe1b1fd90b0 Apr 28 14:22:11 ubuntu kernel: </TASK> Apr 28 14:22:11 ubuntu kernel: Modules linked in: bcache btrfs libblake2b ufs qnx4 hfsplus hfs minix msdos jfs nls_ucs2_utils xfs snd_seq_dummy snd_hrtimer qrtr binfmt_misc zfs(PO) spl(O) snd_hda_codec_generic intel_rapl_msr snd_hda_intel intel_rapl_common snd_hda_codec snd_hda_core snd_intel_dspcfg snd_intel_sdw_acpi snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi kvm_amd ccp snd_seq snd_seq_device kvm snd_timer irqbypass snd soundcore i2c_piix4 qxl i2c_smbus drm_ttm_helper ttm input_leds joydev drm_exec mac_hid sch_fq_codel lp ppdev parport_pc parport msr efi_pstore nfnetlink dmi_sysfs qemu_fw_cfg virtiofs vmw_vsock_virtio_transport vmw_vsock_virtio_transport_common vsock autofs4 overlay isofs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 linear 8139too psmouse floppy ghash_clmulni_intel vga16fb serio_raw 8139cp vgastate mii pata_acpi aesni_intel Apr 28 14:22:11 ubuntu kernel: CR2: ffffffff825c9290 Apr 28 14:22:11 ubuntu kernel: ---[ end trace 0000000000000000 ]--- Apr 28 14:22:11 ubuntu kernel: RIP: 0010:ovl_iterate_merged+0x1d8/0x2b0 [overlay] Apr 28 14:22:11 ubuntu kernel: 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 Apr 28 14:22:11 ubuntu kernel: RSP: 0018:ffffd4ec88763b88 EFLAGS: 00010286 Apr 28 14:22:11 ubuntu kernel: RAX: 0000000000000000 RBX: ffff8de082540940 RCX: ffffffff825c9290 Apr 28 14:22:11 ubuntu kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 Apr 28 14:22:11 ubuntu kernel: RBP: ffffd4ec88763bc8 R08: 0000000000000000 R09: 0000000000000000 Apr 28 14:22:11 ubuntu kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8de13c0df080 Apr 28 14:22:11 ubuntu kernel: R13: ffffd4ec88763ca0 R14: 00000000825c9280 R15: ffff8de0821af0f8 Apr 28 14:22:11 ubuntu kernel: FS: 00007fe1b1fd9100(0000) GS:ffff8de224a00000(0000) knlGS:0000000000000000 Apr 28 14:22:11 ubuntu kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 28 14:22:11 ubuntu kernel: CR2: ffffffff825c9290 CR3: 00000001cb64f000 CR4: 0000000000750ef0 Apr 28 14:22:11 ubuntu kernel: PKRU: 55555554 Apr 28 14:22:11 ubuntu kernel: note: rsync[7495] exited with irqs disabled Apr 28 14:22:11 ubuntu subiquity_log.3304[7458]: rsync error: error in rsync protocol data stream (code 12) at io.c(232) [Receiver=3.4.1] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150640/+subscriptions