[Kernel-packages] [Bug 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4
The fix is landed in Ubuntu-oem-6.1-6.1.0-1024.24, Ubuntu-6.2.0-36.36 and Ubuntu-5.15.0-88.98 ** Tags removed: verification-needed-jammy-linux verification-needed-jammy-linux-oem-6.1 verification-needed-lunar-linux ** Tags added: verification-done-jammy-linux verification-done-jammy-linux-oem-6.1 verification-done-lunar-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2037077 Title: Fix unstable audio at low levels on Thinkpad P1G4 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The audio at low levels is not stable with fluctuating levels. [Fix] Forcibly assign NID 0x03 to HP while NID 0x02 to SPK. [Test] Tested on hardware, the audio output is OK at all levels. [Where problems could occur] It may break audio output on Thinkpad P1G4/5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037077/+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 2033452] Re: Enable D3cold at s2idle for Intel DG2 GPU
The fix is landed in Ubuntu-6.2.0-34.34 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033452 Title: Enable D3cold at s2idle for Intel DG2 GPU Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The system wakes up during s2idle with Intel DG2 GPU. It causes high power consumption during suspend. [Fix] Enable D3cold at s2idle. [Test] Tested on hardware, the system sleeps as long as expected, the power consumption is lower. [Where problems could occur] It may break i915 driver. It's a fix of regression in v6.1, no need for jammy and already in 6.5. SRU for lunar and oem-6.1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033452/+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 2034479] Re: Fix suspend hang on Lenovo workstation
The fix is landed in Ubuntu-5.15.0-88.98 and Ubuntu-6.2.0-36.36. ** Tags removed: verification-needed-jammy-linux verification-needed-lunar-linux ** Tags added: verification-done-jammy-linux verification-done-lunar-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2034479 Title: Fix suspend hang on Lenovo workstation Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Invalid Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The system hang after resume from S3. Error logs: kernel: igb :02:00.0: disabling already-disabled device kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 pci_disable_device+0xc4/0xf0 kernel: RIP: 0010:pci_disable_device+0xc4/0xf0 kernel: Call Trace: kernel: kernel: igb_io_error_detected+0x3e/0x60 kernel: report_error_detected+0xd6/0x1c0 kernel: ? __pfx_report_normal_detected+0x10/0x10 kernel: report_normal_detected+0x16/0x30 kernel: pci_walk_bus+0x74/0xa0 kernel: pcie_do_recovery+0xb9/0x340 kernel: ? __pfx_aer_root_reset+0x10/0x10 kernel: aer_process_err_devices+0x168/0x220 kernel: aer_isr+0x1b5/0x1e0 kernel: ? __pfx_irq_thread_fn+0x10/0x10 kernel: irq_thread_fn+0x21/0x70 kernel: irq_thread+0xf8/0x1c0 kernel: ? __pfx_irq_thread_dtor+0x10/0x10 kernel: ? __pfx_irq_thread+0x10/0x10 kernel: kthread+0xef/0x120 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x29/0x50 kernel: kernel: ---[ end trace ]--- [Fix] The pci io error detected ops is called before the driver resumed. Avoid this race condition to fix the issue. [Test] Tested on hardware, the system suspend/resume OK. [Where problems could occur] It may break igb driver. The commit is included in 6.5-rc1 and merged by stable update in oem-6.1, SRU for Jammy and Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034479/+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 2024427] Re: S3 stress issue for amdgpu Navi 31/Navi33
Can you please upload your journal from the failure? Also can you please experiment with rolling back to this one version of this one firmware binary: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/amdgpu/gc_11_0_0_imu.bin?id=e32209f07556427c9b0b841bfb76ca71e8beab05 Place that in /lib/firmware/updates and rebuild your initramfs and then reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2024427 Title: S3 stress issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-firmware source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Triaged Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2024427 [Impact] Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms will sometimes fail to wake from S3. [Fix] kernel patches: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 firmware patches: * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release [Test Case] $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Little we know about the firmware fixes. However, while with these commits have been pulled via stable kernel fixes, the driver begins to request new firmware blobs of a different filename. [Other Info] The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has to be fixed. For the firmware parts, they have been included in linux-firmware/mantic, leaving linux-firmware/lunar and linux-firmware/jammy to be fixed. == original bug report == amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+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 2033122] Re: Request backport of xen timekeeping performance improvements
** Tags removed: verification-needed-jammy-linux-aws ** Tags added: verification-done-jammy-linux-aws -- 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/2033122 Title: Request backport of xen timekeeping performance improvements Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Users, especially those on EC2, are encouraged to select tsc as their default clocksource. However, this requires manual tuning of the operating system. Kvm can determine if it safe to use the tsc, and will default to that instead of its pvclock when appropriate. This requests a backport of patch does the same for Xen instances. If appropriate, it's fine if this is applied to only the linux-aws branches. Not all Xen EC2 instances advertise explicit nomigrate support, however, on those that do we'll select tsc by default. On the subset of hosts where this is advertised, users will safely default to the more performant clocksource. [Impact] Xen instances default to the xen clocksource which has been documented to be slower. This is required for instances where the tsc is not safe to use, or the guest is subject to migration. On some platforms the performance impact can be high, and users are encouraged to select the tsc when appropriate. Instead of leaving up to users to figure this out by reading a variety of different documents, pick the fast clocksource when it can be determined to be safe to do so. [Backport] Clean cherry pick. No conflicts applying to 5.15 or 6.2. [Test] Booted EC2 xen instances with and without this patch and validated that on those that properly advertised the required criteria via cpuid, that the clocksource defaulted to tsc instead of xen. [Potential Regression] Potential is low, since only absurd configurations could lead to a problem. If this is considered risky, it can be applied to only linux-aws where the documented guidance is for users to enable tsc as the clocksource on Xen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033122/+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 2024427] Re: S3 stress issue for amdgpu Navi 31/Navi33
I upgraded to linux-firmware_20220329.git681281e4-0ubuntu3.19 last night and I couldn't start my computer without going into recovery mode this morning. There were a few warnings about missing firmware in the apt logs, but when I googled them, the usual response is "that's normal". I played around with a pretty good chunk of settings in BIOS, such as Resizable BAR, but it consistently hangs right after "JPEG decode is enabled in VM mode". In recovery mode, I only have access to one monitor; I believe that's by design. GPU: RX 7900 XT Kernel: 6.2.0-34-generic I installed my other GPU during my lunch break, an RX 6700 XT, and it booted up just fine in normal mode. I also tried linux-firmware_20220329.git681281e4-0ubuntu3.20 and it has the same behavior. W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_2_mes_2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_mes_2.bin for module amdgpu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2024427 Title: S3 stress issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-firmware source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Triaged Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2024427 [Impact] Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms will sometimes fail to wake from S3. [Fix] kernel patches: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 firmware patches: * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release [Test Case] $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Little we know about the firmware fixes. However, while with these commits have been pulled via stable kernel fixes, the driver begins to request new firmware blobs of a different filename. [Other Info] The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has to be fixed. For the firmware parts, they have been included in linux-firmware/mantic, leaving linux-firmware/lunar and linux-firmware/jammy to be fixed. == original bug report == amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+subscriptions --
[Kernel-packages] [Bug 2025616] Re: kernel Firmware Bug: TSC ADJUST differs failures during suspend
I have discovered that the bug causes Ubuntu 22.04 NOT to suspend to S3 state (deep). Setting the suspend state to S2Idle works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2025616 Title: kernel Firmware Bug: TSC ADJUST differs failures during suspend Status in linux-nvidia package in Ubuntu: New Bug description: [Summary] Discoverd kernel error message during suspend stress test test case id: power-management/suspend_30_cycles_with_reboots collected log ~~~ High failures: s3: 180 failures HIGH Kernel message: [38779.612837] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5266754042. Restoring (x 3) HIGH Kernel message: [38839.622411] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5295340520. Restoring (x 3) HIGH Kernel message: [38868.467564] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5270514862. Restoring (x 3) HIGH Kernel message: [38897.419897] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5275834616. Restoring (x 3) HIGH Kernel message: [38926.135900] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5249511520. Restoring (x 3) HIGH Kernel message: [38955.114760] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5252454094. Restoring (x 3) HIGH Kernel message: [38983.860142] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5270474360. Restoring (x 3) HIGH Kernel message: [39012.819868] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5264045578. Restoring (x 3) ~~~ [Failure rate] 1/1 [Additional information] CID: 201711-25989 SKU: DGX-1 Station system-manufacturer: NVIDIA system-product-name: DGX Station bios-version: 0406 CPU: Intel(R) Xeon(R) CPU E5-2698 v4 @ 2.20GHz (40x) GPU: 07:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1db2] (rev a1) 08:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1db2] (rev a1) 0e:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1db2] (rev a1) 0f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1db2] (rev a1) nvidia-driver-version: 525.105.17 kernel-version: 5.15.0-1028-nvidia [Stage] Issue reported and logs collected at a later stage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2025616/+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 2033551] Re: mlxbf_bootctl: replace SAUCE patches with upstream
This bug is awaiting verification that the linux- bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2033551 Title: mlxbf_bootctl: replace SAUCE patches with upstream Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The mlxbf_bootctl BlueField platform driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. One patch for the mlxbf_bootctl driver is not yet upstreamed, so that patch will remain as SAUCE patch for now. [Test Case] * Boot BF2/BF3 platform, verify no new errors * Program MFG fields via "bfcfg" tool: 1) With current image, use 'bfcfg -d' to display current values 2) Reboot, stopping at UEFI menu, trigger 'Reset MFG Info' 3) With new image, use 'bfcfg' to push new or same MFG fields 4) Verify that the MFG fields are programmed properly via 'bfcfg -d' 5) Repeat process to replace proper MFG fields * Display BlueField boot log 1) cd /sys/bus/platform/devices/MLNXBF04:00 2) cat rsh_log 3) Should see boot log entries relevant to last boot [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2033551/+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 2033551] Re: mlxbf_bootctl: replace SAUCE patches with upstream
** Tags removed: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2033551 Title: mlxbf_bootctl: replace SAUCE patches with upstream Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The mlxbf_bootctl BlueField platform driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. One patch for the mlxbf_bootctl driver is not yet upstreamed, so that patch will remain as SAUCE patch for now. [Test Case] * Boot BF2/BF3 platform, verify no new errors * Program MFG fields via "bfcfg" tool: 1) With current image, use 'bfcfg -d' to display current values 2) Reboot, stopping at UEFI menu, trigger 'Reset MFG Info' 3) With new image, use 'bfcfg' to push new or same MFG fields 4) Verify that the MFG fields are programmed properly via 'bfcfg -d' 5) Repeat process to replace proper MFG fields * Display BlueField boot log 1) cd /sys/bus/platform/devices/MLNXBF04:00 2) cat rsh_log 3) Should see boot log entries relevant to last boot [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2033551/+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 2038700] [NEW] package linux-objects-nvidia-535-open-6.2.0-34-generic (not installed) failed to install/upgrade: tentata sovrascrittura di "/lib/modules/6.2.0-34-generic/kernel/
Public bug reported: Linux antonio-System-Product-Name 6.2.0-34-generic #34-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 4 13:06:55 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 6.2.0-34.34-generic 6.2.16 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-objects-nvidia-535-open-6.2.0-34-generic (not installed) ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Oct 6 23:25:32 2023 ErrorMessage: tentata sovrascrittura di "/lib/modules/6.2.0-34-generic/kernel/nvidia-535-open/nvidia-drm.ko" presente anche nel pacchetto linux-modules-nvidia-535-open-6.2.0-34-generic 6.2.0-34.34+1 InstallationDate: Installed on 2023-07-04 (94 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: linux-restricted-modules Title: package linux-objects-nvidia-535-open-6.2.0-34-generic (not installed) failed to install/upgrade: tentata sovrascrittura di "/lib/modules/6.2.0-34-generic/kernel/nvidia-535-open/nvidia-drm.ko" presente anche nel pacchetto linux-modules-nvidia-535-open-6.2.0-34-generic 6.2.0-34.34+1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2038700 Title: package linux-objects-nvidia-535-open-6.2.0-34-generic (not installed) failed to install/upgrade: tentata sovrascrittura di "/lib/modules/6.2.0-34-generic/kernel/nvidia-535-open/nvidia-drm.ko" presente anche nel pacchetto linux-modules- nvidia-535-open-6.2.0-34-generic 6.2.0-34.34+1 Status in linux-restricted-modules package in Ubuntu: New Bug description: Linux antonio-System-Product-Name 6.2.0-34-generic #34-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 4 13:06:55 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 6.2.0-34.34-generic 6.2.16 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-objects-nvidia-535-open-6.2.0-34-generic (not installed) ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Oct 6 23:25:32 2023 ErrorMessage: tentata sovrascrittura di "/lib/modules/6.2.0-34-generic/kernel/nvidia-535-open/nvidia-drm.ko" presente anche nel pacchetto linux-modules-nvidia-535-open-6.2.0-34-generic 6.2.0-34.34+1 InstallationDate: Installed on 2023-07-04 (94 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: linux-restricted-modules Title: package linux-objects-nvidia-535-open-6.2.0-34-generic (not installed) failed to install/upgrade: tentata sovrascrittura di "/lib/modules/6.2.0-34-generic/kernel/nvidia-535-open/nvidia-drm.ko" presente anche nel pacchetto linux-modules-nvidia-535-open-6.2.0-34-generic 6.2.0-34.34+1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2038700/+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 2035163] Re: Avoid address overwrite in kernel_connect
** Also affects: linux-gkeop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2035163 Title: Avoid address overwrite in kernel_connect Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Invalid Status in linux-gkeop package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-gcp source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Released Status in linux-gke source package in Jammy: Fix Released Status in linux-gkeop source package in Jammy: New Status in linux source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 Testing: - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. Regression potenial: - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035163/+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 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
Special maas image built with util-linux, 2.39.1-4ubuntu2, from https://ppa.launchpadcontent.net/xnox/release-critical/ubuntu is looking good. I have one machine deployed with this: ubuntu@rumford:~$ uname -r 6.5.0-5-lowlatency ubuntu@rumford:~$ apt-cache policy util-linux util-linux: Installed: 2.39.1-4ubuntu2 Candidate: 2.39.1-4ubuntu2 Version table: *** 2.39.1-4ubuntu2 500 500 https://ppa.launchpadcontent.net/xnox/release-critical/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status 2.39.1-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages ubuntu@rumford:~$ cat /etc/cloud/build.info build_name: server serial: 20231006.1732 -- 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/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in cloud-images: New Status in maas-images: Confirmed Status in The Ubuntu-power-systems project: Invalid Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Triaged Status in linux source package in Mantic: Invalid Status in systemd source package in Mantic: Invalid Status in util-linux source package in Mantic: Triaged Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2037417/+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 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
** Changed in: util-linux (Ubuntu Mantic) Status: New => Triaged ** Changed in: util-linux (Ubuntu Mantic) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu Mantic) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Mantic) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu Mantic) Status: Incomplete => Invalid ** Changed in: ubuntu-power-systems Status: Confirmed => Invalid ** Changed in: maas-images Status: New => Confirmed ** Also affects: cloud-images 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/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in cloud-images: New Status in maas-images: Confirmed Status in The Ubuntu-power-systems project: Invalid Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Triaged Status in linux source package in Mantic: Invalid Status in systemd source package in Mantic: Invalid Status in util-linux source package in Mantic: Triaged Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2037417/+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 2038685] Re: Missing BTF file in Ubuntu ESM kernels
** Attachment added: "/proc/version_signature" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707486/+files/version.log ** Attachment removed: "cat /proc/version_signature" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707462/+files/version.log ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707463/+files/AlsaInfo.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707464/+files/CRDA.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707465/+files/CurrentDmesg.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707466/+files/IwConfig.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707467/+files/Lspci.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707469/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707468/+files/ProcCpuinfo.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707470/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707471/+files/ProcModules.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707472/+files/PulseList.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707473/+files/UdevDb.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707474/+files/WifiSyslog.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-4.15.0-218-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not
[Kernel-packages] [Bug 2038685] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707485/+files/WifiSyslog.txt ** Description changed: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. - P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. - --- - ProblemType: Bug - ApportVersion: 2.20.9-0ubuntu7.29 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: andres 3050 F pulseaudio - CurrentDesktop: ubuntu:GNOME - DistroRelease: Ubuntu 18.04 - InstallationDate: Installed on 2021-05-18 (870 days ago) - InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) - Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. - Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub - Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse - Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub - MachineType: VMware, Inc. VMware Virtual Platform - Package: linux (not installed) - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - ProcFB: 0 svgadrmfb - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet - ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248 - RelatedPackageVersions: - linux-restricted-modules-5.4.0-164-generic N/A - linux-backports-modules-5.4.0-164-generic N/A - linux-firmware 1.173.21 - RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no - Tags: bionic - Uname: Linux 5.4.0-164-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo - _MarkForUpload: True - dmi.bios.date: 11/12/2020 - dmi.bios.vendor: Phoenix Technologies LTD - dmi.bios.version: 6.00 - dmi.board.name: 440BX Desktop Reference Platform - dmi.board.vendor: Intel Corporation - dmi.board.version: None - dmi.chassis.asset.tag: No Asset Tag - dmi.chassis.type: 1 - dmi.chassis.vendor: No Enclosure - dmi.chassis.version: N/A - dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: - dmi.product.name: VMware Virtual Platform - dmi.product.version: None - dmi.sys.vendor: VMware, Inc. - --- + P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave + me an error saying `Problem in linux-image-4.15.0-218-generic This is + not an official Ubuntu package. Please remove any third party package + and try again`. I am not sure why it says that as this is a Ubuntu VM + downloaded from the Ubuntu site, upgraded by doing `pro attach` and then + updated to the latest ESM kernel. + + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME
[Kernel-packages] [Bug 2038685] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707484/+files/UdevDb.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-4.15.0-218-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-218-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 4.15.0-218.229-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-218-generic N/A linux-backports-modules-4.15.0-218-generic N/A linux-firmware 1.173.21 RfKill: Tags: bionic Uname: Linux 4.15.0-218-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707483/+files/PulseList.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-4.15.0-218-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-218-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 4.15.0-218.229-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-218-generic N/A linux-backports-modules-4.15.0-218-generic N/A linux-firmware 1.173.21 RfKill: Tags: bionic Uname: Linux 4.15.0-218-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707482/+files/ProcModules.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-4.15.0-218-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-218-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 4.15.0-218.229-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-218-generic N/A linux-backports-modules-4.15.0-218-generic N/A linux-firmware 1.173.21 RfKill: Tags: bionic Uname: Linux 4.15.0-218-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707480/+files/ProcCpuinfoMinimal.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-4.15.0-218-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-218-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 4.15.0-218.229-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-218-generic N/A linux-backports-modules-4.15.0-218-generic N/A linux-firmware 1.173.21 RfKill: Tags: bionic Uname: Linux 4.15.0-218-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707479/+files/ProcCpuinfo.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-4.15.0-218-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-218-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 4.15.0-218.229-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-218-generic N/A linux-backports-modules-4.15.0-218-generic N/A linux-firmware 1.173.21 RfKill: Tags: bionic Uname: Linux 4.15.0-218-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707481/+files/ProcInterrupts.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-4.15.0-218-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-218-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 4.15.0-218.229-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-218-generic N/A linux-backports-modules-4.15.0-218-generic N/A linux-firmware 1.173.21 RfKill: Tags: bionic Uname: Linux 4.15.0-218-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707478/+files/Lspci.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-4.15.0-218-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-218-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 4.15.0-218.229-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-218-generic N/A linux-backports-modules-4.15.0-218-generic N/A linux-firmware 1.173.21 RfKill: Tags: bionic Uname: Linux 4.15.0-218-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707477/+files/IwConfig.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-4.15.0-218-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-218-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 4.15.0-218.229-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-218-generic N/A linux-backports-modules-4.15.0-218-generic N/A linux-firmware 1.173.21 RfKill: Tags: bionic Uname: Linux 4.15.0-218-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707476/+files/CurrentDmesg.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-4.15.0-218-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-218-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 4.15.0-218.229-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-218-generic N/A linux-backports-modules-4.15.0-218-generic N/A linux-firmware 1.173.21 RfKill: Tags: bionic Uname: Linux 4.15.0-218-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] Re: Missing BTF file in Ubuntu ESM kernels
apport information ** Description changed: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andres 3050 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.173.21 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.29 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2021-05-18 (870 days ago) + InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) + Lsusb: + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. + Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub + Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: VMware, Inc. VMware Virtual Platform +
[Kernel-packages] [Bug 2038685] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707473/+files/UdevDb.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andres 3050 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.173.21 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707471/+files/ProcModules.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andres 3050 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.173.21 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707472/+files/PulseList.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andres 3050 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.173.21 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707470/+files/ProcInterrupts.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andres 3050 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.173.21 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707474/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andres 3050 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.173.21 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707469/+files/ProcCpuinfoMinimal.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andres 3050 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.173.21 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707468/+files/ProcCpuinfo.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andres 3050 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.173.21 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707467/+files/Lspci.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andres 3050 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.173.21 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707466/+files/IwConfig.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andres 3050 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.173.21 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707465/+files/CurrentDmesg.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andres 3050 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.173.21 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707464/+files/CRDA.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andres 3050 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.173.21 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038685] Re: Missing BTF file in Ubuntu ESM kernels
apport information ** Tags added: apport-collected bionic ** Description changed: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. - P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave - me an error saying `Problem in linux-image-5.4.0-164-generic This is not - an official Ubuntu package. Please remove any third party package and - try again`. I am not sure why it says that as this is a Ubuntu VM - downloaded from the Ubuntu site, upgraded by doing `pro attach` and then - updated to the latest ESM kernel. + P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.29 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: andres 3050 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2021-05-18 (870 days ago) + InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) + Lsusb: + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. + Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub + Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: VMware, Inc. VMware Virtual Platform + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 svgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet + ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-164-generic N/A + linux-backports-modules-5.4.0-164-generic N/A + linux-firmware 1.173.21 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: bionic + Uname: Linux 5.4.0-164-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/12/2020 + dmi.bios.vendor: Phoenix Technologies LTD + dmi.bios.version: 6.00 + dmi.board.name: 440BX Desktop Reference Platform + dmi.board.vendor: Intel Corporation + dmi.board.version: None + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 1 + dmi.chassis.vendor: No Enclosure + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: + dmi.product.name: VMware Virtual Platform + dmi.product.version: None + dmi.sys.vendor: VMware, Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2038685/+attachment/5707463/+files/AlsaInfo.txt -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Bug description: This is a follow-up
[Kernel-packages] [Bug 2021572] Re: dGPU cannot resume because system firmware stuck in IPCS method
This bug is awaiting verification that the linux- aws-6.2/6.2.0-1014.14~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2021572 Title: dGPU cannot resume because system firmware stuck in IPCS method Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When a dGPU on a laptop is in PCIe D3cold and TBT port is connected to a monitor via a cable, unplugging the cable will make the dGPU unable to resume to D0. [Fix] There's a part of system firmware, IOM, need the driver to disconnect all TBT/Type-C phy to let dGPU function normally. [Test] With the fix applied, the dGPU continues to work after replugging video cable many times. [Where problems could occur] The fix is composed of several overhaul, so it's likely to regression i915 GFX driver. To limit the impact, only target OEM kernel for now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2021572/+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 2022361] Re: Please enable Renesas RZ platform serial installer
This bug is awaiting verification that the linux- aws-6.2/6.2.0-1014.14~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2 -- 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/2022361 Title: Please enable Renesas RZ platform serial installer Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] The ubuntu installer does not work via serial ports for Renesas boards like RZ/G2M-HiHope (https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board, RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board (https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC). The installation can be done using HDMI ports, but it would be nice to support installation via serial port as well. [Test case] Try to install Ubuntu on a Renesas board. [Fix] Statically build SuperH SCI(F) serial port support (with earlyconsole). [Regression potential] Statically building an additional driver in the kernel can make the kernel image bigger, potentially causing boot issues in small (arm64 / armhf) platforms. [Original bug report] Package: linux Version: Ubuntu-6.2.0-21.21 Severity: normal File: /mantic/debian.master/config/annotations Dear Maintainer, The ubuntu kernel is missing a few configuration options for Renesas RZ/G2M MPU as below: #Modify the following config from m to y. CONFIG_SERIAL_SH_SCI=y #add below configuration CONFIG_SERIAL_SH_SCI_CONSOLE=y CONFIG_SERIAL_SH_SCI_EARLYCON=y The above changes are required in annotations file: "/mantic/debian.master/config/annotations" code location: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372 #Modify the following line (change 'm' to 'y') CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}> #Add the following lines: CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}> CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}> Could you please add those configuration options to the Ubuntu kernel? Best Regards John To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+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 2026322] Re: Fix non-working MT7921e when pre-boot WiFi is enabled
This bug is awaiting verification that the linux- aws-6.2/6.2.0-1014.14~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2026322 Title: Fix non-working MT7921e when pre-boot WiFi is enabled Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When "pre-boot WiFi" is enabled in UEFI, MT7921e WiFi doesn't work under Linux. [Fix] Reset the device earlier at the probing process. [Test] With the patch applied, WiFi always works regardless of pre-boot WiFi is toggled or not. [Where problems could occur] Probe routine might fail one some other corner cases. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2026322/+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 2028122] Re: Fix unreliable ethernet cable detection on I219 NIC
This bug is awaiting verification that the linux- aws-6.2/6.2.0-1014.14~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2028122 Title: Fix unreliable ethernet cable detection on I219 NIC Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Hotplugging RJ45 ethernet cable only works for one time because ACPI GPE wake doesn't working properly anymore. [Fix] Always use PME poll to read PCI PME to know if there's wake event. [Test] With the patch applied, ethernet cable can always be detected. [Where problems could occur] PME poll mechanism periodically reads the PMCTRL register, so the power consumption can be slightly higher. The increase will be very low, probably won't be noticeable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028122/+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 2030924] Re: [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in cpuinfo_min_freq and cpuino_max_freq sysfs files.
This bug is awaiting verification that the linux- aws-6.2/6.2.0-1014.14~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2 -- 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/2030924 Title: [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in cpuinfo_min_freq and cpuino_max_freq sysfs files. Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] On DELL EMC PowerEdge system when Ubuntu 22.04.1 OS is Installed, Unable to Interpret the values in cpuinfo_max_freq and cpuinfo_min_freq sysfs files as per the Intel specs document. Steps to Reproduce: 1. Install one CPU that supports DBS "Demand-Based Power Management". 2. Install Ubuntu 22.04.1 OS. 2. Enable "Logical Processor" under CPU Information menu from F2 setup. 3. Save changes and reboot to Ubuntu 22.04.1 OS. 4. Right click on "Computer" and select "File system" and check for the following CPU directories. /sys/devices/system/cpu/cpu0/cpufreq/cpu0 /sys/devices/system/cpu/cpu0/cpufreq/cpu1 5. View the Max Frequency and Min Frequency under CPU0 and CPU1 directory. 6. The Max and Min Frequency did not match as per the Intel specs datasheet. Actual results: /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 680 /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 80 /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 390 Expected results: As per Intel datasheet specification. /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 5300 MHz /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 800 MHz /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 3000 MHz [Fix] cpufreq: intel_pstate: Fix scaling for hybrid-capable systems with disabled E-cores https://github.com/torvalds/linux/commit/0fcfc9e51990246a9813475716746ff5eb98c6aa [github.com] [Test Plan] Same as steps to reproduce [ Where problems could occur ] This issue is seen on Intel based system under development which supports DBS "Demand-Based Power Management", then install Ubuntu-22.04 and boot into OS then check for the frequency values under /sys/devices/system/cpu/cpu0/cpufreq/cpu0 Regression risk = Low to medium [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/cpuinfo_freq lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/cpuinfo_freq_lunar_2 Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/cpuinfo_freq_mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030924/+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 2032704] Re: Fix panel brightness issues on HP laptops
This bug is awaiting verification that the linux- aws-6.2/6.2.0-1014.14~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2032704 Title: Fix panel brightness issues on HP laptops Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Brightness can't be changed or can only be changed once on some modern HP laptops. [Fix] BIOS folks identified the issue where the ACPI _PS0 method isn't called for the panel device. On Windows the method is being invoked. This is due to missing _PSC, but since Windows is the de facto spec, we have to perform the same to make the device functional. [Test] Once the fix is applied, the brightness can be changed smoothly. [Where problems could occur] According to BIOS folks, Windows also invokes _PS3 for sleep and shutdown, we need to tackle that in the future. Right now not calling _PS3 has no ill-effect, per BIOS folks. X-HWE-Bug: Bug #2032704 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032704/+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 2033025] Re: Fix numerous AER related issues
This bug is awaiting verification that the linux- aws-6.2/6.2.0-1014.14~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2032767] Re: Fix ACPI TAD on some Intel based systems
This bug is awaiting verification that the linux- aws-6.2/6.2.0-1014.14~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2032767 Title: Fix ACPI TAD on some Intel based systems Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] ACPI TAD doesn't really work on several systems. When accessing TAD interface via sysfs, like setting/getting realtime, it also causes errors: [ 478.255453] ACPI Error: No handler for Region [RTCM] (a8d2dd39) [SystemCMOS] (20230331/evregion-130) [ 478.255458] ACPI Error: Region SystemCMOS (ID=5) has no handler (20230331/exfldio-261) [ 478.255461] Initialized Local Variables for Method [_GRT]: [ 478.255461] Local1: f182542cInteger [ 478.255464] No Arguments are initialized for method [_GRT] [ 478.255465] ACPI Error: Aborting method \_SB.AWAC._GRT due to previous error (AE_NOT_EXIST) (20230331/psparse-529) [Fix] Let the driver to install a handler for its SystemCMOS region. The spec on whether certain devices can use SystemCMOS or not is quite vague, so follow the de facto implementation, Windows :) [Test] Once the patch is applied, setting and getting realtime through TAD sysfs work, and there's no more error in dmesg. [Where problems could occur] Now ACPI TAD driver also depends on ACPI RTC driver, so the memory usage will go up slightly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032767/+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 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux- aws-6.2/6.2.0-1014.14~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2 -- 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/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 2033452] Re: Enable D3cold at s2idle for Intel DG2 GPU
This bug is awaiting verification that the linux- aws-6.2/6.2.0-1014.14~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033452 Title: Enable D3cold at s2idle for Intel DG2 GPU Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The system wakes up during s2idle with Intel DG2 GPU. It causes high power consumption during suspend. [Fix] Enable D3cold at s2idle. [Test] Tested on hardware, the system sleeps as long as expected, the power consumption is lower. [Where problems could occur] It may break i915 driver. It's a fix of regression in v6.1, no need for jammy and already in 6.5. SRU for lunar and oem-6.1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033452/+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 2033122] Re: Request backport of xen timekeeping performance improvements
This bug is awaiting verification that the linux- aws-6.2/6.2.0-1014.14~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2 -- 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/2033122 Title: Request backport of xen timekeeping performance improvements Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Users, especially those on EC2, are encouraged to select tsc as their default clocksource. However, this requires manual tuning of the operating system. Kvm can determine if it safe to use the tsc, and will default to that instead of its pvclock when appropriate. This requests a backport of patch does the same for Xen instances. If appropriate, it's fine if this is applied to only the linux-aws branches. Not all Xen EC2 instances advertise explicit nomigrate support, however, on those that do we'll select tsc by default. On the subset of hosts where this is advertised, users will safely default to the more performant clocksource. [Impact] Xen instances default to the xen clocksource which has been documented to be slower. This is required for instances where the tsc is not safe to use, or the guest is subject to migration. On some platforms the performance impact can be high, and users are encouraged to select the tsc when appropriate. Instead of leaving up to users to figure this out by reading a variety of different documents, pick the fast clocksource when it can be determined to be safe to do so. [Backport] Clean cherry pick. No conflicts applying to 5.15 or 6.2. [Test] Booted EC2 xen instances with and without this patch and validated that on those that properly advertised the required criteria via cpuid, that the clocksource defaulted to tsc instead of xen. [Potential Regression] Potential is low, since only absurd configurations could lead to a problem. If this is considered risky, it can be applied to only linux-aws where the documented guidance is for users to enable tsc as the clocksource on Xen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033122/+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 2033654] Re: amdgpu: Fixes for S0i3 resume on Phoenix
This bug is awaiting verification that the linux- aws-6.2/6.2.0-1014.14~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033654 Title: amdgpu: Fixes for S0i3 resume on Phoenix Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Hard hangs in some cases on resume from suspend on AMD Phoenix [Fix] pick three commits from v6.5-rc7 (also in 6.1.47): 730d44e1fa306a2 drm/amd/pm: skip the RLC stop when S0i3 suspend for SMU v13.0.4/11 f1740b1ab2703b2 drm/amdgpu: skip fence GFX interrupts disable/enable for S0ix a7b7d9e8aee4f71 drm/amd: flush any delayed gfxoff on suspend entry [Test Case] Check the updated kernel on a failing system, and test resume from suspend. [Where problems could occur] These are cherry-picks from upstream stable, and limited to Phoenix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033654/+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 2037316] Re: SEV_SNP failure to init
This bug is awaiting verification that the linux-gcp/6.2.0-1017.19 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-gcp' to 'verification-done-lunar- linux-gcp'. If the problem still exists, change the tag 'verification- needed-lunar-linux-gcp' to 'verification-failed-lunar-linux-gcp'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-gcp-v2 verification-needed-lunar-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: Invalid Status in linux-gcp source package in Jammy: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+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 2038685] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2038685 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Incomplete Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature
Fix under review https://lists.ubuntu.com/archives/kernel- team/2023-October/146015.html -- 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/2038567 Title: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in lxd package in Ubuntu: Triaged Status in snapd package in Ubuntu: New Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+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 2038685] [NEW] Missing BTF file in Ubuntu ESM kernels
Public bug reported: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "cat /proc/version_signature" https://bugs.launchpad.net/bugs/2038685/+attachment/5707462/+files/version.log -- 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/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: New Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+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 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature
Fix for the ptrace issue ** Patch added: "0001-UBUNTU-SAUCE-no-up-apparmor-disable-1ea37b26d720-UBU.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038567/+attachment/5707461/+files/0001-UBUNTU-SAUCE-no-up-apparmor-disable-1ea37b26d720-UBU.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/2038567 Title: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in lxd package in Ubuntu: Triaged Status in snapd package in Ubuntu: New Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+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 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/snap not yet compatible with this new apparmor feature
** Summary changed: - Mantic 6.5.0-7 kernel causes regression in LXD container usage + Disable restricting unprivileged change_profile by default, due to LXD latest/snap not yet compatible with this new apparmor feature ** Changed in: lxd (Ubuntu) Importance: Undecided => High ** Changed in: lxd (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Summary changed: - Disable restricting unprivileged change_profile by default, due to LXD latest/snap not yet compatible with this new apparmor feature + Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature -- 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/2038567 Title: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in lxd package in Ubuntu: Triaged Status in snapd package in Ubuntu: New Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+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 2038681] Re: nvidia-driver-535.113.01 crash
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2038681 Title: nvidia-driver-535.113.01 crash Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: It was running RealVNC server, VMware Workstation Pro with Windows 11 guest, Firefox and Thunderbird. I used it with RealVNC Viewer on another machine and suddenly my VNC connection dropped. Coming to my nVIDIA laptop it was showing no gnome desktop anymore but a black screen. I could still ssh to the laptop to trigger a reboot. Via journalctl I saw that nVIDIA driver had crashed. I have seen this now with both 535.113.01-0ubuntu0.23.04.1 535.113.01-0ubuntu0.23.04.3 Oct 06 17:01:57 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): The NVIDIA X driver has encountered an error; attempting to Oct 06 17:01:57 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): recover... Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(GPU-0): Failed to initialize DMA. Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): Failed to allocate push buffer Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): Error recovery failed. Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): *** Aborting *** Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: Fatal server error: Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) Failed to recover from error! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.113.01 Tue Sep 12 19:41:24 UTC 2023 GCC version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~23.04) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: GNOME Date: Fri Oct 6 19:12:16 2023 DistUpgraded: 2023-04-14 13:11:36,442 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/535.113.01, 6.2.0-33-generic, x86_64: installed nvidia/535.113.01, 6.2.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3f8c] InstallationDate: Installed on 2021-05-17 (871 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 81Y6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=998a3bca-88e2-4d44-ab68-6776750daa09 ro nvidia-drm.modeset=1 acpi_backlight=native nvidia.NVreg_RegistryDwords=EnableBrightnessControl=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to lunar on 2023-04-14 (175 days ago) dmi.bios.date: 06/09/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: EFCN59WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15IMH05H dmi.ec.firmware.release: 1.59 dmi.modalias: dmi:bvnLENOVO:bvrEFCN59WW:bd06/09/2023:br1.59:efr1.59:svnLENOVO:pn81Y6:pvrLenovoLegion515IMH05H:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegion515IMH05H:skuLENOVO_MT_81Y6_BU_idea_FM_Legion515IMH05H: dmi.product.family: Legion 5 15IMH05H dmi.product.name: 81Y6 dmi.product.sku: LENOVO_MT_81Y6_BU_idea_FM_Legion 5 15IMH05H dmi.product.version: Lenovo Legion 5 15IMH05H dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core:
[Kernel-packages] [Bug 2038681] [NEW] nvidia-driver-535.113.01 crash
You have been subscribed to a public bug: It was running RealVNC server, VMware Workstation Pro with Windows 11 guest, Firefox and Thunderbird. I used it with RealVNC Viewer on another machine and suddenly my VNC connection dropped. Coming to my nVIDIA laptop it was showing no gnome desktop anymore but a black screen. I could still ssh to the laptop to trigger a reboot. Via journalctl I saw that nVIDIA driver had crashed. I have seen this now with both 535.113.01-0ubuntu0.23.04.1 535.113.01-0ubuntu0.23.04.3 Oct 06 17:01:57 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): The NVIDIA X driver has encountered an error; attempting to Oct 06 17:01:57 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): recover... Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(GPU-0): Failed to initialize DMA. Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): Failed to allocate push buffer Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): Error recovery failed. Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): *** Aborting *** Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: Fatal server error: Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) Failed to recover from error! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.113.01 Tue Sep 12 19:41:24 UTC 2023 GCC version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~23.04) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: GNOME Date: Fri Oct 6 19:12:16 2023 DistUpgraded: 2023-04-14 13:11:36,442 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/535.113.01, 6.2.0-33-generic, x86_64: installed nvidia/535.113.01, 6.2.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3f8c] InstallationDate: Installed on 2021-05-17 (871 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 81Y6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=998a3bca-88e2-4d44-ab68-6776750daa09 ro nvidia-drm.modeset=1 acpi_backlight=native nvidia.NVreg_RegistryDwords=EnableBrightnessControl=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to lunar on 2023-04-14 (175 days ago) dmi.bios.date: 06/09/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: EFCN59WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15IMH05H dmi.ec.firmware.release: 1.59 dmi.modalias: dmi:bvnLENOVO:bvrEFCN59WW:bd06/09/2023:br1.59:efr1.59:svnLENOVO:pn81Y6:pvrLenovoLegion515IMH05H:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegion515IMH05H:skuLENOVO_MT_81Y6_BU_idea_FM_Legion515IMH05H: dmi.product.family: Legion 5 15IMH05H dmi.product.name: 81Y6 dmi.product.sku: LENOVO_MT_81Y6_BU_idea_FM_Legion 5 15IMH05H dmi.product.version: Lenovo Legion 5 15IMH05H dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash lunar ubuntu -- nvidia-driver-535.113.01
[Kernel-packages] [Bug 2038567] Re: Mantic 6.5.0-7 kernel causes regression in LXD container usage
Thanks John, it has been confirmed that 1ea37b26d720 UBUNTU: SAUCE: apparmor4.0.0 [73/76]: userns - allow restricting unprivileged change_profile is causing the issue. It has a sysctl to disable its behavior, but the sysctl can't be defaulted to off in the kernel. So to disable the sysctl, either 1. lxd needs to do it dynamically like it is doing for some other sysctls 2. we need the disable it at the system level 3. we revert the patch For the time frame we are looking at, I recommend reverting the patch. Doing so will not materially affect the userns mediation feature. This patch is about closing off a confinement escape. -- 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/2038567 Title: Mantic 6.5.0-7 kernel causes regression in LXD container usage Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+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 2038678] Re: linux (6.2.0-34.34) lunar; urgency=medium * lunar/linux: 6.2.0-34.34 -proposed tracker (LP: #2033779)
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: - black screen after grub and after login using i915 + black screen after grub and after login using i915 revert back to previous kernel. 6.2.0-33 + unable to run report for logs due to black screen. -- 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/2038678 Title: linux (6.2.0-34.34) lunar; urgency=medium* lunar/linux: 6.2.0-34.34 -proposed tracker (LP: #2033779) Status in linux package in Ubuntu: Confirmed Bug description: black screen after grub and after login using i915 revert back to previous kernel. 6.2.0-33 unable to run report for logs due to black screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038678/+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 2038678] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2038678 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/2038678 Title: linux (6.2.0-34.34) lunar; urgency=medium* lunar/linux: 6.2.0-34.34 -proposed tracker (LP: #2033779) Status in linux package in Ubuntu: Incomplete Bug description: black screen after grub and after login using i915 revert back to previous kernel. 6.2.0-33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038678/+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 2038678] [NEW] linux (6.2.0-34.34) lunar; urgency=medium * lunar/linux: 6.2.0-34.34 -proposed tracker (LP: #2033779)
Public bug reported: black screen after grub and after login using i915 revert back to previous kernel. 6.2.0-33 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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/2038678 Title: linux (6.2.0-34.34) lunar; urgency=medium* lunar/linux: 6.2.0-34.34 -proposed tracker (LP: #2033779) Status in linux package in Ubuntu: Incomplete Bug description: black screen after grub and after login using i915 revert back to previous kernel. 6.2.0-33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038678/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Thanks, Pradip! You are great! I hope the fix will come soon. I like Linux, so I would like to use it. Have a nice day! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 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.2/+bug/2034477/+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 2038675] Re: mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet)
Patches submitted for review: https://lists.ubuntu.com/archives/kernel- team/2023-October/146007.html ** Also affects: linux-azure (Ubuntu Lunar) Importance: Undecided Status: New -- 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/2038675 Title: mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet) Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Lunar: New Status in linux-azure source package in Mantic: New Bug description: SRU Justification [Impact] The Microsoft MANA network driver does not accurately report some statistics and does not correctly handle some error conditions. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b2b69a4c https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=7a54de926574 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=a43e8e9ffa0d [Test Plan] Microsoft tested. [Regression Potential] GSO packets may not be correctly reported. Some error conditions may cause incorrect statistics to be recorded, or flood the kernel log with error messages. [Other Info] SF: 00370665 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2038675/+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 2037560] Re: wireless modules not loaded after suspend?
This may be related to this file that I had set up at some point (to workaround some suspend bluetooth issues?): $ cat /usr/lib/systemd/system-sleep/bluetooth #!/bin/sh case $1 in pre) systemctl stop NetworkManager.service rmmod ath10k_pci ath10k_core ath btmgmt power off ;; post) btmgmt power on modprobe ath10k_pci systemctl start NetworkManager.service ;; esac ... at least that would explain the unloading of the modules, but not sure why the `post` section isn't reloading them? -- 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/2037560 Title: wireless modules not loaded after suspend? Status in linux package in Ubuntu: Confirmed Bug description: On mantic, after a suspend my network doesn't come up automatically. I have historically run the following to "reset" networking; not sure what of it is necessary and what's not, but this brings it up: $ sudo systemctl stop NetworkManager.service; sudo rmmod ath10k_pci ath10k_core ath; sleep 3; sudo modprobe ath10k_pci ; sudo systemctl start NetworkManager.service rmmod does complain that none of the ath* modules are currently loaded, so perhaps that's why the network doesn't come up automatically? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-5-generic 6.5.0-5.5 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbarnett 74523 F wireplumber /dev/snd/controlC0: jbarnett 74523 F wireplumber /dev/snd/seq:jbarnett 74508 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Sep 27 08:12:37 2023 InstallationDate: Installed on 2019-08-17 (1502 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.5.0-5-generic N/A linux-backports-modules-6.5.0-5-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to mantic on 2023-09-26 (1 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037560/+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 2038675] [NEW] mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet)
Public bug reported: SRU Justification [Impact] The Microsoft MANA network driver does not accurately report some statistics and does not correctly handle some error conditions. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b2b69a4c https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=7a54de926574 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=a43e8e9ffa0d [Test Plan] Microsoft tested. [Regression Potential] GSO packets may not be correctly reported. Some error conditions may cause incorrect statistics to be recorded, or flood the kernel log with error messages. [Other Info] SF: 00370665 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Also affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: New -- 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/2038675 Title: mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet) Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Mantic: New Bug description: SRU Justification [Impact] The Microsoft MANA network driver does not accurately report some statistics and does not correctly handle some error conditions. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b2b69a4c https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=7a54de926574 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=a43e8e9ffa0d [Test Plan] Microsoft tested. [Regression Potential] GSO packets may not be correctly reported. Some error conditions may cause incorrect statistics to be recorded, or flood the kernel log with error messages. [Other Info] SF: 00370665 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2038675/+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 2036627] Re: Azure: net: mana: Configure hwc timeout from hardware
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Mantic) Status: In Progress => Fix Committed -- 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/2036627 Title: Azure: net: mana: Configure hwc timeout from hardware Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] At present hwc timeout value is a fixed value. This patch sets the hwc timeout from the hardware. It now uses a new hardware capability GDMA_DRV_CAP_FLAG_1_HWC_TIMEOUT_RECONFIG to query and set the value in hwc_timeout. [Test Plan] Microsoft tested and approved. [Regression Potential] Timeouts could get mis-configured. [Other Info] SF: #00365762 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036627/+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 2036450] Re: Azure: Update CIFS to v6.5
** Changed in: linux-azure (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-azure in Ubuntu. https://bugs.launchpad.net/bugs/2036450 Title: Azure: Update CIFS to v6.5 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested this patch set to update CIFS and smbfs to the Linux kernel version 6.5. [Test Plan] Microsoft has tested with positive results. [Regression Potential] This is a huge patch set. The potential exists for corruption, connection instabilities, or other cifs related maladies. [Other Info] SF: #00365185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036450/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
I can confirm @cmmrandau findings. mutter 45.0-3ubuntu 3 does not fix the bug but Martin's workaround works for me. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: Triaged Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2038443] Re: mantic:linux: ubuntu_qrt_apparmor: ApparmorTestsuites.test_regression_testsuiteattach_disconnected.
I was going over the ADT results for the complete linux suite: https://autopkgtest.ubuntu.com/results/autopkgtest- mantic/mantic/amd64/l/linux/20231002_144159_55314@/log.gz (6.5.0-7.7) -- 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/2038443 Title: mantic:linux: ubuntu_qrt_apparmor: ApparmorTestsuites.test_regression_testsuiteattach_disconnected. Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in apparmor source package in Mantic: New Status in linux source package in Mantic: Confirmed Bug description: This might be apparmor, the test case, kernel or anything in between: 7720s running attach_disconnected 7720s Fatal Error (unix_fd_server): Unable to run test sub-executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2038443/+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 2038546] Re: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64
linux-firmware - 20230919.git3672ccab-0ubuntu3 is available in ppa:xypron/gnu-efi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2038546 Title: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 Status in linux-firmware package in Ubuntu: Confirmed Bug description: /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the StarFive VisionFive board which uses the starfive kernel flavor. The file was available in Jammy and only recently removed from Mantic. File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding it cyfmac43430-sdio.clm_blob which file WHENCE links to brcmfmac43430-sdio.bin. So this file needs to change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+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 2038546] Re: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64
** Patch added: "linux-firmware-20230919.git3672ccab-0ubuntu2..20230919.git3672ccab-0ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+attachment/5707392/+files/linux-firmware-20230919.git3672ccab-0ubuntu2..20230919.git3672ccab-0ubuntu3.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2038546 Title: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 Status in linux-firmware package in Ubuntu: Confirmed Bug description: /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the StarFive VisionFive board which uses the starfive kernel flavor. The file was available in Jammy and only recently removed from Mantic. File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding it cyfmac43430-sdio.clm_blob which file WHENCE links to brcmfmac43430-sdio.bin. So this file needs to change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
** Changed in: mutter (Ubuntu Mantic) Status: Fix Released => Triaged -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: Triaged Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
I can confirm @cmmrandau findings. mutter 45.0-3ubuntu 3 does not fix the bug but Martin's workaround works for me. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: Triaged Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2038665] Re: bluetooth not working proper; ly
Bluetooth not working as expected in ubuntu 20.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2038665 Title: bluetooth not working proper;ly Status in bluez package in Ubuntu: New Bug description: My bluetooth it's loosing connection every 3 or 4 seconds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 11:21:08 2023 InstallationDate: Installed on 2023-10-04 (1 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUS System Product Name PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic root=UUID=9828ca97-751b-4832-b775-db6c7dab004d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2022 dmi.bios.release: 8.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X670E-E GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/04/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS hciconfig: hci0:Type: Primary Bus: USB BD Address: 2C:0D:A7:1D:E9:2F ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:2128 acl:114 sco:417074 events:3840 errors:0 TX bytes:24227828 acl:3643 sco:414720 commands:147 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2038665/+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 2038665] [NEW] bluetooth not working proper; ly
Public bug reported: My bluetooth it's loosing connection every 3 or 4 seconds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 11:21:08 2023 InstallationDate: Installed on 2023-10-04 (1 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUS System Product Name PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic root=UUID=9828ca97-751b-4832-b775-db6c7dab004d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2022 dmi.bios.release: 8.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X670E-E GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/04/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS hciconfig: hci0: Type: Primary Bus: USB BD Address: 2C:0D:A7:1D:E9:2F ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:2128 acl:114 sco:417074 events:3840 errors:0 TX bytes:24227828 acl:3643 sco:414720 commands:147 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2038665 Title: bluetooth not working proper;ly Status in bluez package in Ubuntu: New Bug description: My bluetooth it's loosing connection every 3 or 4 seconds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 11:21:08 2023 InstallationDate: Installed on 2023-10-04 (1 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUS System Product Name PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic root=UUID=9828ca97-751b-4832-b775-db6c7dab004d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2022 dmi.bios.release: 8.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X670E-E GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/04/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS hciconfig: hci0:Type: Primary Bus: USB BD Address: 2C:0D:A7:1D:E9:2F ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:2128 acl:114 sco:417074 events:3840 errors:0 TX bytes:24227828 acl:3643 sco:414720 commands:147 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2038665/+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 2038443] Re: mantic:linux: ubuntu_qrt_apparmor: ApparmorTestsuites.test_regression_testsuiteattach_disconnected.
Hi! Could you share the kernel and apparmor version? I tested on mantic with the configuration below and I wasn't able to reproduce the failure for this specific test. I did see an unrelated dbus issue with the test suite and proposed a fixed on https://code.launchpad.net/~georgiag/qa-regression-testing/+git/qa-regression-testing/+merge/453056 georgia@sec-mantic-amd64:~/qrt-test-apparmor$ sudo ./test-apparmor.py ApparmorTestsuites.test_regression_testsuite [sudo] password for georgia: Skipping private tests preparing apparmor_4.0.0~alpha2-0ubuntu5.dsc... done (disabling ptrace for this test) . -- Ran 1 test in 574.715s OK georgia@sec-mantic-amd64:~/qrt-test-apparmor$ uname -a Linux sec-mantic-amd64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux georgia@sec-mantic-amd64:~/qrt-test-apparmor$ apt-cache policy apparmor apparmor: Installed: 4.0.0~alpha2-0ubuntu5 Candidate: 4.0.0~alpha2-0ubuntu5 Version table: *** 4.0.0~alpha2-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status georgia@sec-mantic-amd64:~/qrt-test-apparmor$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 Codename: mantic -- 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/2038443 Title: mantic:linux: ubuntu_qrt_apparmor: ApparmorTestsuites.test_regression_testsuiteattach_disconnected. Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in apparmor source package in Mantic: New Status in linux source package in Mantic: Confirmed Bug description: This might be apparmor, the test case, kernel or anything in between: 7720s running attach_disconnected 7720s Fatal Error (unix_fd_server): Unable to run test sub-executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2038443/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Just updated and mutter 45.0-3ubuntu3 does not fix this error. Still crash when lock screen and works with MUTTER_DEBUG_KMS_THREAD_TYPE=user added to /etc/environment -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: Fix Released Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2020413] Re: fix typo in config-checks invocation
** Tags removed: verification-needed-focal-linux ** Tags added: verification-done-focal-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2020413 Title: fix typo in config-checks invocation Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-kvm source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-kvm source package in Jammy: Fix Released Bug description: [Impact] After migrating to the new annotations-only model in jammy we introduced a typo in debian/rules.d/4-checks.mk, that is triggered if we opt to not migrate to the new model and still use the old configs+annotations. [Test case] With debian./config/config.common.ubuntu present run the following command: $ fakeroot debian/rules clean updateconfigs [Fix] Replace @perl -> perl. [Regression potential] It's a trivial typo fix. Regressions can be introduced only if we are still using the old configs+annotations model. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020413/+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 2020531] Re: support python < 3.9 with annotations
** Tags removed: verification-needed-focal-linux ** Tags added: verification-done-focal-linux -- 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/2020531 Title: support python < 3.9 with annotations Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] At the moment we can't use the annotations scripts in focal, because we are using the'|=' update operator for merging dicts, that has been introduced with python 3.9. Rewrite the code that is using this operator in a more portable way and apply this change everywhere, so that annotations will work on any backport/derivative kernels. [Test case] Run `fakeroot debian/rules updateconfigs` in focal (using the new annotations model). [Fix] Try to use the '|=' operator in a try/except block, if it fails fallback to a more portable way. [Regression potential] With this change applied we may experience regressions during the updateconfigs phase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020531/+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 2038567] Re: Mantic 6.5.0-7 kernel causes regression in LXD container usage
on my machine (specs at the end) running Jammy as the host, and launching a Jammy container: 1. lxc launch ubuntu:jammy test-jammy-on-jammy from journal Oct 06 07:36:47 j5awry-sys76 kernel: audit: type=1400 audit(1696595807.223:51559): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-test-jammy-on-jammy_" name="/run/systemd/unit-root/proc/" pid=723735 comm="(d-logind)" fstype="proc" srcname="proc" flags="rw, nosuid, nodev, noexec" Oct 06 07:36:47 j5awry-sys76 kernel: audit: type=1400 audit(1696595807.227:51560): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-test-jammy-on-jammy_" name="/run/systemd/unit-root/tmp/" pid=723724 comm="(crub_all)" flags="rw, nosuid, remount, bind" Oct 06 07:36:47 j5awry-sys76 kernel: audit: type=1400 audit(1696595807.239:51561): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-test-jammy-on-jammy_" name="/run/systemd/unit-root/proc/" pid=723750 comm="(ostnamed)" fstype="proc" srcname="proc" flags="rw, nosuid, nodev, noexec" so i get the same `mount - failed flags match` that i see above, but not the `file-inherit` denies. -- 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/2038567 Title: Mantic 6.5.0-7 kernel causes regression in LXD container usage Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+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 2038567] Re: Mantic 6.5.0-7 kernel causes regression in LXD container usage
Repeating a bit with a Jammy container (hence new comment) ### PRE CONDITION this is using the custom Mantic VM _and_ has apparmor_restrict_unprivileged_unconfined disabled sudo bash -c "echo 0 > /proc/sys/kernel/apparmor_restrict_unprivileged_unconfined" 1. start a jammy container lxc launch ubuntu:jammy Creating the instance Instance name is: alive-bee Starting alive-bee 2. see some apparmor denies in journal Oct 06 12:32:57 mantic-cust-vm kernel: audit: type=1400 audit(1696595577.647:954): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-alive-bee_" name="/run/systemd/unit-root/proc/" pid=5421 comm="(d-logind)" fstype="proc" srcname="proc" flags="rw, nosuid, nodev, noexec" Oct 06 12:33:01 mantic-cust-vm kernel: kauditd_printk_skb: 20 callbacks suppressed Oct 06 12:33:01 mantic-cust-vm kernel: audit: type=1400 audit(1696595581.539:975): apparmor="DENIED" operation="file_inherit" class="file" namespace="root//lxd-alive-bee_" profile="snap.lxd.hook.install" name="/apparmor/.null" pid=5538 comm="snap-exec" requested_mask="wr" denied_mask="wr" fsuid=100 ouid=0 Oct 06 12:33:03 mantic-cust-vm kernel: audit: type=1400 audit(1696595583.771:976): apparmor="DENIED" operation="file_inherit" class="net" namespace="root//lxd-alive-bee_" profile="/snap/snapd/20092/usr/lib/snapd/snap-confine" pid=5784 comm="snap-confine" family="netlink" sock_type="raw" protocol=15 requested_mask="send receive" denied_mask="send receive" Oct 06 12:33:03 mantic-cust-vm kernel: audit: type=1400 audit(1696595583.779:977): apparmor="DENIED" operation="file_inherit" class="file" namespace="root//lxd-alive-bee_" profile="snap.lxd.hook.configure" name="/apparmor/.null" pid=5784 comm="snap-exec" requested_mask="wr" denied_mask="wr" fsuid=100 ouid=0 Oct 06 12:33:03 mantic-cust-vm kernel: audit: type=1400 audit(1696595583.791:978): apparmor="DENIED" operation="file_inherit" class="file" namespace="root//lxd-alive-bee_" profile="/snap/snapd/20092/usr/lib/snapd/snap-confine" name="/apparmor/.null" pid=5784 comm="aa-exec" requested_mask="wr" denied_mask="wr" fsuid=100 ouid=0 Oct 06 12:33:04 mantic-cust-vm kernel: audit: type=1400 audit(1696595584.007:979): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-alive-bee_" name="/run/systemd/unit-root/proc/" pid=5933 comm="(imedated)" fstype="proc" srcname="proc" flags="rw, nosuid, nodev, noexec" 3. snap changes is Done root@alive-bee:~# snap changes ID Status Spawn Ready Summary 1Done9 days ago, at 02:11 UTC today at 12:33 UTC Initialize system state 2Donetoday at 12:32 UTCtoday at 12:33 UTC Initialize device 4. cloud-init is done root@alive-bee:~# cloud-init status status: done So using the latest released jammy container is also now launching "successfully." Unsure how the other apparmor things denies affect container performance. Running a quick spot check of my machine (Jammy) launching a Jammy container -- 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/2038567 Title: Mantic 6.5.0-7 kernel causes regression in LXD container usage Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p
[Kernel-packages] [Bug 2038567] Re: Mantic 6.5.0-7 kernel causes regression in LXD container usage
Did the following: 1. launched a new VM from the custom build lxc launch mantic-20231005 --vm --device root,size=20GiB mantic-cust-vm 2. pushed squashfs and lxc metadata from same custom build lxc file push build.output/livecd.ubuntu-cpc.squashfs mantic-cust-vm/root/ lxc file push vm/mantic-server-cloudimg-amd64-lxd.tar.xz mantic-cust-vm/root/ 3. initialized lxd lxd init --auto 3. imported into lxc lxc image import ./mantic-server-cloudimg-amd64-lxd.tar.xz ./livecd.ubuntu-cpc.squashfs --alias mantic-cust-con 4. launched the container lxc launch mantic-cust-con m-c-c 5. observed the DENIED ptrace Oct 06 12:27:01 mantic-cust-vm kernel: audit: type=1400 audit(1696595221.386:113): apparmor="DENIED" operation="ptrace" class="ptrace" profile="lxd-m-c-c_" pid=2420 comm="systemd" requested_mask="read" denied_mask="read" peer="lxd-m-c- c_//" 6. deleted the container lxc stop m-c-c lxc delete m-c-c 6. disabled apparmor_restrict_unprivileged_unconfined sudo bash -c "echo 0 > /proc/sys/kernel/apparmor_restrict_unprivileged_unconfined" 7. launched container lxc launch mantic-cust-con m-c-c 8. see different apparmor denied messages: Oct 06 12:29:58 mantic-cust-vm kernel: audit: type=1400 audit(1696595398.722:905): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-m-c-c_" name="/run/systemd/unit-root/proc/" pid=4055 comm="(d-logind)" fstype="proc" srcname="proc" flags="rw, nosuid, nodev, noexec" Oct 06 12:29:58 mantic-cust-vm kernel: audit: type=1400 audit(1696595398.766:906): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-m-c-c_" name="/run/systemd/unit-root/proc/" pid=4048 comm="(polkitd)" fstype="proc" srcname="proc" flags="rw, nosuid, nodev, noexec" Oct 06 12:29:58 mantic-cust-vm kernel: audit: type=1400 audit(1696595398.818:907): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-m-c-c_" name="/run/systemd/unit-root/proc/" pid=4071 comm="(ostnamed)" fstype="proc" srcname="proc" flags="rw, nosuid, nodev, noexec" Oct 06 12:29:58 mantic-cust-vm kernel: audit: type=1400 audit(1696595398.874:908): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" label="lxd-m-c-c_//&:lxd-m-c-c_:unconfined" name="rsyslogd" pid=4062 comm="apparmor_parser" Oct 06 12:29:59 mantic-cust-vm kernel: audit: type=1400 audit(1696595399.106:909): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" label="lxd-m-c-c_//&:lxd-m-c-c_:unconfined" name="/usr/lib/snapd/snap-confine" pid=4130 comm="apparmor_parser" Oct 06 12:29:59 mantic-cust-vm kernel: audit: type=1400 audit(1696595399.106:910): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" label="lxd-m-c-c_//&:lxd-m-c-c_:unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=4130 comm="apparmor_parser" Oct 06 12:29:59 mantic-cust-vm kernel: audit: type=1400 audit(1696595399.482:911): apparmor="DENIED" operation="file_inherit" class="net" namespace="root//lxd-m-c-c_" profile="/usr/lib/snapd/snap-confine" pid=4146 comm="snap-confine" family="netlink" sock_type="raw" protocol=15 requested_mask="send receive" denied_mask="send receive" Oct 06 12:29:59 mantic-cust-vm kernel: audit: type=1400 audit(1696595399.498:912): apparmor="DENIED" operation="file_inherit" class="file" namespace="root//lxd-m-c-c_" profile="snap-update-ns.lxd" name="/apparmor/.null" pid=4157 comm="6" requested_mask="wr" denied_mask="wr" fsuid=100 ouid=0 Oct 06 12:29:59 mantic-cust-vm kernel: audit: type=1400 audit(1696595399.558:913): apparmor="DENIED" operation="file_inherit" class="file" namespace="root//lxd-m-c-c_" profile="snap.lxd.hook.install" name="/apparmor/.null" pid=4146 comm="snap-exec" requested_mask="wr" denied_mask="wr" fsuid=100 ouid=0 9. However, these are not affecting the container in the same fashion. Snap finishes initializing, and cloud-init finishes root@mantic-cust-vm:~# lxc shell m-c-c root@m-c-c:~# snap changes ID Status Spawn Ready Summary 1Doneyesterday at 21:03 UTC today at 12:30 UTC Initialize system state 2Donetoday at 12:29 UTC today at 12:30 UTC Initialize device root@m-c-c:~# cloud-init status status: done -- 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/2038567 Title: Mantic 6.5.0-7 kernel causes regression in LXD container usage Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs
[Kernel-packages] [Bug 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- 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/2038582 Title: Turning COMPAT_32BIT_TIME off on arm64 Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-ibm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Bug description: This will prevent existing armhf 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/+source/linux/+bug/2038582/+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 2038586] Re: Turning COMPAT_32BIT_TIME off on armhf
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2038586 Title: Turning COMPAT_32BIT_TIME off on armhf Status in linux package in Ubuntu: Incomplete Status in linux-raspi package in Ubuntu: New Bug description: This will prevent existing armhf 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. Also note small inodes cannot be used by ext4. 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/+source/linux/+bug/2038586/+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 2038652] Re: Focal update: v5.4.253 upstream stable release
** Description changed: + SRU Justification - 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: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.253 upstream stable release + from git://git.kernel.org/ -v5.4.253 upstream stable release -from git://git.kernel.org/ + jbd2: fix incorrect code style + jbd2: fix kernel-doc markups + jbd2: remove redundant buffer io error checks + jbd2: recheck chechpointing non-dirty buffer + jbd2: Fix wrongly judgement for buffer head removing while doing checkpoint + gpio: tps68470: Make tps68470_gpio_output() always set the initial value + bcache: remove 'int n' from parameter list of bch_bucket_alloc_set() + bcache: Fix __bch_btree_node_alloc to make the failure behavior consistent + btrfs: qgroup: catch reserved space leaks at unmount time + btrfs: fix race between quota disable and relocation + btrfs: fix extent buffer leak after tree mod log failure at split_node() + ext4: rename journal_dev to s_journal_dev inside ext4_sb_info + ext4: Fix reusing stale buffer heads from last failed mounting + PCI/ASPM: Return 0 or -ETIMEDOUT from pcie_retrain_link() + PCI/ASPM: Factor out pcie_wait_for_retrain() + PCI/ASPM: Avoid link retraining race + dlm: cleanup plock_op vs plock_xop + dlm: rearrange async condition return + fs: dlm: interrupt posix locks only when process is killed + ftrace: Add information on number of page groups allocated + ftrace: Check if pages were allocated before calling free_pages() + ftrace: Store the order of pages allocated in ftrace_page + ftrace: Fix possible warning on checking all pages used in ftrace_process_locs() + pwm: meson: Remove redundant assignment to variable fin_freq + pwm: meson: Simplify duplicated per-channel tracking + pwm: meson: fix handling of period/duty if greater than UINT_MAX + scsi: qla2xxx: Fix inconsistent format argument type in qla_os.c + scsi: qla2xxx: Array index may go out of bound + uapi: General notification queue definitions + keys: Fix linking a duplicate key to a keyring's assoc_array + ext4: fix to check return value of freeze_bdev() in ext4_shutdown() + i40e: Fix an NULL vs IS_ERR() bug for debugfs_create_dir() + vxlan: calculate correct header length for GPE + phy: hisilicon: Fix an out of bounds check in hisi_inno_phy_probe() + ethernet: atheros: fix return value check in atl1e_tso_csum() + ipv6 addrconf: fix bug where deleting a mngtmpaddr can create a new temporary address + bonding: reset bond's flags when down link is P2P device + team: reset team's flags when down link is P2P device + platform/x86: msi-laptop: Fix rfkill out-of-sync on MSI Wind U100 + net/sched: mqprio: refactor nlattr parsing to a separate function + net/sched: mqprio: add extack to mqprio_parse_nlattr() + net/sched: mqprio: Add length check for TCA_MQPRIO_{MAX/MIN}_RATE64 + benet: fix return value check in be_lancer_xmit_workarounds() + RDMA/mlx4: Make check for invalid flags stricter + drm/msm/dpu: drop enum dpu_core_perf_data_bus_id + drm/msm/adreno: Fix snapshot BINDLESS_DATA size + drm/msm: Fix IS_ERR_OR_NULL() vs NULL check in a5xx_submit_in_rb() + ASoC: fsl_spdif: Silence output on stop + block: Fix a source code comment in include/uapi/linux/blkzoned.h + dm raid: fix missing reconfig_mutex unlock in raid_ctr() error paths + ata: pata_ns87415: mark ns87560_tf_read static + ring-buffer: Fix wrong stat of cpu_buffer->read + tracing: Fix warning in trace_buffered_event_disable() + serial: 8250_dw: Preserve original value of DLF register + serial: sifive: Fix sifive_serial_console_setup() section + USB: serial: option: support Quectel EM060K_128 + USB: serial: option: add Quectel EC200A module support + USB: serial: simple: add Kaufmann RKS+CAN VCP + USB: serial: simple: sort driver entries + can: gs_usb: gs_can_close(): add missing set of CAN state to CAN_STATE_STOPPED + Revert "usb: dwc3: core: Enable AutoRetry feature in the controller" + usb: dwc3: pci: skip BYT GPIO lookup table for hardwired phy + usb: dwc3: don't reset device side if dwc3 was configured as host-only + usb: ohci-at91: Fix the unhandle interrupt when resume + USB: quirks: add quirk for Focusrite Scarlett + usb: xhci-mtk: set
[Kernel-packages] [Bug 2038652] [NEW] Focal update: v5.4.253 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.253 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Roxana Nicolescu (roxanan) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Roxana Nicolescu (roxanan) -- 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/2038652 Title: Focal update: v5.4.253 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.253 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038652/+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 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
This bug is awaiting verification that the linux/6.2.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar- linux' to 'verification-failed-lunar-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux -- 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/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Fix Committed Bug description: [Impact] After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. [Fix] Updated patch from linux-next: https://patchwork.freedesktop.org/patch/538562/ [Test Case] Suspend,resume,shutdown,reboot should all work correctly. No nouveau stack trace in the kernel log. [Where Problems Could Occur] Limited to nouveau driver that wants to load nonexistent ACR firmware. Only nvidia GPUs are affected. [Additional information] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031352/+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 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
This bug is awaiting verification that the linux/6.2.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar- linux' to 'verification-failed-lunar-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Status in linux source package in Lunar: Fix Committed Bug description: [Impact] Ethernet is unstable with Realtek RTL8168h/8111h NIC and kernel 6.2 resulting in frequent transmit queue timeouts. Related to ASPM. See 'original description' below. [Test Case] Just regular usage for an extended period of time. No transmit queue timeouts with RTL8168h/8111h NICs. [Where Problems Could Occur] Modification are isolated to the r8169 driver so only machine where that driver is loaded are affected. Issues could show up as kernel crashes, stack traces, non-fnuctional wired network. [Original Description] hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clmulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9
[Kernel-packages] [Bug 2034479] Re: Fix suspend hang on Lenovo workstation
This bug is awaiting verification that the linux/6.2.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar- linux' to 'verification-failed-lunar-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2034479 Title: Fix suspend hang on Lenovo workstation Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Invalid Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The system hang after resume from S3. Error logs: kernel: igb :02:00.0: disabling already-disabled device kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 pci_disable_device+0xc4/0xf0 kernel: RIP: 0010:pci_disable_device+0xc4/0xf0 kernel: Call Trace: kernel: kernel: igb_io_error_detected+0x3e/0x60 kernel: report_error_detected+0xd6/0x1c0 kernel: ? __pfx_report_normal_detected+0x10/0x10 kernel: report_normal_detected+0x16/0x30 kernel: pci_walk_bus+0x74/0xa0 kernel: pcie_do_recovery+0xb9/0x340 kernel: ? __pfx_aer_root_reset+0x10/0x10 kernel: aer_process_err_devices+0x168/0x220 kernel: aer_isr+0x1b5/0x1e0 kernel: ? __pfx_irq_thread_fn+0x10/0x10 kernel: irq_thread_fn+0x21/0x70 kernel: irq_thread+0xf8/0x1c0 kernel: ? __pfx_irq_thread_dtor+0x10/0x10 kernel: ? __pfx_irq_thread+0x10/0x10 kernel: kthread+0xef/0x120 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x29/0x50 kernel: kernel: ---[ end trace ]--- [Fix] The pci io error detected ops is called before the driver resumed. Avoid this race condition to fix the issue. [Test] Tested on hardware, the system suspend/resume OK. [Where problems could occur] It may break igb driver. The commit is included in 6.5-rc1 and merged by stable update in oem-6.1, SRU for Jammy and Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034479/+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 2034491] Re: Fix blank display when Thunderbolt monitor is plugged second time
This bug is awaiting verification that the linux/6.2.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar- linux' to 'verification-failed-lunar-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2034491 Title: Fix blank display when Thunderbolt monitor is plugged second time Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When a Thunderbolt monitor gets plugged to an AMD laptop for second time, the Thunderbolt monitor remains blank. [Fix] Reinitialize TMU and perform proper Time Synchronization Handshake every time. [Test] The Thunderbolt monitor still has image after many replugging. [Where problems could occur] This change the flow on disabling TMU, which is responsible for time synchronization, so behavior of Thunderbolt docking might be affected. Per my limited test no issue has been observed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034491/+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 2034504] Re: Enable ASPM for NVMe behind VMD
This bug is awaiting verification that the linux/6.2.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar- linux' to 'verification-failed-lunar-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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 2035116] Re: allow io_uring to be disabled in runtime
This bug is awaiting verification that the linux/6.2.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar- linux' to 'verification-failed-lunar-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2035116 Title: allow io_uring to be disabled in runtime Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] io_uring has been an important attack vector in the recent years in local privilege escalation attacks. Allowing admins that don't use io_uring to disable it in their systems allows them to reduce their attack surface. [Test case] sysctl -w kernel.io_uring_disabled=1 then try to use io_uring from an unprivileged user, then try it with privileges (CAP_SYS_ADMIN) Actually also tried setting kernel.io_uring_disabled=2 and checking that neither (privileged or unprivileged worked). Then testing setting it back to 0. Then tested with io_uring_disabled set to 1 and io_uring_group=1000 and that it worked for group 1000, then set it to 1001 and verified that it didn't work anymore for group 1000. [Potential regression] Uses can be denied from using io_uring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035116/+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 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
This bug is awaiting verification that the linux/6.2.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar- linux' to 'verification-failed-lunar-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+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 2035163] Re: Avoid address overwrite in kernel_connect
This bug is awaiting verification that the linux/6.2.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar- linux' to 'verification-failed-lunar-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2035163 Title: Avoid address overwrite in kernel_connect Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-gcp source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Released Status in linux-gke source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 Testing: - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. Regression potenial: - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035163/+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 2035181] Re: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
This bug is awaiting verification that the linux/6.2.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar- linux' to 'verification-failed-lunar-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux -- 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/2035181 Title: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Confirmed Bug description: [Impact] Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work with CO-RE") from stable update breaks the ubuntu_bpf test build and cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in ubuntu_kernel_selftests stopped working, as they require bpf selftest to be built first. The following is extracted from the commit message: The problem is the new offsetof() does not play nice with static asserts. Given that the context is a static assert (and CO-RE relocation is not needed at compile time), offsetof() usage can be replaced by restoring the original offsetof() definition as __builtin_offsetof(). [Test Plan] Build bpf selftest in tools/testing/selftests with the following command: make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \ clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/ The build can finish successfully with patched kernel source code. [Where problems could occur] Fix limited to testing tool, if this fix is incorrect the bpf selftest build will remain broken. == Original bug report == Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04 This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84 is a security cycle, in which the ubuntu_bpf test was not triggered there) Test build failed with: CLNG-BPF [test_maps] test_btf_map_in_map.o CLNG-BPF [test_maps] test_btf_newkv.o CLNG-BPF [test_maps] test_btf_nokv.o CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o CLNG-BPF [test_maps] test_cgroup_link.o CLNG-BPF [test_maps] test_check_mtu.o CLNG-BPF [test_maps] test_cls_redirect.o make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from latest version at 'include/uapi/linux/bpf.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs from latest version at 'include/uapi/linux/netlink.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' progs/test_cls_redirect.c:90:2: error: static_assert expression is not an integral constant expression sizeof(flow_ports_t) != ^~~ progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a reinterpret_cast is not allowed in a constant expression offsetofend(struct bpf_sock_tuple, ipv4.dport) - ^ progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend' (offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER))) ^ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33: note: expanded from macro 'offsetof' #define offsetof(type, member) ((unsigned long)&((type *)0)->member) ^ progs/test_cls_redirect.c:95:2: error: static_assert expression is not an integral constant expression sizeof(flow_ports_t) != ^~~ progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a reinterpret_cast is not allowed in a constant expression offsetofend(struct bpf_sock_tuple, ipv6.dport) - ^ progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend' (offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER))) ^ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33: note: expanded from macro 'offsetof'
[Kernel-packages] [Bug 2035313] Re: Fix non-working I219 after system sleep
This bug is awaiting verification that the linux/6.2.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar- linux' to 'verification-failed-lunar-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2035313 Title: Fix non-working I219 after system sleep Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Intel I219 ethernet stops working after system sleep. [Fix] Force resume Intel ME to fix I219. It's not surprising because ME/AMT is controlled through Intel I219. [Test] Use `ping 1.1.1.1` to test if I219 is still alive. With the patch applied, the ethernet can survive several system sleeps. [Where problems could occur] The commit essentially disables direct-complete optimization, so it will make system suspend/resume slightly slower. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2035313/+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 2036377] Re: Fix RCU warning on AMD laptops
This bug is awaiting verification that the linux/6.2.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar- linux' to 'verification-failed-lunar-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2036377 Title: Fix RCU warning on AMD laptops Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Scary kernel splat about RCU can be observed everytime laptop resumes from suspend. [Fix] Use non-atomic notifier for power supply change to relax the constraint. [Test] Once the fix is applied, no more RCU warning can be found after several suspend/resume cycle. [Where problems could occur] Essentially no regression potential. Atomic notifier should be used by core kernel, and things like power supply doesn't need to be atomic anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2036377/+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 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4
This bug is awaiting verification that the linux/6.2.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar- linux' to 'verification-failed-lunar-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2037077 Title: Fix unstable audio at low levels on Thinkpad P1G4 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The audio at low levels is not stable with fluctuating levels. [Fix] Forcibly assign NID 0x03 to HP while NID 0x02 to SPK. [Test] Tested on hardware, the audio output is OK at all levels. [Where problems could occur] It may break audio output on Thinkpad P1G4/5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037077/+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 2011421] Re: TDX azure instances crash during boot because of glibc bug
This bug is awaiting verification that the linux-azure/6.2.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-azure' to 'verification-done-lunar- linux-azure'. If the problem still exists, change the tag 'verification- needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done ** Tags added: kernel-spammed-lunar-linux-azure-v2 verification-needed-lunar-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-fde-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2011421 Title: TDX azure instances crash during boot because of glibc bug Status in glibc package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-fde-6.2 package in Ubuntu: New Status in glibc source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Invalid Status in linux-azure-fde-6.2 source package in Jammy: Fix Released Status in glibc source package in Kinetic: Won't Fix Status in linux-azure source package in Kinetic: Won't Fix Status in linux-azure-fde-6.2 source package in Kinetic: Won't Fix Status in glibc source package in Lunar: Fix Released Status in linux-azure source package in Lunar: Fix Released Status in linux-azure-fde-6.2 source package in Lunar: Fix Released Bug description: [IMPACT] Glibc in jammy and kinetic is affected by the following bug : https://sourceware.org/bugzilla/show_bug.cgi?id=29953 When cpuid reports no information on a shared cache, the x86_non_temporal_threshold will be set to zero, causing memcpy/memset to behave wrong for mid-sized operations. sysdeps/x86/dl-cacheinfo.h indicates that the minimum value must be 0x4040, but this is not enforced for the default value. The issue was reported because jammy tdx instances are failing to boot (crashing) on azure. The bug has been resolved upstream in https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b [TEST CASE] Test case requires an azure tdx instance. Microsoft has tested a test package with the above commit and confirmed that instances boot successfully. [REGRESSION POTENTIAL] The patches have been accepted upstream. They modify code for x86 architecture, so any potential regression would affect x86. [OTHER] Bug upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=29953 Duplicate bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30037 In jammy we need 2 commits : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b446822b6ae4e8149902a78cdd4a886634ad6321 https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b In kinetic we just need : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2011421/+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 2021572] Re: dGPU cannot resume because system firmware stuck in IPCS method
This bug is awaiting verification that the linux-azure/6.2.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-azure' to 'verification-done-lunar- linux-azure'. If the problem still exists, change the tag 'verification- needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-azure-v2 verification-needed-lunar-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2021572 Title: dGPU cannot resume because system firmware stuck in IPCS method Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When a dGPU on a laptop is in PCIe D3cold and TBT port is connected to a monitor via a cable, unplugging the cable will make the dGPU unable to resume to D0. [Fix] There's a part of system firmware, IOM, need the driver to disconnect all TBT/Type-C phy to let dGPU function normally. [Test] With the fix applied, the dGPU continues to work after replugging video cable many times. [Where problems could occur] The fix is composed of several overhaul, so it's likely to regression i915 GFX driver. To limit the impact, only target OEM kernel for now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2021572/+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