[Kernel-packages] [Bug 2038876] [NEW] package linux-firmware 20220329.git681281e4-0ubuntu3.19 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned e
Public bug reported: I have made an older version of the kernel immutable to prevent its deletion, because the newer kernels will not boot. This has the side effect of preventing hardlinks, which caused an error message. I don't know if this is related. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.19 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kevin 4659 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown Date: Mon Oct 9 21:45:10 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-04-01 (556 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dynabook Inc. dynabook TECRA A50-F PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=1306d535-dd60-4b0c-91b2-d152242759e3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.19 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-07-05 (96 days ago) dmi.bios.date: 06/21/2021 dmi.bios.release: 2.50 dmi.bios.vendor: Dynabook Inc. dmi.bios.version: Version 2.50 dmi.board.asset.tag: 00 dmi.board.name: A0105/ dmi.board.vendor: Dynabook Inc. dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: Dynabook Inc. dmi.chassis.version: Version 1.0 dmi.ec.firmware.release: 1.90 dmi.modalias: dmi:bvnDynabookInc.:bvrVersion2.50:bd06/21/2021:br2.50:efr1.90:svnDynabookInc.:pndynabookTECRAA50-F:pvrPT5B1U-01K006:rvnDynabookInc.:rnA0105/:rvrVersionA0:cvnDynabookInc.:ct10:cvrVersion1.0:skuPT5B1U: dmi.product.family: dynabook TECRA dmi.product.name: dynabook TECRA A50-F dmi.product.sku: PT5B1U dmi.product.version: PT5B1U-01K006 dmi.sys.vendor: Dynabook Inc. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- 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/2038876 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.19 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: I have made an older version of the kernel immutable to prevent its deletion, because the newer kernels will not boot. This has the side effect of preventing hardlinks, which caused an error message. I don't know if this is related. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.19 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kevin 4659 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown Date: Mon Oct 9 21:45:10 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-04-01 (556 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dynabook Inc. dynabook TECRA A50-F PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=1306d535-dd60-4b0c-91b2-d152242759e3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.19 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-07-05 (96 days ago) dmi.bios.date:
[Kernel-packages] [Bug 2038813] Re: Nvidia Driver External Display Stability Issues
This is usually a problem with display connection quality. Please try a different HDMI cable. Also next time the problem happens please run: journalctl -b0 > journal.txt grep . /sys/class/drm/*/status > connections.txt sudo apt install drm-info drm_info > drminfo.txt and attach the resulting text files here. ** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu) ** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038813 Title: Nvidia Driver External Display Stability Issues Status in linux-hwe-6.2 package in Ubuntu: New Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: When using an external HDMI monitor, the screen frequently goes blank for a few seconds. This only happens with the external monitor and not the integral screen of the laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.104.12 Wed Sep 20 09:35:17 UTC 2023 GCC version: gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 10:30:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0c00] Subsystem: Dell Device [1028:0c00] InstallationDate: Installed on 2023-09-07 (31 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Latitude 5440 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-34-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2023 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0CDJ5X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: IT099142 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd07/12/2023:br1.6:efr1.3:svnDellInc.:pnLatitude5440:pvr:rvnDellInc.:rn0CDJ5X:rvrA00:cvnDellInc.:ct10:cvr:sku0C00: dmi.product.family: Latitude dmi.product.name: Latitude 5440 dmi.product.sku: 0C00 dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: An internal driver error occurred version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2038813/+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 2038813] [NEW] Nvidia Driver External Display Stability Issues
You have been subscribed to a public bug: When using an external HDMI monitor, the screen frequently goes blank for a few seconds. This only happens with the external monitor and not the integral screen of the laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.104.12 Wed Sep 20 09:35:17 UTC 2023 GCC version: gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 10:30:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0c00] Subsystem: Dell Device [1028:0c00] InstallationDate: Installed on 2023-09-07 (31 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Latitude 5440 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-34-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2023 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0CDJ5X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: IT099142 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd07/12/2023:br1.6:efr1.3:svnDellInc.:pnLatitude5440:pvr:rvnDellInc.:rn0CDJ5X:rvrA00:cvnDellInc.:ct10:cvr:sku0C00: dmi.product.family: Latitude dmi.product.name: Latitude 5440 dmi.product.sku: 0C00 dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: An internal driver error occurred version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- Nvidia Driver External Display Stability Issues https://bugs.launchpad.net/bugs/2038813 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. -- 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 2038867] Re: Linux firmware 1.7 prevents system with AMD 7900XT from booting
I'm having the same problem after updating to version 1.7. My desktop freezes before boot with a RX7900XT -- 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/2038867 Title: Linux firmware 1.7 prevents system with AMD 7900XT from booting Status in linux-firmware package in Ubuntu: New Bug description: I just upgraded my System76 Thelio running 23.04 with a Navi 31 [Radeon RX 7900 XT/7900 XTX] GPU. It seems this update causes my displays to freeze very early in the boot process. I see some basic messages and then some screen corruption and that is where the screen remains. I was able to ssh into it from another machine and downgrade the linux-firmware package to 1.6 which fixed the display freeze problem. The problem package is 20230323.gitbcdcfbcf-0ubuntu1.7 Reverting to 20230323.gitbcdcfbcf-0ubuntu1.6 fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038867/+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 2038745] Re: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed
@Juerg: Internal team looked at it, VP with Navi31 XTX boards, VNP with the others. So the testing with OEM-6.1/OEM-6.5 on other Navi31 from earlier bug is accurate. Confirmed that upgrading SMU binary (just dropped into /lib/firmware/updates/amdgpu) fixes the issue. Considering the regression impact; can we please roll this extra file out? -- 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/2038745 Title: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Confirmed Status in linux-firmware source package in Lunar: Confirmed Status in linux-firmware source package in Mantic: Fix Released Bug description: [Impact] NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to latest Ubuntu 22.04.3 kernel and firmware Not repro with NV21 XL or W6800 [Fix] Cherry-pick the latest PMFW https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin [Other Info] The IMU FW included in Linux firmware package needs to be paired with the latest PMFW smu_13_0_0.bin for Navi31 Jammy firmware updates only include latest IMU firmware. https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux- firmware 20220329.git681281e4-0ubuntu3.19 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin (Missing) https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745/+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 2038868] [NEW] gpio-mlxbf3: support valid mask
Public bug reported: SRU Justification: [Impact] After syncing up the gpio-mlxbf3.c driver with the upstreamed version, we dropped the use of the valid_mask variable because kernels greater or equal to 6.2.0 dont need it. This is no longer needed in kernel versions >= 6.2.0 because valid_mask is populated by core gpio code. 5.15 kernel doesnt support that feature so we still need to explicitly define valid_mask like we did before. This doesnt impact the functionality of the GPIO driver but it is a security breach as it doesnt restrict the access to only gpios defined in the acpi table by valid_mask. [Fix] * define valid_mask and init_valid_mask [Test Case] * Make sure that the user (libgpiod) cannot access any other gpio besides 0->4 (gpiochip0) and 22-23 in gpiochip1. [Regression Potential] no known regression. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- 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/2038868 Title: gpio-mlxbf3: support valid mask Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] After syncing up the gpio-mlxbf3.c driver with the upstreamed version, we dropped the use of the valid_mask variable because kernels greater or equal to 6.2.0 dont need it. This is no longer needed in kernel versions >= 6.2.0 because valid_mask is populated by core gpio code. 5.15 kernel doesnt support that feature so we still need to explicitly define valid_mask like we did before. This doesnt impact the functionality of the GPIO driver but it is a security breach as it doesnt restrict the access to only gpios defined in the acpi table by valid_mask. [Fix] * define valid_mask and init_valid_mask [Test Case] * Make sure that the user (libgpiod) cannot access any other gpio besides 0->4 (gpiochip0) and 22-23 in gpiochip1. [Regression Potential] no known regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2038868/+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 2038864] Re: 20230323.gitbcdcfbcf-0ubuntu1.7 hangs on boot with amdgpu
I just reported the same issue https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038867 -- 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/2038864 Title: 20230323.gitbcdcfbcf-0ubuntu1.7 hangs on boot with amdgpu Status in linux-firmware package in Ubuntu: Confirmed Bug description: [Impact] 20230323.gitbcdcfbcf-0ubuntu1.7 borks amdgpu during boot, it completely hangs the entire kernel on a RX 7900 XTX. Reverting back to 20230323.gitbcdcfbcf-0ubuntu1.2 made the kernel boot properly again. [Fix] Revert AMD firmware updates. [Test Case] Boot a machine with an affected AMD GPU. [Where Problems Could Occur] Machines with AMD GPUs might not boot or crash. This on Ubuntu 23.04 and 6.2.0-34-generic, but since the previous firmware worked I assume that the kernel version is not important here and it more is that the 1.7 update contains a firmware for the rx7900xtx that hangs it. Also booting to recovery and trying to enter non-graphical recovery mode worked just fine. This may be a very similar issue to https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2029396 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038864/+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 2038864] Re: 20230323.gitbcdcfbcf-0ubuntu1.7 hangs on boot with amdgpu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/2038864 Title: 20230323.gitbcdcfbcf-0ubuntu1.7 hangs on boot with amdgpu Status in linux-firmware package in Ubuntu: Confirmed Bug description: [Impact] 20230323.gitbcdcfbcf-0ubuntu1.7 borks amdgpu during boot, it completely hangs the entire kernel on a RX 7900 XTX. Reverting back to 20230323.gitbcdcfbcf-0ubuntu1.2 made the kernel boot properly again. [Fix] Revert AMD firmware updates. [Test Case] Boot a machine with an affected AMD GPU. [Where Problems Could Occur] Machines with AMD GPUs might not boot or crash. This on Ubuntu 23.04 and 6.2.0-34-generic, but since the previous firmware worked I assume that the kernel version is not important here and it more is that the 1.7 update contains a firmware for the rx7900xtx that hangs it. Also booting to recovery and trying to enter non-graphical recovery mode worked just fine. This may be a very similar issue to https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2029396 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038864/+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 2038867] [NEW] Linux firmware 1.7 prevents system with AMD 7900XT from booting
Public bug reported: I just upgraded my System76 Thelio running 23.04 with a Navi 31 [Radeon RX 7900 XT/7900 XTX] GPU. It seems this update causes my displays to freeze very early in the boot process. I see some basic messages and then some screen corruption and that is where the screen remains. I was able to ssh into it from another machine and downgrade the linux- firmware package to 1.6 which fixed the display freeze problem. The problem package is 20230323.gitbcdcfbcf-0ubuntu1.7 Reverting to 20230323.gitbcdcfbcf-0ubuntu1.6 fixes it. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/2038867 Title: Linux firmware 1.7 prevents system with AMD 7900XT from booting Status in linux-firmware package in Ubuntu: New Bug description: I just upgraded my System76 Thelio running 23.04 with a Navi 31 [Radeon RX 7900 XT/7900 XTX] GPU. It seems this update causes my displays to freeze very early in the boot process. I see some basic messages and then some screen corruption and that is where the screen remains. I was able to ssh into it from another machine and downgrade the linux-firmware package to 1.6 which fixed the display freeze problem. The problem package is 20230323.gitbcdcfbcf-0ubuntu1.7 Reverting to 20230323.gitbcdcfbcf-0ubuntu1.6 fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038867/+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 2038866] [NEW] package nvidia-kernel-common-535 535.113.01-0ubuntu3 failed to install/upgrade: installed nvidia-kernel-common-535 package post-installation script subprocess ret
Public bug reported: Nvidia crash ProblemType: Package DistroRelease: Ubuntu 23.10 Package: nvidia-kernel-common-535 535.113.01-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Mon Oct 9 21:22:52 2023 ErrorMessage: installed nvidia-kernel-common-535 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-09 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: nvidia-graphics-drivers-535 Title: package nvidia-kernel-common-535 535.113.01-0ubuntu3 failed to install/upgrade: installed nvidia-kernel-common-535 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2038866 Title: package nvidia-kernel-common-535 535.113.01-0ubuntu3 failed to install/upgrade: installed nvidia-kernel-common-535 package post- installation script subprocess returned error exit status 1 Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: Nvidia crash ProblemType: Package DistroRelease: Ubuntu 23.10 Package: nvidia-kernel-common-535 535.113.01-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Mon Oct 9 21:22:52 2023 ErrorMessage: installed nvidia-kernel-common-535 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-09 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: nvidia-graphics-drivers-535 Title: package nvidia-kernel-common-535 535.113.01-0ubuntu3 failed to install/upgrade: installed nvidia-kernel-common-535 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2038866/+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 2038864] Re: 20230323.gitbcdcfbcf-0ubuntu1.7 hangs on boot with amdgpu
Relevant information may be: c1:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch [1002:1478] (rev 10) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 38, NUMA node 0 Memory at d8e0 (32-bit, non-prefetchable) [size=16K] Bus: primary=c1, secondary=c2, subordinate=c3, sec-latency=0 I/O behind bridge: b000-bfff [size=4K] [16-bit] Memory behind bridge: d8c0-d8df [size=2M] [32-bit] Prefetchable memory behind bridge: 170-1780fff [size=33024M] [32-bit] Capabilities: Kernel driver in use: pcieport c2:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch [1002:1479] (rev 10) (prog-if 00 [Normal decode]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch [1002:1479] Flags: bus master, fast devsel, latency 0, IRQ 39, NUMA node 0 Bus: primary=c2, secondary=c3, subordinate=c3, sec-latency=0 I/O behind bridge: b000-bfff [size=4K] [16-bit] Memory behind bridge: d8c0-d8df [size=2M] [32-bit] Prefetchable memory behind bridge: 170-1780fff [size=33024M] [32-bit] Capabilities: Kernel driver in use: pcieport c3:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900 XTX] [1002:744c] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Device [148c:2422] Flags: bus master, fast devsel, latency 0, IRQ 94, NUMA node 0 Memory at 170 (64-bit, prefetchable) [size=32G] Memory at 178 (64-bit, prefetchable) [size=256M] I/O ports at b000 [size=256] Memory at d8c0 (32-bit, non-prefetchable) [size=1M] Expansion ROM at d8d0 [disabled] [size=128K] Capabilities: Kernel driver in use: amdgpu Kernel modules: amdgpu c3:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:ab30] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:ab30] Flags: bus master, fast devsel, latency 0, IRQ 111, NUMA node 0 Memory at d8d2 (32-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ** Attachment added: "lspci -vnn.txt" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038864/+attachment/5708064/+files/lspci%20-vnn.txt -- 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/2038864 Title: 20230323.gitbcdcfbcf-0ubuntu1.7 hangs on boot with amdgpu Status in linux-firmware package in Ubuntu: New Bug description: [Impact] 20230323.gitbcdcfbcf-0ubuntu1.7 borks amdgpu during boot, it completely hangs the entire kernel on a RX 7900 XTX. Reverting back to 20230323.gitbcdcfbcf-0ubuntu1.2 made the kernel boot properly again. [Fix] Revert AMD firmware updates. [Test Case] Boot a machine with an affected AMD GPU. [Where Problems Could Occur] Machines with AMD GPUs might not boot or crash. This on Ubuntu 23.04 and 6.2.0-34-generic, but since the previous firmware worked I assume that the kernel version is not important here and it more is that the 1.7 update contains a firmware for the rx7900xtx that hangs it. Also booting to recovery and trying to enter non-graphical recovery mode worked just fine. This may be a very similar issue to https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2029396 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038864/+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 2038864] [NEW] 20230323.gitbcdcfbcf-0ubuntu1.7 hangs on boot with amdgpu
Public bug reported: [Impact] 20230323.gitbcdcfbcf-0ubuntu1.7 borks amdgpu during boot, it completely hangs the entire kernel on a RX 7900 XTX. Reverting back to 20230323.gitbcdcfbcf-0ubuntu1.2 made the kernel boot properly again. [Fix] Revert AMD firmware updates. [Test Case] Boot a machine with an affected AMD GPU. [Where Problems Could Occur] Machines with AMD GPUs might not boot or crash. This on Ubuntu 23.04 and 6.2.0-34-generic, but since the previous firmware worked I assume that the kernel version is not important here and it more is that the 1.7 update contains a firmware for the rx7900xtx that hangs it. Also booting to recovery and trying to enter non- graphical recovery mode worked just fine. This may be a very similar issue to https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2029396 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/2038864 Title: 20230323.gitbcdcfbcf-0ubuntu1.7 hangs on boot with amdgpu Status in linux-firmware package in Ubuntu: New Bug description: [Impact] 20230323.gitbcdcfbcf-0ubuntu1.7 borks amdgpu during boot, it completely hangs the entire kernel on a RX 7900 XTX. Reverting back to 20230323.gitbcdcfbcf-0ubuntu1.2 made the kernel boot properly again. [Fix] Revert AMD firmware updates. [Test Case] Boot a machine with an affected AMD GPU. [Where Problems Could Occur] Machines with AMD GPUs might not boot or crash. This on Ubuntu 23.04 and 6.2.0-34-generic, but since the previous firmware worked I assume that the kernel version is not important here and it more is that the 1.7 update contains a firmware for the rx7900xtx that hangs it. Also booting to recovery and trying to enter non-graphical recovery mode worked just fine. This may be a very similar issue to https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2029396 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038864/+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 2038852] Re: Isotp driver causes timeout because of race condition during nonblocking writes
I cannot provide logs using apport. Please let me know if you need to
know how I am using this driver.
** 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/2038852
Title:
Isotp driver causes timeout because of race condition during
nonblocking writes
Status in linux package in Ubuntu:
Confirmed
Bug description:
This are my system details
Description:Ubuntu 20.04.6 LTS
Release:20.04
When using 5.15.133 kernel on Ubuntu 20.04. I am seeing that non blocking
writes cause race condition and locks the socket. This issue is resolved by a
patch from here
https://lore.kernel.org/linux-can/96d31e8c-fa26-4e32-4c36-768981f20...@hartkopp.net/T/#u.
This patch is supposed to make in the 6.7 kernel commit id 61caf48cf7 and I
would like it to be fixed for 5.15 stream as well. I have tested that this
patch when applied to 5.15.133 works. The patch cannot be directly applied but
a more comprehensive look at the current code at net/can/isotp.c. This is a
diff of my changes to isotp.c
119c119,120
< ISOTP_SENDING
---
> ISOTP_SENDING,
> ISOTP_SHUTDOWN,
873c874
< if (!so->bound)
---
> if (!so->bound|| so->tx.state == ISOTP_SHUTDOWN)
876,893c877,887
< /* we do not support multiple buffers - for now */
< if (cmpxchg(>tx.state, ISOTP_IDLE, ISOTP_SENDING) != ISOTP_IDLE ||
< wq_has_sleeper(>wait)) {
< if (msg->msg_flags & MSG_DONTWAIT) {
wait, so->tx.state ==
ISOTP_IDLE);
< if (err)
MAX_MSG_LENGTH) {
< err = -EINVAL;
< goto err_out_drop;
< }
---
> while (cmpxchg(>tx.state, ISOTP_IDLE, ISOTP_SENDING) !=
ISOTP_IDLE) {
> /* we do not support multiple buffers - for now */
> if (msg->msg_flags & MSG_DONTWAIT)
> return -EAGAIN;
> if (so->tx.state == ISOTP_SHUTDOWN)
> return -EADDRNOTAVAIL;
> /* wait for complete transmission of current pdu */
> err = wait_event_interruptible(so->wait, so->tx.state ==
ISOTP_IDLE);
> if (err)
>goto err_out;
> }
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038852/+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 2038859] [NEW] No driver for 14c3:7902
Public bug reported: I bought a new Asus Vivobook Notebook X1504ZA-NJ205 and installed ubuntu on it, but I couldn't use my wifi card: Network controller [0280]: MEDIATEK Corp. Device [14c3:7902]. After posting on that on the Ubuntu forum someone suggested me to file a bug report: https://ubuntuforums.org/showthread.php?t=2490705=14157764 so that's what I'm doing now. Can you please write a driver for this card? Thanks! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 21:51:08 2023 InstallationDate: Installed on 2023-09-08 (31 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RebootRequiredPkgs: Error: path contained symlinks. 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 wayland-session -- 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/2038859 Title: No driver for 14c3:7902 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: I bought a new Asus Vivobook Notebook X1504ZA-NJ205 and installed ubuntu on it, but I couldn't use my wifi card: Network controller [0280]: MEDIATEK Corp. Device [14c3:7902]. After posting on that on the Ubuntu forum someone suggested me to file a bug report: https://ubuntuforums.org/showthread.php?t=2490705=14157764 so that's what I'm doing now. Can you please write a driver for this card? Thanks! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 21:51:08 2023 InstallationDate: Installed on 2023-09-08 (31 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RebootRequiredPkgs: Error: path contained symlinks. 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/2038859/+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 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash
After installing via the legacy iso I saw the same message on login.
Opening a terminal and typing df I saw again the same message in the
terminal followed by the normal df output.
--
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/2038765
Title:
df: /sys/firmware/efi/efivars: Invalid argument causes installation
crash
Status in lightdm package in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
df: /sys/firmware/efi/efivars: Invalid argument appears on first
display of the live session - I note subsequently that at the end of
the installation curtin fails due to an efivars error - looking at
syslog I saw various efivars errors so I'm filing this with the kernel
since this is the first instance.
i.e. running grep efivars /var/log/*
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber
/dev/snd/seq:ubuntu-budgie 2074 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CasperVersion: 1.486
CurrentDesktop: Budgie:GNOME
Date: Sun Oct 8 16:27:29 2023
LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64
(20231008.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-7-generic N/A
linux-backports-modules-6.5.0-7-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/2038765/+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
Re: [Kernel-packages] [Bug 2031969] Re: Ubuntu 23.04: Suspend & Power off
I can confirm that in my case I was experiencing this problem on 22.04 so indeed both are affected. On Mon, Oct 9, 2023 at 1:55 AM Juerg Haefliger <2031...@bugs.launchpad.net> wrote: > The problem is with kernel 6.2 which is in both 23.04 and 22.04 (hwe) so > affects both releases. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2036368). > https://bugs.launchpad.net/bugs/2031969 > > Title: > Ubuntu 23.04: Suspend & Power off > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Since update to version 23.04 I am facing several problems related to > system suspend and shutdownon a HP Envy 15 notebook (2016). The system > refuses to wake up from standby mode, especially if it has run for a > longer time. Screen is black, no response to keyboard or trackpad > actions, power button led is on. The only way out of here is a long > press on the power button. > > Another problem with this and I think it's kind of related. If you > want to shut down the computer after a long runtime, the machine won't > power off. In the logs you can see the steps for shutting down the > OS, but sometimes the machine stays powered on. The power led is on, > screen is black, no response to keyboard or trackpad actions. System > has to be powered off by a long press on the power button. > > Ubuntu 6.2.0-27.28-generic 6.2.15 > > ProblemType: Bug > DistroRelease: Ubuntu 23.04 > Package: linux-image-6.2.0-27-generic 6.2.0-27.28 > ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 > Uname: Linux 6.2.0-27-generic x86_64 > ApportVersion: 2.26.1-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: tom2051 F wireplumber >/dev/snd/seq:tom2037 F pipewire > CasperMD5CheckResult: unknown > CurrentDesktop: ubuntu:GNOME > Date: Sat Aug 19 16:01:07 2023 > InstallationDate: Installed on 2018-07-01 (1875 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 > (20171018) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless > interface >Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide > Vision HD >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: HP HP ENVY Notebook > ProcEnviron: >LANG=de_DE.UTF-8 >PATH=(custom, no user) >SHELL=/bin/bash >TERM=xterm-256color >XDG_RUNTIME_DIR= > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic > root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: >linux-restricted-modules-6.2.0-27-generic N/A >linux-backports-modules-6.2.0-27-generic N/A >linux-firmware > 20230323.gitbcdcfbcf-0ubuntu1.5 > SourcePackage: linux > UpgradeStatus: Upgraded to lunar on 2023-05-01 (109 days ago) > dmi.bios.date: 11/10/2020 > dmi.bios.release: 15.62 > dmi.bios.vendor: Insyde > dmi.bios.version: F.62 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 81D2 > dmi.board.vendor: HP > dmi.board.version: KBC Version 87.21 > dmi.chassis.type: 10 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.ec.firmware.release: 87.21 > dmi.modalias: > dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD: > dmi.product.family: 103C_5335KV > dmi.product.name: HP ENVY Notebook > dmi.product.sku: Z6J78EA#ABD > dmi.product.version: Type1ProductConfigId > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031969/+subscriptions > > -- 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/2031969 Title: Ubuntu 23.04: Suspend & Power off Status in linux package in Ubuntu: Confirmed Bug description: Since update to version 23.04 I am facing several problems related to system suspend and shutdownon a HP Envy 15 notebook (2016). The system refuses to wake up from standby mode, especially if it has run for a longer time. Screen is black, no response to keyboard or trackpad actions, power button led is on. The only way out of here is a long press on the power button. Another problem with this and I think it's kind of related. If you want to shut down the computer after a long runtime, the machine won't power off. In the logs you can see the steps for shutting down the OS, but sometimes the machine stays powered on. The
[Kernel-packages] [Bug 2038852] 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 2038852
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/2038852
Title:
Isotp driver causes timeout because of race condition during
nonblocking writes
Status in linux package in Ubuntu:
Incomplete
Bug description:
This are my system details
Description:Ubuntu 20.04.6 LTS
Release:20.04
When using 5.15.133 kernel on Ubuntu 20.04. I am seeing that non blocking
writes cause race condition and locks the socket. This issue is resolved by a
patch from here
https://lore.kernel.org/linux-can/96d31e8c-fa26-4e32-4c36-768981f20...@hartkopp.net/T/#u.
This patch is supposed to make in the 6.7 kernel commit id 61caf48cf7 and I
would like it to be fixed for 5.15 stream as well. I have tested that this
patch when applied to 5.15.133 works. The patch cannot be directly applied but
a more comprehensive look at the current code at net/can/isotp.c. This is a
diff of my changes to isotp.c
119c119,120
< ISOTP_SENDING
---
> ISOTP_SENDING,
> ISOTP_SHUTDOWN,
873c874
< if (!so->bound)
---
> if (!so->bound|| so->tx.state == ISOTP_SHUTDOWN)
876,893c877,887
< /* we do not support multiple buffers - for now */
< if (cmpxchg(>tx.state, ISOTP_IDLE, ISOTP_SENDING) != ISOTP_IDLE ||
< wq_has_sleeper(>wait)) {
< if (msg->msg_flags & MSG_DONTWAIT) {
wait, so->tx.state ==
ISOTP_IDLE);
< if (err)
MAX_MSG_LENGTH) {
< err = -EINVAL;
< goto err_out_drop;
< }
---
> while (cmpxchg(>tx.state, ISOTP_IDLE, ISOTP_SENDING) !=
ISOTP_IDLE) {
> /* we do not support multiple buffers - for now */
> if (msg->msg_flags & MSG_DONTWAIT)
> return -EAGAIN;
> if (so->tx.state == ISOTP_SHUTDOWN)
> return -EADDRNOTAVAIL;
> /* wait for complete transmission of current pdu */
> err = wait_event_interruptible(so->wait, so->tx.state ==
ISOTP_IDLE);
> if (err)
>goto err_out;
> }
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038852/+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 2038852] Re: Isotp driver causes timeout because of race condition during nonblocking writes
** Package changed: ubuntu => linux (Ubuntu)
** Tags added: jammy
--
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/2038852
Title:
Isotp driver causes timeout because of race condition during
nonblocking writes
Status in linux package in Ubuntu:
New
Bug description:
This are my system details
Description:Ubuntu 20.04.6 LTS
Release:20.04
When using 5.15.133 kernel on Ubuntu 20.04. I am seeing that non blocking
writes cause race condition and locks the socket. This issue is resolved by a
patch from here
https://lore.kernel.org/linux-can/96d31e8c-fa26-4e32-4c36-768981f20...@hartkopp.net/T/#u.
This patch is supposed to make in the 6.7 kernel commit id 61caf48cf7 and I
would like it to be fixed for 5.15 stream as well. I have tested that this
patch when applied to 5.15.133 works. The patch cannot be directly applied but
a more comprehensive look at the current code at net/can/isotp.c. This is a
diff of my changes to isotp.c
119c119,120
< ISOTP_SENDING
---
> ISOTP_SENDING,
> ISOTP_SHUTDOWN,
873c874
< if (!so->bound)
---
> if (!so->bound|| so->tx.state == ISOTP_SHUTDOWN)
876,893c877,887
< /* we do not support multiple buffers - for now */
< if (cmpxchg(>tx.state, ISOTP_IDLE, ISOTP_SENDING) != ISOTP_IDLE ||
< wq_has_sleeper(>wait)) {
< if (msg->msg_flags & MSG_DONTWAIT) {
wait, so->tx.state ==
ISOTP_IDLE);
< if (err)
MAX_MSG_LENGTH) {
< err = -EINVAL;
< goto err_out_drop;
< }
---
> while (cmpxchg(>tx.state, ISOTP_IDLE, ISOTP_SENDING) !=
ISOTP_IDLE) {
> /* we do not support multiple buffers - for now */
> if (msg->msg_flags & MSG_DONTWAIT)
> return -EAGAIN;
> if (so->tx.state == ISOTP_SHUTDOWN)
> return -EADDRNOTAVAIL;
> /* wait for complete transmission of current pdu */
> err = wait_event_interruptible(so->wait, so->tx.state ==
ISOTP_IDLE);
> if (err)
>goto err_out;
> }
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038852/+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 2038852] [NEW] Isotp driver causes timeout because of race condition during nonblocking writes
You have been subscribed to a public bug:
This are my system details
Description:Ubuntu 20.04.6 LTS
Release:20.04
When using 5.15.133 kernel on Ubuntu 20.04. I am seeing that non blocking
writes cause race condition and locks the socket. This issue is resolved by a
patch from here
https://lore.kernel.org/linux-can/96d31e8c-fa26-4e32-4c36-768981f20...@hartkopp.net/T/#u.
This patch is supposed to make in the 6.7 kernel commit id 61caf48cf7 and I
would like it to be fixed for 5.15 stream as well. I have tested that this
patch when applied to 5.15.133 works. The patch cannot be directly applied but
a more comprehensive look at the current code at net/can/isotp.c. This is a
diff of my changes to isotp.c
119c119,120
< ISOTP_SENDING
---
> ISOTP_SENDING,
> ISOTP_SHUTDOWN,
873c874
< if (!so->bound)
---
> if (!so->bound|| so->tx.state == ISOTP_SHUTDOWN)
876,893c877,887
< /* we do not support multiple buffers - for now */
< if (cmpxchg(>tx.state, ISOTP_IDLE, ISOTP_SENDING) != ISOTP_IDLE ||
< wq_has_sleeper(>wait)) {
< if (msg->msg_flags & MSG_DONTWAIT) {
wait, so->tx.state ==
ISOTP_IDLE);
< if (err)
MAX_MSG_LENGTH) {
< err = -EINVAL;
< goto err_out_drop;
< }
---
> while (cmpxchg(>tx.state, ISOTP_IDLE, ISOTP_SENDING) != ISOTP_IDLE)
> {
> /* we do not support multiple buffers - for now */
> if (msg->msg_flags & MSG_DONTWAIT)
> return -EAGAIN;
> if (so->tx.state == ISOTP_SHUTDOWN)
> return -EADDRNOTAVAIL;
> /* wait for complete transmission of current pdu */
> err = wait_event_interruptible(so->wait, so->tx.state == ISOTP_IDLE);
> if (err)
>goto err_out;
> }
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
Isotp driver causes timeout because of race condition during nonblocking writes
https://bugs.launchpad.net/bugs/2038852
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038546] Re: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64
This bug was fixed in the package linux-firmware - 20230919.git3672ccab-0ubuntu2.1 --- linux-firmware (20230919.git3672ccab-0ubuntu2.1) mantic; urgency=medium * /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 (LP: #2038546) - [Packaging] config: Don't exclude cypress fw link targets -- Juerg Haefliger Mon, 09 Oct 2023 16:16:20 +0200 ** Changed in: linux-firmware (Ubuntu Mantic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2038546 Title: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Mantic: Fix Released Bug description: [Impact] /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the StarFive VisionFive board which uses the starfive kernel flavor. The file was available in Jammy and only recently removed from Mantic. File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding it cyfmac43430-sdio.clm_blob which file WHENCE links to brcmfmac43430-sdio.bin. So this file needs to change. [Fix] Include cypress/cyfmac firmware files in firmware packages. [Test Case] Check that wifi is functional. [Where Problems Could Occur] Potential wifi problems on platforms that are using the brcmfmac driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914881] Re: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,
I have this issue on an HP Spectre X360-Convertible 14 with Bang & Olufsen internal speakers, and Ubuntu 22.04.3 LTS. As others, I can use the audio jack or bluetooth the sound out. It worked well with Windows 11. -- 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/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Status in linux package in Ubuntu: Confirmed Bug description: There is no sound output from the laptop internal speakers when running Ubuntu 20.10. This is a dual-boot system; - Booting Windows first and then rebooting to Ubuntu -> sound works fine - Booting Ubuntu first and then rebooting to Windows -> Windows identifies sound as not enables and runs its troubleshooter to enable it The card seems to be recognised OK (system sound settings report output device as Speaker - Tiger Lake-LP Smart Sound technology Audio Controller. VU meters etc all appear as if sound is playing, but no sound. Headphone socket works perfectly. Similar bug reports for different laptops in the HP x360 series suggest this is a pinning problem and that the extract below from the boot logs may support this. lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 extract from journalctl -b kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:> kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 kernel: snd_hda_codec_realtek ehdaudio0D0:inputs: kernel: snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 20:48:52 2021 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1481 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=0a15de41-a7a7-4152-a5dc-e7e69f45fccb ro quiet splash vt.handoff=7
[Kernel-packages] [Bug 2038292] Re: nvidia-graphics-drivers-535{, -server} lower than in lunar & jammy
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2038292
Title:
nvidia-graphics-drivers-535{,-server} lower than in lunar & jammy
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
Invalid
Bug description:
nvidia-graphics-drivers-535 and nvidia-graphics-drivers-535-server are
lower than in lunar
meaning we need to sru 535.113 into mantic, before turning on
upgrades.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2038292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038546] Re: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64
** Changed in: linux-firmware (Ubuntu Mantic) Status: Confirmed => In Progress ** Changed in: linux-firmware (Ubuntu Mantic) Milestone: None => ubuntu-23.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2038546 Title: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Mantic: In Progress Bug description: [Impact] /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the StarFive VisionFive board which uses the starfive kernel flavor. The file was available in Jammy and only recently removed from Mantic. File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding it cyfmac43430-sdio.clm_blob which file WHENCE links to brcmfmac43430-sdio.bin. So this file needs to change. [Fix] Include cypress/cyfmac firmware files in firmware packages. [Test Case] Check that wifi is functional. [Where Problems Could Occur] Potential wifi problems on platforms that are using the brcmfmac driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038837] 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/2038837
Title:
kernel: evict_inodes inode 6048f67c, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Bug description:
This gets spammed after I shutdown, though the inode values are
different for each line. Had to phyically reboot to get it to reboot.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: yamiyuki 6735 F wireplumber
/dev/snd/controlC0: yamiyuki 6735 F wireplumber
/dev/snd/controlC1: yamiyuki 6735 F wireplumber
/dev/snd/seq:yamiyuki 6731 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Mon Oct 9 11:32:47 2023
InstallationDate: Installed on 2022-01-14 (634 days ago)
InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.5.0-9-generic
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.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-09-30 (9 days ago)
dmi.bios.date: 02/08/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F5a
dmi.board.asset.tag: Default string
dmi.board.name: X570S AORUS MASTER
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: X570 MB
dmi.product.name: X570S AORUS MASTER
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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-02-05T17:07:36.420620
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038837/+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
I've tested the kernel changes to enable Renesas RZ platform serial
installer.
The changes are working ok. I got the Ubuntu serial installer working
for Renesas RZ platform.
Please can you help to change the status to verification-done for
different releases.
Best Regards
John
** Changed in: linux (Ubuntu Focal)
Assignee: JOHN VINCENT (johnvincent) => (unassigned)
** Changed in: linux (Ubuntu Mantic)
Assignee: JOHN VINCENT (johnvincent) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2022361
Title:
Please enable Renesas RZ platform serial installer
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
The ubuntu installer does not work via serial ports for Renesas boards like
RZ/G2M-HiHope
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).
The installation can be done using HDMI ports, but it would be nice to
support installation via serial port as well.
[Test case]
Try to install Ubuntu on a Renesas board.
[Fix]
Statically build SuperH SCI(F) serial port support (with
earlyconsole).
[Regression potential]
Statically building an additional driver in the kernel can make the
kernel image bigger, potentially causing boot issues in small (arm64 /
armhf) platforms.
[Original bug report]
Package: linux
Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038837] [NEW] kernel: evict_inodes inode 000000006048f67c, i_count = 1, was skipped!
Public bug reported:
This gets spammed after I shutdown, though the inode values are
different for each line. Had to phyically reboot to get it to reboot.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: yamiyuki 6735 F wireplumber
/dev/snd/controlC0: yamiyuki 6735 F wireplumber
/dev/snd/controlC1: yamiyuki 6735 F wireplumber
/dev/snd/seq:yamiyuki 6731 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Mon Oct 9 11:32:47 2023
InstallationDate: Installed on 2022-01-14 (634 days ago)
InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.5.0-9-generic
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.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-09-30 (9 days ago)
dmi.bios.date: 02/08/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F5a
dmi.board.asset.tag: Default string
dmi.board.name: X570S AORUS MASTER
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: X570 MB
dmi.product.name: X570S AORUS MASTER
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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-02-05T17:07:36.420620
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug 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/2038837
Title:
kernel: evict_inodes inode 6048f67c, i_count = 1, was skipped!
Status in linux package in Ubuntu:
New
Bug description:
This gets spammed after I shutdown, though the inode values are
different for each line. Had to phyically reboot to get it to reboot.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: yamiyuki 6735 F wireplumber
/dev/snd/controlC0: yamiyuki 6735 F wireplumber
/dev/snd/controlC1: yamiyuki 6735 F wireplumber
/dev/snd/seq:yamiyuki 6731 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Mon Oct 9 11:32:47 2023
InstallationDate: Installed on 2022-01-14 (634 days ago)
InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.5.0-9-generic
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.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-09-30 (9 days ago)
dmi.bios.date: 02/08/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
[Kernel-packages] [Bug 2022361] Re: Please enable Renesas RZ platform serial installer
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => JOHN VINCENT (johnvincent)
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => JOHN VINCENT (johnvincent)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2022361
Title:
Please enable Renesas RZ platform serial installer
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
The ubuntu installer does not work via serial ports for Renesas boards like
RZ/G2M-HiHope
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).
The installation can be done using HDMI ports, but it would be nice to
support installation via serial port as well.
[Test case]
Try to install Ubuntu on a Renesas board.
[Fix]
Statically build SuperH SCI(F) serial port support (with
earlyconsole).
[Regression potential]
Statically building an additional driver in the kernel can make the
kernel image bigger, potentially causing boot issues in small (arm64 /
armhf) platforms.
[Original bug report]
Package: linux
Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019868] Re: ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips
This bug is awaiting verification that the linux- bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019868 Title: ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: These failures happen on all supported architectures, when fips=1. When fips=0, all test cases pass. The results are shown below: make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/src/linux' TAP version 13 1..1 # selftests: net: tls # TAP version 13 # 1..179 # # Starting 179 tests from 6 test cases. # # RUN global.non_established ... # #OK global.non_established # ok 1 global.non_established # # RUN global.keysizes ... # #OK global.keysizes # ok 2 global.keysizes # # RUN tls_basic.base_base ... # #OK tls_basic.base_base # ok 3 tls_basic.base_base # # RUN tls.12_gcm.sendfile ... # #OK tls.12_gcm.sendfile # ok 4 tls.12_gcm.sendfile # # RUN tls.12_gcm.send_then_sendfile ... # #OK tls.12_gcm.send_then_sendfile # ok 5 tls.12_gcm.send_then_sendfile # # RUN tls.12_gcm.recv_max ... # #OK tls.12_gcm.recv_max # ok 6 tls.12_gcm.recv_max # # RUN tls.12_gcm.recv_small ... # #OK tls.12_gcm.recv_small # ok 7 tls.12_gcm.recv_small # # RUN tls.12_gcm.msg_more ... # #OK tls.12_gcm.msg_more # ok 8 tls.12_gcm.msg_more # # RUN tls.12_gcm.msg_more_unsent ... # #OK tls.12_gcm.msg_more_unsent # ok 9 tls.12_gcm.msg_more_unsent # # RUN tls.12_gcm.sendmsg_single ... # #OK tls.12_gcm.sendmsg_single # ok 10 tls.12_gcm.sendmsg_single # # RUN tls.12_gcm.sendmsg_fragmented ... # #OK tls.12_gcm.sendmsg_fragmented # ok 11 tls.12_gcm.sendmsg_fragmented # # RUN tls.12_gcm.sendmsg_large ... # #OK tls.12_gcm.sendmsg_large # ok 12 tls.12_gcm.sendmsg_large # # RUN tls.12_gcm.sendmsg_multiple ... # #OK tls.12_gcm.sendmsg_multiple # ok 13 tls.12_gcm.sendmsg_multiple # # RUN tls.12_gcm.sendmsg_multiple_stress ... # #OK tls.12_gcm.sendmsg_multiple_stress # ok 14 tls.12_gcm.sendmsg_multiple_stress # # RUN tls.12_gcm.splice_from_pipe ... # #OK tls.12_gcm.splice_from_pipe # ok 15 tls.12_gcm.splice_from_pipe # # RUN tls.12_gcm.splice_from_pipe2 ... # #OK tls.12_gcm.splice_from_pipe2 # ok 16 tls.12_gcm.splice_from_pipe2 # # RUN tls.12_gcm.send_and_splice ... # #OK tls.12_gcm.send_and_splice # ok 17 tls.12_gcm.send_and_splice # # RUN tls.12_gcm.splice_to_pipe ... # #OK tls.12_gcm.splice_to_pipe # ok 18 tls.12_gcm.splice_to_pipe # # RUN tls.12_gcm.recvmsg_single ... # #OK tls.12_gcm.recvmsg_single # ok 19 tls.12_gcm.recvmsg_single # # RUN tls.12_gcm.recvmsg_single_max ... # #OK tls.12_gcm.recvmsg_single_max # ok 20 tls.12_gcm.recvmsg_single_max # # RUN tls.12_gcm.recvmsg_multiple ... # #OK tls.12_gcm.recvmsg_multiple # ok 21 tls.12_gcm.recvmsg_multiple # # RUN tls.12_gcm.single_send_multiple_recv ... # #OK tls.12_gcm.single_send_multiple_recv # ok 22 tls.12_gcm.single_send_multiple_recv # # RUN tls.12_gcm.multiple_send_single_recv ... # #OK tls.12_gcm.multiple_send_single_recv # ok 23 tls.12_gcm.multiple_send_single_recv # # RUN tls.12_gcm.single_send_multiple_recv_non_align ... # #OK tls.12_gcm.single_send_multiple_recv_non_align # ok 24
[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- bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2030924 Title: [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in cpuinfo_min_freq and cpuino_max_freq sysfs files. Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] On DELL EMC PowerEdge system when Ubuntu 22.04.1 OS is Installed, Unable to Interpret the values in cpuinfo_max_freq and cpuinfo_min_freq sysfs files as per the Intel specs document. Steps to Reproduce: 1. Install one CPU that supports DBS "Demand-Based Power Management". 2. Install Ubuntu 22.04.1 OS. 2. Enable "Logical Processor" under CPU Information menu from F2 setup. 3. Save changes and reboot to Ubuntu 22.04.1 OS. 4. Right click on "Computer" and select "File system" and check for the following CPU directories. /sys/devices/system/cpu/cpu0/cpufreq/cpu0 /sys/devices/system/cpu/cpu0/cpufreq/cpu1 5. View the Max Frequency and Min Frequency under CPU0 and CPU1 directory. 6. The Max and Min Frequency did not match as per the Intel specs datasheet. Actual results: /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 680 /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 80 /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 390 Expected results: As per Intel datasheet specification. /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 5300 MHz /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 800 MHz /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 3000 MHz [Fix] cpufreq: intel_pstate: Fix scaling for hybrid-capable systems with disabled E-cores https://github.com/torvalds/linux/commit/0fcfc9e51990246a9813475716746ff5eb98c6aa [github.com] [Test Plan] Same as steps to reproduce [ Where problems could occur ] This issue is seen on Intel based system under development which supports DBS "Demand-Based Power Management", then install Ubuntu-22.04 and boot into OS then check for the frequency values under /sys/devices/system/cpu/cpu0/cpufreq/cpu0 Regression risk = Low to medium [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/cpuinfo_freq lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/cpuinfo_freq_lunar_2 Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/cpuinfo_freq_mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031333] Re: Need to get fine-grained control for FAN(TFN) Participant.
This bug is awaiting verification that the linux- bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2031333 Title: Need to get fine-grained control for FAN(TFN) Participant. Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: This is a public version of the following bugs: https://bugs.launchpad.net/bugs/1987597 https://bugs.launchpad.net/bugs/2027754 [Feature Description] We need Fine-grained Control of TFN participant for enabling active 2 policy in Linux/chrome. Currently, The kernel has provided __FPS table and cur__state to adjust the fan level as per _FPS table . But there is no option to read *_FIF (Fan Information) and _FST (Fan Status).* Once the fine-grained control is enabled, we should be able to the set the control value from 0-100 through Arg0 of _FSL (Fan Set Level). *_FST (Fan Status)* should report current running RPM and control value of the FAN(TFN). please refer ACPI spec for more detail. [https://uefi.org/specs/ACPI/6.4/11_Thermal_Management/fan- device.html] [HW/SW Information] Hardware: Alder Lake Target Release: 22.04 Target Kernel: 5.15 Merged for 5.18-rc1 f1197343f077 ACPI: fan: Add additional attributes for fine grain control bea2d9868ef5 ACPI: fan: Properly handle fine grain control d445571fa369 ACPI: fan: Optimize struct acpi_fan_fif 00ae053a0533 ACPI: fan: Separate file for attributes creation Platform-independent [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031333/+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 2032176] Re: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1
This bug is awaiting verification that the linux- bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032176 Title: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Impact: We had reports of VM setups which would show intermediate crashes and after that locking up completely. This could be reproduced with large memory setups. The problem seems to be that fixes to performance regressions caused more problems in 5.15 kernels and the full fixes are too intrusive to be backported. Fix: The following patch was recently sent to the upstream stable mailing list and looks to be making its way into linux-5.15.y. This changes the default value of kvm.tdp_mmu to off (if anyone is willing to take the risks, this can be changed back in config). Regression potential: VM hosts with many large memory tennants might see a performance impact which the TDP MMU approach tried to solve. If those did not see other problems they might turn this on again. Testcase: Large openstack instance (64GB memory, AMD CPU (using SVM)) with a large second level guest (32GB memory). Repeatedly starting and stopping the 2nd level guest. --- original description --- The crash occurred on a juju machine, and the juju agent was lost. The juju machine is on an openstack instance provision by juju. The openstack console log indicts the it is related to spin_lock and KVM MMU: [418200.348830] ? _raw_spin_lock+0x22/0x30 [418200.349588] _raw_write_lock+0x20/0x30 [418200.350196] kvm_tdp_mmu_map+0x2b1/0x490 [kvm] [418200.351014] kvm_mmu_notifier_invalidate_range_start+0x1ad/0x300 [kvm] [418200.351796] direct_page_fault+0x206/0x310 [kvm] [418200.352667] __mmu_notifier_invalidate_range_start+0x91/0x1b0 [418200.353624] kvm_tdp_page_fault+0x72/0x90 [kvm] [418200.354496] try_to_migrate_one+0x691/0x730 [418200.355436] kvm_mmu_page_fault+0x73/0x1c0 [kvm] openstack console log: https://pastebin.canonical.com/p/spmH8r3crQ/ syslog: https://pastebin.canonical.com/p/wFPsFD8G9n/ The syslog was rotated after the crash occurred, so the syslog at the time of the initial crash was lost. Other juju machine with 5.15.0.79.76 kernel seems to have the same issues. We previously have a similar issue with 5.15.0-73. The juju machine crashed with raw_spin_lock and kvm mmu in the logs as well: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Aug 21 08:59:46 2023 Ec2AMI: ami-0c61 Ec2AMIManifest: FIXME Ec2AvailabilityZone: availability-zone-1 Ec2InstanceType: builder-cpu4-ram72-disk20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 23 03:23 seq crw-rw 1 root audio 116, 33 Aug 23 03:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack
[Kernel-packages] [Bug 2019880] Re: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips
This bug is awaiting verification that the linux- bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019880 Title: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: These failures happen on all supported architectures, when fips=1. When fips=0, all test cases pass. Results are shown below: make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/src/linux' TAP version 13 1..1 # selftests: net: vrf-xfrm-tests.sh # # No qdisc on VRF device # TEST: IPv4 no xfrm policy [ OK ] # TEST: IPv6 no xfrm policy [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy with VRF in selector [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy with xfrm device [FAIL] # TEST: IPv6 xfrm policy with xfrm device [FAIL] # # netem qdisc on VRF device # TEST: IPv4 no xfrm policy [ OK ] # TEST: IPv6 no xfrm policy [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy with VRF in selector [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy with xfrm device [FAIL] # TEST: IPv6 xfrm policy with xfrm device [FAIL] # # Tests passed: 6 # Tests failed: 8 not ok 1 selftests: net: vrf-xfrm-tests.sh # exit=1 make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2019880/+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-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-bluefield-v2
verification-needed-jammy-linux-bluefield
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2022361
Title:
Please enable Renesas RZ platform serial installer
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
The ubuntu installer does not work via serial ports for Renesas boards like
RZ/G2M-HiHope
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).
The installation can be done using HDMI ports, but it would be nice to
support installation via serial port as well.
[Test case]
Try to install Ubuntu on a Renesas board.
[Fix]
Statically build SuperH SCI(F) serial port support (with
earlyconsole).
[Regression potential]
Statically building an additional driver in the kernel can make the
kernel image bigger, potentially causing boot issues in small (arm64 /
armhf) platforms.
[Original bug report]
Package: linux
Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028122] Re: Fix unreliable ethernet cable detection on I219 NIC
This bug is awaiting verification that the linux- bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2028122 Title: Fix unreliable ethernet cable detection on I219 NIC Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Hotplugging RJ45 ethernet cable only works for one time because ACPI GPE wake doesn't working properly anymore. [Fix] Always use PME poll to read PCI PME to know if there's wake event. [Test] With the patch applied, ethernet cable can always be detected. [Where problems could occur] PME poll mechanism periodically reads the PMCTRL register, so the power consumption can be slightly higher. The increase will be very low, probably won't be noticeable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux- bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 2033122] Re: Request backport of xen timekeeping performance improvements
This bug is awaiting verification that the linux- bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033122 Title: Request backport of xen timekeeping performance improvements Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Users, especially those on EC2, are encouraged to select tsc as their default clocksource. However, this requires manual tuning of the operating system. Kvm can determine if it safe to use the tsc, and will default to that instead of its pvclock when appropriate. This requests a backport of patch does the same for Xen instances. If appropriate, it's fine if this is applied to only the linux-aws branches. Not all Xen EC2 instances advertise explicit nomigrate support, however, on those that do we'll select tsc by default. On the subset of hosts where this is advertised, users will safely default to the more performant clocksource. [Impact] Xen instances default to the xen clocksource which has been documented to be slower. This is required for instances where the tsc is not safe to use, or the guest is subject to migration. On some platforms the performance impact can be high, and users are encouraged to select the tsc when appropriate. Instead of leaving up to users to figure this out by reading a variety of different documents, pick the fast clocksource when it can be determined to be safe to do so. [Backport] Clean cherry pick. No conflicts applying to 5.15 or 6.2. [Test] Booted EC2 xen instances with and without this patch and validated that on those that properly advertised the required criteria via cpuid, that the clocksource defaulted to tsc instead of xen. [Potential Regression] Potential is low, since only absurd configurations could lead to a problem. If this is considered risky, it can be applied to only linux-aws where the documented guidance is for users to enable tsc as the clocksource on Xen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034447] Re: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic
This bug is awaiting verification that the linux- bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux 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: Fix Released Status in linux source package in Jammy: Fix Released 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 [
[Kernel-packages] [Bug 2035181] Re: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-bluefield-v2
verification-needed-jammy-linux-bluefield
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035181
Title:
Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Confirmed
Bug description:
[Impact]
Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work
with CO-RE") from stable update breaks the ubuntu_bpf test build and
cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in
ubuntu_kernel_selftests stopped working, as they require bpf selftest
to be built first.
The following is extracted from the commit message:
The problem is the new offsetof() does not play nice with static asserts.
Given that the context is a static assert (and CO-RE relocation is not
needed at compile time), offsetof() usage can be replaced by restoring
the original offsetof() definition as __builtin_offsetof().
[Test Plan]
Build bpf selftest in tools/testing/selftests with the following command:
make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \
clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/
The build can finish successfully with patched kernel source code.
[Where problems could occur]
Fix limited to testing tool, if this fix is incorrect the bpf selftest
build will remain broken.
== Original bug report ==
Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04
This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
is a security cycle, in which the ubuntu_bpf test was not triggered
there)
Test build failed with:
CLNG-BPF [test_maps] test_btf_map_in_map.o
CLNG-BPF [test_maps] test_btf_newkv.o
CLNG-BPF [test_maps] test_btf_nokv.o
CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
CLNG-BPF [test_maps] test_cgroup_link.o
CLNG-BPF [test_maps] test_check_mtu.o
CLNG-BPF [test_maps] test_cls_redirect.o
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from
latest version at 'include/uapi/linux/bpf.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs
from latest version at 'include/uapi/linux/netlink.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at 'include/uapi/linux/if_link.h'
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
[Kernel-packages] [Bug 2038546] Re: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64
In Mantic, we try to exclude firmware files that the kernel doesn't reference. Some bcm/brcmfmac files are symlinks to cypress/cyfmac files so we need to keep the cypress files on all relevant architectures. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2038546 Title: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Mantic: Confirmed Bug description: [Impact] /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the StarFive VisionFive board which uses the starfive kernel flavor. The file was available in Jammy and only recently removed from Mantic. File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding it cyfmac43430-sdio.clm_blob which file WHENCE links to brcmfmac43430-sdio.bin. So this file needs to change. [Fix] Include cypress/cyfmac firmware files in firmware packages. [Test Case] Check that wifi is functional. [Where Problems Could Occur] Potential wifi problems on platforms that are using the brcmfmac driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036675] Re: 5.15.0-85 live migration regression
This bug is awaiting verification that the linux- bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036675 Title: 5.15.0-85 live migration regression Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Released Bug description: Fixes added for LP 2032164 [0] to resolve an issue in live migration have unfortunately introduced a regression, causing a previously working live migration pattern to fail when tested with the 5.15.0-85 kernel from -proposed. Specifically, live migration from a PKRU-enabled host running a kernel older than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail. The destination can be either with or without PKRU; both cases fail, although in different ways (one hangs, the other fails due to a PCID flag issue). The commits in question are commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0 Author: Dr. David Alan Gilbert Date: Mon Aug 21 14:47:28 2023 +0800 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES commit 27a189b881278c8ad9c16b0ee05668d724352733 Author: Leonardo Bras Date: Mon Aug 21 14:47:27 2023 +0800 x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 [0] https://bugs.launchpad.net/bugs/2032164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675/+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 2019868] Re: ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2019868 Title: ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: These failures happen on all supported architectures, when fips=1. When fips=0, all test cases pass. The results are shown below: make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/src/linux' TAP version 13 1..1 # selftests: net: tls # TAP version 13 # 1..179 # # Starting 179 tests from 6 test cases. # # RUN global.non_established ... # #OK global.non_established # ok 1 global.non_established # # RUN global.keysizes ... # #OK global.keysizes # ok 2 global.keysizes # # RUN tls_basic.base_base ... # #OK tls_basic.base_base # ok 3 tls_basic.base_base # # RUN tls.12_gcm.sendfile ... # #OK tls.12_gcm.sendfile # ok 4 tls.12_gcm.sendfile # # RUN tls.12_gcm.send_then_sendfile ... # #OK tls.12_gcm.send_then_sendfile # ok 5 tls.12_gcm.send_then_sendfile # # RUN tls.12_gcm.recv_max ... # #OK tls.12_gcm.recv_max # ok 6 tls.12_gcm.recv_max # # RUN tls.12_gcm.recv_small ... # #OK tls.12_gcm.recv_small # ok 7 tls.12_gcm.recv_small # # RUN tls.12_gcm.msg_more ... # #OK tls.12_gcm.msg_more # ok 8 tls.12_gcm.msg_more # # RUN tls.12_gcm.msg_more_unsent ... # #OK tls.12_gcm.msg_more_unsent # ok 9 tls.12_gcm.msg_more_unsent # # RUN tls.12_gcm.sendmsg_single ... # #OK tls.12_gcm.sendmsg_single # ok 10 tls.12_gcm.sendmsg_single # # RUN tls.12_gcm.sendmsg_fragmented ... # #OK tls.12_gcm.sendmsg_fragmented # ok 11 tls.12_gcm.sendmsg_fragmented # # RUN tls.12_gcm.sendmsg_large ... # #OK tls.12_gcm.sendmsg_large # ok 12 tls.12_gcm.sendmsg_large # # RUN tls.12_gcm.sendmsg_multiple ... # #OK tls.12_gcm.sendmsg_multiple # ok 13 tls.12_gcm.sendmsg_multiple # # RUN tls.12_gcm.sendmsg_multiple_stress ... # #OK tls.12_gcm.sendmsg_multiple_stress # ok 14 tls.12_gcm.sendmsg_multiple_stress # # RUN tls.12_gcm.splice_from_pipe ... # #OK tls.12_gcm.splice_from_pipe # ok 15 tls.12_gcm.splice_from_pipe # # RUN tls.12_gcm.splice_from_pipe2 ... # #OK tls.12_gcm.splice_from_pipe2 # ok 16 tls.12_gcm.splice_from_pipe2 # # RUN tls.12_gcm.send_and_splice ... # #OK tls.12_gcm.send_and_splice # ok 17 tls.12_gcm.send_and_splice # # RUN tls.12_gcm.splice_to_pipe ... # #OK tls.12_gcm.splice_to_pipe # ok 18 tls.12_gcm.splice_to_pipe # # RUN tls.12_gcm.recvmsg_single ... # #OK tls.12_gcm.recvmsg_single # ok 19 tls.12_gcm.recvmsg_single # # RUN tls.12_gcm.recvmsg_single_max ... # #OK tls.12_gcm.recvmsg_single_max # ok 20 tls.12_gcm.recvmsg_single_max # # RUN tls.12_gcm.recvmsg_multiple ... # #OK tls.12_gcm.recvmsg_multiple # ok 21 tls.12_gcm.recvmsg_multiple # # RUN tls.12_gcm.single_send_multiple_recv ... # #OK tls.12_gcm.single_send_multiple_recv # ok 22 tls.12_gcm.single_send_multiple_recv # # RUN tls.12_gcm.multiple_send_single_recv ... # #OK tls.12_gcm.multiple_send_single_recv # ok 23 tls.12_gcm.multiple_send_single_recv # # RUN tls.12_gcm.single_send_multiple_recv_non_align ... # #OK tls.12_gcm.single_send_multiple_recv_non_align # ok 24
[Kernel-packages] [Bug 2019880] Re: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2019880 Title: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: These failures happen on all supported architectures, when fips=1. When fips=0, all test cases pass. Results are shown below: make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/src/linux' TAP version 13 1..1 # selftests: net: vrf-xfrm-tests.sh # # No qdisc on VRF device # TEST: IPv4 no xfrm policy [ OK ] # TEST: IPv6 no xfrm policy [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy with VRF in selector [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy with xfrm device [FAIL] # TEST: IPv6 xfrm policy with xfrm device [FAIL] # # netem qdisc on VRF device # TEST: IPv4 no xfrm policy [ OK ] # TEST: IPv6 no xfrm policy [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy with VRF in selector [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy with xfrm device [FAIL] # TEST: IPv6 xfrm policy with xfrm device [FAIL] # # Tests passed: 6 # Tests failed: 8 not ok 1 selftests: net: vrf-xfrm-tests.sh # exit=1 make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2019880/+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-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-raspi-v2
verification-needed-jammy-linux-raspi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2022361
Title:
Please enable Renesas RZ platform serial installer
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
The ubuntu installer does not work via serial ports for Renesas boards like
RZ/G2M-HiHope
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).
The installation can be done using HDMI ports, but it would be nice to
support installation via serial port as well.
[Test case]
Try to install Ubuntu on a Renesas board.
[Fix]
Statically build SuperH SCI(F) serial port support (with
earlyconsole).
[Regression potential]
Statically building an additional driver in the kernel can make the
kernel image bigger, potentially causing boot issues in small (arm64 /
armhf) platforms.
[Original bug report]
Package: linux
Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032176] Re: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2032176 Title: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Impact: We had reports of VM setups which would show intermediate crashes and after that locking up completely. This could be reproduced with large memory setups. The problem seems to be that fixes to performance regressions caused more problems in 5.15 kernels and the full fixes are too intrusive to be backported. Fix: The following patch was recently sent to the upstream stable mailing list and looks to be making its way into linux-5.15.y. This changes the default value of kvm.tdp_mmu to off (if anyone is willing to take the risks, this can be changed back in config). Regression potential: VM hosts with many large memory tennants might see a performance impact which the TDP MMU approach tried to solve. If those did not see other problems they might turn this on again. Testcase: Large openstack instance (64GB memory, AMD CPU (using SVM)) with a large second level guest (32GB memory). Repeatedly starting and stopping the 2nd level guest. --- original description --- The crash occurred on a juju machine, and the juju agent was lost. The juju machine is on an openstack instance provision by juju. The openstack console log indicts the it is related to spin_lock and KVM MMU: [418200.348830] ? _raw_spin_lock+0x22/0x30 [418200.349588] _raw_write_lock+0x20/0x30 [418200.350196] kvm_tdp_mmu_map+0x2b1/0x490 [kvm] [418200.351014] kvm_mmu_notifier_invalidate_range_start+0x1ad/0x300 [kvm] [418200.351796] direct_page_fault+0x206/0x310 [kvm] [418200.352667] __mmu_notifier_invalidate_range_start+0x91/0x1b0 [418200.353624] kvm_tdp_page_fault+0x72/0x90 [kvm] [418200.354496] try_to_migrate_one+0x691/0x730 [418200.355436] kvm_mmu_page_fault+0x73/0x1c0 [kvm] openstack console log: https://pastebin.canonical.com/p/spmH8r3crQ/ syslog: https://pastebin.canonical.com/p/wFPsFD8G9n/ The syslog was rotated after the crash occurred, so the syslog at the time of the initial crash was lost. Other juju machine with 5.15.0.79.76 kernel seems to have the same issues. We previously have a similar issue with 5.15.0-73. The juju machine crashed with raw_spin_lock and kvm mmu in the logs as well: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Aug 21 08:59:46 2023 Ec2AMI: ami-0c61 Ec2AMIManifest: FIXME Ec2AvailabilityZone: availability-zone-1 Ec2InstanceType: builder-cpu4-ram72-disk20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 23 03:23 seq crw-rw 1 root audio 116, 33 Aug 23 03:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata
[Kernel-packages] [Bug 2028122] Re: Fix unreliable ethernet cable detection on I219 NIC
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2028122 Title: Fix unreliable ethernet cable detection on I219 NIC Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Hotplugging RJ45 ethernet cable only works for one time because ACPI GPE wake doesn't working properly anymore. [Fix] Always use PME poll to read PCI PME to know if there's wake event. [Test] With the patch applied, ethernet cable can always be detected. [Where problems could occur] PME poll mechanism periodically reads the PMCTRL register, so the power consumption can be slightly higher. The increase will be very low, probably won't be noticeable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034447] Re: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- 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: Fix Released Status in linux source package in Jammy: Fix Released 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] ?
[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-raspi/5.15.0-1040.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2030924 Title: [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in cpuinfo_min_freq and cpuino_max_freq sysfs files. Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] On DELL EMC PowerEdge system when Ubuntu 22.04.1 OS is Installed, Unable to Interpret the values in cpuinfo_max_freq and cpuinfo_min_freq sysfs files as per the Intel specs document. Steps to Reproduce: 1. Install one CPU that supports DBS "Demand-Based Power Management". 2. Install Ubuntu 22.04.1 OS. 2. Enable "Logical Processor" under CPU Information menu from F2 setup. 3. Save changes and reboot to Ubuntu 22.04.1 OS. 4. Right click on "Computer" and select "File system" and check for the following CPU directories. /sys/devices/system/cpu/cpu0/cpufreq/cpu0 /sys/devices/system/cpu/cpu0/cpufreq/cpu1 5. View the Max Frequency and Min Frequency under CPU0 and CPU1 directory. 6. The Max and Min Frequency did not match as per the Intel specs datasheet. Actual results: /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 680 /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 80 /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 390 Expected results: As per Intel datasheet specification. /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 5300 MHz /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 800 MHz /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 3000 MHz [Fix] cpufreq: intel_pstate: Fix scaling for hybrid-capable systems with disabled E-cores https://github.com/torvalds/linux/commit/0fcfc9e51990246a9813475716746ff5eb98c6aa [github.com] [Test Plan] Same as steps to reproduce [ Where problems could occur ] This issue is seen on Intel based system under development which supports DBS "Demand-Based Power Management", then install Ubuntu-22.04 and boot into OS then check for the frequency values under /sys/devices/system/cpu/cpu0/cpufreq/cpu0 Regression risk = Low to medium [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/cpuinfo_freq lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/cpuinfo_freq_lunar_2 Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/cpuinfo_freq_mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031333] Re: Need to get fine-grained control for FAN(TFN) Participant.
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2031333 Title: Need to get fine-grained control for FAN(TFN) Participant. Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: This is a public version of the following bugs: https://bugs.launchpad.net/bugs/1987597 https://bugs.launchpad.net/bugs/2027754 [Feature Description] We need Fine-grained Control of TFN participant for enabling active 2 policy in Linux/chrome. Currently, The kernel has provided __FPS table and cur__state to adjust the fan level as per _FPS table . But there is no option to read *_FIF (Fan Information) and _FST (Fan Status).* Once the fine-grained control is enabled, we should be able to the set the control value from 0-100 through Arg0 of _FSL (Fan Set Level). *_FST (Fan Status)* should report current running RPM and control value of the FAN(TFN). please refer ACPI spec for more detail. [https://uefi.org/specs/ACPI/6.4/11_Thermal_Management/fan- device.html] [HW/SW Information] Hardware: Alder Lake Target Release: 22.04 Target Kernel: 5.15 Merged for 5.18-rc1 f1197343f077 ACPI: fan: Add additional attributes for fine grain control bea2d9868ef5 ACPI: fan: Properly handle fine grain control d445571fa369 ACPI: fan: Optimize struct acpi_fan_fif 00ae053a0533 ACPI: fan: Separate file for attributes creation Platform-independent [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033122] Re: Request backport of xen timekeeping performance improvements
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033122 Title: Request backport of xen timekeeping performance improvements Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Users, especially those on EC2, are encouraged to select tsc as their default clocksource. However, this requires manual tuning of the operating system. Kvm can determine if it safe to use the tsc, and will default to that instead of its pvclock when appropriate. This requests a backport of patch does the same for Xen instances. If appropriate, it's fine if this is applied to only the linux-aws branches. Not all Xen EC2 instances advertise explicit nomigrate support, however, on those that do we'll select tsc by default. On the subset of hosts where this is advertised, users will safely default to the more performant clocksource. [Impact] Xen instances default to the xen clocksource which has been documented to be slower. This is required for instances where the tsc is not safe to use, or the guest is subject to migration. On some platforms the performance impact can be high, and users are encouraged to select the tsc when appropriate. Instead of leaving up to users to figure this out by reading a variety of different documents, pick the fast clocksource when it can be determined to be safe to do so. [Backport] Clean cherry pick. No conflicts applying to 5.15 or 6.2. [Test] Booted EC2 xen instances with and without this patch and validated that on those that properly advertised the required criteria via cpuid, that the clocksource defaulted to tsc instead of xen. [Potential Regression] Potential is low, since only absurd configurations could lead to a problem. If this is considered risky, it can be applied to only linux-aws where the documented guidance is for users to enable tsc as the clocksource on Xen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 2035181] Re: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-raspi-v2
verification-needed-jammy-linux-raspi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035181
Title:
Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Confirmed
Bug description:
[Impact]
Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work
with CO-RE") from stable update breaks the ubuntu_bpf test build and
cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in
ubuntu_kernel_selftests stopped working, as they require bpf selftest
to be built first.
The following is extracted from the commit message:
The problem is the new offsetof() does not play nice with static asserts.
Given that the context is a static assert (and CO-RE relocation is not
needed at compile time), offsetof() usage can be replaced by restoring
the original offsetof() definition as __builtin_offsetof().
[Test Plan]
Build bpf selftest in tools/testing/selftests with the following command:
make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \
clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/
The build can finish successfully with patched kernel source code.
[Where problems could occur]
Fix limited to testing tool, if this fix is incorrect the bpf selftest
build will remain broken.
== Original bug report ==
Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04
This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
is a security cycle, in which the ubuntu_bpf test was not triggered
there)
Test build failed with:
CLNG-BPF [test_maps] test_btf_map_in_map.o
CLNG-BPF [test_maps] test_btf_newkv.o
CLNG-BPF [test_maps] test_btf_nokv.o
CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
CLNG-BPF [test_maps] test_cgroup_link.o
CLNG-BPF [test_maps] test_check_mtu.o
CLNG-BPF [test_maps] test_cls_redirect.o
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from
latest version at 'include/uapi/linux/bpf.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs
from latest version at 'include/uapi/linux/netlink.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at 'include/uapi/linux/if_link.h'
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
[Kernel-packages] [Bug 2036675] Re: 5.15.0-85 live migration regression
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2036675 Title: 5.15.0-85 live migration regression Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Released Bug description: Fixes added for LP 2032164 [0] to resolve an issue in live migration have unfortunately introduced a regression, causing a previously working live migration pattern to fail when tested with the 5.15.0-85 kernel from -proposed. Specifically, live migration from a PKRU-enabled host running a kernel older than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail. The destination can be either with or without PKRU; both cases fail, although in different ways (one hangs, the other fails due to a PCID flag issue). The commits in question are commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0 Author: Dr. David Alan Gilbert Date: Mon Aug 21 14:47:28 2023 +0800 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES commit 27a189b881278c8ad9c16b0ee05668d724352733 Author: Leonardo Bras Date: Mon Aug 21 14:47:27 2023 +0800 x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 [0] https://bugs.launchpad.net/bugs/2032164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
** Changed in: ubuntu-release-notes Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in cloud-images: New Status in maas-images: Confirmed Status in The Ubuntu-power-systems project: Invalid Status in Release Notes for Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Fix Released Status in linux source package in Mantic: Invalid Status in systemd source package in Mantic: Invalid Status in util-linux source package in Mantic: Fix Released Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038831] [NEW] Jammy update: v6.1.55 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: v6.1.55 upstream stable release from git://git.kernel.org/ Linux 6.1.55 interconnect: Teach lockdep about icc_bw_lock order net/sched: Retire rsvp classifier drm/amdgpu: fix amdgpu_cs_p1_user_fence Revert "memcg: drop kmem.limit_in_bytes" drm/amd/display: fix the white screen issue when >= 64GB DRAM ext4: fix rec_len verify error scsi: pm8001: Setup IRQs on resume scsi: megaraid_sas: Fix deadlock on firmware crashdump ata: libahci: clear pending interrupt status ata: libata: disallow dev-initiated LPM transitions to unsupported states i2c: aspeed: Reset the i2c controller when timeout occurs tracefs: Add missing lockdown check to tracefs_create_dir() nfsd: fix change_info in NFSv4 RENAME replies selinux: fix handling of empty opts in selinux_fs_context_submount() tracing: Have option files inc the trace array ref count tracing: Have current_trace inc the trace array ref count tracing: Increase trace array ref count on enable and filter files tracing: Have event inject files inc the trace array ref count tracing: Have tracing_max_latency inc the trace array ref count btrfs: check for BTRFS_FS_ERROR in pending ordered assert btrfs: release path before inode lookup during the ino lookup ioctl btrfs: fix a compilation error if DEBUG is defined in btree_dirty_folio btrfs: fix lockdep splat and potential deadlock after failure running delayed items dm: don't attempt to queue IO under RCU protection Revert "drm/amd: Disable S/G for APUs when 64GB or more host memory" md: Put the right device in md_seq_next nvme: avoid bogus CRTO values io_uring/net: fix iter retargeting for selected buf ovl: fix incorrect fdput() on aio completion ovl: fix failed copyup of fileattr on a symlink attr: block mode changes of symlinks Revert "SUNRPC: Fail faster on bad verifier" md/raid1: fix error: ISO C90 forbids mixed declarations samples/hw_breakpoint: fix building without module unloading x86/purgatory: Remove LTO flags x86/boot/compressed: Reserve more memory for page tables panic: Reenable preemption in WARN slowpath scsi: lpfc: Fix the NULL vs IS_ERR() bug for debugfs_create_file() scsi: target: core: Fix target_cmd_counter leak riscv: kexec: Align the kexeced kernel entry x86/ibt: Suppress spurious ENDBR selftests: tracing: Fix to unmount tracefs for recovering environment scsi: qla2xxx: Fix NULL vs IS_ERR() bug for debugfs_create_dir() drm: gm12u320: Fix the timeout usage for usb_bulk_msg() nvmet-tcp: pass iov_len instead of sg->length to bvec_set_page() nvmet: use bvec_set_page to initialize bvecs block: factor out a bvec_set_page helper btrfs: compare the correct fsid/metadata_uuid in btrfs_validate_super btrfs: add a helper to read the superblock metadata_uuid MIPS: Use "grep -E" instead of "egrep" misc: fastrpc: Fix incorrect DMA mapping unmap request misc: fastrpc: Prepare to dynamic dma-buf locking specification dma-buf: Add unlocked variant of attachment-mapping functions printk: Consolidate console deferred printing printk: Keep non-panic-CPUs out of console lock interconnect: Fix locking for runpm vs reclaim kobject: Add sanity check for kset->kobj.ktype in kset_register() media: pci: ipu3-cio2: Initialise timing struct to avoid a compiler warning usb: chipidea: add workaround for chipidea PEC bug usb: ehci: add workaround for chipidea PORTSC.PEC bug misc: open-dice: make OPEN_DICE depend on HAS_IOMEM serial: cpm_uart: Avoid suspicious locking scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() tools: iio: iio_generic_buffer: Fix some integer type and calculation usb: gadget: fsl_qe_udc: validate endpoint index for ch9 udc usb: cdns3: Put the cdns set active part outside the spin lock media: pci: cx23885: replace BUG with error return media: tuners: qt1010: replace BUG_ON with a regular error scsi: lpfc: Abort outstanding ELS cmds when mailbox timeout error is detected media: dvb-usb-v2: gl861: Fix null-ptr-deref in gl861_i2c_master_xfer media: az6007: Fix null-ptr-deref in az6007_i2c_xfer() media: anysee: fix null-ptr-deref in anysee_master_xfer media: af9005: Fix null-ptr-deref in af9005_i2c_xfer media: dw2102: Fix null-ptr-deref in dw2102_i2c_transfer() media: dvb-usb-v2: af9035: Fix null-ptr-deref in af9035_i2c_master_xfer media: mdp3: Fix resource leaks in of_find_device_by_node PCI: fu740: Set the number of MSI vectors PCI: vmd: Disable bridge window for domain reset powerpc/pseries: fix possible memory leak in ibmebus_bus_init() ARM: 9317/1: kexec: Make smp stop calls asynchronous PCI: dwc:
[Kernel-packages] [Bug 2038685] Re: Missing BTF file in Ubuntu ESM kernels
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038685 Title: Missing BTF file in Ubuntu ESM kernels Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: New Status in linux source package in Xenial: New Status in linux source package in Bionic: New Bug description: This is a follow-up from: https://discourse.ubuntu.com/t/ask-us- anything-about-ubuntu-kernels/27664/142 Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it. However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file. P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-4.15.0-218-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2021-05-18 (870 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-218-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 4.15.0-218.229-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-218-generic N/A linux-backports-modules-4.15.0-218-generic N/A linux-firmware 1.173.21 RfKill: Tags: bionic Uname: Linux 4.15.0-218-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 2038830] [NEW] Jammy update: v6.1.54 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: v6.1.54 upstream stable release from git://git.kernel.org/ Linux 6.1.54 drm/amd/display: Fix a bug when searching for insert_above_mpcc MIPS: Only fiddle with CHECKFLAGS if `need-compiler' kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg(). ixgbe: fix timestamp configuration code tcp: Fix bind() regression for v4-mapped-v6 non-wildcard address. tcp: Fix bind() regression for v4-mapped-v6 wildcard address. tcp: Factorise sk_family-independent comparison in inet_bind2_bucket_match(_addr_any). ipv6: Remove in6addr_any alternatives. ipv6: fix ip6_sock_set_addr_preferences() typo net: macb: fix sleep inside spinlock net: macb: Enable PTP unicast net/tls: do not free tls_rec on async operation in bpf_exec_tx_verdict() platform/mellanox: NVSW_SN2201 should depend on ACPI platform/mellanox: mlxbf-pmc: Fix reading of unprogrammed events platform/mellanox: mlxbf-pmc: Fix potential buffer overflows platform/mellanox: mlxbf-tmfifo: Drop jumbo frames platform/mellanox: mlxbf-tmfifo: Drop the Rx packet if no more descriptors kcm: Fix memory leak in error path of kcm_sendmsg() r8152: check budget for r8152_poll() net: dsa: sja1105: block FDB accesses that are concurrent with a switch reset net: dsa: sja1105: serialize sja1105_port_mcast_flood() with other FDB accesses net: dsa: sja1105: fix multicast forwarding working only for last added mdb entry net: dsa: sja1105: propagate exact error code from sja1105_dynamic_config_poll_valid() net: dsa: sja1105: hide all multicast addresses from "bridge fdb show" net:ethernet:adi:adin1110: Fix forwarding offload net: ethernet: adi: adin1110: use eth_broadcast_addr() to assign broadcast address hsr: Fix uninit-value access in fill_frame_info() net: ethernet: mtk_eth_soc: fix possible NULL pointer dereference in mtk_hwlro_get_fdir_all() net: ethernet: mvpp2_main: fix possible OOB write in mvpp2_ethtool_get_rxnfc() net: stmmac: fix handling of zero coalescing tx-usecs net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add selftests: Keep symlinks, when possible kselftest/runner.sh: Propagate SIGTERM to runner child net: ipv4: fix one memleak in __inet_del_ifa() kunit: Fix wild-memory-access bug in kunit_free_suite_set() drm/amdgpu: register a dirty framebuffer callback for fbcon drm/amd/display: Remove wait while locked drm/amd/display: always switch off ODM before committing more streams perf hists browser: Fix the number of entries for 'e' key perf tools: Handle old data in PERF_RECORD_ATTR perf test shell stat_bpf_counters: Fix test on Intel perf hists browser: Fix hierarchy mode header MIPS: Fix CONFIG_CPU_DADDI_WORKAROUNDS `modules_install' regression KVM: SVM: Skip VMSA init in sev_es_init_vmcb() if pointer is NULL KVM: SVM: Set target pCPU during IRTE update if target vCPU is running KVM: nSVM: Load L1's TSC multiplier based on L1 state, not L2 state KVM: nSVM: Check instead of asserting on nested TSC scaling support KVM: SVM: Get source vCPUs from source VM for SEV-ES intrahost migration KVM: SVM: Don't inject #UD if KVM attempts to skip SEV guest insn KVM: SVM: Take and hold ir_list_lock when updating vCPU's Physical ID entry drm/amd/display: prevent potential division by zero errors drm/amd/display: enable cursor degamma for DCN3+ DRM legacy gamma mtd: rawnand: brcmnand: Fix ECC level field setting for v7.2 controller mtd: rawnand: brcmnand: Fix potential false time out warning mtd: spi-nor: Correct flags for Winbond w25q128 mtd: rawnand: brcmnand: Fix potential out-of-bounds access in oob write mtd: rawnand: brcmnand: Fix crash during the panic_write drm/mxsfb: Disable overlay plane in mxsfb_plane_overlay_atomic_disable() btrfs: use the correct superblock to compare fsid in btrfs_validate_super btrfs: zoned: re-enable metadata over-commit for zoned mode btrfs: set page extent mapped after read_folio in relocate_one_page btrfs: don't start transaction when joining with TRANS_JOIN_NOSTART btrfs: free qgroup rsv on io failure btrfs: fix start transaction qgroup rsv double free btrfs: zoned: do not zone finish data relocation block group fuse: nlookup missing decrement in fuse_direntplus_link ata: pata_ftide010: Add missing MODULE_DESCRIPTION ata: sata_gemini: Add missing MODULE_DESCRIPTION ata: pata_falcon: fix IO base selection for Q40 ata: ahci: Add Elkhart Lake AHCI controller hwspinlock: qcom: add missing regmap config for SFPB MMIO implementation lib: test_scanf: Add explicit type cast to result initialization in test_number_prefix()
[Kernel-packages] [Bug 2038768] Re: arm64: linux: stress-ng filename stressor crashes kernel
Did an hour of soak testing with arm64 kernel https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.5.6/arm64/linux-image- unsigned-6.5.6-060506-generic_6.5.6-060506.202310061235_arm64.deb and cannot reproduce this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038768 Title: arm64: linux: stress-ng filename stressor crashes kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Mantic: Incomplete Bug description: Running latest Ubuntu mantic (ext4 file system) with kernel: Linux mantic-arm64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux How to reproduce: Fire up a 24 instance ARM64 QEMU instance with Ubuntu Mantic Server. Install latest stress-ng from git repo: sudo apt-get update sudo apt-get build-dep stress-ng git clone git://github.com/ColinIanKing/stress-ng cd stress-ng make clean make -j 24 make verify-test-all When we reach the filename stressor the kernel crashes as follows: [ 902.594715] kernel BUG at fs/dcache.c:2050! [ 902.598205] Internal error: Oops - BUG: f2000800 [#1] SMP [ 902.603127] Modules linked in: dccp_ipv4 dccp atm vfio_iommu_type1 vfio iommu fd cmac algif_rng twofish_generic twofish_common serpent_generic fcrypt cast6_ge neric cast5_generic cast_common camellia_generic blowfish_generic blowfish_commo n aes_arm64 algif_skcipher algif_hash aria_generic sm4_generic sm4_neon ccm aes_ ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg cfg80211 binfmt_mis c nls_iso8859_1 dm_multipath drm efi_pstore dmi_sysfs qemu_fw_cfg ip_tables x_ta bles autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipa th linear crct10dif_ce polyval_ce polyval_generic ghash_ce sm4 sha2_ce sha256_ar m64 sha1_ce arm_smccc_trng xhci_pci virtio_rng xhci_pci_renesas aes_neon_bs aes_ neon_blk aes_ce_blk aes_ce_cipher [ 902.689941] CPU: 1 PID: 91317 Comm: stress-ng-filen Not tainted 6.5.0-7-gener ic #7-Ubuntu [ 902.699281] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 902.706902] pstate: 4045 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 902.715488] pc : d_instantiate_new+0xa8/0xc8 [ 902.720889] lr : ext4_add_nondir+0x10c/0x160 [ 902.725702] sp : 80008b6d3930 [ 902.729390] x29: 80008b6d3930 x28: x27: bd164e51a980 [ 902.738705] x26: 6789f3b68f20 x25: 8180 x24: 678a541f7968 [ 902.747003] x23: 6789f3b68f00 x22: 80008b6d39b0 x21: 678a6a25bcb0 [ 902.755776] x20: 678a36f8f028 x19: x18: 80008af45068 [ 902.764647] x17: x16: x15: ecececececececec [ 902.773135] x14: ecececececececec x13: ecececececececec x12: ecececececececec [ 902.781386] x11: ecececececececec x10: ecececececececec x9 : bd164d5990bc [ 902.789346] x8 : x7 : x6 : [ 902.798564] x5 : x4 : x3 : [ 902.806851] x2 : bd16504e4ce0 x1 : 678a36f8f028 x0 : 6789f3b68f00 [ 902.815544] Call trace: [ 902.818870] d_instantiate_new+0xa8/0xc8 [ 902.823523] ext4_create+0x120/0x238 [ 902.827716] lookup_open.isra.0+0x480/0x4d0 [ 902.832480] open_last_lookups+0x160/0x3b0 [ 902.837060] path_openat+0xa0/0x2a0 [ 902.840975] do_filp_open+0xa8/0x180 [ 902.845582] do_sys_openat2+0xe8/0x128 [ 902.850426] __arm64_sys_openat+0x70/0xe0 [ 902.854952] invoke_syscall+0x7c/0x128 [ 902.859155] el0_svc_common.constprop.0+0x5c/0x168 [ 902.864979] do_el0_svc+0x38/0x68 [ 902.869364] el0_svc+0x30/0xe0 [ 902.873401] el0t_64_sync_handler+0x148/0x158 [ 902.878336] el0t_64_sync+0x1b0/0x1b8 [ 902.882513] Code: d282 d2800010 d2800011 d65f03c0 (d421) [ 902.890632] ---[ end trace ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038768/+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 2038832] [NEW] Jammy update: v6.1.56 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: v6.1.56 upstream stable release from git://git.kernel.org/ Linux 6.1.56 ASoC: amd: yc: Fix a non-functional mic on Lenovo 82TL mm, memcg: reconsider kmem.limit_in_bytes deprecation memcg: drop kmem.limit_in_bytes drm/meson: fix memory leak on ->hpd_notify callback drm/amdkfd: Use gpu_offset for user queue's wptr fs: binfmt_elf_efpic: fix personality for ELF-FDPIC power: supply: ab8500: Set typing and props power: supply: rk817: Add missing module alias drm/i915/gt: Fix reservation address in ggtt_reserve_guc_top ata: libata-sata: increase PMP SRST timeout to 10s ata: libata-core: Do not register PM operations for SAS ports ata: libata-core: Fix port and device removal ata: libata-core: Fix ata_port_request_pm() locking fs/smb/client: Reset password pointer to NULL net: thunderbolt: Fix TCPv6 GSO checksum calculation bpf: Fix BTF_ID symbol generation collision in tools/ bpf: Fix BTF_ID symbol generation collision bpf: Add override check to kprobe multi link attach media: uvcvideo: Fix OOB read btrfs: properly report 0 avail for very full file systems ring-buffer: Update "shortest_full" in polling mm: memcontrol: fix GFP_NOFS recursion in memory.high enforcement mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy() mm/damon/vaddr-test: fix memory leak in damon_do_test_apply_three_regions() arm64: defconfig: remove CONFIG_COMMON_CLK_NPCM8XX=y drm/tests: Fix incorrect argument in drm_test_mm_insert_range timers: Tag (hr)timer softirq as hotplug safe Revert "SUNRPC dont update timeout value on connection reset" netfilter: nf_tables: fix kdoc warnings after gc rework sched/rt: Fix live lock between select_fallback_rq() and RT push kernel/sched: Modify initial boot task idle setup ASoC: amd: yc: Fix non-functional mic on Lenovo 82QF and 82UG i2c: i801: unregister tco_pdev in i801_probe() error path io_uring/fs: remove sqe->rw_flags checking from LINKAT ata: libata-scsi: ignore reserved bits for REPORT SUPPORTED OPERATION CODES ata: libata-scsi: link ata port and scsi device LoongArch: numa: Fix high_memory calculation LoongArch: Define relocation types for ABI v2.10 ALSA: hda: Disable power save for solving pop issue on Lenovo ThinkCentre M70q netfilter: nf_tables: disallow rule removal from chain binding nilfs2: fix potential use after free in nilfs_gccache_submit_read_data() serial: 8250_port: Check IRQ data before use Revert "tty: n_gsm: fix UAF in gsm_cleanup_mux" misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to probe mptcp: fix bogus receive window shrinkage with multiple subflows KVM: x86/mmu: Do not filter address spaces in for_each_tdp_mmu_root_yield_safe() KVM: x86/mmu: Open code leaf invalidation from mmu_notifier KVM: SVM: Fix TSC_AUX virtualization setup KVM: SVM: INTERCEPT_RDTSCP is never intercepted anyway x86/srso: Add SRSO mitigation for Hygon processors x86/sgx: Resolves SECS reclaim vs. page fault for EAUG race iommu/arm-smmu-v3: Fix soft lockup triggered by arm_smmu_mm_invalidate_range smack: Retrieve transmuting information in smack_inode_getsecurity() smack: Record transmuting in smk_transmuted nvme-pci: always return an ERR_PTR from nvme_pci_alloc_dev scsi: qla2xxx: Fix NULL pointer dereference in target mode wifi: ath11k: Don't drop tx_status when peer cannot be found nvme-pci: do not set the NUMA node of device if it has none nvme-pci: factor out a nvme_pci_alloc_dev helper nvme-pci: factor the iod mempool creation into a helper perf build: Define YYNOMEM as YYNOABORT for bison < 3.81 fbdev/sh7760fb: Depend on FB=y LoongArch: Set all reserved memblocks on Node#0 at initialization tsnep: Fix NAPI polling with budget 0 tsnep: Fix NAPI scheduling net: hsr: Add __packed to struct hsr_sup_tlv. ncsi: Propagate carrier gain/loss events to the NCSI controller powerpc/watchpoints: Annotate atomic context in more places powerpc/watchpoint: Disable pagefaults when getting user instruction powerpc/watchpoints: Disable preemption in thread_change_pc() ASoC: SOF: Intel: MTL: Reduce the DSP init timeout NFSv4.1: fix zero value filehandle in post open getattr media: vb2: frame_vector.c: replace WARN_ONCE with a comment ASoC: imx-rpmsg: Set ignore_pmdown_time for dai_link memblock tests: fix warning ‘struct seq_file’ declared inside parameter list memblock tests: fix warning: "__ALIGN_KERNEL" redefined firmware: cirrus: cs_dsp: Only log list of algorithms in debug build ASoC: cs42l42: Don't rely on GPIOD_OUT_LOW to set RESET initially low ASoC: cs42l42: Ensure a reset
Re: [Kernel-packages] [Bug 2038436] Re: System doesnt recognize second monitor
Glad to help, so is it fixed in the next update? or i need to do it manually On Mon, Oct 9, 2023, 5:30 PM Daniel van Vugt <2038...@bugs.launchpad.net> wrote: > Thanks. That confirms it's the kernel not detecting the monitor. > > ** Package changed: ubuntu => linux-hwe-6.2 (Ubuntu) > > ** Changed in: linux-hwe-6.2 (Ubuntu) >Status: Incomplete => New > > ** Summary changed: > > - System doesnt recognize second monitor > + [i915] System doesn't recognize second monitor > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2038436 > > Title: > [i915] System doesn't recognize second monitor > > Status in linux-hwe-6.2 package in Ubuntu: > New > > Bug description: > I am using an old monitor which using a DVI connectors but I used a > DVI to HDMI adapter which works fine on Windows operating system... My > monitor is HP W2072a... I hope with the information provided helps... > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: xorg 1:7.7+23ubuntu2 > ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 > Uname: Linux 6.2.0-34-generic x86_64 > ApportVersion: 2.20.11-0ubuntu82.5 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: pass > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Oct 4 21:17:37 2023 > DistUpgraded: Fresh install > DistroCodename: jammy > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Alder Lake-P Integrated Graphics Controller > [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) > Subsystem: Device [1b50:1018] > InstallationDate: Installed on 2023-09-30 (3 days ago) > InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 > (20230807.2) > MachineType: ILLEGEAR SDN BHD ATOMIC 16 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic > root=UUID=e60cc65c-b597-415b-b294-3cb6a76ecbd0 ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/26/2022 > dmi.bios.release: 0.2 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: Q3AIL.02 > dmi.board.asset.tag: Default string be filled by O.E.M > dmi.board.name: ATOMIC > dmi.board.vendor: ILLEGEAR SDN BHD > dmi.board.version: Default string be filled by O.E.M > dmi.chassis.asset.tag: Default string be filled by O.E.M > dmi.chassis.type: 9 > dmi.chassis.vendor: Default string be filled by O.E.M > dmi.chassis.version: Default string be filled by O.E.M > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrQ3AIL.02:bd07/26/2022:br0.2:svnILLEGEARSDNBHD:pnATOMIC16:pvrDefaultstringbefilledbyO.E.M:rvnILLEGEARSDNBHD:rnATOMIC:rvrDefaultstringbefilledbyO.E.M:cvnDefaultstringbefilledbyO.E.M:ct9:cvrDefaultstringbefilledbyO.E.M:skuATOMIC16-ADL1: > dmi.product.family: ATOMIC > dmi.product.name: ATOMIC 16 > dmi.product.sku: ATOMIC16-ADL1 > dmi.product.version: Default string be filled by O.E.M > dmi.sys.vendor: ILLEGEAR SDN BHD > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20210115-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.17-2build1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2038436/+subscriptions > > -- 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/2038436 Title: [i915] System doesn't recognize second monitor Status in linux-hwe-6.2 package in Ubuntu: New Bug description: I am using an old monitor which using a DVI connectors but I used a DVI to HDMI adapter which works fine on Windows operating system... My monitor is HP W2072a... I hope with the information provided helps... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 21:17:37 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical
[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- azure/4.15.0-1170.185~14.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty-linux- azure' to 'verification-done-trusty-linux-azure'. If the problem still exists, change the tag 'verification-needed-trusty-linux-azure' to 'verification-failed-trusty-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-trusty-linux-azure-v2 verification-needed-trusty-linux-azure -- 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 2035133] Re: linux-libc-dev:i386 is not produced anymore
This bug is awaiting verification that the linux- azure/4.15.0-1170.185~14.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty-linux- azure' to 'verification-done-trusty-linux-azure'. If the problem still exists, change the tag 'verification-needed-trusty-linux-azure' to 'verification-failed-trusty-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-trusty-linux-azure-v2 verification-needed-trusty-linux-azure -- 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/2035133 Title: linux-libc-dev:i386 is not produced anymore Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] On Bionic, after i386 and other architectures were dropped from building, linux-libc-dev:i386 stopped being produced. That stills needs to be produced for userspace multi-arch support. Otherwise installing newer linux-libc-dev binaries will remove the i386 version of it, as they need to be the same version. [Test case] Install linux-libc-dev and linux-libc-dev:i386 prepared by the same source package. [Potential regression] Packages may fail to build or different config options may be enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035133/+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 2035390] Re: kvm-amd crashes when loaded at svm_init
This bug is awaiting verification that the linux- azure/4.15.0-1170.185~14.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty-linux- azure' to 'verification-done-trusty-linux-azure'. If the problem still exists, change the tag 'verification-needed-trusty-linux-azure' to 'verification-failed-trusty-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-trusty-linux-azure-v2 verification-needed-trusty-linux-azure -- 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/2035390 Title: kvm-amd crashes when loaded at svm_init Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Loading kvm-amd crashes at svm_init preventing the use of KVM on AMD systems. [Test case] Load kvm_amd and start a KVM guest. [Potential regression] KVM initialization may be broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035390/+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 2032338] Re: HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060)
Ok, let's see. Thank you. -- 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/2032338 Title: HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060) Status in linux-firmware package in Ubuntu: Invalid Bug description: $ apt show linux-firmware Package: linux-firmware Version: 20220329.git681281e4-0ubuntu3.17 Priority: optional Section: misc Origin: Ubuntu Maintainer: Ubuntu Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 999 MB Provides: atmel-firmware Recommends: firmware-sof-signed Conflicts: atmel-firmware Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), linux-firmware-snapdragon (<= 1.2-0ubuntu1) Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), linux-restricted-common Download-Size: 254 MB APT-Manual-Installed: yes APT-Sources: http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages Description: Firmware for Linux kernel drivers This package provides firmware used by Linux kernel drivers. N: There are 2 additional records. Please use the '-a' switch to see them. # update-initramfs -u update-initramfs: Generating /boot/initrd.img-6.2.0-26-generic cryptsetup: WARNING: swap: couldn't determine device type, assuming default (plain). cryptsetup: WARNING: Resume target swap uses a key file W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/NET_img.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/NET_img.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/NET_img.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/gr/NET_img.bin for module nouveau W: Possible missing firmware
[Kernel-packages] [Bug 2033418] Re: Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default
Discussing this internally, it was suggested to use:
fbcon=map:X
With X = 0, I see the same behavior (boot process on the BMC, X on
whatever is set)
And other values for X just blank the boot process on both outputs (BMC
and HDMI).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2033418
Title:
Ubuntu desktop does not appear on DGX Station A100 discrete GPU by
default
Status in linux-nvidia package in Ubuntu:
New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
New
Bug description:
The DGX Station A10 has various display options. The BMC provides an
emulated device (Aspeed controller), a physical BMC controller (NVIDIA
Quadro T1000 Mobile), and a discrete GPU card with 4 DisplayPort
outputs (A100 SXM4 80GB). See the user guide[*] for a diagram.
In a default Ubuntu Desktop 22.04 ('jammy') install, nothing appears
on the A100 DisplayPort output.
NVIDIA DGX OS - a derivative of Ubuntu - works around this by
installing a service that generates an xorg config file dynamically
based on the "OnBrd/Ext VGA Select" setting (aka "dmidecode -t 11").
I'll attach samples of those files here. Replacing the default Ubuntu
xorg.conf file with the sample xorg-nvidia.conf file on a default
Ubuntu Desktop install is confirmed to enable output.
[*] https://docs.nvidia.com/dgx/dgx-station-a100-user-guide/getting-
started-station-a100.html
(Note: split from bug 2031367)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2033418/+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 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash
The log messages specifically refer to lightdm,
"2023-10-08T16:35:59.205065+00:00 ubuntu-budgie lightdm[1890]: df:
/sys/firmware/efi/efivars: Invalid argument", and I noticed this patch
in lightdm:
https://git.launchpad.net/ubuntu/+source/lightdm/tree/debian/patches/04_language_handling.patch?h=applied/ubuntu/devel#n79
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038765
Title:
df: /sys/firmware/efi/efivars: Invalid argument causes installation
crash
Status in lightdm package in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
df: /sys/firmware/efi/efivars: Invalid argument appears on first
display of the live session - I note subsequently that at the end of
the installation curtin fails due to an efivars error - looking at
syslog I saw various efivars errors so I'm filing this with the kernel
since this is the first instance.
i.e. running grep efivars /var/log/*
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber
/dev/snd/seq:ubuntu-budgie 2074 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CasperVersion: 1.486
CurrentDesktop: Budgie:GNOME
Date: Sun Oct 8 16:27:29 2023
LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64
(20231008.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-7-generic N/A
linux-backports-modules-6.5.0-7-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/2038765/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036627] Re: Azure: net: mana: Configure hwc timeout from hardware
This bug was fixed in the package linux-azure - 6.5.0-1007.7 --- linux-azure (6.5.0-1007.7) mantic; urgency=medium * mantic/linux-azure: 6.5.0-1007.7 -proposed tracker (LP: #2038690) * Azure: net: mana: Configure hwc timeout from hardware (LP: #2036627) - net: mana: Configure hwc timeout from hardware [ Ubuntu: 6.5.0-9.9 ] * mantic/linux: 6.5.0-9.9 -proposed tracker (LP: #2038687) * update apparmor and LSM stacking patch set (LP: #2028253) - re-apply apparmor 4.0.0 * Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature (LP: #2038567) - SAUCE: apparmor: Make apparmor_restrict_unprivileged_unconfined opt-in [ Ubuntu: 6.5.0-8.8 ] * mantic/linux: 6.5.0-8.8 -proposed tracker (LP: #2038577) * update apparmor and LSM stacking patch set (LP: #2028253) - SAUCE: apparmor3.2.0 [02/60]: rename SK_CTX() to aa_sock and make it an inline fn - SAUCE: apparmor3.2.0 [05/60]: Add sysctls for additional controls of unpriv userns restrictions - SAUCE: apparmor3.2.0 [08/60]: Stacking v38: LSM: Identify modules by more than name - SAUCE: apparmor3.2.0 [09/60]: Stacking v38: LSM: Add an LSM identifier for external use - SAUCE: apparmor3.2.0 [10/60]: Stacking v38: LSM: Identify the process attributes for each module - SAUCE: apparmor3.2.0 [11/60]: Stacking v38: LSM: Maintain a table of LSM attribute data - SAUCE: apparmor3.2.0 [12/60]: Stacking v38: proc: Use lsmids instead of lsm names for attrs - SAUCE: apparmor3.2.0 [13/60]: Stacking v38: integrity: disassociate ima_filter_rule from security_audit_rule - SAUCE: apparmor3.2.0 [14/60]: Stacking v38: LSM: Infrastructure management of the sock security - SAUCE: apparmor3.2.0 [15/60]: Stacking v38: LSM: Add the lsmblob data structure. - SAUCE: apparmor3.2.0 [16/60]: Stacking v38: LSM: provide lsm name and id slot mappings - SAUCE: apparmor3.2.0 [17/60]: Stacking v38: IMA: avoid label collisions with stacked LSMs - SAUCE: apparmor3.2.0 [18/60]: Stacking v38: LSM: Use lsmblob in security_audit_rule_match - SAUCE: apparmor3.2.0 [19/60]: Stacking v38: LSM: Use lsmblob in security_kernel_act_as - SAUCE: apparmor3.2.0 [20/60]: Stacking v38: LSM: Use lsmblob in security_secctx_to_secid - SAUCE: apparmor3.2.0 [21/60]: Stacking v38: LSM: Use lsmblob in security_secid_to_secctx - SAUCE: apparmor3.2.0 [22/60]: Stacking v38: LSM: Use lsmblob in security_ipc_getsecid - SAUCE: apparmor3.2.0 [23/60]: Stacking v38: LSM: Use lsmblob in security_current_getsecid - SAUCE: apparmor3.2.0 [24/60]: Stacking v38: LSM: Use lsmblob in security_inode_getsecid - SAUCE: apparmor3.2.0 [25/60]: Stacking v38: LSM: Use lsmblob in security_cred_getsecid - SAUCE: apparmor3.2.0 [26/60]: Stacking v38: LSM: Specify which LSM to display - SAUCE: apparmor3.2.0 [28/60]: Stacking v38: LSM: Ensure the correct LSM context releaser - SAUCE: apparmor3.2.0 [29/60]: Stacking v38: LSM: Use lsmcontext in security_secid_to_secctx - SAUCE: apparmor3.2.0 [30/60]: Stacking v38: LSM: Use lsmcontext in security_inode_getsecctx - SAUCE: apparmor3.2.0 [31/60]: Stacking v38: Use lsmcontext in security_dentry_init_security - SAUCE: apparmor3.2.0 [32/60]: Stacking v38: LSM: security_secid_to_secctx in netlink netfilter - SAUCE: apparmor3.2.0 [33/60]: Stacking v38: NET: Store LSM netlabel data in a lsmblob - SAUCE: apparmor3.2.0 [34/60]: Stacking v38: binder: Pass LSM identifier for confirmation - SAUCE: apparmor3.2.0 [35/60]: Stacking v38: LSM: security_secid_to_secctx module selection - SAUCE: apparmor3.2.0 [36/60]: Stacking v38: Audit: Keep multiple LSM data in audit_names - SAUCE: apparmor3.2.0 [37/60]: Stacking v38: Audit: Create audit_stamp structure - SAUCE: apparmor3.2.0 [38/60]: Stacking v38: LSM: Add a function to report multiple LSMs - SAUCE: apparmor3.2.0 [39/60]: Stacking v38: Audit: Allow multiple records in an audit_buffer - SAUCE: apparmor3.2.0 [40/60]: Stacking v38: Audit: Add record for multiple task security contexts - SAUCE: apparmor3.2.0 [41/60]: Stacking v38: audit: multiple subject lsm values for netlabel - SAUCE: apparmor3.2.0 [42/60]: Stacking v38: Audit: Add record for multiple object contexts - SAUCE: apparmor3.2.0 [43/60]: Stacking v38: netlabel: Use a struct lsmblob in audit data - SAUCE: apparmor3.2.0 [44/60]: Stacking v38: LSM: Removed scaffolding function lsmcontext_init - SAUCE: apparmor3.2.0 [45/60]: Stacking v38: AppArmor: Remove the exclusive flag - SAUCE: apparmor3.2.0 [46/60]: combine common_audit_data and apparmor_audit_data - SAUCE: apparmor3.2.0 [47/60]: setup
[Kernel-packages] [Bug 2025640] Re: Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to 535.54.03 video output cuts out
This bug was fixed in the package nvidia-graphics-drivers-535-server - 535.104.12-0ubuntu2 --- nvidia-graphics-drivers-535-server (535.104.12-0ubuntu2) mantic; urgency=medium * debian/rules: - Add override_dh_installsystemd. - Pass in --no-stop-on-upgrade --no-restart-after-upgrade to dh_installsystemd (LP: #2025640). -- Alberto Milone Fri, 29 Sep 2023 19:12:51 + ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2025640 Title: Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to 535.54.03 video output cuts out Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 source package in Focal: In Progress Status in nvidia-graphics-drivers-535-server source package in Focal: In Progress Status in nvidia-graphics-drivers-535 source package in Jammy: In Progress Status in nvidia-graphics-drivers-535-server source package in Jammy: In Progress Status in nvidia-graphics-drivers-535 source package in Lunar: In Progress Status in nvidia-graphics-drivers-535-server source package in Lunar: In Progress Bug description: [Impact] The current version nvidia-graphics-drivers-535 and nvidia-graphics- drivers-535-server, from Focal on, use the default values (from the debian compat 10) for dh_installsystemd which cause all the systemd services to be restarted on upgrade. This will cause the screen to go blank and never wake up. [Test Case] Install the nvidia-driver: sudo ubuntu-drivers install nvidia:535 Try re-installing nvidia-kernel-common-535 and nvidia-compute- utils-535: sudo apt --reinstall nvidia-kernel-common-535 nvidia-compute-utils-535 The screen will go black. [Where problems could occur] On servers with no display server in use, if, for some reason, restarting services such as nvidia-persistenced on upgrade is a desired feature, this will not take place any more. _ https://forums.developer.nvidia.com/t/ubuntu-22-04-in-the-middle-of-updating-drivers-from-530-41-03-to-535-54-03-video-input-cuts-out/258588 https://forums.linuxmint.com/viewtopic.php?p=2344294 timeline 10:36 - 10:39 switch to TTY not helped-no video output, SSH not tested After emergency sync, reboot (by sysrq), is all fine. Jul 3 10:37:14 Panter nvidia-persistenced: Received signal 15 Jul 3 10:37:14 Panter systemd[1]: Stopping NVIDIA Persistence Daemon... Jul 3 10:37:14 Panter nvidia-persistenced: Socket closed. Jul 3 10:37:14 Panter nvidia-persistenced: PID file unlocked. Jul 3 10:37:14 Panter nvidia-persistenced: PID file closed. Jul 3 10:37:14 Panter nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Jul 3 10:37:14 Panter nvidia-persistenced: Shutdown (1085) Jul 3 10:37:14 Panter systemd[1]: nvidia-persistenced.service: Deactivated successfully. Jul 3 10:37:14 Panter systemd[1]: Stopped NVIDIA Persistence Daemon. Jul 3 10:37:19 Panter systemd[1]: Reloading. Jul 3 10:37:19 Panter systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Jul 3 10:37:19 Panter systemd[1]: Starting NVIDIA system hibernate actions... Jul 3 10:37:19 Panter hibernate: nvidia-hibernate.service Jul 3 10:37:19 Panter logger[9260]: <13>Jul 3 10:37:19 hibernate: nvidia-hibernate.service Jul 3 10:37:19 Panter kernel: [ 424.892353] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 16 Jul 3 10:37:19 Panter systemd[1]: nvidia-hibernate.service: Deactivated successfully. Jul 3 10:37:19 Panter systemd[1]: Finished NVIDIA system hibernate actions. Jul 3 10:37:20 Panter systemd[1]: Reloading. Jul 3 10:37:20 Panter systemd[1]: Starting NVIDIA system resume actions... Jul 3 10:37:20 Panter suspend: nvidia-resume.service Jul 3 10:37:20 Panter logger[9305]: <13>Jul 3 10:37:20 suspend: nvidia-resume.service Jul 3 10:37:20 Panter systemd[1]: nvidia-resume.service: Deactivated successfully. Jul 3 10:37:20 Panter systemd[1]: Finished NVIDIA system resume actions. Jul 3 10:37:20 Panter acpid: client 1346[0:0] has disconnected Jul 3 10:37:20 Panter rtkit-daemon[1537]: Supervising 7 threads of 3 processes of 1 users. Jul 3 10:37:20 Panter rtkit-daemon[1537]: Successfully made thread 9312 of process 1530 owned by '1000' RT at priority 5. Jul 3 10:37:20 Panter rtkit-daemon[1537]: Supervising 8 threads of 3 processes of 1 users. Jul 3 10:37:20 Panter acpid: client connected from 1346[0:0] Jul 3 10:37:20
[Kernel-packages] [Bug 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature
This bug was fixed in the package linux - 6.5.0-9.9 --- linux (6.5.0-9.9) mantic; urgency=medium * mantic/linux: 6.5.0-9.9 -proposed tracker (LP: #2038687) * update apparmor and LSM stacking patch set (LP: #2028253) - re-apply apparmor 4.0.0 * Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature (LP: #2038567) - SAUCE: apparmor: Make apparmor_restrict_unprivileged_unconfined opt-in -- Andrea Righi Fri, 06 Oct 2023 21:03:52 +0200 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038567 Title: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Triaged Status in snapd package in Ubuntu: New Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037266] Re: Update the 535 driver series - 25/09/2023
This bug was fixed in the package nvidia-graphics-drivers-535-server - 535.104.12-0ubuntu2 --- nvidia-graphics-drivers-535-server (535.104.12-0ubuntu2) mantic; urgency=medium * debian/rules: - Add override_dh_installsystemd. - Pass in --no-stop-on-upgrade --no-restart-after-upgrade to dh_installsystemd (LP: #2025640). -- Alberto Milone Fri, 29 Sep 2023 19:12:51 + ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2037266 Title: Update the 535 driver series - 25/09/2023 Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 source package in Focal: Fix Released Status in nvidia-graphics-drivers-535-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-535 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-535-server source package in Lunar: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] 535 (535.113.01): https://www.nvidia.com/Download/driverResults.aspx/211711/en-us/ 535-server (535.104.12): https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-104-12/index.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2037266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037316] Re: SEV_SNP failure to init
I did test the kernel from lunar proposed (6.2.0.1015.16) on AWS. The image boots with sev-snp enabled: # sudo dmesg | grep -i sev [5.563677] Memory Encryption Features active: AMD SEV SEV-ES SEV-SNP [6.140250] SEV: Using SNP CPUID table, 64 entries present. [8.507286] SEV: SNP guest platform device initialized. [ 20.829729] sev-guest sev-guest: Initialized SEV guest driver (using vmpck_id 0) # apt-cache policy linux-aws linux-aws: Installed: 6.2.0.1015.16 Candidate: 6.2.0.1015.16 Version table: *** 6.2.0.1015.16 100 100 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages 100 /var/lib/dpkg/status 6.2.0.1013.14 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu lunar-security/main amd64 Packages 6.2.0.1003.4 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu lunar/main amd64 Packages ** Tags removed: verification-needed-lunar-linux-aws ** Tags added: verification-done-lunar-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: Invalid Status in linux-gcp source package in Jammy: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038823] [NEW] package nvidia-dkms-510 510.60.02-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit st
Public bug reported: tried to install nvidia driver on fresh install ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-510 510.60.02-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Oct 9 09:13:49 2023 ErrorMessage: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-10-09 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: nvidia-graphics-drivers-510 Title: package nvidia-dkms-510 510.60.02-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/2038823 Title: package nvidia-dkms-510 510.60.02-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: tried to install nvidia driver on fresh install ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-510 510.60.02-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Oct 9 09:13:49 2023 ErrorMessage: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-10-09 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: nvidia-graphics-drivers-510 Title: package nvidia-dkms-510 510.60.02-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/2038823/+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 2032338] Re: HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060)
So it doesn't seem to be firmware related then? Closing the ticket. Please open a new one should you run into issues agaain. ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- 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/2032338 Title: HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060) Status in linux-firmware package in Ubuntu: Invalid Bug description: $ apt show linux-firmware Package: linux-firmware Version: 20220329.git681281e4-0ubuntu3.17 Priority: optional Section: misc Origin: Ubuntu Maintainer: Ubuntu Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 999 MB Provides: atmel-firmware Recommends: firmware-sof-signed Conflicts: atmel-firmware Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), linux-firmware-snapdragon (<= 1.2-0ubuntu1) Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), linux-restricted-common Download-Size: 254 MB APT-Manual-Installed: yes APT-Sources: http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages Description: Firmware for Linux kernel drivers This package provides firmware used by Linux kernel drivers. N: There are 2 additional records. Please use the '-a' switch to see them. # update-initramfs -u update-initramfs: Generating /boot/initrd.img-6.2.0-26-generic cryptsetup: WARNING: swap: couldn't determine device type, assuming default (plain). cryptsetup: WARNING: Resume target swap uses a key file W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/NET_img.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/NET_img.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/NET_img.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/fecs_bl.bin for
[Kernel-packages] [Bug 2032338] Re: HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060)
-- 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/2032338 Title: HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060) Status in linux-firmware package in Ubuntu: Invalid Bug description: $ apt show linux-firmware Package: linux-firmware Version: 20220329.git681281e4-0ubuntu3.17 Priority: optional Section: misc Origin: Ubuntu Maintainer: Ubuntu Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 999 MB Provides: atmel-firmware Recommends: firmware-sof-signed Conflicts: atmel-firmware Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), linux-firmware-snapdragon (<= 1.2-0ubuntu1) Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), linux-restricted-common Download-Size: 254 MB APT-Manual-Installed: yes APT-Sources: http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages Description: Firmware for Linux kernel drivers This package provides firmware used by Linux kernel drivers. N: There are 2 additional records. Please use the '-a' switch to see them. # update-initramfs -u update-initramfs: Generating /boot/initrd.img-6.2.0-26-generic cryptsetup: WARNING: swap: couldn't determine device type, assuming default (plain). cryptsetup: WARNING: Resume target swap uses a key file W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/NET_img.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/NET_img.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/NET_img.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/gr/NET_img.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/gr/gpccs_sig.bin for module
[Kernel-packages] [Bug 2033124] Re: Intel AX201 wifi card is hardware blocked/RF_KILL after suspend/resume
Sounds like a BIOS bug. Does anything happen if you press the airplane hot key? Also is there a difference in loaded modules before and after suspend/resume? You could also try to blacklist any hp modules but that probably won't do much. ** Changed in: linux-firmware (Ubuntu) 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/2033124 Title: Intel AX201 wifi card is hardware blocked/RF_KILL after suspend/resume Status in linux-firmware package in Ubuntu: Incomplete Bug description: I have HP 340S G7 laptop where the Intel AX201 REV=0x332 card is stuck in RF_KILL after suspend. From googling this it appears I am not the only one having problems with this card, but I can't seem to find any solution to the problem. I have the latest BIOS available (F27 11/21/2022). Before with BIOS version F13 the Wifi was not working at all, and by upgrading to the latest it at least works until suspend. I have tested cloning linux-firmware and copying all the iwlwifi-* firmwares into /lib/firmware, which does not seem to do anything. I'm not sure why but the laptop continues to want to use 72.daa05125.0 Qu-c0-hr-b0-72.ucode even if a higher number file is available in the folder. I thought the last number was a version but I was guessing. There are multiple ACPI errors / BIOS Error (bug) in the log. I will upload those logs shortly I just need to get them out of the laptop :) I have tested this on the latest Ubuntu 22.04.3 LTS as per now, and also 23.04 and latest Alpine Linux. Kernel: 6.2.0-27-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2033124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
The latest maas images from 20231008 are booting without issue: ubuntu@akis:~$ lsb_release -sc No LSB modules are available. mantic ubuntu@akis:~$ cat /etc/cloud/build.info build_name: server serial: 20231008 ubuntu@akis:~$ uname -a Linux akis 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in cloud-images: New Status in maas-images: Confirmed Status in The Ubuntu-power-systems project: Invalid Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Fix Released Status in linux source package in Mantic: Invalid Status in systemd source package in Mantic: Invalid Status in util-linux source package in Mantic: Fix Released Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036627] Re: Azure: net: mana: Configure hwc timeout from hardware
This bug is awaiting verification that the linux-azure/6.2.0-1016.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-azure' to 'verification-done-lunar- linux-azure'. If the problem still exists, change the tag 'verification- needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-azure-v2 verification-needed-lunar-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2036627 Title: Azure: net: mana: Configure hwc timeout from hardware Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] At present hwc timeout value is a fixed value. This patch sets the hwc timeout from the hardware. It now uses a new hardware capability GDMA_DRV_CAP_FLAG_1_HWC_TIMEOUT_RECONFIG to query and set the value in hwc_timeout. [Test Plan] Microsoft tested and approved. [Regression Potential] Timeouts could get mis-configured. [Other Info] SF: #00365762 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature
cloud minimized and non minimized images have now been tested with 6.5.0-9 kernel from -proposed and pass our lxd-start-stop test suite which was failing and which is the test suite which prompted this whole thread. +1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038567 Title: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in lxd package in Ubuntu: Triaged Status in snapd package in Ubuntu: New Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013027] Re: Issues over broadcom brcmfmac43455 firmware
Not sure why you think the driver doesn't load a vendored clm_blob. That works fine on a Raspberry Pi. -- 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/2013027 Title: Issues over broadcom brcmfmac43455 firmware Status in linux-firmware package in Ubuntu: Expired Status in linux-firmware-raspi2 package in Ubuntu: Invalid Bug description: Hi, I have a Kodlix Z83-II minicomputer that employs a broadcom chipset for WIFI. The only way to make wifi on that PC work is to use the firmware from the windows image, even if that chipset is apparently managed in ubuntu. With the firmware files provided by ubuntu you get no 5GHz for wifi. The problem is that every time ubuntu updates the firmware package, firmware files dropped in /lib/firmware get overwritten, linking to some file in the cypress sub-directory. - Ideally, Ubuntu should provide all the firmware files that might be needed. Maybe this is not possible as there is a too large variety of different firmwares for broadcom chipsets or licesing issues preventing distribution. - As a second possibility, there should be a way to drop files in /lib/firmware 'side to side' to the distro ones, without having the risk of finding the manually added files rewritten. This implies that different pieces of hardware use firmware files with different filenames. Don't know if this is truly possible, as I do not know how the linux kernel decides the name of the firmware to load. - In cases like mine, it seems that the ubuntu firmware package puts in place symlinks to have brcmfmac43455 files point to the corresponding cypress cyfmac43455 files. Possibly, the package could avoid creating the symlinks if a brcmfmac43455 file is manually placed in lib/firmware. - As a last resort, I think that the documentation in `/usr/share/doc/linux-firmware` should be augmented to describe the most appropriate way to prevent custom firmware files from being rewritten: marking files not-writable? introducing diversions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024427] Re: S3 stress issue for amdgpu Navi 31/Navi33
This bug was fixed in the package linux-firmware - 20230323.gitbcdcfbcf-0ubuntu1.7 --- linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.7) lunar; urgency=medium * linux-firmware is outdated (LP: #2033441) - nvidia: update Tu10x and Tu11x signed firmware to support newer Turing HW * S3 stress issue for amdgpu Navi 31/Navi33 (LP: #2024427) - amdgpu: update GC 11.0.0 firmware for amd.5.5 release - amdgpu: update GC 11.0.2 firmware for amd.5.5 release -- Juerg Haefliger Fri, 22 Sep 2023 15:04:35 +0200 ** Changed in: linux-firmware (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2024427 Title: S3 stress issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Triaged Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2024427 [Impact] Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms will sometimes fail to wake from S3. [Fix] kernel patches: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 firmware patches: * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release [Test Case] $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Little we know about the firmware fixes. However, while with these commits have been pulled via stable kernel fixes, the driver begins to request new firmware blobs of a different filename. [Other Info] The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has to be fixed. For the firmware parts, they have been included in linux-firmware/mantic, leaving linux-firmware/lunar and linux-firmware/jammy to be fixed. == original bug report == amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030882] Re: Jammy: NVIDIA Turing architecture firmware for Nouveau missing (TU117)
*** This bug is a duplicate of bug 2033441 *** https://bugs.launchpad.net/bugs/2033441 ** This bug has been marked a duplicate of bug 2033441 linux-firmware is outdated -- 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/2030882 Title: Jammy: NVIDIA Turing architecture firmware for Nouveau missing (TU117) Status in linux-firmware package in Ubuntu: Confirmed Bug description: Black screen when logging out in KDE Neon. Original bug report for KDE here: https://bugs.kde.org/show_bug.cgi?id=473144 --- Key points in the last comments: I wonder could it be related to this linux-firmware issue with NVIDIA Turing arch: https://gitlab.freedesktop.org/drm/nouveau/-/issues/207 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=2e92a49f90f73c8edc44b25c6e669d5e70893c90 Current linux-firmware package in Jammy is: 20220329.git681281e4-0ubuntu3.17 So that would be slightly older than the one where the NVIDIA fix was introduced (3rd April) - https://gitlab.freedesktop.org/drm/nouveau/-/issues/207 >Versions with this issue can boot with nomodeset kernel parameter. I added 'nomodeset' to the "linux" -line in Grub for kernel 6.2 and now the logout works. So this looks like it very likely is the firmware issue with Ubuntu Jammy. - So, this linux-firmware change would be needed: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=2e92a49f90f73c8edc44b25c6e669d5e70893c90 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2030882/+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 2033441] Re: linux-firmware is outdated
lunar released because upstream made it clear we need this, verified or
not
--
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/2033441
Title:
linux-firmware is outdated
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Confirmed
Status in linux-firmware source package in Lunar:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Released
Bug description:
[Impact]
This is optimus laptop with Intel 11th Gen and Nvidia.
In recent kernels like 6.2.0 it gives a blank screen after booting and if
nouveau.modset=1 is set, it completely freeze the system.
I remember it was working fine in 5.x kernels.
Now I have to blacklist nouveau and use Nvidia driver instead.
Using this commit of linux-firmware solved the issue:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/nvidia?id=2e92a49f90f73c8edc44b25c6e669d5e70893c90
[Fix]
Upstream commit 2e92a49f90f9 ("nvidia: update Tu10x and Tu11x signed
firmware to support newer Turing HW")
[Test Case]
Boot a machine with relevant GPU.
[Where Problems Could Occur]
Updated Nvidia FW so limited to machines with relevant GPUs.
[Additional Information]
# journalctl -b -2 | grep nouveau
Aug 29 21:07:54 ZB kernel: Command line: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic
root=/dev/mapper/vgubuntu-root ro nouveau.modeset=1 quiet splash
Aug 29 21:07:54 ZB kernel: Kernel command line:
BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro
nouveau.modeset=1 quiet splash
Aug 29 21:07:54 ZB kernel: nouveau: detected PR support, will not use DSM
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: enabling device ( ->
0003)
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: NVIDIA TU117 (167000a1)
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: bios: version 90.17.61.00.73
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: pmu: firmware unavailable
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: fb: 2048 MiB GDDR6
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: halted
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021
TIDX 1b1f
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2055
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2305
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 201c
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2303
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2051
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 269e
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2617
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 1822
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 1a97
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 26c8
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2318
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: VRAM: 2048 MiB
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: GART: 536870912 MiB
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: BIT table 'A' not found
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: BIT table 'L' not found
Aug 29 21:07:54 ZB kernel: nouveau
[Kernel-packages] [Bug 2033441] Update Released
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
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/2033441
Title:
linux-firmware is outdated
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Confirmed
Status in linux-firmware source package in Lunar:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Released
Bug description:
[Impact]
This is optimus laptop with Intel 11th Gen and Nvidia.
In recent kernels like 6.2.0 it gives a blank screen after booting and if
nouveau.modset=1 is set, it completely freeze the system.
I remember it was working fine in 5.x kernels.
Now I have to blacklist nouveau and use Nvidia driver instead.
Using this commit of linux-firmware solved the issue:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/nvidia?id=2e92a49f90f73c8edc44b25c6e669d5e70893c90
[Fix]
Upstream commit 2e92a49f90f9 ("nvidia: update Tu10x and Tu11x signed
firmware to support newer Turing HW")
[Test Case]
Boot a machine with relevant GPU.
[Where Problems Could Occur]
Updated Nvidia FW so limited to machines with relevant GPUs.
[Additional Information]
# journalctl -b -2 | grep nouveau
Aug 29 21:07:54 ZB kernel: Command line: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic
root=/dev/mapper/vgubuntu-root ro nouveau.modeset=1 quiet splash
Aug 29 21:07:54 ZB kernel: Kernel command line:
BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro
nouveau.modeset=1 quiet splash
Aug 29 21:07:54 ZB kernel: nouveau: detected PR support, will not use DSM
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: enabling device ( ->
0003)
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: NVIDIA TU117 (167000a1)
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: bios: version 90.17.61.00.73
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: pmu: firmware unavailable
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: fb: 2048 MiB GDDR6
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: halted
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021
TIDX 1b1f
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2055
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2305
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 201c
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2303
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2051
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 269e
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2617
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 1822
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 1a97
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 26c8
Aug 29 21:07:54 ZB kernel:
[Kernel-packages] [Bug 2033441] Re: linux-firmware is outdated
This bug was fixed in the package linux-firmware -
20230323.gitbcdcfbcf-0ubuntu1.7
---
linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.7) lunar; urgency=medium
* linux-firmware is outdated (LP: #2033441)
- nvidia: update Tu10x and Tu11x signed firmware to support newer Turing HW
* S3 stress issue for amdgpu Navi 31/Navi33 (LP: #2024427)
- amdgpu: update GC 11.0.0 firmware for amd.5.5 release
- amdgpu: update GC 11.0.2 firmware for amd.5.5 release
-- Juerg Haefliger Fri, 22 Sep 2023
15:04:35 +0200
** Changed in: linux-firmware (Ubuntu Lunar)
Status: Fix Committed => Fix Released
--
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/2033441
Title:
linux-firmware is outdated
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Confirmed
Status in linux-firmware source package in Lunar:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Released
Bug description:
[Impact]
This is optimus laptop with Intel 11th Gen and Nvidia.
In recent kernels like 6.2.0 it gives a blank screen after booting and if
nouveau.modset=1 is set, it completely freeze the system.
I remember it was working fine in 5.x kernels.
Now I have to blacklist nouveau and use Nvidia driver instead.
Using this commit of linux-firmware solved the issue:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/nvidia?id=2e92a49f90f73c8edc44b25c6e669d5e70893c90
[Fix]
Upstream commit 2e92a49f90f9 ("nvidia: update Tu10x and Tu11x signed
firmware to support newer Turing HW")
[Test Case]
Boot a machine with relevant GPU.
[Where Problems Could Occur]
Updated Nvidia FW so limited to machines with relevant GPUs.
[Additional Information]
# journalctl -b -2 | grep nouveau
Aug 29 21:07:54 ZB kernel: Command line: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic
root=/dev/mapper/vgubuntu-root ro nouveau.modeset=1 quiet splash
Aug 29 21:07:54 ZB kernel: Kernel command line:
BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro
nouveau.modeset=1 quiet splash
Aug 29 21:07:54 ZB kernel: nouveau: detected PR support, will not use DSM
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: enabling device ( ->
0003)
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: NVIDIA TU117 (167000a1)
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: bios: version 90.17.61.00.73
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: pmu: firmware unavailable
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: fb: 2048 MiB GDDR6
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: halted
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021
TIDX 1b1f
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2055
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2305
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 201c
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2303
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2051
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 269e
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2617
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 1822
Aug 29 21:07:54 ZB
[Kernel-packages] [Bug 2033441] Re: linux-firmware is outdated
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => Confirmed
--
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/2033441
Title:
linux-firmware is outdated
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Confirmed
Status in linux-firmware source package in Lunar:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Released
Bug description:
[Impact]
This is optimus laptop with Intel 11th Gen and Nvidia.
In recent kernels like 6.2.0 it gives a blank screen after booting and if
nouveau.modset=1 is set, it completely freeze the system.
I remember it was working fine in 5.x kernels.
Now I have to blacklist nouveau and use Nvidia driver instead.
Using this commit of linux-firmware solved the issue:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/nvidia?id=2e92a49f90f73c8edc44b25c6e669d5e70893c90
[Fix]
Upstream commit 2e92a49f90f9 ("nvidia: update Tu10x and Tu11x signed
firmware to support newer Turing HW")
[Test Case]
Boot a machine with relevant GPU.
[Where Problems Could Occur]
Updated Nvidia FW so limited to machines with relevant GPUs.
[Additional Information]
# journalctl -b -2 | grep nouveau
Aug 29 21:07:54 ZB kernel: Command line: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic
root=/dev/mapper/vgubuntu-root ro nouveau.modeset=1 quiet splash
Aug 29 21:07:54 ZB kernel: Kernel command line:
BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro
nouveau.modeset=1 quiet splash
Aug 29 21:07:54 ZB kernel: nouveau: detected PR support, will not use DSM
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: enabling device ( ->
0003)
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: NVIDIA TU117 (167000a1)
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: bios: version 90.17.61.00.73
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: pmu: firmware unavailable
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: fb: 2048 MiB GDDR6
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: halted
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021
TIDX 1b1f
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2055
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2305
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 201c
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2303
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2051
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 269e
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2617
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 1822
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 1a97
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 26c8
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2318
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: VRAM: 2048 MiB
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: GART: 536870912 MiB
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: BIT table 'A' not found
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0:
[Kernel-packages] [Bug 2038768] Re: arm64: linux: stress-ng filename stressor crashes kernel
And can reproduce on real H/W on a 24 core "SC2A11" is a multi-core chip with 24 cores of ARM® Cortex-A53. with Linux 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux [ 201.075720] EXT4-fs (loop13): mounted filesystem 52e32882-8b3a-47ce-8bf6-ce095960b1e7 r/w with ordered data mode. Quota mode: none. [ 516.665218] [ cut here ] [ 516.665249] kernel BUG at fs/dcache.c:2050! [ 516.665279] Internal error: Oops - BUG: f2000800 [#1] SMP [ 516.665301] Modules linked in: tls vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc overlay cfg80211 binfmt_misc zfs(PO) nls_iso8859_1 spl(O) snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundcore uio_pdrv_genirq uio dm_multipath efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear nouveau crct10dif_ce drm_ttm_helper polyval_ce polyval_generic ttm ghash_ce i2c_algo_bit drm_display_helper cec rc_core sm4 drm_kms_helper sha2_ce sha256_arm64 xhci_pci drm r8169 sha1_ce ahci xhci_pci_renesas realtek sdhci_f_sdh30 sdhci_pltfm sdhci gpio_keys [ 516.665743] netsec gpio_mb86s7x i2c_synquacer aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 516.665900] CPU: 2 PID: 17292 Comm: stress-ng-filen Tainted: P O 6.5.0-7-generic #7-Ubuntu [ 516.665927] Hardware name: Socionext SynQuacer E-series DeveloperBox, BIOS build #85 Nov 6 2020 [ 516.665948] pstate: 4045 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 516.665974] pc : d_instantiate_new+0xa8/0xc8 [ 516.666006] lr : ext4_add_nondir+0x10c/0x160 [ 516.666029] sp : 8000857838d0 [ 516.666043] x29: 8000857838d0 x28: x27: 8000816ea980 [ 516.666076] x26: 0008119915e0 x25: 8180 x24: 000856c61ce8 [ 516.666108] x23: 0008119915c0 x22: 800085783950 x21: 00080359e1c0 [ 516.666140] x20: 0008561b1ce8 x19: x18: 800085a6d068 [ 516.666172] x17: x16: x15: 878b4681cc52c99d [ 516.666204] x14: d59de2a9feb89dca x13: 85e2878b4681cc52 x12: c99dd59de2a9feb8 [ 516.666236] x11: e3b9eedbdf1c7d27 x10: 732db84fa4ef339b x9 : 8000807690bc [ 516.666268] x8 : x7 : x6 : [ 516.666299] x5 : x4 : x3 : [ 516.666330] x2 : 8000836b52e8 x1 : 0008561b1ce8 x0 : 0008119915c0 [ 516.666362] Call trace: [ 516.666377] d_instantiate_new+0xa8/0xc8 [ 516.666401] ext4_create+0x120/0x238 [ 516.666422] lookup_open.isra.0+0x480/0x4d0 [ 516.666447] open_last_lookups+0x160/0x3b0 [ 516.666466] path_openat+0xa0/0x2a0 [ 516.666484] do_filp_open+0xa8/0x180 [ 516.666502] do_sys_openat2+0xe8/0x128 [ 516.666524] __arm64_sys_openat+0x70/0xe0 [ 516.666545] invoke_syscall+0x7c/0x128 [ 516.666566] el0_svc_common.constprop.0+0x5c/0x168 [ 516.666586] do_el0_svc+0x38/0x68 [ 516.04] el0_svc+0x30/0xe0 [ 516.26] el0t_64_sync_handler+0x148/0x158 [ 516.47] el0t_64_sync+0x1b0/0x1b8 [ 516.74] Code: d282 d2800010 d2800011 d65f03c0 (d421) [ 516.96] ---[ end trace ]--- -- 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/2038768 Title: arm64: linux: stress-ng filename stressor crashes kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Mantic: Incomplete Bug description: Running latest Ubuntu mantic (ext4 file system) with kernel: Linux mantic-arm64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux How to reproduce: Fire up a 24 instance ARM64 QEMU instance with Ubuntu Mantic Server. Install latest stress-ng from git repo: sudo apt-get update sudo apt-get build-dep stress-ng git clone git://github.com/ColinIanKing/stress-ng cd stress-ng make clean make -j 24 make verify-test-all When we reach the filename stressor the kernel crashes as follows: [ 902.594715] kernel BUG at fs/dcache.c:2050! [ 902.598205] Internal error: Oops - BUG: f2000800 [#1] SMP [ 902.603127] Modules linked in: dccp_ipv4 dccp atm vfio_iommu_type1 vfio iommu fd cmac algif_rng twofish_generic twofish_common serpent_generic fcrypt cast6_ge neric cast5_generic cast_common camellia_generic blowfish_generic blowfish_commo n aes_arm64 algif_skcipher
[Kernel-packages] [Bug 2038768] Re: arm64: linux: stress-ng filename stressor crashes kernel
Reproduced this with mainline arm64 kernel https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.5.5/arm64/linux-image- unsigned-6.5.5-060505-generic_6.5.5-060505.202309230703_arm64.deb [ 219.219042] Internal error: Oops - BUG: f2000800 [#1] SMP [ 219.262013] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 dm_multipat h drm efi_pstore dmi_sysfs qemu_fw_cfg ip_tables x_tables autofs4 btrfs blake2b_ generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_t x xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_ce poly val_ce polyval_generic ghash_ce sm4 sha2_ce sha256_arm64 virtio_net sha1_ce arm_ smccc_trng virtio_rng net_failover xhci_pci failover xhci_pci_renesas aes_neon_b s aes_neon_blk aes_ce_blk aes_ce_cipher [ 219.322456] CPU: 13 PID: 1182 Comm: stress-ng-filen Not tainted 6.5.5-060505- generic #202309230703 [ 219.332405] Hardware name: QEMU KVM Virtual Machine, BIOS 2023.05-2 09/23/202 3 [ 219.340433] pstate: 4045 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 219.348163] pc : d_instantiate_new+0xa8/0xc8 [ 219.352942] lr : ext4_add_nondir+0x10c/0x160 [ 219.357822] sp : 8000826ab9d0 [ 219.361517] x29: 8000826ab9d0 x28: x27: a9b65720a940 [ 219.369535] x26: 1ea33582d2e0 x25: 8180 x24: 1ea3c2bb3d48 [ 219.377494] x23: 1ea33582d2c0 x22: 8000826abab0 x21: 1ea3c3344930 [ 219.385428] x20: 1ea324bda188 x19: x18: 800080b4d068 [ 219.393336] x17: x16: x15: 9afaefe7af176647 [ 219.401279] x14: f302afa80109b8f3 x13: a3469afaefe7af17 x12: 6647f302afa80109 [ 219.409258] x11: b4e7e46bc44fb52e x10: 4e81094291a860ce x9 : a9b6562b1b74 [ 219.417639] x8 : x7 : x6 : [ 219.426015] x5 : x4 : x3 : [ 219.434462] x2 : a9b6591b27e8 x1 : 1ea324bda188 x0 : 1ea33582d2c0 [ 219.442708] Call trace: [ 219.445901] d_instantiate_new+0xa8/0xc8 [ 219.450786] ext4_create+0x120/0x238 [ 219.454800] lookup_open.isra.0+0x478/0x4c8 [ 219.459476] open_last_lookups+0x160/0x3b0 [ 219.464060] path_openat+0x9c/0x290 [ 219.468062] do_filp_open+0xac/0x188 [ 219.472175] do_sys_openat2+0xe4/0x120 [ 219.476412] __arm64_sys_openat+0x6c/0xd8 [ 219.481300] invoke_syscall+0x7c/0x128 [ 219.485876] el0_svc_common.constprop.0+0x5c/0x168 [ 219.491561] do_el0_svc+0x38/0x68 [ 219.495523] el0_svc+0x30/0xe0 [ 219.499161] el0t_64_sync_handler+0x148/0x158 [ 219.504139] el0t_64_sync+0x1b0/0x1b8 [ 219.508320] Code: d282 d2800010 d2800011 d65f03c0 (d421) [ 219.515430] ---[ end trace ]--- -- 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/2038768 Title: arm64: linux: stress-ng filename stressor crashes kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Mantic: Incomplete Bug description: Running latest Ubuntu mantic (ext4 file system) with kernel: Linux mantic-arm64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux How to reproduce: Fire up a 24 instance ARM64 QEMU instance with Ubuntu Mantic Server. Install latest stress-ng from git repo: sudo apt-get update sudo apt-get build-dep stress-ng git clone git://github.com/ColinIanKing/stress-ng cd stress-ng make clean make -j 24 make verify-test-all When we reach the filename stressor the kernel crashes as follows: [ 902.594715] kernel BUG at fs/dcache.c:2050! [ 902.598205] Internal error: Oops - BUG: f2000800 [#1] SMP [ 902.603127] Modules linked in: dccp_ipv4 dccp atm vfio_iommu_type1 vfio iommu fd cmac algif_rng twofish_generic twofish_common serpent_generic fcrypt cast6_ge neric cast5_generic cast_common camellia_generic blowfish_generic blowfish_commo n aes_arm64 algif_skcipher algif_hash aria_generic sm4_generic sm4_neon ccm aes_ ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg cfg80211 binfmt_mis c nls_iso8859_1 dm_multipath drm efi_pstore dmi_sysfs qemu_fw_cfg ip_tables x_ta bles autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipa th linear crct10dif_ce polyval_ce polyval_generic ghash_ce sm4 sha2_ce sha256_ar m64 sha1_ce arm_smccc_trng xhci_pci virtio_rng xhci_pci_renesas aes_neon_bs aes_ neon_blk aes_ce_blk aes_ce_cipher [ 902.689941] CPU: 1 PID: 91317 Comm: stress-ng-filen Not tainted 6.5.0-7-gener ic #7-Ubuntu [ 902.699281] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 902.706902] pstate: 4045 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 902.715488] pc : d_instantiate_new+0xa8/0xc8 [ 902.720889] lr :
[Kernel-packages] [Bug 2017877] Re: Intel Wireless 7260 - bluetooth drops from USB bus almost immediately after connecting a device on the lastest firmware
Can you check if this kernel commandline makes a difference with the new/broken firmware? enable_autosuspend=0 ** Changed in: linux-firmware (Ubuntu) Status: Confirmed => 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/2017877 Title: Intel Wireless 7260 - bluetooth drops from USB bus almost immediately after connecting a device on the lastest firmware Status in linux-firmware package in Ubuntu: Incomplete Bug description: The bluetooth in my Intel Wireless 7260 on my Thinkpad W541 resets almost immediately after a device connects. This is seen in dmesg as the device disconnecting and reconnecting to the USB bus with no other error messages, like this: [603851.305788] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603851.305827] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [603851.443776] Bluetooth: hci0: unexpected event for opcode 0xfc2f [603851.460922] Bluetooth: hci0: Intel BT fw patch 0x2a completed & activated [603871.948430] usb 3-11: USB disconnect, device number 36 [603872.273696] usb 3-11: new full-speed USB device number 37 using xhci_hcd [603872.422912] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [603872.422916] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [603872.437854] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603872.437873] Bluetooth: hci0: Intel device is already patched. patch num: 2a [603894.932755] input: JBL TUNE700BT (AVRCP) as /devices/virtual/input/input113 [603898.742664] usb 3-11: USB disconnect, device number 37 [603899.057916] usb 3-11: new full-speed USB device number 38 using xhci_hcd [603899.211235] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [603899.211241] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [603899.226972] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603899.226988] Bluetooth: hci0: Intel device is already patched. patch num: 2a [603909.785396] input: JBL TUNE700BT (AVRCP) as /devices/virtual/input/input114 [603914.565733] usb 3-11: USB disconnect, device number 38 [603916.905954] usb 3-11: new full-speed USB device number 39 using xhci_hcd [603917.055128] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [603917.055147] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [603917.071869] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603917.071877] Bluetooth: hci0: Intel device is already patched. patch num: 2a This has been a problem ever since I got this laptop, but recently I managed to fix it by downgrading the ibt firmware. I downgraded the /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq file to this version https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/intel/ibt- hw-37.7.10-fw-1.80.1.2d.d.bseq?id=fb328183532ffc7a1a54e84fb53467e275a95b79 and after that all problems stopped. System info: $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy linux-firmware linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.12 Candidate: 20220329.git681281e4-0ubuntu3.12 Version table: *** 20220329.git681281e4-0ubuntu3.12 500 500 http://pl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://pl.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 20220329.git681281e4-0ubuntu1 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages $ lspci - (see attachment) $ lsusb -v (see attachment) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: krzys_h1511 F pulseaudio /dev/snd/controlC2: krzys_h1511 F pulseaudio /dev/snd/controlC0: krzys_h1511 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-28 (3346 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20EGS2G300 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 [modified: lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq] PackageArchitecture: all
[Kernel-packages] [Bug 2017877] Re: Intel Wireless 7260 - bluetooth drops from USB bus almost immediately after connecting a device on the lastest firmware
Relevant log entries: [ 14.405083] Bluetooth: Core ver 2.22 [ 14.405115] NET: Registered PF_BLUETOOTH protocol family [ 14.405116] Bluetooth: HCI device and connection manager initialized [ 14.405120] Bluetooth: HCI socket layer initialized [ 14.405121] Bluetooth: L2CAP socket layer initialized [ 14.405124] Bluetooth: SCO socket layer initialized [ 14.442194] usbcore: registered new interface driver btusb [ 14.454369] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [ 14.456943] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 14.531540] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 14.531543] Bluetooth: BNEP filters: protocol multicast [ 14.531546] Bluetooth: BNEP socket layer initialized [ 14.603335] Bluetooth: hci0: unexpected event for opcode 0xfc2f [ 14.619356] Bluetooth: hci0: Intel BT fw patch 0x2a completed & activated [ 14.674486] NET: Registered PF_ALG protocol family [ 14.699195] Bluetooth: RFCOMM TTY layer initialized [ 14.699203] Bluetooth: RFCOMM socket layer initialized [ 14.699208] Bluetooth: RFCOMM ver 1.11 [ 80.399089] Bluetooth: hci0: SCO packet for unknown connection handle 0 [ 80.399099] Bluetooth: hci0: SCO packet for unknown connection handle 0 [ 80.399101] Bluetooth: hci0: SCO packet for unknown connection handle 0 [ 80.399103] Bluetooth: hci0: SCO packet for unknown connection handle 0 [ 80.399105] Bluetooth: hci0: SCO packet for unknown connection handle 0 [ 80.399106] Bluetooth: hci0: SCO packet for unknown connection handle 0 [ 80.399108] Bluetooth: hci0: SCO packet for unknown connection handle 0 [ 80.399110] Bluetooth: hci0: SCO packet for unknown connection handle 0 [ 99.657119] usb 3-11: USB disconnect, device number 4 [ 99.701466] Bluetooth: hci0: setting interface failed (19) [ 100.029214] usb 3-11: new full-speed USB device number 7 using xhci_hcd [ 100.182436] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [ 100.182443] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 100.198003] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [ 100.198009] Bluetooth: hci0: Intel device is already patched. patch num: 2a [ 172.057057] usb 3-11: USB disconnect, device number 7 [ 172.407869] usb 3-11: new full-speed USB device number 8 using xhci_hcd [ 172.557024] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [ 172.557029] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 172.572730] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [ 172.572737] Bluetooth: hci0: Intel device is already patched. patch num: 2a [ 189.598594] Bluetooth: hci0: Ignoring error of Inquiry Cancel command [ 196.210563] usb 3-11: USB disconnect, device number 8 [ 196.210829] Bluetooth: hci0: failed to restart LE scan: status 31 [ 196.523336] usb 3-11: new full-speed USB device number 9 using xhci_hcd [ 196.676506] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [ 196.676511] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 196.691589] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [ 196.691597] Bluetooth: hci0: Intel device is already patched. patch num: 2a [ 225.03] usb 3-11: USB disconnect, device number 9 [ 225.666971] Bluetooth: hci0: failed to restart LE scan: status 31 [ 226.010936] usb 3-11: new full-speed USB device number 10 using xhci_hcd [ 226.172153] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [ 226.172158] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 226.187499] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [ 226.187512] Bluetooth: hci0: Intel device is already patched. patch num: 2a [ 242.556427] usb 3-11: USB disconnect, device number 10 [ 242.556554] Bluetooth: hci0: sending frame failed (-19) [ 242.556700] Bluetooth: hci0: HCI reset during shutdown failed [ 277.334467] usb 3-11: new full-speed USB device number 11 using xhci_hcd [ 277.483652] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [ 277.483657] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 277.498237] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [ 277.502124] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 277.667254] Bluetooth: hci0: unexpected event for opcode 0xfc2f [ 277.683274] Bluetooth: hci0: Intel BT fw patch 0x27 completed & activated ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Confirmed -- 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/2017877 Title: Intel Wireless 7260 - bluetooth drops from USB bus almost immediately
[Kernel-packages] [Bug 2038436] Re: System doesnt recognize second monitor
Thanks. That confirms it's the kernel not detecting the monitor. ** Package changed: ubuntu => linux-hwe-6.2 (Ubuntu) ** Changed in: linux-hwe-6.2 (Ubuntu) Status: Incomplete => New ** Summary changed: - System doesnt recognize second monitor + [i915] System doesn't recognize second monitor -- 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/2038436 Title: [i915] System doesn't recognize second monitor Status in linux-hwe-6.2 package in Ubuntu: New Bug description: I am using an old monitor which using a DVI connectors but I used a DVI to HDMI adapter which works fine on Windows operating system... My monitor is HP W2072a... I hope with the information provided helps... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 21:17:37 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Device [1b50:1018] InstallationDate: Installed on 2023-09-30 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: ILLEGEAR SDN BHD ATOMIC 16 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=e60cc65c-b597-415b-b294-3cb6a76ecbd0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2022 dmi.bios.release: 0.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q3AIL.02 dmi.board.asset.tag: Default string be filled by O.E.M dmi.board.name: ATOMIC dmi.board.vendor: ILLEGEAR SDN BHD dmi.board.version: Default string be filled by O.E.M dmi.chassis.asset.tag: Default string be filled by O.E.M dmi.chassis.type: 9 dmi.chassis.vendor: Default string be filled by O.E.M dmi.chassis.version: Default string be filled by O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ3AIL.02:bd07/26/2022:br0.2:svnILLEGEARSDNBHD:pnATOMIC16:pvrDefaultstringbefilledbyO.E.M:rvnILLEGEARSDNBHD:rnATOMIC:rvrDefaultstringbefilledbyO.E.M:cvnDefaultstringbefilledbyO.E.M:ct9:cvrDefaultstringbefilledbyO.E.M:skuATOMIC16-ADL1: dmi.product.family: ATOMIC dmi.product.name: ATOMIC 16 dmi.product.sku: ATOMIC16-ADL1 dmi.product.version: Default string be filled by O.E.M dmi.sys.vendor: ILLEGEAR SDN BHD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2038436/+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 2038768] Re: arm64: linux: stress-ng filename stressor crashes kernel
Reproduced this with mainline arm64 kernel https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.5/arm64/linux-image- unsigned-6.5.0-060500-generic_6.5.0-060500.202308271831_arm64.deb [ 184.853731] pstate: 4045 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 184.862627] pc : d_instantiate_new+0xa8/0xc8 [ 184.867973] lr : ext4_add_nondir+0xf0/0x148 [ 184.872959] sp : 8000828ab950 [ 184.877059] x29: 8000828ab950 x28: x27: d975b8b9a6c0 [ 184.885032] x26: 7b0094e32c20 x25: 8180 x24: 7b01432e9848 [ 184.893573] x23: 8000828aba30 x22: 7b0094e32c00 x21: 7b0172d574d0 [ 184.902071] x20: 7b0089fbc688 x19: x18: 800082295068 [ 184.910550] x17: x16: x15: 5e9ca062546ae354 [ 184.919056] x14: 998c9ec3ecc3a882 x13: 24d23ffaf8b470b6 x12: 022485883b51bee2 [ 184.927692] x11: 5c7ac5c18df459ab x10: 6e24d23ffaf8b470 x9 : d975b7c3d730 [ 184.936212] x8 : x7 : x6 : [ 184.944811] x5 : x4 : x3 : [ 184.953651] x2 : d975bab42cf0 x1 : 7b0089fbc688 x0 : 7b0094e32c00 [ 184.962508] Call trace: [ 184.965316] d_instantiate_new+0xa8/0xc8 [ 184.969803] ext4_create+0x120/0x238 [ 184.973910] lookup_open.isra.0+0x478/0x4c8 [ 184.978689] open_last_lookups+0x160/0x3b0 [ 184.983374] path_openat+0x9c/0x290 [ 184.987372] do_filp_open+0xac/0x188 [ 184.991444] do_sys_openat2+0xe4/0x120 [ 184.995701] __arm64_sys_openat+0x6c/0xd8 [ 185.000271] invoke_syscall+0x7c/0x128 [ 185.004520] el0_svc_common.constprop.0+0x5c/0x168 [ 185.009977] do_el0_svc+0x38/0x68 [ 185.013775] el0_svc+0x30/0xe0 [ 185.017265] el0t_64_sync_handler+0x148/0x158 [ 185.022183] el0t_64_sync+0x1b0/0x1b8 [ 185.026332] Code: d282 d2800010 d2800011 d65f03c0 (d421) [ 185.033606] ---[ end trace ]--- Took a while to trigger. -- 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/2038768 Title: arm64: linux: stress-ng filename stressor crashes kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Mantic: Incomplete Bug description: Running latest Ubuntu mantic (ext4 file system) with kernel: Linux mantic-arm64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux How to reproduce: Fire up a 24 instance ARM64 QEMU instance with Ubuntu Mantic Server. Install latest stress-ng from git repo: sudo apt-get update sudo apt-get build-dep stress-ng git clone git://github.com/ColinIanKing/stress-ng cd stress-ng make clean make -j 24 make verify-test-all When we reach the filename stressor the kernel crashes as follows: [ 902.594715] kernel BUG at fs/dcache.c:2050! [ 902.598205] Internal error: Oops - BUG: f2000800 [#1] SMP [ 902.603127] Modules linked in: dccp_ipv4 dccp atm vfio_iommu_type1 vfio iommu fd cmac algif_rng twofish_generic twofish_common serpent_generic fcrypt cast6_ge neric cast5_generic cast_common camellia_generic blowfish_generic blowfish_commo n aes_arm64 algif_skcipher algif_hash aria_generic sm4_generic sm4_neon ccm aes_ ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg cfg80211 binfmt_mis c nls_iso8859_1 dm_multipath drm efi_pstore dmi_sysfs qemu_fw_cfg ip_tables x_ta bles autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipa th linear crct10dif_ce polyval_ce polyval_generic ghash_ce sm4 sha2_ce sha256_ar m64 sha1_ce arm_smccc_trng xhci_pci virtio_rng xhci_pci_renesas aes_neon_bs aes_ neon_blk aes_ce_blk aes_ce_cipher [ 902.689941] CPU: 1 PID: 91317 Comm: stress-ng-filen Not tainted 6.5.0-7-gener ic #7-Ubuntu [ 902.699281] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 902.706902] pstate: 4045 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 902.715488] pc : d_instantiate_new+0xa8/0xc8 [ 902.720889] lr : ext4_add_nondir+0x10c/0x160 [ 902.725702] sp : 80008b6d3930 [ 902.729390] x29: 80008b6d3930 x28: x27: bd164e51a980 [ 902.738705] x26: 6789f3b68f20 x25: 8180 x24: 678a541f7968 [ 902.747003] x23: 6789f3b68f00 x22: 80008b6d39b0 x21: 678a6a25bcb0 [ 902.755776] x20: 678a36f8f028 x19: x18: 80008af45068 [ 902.764647] x17: x16: x15: ecececececececec [ 902.773135] x14: ecececececececec x13: ecececececececec x12: ecececececececec [ 902.781386] x11: ecececececececec x10: ecececececececec x9 : bd164d5990bc [ 902.789346] x8 : x7 : x6 : [ 902.798564] x5 :
[Kernel-packages] [Bug 2038436] [NEW] System doesnt recognize second monitor
You have been subscribed to a public bug: I am using an old monitor which using a DVI connectors but I used a DVI to HDMI adapter which works fine on Windows operating system... My monitor is HP W2072a... I hope with the information provided helps... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 21:17:37 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Device [1b50:1018] InstallationDate: Installed on 2023-09-30 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: ILLEGEAR SDN BHD ATOMIC 16 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=e60cc65c-b597-415b-b294-3cb6a76ecbd0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2022 dmi.bios.release: 0.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q3AIL.02 dmi.board.asset.tag: Default string be filled by O.E.M dmi.board.name: ATOMIC dmi.board.vendor: ILLEGEAR SDN BHD dmi.board.version: Default string be filled by O.E.M dmi.chassis.asset.tag: Default string be filled by O.E.M dmi.chassis.type: 9 dmi.chassis.vendor: Default string be filled by O.E.M dmi.chassis.version: Default string be filled by O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ3AIL.02:bd07/26/2022:br0.2:svnILLEGEARSDNBHD:pnATOMIC16:pvrDefaultstringbefilledbyO.E.M:rvnILLEGEARSDNBHD:rnATOMIC:rvrDefaultstringbefilledbyO.E.M:cvnDefaultstringbefilledbyO.E.M:ct9:cvrDefaultstringbefilledbyO.E.M:skuATOMIC16-ADL1: dmi.product.family: ATOMIC dmi.product.name: ATOMIC 16 dmi.product.sku: ATOMIC16-ADL1 dmi.product.version: Default string be filled by O.E.M dmi.sys.vendor: ILLEGEAR SDN BHD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy multimonitor ubuntu wayland-session -- System doesnt recognize second monitor https://bugs.launchpad.net/bugs/2038436 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. -- 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 2038768] Re: arm64: linux: stress-ng filename stressor crashes kernel
Can't reproduce this with mainline arm64 kernel https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.5.6/arm64/linux-image- unsigned-6.5.6-060506-generic_6.5.6-060506.202310061235_arm64.deb -- 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/2038768 Title: arm64: linux: stress-ng filename stressor crashes kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Mantic: Incomplete Bug description: Running latest Ubuntu mantic (ext4 file system) with kernel: Linux mantic-arm64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux How to reproduce: Fire up a 24 instance ARM64 QEMU instance with Ubuntu Mantic Server. Install latest stress-ng from git repo: sudo apt-get update sudo apt-get build-dep stress-ng git clone git://github.com/ColinIanKing/stress-ng cd stress-ng make clean make -j 24 make verify-test-all When we reach the filename stressor the kernel crashes as follows: [ 902.594715] kernel BUG at fs/dcache.c:2050! [ 902.598205] Internal error: Oops - BUG: f2000800 [#1] SMP [ 902.603127] Modules linked in: dccp_ipv4 dccp atm vfio_iommu_type1 vfio iommu fd cmac algif_rng twofish_generic twofish_common serpent_generic fcrypt cast6_ge neric cast5_generic cast_common camellia_generic blowfish_generic blowfish_commo n aes_arm64 algif_skcipher algif_hash aria_generic sm4_generic sm4_neon ccm aes_ ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg cfg80211 binfmt_mis c nls_iso8859_1 dm_multipath drm efi_pstore dmi_sysfs qemu_fw_cfg ip_tables x_ta bles autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipa th linear crct10dif_ce polyval_ce polyval_generic ghash_ce sm4 sha2_ce sha256_ar m64 sha1_ce arm_smccc_trng xhci_pci virtio_rng xhci_pci_renesas aes_neon_bs aes_ neon_blk aes_ce_blk aes_ce_cipher [ 902.689941] CPU: 1 PID: 91317 Comm: stress-ng-filen Not tainted 6.5.0-7-gener ic #7-Ubuntu [ 902.699281] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 902.706902] pstate: 4045 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 902.715488] pc : d_instantiate_new+0xa8/0xc8 [ 902.720889] lr : ext4_add_nondir+0x10c/0x160 [ 902.725702] sp : 80008b6d3930 [ 902.729390] x29: 80008b6d3930 x28: x27: bd164e51a980 [ 902.738705] x26: 6789f3b68f20 x25: 8180 x24: 678a541f7968 [ 902.747003] x23: 6789f3b68f00 x22: 80008b6d39b0 x21: 678a6a25bcb0 [ 902.755776] x20: 678a36f8f028 x19: x18: 80008af45068 [ 902.764647] x17: x16: x15: ecececececececec [ 902.773135] x14: ecececececececec x13: ecececececececec x12: ecececececececec [ 902.781386] x11: ecececececececec x10: ecececececececec x9 : bd164d5990bc [ 902.789346] x8 : x7 : x6 : [ 902.798564] x5 : x4 : x3 : [ 902.806851] x2 : bd16504e4ce0 x1 : 678a36f8f028 x0 : 6789f3b68f00 [ 902.815544] Call trace: [ 902.818870] d_instantiate_new+0xa8/0xc8 [ 902.823523] ext4_create+0x120/0x238 [ 902.827716] lookup_open.isra.0+0x480/0x4d0 [ 902.832480] open_last_lookups+0x160/0x3b0 [ 902.837060] path_openat+0xa0/0x2a0 [ 902.840975] do_filp_open+0xa8/0x180 [ 902.845582] do_sys_openat2+0xe8/0x128 [ 902.850426] __arm64_sys_openat+0x70/0xe0 [ 902.854952] invoke_syscall+0x7c/0x128 [ 902.859155] el0_svc_common.constprop.0+0x5c/0x168 [ 902.864979] do_el0_svc+0x38/0x68 [ 902.869364] el0_svc+0x30/0xe0 [ 902.873401] el0t_64_sync_handler+0x148/0x158 [ 902.878336] el0t_64_sync+0x1b0/0x1b8 [ 902.882513] Code: d282 d2800010 d2800011 d65f03c0 (d421) [ 902.890632] ---[ end trace ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Proposed a different fix: https://salsa.debian.org/gnome-team/mutter/-/merge_requests/111 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038546] Re: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64
** Description changed: + [Impact] + /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the StarFive VisionFive board which uses the starfive kernel flavor. The file was available in Jammy and only recently removed from Mantic. File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding it cyfmac43430-sdio.clm_blob which file WHENCE links to brcmfmac43430-sdio.bin. So this file needs to change. + + [Fix] + + Include cypress/cyfmac firmware files in firmware packages. + + [Test Case] + + Check that wifi is functional. + + [Where Problems Could Occur] + + Potential wifi problems on platforms that are using the brcmfmac driver. ** Also affects: linux-firmware (Ubuntu Mantic) Importance: High Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2038546 Title: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Mantic: Confirmed Bug description: [Impact] /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the StarFive VisionFive board which uses the starfive kernel flavor. The file was available in Jammy and only recently removed from Mantic. File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding it cyfmac43430-sdio.clm_blob which file WHENCE links to brcmfmac43430-sdio.bin. So this file needs to change. [Fix] Include cypress/cyfmac firmware files in firmware packages. [Test Case] Check that wifi is functional. [Where Problems Could Occur] Potential wifi problems on platforms that are using the brcmfmac driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64
** Tags added: kern-8207 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2038582 Title: Turning COMPAT_32BIT_TIME off on arm64 Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-ibm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Bug description: This will prevent existing armhf binaries to operate correctly, if they are still using 32bit time. 24.04 LTS is likely to be used for 10 years. And if allowed to overrun and remain active in the field in 2038 can lead to catastrophic failure in the field due to these syscalls enabled and used. I would like to request if we can turn off COMPAT_32BIT_TIME on every architecture, thus this will be arch by arch bug report, and arch by arch decision. This needs to be a per-arch decision, potentially taking into consideration bi-arch userspace support. config COMPAT_32BIT_TIME bool "Provide system calls for 32-bit time_t" default !64BIT || COMPAT help This enables 32 bit time_t support in addition to 64 bit time_t support. This is relevant on all 32-bit architectures, and 64-bit architectures as part of compat syscall handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038586] Re: Turning COMPAT_32BIT_TIME off on armhf
** Tags added: kern-8208 -- 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/2038586 Title: Turning COMPAT_32BIT_TIME off on armhf Status in linux package in Ubuntu: Incomplete Status in linux-raspi package in Ubuntu: New Bug description: This will prevent existing armhf binaries to operate correctly, if they are still using 32bit time. 24.04 LTS is likely to be used for 10 years. And if allowed to overrun and remain active in the field in 2038 can lead to catastrophic failure in the field due to these syscalls enabled and used. Also note small inodes cannot be used by ext4. I would like to request if we can turn off COMPAT_32BIT_TIME on every architecture, thus this will be arch by arch bug report, and arch by arch decision. This needs to be a per-arch decision, potentially taking into consideration bi-arch userspace support. config COMPAT_32BIT_TIME bool "Provide system calls for 32-bit time_t" default !64BIT || COMPAT help This enables 32 bit time_t support in addition to 64 bit time_t support. This is relevant on all 32-bit architectures, and 64-bit architectures as part of compat syscall handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
** Description changed: + [ Impact ] + + gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, + sometimes when the screen locks, sometimes when launching particular + apps. + [ Workaround ] Add this to /etc/environment: - MUTTER_DEBUG_KMS_THREAD_TYPE=user + MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. - [ Original Description] + [ Test Plan ] + + Not all Ryzen systems (including one I just purchased) are able to + reproduce the bug. We have no choice but to leave final verification to + the community. Anyone affected should try locking their screen and + verify they are not instantly returned to the login screen. + + [ Where problems could occur ] + + Anywhere in frame scheduling and particularly for mouse cursor movement + since that's what the real-time thread exists to optimize. + + [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: ** Changed in: mutter (Ubuntu Mantic) Milestone: ubuntu-23.10 => mantic-updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
** Changed in: mutter (Ubuntu Mantic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
