[Kernel-packages] [Bug 2027614] Re: Xorg Black Screen when upgrading packages (after CUDA installation)
Thanks for the bug report. Next time the screen goes black and after rebooting, please run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535 (Ubuntu) ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: New => Incomplete -- 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/2027614 Title: Xorg Black Screen when upgrading packages (after CUDA installation) Status in nvidia-graphics-drivers-535 package in Ubuntu: Incomplete Bug description: Hi, I am trying to setup CUDA on my system. Followed the instructions and everything seemed to work. Tried nvcc command and it works. After a reboot, tried to update packages with `apt update && apt full- upgrade`. The following is the output before I proceeded: The following NEW packages will be installed: cpp-12 dctrl-tools dkms gcc-12 libasan8 libegl-mesa0:i386 libegl1:i386 libgbm1:i386 libgcc-12-dev libgles2:i386 libopengl0:i386 libtsan2 libwayland-client0:i386 libwayland-server0:i386 nvidia-dkms-535 The following packages have been kept back: alsa-ucm-conf gir1.2-adw-1 gjs libadwaita-1-0 libgjs0g libspeechd2 python3-speechd speech-dispatcher speech-dispatcher-audio-plugins speech-dispatcher-espeak-ng ubuntu-advantage-tools The following packages will be upgraded: libnvidia-cfg1-535 libnvidia-common-535 libnvidia-compute-535 libnvidia-compute-535:i386 libnvidia-decode-535 libnvidia-decode-535:i386 libnvidia-encode-535 libnvidia-encode-535:i386 libnvidia-extra-535 libnvidia-fbc1-535 libnvidia-fbc1-535:i386 libnvidia-gl-535 libnvidia-gl-535:i386 libxnvctrl0 nvidia-compute-utils-535 nvidia-driver-535 nvidia-kernel-common-535 nvidia-kernel-source-535 nvidia-utils-535 xserver-xorg-video-nvidia-535 After a while, screen went black and had to do a hard reboot. I tried this two times on a fresh Ubuntu 22.04 installation and same thing happened. I am ready to provide any further information if needed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.54.03 Tue Jun 6 22:20:39 UTC 2023 GCC version: 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 Jul 12 21:06:45 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d86] NVIDIA Corporation Device [10de:2782] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:88e5] InstallationDate: Installed on 2023-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro-Star International Co., Ltd. MS-7D86 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=a9c91108-ed9d-4352-a779-fc46a70f4215 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: MEG Z790 ACE (MS-7D86) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.30:bd03/23/2023:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D86:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGZ790ACE(MS-7D86):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D86 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
[Kernel-packages] [Bug 2012335] Re: Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores (256)
** Tags removed: verification-needed-jammy ** Tags added: verification-done-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/2012335 Title: Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores (256) Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: [Impact] There is a user reporting errors in setup with their Intel E810 NIC with error messages saying that the driver cannot allocate enough MSI-X vectors on their 256 cpu-count system. It seems the ICE ethernet driver has an all or nothing approach to allocating MSI-X vectors and could request more MSI-X vectors than it finds available, which could lead to the driver failing to initialize and start. [Fix] The patch that fixes this allocates as many MSI-X vectors as it can to continue functionality by reducing the number of requested MSI-X vectors if it does not have enough to do full allocation. [Backport] In Jammy we do not carry patches for switchdev support in the driver so do not allocate the switchdev MSI-X vector for it. Also in Jammy use the older way of checking RDMA support by testing the RDMA bit is set as opposed to the newer ice_is_rdma_ena that the patch uses. [Test Plan] Install and startup Ice driver with an Intel 800 series NIC and check that we do not have the failure: Not enough device MSI-X vectors, requested = 260, available = 253 and check that everything works as expected. The backported patch for Jammy has been tested by the original user who submited the bug report with their high cpu count system and confirmed no errors. [Where problems could occur] There could be problems with the logic of reducing the MSI-X vector usage leading to more errors in the driver, but otherwise minimal regression potential as the code is mostly refactoring initial MSI-X setup. -- System Configuration OS: Ubuntu 22.04 LTS Kernel: 5.15.0-25-generic CPUs: 256 NIC: Intel E810 NIC with 512 MSIx vectors each function Errors Not enough device MSI-X vectors, requested = 260, available = 253 Findings (1) the current ice kernel driver (ice_main.c) will pre-allocate all required number of msix (even it's not enough for big core CPUs) (2) the commit https://github.com/torvalds/linux/commit/ce4626131112e1d0066a890371e14d8091323f99 has improved this logic, and it seems merged into kernel version from v6.1 So for supporting the new CPUs with more than 252 vCPUs, will Ubuntu kernel backport above patch to the current kernel (v5.15) ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012335] Re: Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores (256)
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1001.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-nvidia-tegra-igx -- 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/2012335 Title: Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores (256) Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: [Impact] There is a user reporting errors in setup with their Intel E810 NIC with error messages saying that the driver cannot allocate enough MSI-X vectors on their 256 cpu-count system. It seems the ICE ethernet driver has an all or nothing approach to allocating MSI-X vectors and could request more MSI-X vectors than it finds available, which could lead to the driver failing to initialize and start. [Fix] The patch that fixes this allocates as many MSI-X vectors as it can to continue functionality by reducing the number of requested MSI-X vectors if it does not have enough to do full allocation. [Backport] In Jammy we do not carry patches for switchdev support in the driver so do not allocate the switchdev MSI-X vector for it. Also in Jammy use the older way of checking RDMA support by testing the RDMA bit is set as opposed to the newer ice_is_rdma_ena that the patch uses. [Test Plan] Install and startup Ice driver with an Intel 800 series NIC and check that we do not have the failure: Not enough device MSI-X vectors, requested = 260, available = 253 and check that everything works as expected. The backported patch for Jammy has been tested by the original user who submited the bug report with their high cpu count system and confirmed no errors. [Where problems could occur] There could be problems with the logic of reducing the MSI-X vector usage leading to more errors in the driver, but otherwise minimal regression potential as the code is mostly refactoring initial MSI-X setup. -- System Configuration OS: Ubuntu 22.04 LTS Kernel: 5.15.0-25-generic CPUs: 256 NIC: Intel E810 NIC with 512 MSIx vectors each function Errors Not enough device MSI-X vectors, requested = 260, available = 253 Findings (1) the current ice kernel driver (ice_main.c) will pre-allocate all required number of msix (even it's not enough for big core CPUs) (2) the commit https://github.com/torvalds/linux/commit/ce4626131112e1d0066a890371e14d8091323f99 has improved this logic, and it seems merged into kernel version from v6.1 So for supporting the new CPUs with more than 252 vCPUs, will Ubuntu kernel backport above patch to the current kernel (v5.15) ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015972] Re: Dell: Enable speaker mute hotkey LED indicator
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1001.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-nvidia-tegra-igx -- 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/2015972 Title: Dell: Enable speaker mute hotkey LED indicator Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in alsa-ucm-conf source package in Kinetic: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in alsa-ucm-conf source package in Lunar: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2015972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1001.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-nvidia-tegra-igx -- 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/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2007745] Re: [SRU][Jammy] CONFIG_PCI_MESON is not enabled
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1001.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-nvidia-tegra-igx -- 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/2007745 Title: [SRU][Jammy] CONFIG_PCI_MESON is not enabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU justification: [ Impact ] The PCI driver for the amlogic-based Meson platforms (CONFIG_PCI_MESON) is not enabled as a module in the kernel configuration: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/tree/debian.master/config/config.common.ubuntu?h=master#n7036 [ Test Plan ] Check if pci_meson.ko is compiled and present in the linux-modules package. [ Where problems could occur ] * Enabling the driver could enable undesired dependencies * Kernel module does not compile and breaks the build [ Other Info ] This driver is important for systems like the ODROID HC4, which uses a PCIE-SATA bridge to provide a storage interface. This system is fully supported by the kernel (including a device tree), except for the fact that this PCI driver is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008751] Re: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1001.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-nvidia-tegra-igx -- 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/2008751 Title: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: [Impact] Please pick up the latest hpwdt from the upstream 6.1 kernel for Jammy. This version enables hpwdt on RL300 aarch64. [Fix] ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING 891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems. [Test Plan] Boot system with the hpwdt enabled on an arm64 system [Where Problems Could Occur] Regression Risk is Low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt_1 Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008751_hpwdt_kinetic_1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008527] Re: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1001.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-nvidia-tegra-igx -- 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/2008527 Title: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: [Impact] A Dell system that has a profile setting of "Performance Per Watt (DAPC)" enabled in the BIOS and running Ubuntu-22.04 does not boot into OS as quickly as expected. How reproducible: Steps to Reproduce: 1. On the Dell system enable "Performance Per Watt (DAPC)" from BIOS. 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008527_dapc Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008527_dapc_kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016269] Re: conntrack mark is not advertised via netlink
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1001.1 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.
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-nvidia-tegra-igx
--
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/2016269
Title:
conntrack mark is not advertised via netlink
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Bug description:
SRU justification sent to ML:
[Impact]
There was a commit 95fcb42e5f20
("netfilter: ctnetlink: fix compilation warning after data race fixes in ct
mark")
that introduces a regression where the "mark" variable is no longer
dumped in netlink netfilter conntrack messages, which userspace tools use
to mark and track connections.
[Fix]
Introduce the upstream fix 9f7dd42f0db1
("netfilter: ctnetlink: revert to dumping mark regardless of event type")
that always dumps the 'mark' variable for conntrack entries.
This fix has also landed in 5.15 upstream stable.
[Test]
Run 'conntrack -E' and check the output of connection entries.
The 'mark' variable should now be present in connection entries after
the fix.
before fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
after fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1
[Where problems could occur]
The fixes are pretty straight forward so regression potential should be
minimal.
[Impact]
The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix
compilation warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter:
ctnetlink: revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backported in v5.15.103:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c
[Test Case]
Run 'conntrack -E' and check the output.
Before the problematic commit:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED]
mark=0 use=1
'mark=' is seen on connrtack event
after:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
=> 'mark=' is not seen.
[Regression Potential]
The patch is quite simple. It has been backported in the official 5.15
stable. The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016269/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019000] Re: Use new annotations model
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1001.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-nvidia-tegra-igx -- 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/2019000 Title: Use new annotations model Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Confirmed Bug description: [Impact] Starting with lunar we have introduced a new way to manage kernel configs, unifying the duplicated information defined in the annotations file + config chunks into an annotations-only model. [Test case] A kernel build can be considered a valid test case, in particular the specific command that is used to update the .config's for all the supported architectures and flavours: $ fakeroot debian/rules updateconfigs [Fix] Import the required changes in debian/ from lunar (with the required adjustments) to support the annotations-only model also in all the previous releases. [Regression potential] We may experience regressions during the updateconfigs step, especially with derivatives. Moreover, derivatives that want to transition to the new annotations model require to adjust the header in the annotations file as following (make sure to define the corresponding architectures and flavours): # FORMAT: 4 # ARCH: amd64 arm64 armhf ppc64el s390x # FLAVOUR: amd64-generic amd64-lowlatency arm64-generic arm64-generic-64k arm64-lowlatency arm64-lowlatency-64k armhf-generic armhf-generic-lpae ppc64el-generic s390x-generic After adjusting the header a special command is provided to transition to the new annotations-only model: $ fakeroot debian/rules migrateconfigs This command should automatically import the old configs into the new annotations file. A kernel with this change applied can still support the old annotations+configs model, the transition to the new model is not mandatory. Basically without using `fakeroot debian/rules migrateconfigs` the updateconfigs step will continue to use the old model and the old scripts (that is the safest approach to avoid potential unexpected .config changes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019000/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019131] Re: Add PPIN support for Intel EMR cpu
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1001.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-nvidia-tegra-igx -- 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/2019131 Title: Add PPIN support for Intel EMR cpu Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Intel has introduced support for their new Emerald Rapids CPU. It was backported to Jammy in #lp2015372 and in #lp2015855. The remaining feature needed to fully support EMR is PPIN (the Protected Processor Inventory/Identification Number). This was recently pushed to upstream in 6.4 in commit 36168bc061b4368ad19e82b06a6463c95d3bb9a7. The change is very straightforward, it adds a new entry for EMERALDRAPIDS_X in the cpuids table where cpus that support ppin are listed. The table is then used in `ppin_init`. In Jammy, this implementation is missing. Both Amd and Intel have their own implementation which is doing pretty much the same. Instead of a list of cpus supported, a switch case is used instead in their init functions (amd_detect_ppin and intel_ppin_init). To reduce duplication of code and to help backport smoothly the new addition of EMR, commit 0dcab41d3487acadf64d0667398e032341bd9918 “x86/cpu: Merge Intel and AMD ppin_init() functions” was backported too. Thus commits: - 0dcab41d3487acadf64d0667398e032341bd9918: "x86/cpu: Merge Intel and AMD ppin_init() functions" - 36168bc061b4368ad19e82b06a6463c95d3bb9a7: "x86/cpu: Add Xeon Emerald Rapids to list of CPUs that support PPIN" are needed to support PPIN for EMR. [Testing] Kernel was built on cbd and boot tested on a VM. [Regression potential] Very low, it is a small refactor that removes duplication and it should not affect the functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019131/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020413] Re: fix typo in config-checks invocation
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1001.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-nvidia-tegra-igx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2020413 Title: fix typo in config-checks invocation Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux-kvm source package in Jammy: Fix Released Bug description: [Impact] After migrating to the new annotations-only model in jammy we introduced a typo in debian/rules.d/4-checks.mk, that is triggered if we opt to not migrate to the new model and still use the old configs+annotations. [Test case] With debian./config/config.common.ubuntu present run the following command: $ fakeroot debian/rules clean updateconfigs [Fix] Replace @perl -> perl. [Regression potential] It's a trivial typo fix. Regressions can be introduced only if we are still using the old configs+annotations model. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020531] Re: support python < 3.9 with annotations
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1001.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-nvidia-tegra-igx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2020531 Title: support python < 3.9 with annotations Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] At the moment we can't use the annotations scripts in focal, because we are using the'|=' update operator for merging dicts, that has been introduced with python 3.9. Rewrite the code that is using this operator in a more portable way and apply this change everywhere, so that annotations will work on any backport/derivative kernels. [Test case] Run `fakeroot debian/rules updateconfigs` in focal (using the new annotations model). [Fix] Try to use the '|=' operator in a try/except block, if it fails fallback to a more portable way. [Regression potential] With this change applied we may experience regressions during the updateconfigs phase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023807] Re: Initialize linux-nvidia-tegra-igx with patch list from NVIDIA
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1001.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-nvidia-tegra-igx verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2023807 Title: Initialize linux-nvidia-tegra-igx with patch list from NVIDIA Status in linux-nvidia-tegra package in Ubuntu: New Bug description: [Impact] This change reflects the creation and initialization of a new kernel, linux-nvidia-tegra-igx. This kernel will be initialized with the patches already in linux-nvidia-tegra, and be maintained as a sibling to linux-nvidia-tegra. A patch list containing patches required to enable the IGX platform has been provided by NVIDIA, and these patches have been integrated into the new kernel. [Other Info] The following patches are contained in the NVIDIA-provided list, but need backporting to v5.15. 8681e3663411 drm/simpledrm: Support the XB24/AB24 format 9abecb1d338c drm/format-helper: Support the XB24 format 9a10c7e6519b drm/simpledrm: Add support for system memory framebuffers fa904b4cbc60 drm/simpledrm: Use struct iosys_map consistently Hence, these will be addressed in a separate change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2023807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
To no avail -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023313] Re: gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support"
** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gcp-5.19 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-gcp-5.19 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-gcp-5.19 (Ubuntu Jammy) Status: New => Fix Committed -- 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/2023313 Title: gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp-5.19 package in Ubuntu: New Status in linux-gcp source package in Jammy: Invalid Status in linux-gcp-5.19 source package in Jammy: Fix Committed Status in linux-gcp source package in Kinetic: In Progress Status in linux-gcp-5.19 source package in Kinetic: Invalid Bug description: GCP is requesting the backport of the patch "6b080c4e815ceba3c08f iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" from upstream 6.2 to the 5.19 gcp kernel The following two patches are required for the backport: 6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement map_pages io_pgtable_ops callback 251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement unmap_pages io_pgtable_ops callback More info at https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view Impact: - This allows the AMD iommu driver to map/unmap multiple pages in one call. GCP states that these changes also have a security side-effect which they are interested in. Testing: - Boot-tested the changes in SEV, SEV-SNP and non-SEV environments on AMD hardware. Regression potential: - The changes are limited to the AMD iommu driver. Regression potential could impact virtualization on AMD hardware. Risk is considered low as the changes are limited and apply cleanly from upstream. The requested patch is from 6.2 and there have been no follow-up fixes since. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2023313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027634] Re: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2027634 Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: Not sure what caused this bug. The reporting dialog was on my screen when I unlocked the PC. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 4017 F wireplumber /dev/snd/controlC1: david 4017 F wireplumber /dev/snd/seq:david 4013 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Thu Jul 13 06:32:45 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2021-06-16 (756 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20VK001CAU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=6c94f9a7-6ba0-496d-abcc-72b4e2c82feb 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.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-04-30 (73 days ago) dmi.bios.date: 04/26/2023 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: R1FET52W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20VK001CAU dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrR1FET52W(1.26):bd04/26/2023:br1.26:efr1.17:svnLENOVO:pn20VK001CAU:pvrThinkPadL13YogaGen2:rvnLENOVO:rn20VK001CAU:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20VK_BU_Think_FM_ThinkPadL13YogaGen2: dmi.product.family: ThinkPad L13 Yoga Gen 2 dmi.product.name: 20VK001CAU dmi.product.sku: LENOVO_MT_20VK_BU_Think_FM_ThinkPad L13 Yoga Gen 2 dmi.product.version: ThinkPad L13 Yoga Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2027634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027634] [NEW] package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Public bug reported: Not sure what caused this bug. The reporting dialog was on my screen when I unlocked the PC. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 4017 F wireplumber /dev/snd/controlC1: david 4017 F wireplumber /dev/snd/seq:david 4013 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Thu Jul 13 06:32:45 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2021-06-16 (756 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20VK001CAU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=6c94f9a7-6ba0-496d-abcc-72b4e2c82feb 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.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-04-30 (73 days ago) dmi.bios.date: 04/26/2023 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: R1FET52W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20VK001CAU dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrR1FET52W(1.26):bd04/26/2023:br1.26:efr1.17:svnLENOVO:pn20VK001CAU:pvrThinkPadL13YogaGen2:rvnLENOVO:rn20VK001CAU:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20VK_BU_Think_FM_ThinkPadL13YogaGen2: dmi.product.family: ThinkPad L13 Yoga Gen 2 dmi.product.name: 20VK001CAU dmi.product.sku: LENOVO_MT_20VK_BU_Think_FM_ThinkPad L13 Yoga Gen 2 dmi.product.version: ThinkPad L13 Yoga Gen 2 dmi.sys.vendor: LENOVO ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2027634 Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: Not sure what caused this bug. The reporting dialog was on my screen when I unlocked the PC. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 4017 F wireplumber /dev/snd/controlC1: david 4017 F wireplumber /dev/snd/seq:david 4013 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Thu Jul 13 06:32:45 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2021-06-16 (756 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20VK001CAU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=6c94f9a7-6ba0-496d-abcc-72b4e2c82feb 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.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-04-30 (73 days ago) dmi.bios.date: 04/26/2023 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: R1FET52W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20VK001CAU dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias:
[Kernel-packages] [Bug 2024479] Re: kdump fails on big arm64 systems when offset is not specified
Hi Jo,
Thanks for the debdiffs.
Lunar and Jammy (both: 1 patch) look good, just removed '0001' from
.patch.
Focal has 6 patches and required more attention/changes (which I adjusted),
and patches look good (some notes below for documentation/other reviewers).
The (updated) debdiffs built correctly on ppa:mfo/lp2024479 on supported
architectures (amd64, arm64, armhf, ppc64el, s390x) and I'm confident on
your testing to be performed during -proposed verification.
So, uploaded to F/J/L.
Thanks,
Mauricio
...
Focal:
1) all Origin: links had wrong commit IDs; fixed.
2) there are commits to fix 3 different things, IIUIC,
all of which are needed for big arm64 systems:
(patches 1-2) phys_offset on large memory systems;
(patches 3-5) many memory regions in /proc/iomem;
(patch 6) split / memory regions for crash kernel;
3) patch 1 is mostly a big code movement, which I followed,
and the few small changes in existing functions are for
the purpose described (and are additions, not changes).
4) patch 2 adds code and hooks it into existing code
5) patch 3 simplifies the function call path, which is OK,
and does a more significant logic change, but it still
should perform the same thing (parse /proc/iomem format,
which didn't change), and has no fixup commits.
6) patch 4 adds helpers for patches 3 and 5.
7) btw, patches 3/4 order is swapped (3 deps on 4); fixed.
8) patch 5 uses the helpers to change some existing code
from static to dynamic allocation.
9) patch 6 (added to J/L/M) too, similarly, for the number
of crash kernel / usable memory regions.
Fix-up commits: none strictly required.
---
I checked for newer commits (after 1st) in the modified files:
(cat lp2024479_focal-v2.debdiff | grep '^+--- a/' | cut -d/ -f2- | sort -u)
$ git log --oneline f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4..origin/master -- \
kexec/arch/arm64/{kexec,crashdump}-arm64.{c,h} \
kexec/mem_regions.{c,h} \
util_lib/Makefile \
vmcore-dmesg/Makefile \
vmcore-dmesg/vmcore-dmesg.c
Only 4 commits were applicable to these code changes, AFAICT.
There are 3 cleanup/style/optional, no functional impact:
- commit 545c811050a3 ("Cleanup: remove the read_elf_kcore()")
- commit 14ad054e7baa ("Fix an error definition about the variable 'fname'")
- commit a7c4cb8e9985 ("Cleanup: move it back from util_lib/elf_info.c")
There is 1 which is more serious, but does not impact Ubuntu kernels,
since do not use 52-bit (but 48-) virtual address space with M/L/J/F:
- commit 67ea2d99e135 ("arm64: make phys_offset signed")
(... phys_offset can be negative if running 52-bits kernel on 48-bits
hardware ...)
mantic:
$ git grep -r ARM64_VA_BITS origin/master-next -- debian.master/config
| grep -e "'y'" -e ARM64_VA_BITS_52
<...>:CONFIG_ARM64_VA_BITS_48 policy<{'arm64':
'y'}>
<...>:CONFIG_ARM64_VA_BITS_52
policy<{'arm64-generic-64k': 'n'}>
lunar:
$ git grep -r ARM64_VA_BITS origin/master-next -- debian.master/config
| grep -e "'y'" -e ARM64_VA_BITS_52
<...>:CONFIG_ARM64_VA_BITS_48 policy<{'arm64':
'y'}>
<...>:CONFIG_ARM64_VA_BITS_52
policy<{'arm64-generic-64k': 'n'}>
jammy:
$ git grep -r ARM64_VA_BITS origin/master-next -- debian.master/config
| grep -e "'y'" -e ARM64_VA_BITS_52
<...>:CONFIG_ARM64_VA_BITS_48 policy<{'arm64':
'y'}>
<...>:CONFIG_ARM64_VA_BITS_52
policy<{'arm64-generic-64k': 'n', 'arm64-lowlatency-64k': 'n'}>
focal:
$ git grep -r ARM64_VA_BITS origin/master-next -- debian.master/config
| grep -e "'y'" -e ARM64_VA_BITS_52
<...>:CONFIG_ARM64_VA_BITS_48 policy<{'arm64':
'y'}>
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2024479
Title:
kdump fails on big arm64 systems when offset is not specified
Status in kexec-tools package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux-hwe-5.15 package in Ubuntu:
Invalid
Status in kexec-tools source package in Focal:
In Progress
Status in linux source package in Focal:
Won't Fix
Status in linux-hwe-5.15 source package in Focal:
In Progress
Status in kexec-tools source package in Jammy:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux-hwe-5.15 source package in Jammy:
Invalid
Status in kexec-tools source package in Kinetic:
Won't Fix
Status in linux source package in Kinetic:
Won't Fix
Status in linux-hwe-5.15 source package in Kinetic:
Invalid
Status in kexec-tools source package in Lunar:
In Progress
Status in kexec-tools source package in Mantic:
Fix Released
Bug description:
[Impact]
kdump fails on arm64, on machines with a lot of memory when offset is not
[Kernel-packages] [Bug 2026652] Re: Suspend Broken
I'd love to hear if anyone has any suggestions around this, since its a hardware risk if I can't sleep my computer, or a security risk if I `pm- suspend` it and it doesn't lock. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2026652 Title: Suspend Broken Status in linux-signed-lowlatency package in Ubuntu: New Bug description: When I go to suspend my system via the UI "Suspend" option, the system fails to suspend. Instead it looks like its going to suspend, and then wakes up but with a locked screen. When I use `pm-suspend` from the command line, it suspends the system, but does not lock the screen. I have the Settings -> Privacy -> Screen Lock -> "Lock Screen on Suspend" setting enabled. I am using the Nouveau driver, with Wayland, using GNOME 44.2. This bug only started when I switched away from using any of the NVIDIA drivers, so its probably partially Nouveau related. Switching away from NVIDIA drivers (I tried them all) isn't an option, because they break: 1. External monitor connectivity 2. VMWare Horizon Debug info: 1. `lsb_release -rd` Description: Ubuntu 23.04 Release: 23.04 2. `uname -srm` Linux 6.2.0-1007-lowlatency x86_64 Please let me know of any other information needed to debug this. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7 ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12 Uname: Linux 6.2.0-1007-lowlatency x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 9 10:26:06 2023 InstallationDate: Installed on 2021-12-18 (567 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: linux-signed-lowlatency UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2026652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018979] Re: Update the 525 UDA NVIDIA driver series in Bionic, Focal, and Kinetic, Lunar
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.125.06-0ubuntu1 --- nvidia-graphics-drivers-525 (525.125.06-0ubuntu1) mantic; urgency=medium * New upstream release (LP: #2024675). -- Alberto Milone Mon, 26 Jun 2023 09:00:01 + ** Changed in: nvidia-graphics-drivers-525 (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-525 in Ubuntu. https://bugs.launchpad.net/bugs/2018979 Title: Update the 525 UDA NVIDIA driver series in Bionic, Focal, and Kinetic, Lunar Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525 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] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2018979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024675] Re: NVIDIA CVE-2023-25515, CVE-2023-25516
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.125.06-0ubuntu1 --- nvidia-graphics-drivers-525 (525.125.06-0ubuntu1) mantic; urgency=medium * New upstream release (LP: #2024675). -- Alberto Milone Mon, 26 Jun 2023 09:00:01 + ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2024675 Title: NVIDIA CVE-2023-25515, CVE-2023-25516 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-470 package in Ubuntu: Fix Released Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-470 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-530 package in Ubuntu: Triaged Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-470 source package in Focal: Fix Released Status in fabric-manager-525 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in libnvidia-nscq-470 source package in Focal: Fix Released Status in libnvidia-nscq-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-530 source package in Focal: New Status in fabric-manager-450 source package in Jammy: Fix Released Status in fabric-manager-470 source package in Jammy: Fix Released Status in fabric-manager-525 source package in Jammy: Fix Released Status in libnvidia-nscq-450 source package in Jammy: Fix Released Status in libnvidia-nscq-470 source package in Jammy: Fix Released Status in libnvidia-nscq-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-530 source package in Jammy: New Status in fabric-manager-450 source package in Kinetic: Fix Released Status in fabric-manager-470 source package in Kinetic: Fix Released Status in fabric-manager-525 source package in Kinetic: Fix Released Status in libnvidia-nscq-450 source package in Kinetic: Fix Released Status in libnvidia-nscq-470 source package in Kinetic: Fix Released Status in libnvidia-nscq-525 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-530 source package in Kinetic: New Status in fabric-manager-450 source package in Lunar: Fix Released Status in fabric-manager-470 source package in Lunar: Fix Released Status in fabric-manager-525 source package in Lunar: Fix Released Status in libnvidia-nscq-450 source package in Lunar: Fix Released Status in libnvidia-nscq-470 source package in Lunar: Fix Released Status in libnvidia-nscq-525 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-450-server source package in Lunar: Fix Released Status in nvidia-graphics-drivers-470 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-470-server source package in Lunar: Fix Released Status in nvidia-graphics-drivers-525 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-525-server source package in Lunar: Fix Released Status in nvidia-graphics-drivers-530
[Kernel-packages] [Bug 2024247] Re: Migrate the 510 and 515 NVIDIA series to 525, and 515-server to 525-server
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.125.06-0ubuntu1 --- nvidia-graphics-drivers-525 (525.125.06-0ubuntu1) mantic; urgency=medium * New upstream release (LP: #2024675). -- Alberto Milone Mon, 26 Jun 2023 09:00:01 + ** Changed in: nvidia-graphics-drivers-525 (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-525 in Ubuntu. https://bugs.launchpad.net/bugs/2024247 Title: Migrate the 510 and 515 NVIDIA series to 525, and 515-server to 525-server Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-525 source package in Bionic: In Progress Status in libnvidia-nscq-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525-server source package in Bionic: In Progress Status in fabric-manager-525 source package in Focal: Fix Released Status in libnvidia-nscq-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525-server source package in Focal: Fix Released Status in fabric-manager-525 source package in Jammy: Fix Released Status in libnvidia-nscq-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525-server source package in Jammy: Fix Released Status in fabric-manager-525 source package in Kinetic: Fix Released Status in libnvidia-nscq-525 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Kinetic: Fix Released Status in fabric-manager-525 source package in Lunar: In Progress Status in libnvidia-nscq-525 source package in Lunar: In Progress Status in nvidia-graphics-drivers-525 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-525-server source package in Lunar: In Progress Bug description: [Impact] This migrates the now obsolete NVIDIA 510 series and the now dated 515 series to the trusted 525 series, and the 515-server series to the 525-server series. No new driver release is included in this update. See the changelog entry below for a full list of changes and bugs. [Test Case] Smoke tests that we use for the -server driver series. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * debian/templates/control.in: - Add transitional packages for 515-server (LP: #2024247). * debian/templates/libnvidia-gl-flavour.install.in: - Include the missing libnvidia-api.so.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2024247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024479] Re: kdump fails on big arm64 systems when offset is not specified
** Summary changed: - kdump fails on arm64 when offset is not specified + kdump fails on big arm64 systems when offset is not specified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on big arm64 systems when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in kexec-tools source package in Focal: In Progress Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: In Progress Status in kexec-tools source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in linux-hwe-5.15 source package in Jammy: Invalid Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in linux-hwe-5.15 source package in Kinetic: Invalid Status in kexec-tools source package in Lunar: In Progress Status in kexec-tools source package in Mantic: Fix Released Bug description: [Impact] kdump fails on arm64, on machines with a lot of memory when offset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel region. [Fix] To address this issue the following upstream commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the Focal 5.15 hwe kernel (from Jammy) will be fixed. [Test Plan] You need an arm64 machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump, configure the crash kernel size, and trigger a crash. - Failing scenario (crashkernel >= 4G, without offset "@"): It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. - Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G') This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on Focal). [Regression Potential] KERNEL 5.15 - Jammy (and Focal via the HWE kernel): To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. kexec-tools - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. kexec-tools - JAMMY, LUNAR, MANTIC: Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that the reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump. [Other] Commits to backport - MANTIC: kernel 6.3: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more
[Kernel-packages] [Bug 2027567] Re: No more HDMI
After listing all packages in the PPA for Lunar Lobster, I did not found anything newer. -- 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/2027567 Title: No more HDMI Status in linux package in Ubuntu: New Bug description: Hello, Thanks for your hard work :) I just upgraded to kernel 6.2.0-25. There is no more HDMI and my external screen can not be used. Moreover, when I stop my laptop, it takes 30s. If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop takes a few seconds. I'll join screenshots of command: ls /sys/class/drm/* Thanks, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5201 F wireplumber /dev/snd/controlC1: laurent5201 F wireplumber /dev/snd/seq:laurent5192 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 11:34:15 2023 InstallationDate: Installed on 2020-07-01 (1105 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: LANG=fr_FR.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-25-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-25-generic N/A linux-backports-modules-6.2.0-25-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027615] Re: Azure: MANA: Fix doorbell access for receives
https://lists.ubuntu.com/archives/kernel-team/2023-July/141045.html -- 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/2027615 Title: Azure: MANA: Fix doorbell access for receives Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Lunar: In Progress Bug description: SRU Justification [Impact] It's inefficient to ring the doorbell page every time a WQE is posted to the received queue. Excessive MMIO writes result in CPU spending more time waiting on LOCK instructions (atomic operations), resulting in poor scaling performance. [Test Plan] MSFT tested. [Regression Potential] The MANA receive queue could stop. [Other Info] SF: #00363437 These 2 patches have been submitted for upstream inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2027615/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027615] [NEW] Azure: MANA: Fix doorbell access for receives
Public bug reported: SRU Justification [Impact] It's inefficient to ring the doorbell page every time a WQE is posted to the received queue. Excessive MMIO writes result in CPU spending more time waiting on LOCK instructions (atomic operations), resulting in poor scaling performance. [Test Plan] MSFT tested. [Regression Potential] The MANA receive queue could stop. [Other Info] SF: #00363437 These 2 patches have been submitted for upstream inclusion. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Lunar) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Lunar) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Lunar) Importance: Undecided => Medium -- 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/2027615 Title: Azure: MANA: Fix doorbell access for receives Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Lunar: In Progress Bug description: SRU Justification [Impact] It's inefficient to ring the doorbell page every time a WQE is posted to the received queue. Excessive MMIO writes result in CPU spending more time waiting on LOCK instructions (atomic operations), resulting in poor scaling performance. [Test Plan] MSFT tested. [Regression Potential] The MANA receive queue could stop. [Other Info] SF: #00363437 These 2 patches have been submitted for upstream inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2027615/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027567] Re: No more HDMI
I think I found relevant info here: https://wiki.ubuntu.com/Kernel/FAQ """ My bug is Fix Committed but the fix is not in the kernel? Once a fix has been reviewed and approved on the Kernel Team email list it will then be applied to the kernel git tree. When sufficient updates have accumulated a -proposed kernel will be uploaded; you need the proposed pocket enabled to get these kernels. It can take some time before these changes are uploaded, however every day the tree is checked and if there are any new patches a new pre-proposed kernel is automatically uploaded to the kernel team pre-proposed PPA ppa:~kernel-ppa/pre-proposed. Adding both the proposed pocket and the pre-proposed PPA will get you all pending fixes as soon as possible. See Kernel/Dev/KernelTesting for details. """ -- 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/2027567 Title: No more HDMI Status in linux package in Ubuntu: New Bug description: Hello, Thanks for your hard work :) I just upgraded to kernel 6.2.0-25. There is no more HDMI and my external screen can not be used. Moreover, when I stop my laptop, it takes 30s. If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop takes a few seconds. I'll join screenshots of command: ls /sys/class/drm/* Thanks, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5201 F wireplumber /dev/snd/controlC1: laurent5201 F wireplumber /dev/snd/seq:laurent5192 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 11:34:15 2023 InstallationDate: Installed on 2020-07-01 (1105 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: LANG=fr_FR.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-25-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-25-generic N/A linux-backports-modules-6.2.0-25-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027567] Re: No more HDMI
laurent@laurent-GL73-8SD:~$ sudo apt-add-repository ppa:~kernel-ppa/pre-proposed [sudo] Mot de passe de laurent : ERROR: ppa 'kernel-ppa/pre-proposed' not found (use --login if private) It seems the FAQ is not up to date. -- 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/2027567 Title: No more HDMI Status in linux package in Ubuntu: New Bug description: Hello, Thanks for your hard work :) I just upgraded to kernel 6.2.0-25. There is no more HDMI and my external screen can not be used. Moreover, when I stop my laptop, it takes 30s. If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop takes a few seconds. I'll join screenshots of command: ls /sys/class/drm/* Thanks, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5201 F wireplumber /dev/snd/controlC1: laurent5201 F wireplumber /dev/snd/seq:laurent5192 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 11:34:15 2023 InstallationDate: Installed on 2020-07-01 (1105 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: LANG=fr_FR.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-25-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-25-generic N/A linux-backports-modules-6.2.0-25-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027567] Re: No more HDMI
I found this instead: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed -- 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/2027567 Title: No more HDMI Status in linux package in Ubuntu: New Bug description: Hello, Thanks for your hard work :) I just upgraded to kernel 6.2.0-25. There is no more HDMI and my external screen can not be used. Moreover, when I stop my laptop, it takes 30s. If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop takes a few seconds. I'll join screenshots of command: ls /sys/class/drm/* Thanks, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5201 F wireplumber /dev/snd/controlC1: laurent5201 F wireplumber /dev/snd/seq:laurent5192 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 11:34:15 2023 InstallationDate: Installed on 2020-07-01 (1105 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: LANG=fr_FR.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-25-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-25-generic N/A linux-backports-modules-6.2.0-25-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027567] Re: No more HDMI
I have read: https://wiki.ubuntu.com/Kernel/Bugs It seems the next step to help is this: > 4. Finally, it's critical to also make sure to test the latest development > Ubuntu kernel version as well as the latest upstream mainline kernel. But the wiki for latest upstream mainline kernel tells that I may need to disable the Nvidia driver which will guaranty that I'm not testing what the bug is about. And I did not found a wiki for "test the latest development Ubuntu kernel version as well". When I look here: https://packages.ubuntu.com/search?keywords=linux-generic I do not see any newer kernel for lunar lobster. Any help on this would be great :) -- 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/2027567 Title: No more HDMI Status in linux package in Ubuntu: New Bug description: Hello, Thanks for your hard work :) I just upgraded to kernel 6.2.0-25. There is no more HDMI and my external screen can not be used. Moreover, when I stop my laptop, it takes 30s. If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop takes a few seconds. I'll join screenshots of command: ls /sys/class/drm/* Thanks, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5201 F wireplumber /dev/snd/controlC1: laurent5201 F wireplumber /dev/snd/seq:laurent5192 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 11:34:15 2023 InstallationDate: Installed on 2020-07-01 (1105 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: LANG=fr_FR.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-25-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-25-generic N/A linux-backports-modules-6.2.0-25-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027567] Re: No more HDMI
** Attachment added: "Capture d’écran du 2023-07-12 11-24-42.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+attachment/5685790/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-07-12%2011-24-42.png -- 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/2027567 Title: No more HDMI Status in linux package in Ubuntu: New Bug description: Hello, Thanks for your hard work :) I just upgraded to kernel 6.2.0-25. There is no more HDMI and my external screen can not be used. Moreover, when I stop my laptop, it takes 30s. If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop takes a few seconds. I'll join screenshots of command: ls /sys/class/drm/* Thanks, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5201 F wireplumber /dev/snd/controlC1: laurent5201 F wireplumber /dev/snd/seq:laurent5192 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 11:34:15 2023 InstallationDate: Installed on 2020-07-01 (1105 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: LANG=fr_FR.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-25-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-25-generic N/A linux-backports-modules-6.2.0-25-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027567] Re: No more HDMI
I'm sorry. I just tried again to upload the screenshot. But it is not possible to open the PNG files when I click on them in the bug report. -- 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/2027567 Title: No more HDMI Status in linux package in Ubuntu: New Bug description: Hello, Thanks for your hard work :) I just upgraded to kernel 6.2.0-25. There is no more HDMI and my external screen can not be used. Moreover, when I stop my laptop, it takes 30s. If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop takes a few seconds. I'll join screenshots of command: ls /sys/class/drm/* Thanks, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5201 F wireplumber /dev/snd/controlC1: laurent5201 F wireplumber /dev/snd/seq:laurent5192 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 11:34:15 2023 InstallationDate: Installed on 2020-07-01 (1105 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: LANG=fr_FR.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-25-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-25-generic N/A linux-backports-modules-6.2.0-25-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024479] Re: kdump fails on arm64 when offset is not specified
Ioanna and I just discussed about the working scenario (eg, crashkernel=1G on 5.4 kernel), for it to be verified/no regressions with the patches (patched kexec-tools on 5.4 kernel). This apparently isn't an issue, as the patch in J/L mentions it is backward compatible (still going through the other patches in F), but that should, sure, be double checked. Updated the Test Plan section accordingly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on arm64 when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in kexec-tools source package in Focal: In Progress Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: In Progress Status in kexec-tools source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in linux-hwe-5.15 source package in Jammy: Invalid Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in linux-hwe-5.15 source package in Kinetic: Invalid Status in kexec-tools source package in Lunar: In Progress Status in kexec-tools source package in Mantic: Fix Released Bug description: [Impact] kdump fails on arm64, on machines with a lot of memory when offset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel region. [Fix] To address this issue the following upstream commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the Focal 5.15 hwe kernel (from Jammy) will be fixed. [Test Plan] You need an arm64 machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump, configure the crash kernel size, and trigger a crash. - Failing scenario (crashkernel >= 4G, without offset "@"): It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. - Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G') This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on Focal). [Regression Potential] KERNEL 5.15 - Jammy (and Focal via the HWE kernel): To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. kexec-tools - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. kexec-tools - JAMMY, LUNAR, MANTIC: Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that the reserved kernel may
[Kernel-packages] [Bug 2024479] Re: kdump fails on arm64 when offset is not specified
** Description changed: [Impact] kdump fails on arm64, on machines with a lot of memory when offset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel region. [Fix] To address this issue the following upstream commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the Focal 5.15 hwe kernel (from Jammy) will be fixed. [Test Plan] You need an arm64 machine (can be a VM too) with large memory e.g. 128G. - Install linux-crashdump and trigger a crash. - It won't work unless the offset is specified because the memory crashkernel cannot be allocated. + Install linux-crashdump, configure the crash kernel size, and trigger a crash. + + - Failing scenario (crashkernel >= 4G, without offset "@"): + + It won't work unless the offset is specified because the memory + crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. + + - Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G') + + This must continue to work with the new patches (ie, no regressions), + including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on + Focal). [Regression Potential] KERNEL 5.15 - Jammy (and Focal via the HWE kernel): To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. kexec-tools - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. kexec-tools - JAMMY, LUNAR, MANTIC: Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that the reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump. [Other] Commits to backport - MANTIC: kernel 6.3: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - LUNAR: kernel 6.2: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - KINETIC: WON'T FIX Kinetic won't be fixed as it is EOL soon. - JAMMY: kernel (5.15 kernel): a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified 4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel() 8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed 5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64 944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
[Kernel-packages] [Bug 2024479] Re: kdump fails on arm64 when offset is not specified
** Description changed: - [Description] + [Impact] - kdump fails on arm64, on machines with a lot of memory when offeset is not specified, + kdump fails on arm64, on machines with a lot of memory when offset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. - In addition kexec-tools needs to support more than one crash kernel regions. + In addition kexec-tools needs to support more than one crash kernel region. [Fix] - To address this issue the following upstrem commits are needed: + To address this issue the following upstream commits are needed: - From the kernel side: - commit a9ae89df737756d92f0e14873339cf393f7f7eb0 - Author: Zhen Lei - Date: Wed Nov 16 20:10:44 2022 +0800 + commit a9ae89df737756d92f0e14873339cf393f7f7eb0 + Author: Zhen Lei + Date: Wed Nov 16 20:10:44 2022 +0800 - arm64: kdump: Support crashkernel=X fall back to reserve region + arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones - commit a149cf00b158e1793a8dd89ca492379c366300d2 - Author: Zhen Lei - Date: Wed Nov 16 20:10:43 2022 +0800 + commit a149cf00b158e1793a8dd89ca492379c366300d2 + Author: Zhen Lei + Date: Wed Nov 16 20:10:43 2022 +0800 - arm64: kdump: Provide default size when crashkernel=Y,low is not + arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: - commit b5a34a20984c4ad27cc5054d9957af8130b42a50 - Author: Chen Zhou - Date: Mon Jan 10 18:20:08 2022 +0800 + commit b5a34a20984c4ad27cc5054d9957af8130b42a50 + Author: Chen Zhou + Date: Mon Jan 10 18:20:08 2022 +0800 - arm64: support more than one crash kernel regions + arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. - Only the 5.15 hwe focal kernel will be fixed. + Only the Focal 5.15 hwe kernel (from Jammy) will be fixed. - [Test] + [Test Plan] - You need a machine (can be a VM too) with large memory e.g. 128G. + You need an arm64 machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump and trigger a crash. It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. [Regression Potential] - KERNEL 5.15: + KERNEL 5.15 - Jammy (and Focal via the HWE kernel): + To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. - KEXEX - FOCAL: + kexec-tools - FOCAL: + To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. - KEXEC - JAMMY, LUNAR, MANTIC: - Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that teh reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump. + kexec-tools - JAMMY, LUNAR, MANTIC: + + Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 + code. It enables kexec to recognise that the reserved kernel may use + more than one kernel region. Things could go worng when gatherinng a + crashdump. [Other] Commits to backport - MANTIC: - kernel 6.3: not affected + kernel 6.3: not affected - kexec-tools: - b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions + kexec-tools: + b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - LUNAR: - kernel 6.2: not
[Kernel-packages] [Bug 2027567] Re: No more HDMI
** Attachment added: "resultOfCommandWith6_2_0_24" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+attachment/5685683/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-07-12%2011-29-20.png -- 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/2027567 Title: No more HDMI Status in linux package in Ubuntu: New Bug description: Hello, Thanks for your hard work :) I just upgraded to kernel 6.2.0-25. There is no more HDMI and my external screen can not be used. Moreover, when I stop my laptop, it takes 30s. If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop takes a few seconds. I'll join screenshots of command: ls /sys/class/drm/* Thanks, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5201 F wireplumber /dev/snd/controlC1: laurent5201 F wireplumber /dev/snd/seq:laurent5192 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 11:34:15 2023 InstallationDate: Installed on 2020-07-01 (1105 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: LANG=fr_FR.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-25-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-25-generic N/A linux-backports-modules-6.2.0-25-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027567] [NEW] No more HDMI
Public bug reported: Hello, Thanks for your hard work :) I just upgraded to kernel 6.2.0-25. There is no more HDMI and my external screen can not be used. Moreover, when I stop my laptop, it takes 30s. If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop takes a few seconds. I'll join screenshots of command: ls /sys/class/drm/* Thanks, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5201 F wireplumber /dev/snd/controlC1: laurent5201 F wireplumber /dev/snd/seq:laurent5192 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 11:34:15 2023 InstallationDate: Installed on 2020-07-01 (1105 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: LANG=fr_FR.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-25-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-25-generic N/A linux-backports-modules-6.2.0-25-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "resultOfCommandWith6_2_0_25" https://bugs.launchpad.net/bugs/2027567/+attachment/5685665/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-07-12%2011-24-42.png -- 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/2027567 Title: No more HDMI Status in linux package in Ubuntu: New Bug description: Hello, Thanks for your hard work :) I just upgraded to kernel 6.2.0-25. There is no more HDMI and my external screen can not be used. Moreover, when I stop my laptop, it takes 30s. If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop takes a few seconds. I'll join screenshots of command: ls /sys/class/drm/* Thanks, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5201 F wireplumber /dev/snd/controlC1: laurent5201 F wireplumber /dev/snd/seq:laurent5192 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 11:34:15 2023 InstallationDate: Installed on 2020-07-01 (1105 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: LANG=fr_FR.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-25-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-25-generic N/A linux-backports-modules-6.2.0-25-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7
[Kernel-packages] [Bug 2026863] Re: zfs-linux SRU build support against hwe kernels
** Changed in: zfs-linux (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2026863 Title: zfs-linux SRU build support against hwe kernels Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Jammy: In Progress Bug description: [ Impact ] * hwe kernels keep on changing * jammy zfs-linux 2.1.5 upstream releases + cherry-picks is quite old, thus a jump to 2.1.12 or 2.2 has potential to break userspace * Instead cherry-pick patches that continue to enable building zfs-dkms against hwe kernels, if one desires to use dkms from the archive, rather than prebuilt modules that all of Ubuntu kernels ship. * the cherry-picks area gainst config/* code (autoconf/m4) and kernel code (module/ & include/), without any changes to userspace tooling or fixes. [ Test Plan ] * verify zfs-dkms module builds from source against v5.15, v5.19, v6.2, v6.3 kernels on jammy * verify existing zsys installs continue to work * verify kernel team zfs tests-suites continue to work with v5.15 kernel [ Where problems could occur ] * majority of diff is in config macros to detect different compatible kernel APIs and ABIs and use an appropriate one. there are changes to uidmap handling for v6.3 kernels, however it is mostly ignored by userspace without intruducing new feature. LXD will need to be double checked, as it may assume this driver version seems to accept uidmap mount options - which it then ignores. * Note this is still at feature parity with Lunar's upload 2.1.9-2ubuntu1.1, despite having partial kernel driver only build compat with v6.3 - as v6.3 kernels are not expected to land in lunar, and will not land in jammy until after mantic release. Mantic already has much newer 2.2.x series zfs-linux. [ Other Info ] * This is similar to previous zfs-linux SRUs we have performed in the past. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2026863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
** Changed in: archlinux Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: Invalid Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026887] Re: [intel] gnome-shell Wayland sessions fail to start on Intel systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argum
Thanks for the bug report. It appears the kernel '5.15.0-1034-intel- iotg' is too old for the integrated GPU of 'i7-1260P'. Did you install that kernel manually? Or perhaps install some IOT image instead of Ubuntu Desktop? I would have expected a fresh install of Ubuntu Desktop 22.04.2 to come with a newer kernel: https://ubuntu.com/download/desktop so please install that instead. ** Tags added: jammy ** Package changed: mutter (Ubuntu) => linux-intel-iotg (Ubuntu) ** Summary changed: - [intel] gnome-shell Wayland sessions fail to start on Intel systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) + [intel] gnome-shell Wayland sessions fail to start on intel-iotg kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) ** Changed in: linux-intel-iotg (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: [intel] gnome-shell Wayland sessions fail to start on intel-iotg kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux-intel-iotg package in Ubuntu: New Bug description: Hi Ubuntu Team, MY ISSUE: I installed today my PC with Ubuntu IOT Desktop(22.04.2 LTS (Jammy Jellyfish)). But with updated for all packages and with reboot PC, i have error with starting gdm and access to /dev/dri/card0. ERROR: iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:11 MY-PC gnome-session-binary[1022]: Entering running state root@MY-PC:/home/tester# journalctl -b --no-pager | grep gnome- iul 11 19:00:09 MY-PC systemd[1]: Mounting Mount unit for gnome-3-38-2004, revision 119... iul 11 19:00:09 MY-PC systemd[1]: Mounted Mount unit for gnome-3-38-2004, revision 119. iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-shell[1040]: Running GNOME Shell (using mutter 42.9) as a Wayland display server iul 11 19:00:10 MY-PC gnome-shell[1040]: Device '/dev/dri/card0' prefers shadow buffer iul 11 19:00:10 MY-PC gnome-shell[1040]: Added device '/dev/dri/card0' (i915) using atomic mode setting. iul 11 19:00:10 MY-PC gnome-shell[1040]: Created gbm renderer for '/dev/dri/card0' iul 11 19:00:10 MY-PC gnome-shell[1040]: Boot VGA GPU /dev/dri/card0 selected as primary iul 11 19:00:10 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:10 MY-PC gnome-shell[1040]: Using public X11 display :1024, (using :1025 for managed services) iul 11 19:00:10 MY-PC gnome-shell[1040]: Using Wayland display name 'wayland-0' iul 11 19:00:11 MY-PC gnome-shell[1040]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. iul 11 19:00:11 MY-PC gnome-shell[1040]: Will monitor session c1 iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:11 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell "
[Kernel-packages] [Bug 2026789] Re: Display freeze when using gnome settings " display" to enable/disable displays on eGPU
Thanks, I can see you switched to Xorg so the log in comment #5 is no longer relevant to this bug. Not all freezes have the same cause. What I can see in that log is the Nvidia driver refusing to support eGPUs at boot time: Jul 11 13:19:52 semiauto /usr/libexec/gdm-x-session[1638]: (WW) NVIDIA(GPU-0): This device is an external GPU, but external GPUs have not Jul 11 13:19:52 semiauto /usr/libexec/gdm-x-session[1638]: (WW) NVIDIA(GPU-0): been enabled with AllowExternalGpus. Disabling this device Jul 11 13:19:52 semiauto /usr/libexec/gdm-x-session[1638]: (WW) NVIDIA(GPU-0): to prevent crashes from accidental removal. To fix that you need to add a custom Xorg configuration line as documented in: http://us.download.nvidia.com/XFree86/Linux-x86_64/535.54.03/README/egpu.html But that's not actually related to this bug anymore since this original bug was almost certainly about a Wayland session. For this bug we are still waiting on an original log from the Wayland session (unless it's the log already posted in bug 2026790?). ** Tags added: egpu hotplug ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: Incomplete => New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/2026789 Title: Display freeze when using gnome settings " display" to enable/disable displays on eGPU Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: When using the Ubuntu settings app to change displays I was enabling and disabling displays to see if I could replicate a problem. It appears that the drivers / setup are OK with 2x displays, but things start to fall apart when there are 3x displays. 2x displys managed by NVIDIA displayport connection, and 1x display managed by the Intel Iris GPU. I have noticed that windows appear to move between displays, so I think there is a problem with how the displays and the windows are arranged. Attached are as many logs as I can find for this problem. Notably, I am receiving errors in my local terminal when reporting this bug: [15578:15578:0710/200056.340294:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! [15578:15578:0710/200056.356275:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! [15578:15578:0710/200056.357312:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! [15529:15529:0710/200138.416553:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented This appears to be related to DRM ?? Tehese messages occured as I enabled / disabled the displays on displayport: [Mon Jul 10 19:53:29 2023] [drm] [nvidia-drm] [GPU ID 0x5200] Framebuffer memory not appropriate for scanout [Mon Jul 10 19:53:29 2023] [drm] [nvidia-drm] [GPU ID 0x5200] Framebuffer memory not appropriate for scanout [Mon Jul 10 19:53:41 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0xfc099386 [Mon Jul 10 19:54:23 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0xcd359766 [Mon Jul 10 19:54:23 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0x40936ab7 These messages appeard when I started the gnome display manager : Mon Jul 10 19:46:16 2023] rfkill: input handler enabled [Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Mon Jul 10 19:46:17 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0xf989da34 [Mon Jul 10 19:46:17 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0x32149488 [Mon Jul 10 19:46:18 2023] rfkill: input handler disabled [Mon Jul 10 19:46:25 2023] bijiben-shell-s[3102]: segfault at 7f9c05be1b13 ip 7f9c1bb4e5a1 sp 7fff6f49e438 error 4 in libgobject-2.0.so.0.7600.1[7f9c1bb24000+34000] likely on CPU 6 (core 2, socket 0) [Mon Jul 10 19:46:25 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48>
