[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
** Changed in: linux (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-hwe source package in Focal: New Status in livecd-rootfs source package in Focal: New Status in linux source package in Jammy: Fix Released Status in linux-hwe source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: New Bug description: [ Impact ] mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected. Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel. Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel. [ Test Plan ] * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client [ Where problems could occur ] * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
1. Yes. The backport was for 5.15 jammy kernels including HWE derivatives. The user space SRU was done in bug https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1994146 which included Focal. The intent being Focal will only support mqueue if it is using and HWE kernel. 2. Yes that makes sense. I have added a linux-hwe entry for focal ** Also affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe (Ubuntu Jammy) Status: New => Invalid ** Also affects: livecd-rootfs (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in linux source package in Focal: New Status in linux-hwe source package in Focal: New Status in livecd-rootfs source package in Focal: New Status in linux source package in Jammy: Fix Released Status in linux-hwe source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: New Bug description: [ Impact ] mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected. Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel. Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel. [ Test Plan ] * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client [ Where problems could occur ] * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058557] Re: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel
This issue is still present upstream, so I reported it to the original committer of the patch. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058557 Title: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel Status in linux package in Ubuntu: New Bug description: A kernel oops and panic occurred during 22.04 SoC certification on Gunyolk (Grace/Grace) with 6.8 kernel, arm64+largemem variant Steps to reproduce: Run (as root) the following commands: add-apt-repository -y ppa:checkbox-dev/stable apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable apt update apt install -y canonical-certification-server /usr/lib/checkbox-provider-base/bin/stress_ng_test.py disk --device dm-0 --base-time 240 stress_ng_test caused a kernel panic after about 5 minutes. I have attached dmesg output from my reproducer to this report. Initially, this was identified via a panic during the above test, which was running as part of a run of certify-soc-22.04. Attached is a tarball containing: - apport.linux-image-6.8.0-11-generic-64k.kzsondji.apport: The output of `ubuntu-bug linux` on the machine (after reboot) - reproduced-dmesg.202403201942: The dmesg output captured by kdump when I reproduced my original issue by running only the single stress_ng_test.py command above (not the entire cert suite) - original-dmesg.txt: The dmesg output I captured when the stress_ng_test originally failed during the full cert suite run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057155] Re: amdgpu driver crashes running electron application after some time
Anyone looking into this? I get this a few times a week especially with multiple chromium based applications open. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057155 Title: amdgpu driver crashes running electron application after some time Status in linux package in Ubuntu: New Bug description: Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=211055, emitted seq=211057 Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process armcord pid 14844 thread armcord:cs0 pid 14883 Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: amdgpu: GPU reset begin! Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_0.2.1.0 test failed (-110) Mar 11 18:30:07 garrett-desktop kernel: [drm:gfx_v8_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed Mar 11 18:30:07 garrett-desktop kernel: amdgpu: cp is busy, skip halt cp Mar 11 18:30:07 garrett-desktop kernel: amdgpu: rlc is busy, skip halt rlc Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: amdgpu: BACO reset In KDE Wayland session, the screen freezes for a few seconds and then graphical corruption appears on screen. This issue did not happen in previous versions of ubuntu (mantic/jammy) that I have run previously. This appears to be a regresssion in the amdgpu kernel driver or mesa. I have attached a journalctl from the previous boot (any other logs that were auto-uploaded as part of this report are likely not relevant). It is named: look_at_this_journalctl_from_previous_boot.log ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-generic 6.8.0-11.11+1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Mar 11 18:35:54 2024 InstallationDate: Installed on 2022-03-16 (727 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c53f Logitech, Inc. USB Receiver Bus 001 Device 003: ID 05ac:024f Apple, Inc. Aluminium Keyboard (ANSI) Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Micro-Star International Co., Ltd. MS-7B48 ProcFB: 0 amdgpudrmfb 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=1bad4da7-3fac-4981-9976-490388955115 ro quiet splash amdgpu.ppfeaturemask=0x vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-01-22 (50 days ago) dmi.bios.date: 11/18/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.D3 dmi.board.asset.tag: Default string dmi.board.name: Z370-A PRO (MS-7B48) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.D3:bd11/18/2021:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B48:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370-APRO(MS-7B48):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B48 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
Question -- this has landed in various jammy-5.15 kernels. This rolled downstream to the focal HWE kernels (specifically the cloud kernels) 1. was this intentional? 2. if so, could we add an affects for focal as well? it'll help us with tracking downstream dependency changes, specifically in livecd-rootfs: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: Triaged Status in livecd-rootfs package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in livecd-rootfs source package in Jammy: New Bug description: [ Impact ] mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected. Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel. Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel. [ Test Plan ] * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client [ Where problems could occur ] * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058557] Re: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel
I have isolated the cause of this bug to this commit: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/?h=Ubuntu-6.8.0-20.20=71eb6b6b0ba93b1467bccff57b5de746b09113d2 All versions that I tested before this commit during my bisect passed the aiol test at least 15 times in a row, and all versions after this commit panic during at least one test. To confirm, I reverted this patch on the latest 6.8 Ubuntu kernel (which was previously panicking reliably within 5 tests) and verified that, with that change, it passes the test at least 15x in a row without any panics. The contents of the patch also support this conclusion, as the patch is a change to the Linux AIO interface that introduces new calls to spin_lock_irqsave() and wake_up_process() inside aio_complete(), which corresponds with the content of the traces I have observed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058557 Title: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel Status in linux package in Ubuntu: New Bug description: A kernel oops and panic occurred during 22.04 SoC certification on Gunyolk (Grace/Grace) with 6.8 kernel, arm64+largemem variant Steps to reproduce: Run (as root) the following commands: add-apt-repository -y ppa:checkbox-dev/stable apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable apt update apt install -y canonical-certification-server /usr/lib/checkbox-provider-base/bin/stress_ng_test.py disk --device dm-0 --base-time 240 stress_ng_test caused a kernel panic after about 5 minutes. I have attached dmesg output from my reproducer to this report. Initially, this was identified via a panic during the above test, which was running as part of a run of certify-soc-22.04. Attached is a tarball containing: - apport.linux-image-6.8.0-11-generic-64k.kzsondji.apport: The output of `ubuntu-bug linux` on the machine (after reboot) - reproduced-dmesg.202403201942: The dmesg output captured by kdump when I reproduced my original issue by running only the single stress_ng_test.py command above (not the entire cert suite) - original-dmesg.txt: The dmesg output I captured when the stress_ng_test originally failed during the full cert suite run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
*** This bug is a duplicate of bug 2049927 *** https://bugs.launchpad.net/bugs/2049927 ** This bug has been marked a duplicate of bug 2049927 since Linux kernel 6.5.0-14 external monitors are no longer detected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Expired Status in linux-oem-6.5 package in Ubuntu: New Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056445] Re: external monitors flash white with every interrupt
After setting UMA_Game_Optimized, I can confirm that (after 30 minutes of usage), the system appears far more stable. Since X11 appeared stable I also switched back to Wayland which was previously unusable and this also appears to be working. I'll also report back once I am able to test the new kernel. Thanks again for the help Mario. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056445 Title: external monitors flash white with every interrupt Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: an interesting amdgpu issue: I currently have two external monitors, and only one will display the desktop at a time - the other is completely white. The interesting thing is that with each interrupt that the kernel receives from keyboard / mouse, the screens will flip which one is visible. With my monitors positioned above and to the left of the laptop's built-in display, the flashing monitors feel akin to attending an electronic light show, or perhaps a display of fireworks - the monitors flip visibility with each keypress. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 05:23:23 2024 InstallationDate: Installed on 2024-02-02 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053135] Re: Touchpad not working, device not detected
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-6.5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2053135 Title: Touchpad not working, device not detected Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Laptop model: Dell Precision 3560 Touchpad Manufacturer: can't find it First symptoms: today 14th February Description: Ubuntu 22.04.3 LTS Release: 22.04 Touchpad doesn't work and isn't detected as a device. Not sure if the issue started after boot or after the apt-upgrade I did right after boot. I've followed the DebuggingTouchpadDetection guide until here. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 15:21:51 2024 InstallationDate: Installed on 2023-09-19 (148 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2053135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056706] Re: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0"
https://bugzilla.kernel.org/show_bug.cgi?id=218654 ** Bug watch added: Linux Kernel Bug Tracker #218654 https://bugzilla.kernel.org/show_bug.cgi?id=218654 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056706 Title: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0" Status in linux package in Ubuntu: Confirmed Bug description: After upgrading a homelab 24.04 test machine from 6.6 to 6.8 kernel that was recently introduced, the test machine started flooding the terminal with following messages: [ 1877.712068] BUG: Bad page state in process swapper/0 pfn:58919 The process name varies and appears to be whatever is currently doing something. I installed a fresh up to date copy to see if this could be replicated elsewhere and the outcome is the same. Both of the machines are VMs running under Xen with XCP-ng, although unsure if it's related. The issue produces a notable amount of syslog entries. If left running, the system will eventually go into a state where processes get stuck and do not react to systemd control, even when there's no notable load, no memory pressure nor is the disk space low. Booted back to 6.6 kernel the issue no longer happens. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 11 00:31 seq crw-rw+ 1 root audio 116, 33 Mar 11 00:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Mon Mar 11 00:36:24 2024 InstallationDate: Installed on 2024-03-11 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 (20240222) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 002: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Xen HVM domU PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 LC_CTYPE=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=97002c6c-ab61-49d5-b937-891e4e8da514 ro RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2024 dmi.bios.release: 4.13 dmi.bios.vendor: Xen dmi.bios.version: 4.13 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.13:bd01/31/2024:br4.13:svnXen:pnHVMdomU:pvr4.13:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.13 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047154] Re: [amdgpu][drm] *ERROR* flip_done timed out
** Also affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2047154 Title: [amdgpu][drm] *ERROR* flip_done timed out Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: New Bug description: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:25 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [CRTC:84:crtc-0] commit wait timed out gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [CONNECTOR:119:HDMI-A-1] commit wait timed out gru 21 16:32:40 karol.home.prv dbus-daemon[1317]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=2> gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [PLANE:67:plane-5] commit wait timed out gru 21 16:32:46 karol.home.prv kernel: [ cut here ] gru 21 16:32:46 karol.home.prv kernel: WARNING: CPU: 3 PID: 100858 at /var/lib/dkms/amdgpu/6.2.4-1664922.22.04/build/amd/amdgpu/../di> gru 21 16:32:46 karol.home.prv kernel: Modules linked in: xt_recent tls xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_i> gru 21 16:32:46 karol.home.prv kernel: reed_solomon pstore_zone efi_pstore sunrpc ip_tables x_tables autofs4 ib_uverbs ib_core amdgp> gru 21 16:32:46 karol.home.prv kernel: CPU: 3 PID: 100858 Comm: Xorg Tainted: PW OE 6.2.0-26-generic #26~22.04.1-Ubuntu gru 21 16:32:46 karol.home.prv kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X470 Master SLI, BIOS P4.40 03/29> gru 21 16:32:46 karol.home.prv kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x3b20/0x4200 [amdgpu] gru 21 16:32:46 karol.home.prv kernel: Code: ff 4c 89 9d 78 fc ff ff ba 01 00 00 00 31 f6 4c 89 95 80 fc ff ff 41 b9 01 00 00 00 50 5> gru 21 16:32:46 karol.home.prv kernel: RSP: 0018:b5fb50ee7818 EFLAGS: 00010002 gru 21 16:32:46 karol.home.prv kernel: RAX: 0246 RBX: 00013195 RCX: gru 21 16:32:46 karol.home.prv kernel: RDX: RSI: RDI: gru 21 16:32:46 karol.home.prv kernel: RBP: b5fb50ee7ba0 R08: R09: gru 21 16:32:46 karol.home.prv kernel: R10: 0002 R11: R12: 0246 gru 21 16:32:46 karol.home.prv kernel: R13: R14: 9710a5d8d118 R15: 9710a5d8d000 gru 21 16:32:46 karol.home.prv kernel: FS: 7f3267b4ea80() GS:97179eac() knlGS: gru 21 16:32:46 karol.home.prv kernel: CS: 0010 DS: ES: CR0: 80050033 gru 21 16:32:46 karol.home.prv kernel: CR2: 55ef7d6bfb20 CR3: 000250f4e000 CR4: 003506e0 gru 21 16:32:46 karol.home.prv kernel: Call Trace: gru 21 16:32:46 karol.home.prv kernel: gru 21 16:32:46 karol.home.prv kernel: commit_tail+0xc5/0x1a0 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: ? drm_atomic_helper_swap_state+0x246/0x380 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: drm_atomic_helper_commit+0x137/0x160 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: drm_atomic_commit+0x99/0xd0 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx___drm_printfn_info+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_mode_obj_set_property_ioctl+0x179/0x430 [drm] gru 21 16:32:46 karol.home.prv kernel: ? drm_mode_createblob_ioctl+0xff/0x130 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_ioctl_kernel+0xc3/0x160 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_ioctl+0x27b/0x4c0 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pm_runtime_suspend+0x7b/0x110 gru 21 16:32:46 karol.home.prv kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] gru 21 16:32:46 karol.home.prv kernel: __x64_sys_ioctl+0x9d/0xe0 gru 21 16:32:46 karol.home.prv kernel: do_syscall_64+0x5c/0x90 gru 21 16:32:46 karol.home.prv kernel: ? do_syscall_64+0x69/0x90 gru 21 16:32:46 karol.home.prv kernel: ? exit_to_user_mode_prepare+0x3b/0xd0 gru 21 16:32:46 karol.home.prv kernel: ? syscall_exit_to_user_mode+0x2a/0x50 ? do_syscall_64+0x69/0x90 gru 21 16:32:46 karol.home.prv kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc gru 21 16:32:46 karol.home.prv kernel: RIP: 0033:0x7f3267f1a75f gru 21 16:32:46 karol.home.prv kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00
[Kernel-packages] [Bug 2056706] Re: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0"
Patch https://patchwork.kernel.org/project/xen- devel/patch/171154167446.2671062.9127105384591237363.stgit@firesoul/ is fixing the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056706 Title: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0" Status in linux package in Ubuntu: Confirmed Bug description: After upgrading a homelab 24.04 test machine from 6.6 to 6.8 kernel that was recently introduced, the test machine started flooding the terminal with following messages: [ 1877.712068] BUG: Bad page state in process swapper/0 pfn:58919 The process name varies and appears to be whatever is currently doing something. I installed a fresh up to date copy to see if this could be replicated elsewhere and the outcome is the same. Both of the machines are VMs running under Xen with XCP-ng, although unsure if it's related. The issue produces a notable amount of syslog entries. If left running, the system will eventually go into a state where processes get stuck and do not react to systemd control, even when there's no notable load, no memory pressure nor is the disk space low. Booted back to 6.6 kernel the issue no longer happens. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 11 00:31 seq crw-rw+ 1 root audio 116, 33 Mar 11 00:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Mon Mar 11 00:36:24 2024 InstallationDate: Installed on 2024-03-11 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 (20240222) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 002: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Xen HVM domU PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 LC_CTYPE=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=97002c6c-ab61-49d5-b937-891e4e8da514 ro RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2024 dmi.bios.release: 4.13 dmi.bios.vendor: Xen dmi.bios.version: 4.13 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.13:bd01/31/2024:br4.13:svnXen:pnHVMdomU:pvr4.13:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.13 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059143] Re: Remove getabis scripts
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059143] Re: Remove getabis scripts
** Changed in: linux (Ubuntu Trusty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051410] Re: AMD-GPU, decrease video resolution leads to black screen
*** This bug is a duplicate of bug 2046504 *** https://bugs.launchpad.net/bugs/2046504 ** This bug has been marked a duplicate of bug 2046504 AMD GPU display is blank when set lower resolution than native mode on eDP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051410 Title: AMD-GPU, decrease video resolution leads to black screen Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Only the highest resolution can be set (1920x1080). If the resolution will be set to e.g,: 1280x720, only a black screen will be seen. Also games, or "Wine" application does not work, former resolution settings can not be changed, start the "Wine" application leads also to a black screen (rebooting necessary). Additionalinformation Xorg.0.log, resolution modified : [ 4028.159] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4028.170] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4028.170] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4253.595] (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter [ 4254.499] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4254.499] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4254.508] (II) AMDGPU(0): Allocate new frame buffer 1280x720 [ 4254.509] (II) AMDGPU(0): => pitch 5120 bytes [ 4254.859] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4254.859] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4254.859] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4255.673] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4255.674] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4255.674] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4256.307] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4256.307] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4256.307] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4256.768] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4256.768] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4256.768] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4274.945] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4274.945] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4274.969] (II) AMDGPU(0): Allocate new frame buffer 1920x1080 [ 4274.984] (II) AMDGPU(0): => pitch 7680 bytes [ 4276.213] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4276.213] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4276.213] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4276.327] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4276.327] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4276.327] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4277.060] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4277.060] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4277.060] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4277.180] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4277.180] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4277.180] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4292.371] (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter [ 4293.277] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4293.277] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4293.293] (II) AMDGPU(0): Allocate new frame buffer 1680x1050 [ 4293.294] (II) AMDGPU(0): => pitch 7168 bytes [ 4293.642] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4293.642] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4293.642] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4294.332] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4294.332] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4294.332] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4294.416] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4294.416] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4294.416] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP)
[Kernel-packages] [Bug 2055685] Re: Cranky update-dkms-versions rollout
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055685 Title: Cranky update-dkms-versions rollout Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] Having a common file for dkms-versions between main kernels and derivatives causes a lot of conflicts during rebase. Solution is to have a dkms-versions per kernels, under debian./dkms-version. While at it, instead of running ./update-dkms-version script, cranky update-dkms-versions was introduced. This is not used in xenial, therefore for xenial we only replaced debian/dkms-versions with debian./dkms-versions [Fix] This is needed only in the main kernels. 1. remove update-dkms-version script (where needed), in xenial:linux we don't have it 2. rename debian/dkms-version with debian.master/dkms-versions 3. Replace debian/dkms-versions references in debian scripts and rules with $(DEBIAN)/dkms-versions Note for derivatives: These changes will be inherited from the parent during cranky rebase. The only change to the cranky process is: instead of using ./update-dkms-versions script, cranky-update-dkms-versions should be used [Test] Build test on cbd. No issue found. [Regression pottential] Owners have tried this last cycle in derivatives and no issues were found. We may see build failures due to wrong dkms versions, but it will be fixed along the way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059237] Comment bridged from LTC Bugzilla
--- Comment From kowshik.j...@in.ibm.com 2024-03-28 11:43 EDT--- (In reply to comment #13) Hello Frank, I upgraded the system to 6.8.0-20-generic kernel and the issue is not seen even after multiple reboots. Also. I took the source available here: http://launchpadlibrarian.net/720006283/linux- source-6.8.0_6.8.0-20.20_all.deb I see that, the above mentioned patch is not applied in this source. So, if the issue is getting fixed without the patch, is there a need for this patch? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059237 Title: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: == Comment:- Kowshik Jois B S == ---Problem Description--- Below trace messges are observed in dmesg after every reboot. [0.474287] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [0.475750] Freeing unused kernel image (initmem) memory: 8832K [0.507388] Checked W+X mappings: passed, no W+X pages found [0.507400] Run /init as init process [0.507403] with arguments: [0.507404] /init [0.507405] with environment: [0.507406] HOME=/ [0.507407] TERM=linux [0.507408] BOOT_IMAGE=/vmlinux-6.8.0-11-generic [0.511892] [ cut here ] [0.511904] UBSAN: array-index-out-of-bounds in /build/linux-MzA0lF/linux-6.8.0/arch/powerpc/kernel/module_64.c:353:17 [0.511909] index 0 is out of range for type 'char [*]' [0.511912] CPU: 13 PID: 1 Comm: systemd Not tainted 6.8.0-11-generic #11-Ubuntu [0.511917] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1060.00 (NH1060_013) hv:phyp pSeries [0.511921] Call Trace: [0.511922] [c6683620] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.511931] [c6683650] [c0c7bc58] __ubsan_handle_out_of_bounds+0xc4/0x12c [0.511938] [c6683700] [c005d2a8] module_frob_arch_sections+0x4ec/0x8d0 [0.511943] [c66837e0] [c02b98cc] layout_and_allocate.isra.0+0x38/0x2a8 [0.511948] [c6683850] [c02b9dec] load_module+0x138/0xca0 [0.511953] [c6683990] [c02baca8] init_module_from_file+0xb4/0x14c [0.511958] [c6683a70] [c02baf70] sys_finit_module+0x230/0x48c [0.511963] [c6683b80] [c0033248] system_call_exception+0xe8/0x240 [0.511967] [c6683e50] [c000d15c] system_call_vectored_common+0x15c/0x2ec [0.511972] --- interrupt: 3000 at 0x7879b903b8a8 [0.511977] NIP: 7879b903b8a8 LR: CTR: [0.511980] REGS: c6683e80 TRAP: 3000 Not tainted (6.8.0-11-generic) [0.511984] MSR: 8000f033 CR: 48222428 XER: [0.511993] IRQMASK: 0 GPR00: 0161 7fffd683b580 7879b9166d00 0004 GPR04: 7879b8e0c160 0004 0010 0004 GPR08: 0001 GPR12: 7879b99d3a00 2000 0002 GPR16: 1b5c7d7453e0 7fffd683ba68 GPR20: 1b5c82154ae0 1b5c82142360 GPR24: 7879b957f7b0 1b5c82154ae0 1b5c82142160 GPR28: 7879b8e0c160 0002 1b5c82154ae0 1b5c82142380 [0.512029] NIP [7879b903b8a8] 0x7879b903b8a8 [0.512032] LR [] 0x0 [0.512034] --- interrupt: 3000 [0.512036] ---[ end trace ]--- [0.518326] systemd[1]: Inserted module 'autofs4' [0.521570] systemd[1]: systemd 255.2-3ubuntu2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) [0.521583] systemd[1]: Detected virtualization powervm. [0.521589] systemd[1]: Detected architecture ppc64-le. [0.521593] systemd[1]: Running in initrd. [0.521743] systemd[1]: No hostname configured, using default hostname. [0.521789] systemd[1]: Hostname set to . [0.521847] systemd[1]: Initializing machine ID from random generator. [0.600736] systemd[1]: Queued start job for default target initrd.target. Machine Type = P10 LPAR Contact Information = Kowshik Jois B S
[Kernel-packages] [Bug 2056445] Re: external monitors flash white with every interrupt
> If you can add your details for your "specific" FW13 AMD to the upstream bug > maybe others who are affected can help with building the pattern. > I mean the memory vendor, speed of memory, amount, channel configuration. this system has a single DIMM which was provided by framework: DDR5-5600 - 32GB (1 x 32GB) memory vendor: A-DATA Technology speed of memory: 5600 MT/s amount: 32 GB channel configuration: single uefi version: 03.03 see below[2] for more details > What you do to trigger it, etc. Various symptoms appear triggered by different things. The suspend/resume issue (which sounds like it is fixed) causes either the completely white screen or the white screen that flickers. Most graphics-related issues that I see on this machine either happen immediately on first boot, or after a suspend/resume cycle, or don't appear to have a trigger. On my most recent boot, my screen flickers in the upper left and lower right corners as a wide rectangular bar, this started immediately after passing the GDM login screen. Another symptom[1] that I experience on this machine (that is probably unrelated) is that heavy firefox usage causes firefox latency to become unusably high - and CPU usage remains low. Restarting firefox temporarily resolves the issue. This behavior started to happen after I switched to X11. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1883077 [2] memory details # dmidecode 3.5 Getting SMBIOS data from sysfs. SMBIOS 3.5.0 present. Handle 0x0012, DMI type 17, 92 bytes Memory Device Array Handle: 0x0011 Error Information Handle: 0x0015 Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: Unknown Set: None Locator: DIMM 0 Bank Locator: P0 CHANNEL A Type: Unknown Type Detail: Unknown Handle 0x0013, DMI type 17, 92 bytes Memory Device Array Handle: 0x0011 Error Information Handle: 0x0016 Total Width: 64 bits Data Width: 64 bits Size: 32 GB Form Factor: SODIMM Set: None Locator: DIMM 0 Bank Locator: P0 CHANNEL B Type: DDR5 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 5600 MT/s Manufacturer: A-DATA Technology Serial Number: 00301896 Asset Tag: Not Specified Part Number: AD5S560032G-SFW Rank: 2 Configured Memory Speed: 5600 MT/s Minimum Voltage: 1.1 V Maximum Voltage: 1.1 V Configured Voltage: 1.1 V Memory Technology: DRAM Memory Operating Mode Capability: Volatile memory Firmware Version: Unknown Module Manufacturer ID: Bank 5, Hex 0xCB Module Product ID: Unknown Memory Subsystem Controller Manufacturer ID: Unknown Memory Subsystem Controller Product ID: Unknown Non-Volatile Size: None Volatile Size: 32 GB Cache Size: None Logical Size: None ** Bug watch added: Mozilla Bugzilla #1883077 https://bugzilla.mozilla.org/show_bug.cgi?id=1883077 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056445 Title: external monitors flash white with every interrupt Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: an interesting amdgpu issue: I currently have two external monitors, and only one will display the desktop at a time - the other is completely white. The interesting thing is that with each interrupt that the kernel receives from keyboard / mouse, the screens will flip which one is visible. With my monitors positioned above and to the left of the laptop's built-in display, the flashing monitors feel akin to attending an electronic light show, or perhaps a display of fireworks - the monitors flip visibility with each keypress. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 05:23:23 2024 InstallationDate: Installed on 2024-02-02 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware
[Kernel-packages] [Bug 2059712] [NEW] `perf report` complains about missing tips.txt file
Public bug reported: The `perf` command-line tool expects a tips.txt file at /usr/share/doc/perf-tip/tips.txt, from which it displays random tips in `perf report` mode. If this file is not present (it is not on Ubuntu 22.04 LTS), `perf report` complains, both in interactive and in non- interactive mode, that: > Cannot load tips.txt file, please install perf! Reproduction: $ mkdir tmpdir; cd tmpdir $ perf record ls $ perf report | cat The expected behaviour is that this message is not shown (and a (useful?) tip is shown instead). This has led to bug reports (and fixes) on various other Linux distributions: at least Fedora [1] and Arch [2]. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1448402 [2]: https://bugs.archlinux.org/task/48788 Further info: $ lsb_release -rd Description:Ubuntu 22.04.4 LTS Release:22.04 $ apt-cache policy linux-tools-common | head -5 linux-tools-common: Installed: 5.15.0-101.111 Candidate: 5.15.0-101.111 Version table: *** 5.15.0-101.111 500 $ cat /proc/version_signature Ubuntu 5.15.0-101.111-generic 5.15.143 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059712 Title: `perf report` complains about missing tips.txt file Status in linux package in Ubuntu: New Bug description: The `perf` command-line tool expects a tips.txt file at /usr/share/doc/perf-tip/tips.txt, from which it displays random tips in `perf report` mode. If this file is not present (it is not on Ubuntu 22.04 LTS), `perf report` complains, both in interactive and in non-interactive mode, that: > Cannot load tips.txt file, please install perf! Reproduction: $ mkdir tmpdir; cd tmpdir $ perf record ls $ perf report | cat The expected behaviour is that this message is not shown (and a (useful?) tip is shown instead). This has led to bug reports (and fixes) on various other Linux distributions: at least Fedora [1] and Arch [2]. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1448402 [2]: https://bugs.archlinux.org/task/48788 Further info: $ lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 $ apt-cache policy linux-tools-common | head -5 linux-tools-common: Installed: 5.15.0-101.111 Candidate: 5.15.0-101.111 Version table: *** 5.15.0-101.111 500 $ cat /proc/version_signature Ubuntu 5.15.0-101.111-generic 5.15.143 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057936] Re: Azure: hv: hyperv.h: Replace one-element array with flexible-array member
** Tags removed: verification-needed-mantic-linux-azure ** Tags added: verification-done-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2057936 Title: Azure: hv: hyperv.h: Replace one-element array with flexible-array member Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Invalid Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested the inclusion of commit bb9b0e46b84c19d3dd7d453a2da71a0fdc172b31 ('hv: hyperv.h: Replace one- element array with flexible-array member') [Test Plan] Microsoft tested [Regression Potential] This patch could cause seg faults if the logic does not correctly accommodate a flexible array member. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2057936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047154] Re: [amdgpu][drm] *ERROR* flip_done timed out
This has become an intermittent issue in the past few months. I am currently on the latest 6.5 kernel and running Wayland. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2047154 Title: [amdgpu][drm] *ERROR* flip_done timed out Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:25 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [CRTC:84:crtc-0] commit wait timed out gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [CONNECTOR:119:HDMI-A-1] commit wait timed out gru 21 16:32:40 karol.home.prv dbus-daemon[1317]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=2> gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [PLANE:67:plane-5] commit wait timed out gru 21 16:32:46 karol.home.prv kernel: [ cut here ] gru 21 16:32:46 karol.home.prv kernel: WARNING: CPU: 3 PID: 100858 at /var/lib/dkms/amdgpu/6.2.4-1664922.22.04/build/amd/amdgpu/../di> gru 21 16:32:46 karol.home.prv kernel: Modules linked in: xt_recent tls xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_i> gru 21 16:32:46 karol.home.prv kernel: reed_solomon pstore_zone efi_pstore sunrpc ip_tables x_tables autofs4 ib_uverbs ib_core amdgp> gru 21 16:32:46 karol.home.prv kernel: CPU: 3 PID: 100858 Comm: Xorg Tainted: PW OE 6.2.0-26-generic #26~22.04.1-Ubuntu gru 21 16:32:46 karol.home.prv kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X470 Master SLI, BIOS P4.40 03/29> gru 21 16:32:46 karol.home.prv kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x3b20/0x4200 [amdgpu] gru 21 16:32:46 karol.home.prv kernel: Code: ff 4c 89 9d 78 fc ff ff ba 01 00 00 00 31 f6 4c 89 95 80 fc ff ff 41 b9 01 00 00 00 50 5> gru 21 16:32:46 karol.home.prv kernel: RSP: 0018:b5fb50ee7818 EFLAGS: 00010002 gru 21 16:32:46 karol.home.prv kernel: RAX: 0246 RBX: 00013195 RCX: gru 21 16:32:46 karol.home.prv kernel: RDX: RSI: RDI: gru 21 16:32:46 karol.home.prv kernel: RBP: b5fb50ee7ba0 R08: R09: gru 21 16:32:46 karol.home.prv kernel: R10: 0002 R11: R12: 0246 gru 21 16:32:46 karol.home.prv kernel: R13: R14: 9710a5d8d118 R15: 9710a5d8d000 gru 21 16:32:46 karol.home.prv kernel: FS: 7f3267b4ea80() GS:97179eac() knlGS: gru 21 16:32:46 karol.home.prv kernel: CS: 0010 DS: ES: CR0: 80050033 gru 21 16:32:46 karol.home.prv kernel: CR2: 55ef7d6bfb20 CR3: 000250f4e000 CR4: 003506e0 gru 21 16:32:46 karol.home.prv kernel: Call Trace: gru 21 16:32:46 karol.home.prv kernel: gru 21 16:32:46 karol.home.prv kernel: commit_tail+0xc5/0x1a0 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: ? drm_atomic_helper_swap_state+0x246/0x380 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: drm_atomic_helper_commit+0x137/0x160 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: drm_atomic_commit+0x99/0xd0 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx___drm_printfn_info+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_mode_obj_set_property_ioctl+0x179/0x430 [drm] gru 21 16:32:46 karol.home.prv kernel: ? drm_mode_createblob_ioctl+0xff/0x130 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_ioctl_kernel+0xc3/0x160 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_ioctl+0x27b/0x4c0 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pm_runtime_suspend+0x7b/0x110 gru 21 16:32:46 karol.home.prv kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] gru 21 16:32:46 karol.home.prv kernel: __x64_sys_ioctl+0x9d/0xe0 gru 21 16:32:46 karol.home.prv kernel: do_syscall_64+0x5c/0x90 gru 21 16:32:46 karol.home.prv kernel: ? do_syscall_64+0x69/0x90 gru 21 16:32:46 karol.home.prv kernel: ? exit_to_user_mode_prepare+0x3b/0xd0 gru 21 16:32:46 karol.home.prv kernel: ? syscall_exit_to_user_mode+0x2a/0x50 ? do_syscall_64+0x69/0x90 gru 21 16:32:46 karol.home.prv kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc gru 21 16:32:46 karol.home.prv kernel: RIP: 0033:0x7f3267f1a75f gru 21 16:32:46 karol.home.prv kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89
[Kernel-packages] [Bug 2059418] [NEW] Bluetooth earbuds not being 'set up' on new machine
Public bug reported: The problem concerns earbuds 0B:20:24:A3:E7:56 T60 that worked perfectly under completely patched Ubuntu 22.04 on my old machine but now refuse to be setup on a new box running completely patched Ubuntu 22.04 . Other old bluetooth gadgets attached without issue. The end result at the very bottom of this page indicates ‘requestor exited before bonding was completed’ . root@bill:~# bluetoothctl --version bluetoothctl: 5.64 root@bill:~# hciconfig -a hci0: Type: Primary Bus: USB BD Address: BC:C7:46:9D:25:98 ACL MTU: 1021:8 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:11627 acl:0 sco:0 events:466 errors:0 TX bytes:78563 acl:0 sco:0 commands:422 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'bill' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: (0xc) Revision: 0x40d LMP Version: (0xc) Subversion: 0x7225 Manufacturer: Realtek Semiconductor Corporation (93) root@bill:~# bluetoothctl Agent registered [CHG] Controller BC:C7:46:9D:25:98 Pairable: yes [bluetooth]# show Controller BC:C7:46:9D:25:98 (public) Name: bill Alias: bill Class: 0x007c0104 Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control (110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Audio Sink (110b--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer (1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0540 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x0a (10) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded [bluetooth]# devices Device 74:45:CE:BA:24:65 WH-CH710N At this point I started the earbuds (T60) having a problem getting set up. [CHG] Controller BC:C7:46:9D:25:98 Discoverable: yes [CHG] Controller BC:C7:46:9D:25:98 Discovering: yes [NEW] Device 34:95:04:4B:07:3C 34-95-04-4B-07-3C [CHG] Device 34:95:04:4B:07:3C RSSI: -86 [NEW] Device 0B:20:24:A3:E7:56 T60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -52 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: no [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -64 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: no [CHG] Device 0B:20:24:A3:E7:56 RSSI: -50 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -50 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -80 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -46 [bluetooth]# info 0B:20:24:A3:E7:56 Device 0B:20:24:A3:E7:56 (public) Name: T60 Alias: T60 Class: 0x00240404 Icon: audio-headset Paired: no Trusted: no Blocked: no Connected: no LegacyPairing: no ManufacturerData Key: 0x7262
[Kernel-packages] [Bug 2059316] Re: backport arm64 THP improvements from 6.9
I've build-tested on all architectures in this PPA: https://launchpad.net/~dannf/+archive/ubuntu/mthp/+packages I manually tested on a few systems, timing a full kernel build w/ the Ubuntu config in a tmpfs (both to stress the system, and look for performance differences). - ppc64el / Power9 - no performance difference - x86 - AMD EPYC/Naples - 11% improvement - Ampere AltraMax (-generic) - 19% improvement ** Description changed: Initial support for multi-size THP landed upstream in v6.8. In the 6.9 merge window, 2 other series have landed that show significant performance improvements on arm64 mm/memory: optimize fork() with PTE-mapped THP - https://lkml.iu.edu/hypermail/linux/kernel/2401.3/02766.html + https://lkml.iu.edu/hypermail/linux/kernel/2401.3/02766.html Transparent Contiguous PTEs for User Mappings: - https://lwn.net/Articles/962330/ + https://lwn.net/Articles/962330/ On an Ampere AltraMax system w/ 4K page size, kernel builds in a tmpfs are reduced from 6m30s to 5m17s, a ~19% improvement. + + It has been reported that this can have a *10x* improvement for certain + GPU workloads on ARM: + + https://lwn.net/Articles/954094/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059316 Title: backport arm64 THP improvements from 6.9 Status in linux package in Ubuntu: In Progress Bug description: Initial support for multi-size THP landed upstream in v6.8. In the 6.9 merge window, 2 other series have landed that show significant performance improvements on arm64 mm/memory: optimize fork() with PTE-mapped THP https://lkml.iu.edu/hypermail/linux/kernel/2401.3/02766.html Transparent Contiguous PTEs for User Mappings: https://lwn.net/Articles/962330/ On an Ampere AltraMax system w/ 4K page size, kernel builds in a tmpfs are reduced from 6m30s to 5m17s, a ~19% improvement. It has been reported that this can have a *10x* improvement for certain GPU workloads on ARM: https://lwn.net/Articles/954094/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055083] Re: Drop fips-checks script from trees
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055083 Title: Drop fips-checks script from trees Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058573] Re: alsa/realtek: adjust max output valume for headphone on 2 LG machines
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Mantic) Importance: High => Medium ** Changed in: linux (Ubuntu Jammy) Importance: High => Medium ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058573 Title: alsa/realtek: adjust max output valume for headphone on 2 LG machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: [Impact] In an oem project, we found the max playback volume of the headphone is too high on 2 LG machines, it could bring harm to listeners. As requested by OEM customer, we need to decrease the max volume. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booting with the patched kernel, plug the headphone, set the playback volue to max, run: amixer -c1 contents | grep -n2 "Headphone Playback Volume" The value is 77,77 instead of 87,87 like below: numid=1,iface=MIXER,name='Headphone Playback Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=87,step=0 : values=77,77 [Where problems could occur] This patch changes the amplifier's default value, probably will make the audio malfunction, but this change is specific to those 2 LG machines (by SSID), will not bring regression to other machines. For those 2 machines, we already tested patch, the audio worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032164] Re: A general-proteciton exception during guest migration to unsupported PKRU machine
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032164 Title: A general-proteciton exception during guest migration to unsupported PKRU machine Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: [Impact] When a host that supports PKRU initiates a guest that lacks PKRU support, the flag is enabled on the guest's fpstate. This information is then passed to userspace through the vcpu ioctl KVM_GET_XSAVE. However, a problem arises when the user opts to migrate the mentioned guest to another machine that does not support PKRU. In this scenario, the new host attempts to restore the guest's fpu registers. Nevertheless, due to the absence of PKRU support on the new host, a general-protection exception takes place, leading to a guest crash. [Fix] The problem is resolved by the following upstream commit: 18164f66e6c5 x86/fpu: Allow caller to constrain xfeatures when copying to uabi buffer 8647c52e9504 KVM: x86: Constrain guest-supported xfeatures only at KVM_GET_XSAVE{2} [Test Plan] Several scenarios need to be conducted to confirm the migration outcome. Patched kernel with PKRU -> kernel with PKRU Patched kernel with PKRU -> kernel without PKRU Patched kernel without PKRU -> kernel with PKRU Patched kernel without PKRU -> kernel without PKRU Kernel with PKRU -> patched kernel with PKRU Kernel with PKRU -> patched kernel without PKRU Kernel without PKRU -> patched kernel with PKRU Kernel without PKRU -> patched kernel without PKRU Patched kernel with PKRU -> patched kernel without PKRU Each scenarios shall succeed except "Kernel with PKRU -> patched kernel without PKRU" one. Addressing this case poses challenges because the most plausible solution is to clamp the FPU features at the destination during migration. However, upstream does not support this approach due to concerns about silently dropping features requested by userspace. This could potentially lead to other issues and violate KVM's ABI. [Where problems could occur] The introduced commits will impact the guest migration process, potentially leading to failures and preventing the guest from operating successfully on the migration destination. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058485] Re: [ICX] [SPR] [ipc/msg] performance: Mitigate the lock contention with percpu counter
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058485 Title: [ICX] [SPR] [ipc/msg] performance: Mitigate the lock contention with percpu counter Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034980 Backport: ipc/msg: mitigate the lock contention with percpu counter (merged upstream in 6.1) to jammy [Impact] The msg_bytes and msg_hdrs atomic counters are frequently updated when IPC msg queue is in heavy use, causing heavy cache bounce and overhead. Change them to percpu_counter greatly improve the performance. Since there is one percpu struct per namespace, additional memory cost is minimal. Reading of the count done in msgctl call, which is infrequent. So the need to sum up the counts in each CPU is infrequent. [Fix] Backport: 72d1e611082e ipc/msg: mitigate the lock contention with percpu counter For clean backport/build, those are also required: 5d0ce3595ab75 percpu: add percpu_counter_add_local and percpu_counter_sub_local 38cd5b12b7854 ipc: Remove extra braces 0889f44e28103 ipc: Check permissions for checkpoint_restart sysctls at open time dd141a4955d5e ipc: Remove extra1 field abuse to pass ipc namespace def7343ff03bb ipc: Use the same namespace to modify and validate 1f5c135ee509e ipc: Store ipc sysctls in the ipc namespace dc55e35f9e810 ipc: Store mqueue sysctls in the ipc namespace 0e9beb8a96f21 ipc/ipc_sysctl.c: remove fallback for !CONFIG_PROC_SYSCTL 5563cabdde7ee ipc: check checkpoint_restore_ns_capable() to modify C/R proc files [Test Plan] Test as the original patch, with pts/stress-ng message passing and compare performance. [Where problems could occur] Performance regression in IPC communication/workload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038583] Re: Turning COMPAT_32BIT_TIME off on s390x
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038583 Title: Turning COMPAT_32BIT_TIME off on s390x Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This will prevent existing s390 binaries to operate correctly, if they are still using 32bit time. 24.04 LTS is likely to be used for 10 years. And if allowed to overrun and remain active in the field in 2038 can lead to catastrophic failure in the field due to these syscalls enabled and used. I would like to request if we can turn off COMPAT_32BIT_TIME on every architecture, thus this will be arch by arch bug report, and arch by arch decision. This needs to be a per-arch decision, potentially taking into consideration bi-arch userspace support. config COMPAT_32BIT_TIME bool "Provide system calls for 32-bit time_t" default !64BIT || COMPAT help This enables 32 bit time_t support in addition to 64 bit time_t support. This is relevant on all 32-bit architectures, and 64-bit architectures as part of compat syscall handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2038583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051683] Re: [24.04 FEAT] [LDP2406] 64bit Only Distro - Remove 31/32bit Support Completely
*** This bug is a duplicate of bug 2038583 *** https://bugs.launchpad.net/bugs/2038583 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051683 Title: [24.04 FEAT] [LDP2406] 64bit Only Distro - Remove 31/32bit Support Completely Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Make the final step to a 64bit only distro by removing kernel compat support for 31/32 bit. This will mean that statically linked 31/32bit binaries and container images cannot be run anymore. Such a step needs to be done for a major release, and will also be made for the upstream kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2051683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038583] Re: Turning COMPAT_32BIT_TIME off on s390x
This bug was fixed in the package linux - 6.8.0-20.20 --- linux (6.8.0-20.20) noble; urgency=medium * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y -- Paolo Pisati Mon, 18 Mar 2024 11:08:14 +0100 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038583 Title: Turning COMPAT_32BIT_TIME off on s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: This will prevent existing s390 binaries to operate correctly, if they are still using 32bit time. 24.04 LTS is likely to be used for 10 years. And if allowed to overrun and remain active in the field in 2038 can lead to catastrophic failure in the field due to these syscalls enabled and used. I would like to request if we can turn off COMPAT_32BIT_TIME on every architecture, thus this will be arch by arch bug report, and arch by arch decision. This needs to be a per-arch decision, potentially taking into consideration bi-arch userspace support. config COMPAT_32BIT_TIME bool "Provide system calls for 32-bit time_t" default !64BIT || COMPAT help This enables 32 bit time_t support in addition to 64 bit time_t support. This is relevant on all 32-bit architectures, and 64-bit architectures as part of compat syscall handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2038583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951440] Re: Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON
This bug was fixed in the package linux - 6.8.0-20.20 --- linux (6.8.0-20.20) noble; urgency=medium * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y -- Paolo Pisati Mon, 18 Mar 2024 11:08:14 +0100 ** Changed in: linux (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951440 Title: Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Invalid Status in linux source package in Noble: Fix Released Bug description: Starting with the following commit, upstream kernel is enabling Intel IOMMU related options by default: 792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by default") We should follow upstream direction enabling CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON. A downside is that this change may introduce boot regressions on old systems (especially those with buggy firmware). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
This bug was fixed in the package linux - 6.8.0-20.20 --- linux (6.8.0-20.20) noble; urgency=medium * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y -- Paolo Pisati Mon, 18 Mar 2024 11:08:14 +0100 ** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045561 Title: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux- virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from being configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a built-in, and on SUSE it is a module installed by default. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this module installed and loaded, the directory won't be there. Once enabled, it will be there. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if dmi-sysfs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name dmi-sysfs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048183] Re: Don't produce linux-*-cloud-tools-common, linux-*-tools-common and linux-*-tools-host binary packages
This bug was fixed in the package linux - 6.8.0-20.20 --- linux (6.8.0-20.20) noble; urgency=medium * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y -- Paolo Pisati Mon, 18 Mar 2024 11:08:14 +0100 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048183 Title: Don't produce linux-*-cloud-tools-common, linux-*-tools-common and linux-*-tools-host binary packages Status in linux package in Ubuntu: Fix Released Bug description: [Impact] Some kernels produce linux-*-cloud-tools-common, linux-*-tools-common and/or linux-*-tools-host binary deb packages. That is all wrong, only the primary/main linux source package should produce these. These packages result in install failures of the regular linux-cloud-tools- common, linux-tools-common and linux-tools-host packages. [Test Case] Check list of built binary packages in LP and verify the packages are not built. [Where Problems Could Occur] Already installed packages won't upgrade and become stale. [Notes] This bug is filed against the main linux package because that's where the build rules live. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049390] Re: Please change CONFIG_CONSOLE_LOGLEVEL_QUIET to 3
This bug was fixed in the package linux - 6.8.0-20.20 --- linux (6.8.0-20.20) noble; urgency=medium * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y -- Paolo Pisati Mon, 18 Mar 2024 11:08:14 +0100 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049390 Title: Please change CONFIG_CONSOLE_LOGLEVEL_QUIET to 3 Status in linux package in Ubuntu: Fix Released Bug description: The Ubuntu Desktop boot isn't flickerfree today as reported on bug #1970069 , one of the reason is that kernel error messages are often being logged and not filtered out by our default loglevel (one example with usb messages on https://launchpadlibrarian.net/598152686/20220422_014058.jpg) Fedora is using CONFIG_CONSOLE_LOGLEVEL_QUIET=3 (instead of 4 which is the default), they change it 5 years ago (https://src.fedoraproject.org/rpms/kernel/c/838818e5), the rational is in the commit message that added the configuration option to the kernel > This for example will allow distros which want quiet to really mean quiet to set > CONSOLE_LOGLEVEL_QUIET so that only messages with a higher severity then KERN_ERR (CRIT, ALERT, EMERG) > get printed, avoiding an endless game of whack-a-mole silencing harmless error messages. ' Could we also get the default change to 3 in Ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051342] Re: Enable lowlatency settings in the generic kernel
This bug was fixed in the package linux - 6.8.0-20.20 --- linux (6.8.0-20.20) noble; urgency=medium * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y -- Paolo Pisati Mon, 18 Mar 2024 11:08:14 +0100 ** Changed in: linux (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051342 Title: Enable lowlatency settings in the generic kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] Ubuntu provides the "lowlatency" kernel: a kernel optimized for applications that have special "low latency" requirements. Currently, this kernel does not include any specific UBUNTU SAUCE patches to improve the extra "low latency" requirements, but the only difference is a small subset of .config options. Almost all these options are now configurable either at boot-time or even at run-time, with the only exception of CONFIG_HZ (250 in the generic kernel vs 1000 in the lowlatency kernel). Maintaining a separate kernel for a single config option seems a bit overkill and it is a significant cost of engineering hours, build time, regression testing time and resources. Not to mention the risk of the low-latency kernel falling behind and not being perfectly in sync with the latest generic kernel. Enabling the low-latency settings in the generic kernel has been evaluated before, but it has been never finalized due to the potential risk of performance regressions in CPU-intensive applications (increasing HZ from 250 to 1000 may introduce more kernel jitter in number crunching workloads). The outcome of the original proposal resulted in a re-classification of the lowlatency kernel as a desktop- oriented kernel, enabling additional low latency features (LP: #2023007). As we are approaching the release of the new Ubuntu 24.04 we may want to re-consider merging the low-latency settings in the generic kernel again. Following a detailed analysis of the specific low-latency features: - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown clock tick when possible across all the enabled CPUs if they are either idle or running 1 task - reduce kernel jitter of running tasks due to the periodic clock tick, must be enabled at boot time passing `nohz_full=`); this can actually help CPU-intensive workloads and it could provide much more benefits than the CONFIG_HZ difference (since it can potentially shutdown any kernel jitter on specific CPUs), this one should really be enabled anyway, considering that it is configurable at boot time - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to kthread context (reduce time spent in softirqs with preemption disabled to improve the overall system responsiveness, at the cost of introducing a potential performance penalty, because RCU callbacks are not processed by kernel threads); this should be enabled as well, since it is configurable at boot time (via the rcu_nocbs= parameter) - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a timed delay instead of executing them immediately (c'an provide 5~10% power-savings for idle or lightly-loaded systems, this is extremely useful for laptops / portable devices - https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/); this has the potential to introduce significant performance regressions, but in the Noble kernel we already have a SAUCE patch that allows to enable/disable this option at boot time (see LP: #2045492), and by default it will be disabled (CONFIG_RCU_LAZY_DEFAULT_OFF=y) - CONFIG_HZ=1000 last but not least, the only option that is *only* tunable at compile time. As already mentioned there is a potential risk of regressions for CPU-intensive applications, but they can be mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On the other hand, HZ=1000 can improve system responsiveness, that means most of the desktop and server applications will benefit from this (the largest part of the server workloads is I/O bound, more than CPU- bound, so they can benefit from having a kernel that can react
[Kernel-packages] [Bug 2052005] Re: Validate connection interval to pass Bluetooth Test Suite
This bug was fixed in the package linux - 6.8.0-20.20 --- linux (6.8.0-20.20) noble; urgency=medium * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y -- Paolo Pisati Mon, 18 Mar 2024 11:08:14 +0100 ** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052005 Title: Validate connection interval to pass Bluetooth Test Suite Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: [Impact] Ubuntu doesn't pass Bluetooth Test Suite to get Bluetooth certified. [Fix] Validate max connection interval to pass test case "GAP/CONN/CPUP/BV-05-C 'Connection Parameter Update Procedure Invalid Parameters Central Responder'" [Test] Run the test suite. With the patch applied the case is passed. [Where problems could occur] If any device requires setting a wrong interval to function properly, this might affect those devices in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64
This bug was fixed in the package linux - 6.8.0-20.20 --- linux (6.8.0-20.20) noble; urgency=medium * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y -- Paolo Pisati Mon, 18 Mar 2024 11:08:14 +0100 ** Changed in: linux (Ubuntu Noble) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: Confirmed Status in gcc-11 package in Ubuntu: Confirmed Status in gcc-12 package in Ubuntu: Confirmed Status in gcc-13 package in Ubuntu: Fix Released Status in gcc-8 package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in llvm-toolchain-16 package in Ubuntu: Confirmed Status in gcc-10 source package in Noble: Confirmed Status in gcc-11 source package in Noble: Confirmed Status in gcc-12 source package in Noble: Confirmed Status in gcc-13 source package in Noble: Fix Released Status in gcc-8 source package in Noble: Invalid Status in gcc-9 source package in Noble: Confirmed Status in linux source package in Noble: Fix Released Status in llvm-toolchain-14 source package in Noble: Confirmed Status in llvm-toolchain-15 source package in Noble: Confirmed Status in llvm-toolchain-16 source package in Noble: Confirmed Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5e9c3445acb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8634==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5f19be5f6d12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5f19be632cb8 in main
[Kernel-packages] [Bug 2052439] Re: Don't produce linux-*-source- package
This bug was fixed in the package linux - 6.8.0-20.20 --- linux (6.8.0-20.20) noble; urgency=medium * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y -- Paolo Pisati Mon, 18 Mar 2024 11:08:14 +0100 ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052439 Title: Don't produce linux-*-source- package Status in linux package in Ubuntu: Fix Released Bug description: [Impact] Some kernels produce a linux-*-source- binary deb package. That is all wrong and confusing, only the primary/main linux source package should produce that package. [Test Case] Check list of built binary packages in LP and verify the package is not built. [Where Problems Could Occur] Already installed packages won't upgrade and become stale. [Notes] This bug is filed against the main linux package because that's where the build rules live. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules
This bug was fixed in the package linux - 6.8.0-20.20 --- linux (6.8.0-20.20) noble; urgency=medium * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y -- Paolo Pisati Mon, 18 Mar 2024 11:08:14 +0100 ** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054809 Title: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Justification [Impact] The erofs.ko module (CONFIG_EROFS) is currently shipped in linux- modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from using the erofs filesystem. Erofs is a modern alternative to squashfs that supports more features such as ACLs. The following LPC presentation has more details on erofs and its advantages over squashfs: https://youtu.be/jt-hp_LtSBc. A user launching a VM using the linux-virtual kernel image is not able to mount erofs filesystems due to the lack of this kconfig. We make extensive use of erofs in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a (core) module that is built by default. To verify this works, it is sufficient to create an erofs filesystem with mkfs.erofs and verify that it can be mounted: $ mkdir sources $ echo abcde > sources/file $ mkfs.erofs erofs sources $ mount erofs mnt --mkdir $ ls mnt file Without this module installed and loaded, the mount will fail. Once enabled, it will succeed. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if erofs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name erofs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056126] Re: hwmon: (coretemp) Fix core count limitation
This bug was fixed in the package linux - 6.8.0-20.20 --- linux (6.8.0-20.20) noble; urgency=medium * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y -- Paolo Pisati Mon, 18 Mar 2024 11:08:14 +0100 ** Changed in: linux (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056126 Title: hwmon: (coretemp) Fix core count limitation Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] In linux 6.8 the coretemp driver supports at most 128 cores per package. Cores higher than 128 will lose their core temperature information. There is an upstream patch set that allows to support more than 128 cores per package, but it's applied to linux-next for now and it's scheduled for 6.9. We should apply the patch set to the Noble 6.8 kernel, so that we can properly support systems with a large amount of cores per package. [Test case] Read temperature info from /sys/class/hwmon on a system with > 128 cores per package (that means we don't have a proper test case to verify the fix at the moment). [Fix] Apply the following commits (from linux-next): 18cb15e9c108 hwmon: (coretemp) Use dynamic allocated memory for core temp_data f0a5f46b0100 hwmon: (coretemp) Remove redundant temp_data->is_pkg_data 16a29729c00c hwmon: (coretemp) Split package temp_data and core temp_data b48fddda2b30 hwmon: (coretemp) Abstract core_temp helpers a30f3dc6e9bf hwmon: (coretemp) Remove redundant pdata->cpu_map[] e416450cb080 hwmon: (coretemp) Replace sensor_device_attribute with device_attribute 46ee134971bb hwmon: (coretemp) Remove unnecessary dependency of array index 9f360b22929c hwmon: (coretemp) Introduce enum for attr index [Regression potential] We may experience hwmon-related regressions, either systems reading incorrect temperature information or even bugs/crashes when accessing data from /sys/class/hwmon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056126/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056354] Re: qat: Improve error recovery flows
This bug was fixed in the package linux - 6.8.0-20.20 --- linux (6.8.0-20.20) noble; urgency=medium * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y -- Paolo Pisati Mon, 18 Mar 2024 11:08:14 +0100 ** Changed in: linux (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056354 Title: qat: Improve error recovery flows Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] This set improves the error recovery flows in the QAT drivers and adds a mechanism to test it through an heartbeat simulator. This is an upstream patch set applied to linux-next and scheduled for 6.9. Link to the upstream submission: https://patchwork.kernel.org/project/linux-crypto/cover/20240202105324.50391-1-mun.chun@intel.com/ We should apply this set to the Noble 6.8 kernel, in order to experience less issues with qat and improve maintainability. An added commit is required to update the configuration. [Test case] Unload and reload the module to verify that qat recover and log issues properly. Use the added error injection mechanism to verify the recovery flow. [Fix] Apply the following commits (from linux-next): 2ecd43413d76 Documentation: qat: fix auto_reset section 7d42e097607c crypto: qat - resolve race condition during AER recovery c2304e1a0b80 crypto: qat - change SLAs cleanup flow at shutdown 9567d3dc7609 crypto: qat - improve aer error reset handling 750fa7c20e60 crypto: qat - limit heartbeat notifications f5419a4239af crypto: qat - add auto reset on error 2aaa1995a94a crypto: qat - add fatal error notification 4469f9b23468 crypto: qat - re-enable sriov after pf reset ec26f8e6c784 crypto: qat - update PFVF protocol for recovery 758a0087db98 crypto: qat - disable arbitration before reset ae508d7afb75 crypto: qat - add fatal error notify method e2b67859ab6e crypto: qat - add heartbeat error simulator [Regression potential] We may experience qat regression when crashing or restarting the module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056354/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056616] Re: left-over ceph debugging printks
This bug was fixed in the package linux - 6.8.0-20.20 --- linux (6.8.0-20.20) noble; urgency=medium * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y -- Paolo Pisati Mon, 18 Mar 2024 11:08:14 +0100 ** Changed in: linux (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056616 Title: left-over ceph debugging printks Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: Hello, a pal recently mentioned some debugging printk statements in our kernels, eg: evict_inodes inode d69da69b, i_count = 1, was skipped! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214 has some additional details. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041613 looks like an effort to remove it? This apparently hasn't been finished yet, and it's in the middle of a big run of actual real work, so it might not be super-easy to just yank this out, it might also justify a larger look at the surrounding context. In noble master-next: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/fs/inode.c?h=master- next=603b74b4176fdf6ab2fb83306136947296e7aeb4 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058224] Re: Noble update: v6.8.1 upstream stable release
This bug was fixed in the package linux - 6.8.0-20.20 --- linux (6.8.0-20.20) noble; urgency=medium * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y -- Paolo Pisati Mon, 18 Mar 2024 11:08:14 +0100 ** Changed in: linux (Ubuntu Noble) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058224 Title: Noble update: v6.8.1 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.8.1 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059237] Re: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot
Hi Kowshik, sorry, just noticed the machine data line in the log: "IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1060.00 (NH1060_013) hv:phyp" Well, there is no proposed "ISO" - "-proposed" is just a special (pre-release) area in the archive for packages, incl. kernel. So I just thought about updating to the -20 kernel post install, rebooting and checking if it still happens. Btw. does the IBM Power kernel team has an opinion about Andrea's comment #4: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059237/comments/4 (Since there is a good chance that this is also in the upstream kernels). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059237 Title: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: == Comment:- Kowshik Jois B S == ---Problem Description--- Below trace messges are observed in dmesg after every reboot. [0.474287] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [0.475750] Freeing unused kernel image (initmem) memory: 8832K [0.507388] Checked W+X mappings: passed, no W+X pages found [0.507400] Run /init as init process [0.507403] with arguments: [0.507404] /init [0.507405] with environment: [0.507406] HOME=/ [0.507407] TERM=linux [0.507408] BOOT_IMAGE=/vmlinux-6.8.0-11-generic [0.511892] [ cut here ] [0.511904] UBSAN: array-index-out-of-bounds in /build/linux-MzA0lF/linux-6.8.0/arch/powerpc/kernel/module_64.c:353:17 [0.511909] index 0 is out of range for type 'char [*]' [0.511912] CPU: 13 PID: 1 Comm: systemd Not tainted 6.8.0-11-generic #11-Ubuntu [0.511917] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1060.00 (NH1060_013) hv:phyp pSeries [0.511921] Call Trace: [0.511922] [c6683620] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.511931] [c6683650] [c0c7bc58] __ubsan_handle_out_of_bounds+0xc4/0x12c [0.511938] [c6683700] [c005d2a8] module_frob_arch_sections+0x4ec/0x8d0 [0.511943] [c66837e0] [c02b98cc] layout_and_allocate.isra.0+0x38/0x2a8 [0.511948] [c6683850] [c02b9dec] load_module+0x138/0xca0 [0.511953] [c6683990] [c02baca8] init_module_from_file+0xb4/0x14c [0.511958] [c6683a70] [c02baf70] sys_finit_module+0x230/0x48c [0.511963] [c6683b80] [c0033248] system_call_exception+0xe8/0x240 [0.511967] [c6683e50] [c000d15c] system_call_vectored_common+0x15c/0x2ec [0.511972] --- interrupt: 3000 at 0x7879b903b8a8 [0.511977] NIP: 7879b903b8a8 LR: CTR: [0.511980] REGS: c6683e80 TRAP: 3000 Not tainted (6.8.0-11-generic) [0.511984] MSR: 8000f033 CR: 48222428 XER: [0.511993] IRQMASK: 0 GPR00: 0161 7fffd683b580 7879b9166d00 0004 GPR04: 7879b8e0c160 0004 0010 0004 GPR08: 0001 GPR12: 7879b99d3a00 2000 0002 GPR16: 1b5c7d7453e0 7fffd683ba68 GPR20: 1b5c82154ae0 1b5c82142360 GPR24: 7879b957f7b0 1b5c82154ae0 1b5c82142160 GPR28: 7879b8e0c160 0002 1b5c82154ae0 1b5c82142380 [0.512029] NIP [7879b903b8a8] 0x7879b903b8a8 [0.512032] LR [] 0x0 [0.512034] --- interrupt: 3000 [0.512036] ---[ end trace ]--- [0.518326] systemd[1]: Inserted module 'autofs4' [0.521570] systemd[1]: systemd 255.2-3ubuntu2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) [0.521583] systemd[1]: Detected virtualization powervm. [0.521589] systemd[1]: Detected architecture ppc64-le. [0.521593] systemd[1]: Running in initrd. [0.521743] systemd[1]: No hostname configured, using default hostname. [0.521789] systemd[1]: Hostname set to . [0.521847] systemd[1]: Initializing machine ID from random generator. [0.600736] systemd[1]: Queued start job
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
This bug was fixed in the package plymouth - 24.004.60-1ubuntu6 --- plymouth (24.004.60-1ubuntu6) noble; urgency=medium * Cherry-pick upstream fixes for consistent default scale selection that matches what Mutter chooses on the login screen (LP: #2054769) * plymouth.hook: Stop automatically re-installing DRM kernel modules in initrd. initramfs-tools already does this for us in hooks/framebuffer and should be the authority for which drivers to include. * Install a /usr/share/initramfs-tools/conf-hooks.d/plymouth with FRAMEBUFFER=y to make it clear to initramfs-tools that we always want framebuffer support when Plymouth is installed. (LP: #1970069) -- Daniel van Vugt Thu, 21 Mar 2024 14:46:56 +0100 ** Changed in: plymouth (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2050019] Comment bridged from LTC Bugzilla
--- Comment From fre...@de.ibm.com 2024-03-28 03:42 EDT--- (In reply to comment #13) > Well, I was not able to easily cherry-pick these t commits. > I got merge conflicts due to several debug lines. > > After some investigations (using git blame) I found that the commits: > 0ccac4529540 s390/pkey: harmonize pkey s390 debug feature calls > 6d749b4e0208 s390/pkey: introduce dynamic debugging for pkey > seem to be needed - then even some more. > I finally found that adding the following set of commits (that I've found as > block earlier in git log): > 88e4c0da9b08 s390/zcrypt: harmonize debug feature calls and defines > 08b2c3706de2 s390/zcrypt: introduce dynamic debugging for AP and zcrypt code > 0ccac4529540 s390/pkey: harmonize pkey s390 debug feature calls > 6d749b4e0208 s390/pkey: introduce dynamic debugging for pkey > 6a2892d09df5 s390/ap: add debug possibility for AP messages > b69b65f51148 s390/zcrypt: add debug possibility for CCA and EP11 messages > helped me to apply the initial commits. > > And with that I was also able to build a test kernel in PPA: > https://launchpad.net/~fheimes/+archive/ubuntu/lp2050019 > > Please can you confirm that it's reasonable to go with these (in total now) > 13 commits instead? Well, dependent on your kernel base you may need to pull in some more fixes. Best is to simple follow the commit chain. For example with an git log drivers/s390/crypto you get the commit chain. Filter out the vfio stuff (or even simpler, pick it also) - this way you get an update of the while AP bus + zcrypt + pkey + vfio stuff. Dependencies to the rest of the kernel are rare and can usually be solved simple by pulling in one patch or so. Doing the update this way keeps the code consistent and ready for future backports. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2050019 Title: [24.04 FEAT] [SEC2353] zcrypt: extend error recovery to deal with device scans Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: The error recovery of a crypto request currently fails if a device is not available or the device is not completely setup and bound if the device has been discovered due to a bus scan. If, during request handling, a device is lost and a bus scan is triggered the DD must wait for the bus scan (including the device binding) to complete before giving up on reties. This item is important to support life guest relocation where the APQN sets on the source and target guests differ. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2050019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
I thought it was worth mentioning that sound does work via the headphone jack on Ubuntu 23.10 and that when using the speaker, audio levels are still detected in system settings. This makes me think all codecs etc are working but that it's a simple toggle somewhere to get the speaker to work rather than it requiring driver updates etc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp