[Kernel-packages] [Bug 2031969] Re: Ubuntu 23.04: Suspend & Power off
The problem is with kernel 6.2 which is in both 23.04 and 22.04 (hwe) so affects both releases. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2031969 Title: Ubuntu 23.04: Suspend & Power off Status in linux package in Ubuntu: Confirmed Bug description: Since update to version 23.04 I am facing several problems related to system suspend and shutdownon a HP Envy 15 notebook (2016). The system refuses to wake up from standby mode, especially if it has run for a longer time. Screen is black, no response to keyboard or trackpad actions, power button led is on. The only way out of here is a long press on the power button. Another problem with this and I think it's kind of related. If you want to shut down the computer after a long runtime, the machine won't power off. In the logs you can see the steps for shutting down the OS, but sometimes the machine stays powered on. The power led is on, screen is black, no response to keyboard or trackpad actions. System has to be powered off by a long press on the power button. Ubuntu 6.2.0-27.28-generic 6.2.15 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom2051 F wireplumber /dev/snd/seq:tom2037 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 19 16:01:07 2023 InstallationDate: Installed on 2018-07-01 (1875 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-27-generic N/A linux-backports-modules-6.2.0-27-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-05-01 (109 days ago) dmi.bios.date: 11/10/2020 dmi.bios.release: 15.62 dmi.bios.vendor: Insyde dmi.bios.version: F.62 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81D2 dmi.board.vendor: HP dmi.board.version: KBC Version 87.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.21 dmi.modalias: dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY Notebook dmi.product.sku: Z6J78EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038719] Re: Monitor Issues
At least attach the logs from the previous (failed) boot: $ journalctl -b -1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038719 Title: Monitor Issues Status in linux package in Ubuntu: Incomplete Bug description: Originally on Kernel 5.13 my GPU is not detected and only one monitor out of my three functions. I originally fixed this by moving to the latest (6.2) which came with its own issues, of which all were resolved. Yesterday I updated firmware, and this morning after reboot only one monitor works again, and the monitor is all stripey and there are 4 of a corner of the screen displayed in strips. The operation is fine but the display is broken. Hopefully this describes the issue enough, if you need an image just tell me how to upload it - I am on the mint distro, I am a newbie to this so I hope this is still the right place. CPU: Ryzen 7 3700X GPU: Radeon 7900XTX Boot: Clean linux only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038745] Re: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed
** Tags added: kern-8205 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2038745 Title: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Confirmed Status in linux-firmware source package in Lunar: Confirmed Status in linux-firmware source package in Mantic: Fix Released Bug description: [Impact] NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to latest Ubuntu 22.04.3 kernel and firmware Not repro with NV21 XL or W6800 [Fix] Cherry-pick the latest PMFW https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin [Other Info] The IMU FW included in Linux firmware package needs to be paired with the latest PMFW smu_13_0_0.bin for Navi31 Jammy firmware updates only include latest IMU firmware. https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux- firmware 20220329.git681281e4-0ubuntu3.19 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin (Missing) https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038678] Re: linux (6.2.0-34.34) lunar; urgency=medium * lunar/linux: 6.2.0-34.34 -proposed tracker (LP: #2033779)
Please attach logs from the failed (previous) boot. Something like: $ journalctl -b -1 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Summary changed: - linux (6.2.0-34.34) lunar; urgency=medium* lunar/linux: 6.2.0-34.34 -proposed tracker (LP: #2033779) + 6.2.0-34.34 - Black screen with i915 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038678 Title: 6.2.0-34.34 - Black screen with i915 Status in linux package in Ubuntu: Incomplete Bug description: black screen after grub and after login using i915 revert back to previous kernel. 6.2.0-33 unable to run report for logs due to black screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029905] Re: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS
This does not appear to be a blocker for Ubuntu 23.10; removing the milestone. ** Changed in: linux (Ubuntu Mantic) Milestone: ubuntu-23.10 => None -- 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/2029905 Title: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Incomplete Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Bug description: This BUG is created to integrate the latest mpi3mr driver available upstream into the upcoming Ubuntu LTS OS inbox driver. - The mpi3mr inbox driver version available in the latest LTS (22.04.02) is 8.0.0.69.0. which is considerably the base driver + management app support. - The latest mpi3mr driver available in the upstream is 8.4.1.0.0 which has various important features and critical bugs. Please include below the latest mpi3mr upstream patset: git online commit id and description: f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0 2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time 130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA 7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels 47cd930ee6ae scsi: mpi3mr: Support new power management framework ee6f2d6bb2a0 scsi: mpi3mr: Update mpi3 header files 5ba207e55e7f scsi: mpi3mr: Fix error code in mpi3mr_transport_smp_handler() a113c02f5738 scsi: mpi3mr: Fix error codes in mpi3mr_report_manufacture() 7f90bc70d1a6 scsi: mpi3mr: Block I/Os while refreshing target dev objects 2745ce0e6d30 scsi: mpi3mr: Refresh SAS ports during soft reset 176d4aa69c6e scsi: mpi3mr: Support SAS transport class callbacks 2bd37e284914 scsi: mpi3mr: Add framework to issue MPT transport cmds 7f56c791969e scsi: mpi3mr: Add SAS SATA end devices to STL 626665e9c38d scsi: mpi3mr: Get
[Kernel-packages] [Bug 1942260] Re: compress firmware in /lib/firmware
** Changed in: linux-firmware-raspi (Ubuntu Mantic) Milestone: ubuntu-23.10 => mantic-updates ** Changed in: linux-firmware-raspi (Ubuntu Mantic) Milestone: mantic-updates => None -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1942260 Title: compress firmware in /lib/firmware Status in firmware-sof package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in firmware-sof source package in Mantic: Fix Released Status in initramfs-tools source package in Mantic: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-firmware-raspi source package in Mantic: Confirmed Bug description: -- initramfs-tools [Impact] * linux supports xz compressed linux-firmware which saves disk space. In focal, initramfs-tools only knows how to included uncompressed firmware files (even when kernel supports loading compressed ones). Newer releases of linux-firmware may use compressed firmware files only, in such cases it would be nice for focal's initramfs-tools to support compressed firmware files in case of partial or incomplete upgrades (i.e. linux-firmware force installed or upgraded, without newer initramfs-tools). The proposed changes to initramfs-tools are backwards and forwards compatible, they prefer to include uncompressed firmware files; and if missing, include compressed firmware files in their uncompressed form. Thus maintaining compatibility with any kernels, irrespective of compressed/uncompressed firmware inputs. [Test Plan] * Compress all files shipped by linux-firmware with xz * Rebuild initrd * Check that all the same firmware files are still included in the initramfs, in their uncompressed form as before [Where problems could occur] * This SRU is precautionary to prevent accidental installation of compressed linux-firmware from generating incorrect initramfs. It should be noted that whilst initramfs-tools would create a compatible initramfs with any kernels, pre-v5.3 kernels do not support xz compressed firmware files at runtime. Mixing this new initramfs with compressed firmwares and pre 5.3 kernels may lead to expectations of supporting compressed firmware files with them only working at initrd stage and not at runtime. [Other Info] Original bug report Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1942260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038292] Re: nvidia-graphics-drivers-535{, -server} lower than in lunar & jammy
My understanding is this will be able to go into the mantic release
pocket with the kernel respin currently in progress, so should not need
to be an SRU.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2038292
Title:
nvidia-graphics-drivers-535{,-server} lower than in lunar & jammy
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Fix Committed
Status in ubuntu-release-upgrader package in Ubuntu:
Invalid
Bug description:
nvidia-graphics-drivers-535 and nvidia-graphics-drivers-535-server are
lower than in lunar
meaning we need to sru 535.113 into mantic, before turning on
upgrades.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2038292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature
marking this fix committed for linux, version 6.5.0-9.9 in mantic- proposed should contain the fix. ** Changed in: linux (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038567 Title: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in lxd package in Ubuntu: Triaged Status in snapd package in Ubuntu: New Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Please continue to use MUTTER_DEBUG_KMS_THREAD_TYPE=user as a workaround then. Also if you're still experiencing the bug please run: sudo apt install drm-info drm_info > drminfo.txt and attach the resulting text file here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: Triaged Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038665] Re: Intel AX210 Bluetooth not working properly in focal kernel 5.15
** Summary changed: - bluetooth not working proper;ly + Intel AX210 Bluetooth not working properly in focal kernel 5.15 ** Package changed: bluez (Ubuntu) => linux-hwe-5.15 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2038665 Title: Intel AX210 Bluetooth not working properly in focal kernel 5.15 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: My bluetooth it's loosing connection every 3 or 4 seconds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 11:21:08 2023 InstallationDate: Installed on 2023-10-04 (1 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUS System Product Name PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic root=UUID=9828ca97-751b-4832-b775-db6c7dab004d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2022 dmi.bios.release: 8.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X670E-E GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/04/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS hciconfig: hci0:Type: Primary Bus: USB BD Address: 2C:0D:A7:1D:E9:2F ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:2128 acl:114 sco:417074 events:3840 errors:0 TX bytes:24227828 acl:3643 sco:414720 commands:147 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2038665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038782] [NEW] linux-firmware halts boot before grub screen on clean install-upgrade to Ubuntu 22.04.3
Public bug reported: System halts just after filesystem journaling after USB install of LTS Ubuntu 22.04.2 to Ubuntu 22.04.3, never makes it to grub screen, can't boot system. Another bug report from 2020 says their system gets past grub screen and then gets stuck, I don't even make it that far, no other bug reports I found seems similar. Since I can't get to grub, I can't adjust boot options because it's apparently not going to load the OS. I receive no errors. Since the OS isn't loaded, nothing shows up in the filesystem logs. Can CTRL+ALT+DEL reboot, but can't get past journaling and into GRUB. Since system won't proceed further after journaling completes, apport can't start or dump a report. Steps to Reproduce: --- * Boot from official USB 22.04.2 USB image made as per Ubuntu instructions using Ubuntu bootable disk tool * Accept all installation defaults * reboot Once rebooted and at 22.04.2 desktop, open terminal and issue: * sudo apt update (You will be told 340+ packages need to be installed) * sudo apt upgrade (wait for apt upgrade to complete) * reboot After rebooting from upgrade, system halts after filesystem journaling (which reports filesystem is in a good state on my system), yet system will not continue to grub/OS boot options screen despite filesystem being OK. I left system running at that spot overnight, no change in the AM, still stuck at journaling screen. Again, journaling reports no errors, computer simply won't boot. HOW I VERIFIED: --- Wiped disk (full overwrite erase) Reinstalled as per above sudo apt update sudo apt-mark hold linux-firmware sudo apt upgrade reboot After above steps, system boots & runs (using same system now to write this bug report). At this time, the system is as fully patched as I can get it: user@myhost:~$ sudo apt list --upgradeable [sudo] password for user: Listing... Done gjs/jammy-updates 1.72.4-0ubuntu0.22.04.1 amd64 [upgradable from: 1.72.2-0ubuntu1] libgjs0g/jammy-updates 1.72.4-0ubuntu0.22.04.1 amd64 [upgradable from: 1.72.2-0ubuntu1] linux-firmware/jammy-updates,jammy-updates 20220329.git681281e4-0ubuntu3.19 all [upgradable from: 20220329.git681281e4-0ubuntu3.10] ADDITIONAL NOTES: Booting into a stand-alone memory test on the system finds no memory faults or errors. Video stress-test of all functions (2D, shaders, vector, bump, buffer, raytrace etc.) performed on the system prior to running "sudo apt upgrade". No failure, no crash, frame rates on par with public benchmarks. Crushed the card at 4K resolution, and also ran it with eight 1k instances with no problems. Video card ruled out. Replaced hard disk with new disk from different vendor, (even though journal finds no errors), problem persisted. Simply placing a hold on linux-firmware package prevents the problem reliably regardless of hardware setup. System up and stable now across multiple reboots and software installs for 6 hours and now has full software load, including qemu/kvm. DIAGNOSTICS --- user@myhost:~$ sudo lshw -short H/W path Device Class Description system System Product Name (SKU) /0busTUF GAMING B550-PLUS WIFI II /0/0 memory 64KiB BIOS /0/34 memory 64GiB System Memory /0/34/0 memory 16GiB DIMM DDR4 Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns) /0/34/1 memory 16GiB DIMM DDR4 Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns) /0/34/2 memory 16GiB DIMM DDR4 Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns) /0/34/3 memory 16GiB DIMM DDR4 Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns) /0/37 memory 512KiB L1 cache /0/38 memory 4MiB L2 cache /0/39 memory 32MiB L3 cache /0/3a processor AMD Ryzen 7 5800X 8-Core Processor /0/100bridge Starship/Matisse Root Complex /0/100/0.2genericStarship/Matisse IOMMU /0/100/1.1bridge Starship/Matisse GPP Bridge /0/100/1.1/0 /dev/nvme0 storageWD_BLACK SN770 2TB /0/100/1.1/0/0hwmon0 disk NVMe disk /0/100/1.1/0/2/dev/ng0n1 disk NVMe disk /0/100/1.1/0/1/dev/nvme0n1disk 2TB NVMe disk /0/100/1.1/0/1/1 volume 511MiB Windows FAT
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Removing packages from mantic: nvidia-graphics-drivers-450-server 450.248.02-0ubuntu2 in mantic libnvidia-cfg1-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-cfg1-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-common-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-common-440-server 450.248.02-0ubuntu2 in mantic arm64 libnvidia-common-440-server 450.248.02-0ubuntu2 in mantic armhf libnvidia-common-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-common-440-server 450.248.02-0ubuntu2 in mantic ppc64el libnvidia-common-440-server 450.248.02-0ubuntu2 in mantic riscv64 libnvidia-common-440-server 450.248.02-0ubuntu2 in mantic s390x libnvidia-common-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-common-450-server 450.248.02-0ubuntu2 in mantic arm64 libnvidia-common-450-server 450.248.02-0ubuntu2 in mantic armhf libnvidia-common-450-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-common-450-server 450.248.02-0ubuntu2 in mantic ppc64el libnvidia-common-450-server 450.248.02-0ubuntu2 in mantic riscv64 libnvidia-common-450-server 450.248.02-0ubuntu2 in mantic s390x libnvidia-compute-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-compute-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-compute-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-compute-450-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-decode-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-decode-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-decode-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-decode-450-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-encode-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-encode-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-encode-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-encode-450-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-extra-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-extra-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-extra-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-extra-450-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-fbc1-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-fbc1-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-fbc1-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-fbc1-450-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-gl-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-gl-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-gl-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-gl-450-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-ifr1-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-ifr1-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-ifr1-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-ifr1-450-server 450.248.02-0ubuntu2 in mantic i386 nvidia-compute-utils-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-compute-utils-450-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-dkms-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-dkms-450-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-driver-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-driver-450-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-headless-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-headless-450-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-headless-no-dkms-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-headless-no-dkms-450-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-kernel-common-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-kernel-common-450-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-kernel-source-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-kernel-source-450-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-utils-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-utils-450-server 450.248.02-0ubuntu2 in mantic amd64 xserver-xorg-video-nvidia-440-server 450.248.02-0ubuntu2 in mantic amd64
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Now: $ reverse-depends src:nvidia-graphics-drivers-450-server Reverse-Depends === * libnvidia-decode-440-server (for libnvidia-decode-450-server) * libnvidia-encode-440-server (for libnvidia-encode-450-server) * libnvidia-fbc1-440-server (for libnvidia-fbc1-450-server) * libnvidia-ifr1-440-server (for libnvidia-ifr1-450-server) Packages without architectures listed are reverse-dependencies in: amd64, i386 $ And these are false-positives because built from this source. (I wonder if the server implementation has trouble parsing the Sources file for this, because the Binary: field is strangely split across lines...) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038759] Re: ubuntu does not mount usb disks
The failure is strange, since it initially affected USB ports 3 and 2. Several hours later, when I turned the machine back on, it recognized a USB memory in a USB 2 port and subsequently recognized a 500 GB HDD in a USB port 3. When I disconnected the HDD disk and reconnected a similar one into USB port 3, the system does not recognize it, the lights on the disk turn on but with the lsusb instruction it does not appear; Next I mounted the 15 GB USB memory again in USB port 2, and it was recognized, then the 500 GB HDD disk that was connected was also recognized and I was able to make a backup of 4 internal HDD disks, which are mounted automatically when turning on the computer. -- 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/2038759 Title: ubuntu does not mount usb disks Status in linux package in Ubuntu: Confirmed Bug description: A week ago this problem appeared and was corrected by changing the cat file /sys/module/usbcore/parameters/autosuspend from 2 to -1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 8 08:15:59 2023 HibernationDevice: RESUME=UUID=b5cba8c3-2b5b-4e92-8409-cb3f5249bdc5 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2021-05-23 (867 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: MSI MS-7978 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic root=UUID=8e20c169-8bb1-4137-9a73-42655ef53e43 ro acpi_enforce_resources=lax quiet libata.noacpi=1 quiet splash usbcore.autosuspend=-1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-86-generic N/A linux-backports-modules-5.15.0-86-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.19 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 08:16:20.065: The udisks-daemon is running (name-owner :1.6). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.G0 dmi.board.asset.tag: Default string dmi.board.name: B150A GAMING PRO (MS-7978) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.G0:bd07/04/2018:br5.12:svnMSI:pnMS-7978:pvr1.0:rvnMSI:rnB150AGAMINGPRO(MS-7978):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7978 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2038765
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038765
Title:
df: /sys/firmware/efi/efivars: Invalid argument causes installation
crash
Status in linux package in Ubuntu:
Confirmed
Bug description:
df: /sys/firmware/efi/efivars: Invalid argument appears on first
display of the live session - I note subsequently that at the end of
the installation curtin fails due to an efivars error - looking at
syslog I saw various efivars errors so I'm filing this with the kernel
since this is the first instance.
i.e. running grep efivars /var/log/*
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber
/dev/snd/seq:ubuntu-budgie 2074 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CasperVersion: 1.486
CurrentDesktop: Budgie:GNOME
Date: Sun Oct 8 16:27:29 2023
LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64
(20231008.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-7-generic N/A
linux-backports-modules-6.5.0-7-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038765/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash
** Description changed:
df: /sys/firmware/efi/efivars: Invalid argument appears on first display
- of the installer - I note that at the end of the installation curtin
- fails due to an efivars error - looking at syslog I saw various efivars
- errors so I'm filing this with the kernel since this is the first
- instance.
+ of the live session - I note subsequently that at the end of the
+ installation curtin fails due to an efivars error - looking at syslog I
+ saw various efivars errors so I'm filing this with the kernel since this
+ is the first instance.
i.e. running grep efivars /var/log/*
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber
- /dev/snd/seq:ubuntu-budgie 2074 F pipewire
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber
+ /dev/snd/seq:ubuntu-budgie 2074 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CasperVersion: 1.486
CurrentDesktop: Budgie:GNOME
Date: Sun Oct 8 16:27:29 2023
LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64
(20231008.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
- LANG=C.UTF-8
- PATH=(custom, no user)
- SHELL=/bin/bash
- TERM=xterm-256color
- XDG_RUNTIME_DIR=
+ LANG=C.UTF-8
+ PATH=(custom, no user)
+ SHELL=/bin/bash
+ TERM=xterm-256color
+ XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
- linux-restricted-modules-6.5.0-7-generic N/A
- linux-backports-modules-6.5.0-7-generic N/A
- linux-firmware 20230919.git3672ccab-0ubuntu2
+ linux-restricted-modules-6.5.0-7-generic N/A
+ linux-backports-modules-6.5.0-7-generic N/A
+ linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038765
Title:
df: /sys/firmware/efi/efivars: Invalid argument causes installation
crash
Status in linux package in Ubuntu:
Confirmed
Bug description:
df: /sys/firmware/efi/efivars: Invalid argument appears on first
display of the live session - I note subsequently that at the end of
the installation curtin fails due to an efivars error - looking at
syslog I saw various efivars errors so I'm filing this with the kernel
since this is the first instance.
i.e. running grep efivars /var/log/*
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber
/dev/snd/seq:ubuntu-budgie 2074 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CasperVersion: 1.486
CurrentDesktop: Budgie:GNOME
Date: Sun Oct 8 16:27:29 2023
LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64
(20231008.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-7-generic N/A
linux-backports-modules-6.5.0-7-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade
[Kernel-packages] [Bug 2038774] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2038774 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038774 Title: Cursor dissappears in full screen Status in linux package in Ubuntu: Incomplete Bug description: Only started recently, but not all apps. Some snap, flatpak, or deb. Snap: youtube music desktop Flatpak: Easy effects Deb: MultiViewer When in windowed mode the cursor is fine, But in full screen mode in some apps it is invisible. Ubuntu 20.04.3 LTS Kernel: 5.15.0-86 Window system: wayland Gnome: 42.9 Mesa: 23.0.4-ubuntu1~22.04.1 Cpu/gpu: AMD Kaveri A10-7800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038774] [NEW] Cursor dissappears in full screen
Public bug reported: Only started recently, but not all apps. Some snap, flatpak, or deb. Snap: youtube music desktop Flatpak: Easy effects Deb: MultiViewer When in windowed mode the cursor is fine, But in full screen mode in some apps it is invisible. Ubuntu 20.04.3 LTS Kernel: 5.15.0-86 Window system: wayland Gnome: 42.9 Mesa: 23.0.4-ubuntu1~22.04.1 Cpu/gpu: AMD Kaveri A10-7800 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038774 Title: Cursor dissappears in full screen Status in linux package in Ubuntu: New Bug description: Only started recently, but not all apps. Some snap, flatpak, or deb. Snap: youtube music desktop Flatpak: Easy effects Deb: MultiViewer When in windowed mode the cursor is fine, But in full screen mode in some apps it is invisible. Ubuntu 20.04.3 LTS Kernel: 5.15.0-86 Window system: wayland Gnome: 42.9 Mesa: 23.0.4-ubuntu1~22.04.1 Cpu/gpu: AMD Kaveri A10-7800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038775] [NEW] Cursor dissappears in full screen
Public bug reported: Only started recently, but not all apps. Some snap, flatpak, or deb. Snap: youtube music desktop Flatpak: Easy effects Deb: MultiViewer When in windowed mode the cursor is fine, But in full screen mode in some apps it is invisible. Ubuntu 20.04.3 LTS Kernel: 5.15.0-86 Window system: wayland Gnome: 42.9 Mesa: 23.0.4-ubuntu1~22.04.1 Cpu/gpu: AMD Kaveri A10-7800 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038775 Title: Cursor dissappears in full screen Status in mutter package in Ubuntu: New Bug description: Only started recently, but not all apps. Some snap, flatpak, or deb. Snap: youtube music desktop Flatpak: Easy effects Deb: MultiViewer When in windowed mode the cursor is fine, But in full screen mode in some apps it is invisible. Ubuntu 20.04.3 LTS Kernel: 5.15.0-86 Window system: wayland Gnome: 42.9 Mesa: 23.0.4-ubuntu1~22.04.1 Cpu/gpu: AMD Kaveri A10-7800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2038775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038768] Re: arm64: linux: stress-ng filename stressor crashes kernel
Can't seem to trip the issue on a 24 core x86 instance, maybe this is ARM64 specific. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038768 Title: arm64: linux: stress-ng filename stressor crashes kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Mantic: Incomplete Bug description: Running latest Ubuntu mantic (ext4 file system) with kernel: Linux mantic-arm64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux How to reproduce: Fire up a 24 instance ARM64 QEMU instance with Ubuntu Mantic Server. Install latest stress-ng from git repo: sudo apt-get update sudo apt-get build-dep stress-ng git clone git://github.com/ColinIanKing/stress-ng cd stress-ng make clean make -j 24 make verify-test-all When we reach the filename stressor the kernel crashes as follows: [ 902.594715] kernel BUG at fs/dcache.c:2050! [ 902.598205] Internal error: Oops - BUG: f2000800 [#1] SMP [ 902.603127] Modules linked in: dccp_ipv4 dccp atm vfio_iommu_type1 vfio iommu fd cmac algif_rng twofish_generic twofish_common serpent_generic fcrypt cast6_ge neric cast5_generic cast_common camellia_generic blowfish_generic blowfish_commo n aes_arm64 algif_skcipher algif_hash aria_generic sm4_generic sm4_neon ccm aes_ ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg cfg80211 binfmt_mis c nls_iso8859_1 dm_multipath drm efi_pstore dmi_sysfs qemu_fw_cfg ip_tables x_ta bles autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipa th linear crct10dif_ce polyval_ce polyval_generic ghash_ce sm4 sha2_ce sha256_ar m64 sha1_ce arm_smccc_trng xhci_pci virtio_rng xhci_pci_renesas aes_neon_bs aes_ neon_blk aes_ce_blk aes_ce_cipher [ 902.689941] CPU: 1 PID: 91317 Comm: stress-ng-filen Not tainted 6.5.0-7-gener ic #7-Ubuntu [ 902.699281] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 902.706902] pstate: 4045 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 902.715488] pc : d_instantiate_new+0xa8/0xc8 [ 902.720889] lr : ext4_add_nondir+0x10c/0x160 [ 902.725702] sp : 80008b6d3930 [ 902.729390] x29: 80008b6d3930 x28: x27: bd164e51a980 [ 902.738705] x26: 6789f3b68f20 x25: 8180 x24: 678a541f7968 [ 902.747003] x23: 6789f3b68f00 x22: 80008b6d39b0 x21: 678a6a25bcb0 [ 902.755776] x20: 678a36f8f028 x19: x18: 80008af45068 [ 902.764647] x17: x16: x15: ecececececececec [ 902.773135] x14: ecececececececec x13: ecececececececec x12: ecececececececec [ 902.781386] x11: ecececececececec x10: ecececececececec x9 : bd164d5990bc [ 902.789346] x8 : x7 : x6 : [ 902.798564] x5 : x4 : x3 : [ 902.806851] x2 : bd16504e4ce0 x1 : 678a36f8f028 x0 : 6789f3b68f00 [ 902.815544] Call trace: [ 902.818870] d_instantiate_new+0xa8/0xc8 [ 902.823523] ext4_create+0x120/0x238 [ 902.827716] lookup_open.isra.0+0x480/0x4d0 [ 902.832480] open_last_lookups+0x160/0x3b0 [ 902.837060] path_openat+0xa0/0x2a0 [ 902.840975] do_filp_open+0xa8/0x180 [ 902.845582] do_sys_openat2+0xe8/0x128 [ 902.850426] __arm64_sys_openat+0x70/0xe0 [ 902.854952] invoke_syscall+0x7c/0x128 [ 902.859155] el0_svc_common.constprop.0+0x5c/0x168 [ 902.864979] do_el0_svc+0x38/0x68 [ 902.869364] el0_svc+0x30/0xe0 [ 902.873401] el0t_64_sync_handler+0x148/0x158 [ 902.878336] el0t_64_sync+0x1b0/0x1b8 [ 902.882513] Code: d282 d2800010 d2800011 d65f03c0 (d421) [ 902.890632] ---[ end trace ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038768] Re: arm64: linux: stress-ng filename stressor crashes kernel
** Also affects: linux (Ubuntu Mantic) Importance: High Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038768 Title: arm64: linux: stress-ng filename stressor crashes kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Mantic: Incomplete Bug description: Running latest Ubuntu mantic (ext4 file system) with kernel: Linux mantic-arm64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux How to reproduce: Fire up a 24 instance ARM64 QEMU instance with Ubuntu Mantic Server. Install latest stress-ng from git repo: sudo apt-get update sudo apt-get build-dep stress-ng git clone git://github.com/ColinIanKing/stress-ng cd stress-ng make clean make -j 24 make verify-test-all When we reach the filename stressor the kernel crashes as follows: [ 902.594715] kernel BUG at fs/dcache.c:2050! [ 902.598205] Internal error: Oops - BUG: f2000800 [#1] SMP [ 902.603127] Modules linked in: dccp_ipv4 dccp atm vfio_iommu_type1 vfio iommu fd cmac algif_rng twofish_generic twofish_common serpent_generic fcrypt cast6_ge neric cast5_generic cast_common camellia_generic blowfish_generic blowfish_commo n aes_arm64 algif_skcipher algif_hash aria_generic sm4_generic sm4_neon ccm aes_ ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg cfg80211 binfmt_mis c nls_iso8859_1 dm_multipath drm efi_pstore dmi_sysfs qemu_fw_cfg ip_tables x_ta bles autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipa th linear crct10dif_ce polyval_ce polyval_generic ghash_ce sm4 sha2_ce sha256_ar m64 sha1_ce arm_smccc_trng xhci_pci virtio_rng xhci_pci_renesas aes_neon_bs aes_ neon_blk aes_ce_blk aes_ce_cipher [ 902.689941] CPU: 1 PID: 91317 Comm: stress-ng-filen Not tainted 6.5.0-7-gener ic #7-Ubuntu [ 902.699281] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 902.706902] pstate: 4045 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 902.715488] pc : d_instantiate_new+0xa8/0xc8 [ 902.720889] lr : ext4_add_nondir+0x10c/0x160 [ 902.725702] sp : 80008b6d3930 [ 902.729390] x29: 80008b6d3930 x28: x27: bd164e51a980 [ 902.738705] x26: 6789f3b68f20 x25: 8180 x24: 678a541f7968 [ 902.747003] x23: 6789f3b68f00 x22: 80008b6d39b0 x21: 678a6a25bcb0 [ 902.755776] x20: 678a36f8f028 x19: x18: 80008af45068 [ 902.764647] x17: x16: x15: ecececececececec [ 902.773135] x14: ecececececececec x13: ecececececececec x12: ecececececececec [ 902.781386] x11: ecececececececec x10: ecececececececec x9 : bd164d5990bc [ 902.789346] x8 : x7 : x6 : [ 902.798564] x5 : x4 : x3 : [ 902.806851] x2 : bd16504e4ce0 x1 : 678a36f8f028 x0 : 6789f3b68f00 [ 902.815544] Call trace: [ 902.818870] d_instantiate_new+0xa8/0xc8 [ 902.823523] ext4_create+0x120/0x238 [ 902.827716] lookup_open.isra.0+0x480/0x4d0 [ 902.832480] open_last_lookups+0x160/0x3b0 [ 902.837060] path_openat+0xa0/0x2a0 [ 902.840975] do_filp_open+0xa8/0x180 [ 902.845582] do_sys_openat2+0xe8/0x128 [ 902.850426] __arm64_sys_openat+0x70/0xe0 [ 902.854952] invoke_syscall+0x7c/0x128 [ 902.859155] el0_svc_common.constprop.0+0x5c/0x168 [ 902.864979] do_el0_svc+0x38/0x68 [ 902.869364] el0_svc+0x30/0xe0 [ 902.873401] el0t_64_sync_handler+0x148/0x158 [ 902.878336] el0t_64_sync+0x1b0/0x1b8 [ 902.882513] Code: d282 d2800010 d2800011 d65f03c0 (d421) [ 902.890632] ---[ end trace ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-nvidia-tegra/5.15.0.1018.18)
All autopkgtests for the newly accepted linux-meta-nvidia-tegra (5.15.0.1018.18) for jammy have finished running. The following regressions have been reported in tests triggered by the package: wireguard/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-nvidia-tegra [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038768] Re: arm64: linux: stress-ng filename stressor crashes kernel
I created a 1GB file and created a fresh ext4 file system on it and loop back mounted it on /mnt, I created test directory /mnt/test and ran: /stress-ng --filename 0 --temp-path /mnt/test --klog-check Managed to trip the kernel crash again. So it appears to occur on a fresh ext4 file system too :-( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038768 Title: arm64: linux: stress-ng filename stressor crashes kernel Status in linux package in Ubuntu: Incomplete Bug description: Running latest Ubuntu mantic (ext4 file system) with kernel: Linux mantic-arm64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux How to reproduce: Fire up a 24 instance ARM64 QEMU instance with Ubuntu Mantic Server. Install latest stress-ng from git repo: sudo apt-get update sudo apt-get build-dep stress-ng git clone git://github.com/ColinIanKing/stress-ng cd stress-ng make clean make -j 24 make verify-test-all When we reach the filename stressor the kernel crashes as follows: [ 902.594715] kernel BUG at fs/dcache.c:2050! [ 902.598205] Internal error: Oops - BUG: f2000800 [#1] SMP [ 902.603127] Modules linked in: dccp_ipv4 dccp atm vfio_iommu_type1 vfio iommu fd cmac algif_rng twofish_generic twofish_common serpent_generic fcrypt cast6_ge neric cast5_generic cast_common camellia_generic blowfish_generic blowfish_commo n aes_arm64 algif_skcipher algif_hash aria_generic sm4_generic sm4_neon ccm aes_ ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg cfg80211 binfmt_mis c nls_iso8859_1 dm_multipath drm efi_pstore dmi_sysfs qemu_fw_cfg ip_tables x_ta bles autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipa th linear crct10dif_ce polyval_ce polyval_generic ghash_ce sm4 sha2_ce sha256_ar m64 sha1_ce arm_smccc_trng xhci_pci virtio_rng xhci_pci_renesas aes_neon_bs aes_ neon_blk aes_ce_blk aes_ce_cipher [ 902.689941] CPU: 1 PID: 91317 Comm: stress-ng-filen Not tainted 6.5.0-7-gener ic #7-Ubuntu [ 902.699281] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 902.706902] pstate: 4045 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 902.715488] pc : d_instantiate_new+0xa8/0xc8 [ 902.720889] lr : ext4_add_nondir+0x10c/0x160 [ 902.725702] sp : 80008b6d3930 [ 902.729390] x29: 80008b6d3930 x28: x27: bd164e51a980 [ 902.738705] x26: 6789f3b68f20 x25: 8180 x24: 678a541f7968 [ 902.747003] x23: 6789f3b68f00 x22: 80008b6d39b0 x21: 678a6a25bcb0 [ 902.755776] x20: 678a36f8f028 x19: x18: 80008af45068 [ 902.764647] x17: x16: x15: ecececececececec [ 902.773135] x14: ecececececececec x13: ecececececececec x12: ecececececececec [ 902.781386] x11: ecececececececec x10: ecececececececec x9 : bd164d5990bc [ 902.789346] x8 : x7 : x6 : [ 902.798564] x5 : x4 : x3 : [ 902.806851] x2 : bd16504e4ce0 x1 : 678a36f8f028 x0 : 6789f3b68f00 [ 902.815544] Call trace: [ 902.818870] d_instantiate_new+0xa8/0xc8 [ 902.823523] ext4_create+0x120/0x238 [ 902.827716] lookup_open.isra.0+0x480/0x4d0 [ 902.832480] open_last_lookups+0x160/0x3b0 [ 902.837060] path_openat+0xa0/0x2a0 [ 902.840975] do_filp_open+0xa8/0x180 [ 902.845582] do_sys_openat2+0xe8/0x128 [ 902.850426] __arm64_sys_openat+0x70/0xe0 [ 902.854952] invoke_syscall+0x7c/0x128 [ 902.859155] el0_svc_common.constprop.0+0x5c/0x168 [ 902.864979] do_el0_svc+0x38/0x68 [ 902.869364] el0_svc+0x30/0xe0 [ 902.873401] el0t_64_sync_handler+0x148/0x158 [ 902.878336] el0t_64_sync+0x1b0/0x1b8 [ 902.882513] Code: d282 d2800010 d2800011 d65f03c0 (d421) [ 902.890632] ---[ end trace ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038768] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2038768 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038768 Title: arm64: linux: stress-ng filename stressor crashes kernel Status in linux package in Ubuntu: Incomplete Bug description: Running latest Ubuntu mantic (ext4 file system) with kernel: Linux mantic-arm64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux How to reproduce: Fire up a 24 instance ARM64 QEMU instance with Ubuntu Mantic Server. Install latest stress-ng from git repo: sudo apt-get update sudo apt-get build-dep stress-ng git clone git://github.com/ColinIanKing/stress-ng cd stress-ng make clean make -j 24 make verify-test-all When we reach the filename stressor the kernel crashes as follows: [ 902.594715] kernel BUG at fs/dcache.c:2050! [ 902.598205] Internal error: Oops - BUG: f2000800 [#1] SMP [ 902.603127] Modules linked in: dccp_ipv4 dccp atm vfio_iommu_type1 vfio iommu fd cmac algif_rng twofish_generic twofish_common serpent_generic fcrypt cast6_ge neric cast5_generic cast_common camellia_generic blowfish_generic blowfish_commo n aes_arm64 algif_skcipher algif_hash aria_generic sm4_generic sm4_neon ccm aes_ ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg cfg80211 binfmt_mis c nls_iso8859_1 dm_multipath drm efi_pstore dmi_sysfs qemu_fw_cfg ip_tables x_ta bles autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipa th linear crct10dif_ce polyval_ce polyval_generic ghash_ce sm4 sha2_ce sha256_ar m64 sha1_ce arm_smccc_trng xhci_pci virtio_rng xhci_pci_renesas aes_neon_bs aes_ neon_blk aes_ce_blk aes_ce_cipher [ 902.689941] CPU: 1 PID: 91317 Comm: stress-ng-filen Not tainted 6.5.0-7-gener ic #7-Ubuntu [ 902.699281] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 902.706902] pstate: 4045 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 902.715488] pc : d_instantiate_new+0xa8/0xc8 [ 902.720889] lr : ext4_add_nondir+0x10c/0x160 [ 902.725702] sp : 80008b6d3930 [ 902.729390] x29: 80008b6d3930 x28: x27: bd164e51a980 [ 902.738705] x26: 6789f3b68f20 x25: 8180 x24: 678a541f7968 [ 902.747003] x23: 6789f3b68f00 x22: 80008b6d39b0 x21: 678a6a25bcb0 [ 902.755776] x20: 678a36f8f028 x19: x18: 80008af45068 [ 902.764647] x17: x16: x15: ecececececececec [ 902.773135] x14: ecececececececec x13: ecececececececec x12: ecececececececec [ 902.781386] x11: ecececececececec x10: ecececececececec x9 : bd164d5990bc [ 902.789346] x8 : x7 : x6 : [ 902.798564] x5 : x4 : x3 : [ 902.806851] x2 : bd16504e4ce0 x1 : 678a36f8f028 x0 : 6789f3b68f00 [ 902.815544] Call trace: [ 902.818870] d_instantiate_new+0xa8/0xc8 [ 902.823523] ext4_create+0x120/0x238 [ 902.827716] lookup_open.isra.0+0x480/0x4d0 [ 902.832480] open_last_lookups+0x160/0x3b0 [ 902.837060] path_openat+0xa0/0x2a0 [ 902.840975] do_filp_open+0xa8/0x180 [ 902.845582] do_sys_openat2+0xe8/0x128 [ 902.850426] __arm64_sys_openat+0x70/0xe0 [ 902.854952] invoke_syscall+0x7c/0x128 [ 902.859155] el0_svc_common.constprop.0+0x5c/0x168 [ 902.864979] do_el0_svc+0x38/0x68 [ 902.869364] el0_svc+0x30/0xe0 [ 902.873401] el0t_64_sync_handler+0x148/0x158 [ 902.878336] el0t_64_sync+0x1b0/0x1b8 [ 902.882513] Code: d282 d2800010 d2800011 d65f03c0 (d421) [ 902.890632] ---[ end trace ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038768] [NEW] arm64: linux: stress-ng filename stressor crashes kernel
Public bug reported: Running latest Ubuntu mantic (ext4 file system) with kernel: Linux mantic-arm64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux How to reproduce: Fire up a 24 instance ARM64 QEMU instance with Ubuntu Mantic Server. Install latest stress-ng from git repo: sudo apt-get update sudo apt-get build-dep stress-ng git clone git://github.com/ColinIanKing/stress-ng cd stress-ng make clean make -j 24 make verify-test-all When we reach the filename stressor the kernel crashes as follows: [ 902.594715] kernel BUG at fs/dcache.c:2050! [ 902.598205] Internal error: Oops - BUG: f2000800 [#1] SMP [ 902.603127] Modules linked in: dccp_ipv4 dccp atm vfio_iommu_type1 vfio iommu fd cmac algif_rng twofish_generic twofish_common serpent_generic fcrypt cast6_ge neric cast5_generic cast_common camellia_generic blowfish_generic blowfish_commo n aes_arm64 algif_skcipher algif_hash aria_generic sm4_generic sm4_neon ccm aes_ ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg cfg80211 binfmt_mis c nls_iso8859_1 dm_multipath drm efi_pstore dmi_sysfs qemu_fw_cfg ip_tables x_ta bles autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipa th linear crct10dif_ce polyval_ce polyval_generic ghash_ce sm4 sha2_ce sha256_ar m64 sha1_ce arm_smccc_trng xhci_pci virtio_rng xhci_pci_renesas aes_neon_bs aes_ neon_blk aes_ce_blk aes_ce_cipher [ 902.689941] CPU: 1 PID: 91317 Comm: stress-ng-filen Not tainted 6.5.0-7-gener ic #7-Ubuntu [ 902.699281] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 902.706902] pstate: 4045 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 902.715488] pc : d_instantiate_new+0xa8/0xc8 [ 902.720889] lr : ext4_add_nondir+0x10c/0x160 [ 902.725702] sp : 80008b6d3930 [ 902.729390] x29: 80008b6d3930 x28: x27: bd164e51a980 [ 902.738705] x26: 6789f3b68f20 x25: 8180 x24: 678a541f7968 [ 902.747003] x23: 6789f3b68f00 x22: 80008b6d39b0 x21: 678a6a25bcb0 [ 902.755776] x20: 678a36f8f028 x19: x18: 80008af45068 [ 902.764647] x17: x16: x15: ecececececececec [ 902.773135] x14: ecececececececec x13: ecececececececec x12: ecececececececec [ 902.781386] x11: ecececececececec x10: ecececececececec x9 : bd164d5990bc [ 902.789346] x8 : x7 : x6 : [ 902.798564] x5 : x4 : x3 : [ 902.806851] x2 : bd16504e4ce0 x1 : 678a36f8f028 x0 : 6789f3b68f00 [ 902.815544] Call trace: [ 902.818870] d_instantiate_new+0xa8/0xc8 [ 902.823523] ext4_create+0x120/0x238 [ 902.827716] lookup_open.isra.0+0x480/0x4d0 [ 902.832480] open_last_lookups+0x160/0x3b0 [ 902.837060] path_openat+0xa0/0x2a0 [ 902.840975] do_filp_open+0xa8/0x180 [ 902.845582] do_sys_openat2+0xe8/0x128 [ 902.850426] __arm64_sys_openat+0x70/0xe0 [ 902.854952] invoke_syscall+0x7c/0x128 [ 902.859155] el0_svc_common.constprop.0+0x5c/0x168 [ 902.864979] do_el0_svc+0x38/0x68 [ 902.869364] el0_svc+0x30/0xe0 [ 902.873401] el0t_64_sync_handler+0x148/0x158 [ 902.878336] el0t_64_sync+0x1b0/0x1b8 [ 902.882513] Code: d282 d2800010 d2800011 d65f03c0 (d421) [ 902.890632] ---[ end trace ]--- ** Affects: linux (Ubuntu) Importance: High Status: Incomplete ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Description changed: Running latest Ubuntu mantic with kernel: Linux mantic-arm64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux - How to reproduce: Fire up a 24 instance ARM64 QEMU instance with Ubuntu Mantic Server. Install latest stress-ng from git repo: sudo apt-get update sudo apt-get build-dep stress-ng git clone git://github.com/ColinIanKing/stress-ng cd stress-ng make clean make -j 24 make verify-test-all When we reach the filename stressor the kernel crashes as follows: - [ 902.594715] kernel BUG at fs/dcache.c:2050! [ 902.598205] Internal error: Oops - BUG: f2000800 [#1] SMP [ 902.603127] Modules linked in: dccp_ipv4 dccp atm vfio_iommu_type1 vfio iommu fd cmac algif_rng twofish_generic twofish_common serpent_generic fcrypt cast6_ge neric cast5_generic cast_common camellia_generic blowfish_generic blowfish_commo n aes_arm64 algif_skcipher algif_hash aria_generic sm4_generic sm4_neon ccm aes_ ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg cfg80211 binfmt_mis c nls_iso8859_1 dm_multipath drm efi_pstore dmi_sysfs qemu_fw_cfg ip_tables x_ta bles autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy - async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0
[Kernel-packages] [Bug 2038768] Re: arm64: linux: stress-ng filename stressor crashes kernel
Note that just running stress-ng with --filename 0 will reproduce the issue. I'm testing this now on a cleanly formatted ext4 file system -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038768 Title: arm64: linux: stress-ng filename stressor crashes kernel Status in linux package in Ubuntu: Incomplete Bug description: Running latest Ubuntu mantic (ext4 file system) with kernel: Linux mantic-arm64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux How to reproduce: Fire up a 24 instance ARM64 QEMU instance with Ubuntu Mantic Server. Install latest stress-ng from git repo: sudo apt-get update sudo apt-get build-dep stress-ng git clone git://github.com/ColinIanKing/stress-ng cd stress-ng make clean make -j 24 make verify-test-all When we reach the filename stressor the kernel crashes as follows: [ 902.594715] kernel BUG at fs/dcache.c:2050! [ 902.598205] Internal error: Oops - BUG: f2000800 [#1] SMP [ 902.603127] Modules linked in: dccp_ipv4 dccp atm vfio_iommu_type1 vfio iommu fd cmac algif_rng twofish_generic twofish_common serpent_generic fcrypt cast6_ge neric cast5_generic cast_common camellia_generic blowfish_generic blowfish_commo n aes_arm64 algif_skcipher algif_hash aria_generic sm4_generic sm4_neon ccm aes_ ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg cfg80211 binfmt_mis c nls_iso8859_1 dm_multipath drm efi_pstore dmi_sysfs qemu_fw_cfg ip_tables x_ta bles autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipa th linear crct10dif_ce polyval_ce polyval_generic ghash_ce sm4 sha2_ce sha256_ar m64 sha1_ce arm_smccc_trng xhci_pci virtio_rng xhci_pci_renesas aes_neon_bs aes_ neon_blk aes_ce_blk aes_ce_cipher [ 902.689941] CPU: 1 PID: 91317 Comm: stress-ng-filen Not tainted 6.5.0-7-gener ic #7-Ubuntu [ 902.699281] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 902.706902] pstate: 4045 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 902.715488] pc : d_instantiate_new+0xa8/0xc8 [ 902.720889] lr : ext4_add_nondir+0x10c/0x160 [ 902.725702] sp : 80008b6d3930 [ 902.729390] x29: 80008b6d3930 x28: x27: bd164e51a980 [ 902.738705] x26: 6789f3b68f20 x25: 8180 x24: 678a541f7968 [ 902.747003] x23: 6789f3b68f00 x22: 80008b6d39b0 x21: 678a6a25bcb0 [ 902.755776] x20: 678a36f8f028 x19: x18: 80008af45068 [ 902.764647] x17: x16: x15: ecececececececec [ 902.773135] x14: ecececececececec x13: ecececececececec x12: ecececececececec [ 902.781386] x11: ecececececececec x10: ecececececececec x9 : bd164d5990bc [ 902.789346] x8 : x7 : x6 : [ 902.798564] x5 : x4 : x3 : [ 902.806851] x2 : bd16504e4ce0 x1 : 678a36f8f028 x0 : 6789f3b68f00 [ 902.815544] Call trace: [ 902.818870] d_instantiate_new+0xa8/0xc8 [ 902.823523] ext4_create+0x120/0x238 [ 902.827716] lookup_open.isra.0+0x480/0x4d0 [ 902.832480] open_last_lookups+0x160/0x3b0 [ 902.837060] path_openat+0xa0/0x2a0 [ 902.840975] do_filp_open+0xa8/0x180 [ 902.845582] do_sys_openat2+0xe8/0x128 [ 902.850426] __arm64_sys_openat+0x70/0xe0 [ 902.854952] invoke_syscall+0x7c/0x128 [ 902.859155] el0_svc_common.constprop.0+0x5c/0x168 [ 902.864979] do_el0_svc+0x38/0x68 [ 902.869364] el0_svc+0x30/0xe0 [ 902.873401] el0t_64_sync_handler+0x148/0x158 [ 902.878336] el0t_64_sync+0x1b0/0x1b8 [ 902.882513] Code: d282 d2800010 d2800011 d65f03c0 (d421) [ 902.890632] ---[ end trace ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038765] Status changed to Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038765
Title:
df: /sys/firmware/efi/efivars: Invalid argument causes installation
crash
Status in linux package in Ubuntu:
Confirmed
Bug description:
df: /sys/firmware/efi/efivars: Invalid argument appears on first
display of the installer - I note that at the end of the installation
curtin fails due to an efivars error - looking at syslog I saw various
efivars errors so I'm filing this with the kernel since this is the
first instance.
i.e. running grep efivars /var/log/*
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber
/dev/snd/seq:ubuntu-budgie 2074 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CasperVersion: 1.486
CurrentDesktop: Budgie:GNOME
Date: Sun Oct 8 16:27:29 2023
LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64
(20231008.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-7-generic N/A
linux-backports-modules-6.5.0-7-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038765/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038765/+attachment/5707866/+files/syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038765
Title:
df: /sys/firmware/efi/efivars: Invalid argument causes installation
crash
Status in linux package in Ubuntu:
New
Bug description:
df: /sys/firmware/efi/efivars: Invalid argument appears on first
display of the installer - I note that at the end of the installation
curtin fails due to an efivars error - looking at syslog I saw various
efivars errors so I'm filing this with the kernel since this is the
first instance.
i.e. running grep efivars /var/log/*
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber
/dev/snd/seq:ubuntu-budgie 2074 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CasperVersion: 1.486
CurrentDesktop: Budgie:GNOME
Date: Sun Oct 8 16:27:29 2023
LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64
(20231008.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-7-generic N/A
linux-backports-modules-6.5.0-7-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038765/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038765] [NEW] df: /sys/firmware/efi/efivars: Invalid argument causes installation crash
Public bug reported:
df: /sys/firmware/efi/efivars: Invalid argument appears on first display
of the installer - I note that at the end of the installation curtin
fails due to an efivars error - looking at syslog I saw various efivars
errors so I'm filing this with the kernel since this is the first
instance.
i.e. running grep efivars /var/log/*
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber
/dev/snd/seq:ubuntu-budgie 2074 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CasperVersion: 1.486
CurrentDesktop: Budgie:GNOME
Date: Sun Oct 8 16:27:29 2023
LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 (20231008.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-7-generic N/A
linux-backports-modules-6.5.0-7-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038765
Title:
df: /sys/firmware/efi/efivars: Invalid argument causes installation
crash
Status in linux package in Ubuntu:
New
Bug description:
df: /sys/firmware/efi/efivars: Invalid argument appears on first
display of the installer - I note that at the end of the installation
curtin fails due to an efivars error - looking at syslog I saw various
efivars errors so I'm filing this with the kernel since this is the
first instance.
i.e. running grep efivars /var/log/*
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber
/dev/snd/seq:ubuntu-budgie 2074 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CasperVersion: 1.486
CurrentDesktop: Budgie:GNOME
Date: Sun Oct 8 16:27:29 2023
LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64
(20231008.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-7-generic N/A
linux-backports-modules-6.5.0-7-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
dmi.product.family: MacBook Pro
dmi.product.name:
[Kernel-packages] [Bug 2031969] Re: Ubuntu 23.04: Suspend & Power off
Sorry, but that was a kind request, very respectful. Not with a single word I did imply any malicious intent. How respectful is this treatment of other people's wording? Anyway, it just doesn't make sense to mix these things up, as mentioned earlier. Even if it will end up with the same cause, a bug in a certain 6.x kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2031969 Title: Ubuntu 23.04: Suspend & Power off Status in linux package in Ubuntu: Confirmed Bug description: Since update to version 23.04 I am facing several problems related to system suspend and shutdownon a HP Envy 15 notebook (2016). The system refuses to wake up from standby mode, especially if it has run for a longer time. Screen is black, no response to keyboard or trackpad actions, power button led is on. The only way out of here is a long press on the power button. Another problem with this and I think it's kind of related. If you want to shut down the computer after a long runtime, the machine won't power off. In the logs you can see the steps for shutting down the OS, but sometimes the machine stays powered on. The power led is on, screen is black, no response to keyboard or trackpad actions. System has to be powered off by a long press on the power button. Ubuntu 6.2.0-27.28-generic 6.2.15 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom2051 F wireplumber /dev/snd/seq:tom2037 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 19 16:01:07 2023 InstallationDate: Installed on 2018-07-01 (1875 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-27-generic N/A linux-backports-modules-6.2.0-27-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-05-01 (109 days ago) dmi.bios.date: 11/10/2020 dmi.bios.release: 15.62 dmi.bios.vendor: Insyde dmi.bios.version: F.62 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81D2 dmi.board.vendor: HP dmi.board.version: KBC Version 87.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.21 dmi.modalias: dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY Notebook dmi.product.sku: Z6J78EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038759] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038759 Title: ubuntu does not mount usb disks Status in linux package in Ubuntu: Confirmed Bug description: A week ago this problem appeared and was corrected by changing the cat file /sys/module/usbcore/parameters/autosuspend from 2 to -1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 8 08:15:59 2023 HibernationDevice: RESUME=UUID=b5cba8c3-2b5b-4e92-8409-cb3f5249bdc5 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2021-05-23 (867 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: MSI MS-7978 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic root=UUID=8e20c169-8bb1-4137-9a73-42655ef53e43 ro acpi_enforce_resources=lax quiet libata.noacpi=1 quiet splash usbcore.autosuspend=-1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-86-generic N/A linux-backports-modules-5.15.0-86-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.19 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 08:16:20.065: The udisks-daemon is running (name-owner :1.6). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.G0 dmi.board.asset.tag: Default string dmi.board.name: B150A GAMING PRO (MS-7978) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.G0:bd07/04/2018:br5.12:svnMSI:pnMS-7978:pvr1.0:rvnMSI:rnB150AGAMINGPRO(MS-7978):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7978 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038759] [NEW] ubuntu does not mount usb disks
Public bug reported: A week ago this problem appeared and was corrected by changing the cat file /sys/module/usbcore/parameters/autosuspend from 2 to -1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 8 08:15:59 2023 HibernationDevice: RESUME=UUID=b5cba8c3-2b5b-4e92-8409-cb3f5249bdc5 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2021-05-23 (867 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: MSI MS-7978 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic root=UUID=8e20c169-8bb1-4137-9a73-42655ef53e43 ro acpi_enforce_resources=lax quiet libata.noacpi=1 quiet splash usbcore.autosuspend=-1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-86-generic N/A linux-backports-modules-5.15.0-86-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.19 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 08:16:20.065: The udisks-daemon is running (name-owner :1.6). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.G0 dmi.board.asset.tag: Default string dmi.board.name: B150A GAMING PRO (MS-7978) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.G0:bd07/04/2018:br5.12:svnMSI:pnMS-7978:pvr1.0:rvnMSI:rnB150AGAMINGPRO(MS-7978):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7978 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038759 Title: ubuntu does not mount usb disks Status in linux package in Ubuntu: Confirmed Bug description: A week ago this problem appeared and was corrected by changing the cat file /sys/module/usbcore/parameters/autosuspend from 2 to -1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 8 08:15:59 2023 HibernationDevice: RESUME=UUID=b5cba8c3-2b5b-4e92-8409-cb3f5249bdc5 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2021-05-23 (867 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: MSI MS-7978 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic root=UUID=8e20c169-8bb1-4137-9a73-42655ef53e43 ro acpi_enforce_resources=lax quiet libata.noacpi=1 quiet splash usbcore.autosuspend=-1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-86-generic N/A linux-backports-modules-5.15.0-86-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.19 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 08:16:20.065: The udisks-daemon is running (name-owner :1.6). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.G0 dmi.board.asset.tag: Default string dmi.board.name: B150A GAMING PRO (MS-7978) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor:
[Kernel-packages] [Bug 2019868] Re: ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. 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-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019868 Title: ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: These failures happen on all supported architectures, when fips=1. When fips=0, all test cases pass. The results are shown below: make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/src/linux' TAP version 13 1..1 # selftests: net: tls # TAP version 13 # 1..179 # # Starting 179 tests from 6 test cases. # # RUN global.non_established ... # #OK global.non_established # ok 1 global.non_established # # RUN global.keysizes ... # #OK global.keysizes # ok 2 global.keysizes # # RUN tls_basic.base_base ... # #OK tls_basic.base_base # ok 3 tls_basic.base_base # # RUN tls.12_gcm.sendfile ... # #OK tls.12_gcm.sendfile # ok 4 tls.12_gcm.sendfile # # RUN tls.12_gcm.send_then_sendfile ... # #OK tls.12_gcm.send_then_sendfile # ok 5 tls.12_gcm.send_then_sendfile # # RUN tls.12_gcm.recv_max ... # #OK tls.12_gcm.recv_max # ok 6 tls.12_gcm.recv_max # # RUN tls.12_gcm.recv_small ... # #OK tls.12_gcm.recv_small # ok 7 tls.12_gcm.recv_small # # RUN tls.12_gcm.msg_more ... # #OK tls.12_gcm.msg_more # ok 8 tls.12_gcm.msg_more # # RUN tls.12_gcm.msg_more_unsent ... # #OK tls.12_gcm.msg_more_unsent # ok 9 tls.12_gcm.msg_more_unsent # # RUN tls.12_gcm.sendmsg_single ... # #OK tls.12_gcm.sendmsg_single # ok 10 tls.12_gcm.sendmsg_single # # RUN tls.12_gcm.sendmsg_fragmented ... # #OK tls.12_gcm.sendmsg_fragmented # ok 11 tls.12_gcm.sendmsg_fragmented # # RUN tls.12_gcm.sendmsg_large ... # #OK tls.12_gcm.sendmsg_large # ok 12 tls.12_gcm.sendmsg_large # # RUN tls.12_gcm.sendmsg_multiple ... # #OK tls.12_gcm.sendmsg_multiple # ok 13 tls.12_gcm.sendmsg_multiple # # RUN tls.12_gcm.sendmsg_multiple_stress ... # #OK tls.12_gcm.sendmsg_multiple_stress # ok 14 tls.12_gcm.sendmsg_multiple_stress # # RUN tls.12_gcm.splice_from_pipe ... # #OK tls.12_gcm.splice_from_pipe # ok 15 tls.12_gcm.splice_from_pipe # # RUN tls.12_gcm.splice_from_pipe2 ... # #OK tls.12_gcm.splice_from_pipe2 # ok 16 tls.12_gcm.splice_from_pipe2 # # RUN tls.12_gcm.send_and_splice ... # #OK tls.12_gcm.send_and_splice # ok 17 tls.12_gcm.send_and_splice # # RUN tls.12_gcm.splice_to_pipe ... # #OK tls.12_gcm.splice_to_pipe # ok 18 tls.12_gcm.splice_to_pipe # # RUN tls.12_gcm.recvmsg_single ... # #OK tls.12_gcm.recvmsg_single # ok 19 tls.12_gcm.recvmsg_single # # RUN tls.12_gcm.recvmsg_single_max ... # #OK tls.12_gcm.recvmsg_single_max # ok 20 tls.12_gcm.recvmsg_single_max # # RUN tls.12_gcm.recvmsg_multiple ... # #OK tls.12_gcm.recvmsg_multiple # ok 21 tls.12_gcm.recvmsg_multiple # # RUN tls.12_gcm.single_send_multiple_recv ... # #OK tls.12_gcm.single_send_multiple_recv # ok 22 tls.12_gcm.single_send_multiple_recv # # RUN tls.12_gcm.multiple_send_single_recv ... # #OK tls.12_gcm.multiple_send_single_recv # ok 23 tls.12_gcm.multiple_send_single_recv # # RUN tls.12_gcm.single_send_multiple_recv_non_align ... # #OK
[Kernel-packages] [Bug 2019880] Re: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. 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-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019880 Title: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: These failures happen on all supported architectures, when fips=1. When fips=0, all test cases pass. Results are shown below: make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/src/linux' TAP version 13 1..1 # selftests: net: vrf-xfrm-tests.sh # # No qdisc on VRF device # TEST: IPv4 no xfrm policy [ OK ] # TEST: IPv6 no xfrm policy [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy with VRF in selector [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy with xfrm device [FAIL] # TEST: IPv6 xfrm policy with xfrm device [FAIL] # # netem qdisc on VRF device # TEST: IPv4 no xfrm policy [ OK ] # TEST: IPv6 no xfrm policy [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy with VRF in selector [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy with xfrm device [FAIL] # TEST: IPv6 xfrm policy with xfrm device [FAIL] # # Tests passed: 6 # Tests failed: 8 not ok 1 selftests: net: vrf-xfrm-tests.sh # exit=1 make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2019880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022361] Re: Please enable Renesas RZ platform serial installer
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.
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-v2
verification-needed-jammy-linux-nvidia-tegra
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2022361
Title:
Please enable Renesas RZ platform serial installer
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
The ubuntu installer does not work via serial ports for Renesas boards like
RZ/G2M-HiHope
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).
The installation can be done using HDMI ports, but it would be nice to
support installation via serial port as well.
[Test case]
Try to install Ubuntu on a Renesas board.
[Fix]
Statically build SuperH SCI(F) serial port support (with
earlyconsole).
[Regression potential]
Statically building an additional driver in the kernel can make the
kernel image bigger, potentially causing boot issues in small (arm64 /
armhf) platforms.
[Original bug report]
Package: linux
Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028122] Re: Fix unreliable ethernet cable detection on I219 NIC
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. 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-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2028122 Title: Fix unreliable ethernet cable detection on I219 NIC Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Hotplugging RJ45 ethernet cable only works for one time because ACPI GPE wake doesn't working properly anymore. [Fix] Always use PME poll to read PCI PME to know if there's wake event. [Test] With the patch applied, ethernet cable can always be detected. [Where problems could occur] PME poll mechanism periodically reads the PMCTRL register, so the power consumption can be slightly higher. The increase will be very low, probably won't be noticeable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032164] Re: A general-proteciton exception during guest migration to unsupported PKRU machine
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. 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-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032164 Title: A general-proteciton exception during guest migration to unsupported PKRU machine Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Triaged Bug description: [Impact] When a host that supports PKRU initiates a guest that lacks PKRU support, the flag is enabled on the guest's fpstate. This information is then passed to userspace through the vcpu ioctl KVM_GET_XSAVE. However, a problem arises when the user opts to migrate the mentioned guest to another machine that does not support PKRU. In this scenario, the new host attempts to restore the guest's fpu registers. Nevertheless, due to the absence of PKRU support on the new host, a general-protection exception takes place, leading to a guest crash. [Fix] The problem is resolved by the following upstream commit: ad856280ddea x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 Additionally, a subsequent fix tackles the migration problem stemming from the earlier commit: a1020a25e697 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES [Test Plan] 1. Set up two machines: one with PKRU support and the other without. 2. Initiate a guest that lacks PKRU support on the machine with PKRU support. 3. Utilize libvirt to migrate the aforementioned guest to a different machine that lacks PKRU support. 4. The error emerges on the destination machine: KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=86cf7970 EBX= ECX=0001 EDX=005b0036 ESI=0087 EDI=0087 EBP=87c03e38 ESP=87c03e18 EIP=86cf7d5e EFL=0246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2023-07-09T03:03:14.911750Z qemu-system-x86_64: terminating on signal 15 from pid 4134 (/usr/sbin/libvirtd) 2023-07-09 03:03:15.312+: shutting down, reason=destroyed [Where problems could occur] The introduced commits will impact the guest migration process, potentially leading to failures and preventing the guest from operating successfully on the migration destination. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031333] Re: Need to get fine-grained control for FAN(TFN) Participant.
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. 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-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2031333 Title: Need to get fine-grained control for FAN(TFN) Participant. Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: This is a public version of the following bugs: https://bugs.launchpad.net/bugs/1987597 https://bugs.launchpad.net/bugs/2027754 [Feature Description] We need Fine-grained Control of TFN participant for enabling active 2 policy in Linux/chrome. Currently, The kernel has provided __FPS table and cur__state to adjust the fan level as per _FPS table . But there is no option to read *_FIF (Fan Information) and _FST (Fan Status).* Once the fine-grained control is enabled, we should be able to the set the control value from 0-100 through Arg0 of _FSL (Fan Set Level). *_FST (Fan Status)* should report current running RPM and control value of the FAN(TFN). please refer ACPI spec for more detail. [https://uefi.org/specs/ACPI/6.4/11_Thermal_Management/fan- device.html] [HW/SW Information] Hardware: Alder Lake Target Release: 22.04 Target Kernel: 5.15 Merged for 5.18-rc1 f1197343f077 ACPI: fan: Add additional attributes for fine grain control bea2d9868ef5 ACPI: fan: Properly handle fine grain control d445571fa369 ACPI: fan: Optimize struct acpi_fan_fif 00ae053a0533 ACPI: fan: Separate file for attributes creation Platform-independent [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. 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-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2030924] Re: [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in cpuinfo_min_freq and cpuino_max_freq sysfs files.
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. 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-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2030924 Title: [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in cpuinfo_min_freq and cpuino_max_freq sysfs files. Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] On DELL EMC PowerEdge system when Ubuntu 22.04.1 OS is Installed, Unable to Interpret the values in cpuinfo_max_freq and cpuinfo_min_freq sysfs files as per the Intel specs document. Steps to Reproduce: 1. Install one CPU that supports DBS "Demand-Based Power Management". 2. Install Ubuntu 22.04.1 OS. 2. Enable "Logical Processor" under CPU Information menu from F2 setup. 3. Save changes and reboot to Ubuntu 22.04.1 OS. 4. Right click on "Computer" and select "File system" and check for the following CPU directories. /sys/devices/system/cpu/cpu0/cpufreq/cpu0 /sys/devices/system/cpu/cpu0/cpufreq/cpu1 5. View the Max Frequency and Min Frequency under CPU0 and CPU1 directory. 6. The Max and Min Frequency did not match as per the Intel specs datasheet. Actual results: /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 680 /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 80 /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 390 Expected results: As per Intel datasheet specification. /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 5300 MHz /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 800 MHz /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 3000 MHz [Fix] cpufreq: intel_pstate: Fix scaling for hybrid-capable systems with disabled E-cores https://github.com/torvalds/linux/commit/0fcfc9e51990246a9813475716746ff5eb98c6aa [github.com] [Test Plan] Same as steps to reproduce [ Where problems could occur ] This issue is seen on Intel based system under development which supports DBS "Demand-Based Power Management", then install Ubuntu-22.04 and boot into OS then check for the frequency values under /sys/devices/system/cpu/cpu0/cpufreq/cpu0 Regression risk = Low to medium [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/cpuinfo_freq lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/cpuinfo_freq_lunar_2 Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/cpuinfo_freq_mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032176] Re: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. 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-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032176 Title: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Impact: We had reports of VM setups which would show intermediate crashes and after that locking up completely. This could be reproduced with large memory setups. The problem seems to be that fixes to performance regressions caused more problems in 5.15 kernels and the full fixes are too intrusive to be backported. Fix: The following patch was recently sent to the upstream stable mailing list and looks to be making its way into linux-5.15.y. This changes the default value of kvm.tdp_mmu to off (if anyone is willing to take the risks, this can be changed back in config). Regression potential: VM hosts with many large memory tennants might see a performance impact which the TDP MMU approach tried to solve. If those did not see other problems they might turn this on again. Testcase: Large openstack instance (64GB memory, AMD CPU (using SVM)) with a large second level guest (32GB memory). Repeatedly starting and stopping the 2nd level guest. --- original description --- The crash occurred on a juju machine, and the juju agent was lost. The juju machine is on an openstack instance provision by juju. The openstack console log indicts the it is related to spin_lock and KVM MMU: [418200.348830] ? _raw_spin_lock+0x22/0x30 [418200.349588] _raw_write_lock+0x20/0x30 [418200.350196] kvm_tdp_mmu_map+0x2b1/0x490 [kvm] [418200.351014] kvm_mmu_notifier_invalidate_range_start+0x1ad/0x300 [kvm] [418200.351796] direct_page_fault+0x206/0x310 [kvm] [418200.352667] __mmu_notifier_invalidate_range_start+0x91/0x1b0 [418200.353624] kvm_tdp_page_fault+0x72/0x90 [kvm] [418200.354496] try_to_migrate_one+0x691/0x730 [418200.355436] kvm_mmu_page_fault+0x73/0x1c0 [kvm] openstack console log: https://pastebin.canonical.com/p/spmH8r3crQ/ syslog: https://pastebin.canonical.com/p/wFPsFD8G9n/ The syslog was rotated after the crash occurred, so the syslog at the time of the initial crash was lost. Other juju machine with 5.15.0.79.76 kernel seems to have the same issues. We previously have a similar issue with 5.15.0-73. The juju machine crashed with raw_spin_lock and kvm mmu in the logs as well: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Aug 21 08:59:46 2023 Ec2AMI: ami-0c61 Ec2AMIManifest: FIXME Ec2AvailabilityZone: availability-zone-1 Ec2InstanceType: builder-cpu4-ram72-disk20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 23 03:23 seq crw-rw 1 root audio 116, 33 Aug 23 03:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack
[Kernel-packages] [Bug 2034447] Re: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. 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-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034447 Title: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Seeing a panic on hidon (an Nvidia H100) after booting the 5.15.0-85-generic kernel: [ 58.935877] [ cut here ] [ 58.935893] refcount_t: underflow; use-after-free. [ 58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28 refcount_warn_saturate+0xf7/0x150 [ 58.935943] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp coretemp nls_iso8859_1 rapl irdma(+) i40e qat_4xxx(+) isst_if_mbox_pci intel_qat pmt_telemetry pmt_crashlog idxd(+) isst_if_mmio pmt_class isst_if_common authenc idxd_bus intel_th_gth mei_me intel_th_pci intel_th mei switchtec ipmi_ssif acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 multipath linear mlx5_ib ib_uverbs ib_core ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper raid0 mlx5_core syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ixgbe cec mlxfw ghash_clmulni_intel aesni_intel psample crypto_simd xfrm_algo ice rc_core cryptd tls nvme i2c_i801 dca xhci_pci intel_pmt drm [ 58.936077] pci_hyperv_intf i2c_ismt i2c_smbus [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936083] mdio [ 58.936096] xhci_pci_renesas nvme_core wmi pinctrl_emmitsburg [ 58.936106] CPU: 207 PID: 2985 Comm: systemd-udevd Not tainted 5.15.0-85-generic #95-Ubuntu [ 58.936115] Hardware name: NVIDIA DGXH100/DGXH100, BIOS 1.0.7 05/08/2023 [ 58.936119] RIP: 0010:refcount_warn_saturate+0xf7/0x150 [ 58.936130] Code: eb 9e 0f b6 1d 5e e6 b9 01 80 fb 01 0f 87 f4 63 6f 00 83 e3 01 75 89 48 c7 c7 88 c3 23 9e c6 05 42 e6 b9 01 01 e8 d8 e4 6b 00 <0f> 0b e9 6f ff ff ff 0f b6 1d 2d e6 b9 01 80 fb 01 0f 87 b1 63 6f [ 58.936135] RSP: 0018:ff4d5d94b2c7fa28 EFLAGS: 00010282 [ 58.936142] RAX: RBX: RCX: 0027 [ 58.936146] RDX: ff314dbbbf9e0588 RSI: 0001 RDI: ff314dbbbf9e0580 [ 58.936149] RBP: ff4d5d94b2c7fa30 R08: 0026 R09: ff4d5d94b2c7f9c0 [ 58.936153] R10: 0028 R11: 0001 R12: [ 58.936156] R13: ff314cbfdbcb6900 R14: ff314cbfdbcb67b8 R15: ff314cbfd24b4000 [ 58.936159] FS: 7fadd2f6c8c0() GS:ff314dbbbf9c() knlGS: [ 58.936163] CS: 0010 DS: ES: CR0: 80050033 [ 58.936167] CR2: 7fadd243b584 CR3: 00012972c006 CR4: 00771ee0 [ 58.936171] DR0: DR1: DR2: [ 58.936174] DR3: DR6: fffe07f0 DR7: 0400 [ 58.936177] PKRU: 5554 [ 58.936179] Call Trace: [ 58.936184] [ 58.936188] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936204] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936212] ? crypto_mod_put+0x6b/0x80 [ 58.936225] ? show_regs.part.0+0x23/0x29 [ 58.936232] ? show_regs.cold+0x8/0xd [ 58.936239] ? refcount_warn_saturate+0xf7/0x150 [ 58.936246] ? __warn+0x8c/0x100 [ 58.936255] ? refcount_warn_saturate+0xf7/0x150 [ 58.936263] ? report_bug+0xa4/0xd0 [ 58.936274] ? down_trylock+0x2e/0x40 [ 58.936285] ? handle_bug+0x39/0x90 [ 58.936296] ? exc_invalid_op+0x19/0x70 [ 58.936301] ?
[Kernel-packages] [Bug 2034622] Re: NVIDIA pull requests 1017-001v3
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. 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-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2034622 Title: NVIDIA pull requests 1017-001v3 Status in linux-nvidia-tegra package in Ubuntu: New Bug description: Apply patches from NVIDIA pull request sent on 2023-09-04 to jammy:linux-nvidia-tegra. 1017-001 V3 (2023-09-14): Akhil R (1): NVIDIA: SAUCE: Revert "i2c: tegra: Allocate DMA memory for DMA engine" Andy Sobczyk (1): NVIDIA: SAUCE: arm64: config: Enable MTD_UBI Ashish Mhetre (2): NVIDIA: SAUCE: iommu: Don't reserve IOVA when address and size are zero NVIDIA: SAUCE: memory: tegra: Add SID override on resume Kartik (1): NVIDIA: SAUCE: mailbox: tegra-hsp: Add sm ops route_irq & set_irq Laxman Dewangan (2): NVIDIA: SAUCE: config: Disable CONFIG_LOCALVERSION_AUTO NVIDIA: SAUCE: arm64: config: recovery_chain: Enable KEXEC configs Mikko Perttunen (2): thermal: tegra-bpmp: Handle errors in BPMP response thermal/drivers/tegra-bpmp: Handle offline zones Mohan Kumar (1): NVIDIA: SAUCE: arch: arm64: enable HDA_INTEL config Parker Newman (1): i2c: tegra: Fix i2c-tegra DMA config option processing Penny Chiu (1): NVIDIA: SAUCE: arm64: configs: Enable BINFMT_MISC support Sumit Gupta (2): NVIDIA: SAUCE: driver: cpufreq: remove volatile as not needed cpufreq: tegra194: add online/offline hooks Vishwaroop A (1): NVIDIA: SAUCE: spi: spi-tegra114: retain the spi mode raju patel (1): NVIDIA: SAUCE: code-owners: Populate OWNERS file zuyih (1): NVIDIA: SAUCE: s25fs: Add post-get-map-id fixup for S25FS512S --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2034622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033122] Re: Request backport of xen timekeeping performance improvements
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. 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-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033122 Title: Request backport of xen timekeeping performance improvements Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Users, especially those on EC2, are encouraged to select tsc as their default clocksource. However, this requires manual tuning of the operating system. Kvm can determine if it safe to use the tsc, and will default to that instead of its pvclock when appropriate. This requests a backport of patch does the same for Xen instances. If appropriate, it's fine if this is applied to only the linux-aws branches. Not all Xen EC2 instances advertise explicit nomigrate support, however, on those that do we'll select tsc by default. On the subset of hosts where this is advertised, users will safely default to the more performant clocksource. [Impact] Xen instances default to the xen clocksource which has been documented to be slower. This is required for instances where the tsc is not safe to use, or the guest is subject to migration. On some platforms the performance impact can be high, and users are encouraged to select the tsc when appropriate. Instead of leaving up to users to figure this out by reading a variety of different documents, pick the fast clocksource when it can be determined to be safe to do so. [Backport] Clean cherry pick. No conflicts applying to 5.15 or 6.2. [Test] Booted EC2 xen instances with and without this patch and validated that on those that properly advertised the required criteria via cpuid, that the clocksource defaulted to tsc instead of xen. [Potential Regression] Potential is low, since only absurd configurations could lead to a problem. If this is considered risky, it can be applied to only linux-aws where the documented guidance is for users to enable tsc as the clocksource on Xen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035181] Re: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.
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-v2
verification-needed-jammy-linux-nvidia-tegra
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035181
Title:
Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Confirmed
Bug description:
[Impact]
Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work
with CO-RE") from stable update breaks the ubuntu_bpf test build and
cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in
ubuntu_kernel_selftests stopped working, as they require bpf selftest
to be built first.
The following is extracted from the commit message:
The problem is the new offsetof() does not play nice with static asserts.
Given that the context is a static assert (and CO-RE relocation is not
needed at compile time), offsetof() usage can be replaced by restoring
the original offsetof() definition as __builtin_offsetof().
[Test Plan]
Build bpf selftest in tools/testing/selftests with the following command:
make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \
clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/
The build can finish successfully with patched kernel source code.
[Where problems could occur]
Fix limited to testing tool, if this fix is incorrect the bpf selftest
build will remain broken.
== Original bug report ==
Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04
This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
is a security cycle, in which the ubuntu_bpf test was not triggered
there)
Test build failed with:
CLNG-BPF [test_maps] test_btf_map_in_map.o
CLNG-BPF [test_maps] test_btf_newkv.o
CLNG-BPF [test_maps] test_btf_nokv.o
CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
CLNG-BPF [test_maps] test_cgroup_link.o
CLNG-BPF [test_maps] test_check_mtu.o
CLNG-BPF [test_maps] test_cls_redirect.o
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from
latest version at 'include/uapi/linux/bpf.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs
from latest version at 'include/uapi/linux/netlink.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at 'include/uapi/linux/if_link.h'
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
[Kernel-packages] [Bug 2036675] Re: 5.15.0-85 live migration regression
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. 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-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036675 Title: 5.15.0-85 live migration regression Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Released Bug description: Fixes added for LP 2032164 [0] to resolve an issue in live migration have unfortunately introduced a regression, causing a previously working live migration pattern to fail when tested with the 5.15.0-85 kernel from -proposed. Specifically, live migration from a PKRU-enabled host running a kernel older than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail. The destination can be either with or without PKRU; both cases fail, although in different ways (one hangs, the other fails due to a PCID flag issue). The commits in question are commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0 Author: Dr. David Alan Gilbert Date: Mon Aug 21 14:47:28 2023 +0800 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES commit 27a189b881278c8ad9c16b0ee05668d724352733 Author: Leonardo Bras Date: Mon Aug 21 14:47:27 2023 +0800 x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 [0] https://bugs.launchpad.net/bugs/2032164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037316] Re: SEV_SNP failure to init
This bug is awaiting verification that the linux-aws/6.2.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-aws' to 'verification-done-lunar- linux-aws'. If the problem still exists, change the tag 'verification- needed-lunar-linux-aws' to 'verification-failed-lunar-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-aws-v2 verification-needed-lunar-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: Invalid Status in linux-gcp source package in Jammy: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Does anyone know of a Linux distribution with the latest kernel version 6.6? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038645] Re: Ubuntu Mate 22.04 scaling problem
I open mate-display-properties and I changed the screen resolution from 4K to
1920x1080,
then after reboot system I have 1920x1080.
Do these programs use a different configuration file?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2038645
Title:
Ubuntu Mate 22.04 scaling problem
Status in nvidia-settings package in Ubuntu:
New
Bug description:
I changed monitor from 24" LG to 32" Samsung LS32A704NWPXEN
The situation looks like this:
1. 4K starts default, I can save settings to /etc/X11/xorg.conf only with
sudo chmod u+x /usr/share/screen-resolution-extra/nvidia-polkit
2. Problem I have with HDMI and DisplayPort, the situation is the same,
after changing from 1920x1080 to 4K I can see 1/4 of the screen
lower left part of the screen.
The problem does not occur from 4K to 1920x1080 when 4K is default.
To switch to 4K I need remove /etc/X11/xorg.conf and reboot system.
3. Scaling in Mate does not change the size of the Steam icon xD wtf? Why?
I have only option 100% and 200%.
4. Scaling with Nvidia, ( Option Underscan in second tab of nvidia-settings,
default is 0 )
I managed to check by placing the panel at the top and then changing the
scaling in nvidia
(because the image is cut off from the bottom)
It seems to me that this option does not scale, but crops the image.
Because the font and icon sizes looks identical.
Only the picture frame is cut off and the center remains.
5. This monitor does not have an image scaling option.
nvidia-settings 510.47.03-0ubuntu1
System Info
{
inxi -Fxxrzc0
System:
Kernel: 5.15.0-84-generic x86_64 bits: 64 compiler: gcc v: 11.4.0
Desktop: MATE 1.26.0 wm: marco dm: LightDM
Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
Machine:
Type: Desktop Mobo: MSI model: B150M PRO-VDH (MS-7982) v: 1.0
serial: UEFI: American Megatrends v: 3.H0
date: 07/10/2018
CPU:
Info: quad core model: Intel Core i5-6400 bits: 64 type: MCP
arch: Skylake-S rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 2256 high: 3219 min/max: 800/3300 cores: 1: 1271
2: 1623 3: 2912 4: 3219 bogomips: 21599
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: NVIDIA GA106 [Geforce RTX 3050] vendor: Gigabyte driver: nvidia
v: 525.125.06 pcie: speed: 2.5 GT/s lanes: 8 ports: active: none
off: HDMI-A-1 empty: DP-1,DP-2,HDMI-A-2 bus-ID: 01:00.0
chip-ID: 10de:2507
Display: x11 server: X.Org v: 1.21.1.4 compositors: 1: Picom v: 9
2: marco v: 1.26.0 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 69
Monitor-1: HDMI-0 res: 1920x1080 dpi: 70 diag: 801mm (31.5")
OpenGL: renderer: NVIDIA GeForce RTX 3050/PCIe/SSE2
v: 4.6.0 NVIDIA 525.125.06 direct render: Yes
...
Sensors:
System Temperatures: cpu: 29.8 C pch: 37.0 C mobo: 27.8 C gpu: nvidia
temp: 40 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
Packages: 3100 apt: 3082 snap: 18
Active apt repos in: /etc/apt/sources.list
1: deb http://pl.archive.ubuntu.com/ubuntu/ jammy main restricted
2: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-updates main restricted
3: deb http://pl.archive.ubuntu.com/ubuntu/ jammy universe
4: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-updates universe
5: deb http://pl.archive.ubuntu.com/ubuntu/ jammy multiverse
6: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-updates multiverse
7: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-backports main
restricted universe multiverse
8: deb http://security.ubuntu.com/ubuntu jammy-security main restricted
9: deb http://security.ubuntu.com/ubuntu jammy-security universe
10: deb http://security.ubuntu.com/ubuntu jammy-security multiverse
No active apt repos in:
/etc/apt/sources.list.d/minetestdevs-ubuntu-stable-jammy.list
Active apt repos in:
/etc/apt/sources.list.d/mozillateam-ubuntu-ppa-jammy.list
1: deb https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/ jammy main
2: deb-src https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/ jammy
main
Info:
Processes: 247 Uptime: 2h 7m Memory: 15.56 GiB used: 4.49 GiB (28.8%)
Init: systemd v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12
Shell: Bash v: 5.1.16 running-in: mate-terminal inxi: 3.3.13
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/2038645/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 2038645] Re: Ubuntu Mate 22.04 scaling problem
>From sudo /usr/bin/nvidia-bug-report.sh
{
/var/log/kern.log:
Oct 8 01:43:29 tele kernel: [ 260.464109] NVRM: API mismatch: the client has
the version 535.113.01, but
Oct 8 01:43:29 tele kernel: [ 260.464109] NVRM: this kernel module has the
version 525.125.06. Please
Oct 8 01:43:29 tele kernel: [ 260.464109] NVRM: make sure that this kernel
module and all NVIDIA driver
Oct 8 01:43:29 tele kernel: [ 260.464109] NVRM: components have the same
version.
}
>From terminal
{
$ dpkg -l | grep nvidia
ii libnvidia-cfg1-535:amd64 535.113.01-0ubuntu0.22.04.1
amd64NVIDIA binary OpenGL/GLX configuration library
ii libnvidia-common-535 535.113.01-0ubuntu0.22.04.1
all Shared files used by the NVIDIA libraries
rc libnvidia-compute-515:amd64525.125.06-0ubuntu0.22.04.1
amd64Transitional package for libnvidia-compute-525
rc libnvidia-compute-525:amd64525.125.06-0ubuntu0.22.04.1
amd64NVIDIA libcompute package
ii libnvidia-compute-535:amd64535.113.01-0ubuntu0.22.04.1
amd64NVIDIA libcompute package
ii libnvidia-compute-535:i386 535.113.01-0ubuntu0.22.04.1
i386 NVIDIA libcompute package
ii libnvidia-decode-535:amd64 535.113.01-0ubuntu0.22.04.1
amd64NVIDIA Video Decoding runtime libraries
ii libnvidia-decode-535:i386 535.113.01-0ubuntu0.22.04.1
i386 NVIDIA Video Decoding runtime libraries
ii libnvidia-egl-wayland1:amd64 1:1.1.9-1.1
amd64Wayland EGL External Platform library -- shared library
ii libnvidia-encode-535:amd64 535.113.01-0ubuntu0.22.04.1
amd64NVENC Video Encoding runtime library
ii libnvidia-encode-535:i386 535.113.01-0ubuntu0.22.04.1
i386 NVENC Video Encoding runtime library
ii libnvidia-extra-535:amd64 535.113.01-0ubuntu0.22.04.1
amd64Extra libraries for the NVIDIA driver
ii libnvidia-fbc1-535:amd64 535.113.01-0ubuntu0.22.04.1
amd64NVIDIA OpenGL-based Framebuffer Capture runtime library
ii libnvidia-fbc1-535:i386535.113.01-0ubuntu0.22.04.1
i386 NVIDIA OpenGL-based Framebuffer Capture runtime library
ii libnvidia-gl-535:amd64 535.113.01-0ubuntu0.22.04.1
amd64NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii libnvidia-gl-535:i386 535.113.01-0ubuntu0.22.04.1
i386 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
rc linux-modules-nvidia-515-5.15.0-40-generic 5.15.0-40.43+1
amd64Linux kernel nvidia modules for version 5.15.0-40
rc linux-modules-nvidia-515-5.15.0-41-generic 5.15.0-41.44+1
amd64Linux kernel nvidia modules for version 5.15.0-41
rc linux-modules-nvidia-515-5.15.0-43-generic 5.15.0-43.46+1
amd64Linux kernel nvidia modules for version 5.15.0-43
rc linux-modules-nvidia-515-5.15.0-46-generic 5.15.0-46.49
amd64Linux kernel nvidia modules for version 5.15.0-46
rc linux-modules-nvidia-515-5.15.0-47-generic 5.15.0-47.51
amd64Linux kernel nvidia modules for version 5.15.0-47
rc linux-modules-nvidia-515-5.15.0-48-generic 5.15.0-48.54
amd64Linux kernel nvidia modules for version 5.15.0-48
rc linux-modules-nvidia-515-5.15.0-52-generic 5.15.0-52.58+1
amd64Linux kernel nvidia modules for version 5.15.0-52
rc linux-modules-nvidia-515-5.15.0-53-generic 5.15.0-53.59+1
amd64Linux kernel nvidia modules for version 5.15.0-53
rc linux-modules-nvidia-515-5.15.0-56-generic 5.15.0-56.62+1
amd64Linux kernel nvidia modules for version 5.15.0-56
rc linux-modules-nvidia-515-5.15.0-57-generic 5.15.0-57.63+1
amd64Linux kernel nvidia modules for version 5.15.0-57
rc linux-modules-nvidia-515-5.15.0-58-generic 5.15.0-58.64+1
amd64Linux kernel nvidia modules for version 5.15.0-58
rc linux-modules-nvidia-515-5.15.0-60-generic 5.15.0-60.66
amd64Linux kernel nvidia modules for version 5.15.0-60
rc linux-modules-nvidia-515-5.15.0-67-generic 5.15.0-67.74
amd64Linux kernel nvidia modules for version 5.15.0-67
rc linux-modules-nvidia-515-5.15.0-69-generic
[Kernel-packages] [Bug 2031969] Re: Ubuntu 23.04: Suspend & Power off
@polarbaerhh, First and foremost, I expect to be treated, and for others to be treated, with respect. It was inappropriate for you to suggest that users are maliciously manipulating and altering others' reports. Please be mindful of your words, as I can bring your behavior to the attention of your superiors. I simply refined the bug description based on user feedback. It's worth noting that I reported a bug under #2031352, and a Canonical employee modified the bug description to a different issue unrelated to the one I initially described. That same employee later apologized and asked me to add more details to the bug. I will not tolerate being treated this way. I'm providing information to help resolve the bug in the best possible manner. I aim to act professionally and communicate assertively. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2031969 Title: Ubuntu 23.04: Suspend & Power off Status in linux package in Ubuntu: Confirmed Bug description: Since update to version 23.04 I am facing several problems related to system suspend and shutdownon a HP Envy 15 notebook (2016). The system refuses to wake up from standby mode, especially if it has run for a longer time. Screen is black, no response to keyboard or trackpad actions, power button led is on. The only way out of here is a long press on the power button. Another problem with this and I think it's kind of related. If you want to shut down the computer after a long runtime, the machine won't power off. In the logs you can see the steps for shutting down the OS, but sometimes the machine stays powered on. The power led is on, screen is black, no response to keyboard or trackpad actions. System has to be powered off by a long press on the power button. Ubuntu 6.2.0-27.28-generic 6.2.15 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom2051 F wireplumber /dev/snd/seq:tom2037 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 19 16:01:07 2023 InstallationDate: Installed on 2018-07-01 (1875 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-27-generic N/A linux-backports-modules-6.2.0-27-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-05-01 (109 days ago) dmi.bios.date: 11/10/2020 dmi.bios.release: 15.62 dmi.bios.vendor: Insyde dmi.bios.version: F.62 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81D2 dmi.board.vendor: HP dmi.board.version: KBC Version 87.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.21 dmi.modalias: dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY Notebook dmi.product.sku: Z6J78EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038645] Re: Ubuntu Mate 22.04 scaling problem
At the present day
- I upgraded driver to nvidia-driver-535 , 535.113.01-0ubuntu0.22.04.1
- I installed xserver-xorg-dev to remove above error about `xorg-server.pc'
But when I'm trying save settings to /etc/X11/xorg.conf
I have warning:
={
WARNING: Unable to parse X.Org version string.
=}
- After reboot I have 4K instead 1920x1080
- I checked whether the changes had actually been saved.
I did
- removed /etc/X11/xorg.conf
- checked with ls and not exist file /etc/X11/xorg.conf
- saved settings to /etc/X11/xorg.conf
and file exist
- after reboot, in /var/log/Xorg.0.log I see
={
...
[ 889.417] (II) NVIDIA(0): Validated MetaModes:
[ 889.417] (II) NVIDIA(0): "1920x1080_50+0+0"
[ 889.417] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 889.491] (--) NVIDIA(0): DPI set to (69, 68); computed from "UseEdidDpi" X
config
[ 889.491] (--) NVIDIA(0): option
[ 889.492] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect
memory
[ 889.492] (II) NVIDIA: access.
[ 889.518] (II) NVIDIA(0): Setting mode "1920x1080_50+0+0"
[ 889.576] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 889.576] (==) NVIDIA(0): Backing store enabled
[ 889.576] (==) NVIDIA(0): Silken mouse enabled
[ 889.577] (**) NVIDIA(0): DPMS enabled
...
=}
- After reboot I have 4K instead 1920x1080
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2038645
Title:
Ubuntu Mate 22.04 scaling problem
Status in nvidia-settings package in Ubuntu:
New
Bug description:
I changed monitor from 24" LG to 32" Samsung LS32A704NWPXEN
The situation looks like this:
1. 4K starts default, I can save settings to /etc/X11/xorg.conf only with
sudo chmod u+x /usr/share/screen-resolution-extra/nvidia-polkit
2. Problem I have with HDMI and DisplayPort, the situation is the same,
after changing from 1920x1080 to 4K I can see 1/4 of the screen
lower left part of the screen.
The problem does not occur from 4K to 1920x1080 when 4K is default.
To switch to 4K I need remove /etc/X11/xorg.conf and reboot system.
3. Scaling in Mate does not change the size of the Steam icon xD wtf? Why?
I have only option 100% and 200%.
4. Scaling with Nvidia, ( Option Underscan in second tab of nvidia-settings,
default is 0 )
I managed to check by placing the panel at the top and then changing the
scaling in nvidia
(because the image is cut off from the bottom)
It seems to me that this option does not scale, but crops the image.
Because the font and icon sizes looks identical.
Only the picture frame is cut off and the center remains.
5. This monitor does not have an image scaling option.
nvidia-settings 510.47.03-0ubuntu1
System Info
{
inxi -Fxxrzc0
System:
Kernel: 5.15.0-84-generic x86_64 bits: 64 compiler: gcc v: 11.4.0
Desktop: MATE 1.26.0 wm: marco dm: LightDM
Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
Machine:
Type: Desktop Mobo: MSI model: B150M PRO-VDH (MS-7982) v: 1.0
serial: UEFI: American Megatrends v: 3.H0
date: 07/10/2018
CPU:
Info: quad core model: Intel Core i5-6400 bits: 64 type: MCP
arch: Skylake-S rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 2256 high: 3219 min/max: 800/3300 cores: 1: 1271
2: 1623 3: 2912 4: 3219 bogomips: 21599
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: NVIDIA GA106 [Geforce RTX 3050] vendor: Gigabyte driver: nvidia
v: 525.125.06 pcie: speed: 2.5 GT/s lanes: 8 ports: active: none
off: HDMI-A-1 empty: DP-1,DP-2,HDMI-A-2 bus-ID: 01:00.0
chip-ID: 10de:2507
Display: x11 server: X.Org v: 1.21.1.4 compositors: 1: Picom v: 9
2: marco v: 1.26.0 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 69
Monitor-1: HDMI-0 res: 1920x1080 dpi: 70 diag: 801mm (31.5")
OpenGL: renderer: NVIDIA GeForce RTX 3050/PCIe/SSE2
v: 4.6.0 NVIDIA 525.125.06 direct render: Yes
...
Sensors:
System Temperatures: cpu: 29.8 C pch: 37.0 C mobo: 27.8 C gpu: nvidia
temp: 40 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
Packages: 3100 apt: 3082 snap: 18
Active apt repos in: /etc/apt/sources.list
1: deb http://pl.archive.ubuntu.com/ubuntu/ jammy main restricted
2: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-updates main restricted
3: deb http://pl.archive.ubuntu.com/ubuntu/ jammy universe
4: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-updates universe
5: deb http://pl.archive.ubuntu.com/ubuntu/ jammy multiverse
6: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-updates multiverse
7: deb http://pl.archive.ubuntu.com/ubuntu/
[Kernel-packages] [Bug 2038748] Re: amdgpu mst power saving null ptr deref
A fix may already be available at https://gitlab.freedesktop.org/drm/amd/-/issues/2486 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2486 https://gitlab.freedesktop.org/drm/amd/-/issues/2486 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038748 Title: amdgpu mst power saving null ptr deref Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Reoccurrence of amdgpu MST power saving related null pointer deref. Likely should be against kernel instead, but let's see whether ubuntu- bug attached sensible part of logs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Sun Oct 8 10:23:57 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038748] Re: Xorg freeze amdgpu mst powersaving
** Package changed: xorg (Ubuntu) => linux-signed-hwe-6.2 (Ubuntu) ** Summary changed: - Xorg freeze amdgpu mst powersaving + amdgpu mst power saving null ptr deref -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038748 Title: amdgpu mst power saving null ptr deref Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Reoccurrence of amdgpu MST power saving related null pointer deref. Likely should be against kernel instead, but let's see whether ubuntu- bug attached sensible part of logs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Sun Oct 8 10:23:57 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038749] Re: amdgpu mst power saving null ptr deref
** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Incomplete ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038749 Title: amdgpu mst power saving null ptr deref Status in linux-signed-hwe-6.2 package in Ubuntu: Invalid Bug description: Amdgpu tends to crash when attempting to unlock screen after power saving has been triggered on MST screen(s). Further details to be filled in post-reboot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Oct 8 11:03:13 2023 InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038748] [NEW] Xorg freeze amdgpu mst powersaving
You have been subscribed to a public bug: Reoccurrence of amdgpu MST power saving related null pointer deref. Likely should be against kernel instead, but let's see whether ubuntu- bug attached sensible part of logs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Sun Oct 8 10:23:57 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze jammy ubuntu -- Xorg freeze amdgpu mst powersaving https://bugs.launchpad.net/bugs/2038748 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038749] Re: amdgpu mst power saving null ptr deref
Duplicate of #2038748 which apparently got some more logs than this one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038749 Title: amdgpu mst power saving null ptr deref Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Amdgpu tends to crash when attempting to unlock screen after power saving has been triggered on MST screen(s). Further details to be filled in post-reboot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Oct 8 11:03:13 2023 InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038749] [NEW] amdgpu mst power saving null ptr deref
Public bug reported: Amdgpu tends to crash when attempting to unlock screen after power saving has been triggered on MST screen(s). Further details to be filled in post-reboot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Oct 8 11:03:13 2023 InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038749 Title: amdgpu mst power saving null ptr deref Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Amdgpu tends to crash when attempting to unlock screen after power saving has been triggered on MST screen(s). Further details to be filled in post-reboot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Oct 8 11:03:13 2023 InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031969] Re: Ubuntu 23.04: Suspend & Power off
@cfgnunes: Please do not hijack and mangle other people's reports. I did not have this experience with 22.04.3 LTS. The logs and the description belong to 23.04. Changing only the summary is pointless. Maybe the problem exists in other Ubuntu versions too. It probably has to do with kernel version 6.x. So if someone has also had this experience with another installation, it makes sense to file a report for this as well. Marking it as a duplicate will generate more heat on the issue. ** Summary changed: - Ubuntu 22.04.3 LTS sometimes stuck on power-off/reboot screen + Ubuntu 23.04: Suspend & Power off ** Description changed: - Since I updated to version 23.04 I am facing several problems related to - system suspend and shutdown. The system refuses to wake up from standby - mode, especially if it has run for a longer time. Screen is black, no - response to keyboard or trackpad actions, Power button led is on. The - only way out of here is a long press on the power button. + Since update to version 23.04 I am facing several problems related to + system suspend and shutdownon a HP Envy 15 notebook (2016). The system + refuses to wake up from standby mode, especially if it has run for a + longer time. Screen is black, no response to keyboard or trackpad + actions, power button led is on. The only way out of here is a long + press on the power button. - Another issue with this, and I think it's related. If you want to shut - down the computer after a long runtime, the machine won't power off. In - the logs you can see the steps for shutting down the OS, but eventually - the machine stays powered on. The power lead is on, the screen is black, - no response to keyboard or trackpad actions. System has to be powered - off by a long press on the power button. + Another problem with this and I think it's kind of related. If you want + to shut down the computer after a long runtime, the machine won't power + off. In the logs you can see the steps for shutting down the OS, but + sometimes the machine stays powered on. The power led is on, screen is + black, no response to keyboard or trackpad actions. System has to be + powered off by a long press on the power button. Ubuntu 6.2.0-27.28-generic 6.2.15 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom2051 F wireplumber /dev/snd/seq:tom2037 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 19 16:01:07 2023 InstallationDate: Installed on 2018-07-01 (1875 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-27-generic N/A linux-backports-modules-6.2.0-27-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-05-01 (109 days ago) dmi.bios.date: 11/10/2020 dmi.bios.release: 15.62 dmi.bios.vendor: Insyde dmi.bios.version: F.62 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81D2 dmi.board.vendor: HP dmi.board.version: KBC Version 87.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.21 dmi.modalias: dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY Notebook dmi.product.sku: Z6J78EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2031969 Title: Ubuntu 23.04: Suspend & Power off Status in linux package in Ubuntu: Confirmed Bug description: Since update to version 23.04 I am facing several
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Exactly Endre. These are the major problems. Request to kernel team will be to address these three problems on priority. In addition to that there is one more problem that I might not have mentioned earlier and that is the issue related to system Suspend functionality. In my LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop, system does not enter into standby mode when physical power button is pressed even though the button is mapped to suspend mode done through Settings-->Power-->Power Button Behavior. This is inconveinent especially when I wish to talk for a shorter distance with just laptop lid closed, but cannot do because then the system gets unstable. So, only option left to me is to move around by keeping the laptop lid open. So, it should also be checked by others if they are experiencing the same behavior. And if so, then it could also be another concern that the kernel team might be interested to look into. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
418 is clean. $ reverse-depends src:nvidia-graphics-drivers-418-server No reverse dependencies found $ reverse-depends src:nvidia-graphics-drivers-418-server -a source No reverse dependencies found $ Removing packages from mantic: nvidia-graphics-drivers-418-server 418.226.00-0ubuntu5 in mantic libnvidia-cfg1-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-common-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-common-418-server 418.226.00-0ubuntu5 in mantic arm64 libnvidia-common-418-server 418.226.00-0ubuntu5 in mantic armhf libnvidia-common-418-server 418.226.00-0ubuntu5 in mantic i386 libnvidia-common-418-server 418.226.00-0ubuntu5 in mantic ppc64el libnvidia-common-418-server 418.226.00-0ubuntu5 in mantic riscv64 libnvidia-common-418-server 418.226.00-0ubuntu5 in mantic s390x libnvidia-compute-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-compute-418-server 418.226.00-0ubuntu5 in mantic i386 libnvidia-decode-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-decode-418-server 418.226.00-0ubuntu5 in mantic i386 libnvidia-encode-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-encode-418-server 418.226.00-0ubuntu5 in mantic i386 libnvidia-fbc1-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-fbc1-418-server 418.226.00-0ubuntu5 in mantic i386 libnvidia-gl-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-gl-418-server 418.226.00-0ubuntu5 in mantic i386 libnvidia-ifr1-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-ifr1-418-server 418.226.00-0ubuntu5 in mantic i386 nvidia-compute-utils-418-server 418.226.00-0ubuntu5 in mantic amd64 nvidia-dkms-418-server 418.226.00-0ubuntu5 in mantic amd64 nvidia-driver-418-server 418.226.00-0ubuntu5 in mantic amd64 nvidia-headless-418-server 418.226.00-0ubuntu5 in mantic amd64 nvidia-headless-no-dkms-418-server 418.226.00-0ubuntu5 in mantic amd64 nvidia-kernel-common-418-server 418.226.00-0ubuntu5 in mantic amd64 nvidia-kernel-source-418-server 418.226.00-0ubuntu5 in mantic amd64 nvidia-utils-418-server 418.226.00-0ubuntu5 in mantic amd64 xserver-xorg-video-nvidia-418-server 418.226.00-0ubuntu5 in mantic amd64 Comment: EOL and obsolete; LP: #2035189 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Removing packages from mantic: nvidia-graphics-drivers-440-server 440.95.01-0ubuntu2 in mantic Comment: EOL, obsolete source package; LP: #2035189 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-440-server (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
The reason for adding bumblebee is that Recommends and alternative Depends on removed packages can cause them to be retained on end user systems after upgrade. Better to remove the references than to try to work out if nvidia would manage to not be affected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Ok, on the correct package reverse-depends now shows: $ reverse-depends src:nvidia-graphics-drivers-450-server Reverse-Depends === * libnvidia-decode-440-server (for libnvidia-decode-450-server) * libnvidia-encode-440-server (for libnvidia-encode-450-server) * libnvidia-fbc1-440-server (for libnvidia-fbc1-450-server) * libnvidia-ifr1-440-server (for libnvidia-ifr1-450-server) * linux-modules-nvidia-450-server-6.5.0-1004-azure [amd64] * linux-modules-nvidia-450-server-6.5.0-1004-gcp [amd64] * linux-modules-nvidia-450-server-6.5.0-1005-aws [amd64] * linux-modules-nvidia-450-server-6.5.0-1005-oracle [amd64] * linux-modules-nvidia-450-server-6.5.0-5-generic [amd64] * linux-modules-nvidia-450-server-6.5.0-5-lowlatency [amd64] * linux-modules-nvidia-450-server-aws [amd64] * linux-modules-nvidia-450-server-azure [amd64] * linux-modules-nvidia-450-server-gcp [amd64] * linux-modules-nvidia-450-server-generic [amd64] * linux-modules-nvidia-450-server-generic-hwe-22.04 [amd64] * linux-modules-nvidia-450-server-generic-hwe-22.04-edge [amd64] * linux-modules-nvidia-450-server-lowlatency [amd64] * linux-modules-nvidia-450-server-lowlatency-hwe-22.04 [amd64] * linux-modules-nvidia-450-server-lowlatency-hwe-22.04-edge [amd64] * linux-modules-nvidia-450-server-oracle [amd64] Packages without architectures listed are reverse-dependencies in: amd64, i386 $ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038719] Re: Monitor Issues
I am unable to do this as the GUI is completely unusable, it is like trying to use your computer while the screen is off. I will keep this in mind for future however, as I am trying to install a different distro - hopefully one still Ubunutu based, but I am yet to decide. -- 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/2038719 Title: Monitor Issues Status in linux package in Ubuntu: Incomplete Bug description: Originally on Kernel 5.13 my GPU is not detected and only one monitor out of my three functions. I originally fixed this by moving to the latest (6.2) which came with its own issues, of which all were resolved. Yesterday I updated firmware, and this morning after reboot only one monitor works again, and the monitor is all stripey and there are 4 of a corner of the screen displayed in strips. The operation is fine but the display is broken. Hopefully this describes the issue enough, if you need an image just tell me how to upload it - I am on the mint distro, I am a newbie to this so I hope this is still the right place. CPU: Ryzen 7 3700X GPU: Radeon 7900XTX Boot: Clean linux only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
