[Kernel-packages] [Bug 2034636] Re: Error while updating linux-intel-iotg-tools-common
** Summary changed: - While running Updates in Discover on Ubuntu Studio 22.04, an error occures about overwiting acpidbg file + Error while updating linux-intel-iotg-tools-common -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2034636 Title: Error while updating linux-intel-iotg-tools-common Status in linux-intel-iotg package in Ubuntu: New Bug description: Error while installing package: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-83.92 The linux-intel-iotg-tools-common update fails. I am able to continue normally. I have looked at previous similarly reported bugs, most involve different versions of Kernel, linux-intel-iotg-tools-common or linux- tools-common. None appear to have a resolution. 1) lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 2) apt-cache policy linux-intel-iotg-tools-common linux-intel-iotg-tools-common: Installed: 5.15.0-1037.42 Candidate: 5.15.0-1038.43 Version table: 5.15.0-1038.43 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages *** 5.15.0-1037.42 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 100 /var/lib/dpkg/status 5.15.0-1036.41 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1035.40 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 5.15.0-1034.39 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1033.38 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1031.36 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1030.35 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1028.33 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1004.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages 3) I expected the update to complete successfully. 4) The update failed with an error. ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-83.92-lowlatency 5.15.116 Uname: Linux 5.15.0-83-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 6 21:47:28 2023 InstallationDate: Installed on 2022-10-03 (338 days ago) InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Release amd64
[Kernel-packages] [Bug 2032767] Re: Fix ACPI TAD on some Intel based systems
** Tags removed: verification-needed-jammy-linux-oem-6.5 verification-needed-lunar-linux ** Tags added: verification-done-jammy-linux-oem-6.5 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/2032767 Title: Fix ACPI TAD on some Intel based systems 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-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 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: Confirmed 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 2032704] Re: Fix panel brightness issues on HP laptops
** Tags removed: verification-needed-lunar-linux ** Tags added: 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/2032704 Title: Fix panel brightness issues on HP laptops 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-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 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: Confirmed 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 2028122] Re: Fix unreliable ethernet cable detection on I219 NIC
** 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/2028122 Title: Fix unreliable ethernet cable detection on I219 NIC 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 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] 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 2026322] Re: Fix non-working MT7921e when pre-boot WiFi is enabled
** Tags removed: verification-needed-lunar-linux ** Tags added: 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/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 Committed 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 2021572] Re: dGPU cannot resume because system firmware stuck in IPCS method
** Tags removed: verification-needed-lunar-linux ** Tags added: 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/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 Committed 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 2034646] [NEW] warm-boot-loop-test24
Public bug reported: Model Name: MVP-6200 scope: ## Dumping the devices information to /var/tmp/checkbox-ng/sessions/session_title-2023-09-05T06.56.19.session/session-share/warm_reboot_cycle24... Gathering information about PCI devices (lspci)... Gathering information about WiFi connections (iw)... Gathering information about USB devices (lsusb)... dump devices complete ## Checking if support fwts... FWTS supported ## Running FWTS of test: klog oops... Test: Scan kernel log for errors and warnings. : 0.0% / Kernel log error check.: 0.0% - Kernel log error check.: 50.0% \ Kernel log error check. Test: Scan kernel log for Oopses. : 50.0% | Kernel log oops check. : 50.0% / Kernel log oops check. : 100.0% - Kernel log oops check. 2 passed Running 2 tests, results appended to /var/tmp/checkbox-ng/sessions/session_title-2023-09-05T06.56.19.session/session-share/warm_reboot_cycle24/fwts_klog_oops.log ## Checking FWTS log failures... No errors detected ## Comparing the devices... --- /var/tmp/checkbox-ng/sessions/session_title-2023-09-05T06.56.19.session/session-share/before_reboot/lsusb_log 2023-09-05 16:32:35.427809910 +0800 +++ /var/tmp/checkbox-ng/sessions/session_title-2023-09-05T06.56.19.session/session-share/warm_reboot_cycle24/lsusb_log 2023-09-05 17:46:28.648000706 +0800 @@ -1,2 +1,3 @@ +ID 046d:c52b Logitech USB Receiver ID 1d6b:0002 Linux Foundation 2.00 root hub ID 1d6b:0003 Linux Foundation 3.10 root hub The list of USB devices (lsusb) is different from the original list gathered at the beginning of the session! ## Checking system services... Found 0 failed units ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2034646 Title: warm-boot-loop-test24 Status in linux-intel-iotg package in Ubuntu: New Bug description: Model Name: MVP-6200 scope: ## Dumping the devices information to /var/tmp/checkbox-ng/sessions/session_title-2023-09-05T06.56.19.session/session-share/warm_reboot_cycle24... Gathering information about PCI devices (lspci)... Gathering information about WiFi connections (iw)... Gathering information about USB devices (lsusb)... dump devices complete ## Checking if support fwts... FWTS supported ## Running FWTS of test: klog oops... Test: Scan kernel log for errors and warnings. : 0.0% / Kernel log error check.: 0.0% - Kernel log error check.: 50.0% \ Kernel log error check. Test: Scan kernel log for Oopses. : 50.0% | Kernel log oops check. : 50.0% / Kernel log oops check. : 100.0% - Kernel log oops check. 2 passed Running 2 tests, results appended to /var/tmp/checkbox-ng/sessions/session_title-2023-09-05T06.56.19.session/session-share/warm_reboot_cycle24/fwts_klog_oops.log ## Checking FWTS log failures... No errors detected ## Comparing the devices... --- /var/tmp/checkbox-ng/sessions/session_title-2023-09-05T06.56.19.session/session-share/before_reboot/lsusb_log 2023-09-05 16:32:35.427809910 +0800 +++ /var/tmp/checkbox-ng/sessions/session_title-2023-09-05T06.56.19.session/session-share/warm_reboot_cycle24/lsusb_log 2023-09-05 17:46:28.648000706 +0800 @@ -1,2 +1,3 @@ +ID 046d:c52b Logitech USB Receiver ID 1d6b:0002 Linux Foundation 2.00 root hub ID 1d6b:0003 Linux Foundation 3.10 root hub The list of USB devices (lsusb) is different from the original list gathered at the beginning of the session! ## Checking system services... Found 0 failed units To manage notifications about this bug go to:
[Kernel-packages] [Bug 2034646] Re: warm-boot-loop-test24
Warm boot system configuration test 24 ** Attachment added: "submission_2023-09-07T00.51.23.751999.html" https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2034646/+attachment/5698123/+files/submission_2023-09-07T00.51.23.751999.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2034646 Title: warm-boot-loop-test24 Status in linux-intel-iotg package in Ubuntu: New Bug description: Model Name: MVP-6200 scope: ## Dumping the devices information to /var/tmp/checkbox-ng/sessions/session_title-2023-09-05T06.56.19.session/session-share/warm_reboot_cycle24... Gathering information about PCI devices (lspci)... Gathering information about WiFi connections (iw)... Gathering information about USB devices (lsusb)... dump devices complete ## Checking if support fwts... FWTS supported ## Running FWTS of test: klog oops... Test: Scan kernel log for errors and warnings. : 0.0% / Kernel log error check.: 0.0% - Kernel log error check.: 50.0% \ Kernel log error check. Test: Scan kernel log for Oopses. : 50.0% | Kernel log oops check. : 50.0% / Kernel log oops check. : 100.0% - Kernel log oops check. 2 passed Running 2 tests, results appended to /var/tmp/checkbox-ng/sessions/session_title-2023-09-05T06.56.19.session/session-share/warm_reboot_cycle24/fwts_klog_oops.log ## Checking FWTS log failures... No errors detected ## Comparing the devices... --- /var/tmp/checkbox-ng/sessions/session_title-2023-09-05T06.56.19.session/session-share/before_reboot/lsusb_log 2023-09-05 16:32:35.427809910 +0800 +++ /var/tmp/checkbox-ng/sessions/session_title-2023-09-05T06.56.19.session/session-share/warm_reboot_cycle24/lsusb_log 2023-09-05 17:46:28.648000706 +0800 @@ -1,2 +1,3 @@ +ID 046d:c52b Logitech USB Receiver ID 1d6b:0002 Linux Foundation 2.00 root hub ID 1d6b:0003 Linux Foundation 3.10 root hub The list of USB devices (lsusb) is different from the original list gathered at the beginning of the session! ## Checking system services... Found 0 failed units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2034646/+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 2034645] [NEW] suspend/1_xrandr_screens_after_suspend.tar.gz_auto
Public bug reported: Model Name: MVP-6200 suspend/1_xrandr_screens_after_suspend.tar.gz_auto ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "submission_2023-09-05T06.08.46.393631.html" https://bugs.launchpad.net/bugs/2034645/+attachment/5698121/+files/submission_2023-09-05T06.08.46.393631.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2034645 Title: suspend/1_xrandr_screens_after_suspend.tar.gz_auto Status in linux-intel-iotg package in Ubuntu: New Bug description: Model Name: MVP-6200 suspend/1_xrandr_screens_after_suspend.tar.gz_auto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2034645/+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 2034636] [NEW] While running Updates in Discover on Ubuntu Studio 22.04, an error occures about overwiting acpidbg file
Public bug reported: Error while installing package: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-83.92 The linux-intel-iotg-tools-common update fails. I am able to continue normally. I have looked at previous similarly reported bugs, most involve different versions of Kernel, linux-intel-iotg-tools-common or linux- tools-common. None appear to have a resolution. 1) lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 2) apt-cache policy linux-intel-iotg-tools-common linux-intel-iotg-tools-common: Installed: 5.15.0-1037.42 Candidate: 5.15.0-1038.43 Version table: 5.15.0-1038.43 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages *** 5.15.0-1037.42 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 100 /var/lib/dpkg/status 5.15.0-1036.41 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1035.40 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 5.15.0-1034.39 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1033.38 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1031.36 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1030.35 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1028.33 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1004.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages 3) I expected the update to complete successfully. 4) The update failed with an error. ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-83.92-lowlatency 5.15.116 Uname: Linux 5.15.0-83-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 6 21:47:28 2023 InstallationDate: Installed on 2022-10-03 (338 days ago) InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: linux-intel-iotg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2034636 Title: While running Updates in Discover on Ubuntu Studio 22.04, an error occures about overwiting acpidbg file Status in linux-intel-iotg package in Ubuntu: New Bug description: Error while installing package: trying
[Kernel-packages] [Bug 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
@juergh, it appears that this bug isn't exclusive to the "Nouveau" driver. I'm using the Nvidia proprietary driver and I am experiencing the same issue. -- 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: Confirmed 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 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
Unfortunately, the bug happened today with me, again. See the attached log using: journalctl -b -1 --since "1 hour ago". I use: - Kernel: 6.2.0-32-generic #32~22.04.1-Ubuntu - NVIDIA Driver Version: 535.86.05 ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352/+attachment/5698102/+files/journalctl.txt -- 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: Confirmed 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 2034622] [NEW] NVIDIA pull requests 2023-09-04
Public bug reported: Apply patches from NVIDIA pull request sent on 2023-09-04 to jammy:linux-nvidia-tegra. 2023-09-04: Andy Sobczyk (1): NVIDIA: SAUCE: arm64: config: Changes to build for Flashing kernel Vishwaroop A (1): NVIDIA: SAUCE: spi: spi-tegra114: retain the spi mode Mohan Kumar (1): NVIDIA: SAUCE: arm64: config: enable HDA_INTEL config Kartik (1): NVIDIA: SAUCE: mailbox: tegra-hsp: Add sm ops route_irq & set_irq raju patel (1): NVIDIA: SAUCE: code-owners: Populate OWNERS file Laxman Dewangan (1): NVIDIA: SAUCE: arm64: config: Disable CONFIG_LOCALVERSION_AUTO Sumit Gupta (1): NVIDIA: SAUCE: driver: cpufreq: remove volatile as not needed --- ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2034622 Title: NVIDIA pull requests 2023-09-04 Status in linux-nvidia-tegra package in Ubuntu: New Bug description: Apply patches from NVIDIA pull request sent on 2023-09-04 to jammy:linux-nvidia-tegra. 2023-09-04: Andy Sobczyk (1): NVIDIA: SAUCE: arm64: config: Changes to build for Flashing kernel Vishwaroop A (1): NVIDIA: SAUCE: spi: spi-tegra114: retain the spi mode Mohan Kumar (1): NVIDIA: SAUCE: arm64: config: enable HDA_INTEL config Kartik (1): NVIDIA: SAUCE: mailbox: tegra-hsp: Add sm ops route_irq & set_irq raju patel (1): NVIDIA: SAUCE: code-owners: Populate OWNERS file Laxman Dewangan (1): NVIDIA: SAUCE: arm64: config: Disable CONFIG_LOCALVERSION_AUTO Sumit Gupta (1): NVIDIA: SAUCE: driver: cpufreq: remove volatile as not needed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2034622/+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 2034506] Re: Audio device fails to function randomly on Intel MTL platform: No CPC match in the firmware file's manifest
SRU:
* http://10.131.201.69/kernel/jammy-linux-oem/pulls/62 (oem-6.5)
* https://lists.ubuntu.com/archives/kernel-team/2023-September/142547.html
(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/2034506
Title:
Audio device fails to function randomly on Intel MTL platform: No CPC
match in the firmware file's manifest
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2034506
[Impact]
Audio device fails to function randomly on Intel MTL platform:
```
sof-audio-pci-intel-mtl :00:1f.3: no llp found, fall back to default HDA
path
sof-audio-pci-intel-mtl :00:1f.3: COPIER (UUID:
9BA00C83-CA12-4A83-943C-1FA2E82F9DDA): No CPC match in the firmware file's
manifest (ibs/obs: 384/192)
```
[Fix]
Proposed fix in upstream commit 26ef47e5ba60 ("ASoC: SOF:
ipc4-topology: Add module parameter to ignore the CPC value") that to
allow ignoring CPC validation for current fw release.
[Test Case]
1. Boot into OS
2. Check if the internal audio input & output devices work
3. Let system enter suspend, then wake system back up
4. Check if the audio input & output devices work
5. Connect an external audio device (e.g. bluetooth headset, external
monitor) and check if they work
6. Disconnect the external audio device
7. Check if the internal audio input & output devices work
8. Reboot system
9. Repeat above steps
[Where problems could occur]
While a 0 CPC value will force the DSP to run at full speed, this is
going to impact power consumption until further fix being released for
firmware.
[Other Info]
CPC checking landed to v6.5-rc1, so Mantic and oem-6.5 are nominated
for fix.
== original bug report ==
sof-audio-pci-intel-mtl :00:1f.3: no llp found, fall back to default HDA
path
sof-audio-pci-intel-mtl :00:1f.3: COPIER (UUID:
9BA00C83-CA12-4A83-943C-1FA2E82F9DDA): No CPC match in the firmware file's
manifest (ibs/obs: 384/192)
Proposed fix in upstream commit 26ef47e5ba60 ("ASoC: SOF:
ipc4-topology: Add module parameter to ignore the CPC value") that to
allow ignoring CPC validation for current fw release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2034506/+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 2034506] Re: Audio device fails to function randomly on Intel MTL platform: No CPC match in the firmware file's manifest
** Description changed:
+ [SRU Justification]
+
+ BugLink: https://bugs.launchpad.net/bugs/2034506
+
+ [Impact]
+
+ Audio device fails to function randomly on Intel MTL platform:
+ ```
+ sof-audio-pci-intel-mtl :00:1f.3: no llp found, fall back to default HDA
path
+ sof-audio-pci-intel-mtl :00:1f.3: COPIER (UUID:
9BA00C83-CA12-4A83-943C-1FA2E82F9DDA): No CPC match in the firmware file's
manifest (ibs/obs: 384/192)
+ ```
+
+ [Fix]
+
+ Proposed fix in upstream commit 26ef47e5ba60 ("ASoC: SOF: ipc4-topology:
+ Add module parameter to ignore the CPC value") that to allow ignoring
+ CPC validation for current fw release.
+
+ [Test Case]
+
+ 1. Boot into OS
+ 2. Check if the internal audio input & output devices work
+ 3. Let system enter suspend, then wake system back up
+ 4. Check if the audio input & output devices work
+ 5. Connect an external audio device (e.g. bluetooth headset, external
monitor) and check if they work
+ 6. Disconnect the external audio device
+ 7. Check if the internal audio input & output devices work
+ 8. Reboot system
+ 9. Repeat above steps
+
+ [Where problems could occur]
+
+ While a 0 CPC value will force the DSP to run at full speed, this is
+ going to impact power consumption until further fix being released for
+ firmware.
+
+ [Other Info]
+
+ CPC checking landed to v6.5-rc1, so Mantic and oem-6.5 are nominated for
+ fix.
+
+ == original bug report ==
+
sof-audio-pci-intel-mtl :00:1f.3: no llp found, fall back to default HDA
path
sof-audio-pci-intel-mtl :00:1f.3: COPIER (UUID:
9BA00C83-CA12-4A83-943C-1FA2E82F9DDA): No CPC match in the firmware file's
manifest (ibs/obs: 384/192)
Proposed fix in upstream commit 26ef47e5ba60 ("ASoC: SOF: ipc4-topology:
Add module parameter to ignore the CPC value") that to allow ignoring
CPC validation for current fw release.
--
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/2034506
Title:
Audio device fails to function randomly on Intel MTL platform: No CPC
match in the firmware file's manifest
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2034506
[Impact]
Audio device fails to function randomly on Intel MTL platform:
```
sof-audio-pci-intel-mtl :00:1f.3: no llp found, fall back to default HDA
path
sof-audio-pci-intel-mtl :00:1f.3: COPIER (UUID:
9BA00C83-CA12-4A83-943C-1FA2E82F9DDA): No CPC match in the firmware file's
manifest (ibs/obs: 384/192)
```
[Fix]
Proposed fix in upstream commit 26ef47e5ba60 ("ASoC: SOF:
ipc4-topology: Add module parameter to ignore the CPC value") that to
allow ignoring CPC validation for current fw release.
[Test Case]
1. Boot into OS
2. Check if the internal audio input & output devices work
3. Let system enter suspend, then wake system back up
4. Check if the audio input & output devices work
5. Connect an external audio device (e.g. bluetooth headset, external
monitor) and check if they work
6. Disconnect the external audio device
7. Check if the internal audio input & output devices work
8. Reboot system
9. Repeat above steps
[Where problems could occur]
While a 0 CPC value will force the DSP to run at full speed, this is
going to impact power consumption until further fix being released for
firmware.
[Other Info]
CPC checking landed to v6.5-rc1, so Mantic and oem-6.5 are nominated
for fix.
== original bug report ==
sof-audio-pci-intel-mtl :00:1f.3: no llp found, fall back to default HDA
path
sof-audio-pci-intel-mtl :00:1f.3: COPIER (UUID:
9BA00C83-CA12-4A83-943C-1FA2E82F9DDA): No CPC match in the firmware file's
manifest (ibs/obs: 384/192)
Proposed fix in upstream commit 26ef47e5ba60 ("ASoC: SOF:
ipc4-topology: Add module parameter to ignore the CPC value") that to
allow ignoring CPC validation for current fw release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2034506/+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 2033455] Re: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202
SRU: * http://10.131.201.69/kernel/jammy-linux-oem/pulls/61 (oem-6.5) * https://lists.ubuntu.com/archives/kernel-team/2023-September/142545.html (mantic) -- 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/2033455 Title: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Incomplete Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Incomplete Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-firmware source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2033455 [Impact] Missing BT IDs for support for Intel Discrete Misty Peak2/BE202. [Fix] Bluetooth: a. kernel driver: - https://lore.kernel.org/linux-bluetooth/20230829124024.40592-1-vijay.sat...@intel.com/T/#t - Also depends on patches for Gale Peak(BE200) from bug 2028065. b. firmware (shared with Gale Peak, to be released): - intel/ibt-0191-0191.sfi - intel/ibt-0191-0191.ddc [Test Case] To boot with patched kernel and prereleased firmware blob and check basic Bluetooth functions. [Where problems could occur] New device. Expect incomplete functions and bugs. [Other Info] Targets 6.5 kernels, so only nominated for Mantic and oem-6.5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033455/+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 2033455] Re: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202
** Description changed: + [SRU Justification] + + BugLink: https://bugs.launchpad.net/bugs/2033455 + [Impact] + + Missing BT IDs for support for Intel Discrete Misty Peak2/BE202. [Fix] + Bluetooth: + a. kernel driver: +- https://lore.kernel.org/linux-bluetooth/20230829124024.40592-1-vijay.sat...@intel.com/T/#t +- Also depends on patches for Gale Peak(BE200) from bug 2028065. + b. firmware (shared with Gale Peak, to be released): +- intel/ibt-0191-0191.sfi +- intel/ibt-0191-0191.ddc + [Test Case] + To boot with patched kernel and prereleased firmware blob and check + basic Bluetooth functions. + [Where problems could occur] + + New device. Expect incomplete functions and bugs. + + [Other Info] + + Targets 6.5 kernels, so only nominated for Mantic and oem-6.5. -- 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/2033455 Title: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Incomplete Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Incomplete Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-firmware source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2033455 [Impact] Missing BT IDs for support for Intel Discrete Misty Peak2/BE202. [Fix] Bluetooth: a. kernel driver: - https://lore.kernel.org/linux-bluetooth/20230829124024.40592-1-vijay.sat...@intel.com/T/#t - Also depends on patches for Gale Peak(BE200) from bug 2028065. b. firmware (shared with Gale Peak, to be released): - intel/ibt-0191-0191.sfi - intel/ibt-0191-0191.ddc [Test Case] To boot with patched kernel and prereleased firmware blob and check basic Bluetooth functions. [Where problems could occur] New device. Expect incomplete functions and bugs. [Other Info] Targets 6.5 kernels, so only nominated for Mantic and oem-6.5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033455/+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 2033455] Re: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu Mantic) Status: New => Incomplete -- 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/2033455 Title: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Incomplete Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Incomplete Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-firmware source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2033455 [Impact] Missing BT IDs for support for Intel Discrete Misty Peak2/BE202. [Fix] Bluetooth: a. kernel driver: - https://lore.kernel.org/linux-bluetooth/20230829124024.40592-1-vijay.sat...@intel.com/T/#t - Also depends on patches for Gale Peak(BE200) from bug 2028065. b. firmware (shared with Gale Peak, to be released): - intel/ibt-0191-0191.sfi - intel/ibt-0191-0191.ddc [Test Case] To boot with patched kernel and prereleased firmware blob and check basic Bluetooth functions. [Where problems could occur] New device. Expect incomplete functions and bugs. [Other Info] Targets 6.5 kernels, so only nominated for Mantic and oem-6.5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033455/+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 2034612] [NEW] Jammy update: v5.15.123 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.15.123 upstream stable release from git://git.kernel.org/ ALSA: hda/realtek - remove 3k pull low procedure ALSA: hda/realtek: Add quirk for Clevo NS70AU ALSA: hda/realtek: Enable Mute LED on HP Laptop 15s-eq2xxx keys: Fix linking a duplicate key to a keyring's assoc_array perf probe: Add test for regression introduced by switch to die_get_decl_file() btrfs: fix warning when putting transaction with qgroups enabled after abort fuse: revalidate: don't invalidate if interrupted btrfs: zoned: fix memory leak after finding block group with super blocks fuse: ioctl: translate ENOSYS in outarg selftests: tc: set timeout to 15 minutes selftests: tc: add 'ct' action kconfig dep regmap: Drop initial version of maximum transfer length fixes regmap: Account for register length in SMBus I/O limits can: bcm: Fix UAF in bcm_proc_show() selftests: tc: add ConnTrack procfs kconfig drm/client: Fix memory leak in drm_client_target_cloned drm/client: Fix memory leak in drm_client_modeset_probe drm/amd/display: Disable MPC split by default on special asic drm/amd/display: Keep PHY active for DP displays on DCN31 ASoC: fsl_sai: Disable bit clock with transmitter ASoC: codecs: wcd938x: fix missing clsh ctrl error handling ASoC: codecs: wcd-mbhc-v2: fix resource leaks on component remove ASoC: codecs: wcd938x: fix resource leaks on component remove ASoC: codecs: wcd938x: fix missing mbhc init error handling ASoC: codecs: wcd934x: fix resource leaks on component remove ASoC: codecs: wcd938x: fix codec initialisation race ASoC: codecs: wcd938x: fix soundwire initialisation race ext4: correct inline offset when handling xattrs in inode body drm/radeon: Fix integer overflow in radeon_cs_parser_init ALSA: emu10k1: roll up loops in DSP setup code for Audigy quota: Properly disable quotas when add_dquot_ref() fails quota: fix warning in dqgrab() udf: Fix uninitialized array access for some pathnames fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev MIPS: dec: prom: Address -Warray-bounds warning FS: JFS: Fix null-ptr-deref Read in txBegin FS: JFS: Check for read-only mounted filesystem in txBegin spi: bcm63xx: fix max prepend length fbdev: imxfb: warn about invalid left/right margin perf build: Fix library not found error when using CSLIBS pinctrl: amd: Use amd_pinconf_set() for all config options net: ethernet: ti: cpsw_ale: Fix cpsw_ale_get_field()/cpsw_ale_set_field() bridge: Add extack warning when enabling STP in netns. ethernet: use eth_hw_addr_set() instead of ether_addr_copy() of: net: add a helper for loading netdev->dev_addr ethernet: use of_get_ethdev_address() net: ethernet: mtk_eth_soc: handle probe deferral net: sched: cls_bpf: Undo tcf_bind_filter in case of an error iavf: Fix use-after-free in free_netdev iavf: Fix out-of-bounds when setting channels on remove security: keys: Modify mismatched function name octeontx2-pf: Dont allocate BPIDs for LBK interfaces bpf: Fix subprog idx logic in check_max_stack_depth igc: Prevent garbled TX queue with XDP ZEROCOPY tcp: annotate data-races around tcp_rsk(req)->ts_recent net: ipv4: Use kfree_sensitive instead of kfree net:ipv6: check return value of pskb_trim() Revert "tcp: avoid the lookup process failing to get sk in ehash table" fbdev: au1200fb: Fix missing IRQ check in au1200fb_drv_probe llc: Don't drop packet from non-root netns. netfilter: nf_tables: fix spurious set element insertion failure netfilter: nf_tables: skip bound chain in netns release path tcp: annotate data-races around tp->tcp_tx_delay tcp: annotate data-races around tp->keepalive_time tcp: annotate data-races around tp->keepalive_intvl tcp: annotate data-races around tp->keepalive_probes tcp: annotate data-races around icsk->icsk_syn_retries tcp: annotate data-races around tp->linger2 tcp: annotate data-races around rskq_defer_accept tcp: annotate data-races around tp->notsent_lowat tcp: annotate data-races around icsk->icsk_user_timeout tcp: annotate data-races around fastopenq.max_qlen net: phy: prevent stale pointer dereference in phy_init() jbd2: recheck chechpointing non-dirty buffer tracing/histograms: Return an error if we fail to add histogram to hist_vars list nixge: fix mac address error handling again Linux 5.15.123 UBUNTU: Upstream stable to v5.15.123 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug **
[Kernel-packages] [Bug 2028065] Re: Support for Intel Discrete Gale Peak2/BE200
SRU:
* http://10.131.201.69/kernel/jammy-linux-oem/pulls/42 (oem-6.5)
* https://lists.ubuntu.com/archives/kernel-team/2023-September/142541.html
(mantic)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ Missing Intel Gale Peak WiFi/Bluetooth support.
+
+ [Fix]
+
+ WIFI:
+ a. kernel driver :
+- commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
+ crash") [v6.5-rc2]
+ b. firmware (to be released):
+- iwlwifi-gl-b0-fm-b0-83.ucode
+- iwlwifi-gl-b0-fm-b0.pnvm
+
+ Bluetooth:
+ a. kernel driver:
+- commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
+- commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
+ b. firmware (to be released):
+- intel/ibt-0191-0191.sfi
+- intel/ibt-0191-0191.ddc
+
+ [Test Case]
+
+ To boot with patched kernel and prereleased firmware blob and check basic
+ WiFi/Bluetooth functions.
+
+ [Where problems could occur]
+
+ New device. Expect incomplete functions and bugs.
+
+ [Other Info]
+
+ Targets 6.5 kernels, so only nominated for Mantic and oem-6.5.
+
+ = original bug report ==
+
WIFI:
a. kernel driver :
- commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
crash") [v6.5-rc2]
b. firmware (to be released):
- iwlwifi-gl-b0-fm-b0-83.ucode
- iwlwifi-gl-b0-fm-b0.pnvm
Bluetooth:
a. kernel driver:
- commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
- commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
b. firmware (to be released):
- intel/ibt-0191-0191.sfi
- intel/ibt-0191-0191.ddc
--
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/2028065
Title:
Support for Intel Discrete Gale Peak2/BE200
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Incomplete
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Incomplete
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-firmware source package in Mantic:
Incomplete
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Intel Gale Peak WiFi/Bluetooth support.
[Fix]
WIFI:
a. kernel driver :
- commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
crash") [v6.5-rc2]
b. firmware (to be released):
- iwlwifi-gl-b0-fm-b0-83.ucode
- iwlwifi-gl-b0-fm-b0.pnvm
Bluetooth:
a. kernel driver:
- commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
- commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
b. firmware (to be released):
- intel/ibt-0191-0191.sfi
- intel/ibt-0191-0191.ddc
[Test Case]
To boot with patched kernel and prereleased firmware blob and check basic
WiFi/Bluetooth functions.
[Where problems could occur]
New device. Expect incomplete functions and bugs.
[Other Info]
Targets 6.5 kernels, so only nominated for Mantic and oem-6.5.
= original bug report ==
WIFI:
a. kernel driver :
- commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
crash") [v6.5-rc2]
b. firmware (to be released):
- iwlwifi-gl-b0-fm-b0-83.ucode
- iwlwifi-gl-b0-fm-b0.pnvm
Bluetooth:
a. kernel driver:
- commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
- commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
b. firmware (to be released):
- intel/ibt-0191-0191.sfi
- intel/ibt-0191-0191.ddc
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2028065/+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 2028065] Re: Support for Intel Discrete Gale Peak2/BE200
** Description changed:
- [WiFi]
-
WIFI:
a. kernel driver :
-- commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
crash") [v6.5-rc2]
+ - commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
crash") [v6.5-rc2]
b. firmware (to be released):
- iwlwifi-gl-b0-fm-b0-83.ucode
- iwlwifi-gl-b0-fm-b0.pnvm
- [Bluetooth]
-
+ Bluetooth:
a. kernel driver:
-- commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
[linux-next]
-- commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
[linux-next]
+ - commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
+ - commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
b. firmware (to be released):
-- intel/ibt-0191-0191.sfi
-- intel/ibt-0191-0191.ddc
+ - intel/ibt-0191-0191.sfi
+ - intel/ibt-0191-0191.ddc
--
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/2028065
Title:
Support for Intel Discrete Gale Peak2/BE200
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Incomplete
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Incomplete
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-firmware source package in Mantic:
Incomplete
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
WIFI:
a. kernel driver :
- commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
crash") [v6.5-rc2]
b. firmware (to be released):
- iwlwifi-gl-b0-fm-b0-83.ucode
- iwlwifi-gl-b0-fm-b0.pnvm
Bluetooth:
a. kernel driver:
- commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
- commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
b. firmware (to be released):
- intel/ibt-0191-0191.sfi
- intel/ibt-0191-0191.ddc
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2028065/+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 2034607] Re: Bus error after reading or writing a specific number of unique locations from/to a shared memory pool.
Even though this was tried with two different gcc versions, I just
installed clang version 17.0.0 and compiled the test program. The Bus
Error issue is the same with the clang compiled program.
--
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/2034607
Title:
Bus error after reading or writing a specific number of unique
locations from/to a shared memory pool.
Status in linux package in Ubuntu:
Confirmed
Bug description:
A Bus error always occurs after reading or writing a specific number
of unique locations from/to a shared memory pool which is created
using shm_open() and mmap(). It does not matter if the pool memory
locations are accessed starting at the base of the pool, incrementing
up through the addresses, or starting at the top of the pool,
decrementing down through the addresses. The count of unique locations
accessed before the Bus error occurs is the same repeatable value. The
count value is close to but not exactly 1/2 of the total system
memory.
The count is of unique locations accessed. If an address range less
than the failure count is accessed repeatedly, the Bus error does not
occur.
The unique addresses do not have to be accessed sequentially to cause
the Bus error. While this aspect has not been tested exhaustively, if
a range of addresses are jumped over, the Bus error still occurs. Note
that the failure count is slightly different than if the addresses are
accessed sequentially.
This error is consistently repeatable on the following 3 systems:
Ubuntu 22.04.3 LTS
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Amazon EC2
CPU: AMD EPYC 7571
Memory: 124.68 GiB
Distro: Linux Mint 20 base: Ubuntu 20.04
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04)
Machine: Dell System XPS L502X
CPU: Intel Core i7-2620M
Total Memory: 8,219,435,008 bytes
Distro: Linux Mint 21 base: Ubuntu 22.04
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Dell Inspiron 5558
CPU: Intel Core i3-5005U
Total Memory: 8,229,298,176 bytes
C++ Test program that demonstrates the issue.
-
// September 2023 - Gene Weber
// This test program generates a Bus error core dump after reading or writing
a specific number
// of unique locations from/to a shared memory pool. It does not matter if
the pool memory locations
// are accessed starting at the base of the pool, incrementing up through the
addresses, or starting
// at the top of the pool, decrementing down through the addresses. The count
of unique locations
// accessed before the Bus error occurs is the same repeatable value. The
count value is close to
// but not exactly 1/2 of the total system memory.
//
// The count is of unique locations accessed. If an address range less than
the failure count is
// accessed repeatedly, the Bus error does not occur.
//
// The unique addresses do not have to be accessed sequentially to cause the
Bus error. While this
// has not been tested exhaustively, if a range of addresses are jumped over,
the Bus error still
// occurs. Note that the failure count is slightly different than if the
addresses are accessed
// sequentially.
//
// This test program has command line options to allow testing these
different scenarios.
// Compiling with either has the same results:
// g++ -std=c++11 test.cpp -W -Wall -Wextra -pedantic -pthread -o test -lrt
// g++ -std=c++20 -O3 test.cpp -W -Wall -Wextra -pedantic -pthread -o test
-lrt
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char** argv) {
int page_size = 4096;
if (argc != 5) {
std::cerr << "\nUsage: ./test
\n\n";
std::cerr << "= total from \"free
-b\".\n";
std::cerr << "= u to index addresses up from bottom of
pool, d for down from top.\n";
std::cerr << "= r to read indexed address, w for
write.\n";
std::cerr << "= j for jump index by 5% of total, r for
limit index range to 1/2 of total, x linear indexing.\n\n";
exit(EXIT_FAILURE);
}
uint_fast64_t total_system_ram = strtoull(argv[1], NULL, 10);
// Set pool_size to a whole number of pages that is ~60% of system memory.
uint_fast64_t pool_size = total_system_ram * 0.6;
pool_size = pool_size - (pool_size % page_size);
std::cout << "pool size = " << pool_size << "\n";
// Create a mask to print status at intervals of ~1/20 of the pool size.
uint_fast64_t print_interval = pow(2,ceil(log2(pool_size/20))) - 1;
// Create a value to start printing all addresses after a few pages less
than
// 1/2 of the pool size has been accessed.
uint_fast64_t almost_half = (total_system_ram/2) - (3 * page_size);
//
[Kernel-packages] [Bug 2030891] Re: In normal PC use, Nvidia crashes, laptop locks up
Eyl 06 21:50:57 oleymod NetworkManager[1760]: [1694026257.4732] device (wlp3s0): supplicant interface state: inactive -> scanning Eyl 06 21:50:57 oleymod NetworkManager[1760]: [1694026257.9281] device (wlp3s0): supplicant interface state: scanning -> inactive Eyl 06 21:50:59 oleymod NetworkManager[1760]: [1694026259.4248] device (wlp3s0): supplicant interface state: inactive -> scanning Eyl 06 21:50:59 oleymod NetworkManager[1760]: [1694026259.8757] device (wlp3s0): supplicant interface state: scanning -> inactive Eyl 06 21:51:01 oleymod NetworkManager[1760]: [1694026261.4236] device (wlp3s0): supplicant interface state: inactive -> scanning Eyl 06 21:51:01 oleymod NetworkManager[1760]: [1694026261.8820] device (wlp3s0): supplicant interface state: scanning -> inactive Eyl 06 21:51:12 oleymod gnome-shell[70364]: [0906/215112.732100:ERROR:file_io_posix.cc(152)] open /home/defatul/.config/google-chrome/Crash Reports/pending/c886dfd9-13db-4532-a95b-00fdb77d883e.lock: File exists (17) Eyl 06 21:51:12 oleymod gnome-shell[70364]: [0906/215112.732413:ERROR:file_io.cc(94)] ReadExactly: expected 8, observed 0 Eyl 06 21:51:12 oleymod gnome-shell[70364]: [0906/215112.732463:ERROR:file_io_posix.cc(152)] open /home/defatul/.config/google-chrome/Crash Reports/pending/c886dfd9-13db-4532-a95b-00fdb77d883e.lock: File exists (17) Eyl 06 21:51:12 oleymod gnome-shell[70364]: [0906/215112.739477:ERROR:file_io_posix.cc(152)] open /home/defatul/.config/google-chrome/Crash Reports/pending/c886dfd9-13db-4532-a95b-00fdb77d883e.lock: File exists (17) Eyl 06 21:51:29 oleymod kernel: NVRM: GPU at PCI::01:00: GPU-ca032ef4-f159-7933-e230-6d4c17459dc1 Eyl 06 21:51:29 oleymod kernel: NVRM: Xid (PCI::01:00): 32, Channel ID 0007 intr 80044000 Eyl 06 21:51:31 oleymod kernel: sched: RT throttling activated Eyl 06 21:51:33 oleymod /usr/lib/gdm3/gdm-x-session[3214]: (EE) NVIDIA(GPU-0): WAIT (2, 8, 0x8000, 0x9954, 0x9a58) Eyl 06 21:51:33 oleymod kernel: NVRM: Xid (PCI::01:00): 32, Channel ID 0007 intr 80004000 Eyl 06 21:51:33 oleymod kernel: NVRM: Xid (PCI::01:00): 39, CCMDs 000a 90b5 Eyl 06 21:51:36 oleymod kernel: NVRM: Xid (PCI::01:00): 38, 0003 9197 0360 20164010 Eyl 06 21:51:40 oleymod /usr/lib/gdm3/gdm-x-session[3214]: (EE) NVIDIA(GPU-0): WAIT (1, 8, 0x8000, 0x9954, 0x9a58) Eyl 06 21:51:48 oleymod /usr/lib/gdm3/gdm-x-session[3214]: (EE) NVIDIA(GPU-0): WAIT (2, 8, 0x8000, 0x9954, 0x9adc) Eyl 06 21:51:53 oleymod kernel: NVRM: Xid (PCI::01:00): 8, Channel 0003 Eyl 06 21:51:55 oleymod kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context Eyl 06 21:51:57 oleymod kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context Eyl 06 21:51:59 oleymod gnome-shell[70364]: [0906/215159.226903:ERROR:directory_reader_posix.cc(42)] opendir /home/defatul/.config/google-chrome/Crash Reports/attachments/4429829c-8803-4c1d-b12a-d6070352b885: No such file or directory (2) Eyl 06 21:51:59 oleymod gnome-shell[70364]: [80296:10:0906/215159.256278:ERROR:command_buffer_proxy_impl.cc(320)] GPU state invalid after WaitForGetOffsetInRange. Eyl 06 21:52:00 oleymod kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context Eyl 06 21:52:00 oleymod NetworkManager[1760]: [1694026320.4784] device (wlp3s0): supplicant interface state: inactive -> scanning Eyl 06 21:52:02 oleymod kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context Eyl 06 21:52:04 oleymod kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context Eyl 06 21:52:05 oleymod wpa_supplicant[1518]: wlp3s0: Reject scan trigger since one is already pending Eyl 06 21:52:06 oleymod /usr/lib/gdm3/gdm-x-session[3214]: (EE) NVIDIA(GPU-0): WAIT (1, 8, 0x8000, 0x9954, 0x9adc) Eyl 06 21:52:06 oleymod kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context Eyl 06 21:52:06 oleymod wpa_supplicant[1518]: wlx6c60eb9a3b24: CTRL-EVENT-BEACON-LOSS Eyl 06 21:52:06 oleymod kernel: wlx6c60eb9a3b24: deauthenticated from 00:31:92:61:95:16 (Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA) Eyl 06 21:52:06 oleymod gnome-shell[70364]: [0906/215206.685180:ERROR:http_transport_libcurl.cc(470)] curl_easy_perform: Couldn't resolve host name (6) Eyl 06 21:52:06 oleymod gnome-shell[70364]: [0906/215206.690213:ERROR:file_io_posix.cc(152)] open /home/defatul/.config/google-chrome/Crash Reports/pending/c886dfd9-13db-4532-a95b-00fdb77d883e.lock: File exists (17) Eyl 06 21:52:09 oleymod /usr/lib/gdm3/gdm-x-session[3214]: (EE) NVIDIA(GPU-0): WAIT (2, 8, 0x8000, 0x9954, 0x4388) Eyl 06 21:52:10 oleymod geoclue[2736]: Failed to query location: “location.services.mozilla.com” çözülürken hata: İsim çözünürlüğünde geçici başarısızlık Eyl 06 21:52:12 oleymod wpa_supplicant[1518]: wlx6c60eb9a3b24:
[Kernel-packages] [Bug 2030891] Re: In normal PC use, Nvidia crashes, laptop locks up
Eyl 06 21:50:57 oleymod NetworkManager[1760]: info [1694026257.4732] device (wlp3s0): supplicant interface state: inactive - scanning Eyl 06 21:50:57 oleymod NetworkManager[1760]: info [1694026257.9281] device (wlp3s0): supplicant interface state: scanning - inactive Eyl 06 21:50:59 oleymod NetworkManager[1760]: info [1694026259.4248] device (wlp3s0): supplicant interface state: inactive - scanning Eyl 06 21:50:59 oleymod NetworkManager[1760]: info [1694026259.8757] device (wlp3s0): supplicant interface state: scanning - inactive Eyl 06 21:51:01 oleymod NetworkManager[1760]: info [1694026261.4236] device (wlp3s0): supplicant interface state: inactive - scanning Eyl 06 21:51:01 oleymod NetworkManager[1760]: info [1694026261.8820] device (wlp3s0): supplicant interface state: scanning - inactive Eyl 06 21:51:12 oleymod gnome-shell[70364]: [0906/215112.732100:ERROR:file_io_posix.cc(152)] open /home/defatul/.config/google-chrome/Crash Reports/pending/c886dfd9-13db-4532-a95b-00fdb77d883e.lock: File exists (17) Eyl 06 21:51:12 oleymod gnome-shell[70364]: [0906/215112.732413:ERROR:file_io.cc(94)] ReadExactly: expected 8, observed 0 Eyl 06 21:51:12 oleymod gnome-shell[70364]: [0906/215112.732463:ERROR:file_io_posix.cc(152)] open /home/defatul/.config/google-chrome/Crash Reports/pending/c886dfd9-13db-4532-a95b-00fdb77d883e.lock: File exists (17) Eyl 06 21:51:12 oleymod gnome-shell[70364]: [0906/215112.739477:ERROR:file_io_posix.cc(152)] open /home/defatul/.config/google-chrome/Crash Reports/pending/c886dfd9-13db-4532-a95b-00fdb77d883e.lock: File exists (17) Eyl 06 21:51:29 oleymod kernel: NVRM: GPU at PCI::01:00: GPU-ca032ef4-f159-7933-e230-6d4c17459dc1 Eyl 06 21:51:29 oleymod kernel: NVRM: Xid (PCI::01:00): 32, Channel ID 0007 intr 80044000 Eyl 06 21:51:31 oleymod kernel: sched: RT throttling activated Eyl 06 21:51:33 oleymod /usr/lib/gdm3/gdm-x-session[3214]: (EE) NVIDIA(GPU-0): WAIT (2, 8, 0x8000, 0x9954, 0x9a58) Eyl 06 21:51:33 oleymod kernel: NVRM: Xid (PCI::01:00): 32, Channel ID 0007 intr 80004000 Eyl 06 21:51:33 oleymod kernel: NVRM: Xid (PCI::01:00): 39, CCMDs 000a 90b5 Eyl 06 21:51:36 oleymod kernel: NVRM: Xid (PCI::01:00): 38, 0003 9197 0360 20164010 Eyl 06 21:51:40 oleymod /usr/lib/gdm3/gdm-x-session[3214]: (EE) NVIDIA(GPU-0): WAIT (1, 8, 0x8000, 0x9954, 0x9a58) Eyl 06 21:51:48 oleymod /usr/lib/gdm3/gdm-x-session[3214]: (EE) NVIDIA(GPU-0): WAIT (2, 8, 0x8000, 0x9954, 0x9adc) Eyl 06 21:51:53 oleymod kernel: NVRM: Xid (PCI::01:00): 8, Channel 0003 Eyl 06 21:51:55 oleymod kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context Eyl 06 21:51:57 oleymod kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context Eyl 06 21:51:59 oleymod gnome-shell[70364]: [0906/215159.226903:ERROR:directory_reader_posix.cc(42)] opendir /home/defatul/.config/google-chrome/Crash Reports/attachments/4429829c-8803-4c1d-b12a-d6070352b885: No such file or directory (2) Eyl 06 21:51:59 oleymod gnome-shell[70364]: [80296:10:0906/215159.256278:ERROR:command_buffer_proxy_impl.cc(320)] GPU state invalid after WaitForGetOffsetInRange. Eyl 06 21:52:00 oleymod kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context Eyl 06 21:52:00 oleymod NetworkManager[1760]: info [1694026320.4784] device (wlp3s0): supplicant interface state: inactive - scanning Eyl 06 21:52:02 oleymod kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context Eyl 06 21:52:04 oleymod kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context Eyl 06 21:52:05 oleymod wpa_supplicant[1518]: wlp3s0: Reject scan trigger since one is already pending Eyl 06 21:52:06 oleymod /usr/lib/gdm3/gdm-x-session[3214]: (EE) NVIDIA(GPU-0): WAIT (1, 8, 0x8000, 0x9954, 0x9adc) Eyl 06 21:52:06 oleymod kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context Eyl 06 21:52:06 oleymod wpa_supplicant[1518]: wlx6c60eb9a3b24: CTRL-EVENT-BEACON-LOSS Eyl 06 21:52:06 oleymod kernel: wlx6c60eb9a3b24: deauthenticated from 00:31:92:61:95:16 (Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA) Eyl 06 21:52:06 oleymod gnome-shell[70364]: [0906/215206.685180:ERROR:http_transport_libcurl.cc(470)] curl_easy_perform: Couldnt resolve host name (6) Eyl 06 21:52:06 oleymod gnome-shell[70364]: [0906/215206.690213:ERROR:file_io_posix.cc(152)] open /home/defatul/.config/google-chrome/Crash Reports/pending/c886dfd9-13db-4532-a95b-00fdb77d883e.lock: File exists (17) Eyl 06 21:52:09 oleymod /usr/lib/gdm3/gdm-x-session[3214]: (EE) NVIDIA(GPU-0): WAIT (2, 8, 0x8000, 0x9954, 0x4388) Eyl 06 21:52:10 oleymod geoclue[2736]: Failed to query location: “location.services.mozilla.com” çözülürken hata: İsim çözünürlüğünde geçici başarısızlık Eyl 06 21:52:12 oleymod
[Kernel-packages] [Bug 2034607] Re: Bus error after reading or writing a specific number of unique locations from/to a shared memory pool.
I am unable to run the apport-collect command.
** 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/2034607
Title:
Bus error after reading or writing a specific number of unique
locations from/to a shared memory pool.
Status in linux package in Ubuntu:
Confirmed
Bug description:
A Bus error always occurs after reading or writing a specific number
of unique locations from/to a shared memory pool which is created
using shm_open() and mmap(). It does not matter if the pool memory
locations are accessed starting at the base of the pool, incrementing
up through the addresses, or starting at the top of the pool,
decrementing down through the addresses. The count of unique locations
accessed before the Bus error occurs is the same repeatable value. The
count value is close to but not exactly 1/2 of the total system
memory.
The count is of unique locations accessed. If an address range less
than the failure count is accessed repeatedly, the Bus error does not
occur.
The unique addresses do not have to be accessed sequentially to cause
the Bus error. While this aspect has not been tested exhaustively, if
a range of addresses are jumped over, the Bus error still occurs. Note
that the failure count is slightly different than if the addresses are
accessed sequentially.
This error is consistently repeatable on the following 3 systems:
Ubuntu 22.04.3 LTS
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Amazon EC2
CPU: AMD EPYC 7571
Memory: 124.68 GiB
Distro: Linux Mint 20 base: Ubuntu 20.04
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04)
Machine: Dell System XPS L502X
CPU: Intel Core i7-2620M
Total Memory: 8,219,435,008 bytes
Distro: Linux Mint 21 base: Ubuntu 22.04
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Dell Inspiron 5558
CPU: Intel Core i3-5005U
Total Memory: 8,229,298,176 bytes
C++ Test program that demonstrates the issue.
-
// September 2023 - Gene Weber
// This test program generates a Bus error core dump after reading or writing
a specific number
// of unique locations from/to a shared memory pool. It does not matter if
the pool memory locations
// are accessed starting at the base of the pool, incrementing up through the
addresses, or starting
// at the top of the pool, decrementing down through the addresses. The count
of unique locations
// accessed before the Bus error occurs is the same repeatable value. The
count value is close to
// but not exactly 1/2 of the total system memory.
//
// The count is of unique locations accessed. If an address range less than
the failure count is
// accessed repeatedly, the Bus error does not occur.
//
// The unique addresses do not have to be accessed sequentially to cause the
Bus error. While this
// has not been tested exhaustively, if a range of addresses are jumped over,
the Bus error still
// occurs. Note that the failure count is slightly different than if the
addresses are accessed
// sequentially.
//
// This test program has command line options to allow testing these
different scenarios.
// Compiling with either has the same results:
// g++ -std=c++11 test.cpp -W -Wall -Wextra -pedantic -pthread -o test -lrt
// g++ -std=c++20 -O3 test.cpp -W -Wall -Wextra -pedantic -pthread -o test
-lrt
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char** argv) {
int page_size = 4096;
if (argc != 5) {
std::cerr << "\nUsage: ./test
\n\n";
std::cerr << "= total from \"free
-b\".\n";
std::cerr << "= u to index addresses up from bottom of
pool, d for down from top.\n";
std::cerr << "= r to read indexed address, w for
write.\n";
std::cerr << "= j for jump index by 5% of total, r for
limit index range to 1/2 of total, x linear indexing.\n\n";
exit(EXIT_FAILURE);
}
uint_fast64_t total_system_ram = strtoull(argv[1], NULL, 10);
// Set pool_size to a whole number of pages that is ~60% of system memory.
uint_fast64_t pool_size = total_system_ram * 0.6;
pool_size = pool_size - (pool_size % page_size);
std::cout << "pool size = " << pool_size << "\n";
// Create a mask to print status at intervals of ~1/20 of the pool size.
uint_fast64_t print_interval = pow(2,ceil(log2(pool_size/20))) - 1;
// Create a value to start printing all addresses after a few pages less
than
// 1/2 of the pool size has been accessed.
uint_fast64_t almost_half = (total_system_ram/2) - (3 * page_size);
// Create a "jump address index" value to use if the jump option is
selected.
[Kernel-packages] [Bug 2028065] Re: Support for Intel Discrete Gale Peak2/BE200
** Description changed:
[WiFi]
- Below is the BKC in v6.5-rc1 for GaP2:
WIFI:
- a. Additional patch for driver :
https://lore.kernel.org/all/20230709181323.12085-2-johan...@sipsolutions.net/
[lore.kernel.org]
- b. FW : https://personal.filesanywhere.com/fs/v.aspx?v=8e6e658a596471b09ea7
[personal.filesanywhere.com]
-i. iwlwifi-gl-b0-fm-b0-83.ucode
-ii. iwlwifi-gl-b0-fm-b0.pnvm
+ a. kernel driver :
+- commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
crash") [v6.5-rc2]
+ b. firmware (to be released):
+ - iwlwifi-gl-b0-fm-b0-83.ucode
+ - iwlwifi-gl-b0-fm-b0.pnvm
[Bluetooth]
- 2 additional patches for driver:
-
i.https://patchwork.kernel.org/project/bluetooth/patch/20230628121831.827171-1-kira...@intel.com/
[patchwork.kernel.org]
-
ii.https://patchwork.kernel.org/project/bluetooth/patch/20230704081651.857493-1-kira...@intel.com/
[patchwork.kernel.org]
-
- FW: https://personal.filesanywhere.com/fs/v.aspx?v=8e6e658a596471b09ea7
[personal.filesanywhere.com]
- i.ibt-0191-0191.sfi
- ii.ibt-0191-0191.ddc
+ a. kernel driver:
+- commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
[linux-next]
+- commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
[linux-next]
+ b. firmware (to be released):
+- intel/ibt-0191-0191.sfi
+- intel/ibt-0191-0191.ddc
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Incomplete
** Also affects: linux-firmware (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => Incomplete
** Changed in: linux-firmware (Ubuntu Mantic)
Status: New => Incomplete
** Also affects: linux-oem-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.5 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Mantic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
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/2028065
Title:
Support for Intel Discrete Gale Peak2/BE200
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Incomplete
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Incomplete
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-firmware source package in Mantic:
Incomplete
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[WiFi]
WIFI:
a. kernel driver :
- commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
crash") [v6.5-rc2]
b. firmware (to be released):
- iwlwifi-gl-b0-fm-b0-83.ucode
- iwlwifi-gl-b0-fm-b0.pnvm
[Bluetooth]
a. kernel driver:
- commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
[linux-next]
- commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
[linux-next]
b. firmware (to be released):
- intel/ibt-0191-0191.sfi
- intel/ibt-0191-0191.ddc
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2028065/+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 2034607] 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 2034607
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/2034607
Title:
Bus error after reading or writing a specific number of unique
locations from/to a shared memory pool.
Status in linux package in Ubuntu:
Incomplete
Bug description:
A Bus error always occurs after reading or writing a specific number
of unique locations from/to a shared memory pool which is created
using shm_open() and mmap(). It does not matter if the pool memory
locations are accessed starting at the base of the pool, incrementing
up through the addresses, or starting at the top of the pool,
decrementing down through the addresses. The count of unique locations
accessed before the Bus error occurs is the same repeatable value. The
count value is close to but not exactly 1/2 of the total system
memory.
The count is of unique locations accessed. If an address range less
than the failure count is accessed repeatedly, the Bus error does not
occur.
The unique addresses do not have to be accessed sequentially to cause
the Bus error. While this aspect has not been tested exhaustively, if
a range of addresses are jumped over, the Bus error still occurs. Note
that the failure count is slightly different than if the addresses are
accessed sequentially.
This error is consistently repeatable on the following 3 systems:
Ubuntu 22.04.3 LTS
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Amazon EC2
CPU: AMD EPYC 7571
Memory: 124.68 GiB
Distro: Linux Mint 20 base: Ubuntu 20.04
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04)
Machine: Dell System XPS L502X
CPU: Intel Core i7-2620M
Total Memory: 8,219,435,008 bytes
Distro: Linux Mint 21 base: Ubuntu 22.04
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Dell Inspiron 5558
CPU: Intel Core i3-5005U
Total Memory: 8,229,298,176 bytes
C++ Test program that demonstrates the issue.
-
// September 2023 - Gene Weber
// This test program generates a Bus error core dump after reading or writing
a specific number
// of unique locations from/to a shared memory pool. It does not matter if
the pool memory locations
// are accessed starting at the base of the pool, incrementing up through the
addresses, or starting
// at the top of the pool, decrementing down through the addresses. The count
of unique locations
// accessed before the Bus error occurs is the same repeatable value. The
count value is close to
// but not exactly 1/2 of the total system memory.
//
// The count is of unique locations accessed. If an address range less than
the failure count is
// accessed repeatedly, the Bus error does not occur.
//
// The unique addresses do not have to be accessed sequentially to cause the
Bus error. While this
// has not been tested exhaustively, if a range of addresses are jumped over,
the Bus error still
// occurs. Note that the failure count is slightly different than if the
addresses are accessed
// sequentially.
//
// This test program has command line options to allow testing these
different scenarios.
// Compiling with either has the same results:
// g++ -std=c++11 test.cpp -W -Wall -Wextra -pedantic -pthread -o test -lrt
// g++ -std=c++20 -O3 test.cpp -W -Wall -Wextra -pedantic -pthread -o test
-lrt
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char** argv) {
int page_size = 4096;
if (argc != 5) {
std::cerr << "\nUsage: ./test
\n\n";
std::cerr << "= total from \"free
-b\".\n";
std::cerr << "= u to index addresses up from bottom of
pool, d for down from top.\n";
std::cerr << "= r to read indexed address, w for
write.\n";
std::cerr << "= j for jump index by 5% of total, r for
limit index range to 1/2 of total, x linear indexing.\n\n";
exit(EXIT_FAILURE);
}
uint_fast64_t total_system_ram = strtoull(argv[1], NULL, 10);
// Set pool_size to a whole number of pages that is ~60% of system memory.
uint_fast64_t pool_size = total_system_ram * 0.6;
pool_size = pool_size - (pool_size % page_size);
std::cout << "pool
[Kernel-packages] [Bug 2034605] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/2034605 Title: Cannot boot after kernel upgrade Status in linux package in Ubuntu: Confirmed Bug description: I use LVM with full disk encryption. After kernel upgrade, I am not able to boot the system running new kernel 6.2.0-32-generic (the 6.2.0-31-generic works just fine). After writing the encryption password, there is an error message "No key available with this passphrase.". The password is correct and there was no such error with older kernels. So I think the bug sits in the linux package. Thanks! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32 ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erik 2310 F pipewire erik 2314 F wireplumber /dev/snd/seq:erik 2310 F pipewire CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Wed Sep 6 19:59:33 2023 InstallationDate: Installed on 2023-03-21 (168 days ago) InstallationMedia: Ubuntu-MATE 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop K3502ZA_K3502ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-03 (156 days ago) dmi.bios.date: 04/26/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: K3502ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K3502ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 208.32 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrK3502ZA.305:bd04/26/2022:br5.25:efr208.32:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopK3502ZA_K3502ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK3502ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Vivobook dmi.product.name: VivoBook_ASUSLaptop K3502ZA_K3502ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034605/+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 2034607] [NEW] Bus error after reading or writing a specific number of unique locations from/to a shared memory pool.
Public bug reported:
A Bus error always occurs after reading or writing a specific number of
unique locations from/to a shared memory pool which is created using
shm_open() and mmap(). It does not matter if the pool memory locations
are accessed starting at the base of the pool, incrementing up through
the addresses, or starting at the top of the pool, decrementing down
through the addresses. The count of unique locations accessed before the
Bus error occurs is the same repeatable value. The count value is close
to but not exactly 1/2 of the total system memory.
The count is of unique locations accessed. If an address range less than
the failure count is accessed repeatedly, the Bus error does not occur.
The unique addresses do not have to be accessed sequentially to cause
the Bus error. While this aspect has not been tested exhaustively, if a
range of addresses are jumped over, the Bus error still occurs. Note
that the failure count is slightly different than if the addresses are
accessed sequentially.
This error is consistently repeatable on the following 3 systems:
Ubuntu 22.04.3 LTS
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Amazon EC2
CPU: AMD EPYC 7571
Memory: 124.68 GiB
Distro: Linux Mint 20 base: Ubuntu 20.04
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04)
Machine: Dell System XPS L502X
CPU: Intel Core i7-2620M
Total Memory: 8,219,435,008 bytes
Distro: Linux Mint 21 base: Ubuntu 22.04
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Dell Inspiron 5558
CPU: Intel Core i3-5005U
Total Memory: 8,229,298,176 bytes
C++ Test program that demonstrates the issue.
-
// September 2023 - Gene Weber
// This test program generates a Bus error core dump after reading or writing a
specific number
// of unique locations from/to a shared memory pool. It does not matter if the
pool memory locations
// are accessed starting at the base of the pool, incrementing up through the
addresses, or starting
// at the top of the pool, decrementing down through the addresses. The count
of unique locations
// accessed before the Bus error occurs is the same repeatable value. The count
value is close to
// but not exactly 1/2 of the total system memory.
//
// The count is of unique locations accessed. If an address range less than the
failure count is
// accessed repeatedly, the Bus error does not occur.
//
// The unique addresses do not have to be accessed sequentially to cause the
Bus error. While this
// has not been tested exhaustively, if a range of addresses are jumped over,
the Bus error still
// occurs. Note that the failure count is slightly different than if the
addresses are accessed
// sequentially.
//
// This test program has command line options to allow testing these different
scenarios.
// Compiling with either has the same results:
// g++ -std=c++11 test.cpp -W -Wall -Wextra -pedantic -pthread -o test -lrt
// g++ -std=c++20 -O3 test.cpp -W -Wall -Wextra -pedantic -pthread -o test -lrt
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char** argv) {
int page_size = 4096;
if (argc != 5) {
std::cerr << "\nUsage: ./test
\n\n";
std::cerr << "= total from \"free
-b\".\n";
std::cerr << "= u to index addresses up from bottom of
pool, d for down from top.\n";
std::cerr << "= r to read indexed address, w for write.\n";
std::cerr << "= j for jump index by 5% of total, r for
limit index range to 1/2 of total, x linear indexing.\n\n";
exit(EXIT_FAILURE);
}
uint_fast64_t total_system_ram = strtoull(argv[1], NULL, 10);
// Set pool_size to a whole number of pages that is ~60% of system memory.
uint_fast64_t pool_size = total_system_ram * 0.6;
pool_size = pool_size - (pool_size % page_size);
std::cout << "pool size = " << pool_size << "\n";
// Create a mask to print status at intervals of ~1/20 of the pool size.
uint_fast64_t print_interval = pow(2,ceil(log2(pool_size/20))) - 1;
// Create a value to start printing all addresses after a few pages less
than
// 1/2 of the pool size has been accessed.
uint_fast64_t almost_half = (total_system_ram/2) - (3 * page_size);
// Create a "jump address index" value to use if the jump option is
selected.
uint_fast64_t jmp_indx = total_system_ram * 0.05;
if (*argv[4] == 'j') {
std::cout << "jump address index by " << jmp_indx << "\n";
}
// Create an "address index range" value to use if range limit option is
selected.
uint_fast64_t indx_range = pool_size / 2;
if (*argv[4] == 'r') {
std::cout << "address index range will be limited to " << indx_range <<
" locations.\n";
}
int fd;
std::string shmpath = "/foo";
// Remove any existing shared memory object
shm_unlink(shmpath.c_str());
// Create the shared memory object with read-write access.
[Kernel-packages] [Bug 2032378] Re: Devlink backport: fix race and lock issue
add merge request https://code.launchpad.net/~wtu/ubuntu/+source/linux-bluefield/+git/linux-bluefield/+merge/450806 -- 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/2032378 Title: Devlink backport: fix race and lock issue Status in linux-bluefield package in Ubuntu: New Bug description: Summary: machine get stuck if try to switch to switchdev mode while toggling ns over BF kernel. This is due to missing lock refactor series devlink and driver from kernel 6.0 How to test: 1. Configure SRIOV 2. Enable switchdev mode 3. Devlink reload 4. Add/Del network namespace Note: Need to run the test multiple times to reproduce the issue. How to fix: Need to backport a series of devlink patches into BlueField 5.15 kernel, from 6.0 upstream kernel. Patches needed for 5.4/5.15 kernel: First series: 367dfa121205^..f0680ef0f949 second series: 5502e8712c9b^..c90005b5f75c Also needed: 644a66c60f02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2032378/+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 2034605] [NEW] Cannot boot after kernel upgrade
Public bug reported: I use LVM with full disk encryption. After kernel upgrade, I am not able to boot the system running new kernel 6.2.0-32-generic (the 6.2.0-31-generic works just fine). After writing the encryption password, there is an error message "No key available with this passphrase.". The password is correct and there was no such error with older kernels. So I think the bug sits in the linux package. Thanks! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32 ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erik 2310 F pipewire erik 2314 F wireplumber /dev/snd/seq:erik 2310 F pipewire CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Wed Sep 6 19:59:33 2023 InstallationDate: Installed on 2023-03-21 (168 days ago) InstallationMedia: Ubuntu-MATE 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop K3502ZA_K3502ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-03 (156 days ago) dmi.bios.date: 04/26/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: K3502ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K3502ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 208.32 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrK3502ZA.305:bd04/26/2022:br5.25:efr208.32:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopK3502ZA_K3502ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK3502ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Vivobook dmi.product.name: VivoBook_ASUSLaptop K3502ZA_K3502ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- 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/2034605 Title: Cannot boot after kernel upgrade Status in linux package in Ubuntu: New Bug description: I use LVM with full disk encryption. After kernel upgrade, I am not able to boot the system running new kernel 6.2.0-32-generic (the 6.2.0-31-generic works just fine). After writing the encryption password, there is an error message "No key available with this passphrase.". The password is correct and there was no such error with older kernels. So I think the bug sits in the linux package. Thanks! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32 ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erik 2310 F pipewire erik 2314 F wireplumber /dev/snd/seq:erik 2310 F pipewire CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Wed Sep 6 19:59:33 2023 InstallationDate: Installed on 2023-03-21 (168 days ago) InstallationMedia: Ubuntu-MATE 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop K3502ZA_K3502ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-03 (156 days ago) dmi.bios.date: 04/26/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: K3502ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K3502ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag
[Kernel-packages] [Bug 2034603] [NEW] nouveau module is loaded in computer with only Intel GPU
Public bug reported: On a computer with only an Intel GPU, the nouveau module is loaded. 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 Date: Wed Sep 6 18:13:36 2023 InstallationDate: Installed on 2022-04-14 (509 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2034603 Title: nouveau module is loaded in computer with only Intel GPU Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: On a computer with only an Intel GPU, the nouveau module is loaded. 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 Date: Wed Sep 6 18:13:36 2023 InstallationDate: Installed on 2022-04-14 (509 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) 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/2034603/+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 2013390] Re: CPU Lockup related to xhci/DMA
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-lowlatency-hwe-5.15 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/2013390 Title: CPU Lockup related to xhci/DMA Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Status in linux-signed-lowlatency package in Ubuntu: Confirmed Status in linux-signed-lowlatency-hwe-5.15 package in Ubuntu: Confirmed Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59
[Kernel-packages] [Bug 2013390] Re: CPU Lockup related to xhci/DMA
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.19 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/2013390 Title: CPU Lockup related to xhci/DMA Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Status in linux-signed-lowlatency package in Ubuntu: Confirmed Status in linux-signed-lowlatency-hwe-5.15 package in Ubuntu: Confirmed Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda
[Kernel-packages] [Bug 2013390] Re: CPU Lockup related to xhci/DMA
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.13 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/2013390 Title: CPU Lockup related to xhci/DMA Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Status in linux-signed-lowlatency package in Ubuntu: Confirmed Status in linux-signed-lowlatency-hwe-5.15 package in Ubuntu: Confirmed Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda
[Kernel-packages] [Bug 2013390] Re: CPU Lockup related to xhci/DMA
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-lowlatency (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/2013390 Title: CPU Lockup related to xhci/DMA Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Status in linux-signed-lowlatency package in Ubuntu: Confirmed Status in linux-signed-lowlatency-hwe-5.15 package in Ubuntu: Confirmed Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda
[Kernel-packages] [Bug 2007055] Re: cifs/samba mount not preserving file timestamps
Hi Andreas! Thanks for taking care. Of course I can not say 100% that the behaviour will never ever happen again with 6.2.0-32, because it was something like 4/10 on 5.15.0-82 with no clear pattern but I'll update this ticket if I have any news. Perhaps you/someone can backport the fix from 6.2.0-32 to 5.15.0-83 because the latter seems to be LTS (until APR 2027) and the former rather short lived. -- 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/2007055 Title: cifs/samba mount not preserving file timestamps Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Incomplete Bug description: I think I've found a bug or regression in something when trying to mount a remote samba share. Modified/Created times are not properly preserved in newer versions of Ubuntu. Because of this, rsync thinks files are different based on their modified times and keeps re-syncing them. I have a NAS on my network, running samba. I have two devices, a desktop and laptop. Both are running Ubuntu, and set up the exact same way. The desktop is running ubuntu 20.04, the laptop 22.04. I have mounted the NAS on both devices the exact same way. I attempt to copy a file (rsync) the exact same way. On the 20.04 desktop, this works perfectly fine. On the 22.04 laptop, the modified times are not preserved and set to the current time, preventing things like rsync -t from working. The only difference i can find is that between the two systems, the newer laptop 22.04 mount adds a few more options than the older system to the cifs mount options. These are added automatically without being specified explicitly (see the mount -v output below): * 'forceuid'/'forcegid' are changed to 'noforceuid'/'noforcegid * iocharset=utf8 added * serverino added desktop: $ lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.9-1ubuntu0.2 Candidate: 2:6.9-1ubuntu0.2 Version table: *** 2:6.9-1ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2:6.9-1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages $ uname -a Linux desktop 5.4.0-132-generic #148-Ubuntu SMP Mon Oct 17 16:02:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) laptop: $ lsb_release -rd Description:KDE neon 5.26 Release:22.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.14-1ubuntu0.1 Candidate: 2:6.14-1ubuntu0.1 Version table: *** 2:6.14-1ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:6.14-1build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ uname -a Linux laptop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,iocharset=utf8,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) the remote NAS is a synology appliance, running Samba version 4.10.18. SMB version 3 Steps to reproduce: 1. Similar setup, 1 device running 20.04, another running 22.04, otherwise up to date. 2. mount the NAS on both devices the exact same way $ sudo mount -t cifs -o vers=3.0,credentials=/etc/samba/smbcreds,iocharset=utf8,rw,uid=1000,gid=1000,dir_mode=0775,file_mode=0664 //nas/backup /media/scratch 3. on the 20.04 older desktop, create a test file and show the modify time $ fallocate -l 1M test1.txt $ stat test1.txt File: test1.txt Size: 1048576 Blocks: 2048 IO Block: 4096 regular file Device: 801h/2049d Inode: 13634663Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/desktop_user) Gid: ( 1000/desktop_user) Access: 2023-02-12 18:35:48.978743377 -0700 Modify: 2023-02-12 18:35:48.978743377 -0700 Change: 2023-02-12 18:35:48.978743377 -0700 Birth: - 4. rsync the test file to the mount, stat the file and see the modify/change are preserved $ rsync -avh test1.txt /media/scratch/ sending incremental file list test1.txt sent 1.05M
[Kernel-packages] [Bug 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second
** Changed in: mesa Status: Unknown => Fix Released -- 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/2033967 Title: Laptop screen blinked, no tty works and 200 dmesg errors per second Status in Mesa: Fix Released Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Bug description: I was using my laptop and suddenly the screen blinked. After that, all I could do was to move the mouse, no interaction worked. Trying to change to a TTY would open the black screen but the text cursor wasn't blinking and nothing happened. I accessed the laptop via SSH and used: screen env DISPLAY=:0 xfwm4 --vblank=xpresent --replace To reload xfwm4. After that, the graphical interface started working again. However, no TTY is accessible and there are 200 dmesg errors per second. These are the errors that repeat endlessly: [43959.444682] amdgpu :06:00.0: amdgpu: couldn't schedule ib on ring [43959.444688] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) And while I was writing this report, another problem happened: [44566.016330] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 timeout, signaled seq=2, emitted seq=6 [44566.016553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process obs pid 38687 thread obs:cs0 pid 38694 [44566.016748] amdgpu :06:00.0: amdgpu: GPU reset begin! [44566.317039] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.525640] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 0x0100 != 0x [44566.728577] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.731204] [ cut here ] [44566.731205] WARNING: CPU: 15 PID: 29333 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731429] Modules linked in: tls wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel nvme_fabrics veth bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) rfcomm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock cmac algif_hash algif_skcipher af_alg bnep zram binfmt_misc nls_iso8859_1 nft_masq snd_sof_amd_rembrandt snd_sof_amd_renoir snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci ledtrig_audio snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel snd_sof_utils snd_intel_dspcfg snd_soc_core snd_intel_sdw_acpi snd_compress nft_limit snd_hda_codec intel_rapl_msr ac97_bus intel_rapl_common snd_hda_core snd_pcm_dmaengine snd_hwdep edac_mce_amd snd_pci_ps btusb snd_seq_midi btrtl snd_rpl_pci_acp6x kvm_amd snd_seq_midi_event btbcm snd_acp_pci btintel btmtk snd_rawmidi uvcvideo [44566.731465] snd_pci_acp6x nf_log_syslog rtw89_8852ae kvm videobuf2_vmalloc bluetooth snd_pcm videobuf2_memops snd_seq rtw89_8852a irqbypass snd_pci_acp5x videobuf2_v4l2 ecdh_generic snd_seq_device snd_rn_pci_acp3x joydev nft_log input_leds rapl videobuf2_common serio_raw snd_timer wmi_bmof hid_multitouch ecc snd_acp_config rtw89_pci snd_soc_acpi snd k10temp rtw89_core snd_pci_acp3x soundcore ideapad_laptop ccp sparse_keymap platform_profile mac_hid nft_ct nvidia_uvm(PO) nft_chain_nat nf_nat sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 cuse msr parport_pc nf_tables ppdev lp nfnetlink parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear overlay v4l2loopback(O) videodev mc virt_wifi virtio_net net_failover failover virtio_gpu virtio_dma_buf drm_shmem_helper z3fold rndis_host cdc_ether usbnet bfq at h10k_pci [44566.731504] ath10k_core ath mac80211 libarc4 cfg80211 usb_storage nbd mii nvidia_drm(PO) nvidia_modeset(PO) usbhid nvidia(PO) amdgpu iommu_v2 drm_buddy gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul polyval_clmulni sysfillrect polyval_generic hid_generic nvme sysimgblt ghash_clmulni_intel drm sha512_ssse3 aesni_intel i2c_hid_acpi crypto_simd xhci_pci nvme_core cryptd r8169 video i2c_piix4 i2c_hid xhci_pci_renesas nvme_common realtek wmi hid [44566.731529] CPU: 15 PID: 29333 Comm: kworker/u32:1 Tainted: PW O 6.2.0-31-generic #31~22.04.1-Ubuntu [44566.731531] Hardware name: LENOVO 82MJ/LNVNB161216, BIOS H3CN36WW(V2.06) 09/30/2022 [44566.731533] Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched] [44566.731539] RIP: 0010:amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731702] Code: 31 f6 31 ff c3 cc cc cc
[Kernel-packages] [Bug 2007055] Re: cifs/samba mount not preserving file timestamps
Thanks for your last update. cifs is indeed provided by the kernel, and mounted via mount.cifs from cifs-utils. Although similar in nature, this is not samba code. All of this discussion is pointing at something in the kernel, so I'm switching the bug task from samba to linux (which is the kernel). ** Package changed: samba (Ubuntu) => linux (Ubuntu) -- 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/2007055 Title: cifs/samba mount not preserving file timestamps Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Incomplete Bug description: I think I've found a bug or regression in something when trying to mount a remote samba share. Modified/Created times are not properly preserved in newer versions of Ubuntu. Because of this, rsync thinks files are different based on their modified times and keeps re-syncing them. I have a NAS on my network, running samba. I have two devices, a desktop and laptop. Both are running Ubuntu, and set up the exact same way. The desktop is running ubuntu 20.04, the laptop 22.04. I have mounted the NAS on both devices the exact same way. I attempt to copy a file (rsync) the exact same way. On the 20.04 desktop, this works perfectly fine. On the 22.04 laptop, the modified times are not preserved and set to the current time, preventing things like rsync -t from working. The only difference i can find is that between the two systems, the newer laptop 22.04 mount adds a few more options than the older system to the cifs mount options. These are added automatically without being specified explicitly (see the mount -v output below): * 'forceuid'/'forcegid' are changed to 'noforceuid'/'noforcegid * iocharset=utf8 added * serverino added desktop: $ lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.9-1ubuntu0.2 Candidate: 2:6.9-1ubuntu0.2 Version table: *** 2:6.9-1ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2:6.9-1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages $ uname -a Linux desktop 5.4.0-132-generic #148-Ubuntu SMP Mon Oct 17 16:02:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) laptop: $ lsb_release -rd Description:KDE neon 5.26 Release:22.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.14-1ubuntu0.1 Candidate: 2:6.14-1ubuntu0.1 Version table: *** 2:6.14-1ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:6.14-1build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ uname -a Linux laptop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,iocharset=utf8,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) the remote NAS is a synology appliance, running Samba version 4.10.18. SMB version 3 Steps to reproduce: 1. Similar setup, 1 device running 20.04, another running 22.04, otherwise up to date. 2. mount the NAS on both devices the exact same way $ sudo mount -t cifs -o vers=3.0,credentials=/etc/samba/smbcreds,iocharset=utf8,rw,uid=1000,gid=1000,dir_mode=0775,file_mode=0664 //nas/backup /media/scratch 3. on the 20.04 older desktop, create a test file and show the modify time $ fallocate -l 1M test1.txt $ stat test1.txt File: test1.txt Size: 1048576 Blocks: 2048 IO Block: 4096 regular file Device: 801h/2049d Inode: 13634663Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/desktop_user) Gid: ( 1000/desktop_user) Access: 2023-02-12 18:35:48.978743377 -0700 Modify: 2023-02-12 18:35:48.978743377 -0700 Change: 2023-02-12 18:35:48.978743377 -0700 Birth: - 4. rsync the test file to the mount, stat the file and see the modify/change are preserved $ rsync -avh test1.txt /media/scratch/ sending incremental file list test1.txt sent 1.05M bytes received 35 bytes 2.10M bytes/sec
[Kernel-packages] [Bug 2007055] [NEW] cifs/samba mount not preserving file timestamps
You have been subscribed to a public bug: I think I've found a bug or regression in something when trying to mount a remote samba share. Modified/Created times are not properly preserved in newer versions of Ubuntu. Because of this, rsync thinks files are different based on their modified times and keeps re-syncing them. I have a NAS on my network, running samba. I have two devices, a desktop and laptop. Both are running Ubuntu, and set up the exact same way. The desktop is running ubuntu 20.04, the laptop 22.04. I have mounted the NAS on both devices the exact same way. I attempt to copy a file (rsync) the exact same way. On the 20.04 desktop, this works perfectly fine. On the 22.04 laptop, the modified times are not preserved and set to the current time, preventing things like rsync -t from working. The only difference i can find is that between the two systems, the newer laptop 22.04 mount adds a few more options than the older system to the cifs mount options. These are added automatically without being specified explicitly (see the mount -v output below): * 'forceuid'/'forcegid' are changed to 'noforceuid'/'noforcegid * iocharset=utf8 added * serverino added desktop: $ lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.9-1ubuntu0.2 Candidate: 2:6.9-1ubuntu0.2 Version table: *** 2:6.9-1ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2:6.9-1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages $ uname -a Linux desktop 5.4.0-132-generic #148-Ubuntu SMP Mon Oct 17 16:02:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) laptop: $ lsb_release -rd Description:KDE neon 5.26 Release:22.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.14-1ubuntu0.1 Candidate: 2:6.14-1ubuntu0.1 Version table: *** 2:6.14-1ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:6.14-1build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ uname -a Linux laptop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,iocharset=utf8,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) the remote NAS is a synology appliance, running Samba version 4.10.18. SMB version 3 Steps to reproduce: 1. Similar setup, 1 device running 20.04, another running 22.04, otherwise up to date. 2. mount the NAS on both devices the exact same way $ sudo mount -t cifs -o vers=3.0,credentials=/etc/samba/smbcreds,iocharset=utf8,rw,uid=1000,gid=1000,dir_mode=0775,file_mode=0664 //nas/backup /media/scratch 3. on the 20.04 older desktop, create a test file and show the modify time $ fallocate -l 1M test1.txt $ stat test1.txt File: test1.txt Size: 1048576 Blocks: 2048 IO Block: 4096 regular file Device: 801h/2049d Inode: 13634663Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/desktop_user) Gid: ( 1000/desktop_user) Access: 2023-02-12 18:35:48.978743377 -0700 Modify: 2023-02-12 18:35:48.978743377 -0700 Change: 2023-02-12 18:35:48.978743377 -0700 Birth: - 4. rsync the test file to the mount, stat the file and see the modify/change are preserved $ rsync -avh test1.txt /media/scratch/ sending incremental file list test1.txt sent 1.05M bytes received 35 bytes 2.10M bytes/sec total size is 1.05M speedup is 1.00 $ stat /media/scratch/test1.txt File: /media/scratch/test1.txt Size: 1048576 Blocks: 2064 IO Block: 1048576 regular file Device: 52h/82d Inode: 321811 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/desktop_user) Gid: ( 1000/desktop_user) Access: 2023-02-12 18:38:25.671230900 -0700 Modify: 2023-02-12 18:35:48.978743300 -0700 Change: 2023-02-12 18:35:48.978743300 -0700 Birth: - 5. rsync again, notice the file is correctly skipped. $ rsync -avh test1.txt /media/scratch/ sending incremental file list sent 68 bytes received 12 bytes 160.00 bytes/sec total size is 1.05M speedup is 13,107.20 6. repeat the same steps above on the newer 22.04 laptop, only this time notice that the modify/change are NOT preserved. rsync re-sends the file because
[Kernel-packages] [Bug 2034578] Re: Support IPSEC full offload implementation
** Merge proposal linked: https://code.launchpad.net/~yifeid/ubuntu/+source/linux-bluefield/+git/linux-bluefield/+merge/450800 -- 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/2034578 Title: Support IPSEC full offload implementation Status in linux-bluefield package in Ubuntu: New Bug description: Summary: Align Kernel IPsec Full offload implementation in the DPU to the upstream Full offload in all components: OFED, Strongswan, etc. This is in order for DPU Kernel IPsec to include policy offload and be fully aligned to what CX Kernel customers will use. How to test: Host 1: /opt/mellanox/iproute2/sbin/devlink dev eswitch set pci/:03:00.0 mode legacy echo 'dmfs' > /sys/bus/pci/devices/:03:00.0/net/p0/compat/devlink/steering_mode echo 'full' > /sys/class/net/p0/compat/devlink/ipsec_mode /opt/mellanox/iproute2/sbin/devlink dev eswitch set pci/:03:00.0 mode switchdev BF on host 1: /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.181.165 dst 196.234.182.166 dir out tmpl src 196.234.181.165/16 dst 196.234.182.166/16 proto esp reqid 0xefa83812 mode transport priority 10 /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.182.166 dst 196.234.181.165 dir in tmpl src 196.234.182.166/16 dst 196.234.181.165/16 proto esp reqid 0x63a7db74 mode transport priority 10 /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.182.166 dst 196.234.181.165 dir fwd tmpl src 196.234.182.166/16 dst 196.234.181.165/16 proto esp reqid 0x63a7db74 mode transport priority 10 /opt/mellanox/iproute2/sbin/ip xfrm state add src 196.234.181.165/16 dst 196.234.182.166/16 proto esp spi 0xefa83812 reqid 0xefa83812 mode transport aead 'rfc4106(gcm(aes))' 0xe2fe3857301d8f72b5d71d295a462ef21868e407 128 offload packet dev p0 dir out sel src 196.234.181.165/16 dst 196.234.182.166/16 flag esn replay-window 32 /opt/mellanox/iproute2/sbin/ip xfrm state add src 196.234.182.166/16 dst 196.234.181.165/16 proto esp spi 0x63a7db74 reqid 0x63a7db74 mode transport aead 'rfc4106(gcm(aes))' 0xe916c4d0db1886e8c877b023e8cebef53b4d2d0f 128 offload packet dev p0 dir in sel src 196.234.182.166/16 dst 196.234.181.165/16 flag esn replay-window 32 Start OVS and set following configure on BF: /usr/bin/ovs-vsctl set Open_vSwitch . other_config:hw-offload=true /usr/bin/ovs-vsctl set Open_vSwitch . other_config:max-idle=30 Host2: /opt/mellanox/iproute2/sbin/devlink dev eswitch set pci/:03:00.1 mode legacy echo 'dmfs' > /sys/bus/pci/devices/:03:00.1/net/p1/compat/devlink/steering_mode echo 'full' > /sys/class/net/p1/compat/devlink/ipsec_mode /opt/mellanox/iproute2/sbin/devlink dev eswitch set pci/:03:00.1 mode switchdev BF on host 2: /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.182.166 dst 196.234.181.165 dir out tmpl src 196.234.182.166/16 dst 196.234.181.165/16 proto esp reqid 0xefa83812 mode transport priority 10 /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.181.165 dst 196.234.182.166 dir in tmpl src 196.234.181.165/16 dst 196.234.182.166/16 proto esp reqid 0x63a7db74 mode transport priority 10 /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.181.165 dst 196.234.182.166 dir fwd tmpl src 196.234.181.165/16 dst 196.234.182.166/16 proto esp reqid 0x63a7db74 mode transport priority 10 /opt/mellanox/iproute2/sbin/ip xfrm state add src 196.234.181.165 dst 196.234.182.166 proto esp spi 0xefa83812 reqid 0xefa83812 mode transport aead 'rfc4106(gcm(aes))' 0xe2fe3857301d8f72b5d71d295a462ef21868e407 128 offload packet dev p0 dir out sel src 196.234.181.165/16 dst 196.234.182.166/16 flag esn replay-window 32 /opt/mellanox/iproute2/sbin/ip xfrm state add src 196.234.181.165 dst 196.234.182.166 proto esp spi 0x63a7db74 reqid 0x63a7db74 mode transport aead 'rfc4106(gcm(aes))' 0xe916c4d0db1886e8c877b023e8cebef53b4d2d0f 128 offload packet dev p0 dir in sel src 196.234.181.165/16 dst 196.234.182.166/16 flag esn replay-window 32 Start OVS and set following configure on BF: /usr/bin/ovs-vsctl set Open_vSwitch . other_config:hw-offload=true /usr/bin/ovs-vsctl set Open_vSwitch . other_config:max-idle=30 Send the traffic between host 1 and host 2 and check IPsec counters in "ethtool -S" statistics on both BF. How to fix: Need to backport a series of xfrm patches into BlueField 5.15 kernel, from 6.0 upstream kernel. Patches needed for 5.15 kernel: afe9e47 xfrm: fix conflict for netdev and tx stats 6aff54d xfrm: don't skip free of empty state in acquire policy 692fecb xfrm: delete offloaded policy 91b6276 xfrm: Support UDP encapsulation in packet offload mode 69e168a xfrm: add missed call to delete offloaded policies 9724724 xfrm: release all offloaded policy memory e57b7ec xfrm: don't require advance ESN callback for packet offload 9e98488 xfrm:
[Kernel-packages] [Bug 2034447] Re: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic
Current upstream stable level is v5.15.122, latest is v5.15.130. Between those versions there seem to be no additional related patches. -- 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/2034447 Title: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic Status in linux package in Ubuntu: Incomplete Bug description: Seeing a panic on hidon (an Nvidia H100) after booting the 5.15.0-85-generic kernel: [ 58.935877] [ cut here ] [ 58.935893] refcount_t: underflow; use-after-free. [ 58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28 refcount_warn_saturate+0xf7/0x150 [ 58.935943] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp coretemp nls_iso8859_1 rapl irdma(+) i40e qat_4xxx(+) isst_if_mbox_pci intel_qat pmt_telemetry pmt_crashlog idxd(+) isst_if_mmio pmt_class isst_if_common authenc idxd_bus intel_th_gth mei_me intel_th_pci intel_th mei switchtec ipmi_ssif acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 multipath linear mlx5_ib ib_uverbs ib_core ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper raid0 mlx5_core syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ixgbe cec mlxfw ghash_clmulni_intel aesni_intel psample crypto_simd xfrm_algo ice rc_core cryptd tls nvme i2c_i801 dca xhci_pci intel_pmt drm [ 58.936077] pci_hyperv_intf i2c_ismt i2c_smbus [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936083] mdio [ 58.936096] xhci_pci_renesas nvme_core wmi pinctrl_emmitsburg [ 58.936106] CPU: 207 PID: 2985 Comm: systemd-udevd Not tainted 5.15.0-85-generic #95-Ubuntu [ 58.936115] Hardware name: NVIDIA DGXH100/DGXH100, BIOS 1.0.7 05/08/2023 [ 58.936119] RIP: 0010:refcount_warn_saturate+0xf7/0x150 [ 58.936130] Code: eb 9e 0f b6 1d 5e e6 b9 01 80 fb 01 0f 87 f4 63 6f 00 83 e3 01 75 89 48 c7 c7 88 c3 23 9e c6 05 42 e6 b9 01 01 e8 d8 e4 6b 00 <0f> 0b e9 6f ff ff ff 0f b6 1d 2d e6 b9 01 80 fb 01 0f 87 b1 63 6f [ 58.936135] RSP: 0018:ff4d5d94b2c7fa28 EFLAGS: 00010282 [ 58.936142] RAX: RBX: RCX: 0027 [ 58.936146] RDX: ff314dbbbf9e0588 RSI: 0001 RDI: ff314dbbbf9e0580 [ 58.936149] RBP: ff4d5d94b2c7fa30 R08: 0026 R09: ff4d5d94b2c7f9c0 [ 58.936153] R10: 0028 R11: 0001 R12: [ 58.936156] R13: ff314cbfdbcb6900 R14: ff314cbfdbcb67b8 R15: ff314cbfd24b4000 [ 58.936159] FS: 7fadd2f6c8c0() GS:ff314dbbbf9c() knlGS: [ 58.936163] CS: 0010 DS: ES: CR0: 80050033 [ 58.936167] CR2: 7fadd243b584 CR3: 00012972c006 CR4: 00771ee0 [ 58.936171] DR0: DR1: DR2: [ 58.936174] DR3: DR6: fffe07f0 DR7: 0400 [ 58.936177] PKRU: 5554 [ 58.936179] Call Trace: [ 58.936184] [ 58.936188] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936204] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936212] ? crypto_mod_put+0x6b/0x80 [ 58.936225] ? show_regs.part.0+0x23/0x29 [ 58.936232] ? show_regs.cold+0x8/0xd [ 58.936239] ? refcount_warn_saturate+0xf7/0x150 [ 58.936246] ? __warn+0x8c/0x100 [ 58.936255] ? refcount_warn_saturate+0xf7/0x150 [ 58.936263] ? report_bug+0xa4/0xd0 [ 58.936274] ? down_trylock+0x2e/0x40 [ 58.936285] ? handle_bug+0x39/0x90 [ 58.936296] ? exc_invalid_op+0x19/0x70 [ 58.936301] ? asm_exc_invalid_op+0x1b/0x20 [ 58.936310] ? refcount_warn_saturate+0xf7/0x150 [ 58.936317] ? refcount_warn_saturate+0xf7/0x150 [ 58.936323] crypto_mod_put+0x6b/0x80 [ 58.936329] crypto_destroy_tfm+0x4e/0xa0 [ 58.936336] pkcs1pad_exit_tfm+0x15/0x20 [ 58.936345] crypto_akcipher_exit_tfm+0x13/0x20 [ 58.936352] crypto_destroy_tfm+0x43/0xa0 [ 58.936358] public_key_verify_signature+0x2dc/0x3c0 [ 58.936366] ? find_asymmetric_key+0xd2/0x1d0 [ 58.936374] ? kfree+0x1f7/0x250 [ 58.936385] public_key_verify_signature_2+0x15/0x20 [ 58.936389] verify_signature+0x37/0x60 [ 58.936393] pkcs7_validate_trust_one.constprop.0+0x156/0x1e0 [ 58.936400] pkcs7_validate_trust+0x4a/0xa0 [
[Kernel-packages] [Bug 2034447] Re: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic
Since this is somewhere in crypto and I saw QAT in the messages, this is the list of related changes between -83 and -85: 88c7bf897ef7 crypto: qat - unmap buffers before free for RSA d66aa0d64549 crypto: qat - unmap buffer before free for DH 32a99d9afc4d crypto: qat - Use helper to set reqsize d389108b0aee crypto: kpp - Add helper to set reqsize 18d6f474609d crypto: qat - use reference to structure in dma_map_single() d72b1246a048 crypto: qat - replace get_current_node() with numa_node_id() abcd04ccb419 crypto: qat - honor CRYPTO_TFM_REQ_MAY_SLEEP flag -- 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/2034447 Title: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic Status in linux package in Ubuntu: Incomplete Bug description: Seeing a panic on hidon (an Nvidia H100) after booting the 5.15.0-85-generic kernel: [ 58.935877] [ cut here ] [ 58.935893] refcount_t: underflow; use-after-free. [ 58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28 refcount_warn_saturate+0xf7/0x150 [ 58.935943] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp coretemp nls_iso8859_1 rapl irdma(+) i40e qat_4xxx(+) isst_if_mbox_pci intel_qat pmt_telemetry pmt_crashlog idxd(+) isst_if_mmio pmt_class isst_if_common authenc idxd_bus intel_th_gth mei_me intel_th_pci intel_th mei switchtec ipmi_ssif acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 multipath linear mlx5_ib ib_uverbs ib_core ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper raid0 mlx5_core syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ixgbe cec mlxfw ghash_clmulni_intel aesni_intel psample crypto_simd xfrm_algo ice rc_core cryptd tls nvme i2c_i801 dca xhci_pci intel_pmt drm [ 58.936077] pci_hyperv_intf i2c_ismt i2c_smbus [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936083] mdio [ 58.936096] xhci_pci_renesas nvme_core wmi pinctrl_emmitsburg [ 58.936106] CPU: 207 PID: 2985 Comm: systemd-udevd Not tainted 5.15.0-85-generic #95-Ubuntu [ 58.936115] Hardware name: NVIDIA DGXH100/DGXH100, BIOS 1.0.7 05/08/2023 [ 58.936119] RIP: 0010:refcount_warn_saturate+0xf7/0x150 [ 58.936130] Code: eb 9e 0f b6 1d 5e e6 b9 01 80 fb 01 0f 87 f4 63 6f 00 83 e3 01 75 89 48 c7 c7 88 c3 23 9e c6 05 42 e6 b9 01 01 e8 d8 e4 6b 00 <0f> 0b e9 6f ff ff ff 0f b6 1d 2d e6 b9 01 80 fb 01 0f 87 b1 63 6f [ 58.936135] RSP: 0018:ff4d5d94b2c7fa28 EFLAGS: 00010282 [ 58.936142] RAX: RBX: RCX: 0027 [ 58.936146] RDX: ff314dbbbf9e0588 RSI: 0001 RDI: ff314dbbbf9e0580 [ 58.936149] RBP: ff4d5d94b2c7fa30 R08: 0026 R09: ff4d5d94b2c7f9c0 [ 58.936153] R10: 0028 R11: 0001 R12: [ 58.936156] R13: ff314cbfdbcb6900 R14: ff314cbfdbcb67b8 R15: ff314cbfd24b4000 [ 58.936159] FS: 7fadd2f6c8c0() GS:ff314dbbbf9c() knlGS: [ 58.936163] CS: 0010 DS: ES: CR0: 80050033 [ 58.936167] CR2: 7fadd243b584 CR3: 00012972c006 CR4: 00771ee0 [ 58.936171] DR0: DR1: DR2: [ 58.936174] DR3: DR6: fffe07f0 DR7: 0400 [ 58.936177] PKRU: 5554 [ 58.936179] Call Trace: [ 58.936184] [ 58.936188] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936204] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936212] ? crypto_mod_put+0x6b/0x80 [ 58.936225] ? show_regs.part.0+0x23/0x29 [ 58.936232] ? show_regs.cold+0x8/0xd [ 58.936239] ? refcount_warn_saturate+0xf7/0x150 [ 58.936246] ? __warn+0x8c/0x100 [ 58.936255] ? refcount_warn_saturate+0xf7/0x150 [ 58.936263] ? report_bug+0xa4/0xd0 [ 58.936274] ? down_trylock+0x2e/0x40 [ 58.936285] ? handle_bug+0x39/0x90 [ 58.936296] ? exc_invalid_op+0x19/0x70 [ 58.936301] ? asm_exc_invalid_op+0x1b/0x20 [ 58.936310] ? refcount_warn_saturate+0xf7/0x150 [ 58.936317] ? refcount_warn_saturate+0xf7/0x150 [ 58.936323] crypto_mod_put+0x6b/0x80 [ 58.936329] crypto_destroy_tfm+0x4e/0xa0 [ 58.936336] pkcs1pad_exit_tfm+0x15/0x20 [ 58.936345] crypto_akcipher_exit_tfm+0x13/0x20 [
[Kernel-packages] [Bug 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second
I believe this likely needs the VCN fixes from https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 backported. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9728 https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Invalid ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 Importance: Unknown Status: Unknown -- 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/2033967 Title: Laptop screen blinked, no tty works and 200 dmesg errors per second Status in Mesa: Unknown Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Bug description: I was using my laptop and suddenly the screen blinked. After that, all I could do was to move the mouse, no interaction worked. Trying to change to a TTY would open the black screen but the text cursor wasn't blinking and nothing happened. I accessed the laptop via SSH and used: screen env DISPLAY=:0 xfwm4 --vblank=xpresent --replace To reload xfwm4. After that, the graphical interface started working again. However, no TTY is accessible and there are 200 dmesg errors per second. These are the errors that repeat endlessly: [43959.444682] amdgpu :06:00.0: amdgpu: couldn't schedule ib on ring [43959.444688] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) And while I was writing this report, another problem happened: [44566.016330] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 timeout, signaled seq=2, emitted seq=6 [44566.016553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process obs pid 38687 thread obs:cs0 pid 38694 [44566.016748] amdgpu :06:00.0: amdgpu: GPU reset begin! [44566.317039] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.525640] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 0x0100 != 0x [44566.728577] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.731204] [ cut here ] [44566.731205] WARNING: CPU: 15 PID: 29333 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731429] Modules linked in: tls wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel nvme_fabrics veth bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) rfcomm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock cmac algif_hash algif_skcipher af_alg bnep zram binfmt_misc nls_iso8859_1 nft_masq snd_sof_amd_rembrandt snd_sof_amd_renoir snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci ledtrig_audio snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel snd_sof_utils snd_intel_dspcfg snd_soc_core snd_intel_sdw_acpi snd_compress nft_limit snd_hda_codec intel_rapl_msr ac97_bus intel_rapl_common snd_hda_core snd_pcm_dmaengine snd_hwdep edac_mce_amd snd_pci_ps btusb snd_seq_midi btrtl snd_rpl_pci_acp6x kvm_amd snd_seq_midi_event btbcm snd_acp_pci btintel btmtk snd_rawmidi uvcvideo [44566.731465] snd_pci_acp6x nf_log_syslog rtw89_8852ae kvm videobuf2_vmalloc bluetooth snd_pcm videobuf2_memops snd_seq rtw89_8852a irqbypass snd_pci_acp5x videobuf2_v4l2 ecdh_generic snd_seq_device snd_rn_pci_acp3x joydev nft_log input_leds rapl videobuf2_common serio_raw snd_timer wmi_bmof hid_multitouch ecc snd_acp_config rtw89_pci snd_soc_acpi snd k10temp rtw89_core snd_pci_acp3x soundcore ideapad_laptop ccp sparse_keymap platform_profile mac_hid nft_ct nvidia_uvm(PO) nft_chain_nat nf_nat sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 cuse msr parport_pc nf_tables ppdev lp nfnetlink parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear overlay v4l2loopback(O) videodev mc virt_wifi virtio_net net_failover failover virtio_gpu virtio_dma_buf drm_shmem_helper z3fold rndis_host cdc_ether usbnet bfq at h10k_pci [44566.731504] ath10k_core ath mac80211 libarc4 cfg80211 usb_storage nbd mii nvidia_drm(PO) nvidia_modeset(PO) usbhid nvidia(PO) amdgpu iommu_v2 drm_buddy gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul polyval_clmulni sysfillrect polyval_generic hid_generic nvme sysimgblt ghash_clmulni_intel drm sha512_ssse3 aesni_intel i2c_hid_acpi crypto_simd xhci_pci nvme_core cryptd r8169 video i2c_piix4
[Kernel-packages] [Bug 2034594] [NEW] mlxbf-ptm: add thermal envelope debugfs node
Public bug reported: SRU Justification: [Impact] mlxbf-ptm is a kernel driver that provides debufgs interface for system software to monitor Bluefield devices' power and thermal management parameters. [Fix] This change: * This change adds additional debugfs node that gets the current thermal envelope set in the thermal state machine [Test Case] * After installing the kernel module, debugfs entry at /sys/kernel/debug/mlxbf-ptm will be created * monitors/status folder contains read-only parameters reported from the Bluefield device * cat /sys/kernel/debug/mlxbf-ptm/temp_envelope shows current thermal envelope [Regression Potential] * Minimal - as these are read-only parameters that report Bluefield device information. [Other] * This code is likely to change depending on feedback we received from maintainers. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New ** Description changed: - RU Justification: + SRU Justification: [Impact] mlxbf-ptm is a kernel driver that provides debufgs interface for system software to monitor Bluefield devices' power and thermal management parameters. [Fix] This change: * This change adds additional debugfs node that gets the current thermal - envelope set in the thermal state machine + envelope set in the thermal state machine [Test Case] * After installing the kernel module, debugfs entry at - /sys/kernel/debug/mlxbf-ptm will be created + /sys/kernel/debug/mlxbf-ptm will be created * monitors/status folder contains read-only parameters reported from the - Bluefield device + Bluefield device * cat /sys/kernel/debug/mlxbf-ptm/temp_envelope shows current thermal - envelope + envelope [Regression Potential] * Minimal - as these are read-only parameters that report Bluefield device - information. + information. [Other] * This code is likely to change depending on feedback we received from - maintainers. + maintainers. ** Summary changed: - ptm debugfs: add thermal envelope debugfs node + mlxbf-ptm: add thermal envelope debugfs node -- 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/2034594 Title: mlxbf-ptm: add thermal envelope debugfs node Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] mlxbf-ptm is a kernel driver that provides debufgs interface for system software to monitor Bluefield devices' power and thermal management parameters. [Fix] This change: * This change adds additional debugfs node that gets the current thermal envelope set in the thermal state machine [Test Case] * After installing the kernel module, debugfs entry at /sys/kernel/debug/mlxbf-ptm will be created * monitors/status folder contains read-only parameters reported from the Bluefield device * cat /sys/kernel/debug/mlxbf-ptm/temp_envelope shows current thermal envelope [Regression Potential] * Minimal - as these are read-only parameters that report Bluefield device information. [Other] * This code is likely to change depending on feedback we received from maintainers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2034594/+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 2034584] Re: F8 and F9 keys are disabled
I have downgraded to kernel 5.15.0-83 and removed the kernels 6.2.0, because I need the notebook to function. I don't think logfiles from a functioning system are any good for a bug report. ** 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/2034584 Title: F8 and F9 keys are disabled Status in linux package in Ubuntu: Confirmed Bug description: Kernel 6.2.0-25 up to 6.2.0-32 F8 and F9 keys are disabled (using now 5.15.0-83 - as also touchpad stopped working in kernel 6.2.0-32, as another user has already reported). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034584/+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 2034510] Re: spl fails to unregister sysctl entries
This bug was fixed in the package zfs-linux - 2.2.0~rc3-0ubuntu4 --- zfs-linux (2.2.0~rc3-0ubuntu4) mantic; urgency=medium * Properly unregister sysctl entries when spl is unloaded (LP: #2034510): - debian/patches/4635-Linux-6.5-compat-spl-properly-unregister-sysctl-entr.patch -- Andrea Righi Wed, 06 Sep 2023 09:03:35 +0200 ** Changed in: zfs-linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2034510 Title: spl fails to unregister sysctl entries Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Mantic: Fix Released Bug description: [Impact] On unload the spl module is not properly cleaning up the registered sysctl entries with kernel 6.5 in Mantic: 06:58 ubuntu@mantic$ sudo modprobe spl modprobe: ERROR: could not insert 'spl': Protocol driver not attached 06:58 ubuntu@mantic$ sudo dmesg | grep duplicate [ 152.587197] sysctl duplicate entry: /kernel/spl/kmem/slab_kvmem_total [Test case] Uninstall zfsutils-linux and try to `modprobe -r zfs; modprobe -r spl`, then `modprobe zfs` again and you should see the error (with a failure to load spl again). At this point it is possible to load spl again only after a reboot. [Fix] Properly cleanup all the registered sysctl entries when the spl module is unloaded. [Regression potential] We may experience regressions in systems that are using zfs with the 6.5 kernel. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: zfs-dkms 2.2.0~rc3-0ubuntu3 ProcVersionSignature: User Name 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230823 CloudSubPlatform: config-disk (/dev/vdb) Date: Wed Sep 6 07:06:33 2023 PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2034510/+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 2015400] Re: losetup with mknod fails on jammy with kernel 5.15.0-69-generic
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2015400 Title: losetup with mknod fails on jammy with kernel 5.15.0-69-generic Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Invalid Bug description: [ Impact ] * Regression in the loop block driver in Jammy kernel between 5.15.0-67 to 5.15.0-68 (in v5.15.86 stable), due to a change in the default behavior (value) of kernel parameter `max_loop` (from 0 to 8) in commit: `loop: Fix the max_loop commandline argument treatment when it is set to 0` (comment #6). * Users of loop devices (major 7) with minor >= 8 now fail to `open()` a loop device created with `mknod()`. * This is a corner case, as most people use `losetup` with usual /dev/loopNUMBER (or `--find`) which are not affected as it uses a different code path. (`losetup` for `/dev/loopNOT-A-NUMBER` is affected.) * Workaround: kernel parameter `max_loop=0`. [ Test Steps ] * Run the test cases (losetup and test-loop.c in comment #6): - max_loop not set (default) - max_loop=0 - max_loop=8 * Verify the default behavior (max_loop not set) is restored. * Verify the modified behavior (max_loop is set) is unchanged. [ Regression Potential ] * Regressions would be limited to the loop block driver, more specifically its default behavior (but it's that now) or specific usage of max_loop parameter (tested; looks OK). [ Other Info ] * Patch 1 [1] is not quite a fix, but adds CONFIG guards that Patch 2 [2] depends on. (Alternatively, a Patch 2 backport with that could be done, but Patch 1 seems trivial enough.) * The fix on Jammy is only Patch 2, with a trivial backport (that CONFIG option is not in Jammy/v5.15, only in v5.18). * The fix on Lunar is both patches; clean cherry-picks. * The fix on Mantic is both patches too, now in v6.5-rc3, which should be automatically incorporated as Mantic apparently will release with the 6.5 kernel [3] [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23881aec85f3219e8462e87c708815ee2cd82358 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bb5faa99f0ce40756ab7bbbce4f16c01ca5ebd5a [3] https://discourse.ubuntu.com/t/introducing-kernel-6-5-for-the-23-10-mantic-minotaur-release Original Description: --- losetup fails with devices created manually by mknod on kernel 5.15.0-69-generic # fallocate -l 1G test # mknod -m 660 /dev/loop8 b 7 8 # chown root:disk /dev/loop8 # losetup /dev/loop8 ./test losetup: ./test: failed to set up loop device: Device or resource busy Possibly as a result of this patch: https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/ which was introduced in 5.15.0-68: http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz On a machine prior to this change (no issue with losetup): # cat /sys/module/loop/parameters/max_loop 0 # uname -r 5.15.0-58-generic On a machine after the change (has losetup issue as described above): # cat /sys/module/loop/parameters/max_loop 8 # uname -r 5.15.0-69-generic So it looks like the default changed and the max amount of loop devices that can be created with mknod (not loop-control) is 8. If we set max_loop=0 on the kernel command line, it works as before. Cannot unload and reload module on a running system to change the parameter because it is built into the kernel. Another workaround is to use `losetup --find` but that means you cannot create with named devices created with mknod. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Confirmed Bug description: [Impact] Opened files reported in /proc/pid/map_files can be shows with the wrong mount point using overlayfs with filesystem namspaces. This incorrect behavior is fixed: UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files However, the fix introduced a new regression, the reference to the original file stored in vma->vm_prfile is not properly released when vma->vm_prfile is replaced with a new file. This can cause a reference counter unbalance, leading errors such as "target is busy" when trying to unmount overlayfs, even if the filesystem has not active reference. [Test case] Reproducer provided by original bug reporter: https://launchpadlibrarian.net/663151659/overlayfsscript_example [Fix] Fix by properly releasing the original file stored in vm_prfile. [Regression potential] This fix seems to solve the reported bug (verified with the reproducer) and it doesn't seem to introduce other regressions or behavior change. However, we may experience regressions in overlayfs or potentially other "target is busy" errors when unmounting overlayfs filesystems with this fix applied, if there are still other corner cases not covered properly. [Original bug report] Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem actually
[Kernel-packages] [Bug 2020295] Re: Include the MAC address pass through function on RTL8153DD-CG
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2020295 Title: Include the MAC address pass through function on RTL8153DD-CG 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 Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Invalid 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 Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] When user connect network cable on the RJ45 port of RTL8153DD-CG on dock, it should show pass through MAC address set in BIOS. But the LAN MAC address pass through doesn't function on RTL8153DD-CG sku. [Fix] Commit in v6.3-rc1 fixes the issue. ec51fbd1b8a2 r8152: add USB device driver for config selection [Test] Verified by OEM. [Where problems could occur] It won't affect the old behavior if there is no preferred cfg is configured and will select the preferred one while probing. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020295/+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 2020743] Re: FM350(mtk_t7xx) failed to suspend, or early wake while suspending
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2020743 Title: FM350(mtk_t7xx) failed to suspend, or early wake while suspending 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 Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Invalid 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 Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] FM350(mtk_t7xx) can't suspend sometimes. kernel: [ 12.917396] mtk_t7xx :57:00.0: [PM] Exiting suspend, modem in invalid state kernel: [ 12.917406] mtk_t7xx :57:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -14 kernel: [ 12.917446] mtk_t7xx :57:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1b0 returns -14 kernel: [ 12.917462] mtk_t7xx :57:00.0: PM: failed to suspend async: error -14 [Fix] The commit in v6.4-rc3 waits for the device to be ready before suspending. ab87603b2511 net: wwan: t7xx: Ensure init is completed before system sleep [Test] Verified on the machine with FM350 wwan module. [Where problems could occur] If the wwan is not ready before the time is up, it results in -ETIMEDOUT. However, in this scenario, we will encounter the same issue where the system fails to enter suspend mode. Therefore, it will not introduce regressions or new issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020743/+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 2022354] Re: sysfs msi_irqs directory empty with kernel-5.19 when being a xen guest
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2022354 Title: sysfs msi_irqs directory empty with kernel-5.19 when being a xen guest Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Committed Bug description: == SRU Justification == Impact: See below Fix: Upstream commit from v6.4-rc4 cherry-picked into 5.19 and 6.2 Test case: Check of sysfs running Xen. Regression potential: Change adds additional calls to populate sysfs related to MSI devices. Any issues would be withing those limits. --- Original Description --- Let's say you launch a Xen-based EC2 instance with enhanced networking, then under kernel-5.19 you'll not see anything under $ ls /sys/class/net/ens3/device/msi_irqs/ This can be fixed by backporting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=335b4223466dd75f9f3ea4918187afbadd22e5c8 (It got already backported to 6.1 and 6.3) With this patch applied, you'll correctly see the sysfs files: $ ls /sys/class/net/ens3/device/msi_irqs/ 690 691 692 693 694 695 696 697 698 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022354/+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 2023197] Re: Fix speaker volume too low on HP G10 laptops
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2023197 Title: Fix speaker volume too low on HP G10 laptops Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete 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: New Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [ Impact ] HP G10 laptops need the quirk ALC245_FIXUP_CS35L41_SPI_4_HP_GPIO_LED to enable all amplifiers to output audio with expected level. [ Test Plan ] * Power up the HP G10 series laptops and adjust the output volume to MAX * Verify speaker output volume by ears. [ Where problems could occur ] * The quirk is for Cirrus codec on particular HP series laptops. * The risk of regression should only impact particular models To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023197/+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 2026776] Re: arm64+ast2600: No Output from BMC's VGA port
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2026776 Title: arm64+ast2600: No Output from BMC's VGA port Status in linux package in Ubuntu: Triaged Status in linux-hwe-5.19 package in Ubuntu: Won't Fix Status in linux-hwe-6.2 package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux-hwe-5.19 source package in Jammy: Won't Fix Status in linux-hwe-6.2 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification: [ Impact ] On systems that have the following combination of hardware 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ No output when connecting a display to the BMC's VGA port. [ Fix ] For AST2500+ MMIO should be enabled by default. [ Test Plan ] Test on targeted hardware to make sure BMC is displaying output. [ Where problems could occur ] Not aware of any potential problems, but any should be confined to ASPEED AST2500+ hardware. [ Other Info ] Patch is already in jammy/nvidia-5.19 and jammy/nvidia-6.2 and has been tested with affected BMC. [Issue] On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6=4327a6137ed43a091d900b1ac833345d60f32228 [Action] Please apply the following two backports to the appropriate Ubuntu HWE kernels: https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026776/+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 2024273] Re: Fix eDP only displays 3/4 area after switching to mirror mode with external HDMI 4K monitor
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2024273 Title: Fix eDP only displays 3/4 area after switching to mirror mode with external HDMI 4K monitor Status in HWE Next: New 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: Incomplete 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: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Panel on laptops connect to some 4K monitors via HDMI only display 3/4 area on eDP after switching to mirror mode. [Fix] Backport a fix from Intel on https://cgit.freedesktop.org/drm-tip/commit/?id=a2da67028cd05516343533c1609fcaf037237fed. [Test] 1. Power on the laptop 2. Connect a 4K monitor (4k Benq EL2870U, 4k HP z27Kg3, 2k ASUS PA27AC) to the laptop with HDMI cable. 3. Switch to mirror mode from default Joint Mode 4. Verify there's no obvious blank space on the leftmost/rightmost side of the laptop's panel. [Where problems could occur] Only observed after connecting with some particular 4K monitors. It's a generic fix to accept arbitrary refresh rate for more advanced panels. Should be low risk to old machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024273/+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 2023638] Re: Various backlight issues with the 6.0/6.1 kernel
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2023638 Title: Various backlight issues with the 6.0/6.1 kernel Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 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.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] There are some new patches for new method to decide which backlight driver should be registered introduced since 6.1. And we backport some of them to 6.0-oem kernel which are not enough to solved all backlight issues. 1. dell_laptop created a non-working backlight driver before nvidia is loaded, that leads to the system can't adjust the display brightness. 2. acpi_backlight0 sometimes will be generated together with intel_backlight. [Fix] Below 2 commits from v6.3-rc6 prevent the acpi_backlight from being registered automatically(which have been included into ubuntu kernels through stable update) e506731c8f35 ACPI: video: Make acpi_backlight=video work independent from GPU driver 78dfc9d1d1ab ACPI: video: Add auto_detect arg to __acpi_video_get_backlight_type() Below patch prevents platform driver(dell_laptop) from creating backlight driver after win8. aa8a950a5d6b ACPI: video: Stop trying to use vendor backlight control on laptops from after ~2012 https://patchwork.kernel.org/project/linux-acpi/patch/20230608091258.7963-1-hdego...@redhat.com/ [Test] Verified on the dell platform which reports this issue. [Where problems could occur] The assumption of the not-yet-upstreamed commit regarding backlight control is that, after Windows 8, all laptop backlights are controlled either by ACPI or the native graphics driver. It impacts the laptops that do not follow the assumption and will lead to broken backlight interface. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023638/+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 2027773] Re: UBSAN: shift-out-of-bounds in amd_sfh
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5
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-starfive' to 'verification-done-
lunar-linux-starfive'. If the problem still exists, change the tag
'verification-needed-lunar-linux-starfive' to 'verification-failed-
lunar-linux-starfive'.
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-starfive-v2
verification-needed-lunar-linux-starfive
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2027773
Title:
UBSAN: shift-out-of-bounds in amd_sfh
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.0 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.0 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.0 source package in Lunar:
Invalid
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.0 source package in Mantic:
Invalid
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
UBSAN: shift-out-of-bounds in
drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c:149:50
[ 7.928631] shift exponent 103 is too large for 64-bit type 'long unsigned
int'
[ 9.877309] Workqueue: events amd_sfh_work_buffer \[amd_sfh]
[ 9.877327] Call Trace:
[ 9.877331] \
[ 9.877335] dump_stack_lvl+0x49/0x63
[ 9.877346] dump_stack+0x10/0x16
[ 9.877348] ubsan_epilogue+0x9/0x36
[ 9.877357] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
[ 9.877363] ? _raw_spin_lock+0x17/0x50
[ 9.877369] ? raw_spin_rq_lock_nested+0x2e/0xa0
[ 9.877378] ? psi_group_change+0x1e2/0x4a0
[ 9.877385] float_to_int.cold+0x18/0xc8 \[amd_sfh]
[ 9.877394] ? get_feature_rep+0xb0/0xb0 \[amd_sfh]
[ 9.877402] get_input_rep+0x219/0x2f0 \[amd_sfh]
[ 9.877409] ? up+0x37/0x70
[ 9.877414] ? hid_input_report+0x104/0x170 \[hid]
[ 9.877428] amd_sfh_work_buffer+0x94/0x150 \[amd_sfh]
[ 9.877436] process_one_work+0x21f/0x3f0
[ 9.877443] worker_thread+0x50/0x3e0
[ 9.877446] ? process_one_work+0x3f0/0x3f0
[ 9.877449] kthread+0xfd/0x130
[ 9.877452] ? kthread_complete_and_exit+0x20/0x20
[ 9.877454] ret_from_fork+0x22/0x30
[ 9.877463] \
[Fix]
Fixes in:
* commit c1685a862a4b ("HID: amd_sfh: Rename the float32 variable")
* commit 878543661764 ("HID: amd_sfh: Fix for shift-out-of-bounds")
[Test Case]
The affected platform should no longer has such error dumped in kernel dmesg
at
boot.
[Where problems could occur]
This renamed a variable and corrected the way shift offset is calculated. No
known side effect.
[Other Info]
The affects kernel >= v6.0 and < v6.5, so Unstable/Mantis/Lunar/OEM-6.1 are
nominated for fix.
== original bug report ==
UBSAN: shift-out-of-bounds in
drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c:149:50
[ 7.928631] shift exponent 103 is too large for 64-bit type 'long unsigned
int'
[ 9.877309] Workqueue: events amd_sfh_work_buffer [amd_sfh]
[ 9.877327] Call Trace:
[ 9.877331]
[ 9.877335] dump_stack_lvl+0x49/0x63
[ 9.877346] dump_stack+0x10/0x16
[ 9.877348] ubsan_epilogue+0x9/0x36
[ 9.877357] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
[ 9.877363] ? _raw_spin_lock+0x17/0x50
[ 9.877369] ? raw_spin_rq_lock_nested+0x2e/0xa0
[ 9.877378] ? psi_group_change+0x1e2/0x4a0
[ 9.877385] float_to_int.cold+0x18/0xc8 [amd_sfh]
[ 9.877394] ? get_feature_rep+0xb0/0xb0 [amd_sfh]
[ 9.877402] get_input_rep+0x219/0x2f0 [amd_sfh]
[ 9.877409] ? up+0x37/0x70
[ 9.877414] ? hid_input_report+0x104/0x170 [hid]
[ 9.877428] amd_sfh_work_buffer+0x94/0x150 [amd_sfh]
[ 9.877436] process_one_work+0x21f/0x3f0
[ 9.877443] worker_thread+0x50/0x3e0
[ 9.877446] ? process_one_work+0x3f0/0x3f0
[ 9.877449] kthread+0xfd/0x130
[ 9.877452] ? kthread_complete_and_exit+0x20/0x20
[ 9.877454] ret_from_fork+0x22/0x30
[ 9.877463]
Fixes in:
https://github.com/torvalds/linux/commit/c1685a862a4bea863537f06abaa37a123aef493c
https://github.com/torvalds/linux/commit/87854366176403438d01f368b09de3ec2234e0f5
This affects kernel >= v6.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2027773/+subscriptions
--
Mailing
[Kernel-packages] [Bug 2027957] Re: Fix AMDGPU: the screen freeze with W7500
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in HWE Next: New 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Invalid 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: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. [Misc] 1. jammy, amdgpu isn't loaded on this platform with 5.15-73-generic. 2. kinetic, amdgpu failed to probe the vga controller with 5.19-46-generic. 3. Passed cbd build against Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027957/+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 2028740] Re: Fix AMD gpu hang when screen off/on
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2028740 Title: Fix AMD gpu hang when screen off/on Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released 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: Invalid 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] AMD GPU hang when screen off/on. error log: kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3 [Fix] Keep a PHY active when detecting DP signal + DPMS active. [Test] Tested on 3 AMD platforms, GPU works fine. [Where problems could occur] Low risk, the fix is in v6.4-rc1. Generic Jammy kernel doesn't need this commit because of no support of AMD Phoenix GPU. SRU for Lunar/oem-6.1 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028740/+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 2028746] Re: Fix UBSAN in Intel EDAC driver
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2028746 Title: Fix UBSAN in Intel EDAC driver 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 Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Bug description: [Impact] UBSAN complains shift-out-of-bounds: [ 13.875276] UBSAN: shift-out-of-bounds in drivers/edac/skx_common.c:369:16 [ 13.875279] shift exponent -66 is negative [Fix] Skip the absent memory controllers so ~0 won't be used. [Test] Boot system with patch applied, no more UBSAN error in dmesg. [Where problems could occur] The fix itself is trivial, however the dependency patches may bring behavioural changes as new platform support is also added. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028746/+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 2028749] Re: Make TTY switching possible for NVIDIA when it's boot VGA
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2028749 Title: Make TTY switching possible for NVIDIA when it's boot VGA Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Incomplete 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] TTY switching is not possible on some workstations when iGPU is present and NVIDIA GFX is boot VGA. On that case, fbdev /dev/fb* is not created. [Fix] Find the correct boot VGA and remove overlapped aperture (BAR), so fbdev can be created properly. [Test] Once the fix gets applied, /dev/fb0 is present and TTY switching works. [Where problems could occur] The fix is a major overhaul over resource management on video apertures (BAR), so the boot VGA discovery might change and different aperture might be evicted. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028749/+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 2029138] Re: cifs: fix mid leak during reconnection after timeout threshold
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2029138 Title: cifs: fix mid leak during reconnection after timeout threshold Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-azure source package in Jammy: In Progress Status in linux source package in Lunar: Fix Committed Status in linux-azure source package in Lunar: Fix Released Bug description: SRU Justification [Impact] A regression in the Ubuntu 5.15 kernel has been causing problems for multiple customers on Azure. This bug has been fixed in the mainline kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69cba9d3c1284e0838ae408830a02c4a063104bc [Test Plan] Microsoft tested [Regression Potential] Reconnections could fail. [Other Info] SF: #00365185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029138/+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 2029199] Re: NULL pointer dereference on CS35L41 HDA AMP
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2029199 Title: NULL pointer dereference on CS35L41 HDA AMP 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-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: New 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 Bug description: [Impact] NULL pointer dereference happens because the HDA driver is trying to use CS35L41 HDA AMP before its probe routine is fully realized. [Fix] Use device link to enforce proper probe order. Since the fixing commit is part of a patch series, pull in the entire series which has several other important fixes too. [Test] Use dmesg to see if there's error. With the fix applied, no more kernel splat can be found. Hence the system can perform suspend, reboot and shutdown normally. [Where problems could occur] Though the entire series isn't trivia, it's not a major overhaul either. The entire changeset is limited to CS35L41 AMP, so the scope of regression risk is constrained. One possible risk factor is that it may require newer DSP firmware, and we'll monitor it closely on such scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2029199/+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 2029332] Re: Reboot command powers off the system
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2029332 Title: Reboot command powers off the system 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: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: [Impact] Issue: When a reboot (or init 6) command is issued the server shuts down instead. Expected behaviour: To reboot and NOT shutdown Impacted HW: HPE DL 380 OR Synergy 480 Gen 10 Plus Server 2P core count greater than 16 (like 24,28 or 32) Impacted OS: Ubuntu 22.04.2 kernel higher than 15.17.15 When the CPU count is 1, issue is not observed. When core count is less than 24 (like 16) issue not observed. [Fix] Problem introduced in v5.18 with commit: 08f253ec3767 x86/cpu: Clear SME feature flag when not in use Fixes for the above:0 9b040453d444 x86/smp: Dont access non-existing CPUID leaf 1f5e7eb7868e x86/smp: Make stop_other_cpus() more robust [Test Case] $ sudo reboot Server should reboot and not power off. [Where Problems Could Occur] The fixes modify x86 stop-CPU code so reboot/poweroff of x86 machines could be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029332/+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 2031093] Re: libgnutls report "trap invalid opcode" when trying to install packages over https
This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 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-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. 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-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2031093 Title: libgnutls report "trap invalid opcode" when trying to install packages over https Status in ubuntu-kernel-tests: New Status in gnutls28 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in gnutls28 source package in Focal: Confirmed Status in linux source package in Focal: Fix Released Status in gnutls28 source package in Jammy: Confirmed Status in linux source package in Jammy: Fix Released Status in gnutls28 source package in Lunar: Confirmed Status in linux source package in Lunar: Fix Released Bug description: [Impact] When booting linux with Gather Data Sampling mitigations without updated microcode on an affected CPU, AVX will be disabled. This will cause programs connecting to https using gnutls on Jammy to break, including apt and git. [Test case] git clone https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] Works fine with the mitigation disabled by default. [Potential regressions] Users booting on affected parts without microcode updates will be subject to Gather Data Sampling attacks (which can be done by local untrusted attackers), which may leak confidential data, including keys. - When trying to install linux-libc-dev on Oracle BM.Standard2.52 (seems to be the only affected instance) with Jammy 5.15.0-81-generic, it will get interrupted with: E: Method https has died unexpectedly! E: Sub-process https received signal 4. $ sudo apt install linux-libc-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-libc-dev 0 upgraded, 1 newly installed, 0 to remove and 54 not upgraded. Need to get 1353 kB of archives. After this operation, 6943 kB of additional disk space will be used. E: Method https has died unexpectedly! E: Sub-process https received signal 4. From dmesg you will see: [ 1078.750067] traps: https[4572] trap invalid opcode ip:7f3c1e6316be sp:7ffea26b61c0 error:0 in libgnutls.so.30.31.0[7f3c1e50f000+129000] Also, git clone is not working as well. $ git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] libgnutls30 version:3.7.3-4ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031093/+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 2025079] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5698009/+files/acpidump.txt ** Description changed: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor + - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) - --- + --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: - linux-restricted-modules-6.2.0-32-generic N/A - linux-backports-modules-6.2.0-32-generic N/A - linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 + linux-restricted-modules-6.2.0-32-generic N/A + linux-backports-modules-6.2.0-32-generic N/A + linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. -- 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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun
[Kernel-packages] [Bug 2025079] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5698006/+files/RfKill.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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5698005/+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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5698008/+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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5698007/+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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5698003/+files/ProcEnviron.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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5698004/+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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5698001/+files/ProcCpuinfo.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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5698002/+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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5698000/+files/Lsusb-v.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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5697999/+files/Lsusb-t.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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5697998/+files/Lsusb.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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5697997/+files/Lspci-vt.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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5697996/+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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5697995/+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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5697994/+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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5697993/+files/AudioDevicesInUse.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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2025079] Re: [amdgpu] Multiple kernel errors and reboot
apport information ** Tags added: apport-collected ** Description changed: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) + --- + ProblemType: Bug + ApportVersion: 2.26.1-0ubuntu2 + Architecture: amd64 + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 23.04 + InstallationDate: Installed on 2023-04-13 (145 days ago) + InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) + MachineType: Dell Inc. Inspiron 5415 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 + RelatedPackageVersions: + linux-restricted-modules-6.2.0-32-generic N/A + linux-backports-modules-6.2.0-32-generic N/A + linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 + Tags: lunar wayland-session + Uname: Linux 6.2.0-32-generic x86_64 + UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) + UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark + _MarkForUpload: True + dmi.bios.date: 02/13/2023 + dmi.bios.release: 1.15 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.15.0 + dmi.board.name: 0WKFHK + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: 1.15.0 + dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 5415 + dmi.product.sku: 0A77 + dmi.product.version: 1.15.0 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2025079/+attachment/5697992/+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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21
[Kernel-packages] [Bug 2034584] 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 2034584 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/2034584 Title: F8 and F9 keys are disabled Status in linux package in Ubuntu: Incomplete Bug description: Kernel 6.2.0-25 up to 6.2.0-32 F8 and F9 keys are disabled (using now 5.15.0-83 - as also touchpad stopped working in kernel 6.2.0-32, as another user has already reported). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034584/+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 2034584] [NEW] F8 and F9 keys are disabled
Public bug reported: Kernel 6.2.0-25 up to 6.2.0-32 F8 and F9 keys are disabled (using now 5.15.0-83 - as also touchpad stopped working in kernel 6.2.0-32, as another user has already reported). ** 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/2034584 Title: F8 and F9 keys are disabled Status in linux package in Ubuntu: Incomplete Bug description: Kernel 6.2.0-25 up to 6.2.0-32 F8 and F9 keys are disabled (using now 5.15.0-83 - as also touchpad stopped working in kernel 6.2.0-32, as another user has already reported). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034584/+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 2029390] Re: [23.10 FEAT] [SEC2352] pkey: support EP11 API ordinal 6 for secure guests
Kernel test build(s) available in this PPA: https://launchpad.net/~fheimes/+archive/ubuntu/lp2028937+lp2029390 Pull request submitted to kernel team's mailing list: https://lists.ubuntu.com/archives/kernel-team/2023-September/thread.html#142534 Changing status to 'In Progress'. Assigning to kernel team. @kernel-team Please notice that the PR for LP: 2028937 needs to be applied first (to mantic's 6.5) to get this cherry-pick in (without conflicts)! (I've mentioned that also in the cover-letter.) ** Changed in: ubuntu-z-systems Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/2029390 Title: [23.10 FEAT] [SEC2352] pkey: support EP11 API ordinal 6 for secure guests Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: Secure Execution guests must use the EP11 API ordinal 6 to create (generate, unwrap, derive) secure keys which encodes a NULL PIN (no session) as a string of zero-bytes. Therefore, the pkey module must be updated to check whether the Linux system is running as a secure guest and if so modify secure key creating requests (key(pair) gen, unwrap) to use ordinal 6 API. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2029390/+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 1956104] Re: firmware-sof description is inaccurate and misleading
** Tags removed: ubuntu-22.04 ** Tags added: packaging ** Description changed: - Package description says Intel firmware. + Package description says Intel systems. https://thesofproject.github.io/latest/platforms/index.html https://www.cadence.com/en_US/home/tools/ip/tensilica-ip/tensilica- xtensa-controllers-and-extensible-processors.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1956104 Title: firmware-sof description is inaccurate and misleading Status in firmware-sof package in Ubuntu: Confirmed Bug description: Package description says Intel systems. https://thesofproject.github.io/latest/platforms/index.html https://www.cadence.com/en_US/home/tools/ip/tensilica-ip/tensilica- xtensa-controllers-and-extensible-processors.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1956104/+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 2034578] [NEW] Support IPSEC full offload implementation
Public bug reported: Summary: Align Kernel IPsec Full offload implementation in the DPU to the upstream Full offload in all components: OFED, Strongswan, etc. This is in order for DPU Kernel IPsec to include policy offload and be fully aligned to what CX Kernel customers will use. How to test: Host 1: /opt/mellanox/iproute2/sbin/devlink dev eswitch set pci/:03:00.0 mode legacy echo 'dmfs' > /sys/bus/pci/devices/:03:00.0/net/p0/compat/devlink/steering_mode echo 'full' > /sys/class/net/p0/compat/devlink/ipsec_mode /opt/mellanox/iproute2/sbin/devlink dev eswitch set pci/:03:00.0 mode switchdev BF on host 1: /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.181.165 dst 196.234.182.166 dir out tmpl src 196.234.181.165/16 dst 196.234.182.166/16 proto esp reqid 0xefa83812 mode transport priority 10 /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.182.166 dst 196.234.181.165 dir in tmpl src 196.234.182.166/16 dst 196.234.181.165/16 proto esp reqid 0x63a7db74 mode transport priority 10 /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.182.166 dst 196.234.181.165 dir fwd tmpl src 196.234.182.166/16 dst 196.234.181.165/16 proto esp reqid 0x63a7db74 mode transport priority 10 /opt/mellanox/iproute2/sbin/ip xfrm state add src 196.234.181.165/16 dst 196.234.182.166/16 proto esp spi 0xefa83812 reqid 0xefa83812 mode transport aead 'rfc4106(gcm(aes))' 0xe2fe3857301d8f72b5d71d295a462ef21868e407 128 offload packet dev p0 dir out sel src 196.234.181.165/16 dst 196.234.182.166/16 flag esn replay-window 32 /opt/mellanox/iproute2/sbin/ip xfrm state add src 196.234.182.166/16 dst 196.234.181.165/16 proto esp spi 0x63a7db74 reqid 0x63a7db74 mode transport aead 'rfc4106(gcm(aes))' 0xe916c4d0db1886e8c877b023e8cebef53b4d2d0f 128 offload packet dev p0 dir in sel src 196.234.182.166/16 dst 196.234.181.165/16 flag esn replay-window 32 Start OVS and set following configure on BF: /usr/bin/ovs-vsctl set Open_vSwitch . other_config:hw-offload=true /usr/bin/ovs-vsctl set Open_vSwitch . other_config:max-idle=30 Host2: /opt/mellanox/iproute2/sbin/devlink dev eswitch set pci/:03:00.1 mode legacy echo 'dmfs' > /sys/bus/pci/devices/:03:00.1/net/p1/compat/devlink/steering_mode echo 'full' > /sys/class/net/p1/compat/devlink/ipsec_mode /opt/mellanox/iproute2/sbin/devlink dev eswitch set pci/:03:00.1 mode switchdev BF on host 2: /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.182.166 dst 196.234.181.165 dir out tmpl src 196.234.182.166/16 dst 196.234.181.165/16 proto esp reqid 0xefa83812 mode transport priority 10 /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.181.165 dst 196.234.182.166 dir in tmpl src 196.234.181.165/16 dst 196.234.182.166/16 proto esp reqid 0x63a7db74 mode transport priority 10 /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.181.165 dst 196.234.182.166 dir fwd tmpl src 196.234.181.165/16 dst 196.234.182.166/16 proto esp reqid 0x63a7db74 mode transport priority 10 /opt/mellanox/iproute2/sbin/ip xfrm state add src 196.234.181.165 dst 196.234.182.166 proto esp spi 0xefa83812 reqid 0xefa83812 mode transport aead 'rfc4106(gcm(aes))' 0xe2fe3857301d8f72b5d71d295a462ef21868e407 128 offload packet dev p0 dir out sel src 196.234.181.165/16 dst 196.234.182.166/16 flag esn replay-window 32 /opt/mellanox/iproute2/sbin/ip xfrm state add src 196.234.181.165 dst 196.234.182.166 proto esp spi 0x63a7db74 reqid 0x63a7db74 mode transport aead 'rfc4106(gcm(aes))' 0xe916c4d0db1886e8c877b023e8cebef53b4d2d0f 128 offload packet dev p0 dir in sel src 196.234.181.165/16 dst 196.234.182.166/16 flag esn replay-window 32 Start OVS and set following configure on BF: /usr/bin/ovs-vsctl set Open_vSwitch . other_config:hw-offload=true /usr/bin/ovs-vsctl set Open_vSwitch . other_config:max-idle=30 Send the traffic between host 1 and host 2 and check IPsec counters in "ethtool -S" statistics on both BF. How to fix: Need to backport a series of xfrm patches into BlueField 5.15 kernel, from 6.0 upstream kernel. Patches needed for 5.15 kernel: afe9e47 xfrm: fix conflict for netdev and tx stats 6aff54d xfrm: don't skip free of empty state in acquire policy 692fecb xfrm: delete offloaded policy 91b6276 xfrm: Support UDP encapsulation in packet offload mode 69e168a xfrm: add missed call to delete offloaded policies 9724724 xfrm: release all offloaded policy memory e57b7ec xfrm: don't require advance ESN callback for packet offload 9e98488 xfrm: copy_to_user_state fetch offloaded SA packets/bytes statistics 4778c10 xfrm: add new device offload acquire flag 2601c94 netlink: provide an ability to set default extack message b4951d5 netlink: add support for formatted extack messages b5dd0fa xfrm: extend add state callback to set failure reason 326a004 xfrm: extend add policy callback to set failure reason 40b173d1 xfrm: document IPsec packet offload mode b1737ae xfrm: add support to HW update soft and hard limits cad4cd7 xfrm: speed-up
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.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 2022361] Re: Please enable Renesas RZ platform serial installer
Hi,
Is the bug awaiting verification from me who raised this issue or from
Ubuntu internal testing?
For me to verify this on Renesas platform, I need iso installer image
for arm64. Is there an iso image with this changes for arm64 to test
please. Thanks
Best Regards
John
--
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 Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
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 2025079] Re: [amdgpu] Multiple kernel errors and reboot
It still crashes if I press "Super" key to view Activities overview (for example to pick a window to share which is very common use case 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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Incomplete Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2034510] Re: spl fails to unregister sysctl entries
** Changed in: zfs-linux (Ubuntu Mantic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2034510 Title: spl fails to unregister sysctl entries Status in zfs-linux package in Ubuntu: Fix Committed Status in zfs-linux source package in Mantic: Fix Committed Bug description: [Impact] On unload the spl module is not properly cleaning up the registered sysctl entries with kernel 6.5 in Mantic: 06:58 ubuntu@mantic$ sudo modprobe spl modprobe: ERROR: could not insert 'spl': Protocol driver not attached 06:58 ubuntu@mantic$ sudo dmesg | grep duplicate [ 152.587197] sysctl duplicate entry: /kernel/spl/kmem/slab_kvmem_total [Test case] Uninstall zfsutils-linux and try to `modprobe -r zfs; modprobe -r spl`, then `modprobe zfs` again and you should see the error (with a failure to load spl again). At this point it is possible to load spl again only after a reboot. [Fix] Properly cleanup all the registered sysctl entries when the spl module is unloaded. [Regression potential] We may experience regressions in systems that are using zfs with the 6.5 kernel. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: zfs-dkms 2.2.0~rc3-0ubuntu3 ProcVersionSignature: User Name 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230823 CloudSubPlatform: config-disk (/dev/vdb) Date: Wed Sep 6 07:06:33 2023 PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2034510/+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 2034557] [NEW] Azure: Improve MANA Rx performance
*** This bug is a duplicate of bug 2034277 ***
https://bugs.launchpad.net/bugs/2034277
Public bug reported:
SRU Justification
[Impact]
With iperf and 128 threads test, this patch improved the throughput
by 12-15%, and decreased the IRQ associated CPU's usage from 99-100% to
10-50%.
commit b1d13f7a3b5396503e6869ed627bb4eeab9b524f ('net: mana: Add page
pool for RX buffers')
[Test Plan]
Microsoft tested
[Regression Potential]
Rx buffers could get orphaned.
[Other Info]
SF: #00365760
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux (Ubuntu Lunar)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux (Ubuntu Lunar)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** This bug has been marked a duplicate of bug 2034277
Azure: net: mana: Add page pool for RX buffers
--
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/2034557
Title:
Azure: Improve MANA Rx performance
Status in linux package in Ubuntu:
New
Status in linux source package in Jammy:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux source package in Mantic:
New
Bug description:
SRU Justification
[Impact]
With iperf and 128 threads test, this patch improved the throughput
by 12-15%, and decreased the IRQ associated CPU's usage from 99-100% to
10-50%.
commit b1d13f7a3b5396503e6869ed627bb4eeab9b524f ('net: mana: Add page
pool for RX buffers')
[Test Plan]
Microsoft tested
[Regression Potential]
Rx buffers could get orphaned.
[Other Info]
SF: #00365760
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034557/+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/6.2.0-34.34 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/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 Committed 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 2021572] Re: dGPU cannot resume because system firmware stuck in IPCS method
This bug is awaiting verification that the linux/6.2.0-34.34 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/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 Committed 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/6.2.0-34.34 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/2022361
Title:
Please enable Renesas RZ platform serial installer
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
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 2028122] Re: Fix unreliable ethernet cable detection on I219 NIC
This bug is awaiting verification that the linux/6.2.0-34.34 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/2028122 Title: Fix unreliable ethernet cable detection on I219 NIC 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 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] 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/6.2.0-34.34 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/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 Committed Status in linux source package in Lunar: Fix Committed 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 2032767] Re: Fix ACPI TAD on some Intel based systems
This bug is awaiting verification that the linux/6.2.0-34.34 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/2032767 Title: Fix ACPI TAD on some Intel based systems 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-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 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: Confirmed 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/6.2.0-34.34 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/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 Committed Status in linux source package in Lunar: Fix Committed 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 : https://help.launchpad.net/ListHelp
