[Kernel-packages] [Bug 2033418] Re: Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default
The data in comment #1 shows only two "VGA" controllers that could be
used:
46:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED
Graphics Family [1a03:2000] (rev 41) (prog-if 00 [VGA controller])
c1:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU117GLM [Quadro
T1000 Mobile] [10de:1fb0] (rev a1) (prog-if 00 [VGA controller]) (this is
"PCI:193:0:0")
So we want to tell the kernel to boot without PCI device "46:00.0" or
else it will likely only use ASPEED as the boot VGA. I can't find a
quick answer right now but maybe by assigning this bug to the kernel
team someone will...
** Also affects: linux-nvidia (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2033418
Title:
Ubuntu desktop does not appear on DGX Station A100 discrete GPU by
default
Status in linux-nvidia package in Ubuntu:
New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
New
Bug description:
The DGX Station A10 has various display options. The BMC provides an
emulated device (Aspeed controller), a physical BMC controller (NVIDIA
Quadro T1000 Mobile), and a discrete GPU card with 4 DisplayPort
outputs (A100 SXM4 80GB). See the user guide[*] for a diagram.
In a default Ubuntu Desktop 22.04 ('jammy') install, nothing appears
on the A100 DisplayPort output.
NVIDIA DGX OS - a derivative of Ubuntu - works around this by
installing a service that generates an xorg config file dynamically
based on the "OnBrd/Ext VGA Select" setting (aka "dmidecode -t 11").
I'll attach samples of those files here. Replacing the default Ubuntu
xorg.conf file with the sample xorg-nvidia.conf file on a default
Ubuntu Desktop install is confirmed to enable output.
[*] https://docs.nvidia.com/dgx/dgx-station-a100-user-guide/getting-
started-station-a100.html
(Note: split from bug 2031367)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2033418/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032535] 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/2032535 Title: [Google_Puff] Screen blank crashes system Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 23.04 screen blank crashes system. Not a sleep problem, I can enter and resume from S2idle, S2ram. (Using command line or Power/Suspend GUI) However, when screen blanks, computer has a hard crash. Just rebooting with power button may not work (operating system not found error) I have to unplug the computer and plug it back in again to reboot properly. I would just turn off screen sleep, but when the S2ram suspend mode engages it often, but not always, crashes as well. I've tried live disks with other OS, and this is not a problem on Linux Mint 21.2, nor on Xubuntu 23.04.Windows 10 works too. I tried Ubuntu 22.04 and it also crashed - using either gnome or wayland. I'm happy to help debug, but I'm not a developer. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 21 15:11:21 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] InstallationDate: Installed on 2023-06-13 (69 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Google Noibat ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=77b0ab13-596d-4e94-8648-e6aeda300b7a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2023 dmi.bios.release: 4.20 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.20.0 dmi.board.name: Noibat dmi.board.vendor: HP dmi.board.version: rev4 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.20.0:bd05/15/2023:br4.20:efr0.0:svnGoogle:pnNoibat:pvrrev4:rvnHP:rnNoibat:rvrrev4:cvnGoogle:ct3:cvr:skusku83886080: dmi.product.family: Google_Puff dmi.product.name: Noibat dmi.product.sku: sku83886080 dmi.product.version: rev4 dmi.sys.vendor: Google version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032535] Re: [Google_Puff] Screen blank crashes system
** Summary changed: - Screen blank crashes system + [Google_Puff] Screen blank crashes system ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032535 Title: [Google_Puff] Screen blank crashes system Status in linux package in Ubuntu: New Bug description: Ubuntu 23.04 screen blank crashes system. Not a sleep problem, I can enter and resume from S2idle, S2ram. (Using command line or Power/Suspend GUI) However, when screen blanks, computer has a hard crash. Just rebooting with power button may not work (operating system not found error) I have to unplug the computer and plug it back in again to reboot properly. I would just turn off screen sleep, but when the S2ram suspend mode engages it often, but not always, crashes as well. I've tried live disks with other OS, and this is not a problem on Linux Mint 21.2, nor on Xubuntu 23.04.Windows 10 works too. I tried Ubuntu 22.04 and it also crashed - using either gnome or wayland. I'm happy to help debug, but I'm not a developer. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 21 15:11:21 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] InstallationDate: Installed on 2023-06-13 (69 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Google Noibat ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=77b0ab13-596d-4e94-8648-e6aeda300b7a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2023 dmi.bios.release: 4.20 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.20.0 dmi.board.name: Noibat dmi.board.vendor: HP dmi.board.version: rev4 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.20.0:bd05/15/2023:br4.20:efr0.0:svnGoogle:pnNoibat:pvrrev4:rvnHP:rnNoibat:rvrrev4:cvnGoogle:ct3:cvr:skusku83886080: dmi.product.family: Google_Puff dmi.product.name: Noibat dmi.product.sku: sku83886080 dmi.product.version: rev4 dmi.sys.vendor: Google version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032535] [NEW] [Google_Puff] Screen blank crashes system
You have been subscribed to a public bug: Ubuntu 23.04 screen blank crashes system. Not a sleep problem, I can enter and resume from S2idle, S2ram. (Using command line or Power/Suspend GUI) However, when screen blanks, computer has a hard crash. Just rebooting with power button may not work (operating system not found error) I have to unplug the computer and plug it back in again to reboot properly. I would just turn off screen sleep, but when the S2ram suspend mode engages it often, but not always, crashes as well. I've tried live disks with other OS, and this is not a problem on Linux Mint 21.2, nor on Xubuntu 23.04.Windows 10 works too. I tried Ubuntu 22.04 and it also crashed - using either gnome or wayland. I'm happy to help debug, but I'm not a developer. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 21 15:11:21 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] InstallationDate: Installed on 2023-06-13 (69 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Google Noibat ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=77b0ab13-596d-4e94-8648-e6aeda300b7a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2023 dmi.bios.release: 4.20 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.20.0 dmi.board.name: Noibat dmi.board.vendor: HP dmi.board.version: rev4 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.20.0:bd05/15/2023:br4.20:efr0.0:svnGoogle:pnNoibat:pvrrev4:rvnHP:rnNoibat:rvrrev4:cvnGoogle:ct3:cvr:skusku83886080: dmi.product.family: Google_Puff dmi.product.name: Noibat dmi.product.sku: sku83886080 dmi.product.version: rev4 dmi.sys.vendor: Google version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze lunar ubuntu -- [Google_Puff] Screen blank crashes system https://bugs.launchpad.net/bugs/2032535 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035313] Re: Fix non-working I219 after system sleep
** Tags added: oem-priority originate-from-2034505 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2035313 Title: Fix non-working I219 after system sleep Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Intel I219 ethernet stops working after system sleep. [Fix] Force resume Intel ME to fix I219. It's not surprising because ME/AMT is controlled through Intel I219. [Test] Use `ping 1.1.1.1` to test if I219 is still alive. With the patch applied, the ethernet can survive several system sleeps. [Where problems could occur] The commit essentially disables direct-complete optimization, so it will make system suspend/resume slightly slower. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2035313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035559] Re: upgrade to latest proposed kernel 6.5.0-5 failed
removed the tp-smapi-dkms package solved the upgrade -- 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/2035559 Title: upgrade to latest proposed kernel 6.5.0-5 failed Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-headers-6.5.0-5-generic (6.5.0-5.5) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.5.0-5-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j12 KERNELRELEASE=6.5.0-5-generic -C /lib/modules/6.5.0-5-generic/build M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel: 6.5.0-5-generic (x86_64) Consult /var/lib/dkms/tp_smapi/0.43/build/make.log for more information. dkms autoinstall on 6.5.0-5-generic/x86_64 succeeded for nvidia dkms autoinstall on 6.5.0-5-generic/x86_64 failed for tp_smapi(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.5.0-5-generic ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.5.0-5-generic (--configure): installed linux-headers-6.5.0-5-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-22.04: linux-headers-generic-hwe-22.04 depends on linux-headers-6.5.0-5-generic; however: Package linux-headers-6.5.0-5-generic is not configured yet. dpkg: error processing package linux-headers-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured Setting up linux-image-6.5.0-5-generic (6.5.0-5.5) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic-hwe-22.04: linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04 (= 6.5.0.5.7); however: Package linux-headers-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-oem-22.04: linux-oem-22.04 depends on linux-generic-hwe-22.04; however: Package linux-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-oem-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.5.0-5-generic; however: Package linux-headers-6.5.0-5-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfNo apport report written because the error message indicates its a followup error from a previous failure. No apport repo rt written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already igured dpkg: dependency problems prevent configuration of linux-headers-oem-22.04: linux-headers-oem-22.04 depends on linux-headers-generic-hwe-22.04; however: Package linux-headers-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-headers-oem-22.04 (--configure): dependency problems - leaving unconfigured Processing triggers for linux-image-6.5.0-5-generic (6.5.0-5.5) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.5.0-5-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j12 KERNELRELEASE=6.5.0-5-generic -C /lib/modules/6.5.0-5-generic/build M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel: 6.5.0-5-generic (x86_64) Consult
[Kernel-packages] [Bug 2035559] 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/2035559 Title: upgrade to latest proposed kernel 6.5.0-5 failed Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-headers-6.5.0-5-generic (6.5.0-5.5) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.5.0-5-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j12 KERNELRELEASE=6.5.0-5-generic -C /lib/modules/6.5.0-5-generic/build M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel: 6.5.0-5-generic (x86_64) Consult /var/lib/dkms/tp_smapi/0.43/build/make.log for more information. dkms autoinstall on 6.5.0-5-generic/x86_64 succeeded for nvidia dkms autoinstall on 6.5.0-5-generic/x86_64 failed for tp_smapi(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.5.0-5-generic ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.5.0-5-generic (--configure): installed linux-headers-6.5.0-5-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-22.04: linux-headers-generic-hwe-22.04 depends on linux-headers-6.5.0-5-generic; however: Package linux-headers-6.5.0-5-generic is not configured yet. dpkg: error processing package linux-headers-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured Setting up linux-image-6.5.0-5-generic (6.5.0-5.5) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic-hwe-22.04: linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04 (= 6.5.0.5.7); however: Package linux-headers-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-oem-22.04: linux-oem-22.04 depends on linux-generic-hwe-22.04; however: Package linux-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-oem-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.5.0-5-generic; however: Package linux-headers-6.5.0-5-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfNo apport report written because the error message indicates its a followup error from a previous failure. No apport repo rt written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already igured dpkg: dependency problems prevent configuration of linux-headers-oem-22.04: linux-headers-oem-22.04 depends on linux-headers-generic-hwe-22.04; however: Package linux-headers-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-headers-oem-22.04 (--configure): dependency problems - leaving unconfigured Processing triggers for linux-image-6.5.0-5-generic (6.5.0-5.5) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.5.0-5-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j12 KERNELRELEASE=6.5.0-5-generic -C /lib/modules/6.5.0-5-generic/build M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel:
[Kernel-packages] [Bug 2035559] [NEW] upgrade to latest proposed kernel 6.5.0-5 failed
Public bug reported: Setting up linux-headers-6.5.0-5-generic (6.5.0-5.5) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.5.0-5-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j12 KERNELRELEASE=6.5.0-5-generic -C /lib/modules/6.5.0-5-generic/build M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel: 6.5.0-5-generic (x86_64) Consult /var/lib/dkms/tp_smapi/0.43/build/make.log for more information. dkms autoinstall on 6.5.0-5-generic/x86_64 succeeded for nvidia dkms autoinstall on 6.5.0-5-generic/x86_64 failed for tp_smapi(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.5.0-5-generic ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.5.0-5-generic (--configure): installed linux-headers-6.5.0-5-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-22.04: linux-headers-generic-hwe-22.04 depends on linux-headers-6.5.0-5-generic; however: Package linux-headers-6.5.0-5-generic is not configured yet. dpkg: error processing package linux-headers-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured Setting up linux-image-6.5.0-5-generic (6.5.0-5.5) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic-hwe-22.04: linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04 (= 6.5.0.5.7); however: Package linux-headers-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-oem-22.04: linux-oem-22.04 depends on linux-generic-hwe-22.04; however: Package linux-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-oem-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.5.0-5-generic; however: Package linux-headers-6.5.0-5-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfNo apport report written because the error message indicates its a followup error from a previous failure. No apport repo rt written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already igured dpkg: dependency problems prevent configuration of linux-headers-oem-22.04: linux-headers-oem-22.04 depends on linux-headers-generic-hwe-22.04; however: Package linux-headers-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-headers-oem-22.04 (--configure): dependency problems - leaving unconfigured Processing triggers for linux-image-6.5.0-5-generic (6.5.0-5.5) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.5.0-5-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j12 KERNELRELEASE=6.5.0-5-generic -C /lib/modules/6.5.0-5-generic/build M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel: 6.5.0-5-generic (x86_64) Consult /var/lib/dkms/tp_smapi/0.43/build/make.log for more information. dkms autoinstall on 6.5.0-5-generic/x86_64 succeeded for nvidia dkms autoinstall on 6.5.0-5-generic/x86_64 failed for tp_smapi(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.5.0-5-generic ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package
[Kernel-packages] [Bug 2035400] Re: Jammy update: v5.15.124 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.15.124 upstream stable release + from git://git.kernel.org/ -v5.15.124 upstream stable release -from git://git.kernel.org/ + jbd2: Fix wrongly judgement for buffer head removing while doing checkpoint + KVM: s390: pv: fix index value of replaced ASCE + io_uring: don't audit the capability check in io_uring_create() + gpio: tps68470: Make tps68470_gpio_output() always set the initial value + pwm: Add a stub for devm_pwmchip_add() + gpio: mvebu: Make use of devm_pwmchip_add + gpio: mvebu: fix irq domain leak + btrfs: fix race between quota disable and relocation + i2c: Delete error messages for failed memory allocations + i2c: Improve size determinations + i2c: nomadik: Remove unnecessary goto label + i2c: nomadik: Use devm_clk_get_enabled() + i2c: nomadik: Remove a useless call in the remove function + PCI/ASPM: Return 0 or -ETIMEDOUT from pcie_retrain_link() + PCI/ASPM: Factor out pcie_wait_for_retrain() + PCI/ASPM: Avoid link retraining race + PCI: rockchip: Remove writes to unused registers + PCI: rockchip: Fix window mapping and address translation for endpoint + PCI: rockchip: Don't advertise MSI-X in PCIe capabilities + dlm: cleanup plock_op vs plock_xop + dlm: rearrange async condition return + fs: dlm: interrupt posix locks only when process is killed + drm/ttm: Don't print error message if eviction was interrupted + drm/ttm: Don't leak a resource on eviction error + n_tty: Rename tail to old_tail in n_tty_read() + tty: fix hang on tty device with no_room set + drm/ttm: never consider pinned BOs for eviction + cifs: missing directory in MAINTAINERS file + cifs: use fs_context for automounts + ksmbd: remove internal.h include + cifs: if deferred close is disabled then close files immediately + pwm: meson: Simplify duplicated per-channel tracking + pwm: meson: fix handling of period/duty if greater than UINT_MAX + tracing/probes: Add symstr type for dynamic events + tracing/probes: Fix to avoid double count of the string length on the array + tracing: Allow synthetic events to pass around stacktraces + Revert "tracing: Add "(fault)" name injection to kernel probes" + tracing/probes: Fix to record 0-length data_loc in fetch_store_string*() if fails + scsi: qla2xxx: Remove unused declarations for qla2xxx + scsi: qla2xxx: Multi-que support for TMF + scsi: qla2xxx: Fix task management cmd failure + scsi: qla2xxx: Fix task management cmd fail due to unavailable resource + scsi: qla2xxx: Add debug prints in the device remove path + scsi: qla2xxx: Fix hang in task management + drm/amdgpu: fix vkms crtc settings + drm/amdgpu/vkms: relax timer deactivation by hrtimer_try_to_cancel + phy: qcom-snps: Use dev_err_probe() to simplify code + phy: qcom-snps: correct struct qcom_snps_hsphy kerneldoc + phy: qcom-snps-femto-v2: keep cfg_ahb_clk enabled during runtime suspend + phy: qcom-snps-femto-v2: properly enable ref clock + soundwire: qcom: update status correctly with mask + media: staging: atomisp: select V4L2_FWNODE + i40e: Fix an NULL vs IS_ERR() bug for debugfs_create_dir() + iavf: fix potential deadlock on allocation failure + iavf: check for removal state before IAVF_FLAG_PF_COMMS_FAILED + net: phy: marvell10g: fix 88x3310 power up + net: hns3: fix wrong tc bandwidth weight data issue + net: hns3: fix wrong bw weight of disabled tc issue + vxlan: move to its own directory + vxlan: calculate correct header length for GPE + phy: hisilicon: Fix an out of bounds check in hisi_inno_phy_probe() + ethernet: atheros: fix return value check in atl1e_tso_csum() + ipv6 addrconf: fix bug where deleting a mngtmpaddr can create a new temporary address + ice: Fix memory management in ice_ethtool_fdir.c + bonding: reset bond's flags when down link is P2P device + team: reset team's flags when down link is P2P device + net: stmmac: Apply redundant write work around on 4.xx too + platform/x86: msi-laptop: Fix rfkill out-of-sync on MSI Wind U100 + igc: Fix Kernel Panic during ndo_tx_timeout callback + netfilter: nft_set_rbtree: fix overlap
[Kernel-packages] [Bug 2016995] Re: Azure: Build-in TDX guest driver
This bug was fixed in the package linux-azure - 6.5.0-1004.4 --- linux-azure (6.5.0-1004.4) mantic; urgency=medium * mantic/linux-azure: 6.5.0-1004.4 -proposed tracker (LP: #2034548) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) * Azure: net: mana: Add page pool for RX buffers (LP: #2034277) - net: mana: Add page pool for RX buffers [ Ubuntu: 6.5.0-5.5 ] * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 16:34:24 +0200 ** Changed in: linux-azure (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2016995 Title: Azure: Build-in TDX guest driver Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-5.19 package in Ubuntu: Invalid Status in linux-azure source package in Jammy: Invalid Status in linux-azure-5.19 source package in Jammy: Fix Released Status in linux-azure source package in Kinetic: Fix Released Status in linux-azure-5.19 source package in Kinetic: Invalid Status in linux-azure source package in Lunar: Fix Released Status in linux-azure-5.19 source package in Lunar: Invalid Bug description: SRU Justification [Impact] The TDX guest driver is currently packaged in linux-modules-extra. This is a non-optimal experience for users of the Azure image that is focused on TDX encryption and security. [Fix] Build in the TDX guest driver [Test Plan] Check that the TDX guest driver no longer appears in linux-modules-extra Microsoft tested as well. [Regression potential] There should be no regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2016995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018591] Re: Enable Tracing Configs for OSNOISE and TIMERLAT
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018591 Title: Enable Tracing Configs for OSNOISE and TIMERLAT 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: == SRU Justification == These config changes will allow tracing with the OSNOISE and TIMERLAT tracing tools. These tracers can be enabled at run-time and should not affect performance or add any additional overhead. == Fix == UBUNTU: [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs == Regression Potential == Low. These config changes will just allow the use of tracing tools. == Test Case == Test build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2021949 Title: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Enabling CL1 (Controller Low Power) states during discovery of existing tunnels established by the system firmware can interfere with the operation of those tunnels. The DisplayPort tunnel establishment timeout of 1.5 seconds can be insufficient for some docking stations, leading to blank displays. [Fix] CL1 states are now not enabled during discovery of existing tunnels. The TMU settings also remain unchanged. The timeout is increased to 3 seconds to allow more time for the DisplayPort connection manager handshake, fixing the issue of displays remaining blank. [Test Cases] 1. plug docking station on the host 2. bring up the host and get into desktop. 3. flip docking station's cable. 4. check if the external monitor works well [Where problems could occur] Low, If the handshake actually requires even more than 3 seconds in some cases, the timeout may still need to be increased further. [Misc] Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a huge, so skip Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2021949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 was fixed in the package linux - 6.5.0-5.5
---
linux (6.5.0-5.5) mantic; urgency=medium
* mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
- debian/dkms-versions -- update from kernel-versions (main/d2023.08.23)
-- Andrea Righi Wed, 06 Sep 2023 15:51:04
+0200
** Changed in: linux (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to 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 Committed
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
Fix 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 2034277] Re: Azure: net: mana: Add page pool for RX buffers
This bug was fixed in the package linux-azure - 6.5.0-1004.4 --- linux-azure (6.5.0-1004.4) mantic; urgency=medium * mantic/linux-azure: 6.5.0-1004.4 -proposed tracker (LP: #2034548) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) * Azure: net: mana: Add page pool for RX buffers (LP: #2034277) - net: mana: Add page pool for RX buffers [ Ubuntu: 6.5.0-5.5 ] * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 16:34:24 +0200 ** Changed in: linux-azure (Ubuntu Mantic) Status: Fix Committed => Fix Released -- 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/2034277 Title: Azure: net: mana: Add page pool for RX buffers Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Released Bug description: SRU Justification [Impact] Microsoft has requested this path be added to the 5.15 and 6.2 Azure kernels. Add page pool for RX buffers for faster buffer cycle and reduce CPU usage. [Test Plan] MSFT tested. [Regression Potential] Could cause receive packet corruption. [Other Info] SF: #00365760 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2034277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035398] 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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560
[Kernel-packages] [Bug 2035398] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700689/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device
[Kernel-packages] [Bug 2035398] Re: PM: hibernation: Image mismatch: architecture specific data
Sorry, I am not sure whether I was supposed to change the status of this to "confirmed". Changed it back to "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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp.
[Kernel-packages] [Bug 2035398] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700688/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID
[Kernel-packages] [Bug 2035398] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700690/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => 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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux
[Kernel-packages] [Bug 2035398] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700686/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device
[Kernel-packages] [Bug 2035398] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700687/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID
[Kernel-packages] [Bug 2035398] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700685/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001
[Kernel-packages] [Bug 2035398] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700684/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera
[Kernel-packages] [Bug 2035398] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700682/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID
[Kernel-packages] [Bug 2035398] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700683/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device
[Kernel-packages] [Bug 2035398] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700681/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID
[Kernel-packages] [Bug 2035398] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700678/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID
[Kernel-packages] [Bug 2035398] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700680/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID
[Kernel-packages] [Bug 2035398] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700679/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003:
[Kernel-packages] [Bug 2035398] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700677/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003:
[Kernel-packages] [Bug 2035398] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700676/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001
[Kernel-packages] [Bug 2035398] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700675/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID
[Kernel-packages] [Bug 2011768] Re: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- 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/2011768 Title: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment 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: Incomplete Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] NVME storage disappeared under Dell factory WINPE environment with RAID ON mode when this WINPE boot entry touched by efibootmgr [Fix] Reset the VMD msi remapping during shutdown. [Test Case] 1. Install Ubuntu 2. Then, system will reboot to WINPE to do some cleanup work. 3. in WINPE, the NVME storage could be listed. [Where problems could occur] Low, the issue may be observed on VMD MSI remapping. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035398] Re: PM: hibernation: Image mismatch: architecture specific data
apport information
** Tags added: apport-collected mantic wayland-session
** Description changed:
Using
ii linux-headers-6.5.0-56.5.0-5.5all Header
files related to Linux kernel version 6.5.0
ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux
kernel headers for version 6.5.0 on 64 bit x86 SMP
ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed
kernel image generic
ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux
kernel extra modules for version 6.5.0 on 64 bit x86 SMP
ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux
kernel extra modules for version 6.5.0 on 64 bit x86 SMP
Resuming from hibernation fails with the following error messages:
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0x-0x0fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0x000a-0x000f]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0x99a0a000-0x99a1bfff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0x99a1d000-0x99a1]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0x99a22000-0x99a22fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0x99a24000-0x]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5d44c000-0xa5d44dfff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5d457000-0xa5d457fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5d469000-0xa5d469fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5d46c000-0xa5d4bafff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5d9ac000-0xa5d9acfff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e0f9000-0xa5e0fafff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e11e000-0xa5e125fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e1ea000-0xa5e1edfff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e1fd000-0xa5e205fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e20b000-0xa5e32afff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e33a000-0xa5e33cfff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e33e000-0xa5e33efff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e345000-0xa5e34dfff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e366000-0xa5e369fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e36f000-0xa5e3a1fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e3b7000-0xa5e3bbfff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e3c-0xa5e3d0fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e3e-0xa5e3e1fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps
created
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch:
architecture specific data
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in
0.01 seconds (1614130.00 MB/s)
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image,
recovering.
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps
freed
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1)
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: nbock 7015 F wireplumber
+ /dev/snd/seq:nbock 6996 F pipewire
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 23.10
+ InstallationDate: Installed on 2020-04-17 (1244 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
+ Lsusb:
+ Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0
Camera
+ Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson
Peak (JfP)
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
+ NonfreeKernelModules: zfs
+ Package: linux (not installed)
+ ProcEnviron:
+ LANG=en_US.UTF-8
+ PATH=(custom, no user)
+
[Kernel-packages] [Bug 2017444] Re: Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20
This bug was fixed in the package linux - 6.5.0-5.5
---
linux (6.5.0-5.5) mantic; urgency=medium
* mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
- debian/dkms-versions -- update from kernel-versions (main/d2023.08.23)
-- Andrea Righi Wed, 06 Sep 2023 15:51:04
+0200
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2017444
Title:
Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-firmware source package in Lunar:
Invalid
Bug description:
== SRU Justification ==
[Impact]
Some Atom based system cannot boot on kernel 6.2 because of atomisp
driver.
[Fix]
Disable the driver via config, suggested by the driver dev.
[Test]
Users confirmed disabling the config works.
[Where problems could occur]
The ISP camera dever worked on Linux. So disabling it shouldn't
introduce any surprise.
== Original Bug Report ==
Computers with Intel Atom CPU will not boot with Kernel 6.2.0-20 OR any other
Kernel in 6.2 series or Kernel 6.3.0.
This bug affects all Intel Atom CPU computers in all Linux
distributions making impossible to install or boot to OS with kernel
6.2 or higher.
The bug is caused by Intel atomisp camera driver module which has
firmware missing: shisp_2401a_v21.bin. Missing firmware causes a
watchdog bug notice and Soft Lockup of boot sequence.
NEW SOLUTION AND NOTICE TO UBUNTU KERNEL MAINTAINERS, April 29th:
The following persons are in charge of atomisp kernel development:
Hans de Goede (maintainer:STAGING - ATOMISP DRIVER)
Mauro Carvalho Chehab (maintainer:STAGING - ATOMISP
DRIVER)
Sakari Ailus (reviewer:STAGING - ATOMISP
DRIVER)
Greg Kroah-Hartman (supporter:STAGING SUBSYSTEM)
linux-me...@vger.kernel.org (open list:STAGING - ATOMISP DRIVER)
linux-stag...@lists.linux.dev (open list:STAGING SUBSYSTEM)
linux-ker...@vger.kernel.org (open list)
April 29th Hans de Goede adviced me personally(
https://github.com/linux-surface/linux-surface/issues/1095 ), that
atomisp driver is still in development and should be disabled. By
disabling driver he meant disabling atomisp modules in kernel.
OLD SOLUTION FOR THIS BUG:
Copying (installing) firmware shisp_2401a0_v21.bin from:
https://github.com/intel-aero/meta-intel-aero-
base/blob/master/recipes-kernel/linux/linux-yocto/shisp_2401a0_v21.bin
to /lib/firmware will solve the bug (partially - it still gives error
messages - but at least the computer boots).**
(dmesg.log with shisp-file with kernel 6.2.0-06 and 6.3.0-06 as
attachments 9. and 10.)
(Another solution - which Manjaro kernel maintainer did - was to
disable atomisp and related modules).
Afterwards Intel Atom CPU computer will be able to boot with kernel
6.2.
DMESG.LOG OF KUBUNTU 23.04 LIVE USB AND MORE INFORMATION IN:
https://askubuntu.com/questions/1464926/not-able-to-boot-
kubuntu-23-04-with-kernel-6-2-and-intel-atom-cpu
The last stable Ubuntu Kernel Intel Atom CPU computer will boot with
is 6.1.25.
This bug was already in 5.19, as you can see from dmesg.logs. It
appears that atomisp failes to launch in both 5.19.0-40 and 6.1.25 but
still the computer boots.
This bug is also reported in Manjaro ( " https://github.com/linux-
surface/linux-surface/issues/1095 ")and Arch Linux ("
https://bbs.archlinux.org/viewtopic.php?id=283920 ") so it is not
limited to Ubuntu Kernels.
This bug has already been reported for Ubuntu 23.04 Beta in Ubuntu
bugtracking system (" https://www.mail-archive.com/kernel-
packa...@lists.launchpad.net/msg501664.html ") with Bug number
#2015794.
Attachments:
1. Picture of stuck boot sequence of HP x2 210 G2 with Intel Atom CPU trying
to boot in to Kubuntu 23.04 with Kernel 6.2.0-20.
2. dmesg.log of the computer with Ubuntu Kernel 6.1.25.
3. xsession-errors of the computer with Ubuntu Kernel 6.1.25.
4. dmesg.log of the computer with Ubuntu Kernel 5.19.0-40.
5. Video of boot sequence with Kernel 6.2.0-20.
6. uname-a.log of Kernel 6.1.25.
7. lspci-vvnn.log of Kernel 6.1.25.
8. version.log of Kernel 5.19.0-40.
9. dmesg.log with shisp-file with ubuntu kernel 6.2.0-06.**
10. dmesg.log with shisp-file with ubuntu kernel 6.3.0-06**
P.S. The apport-collect data is from Kernel 5.19.0-40.
P.S.P.S I had difficulty determining Tags so they are to be changed by you.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017444/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 2018303] Re: move sev-guest module from linux-modules-extra to linux-modules
This bug was fixed in the package linux-aws - 6.5.0-1005.5 --- linux-aws (6.5.0-1005.5) mantic; urgency=medium * mantic/linux-aws: 6.5.0-1005.5 -proposed tracker (LP: #2034547) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) [ Ubuntu: 6.5.0-5.5 ] * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 16:21:02 +0200 ** Changed in: linux-aws (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2018303 Title: move sev-guest module from linux-modules-extra to linux-modules Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Kinetic: Fix Committed Status in linux-aws source package in Lunar: Fix Released Status in linux-aws source package in Mantic: Fix Released Bug description: AWS did recently announce AMD SEV-SNP support (see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sev-snp.html. To have that working in the ubuntu AWS images, the module needs to be available (linux-modules-extra is not installed by default). So please move the module to linux-modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2018303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023629] Re: enable multi-gen LRU by default
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2023629 Title: enable multi-gen LRU by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] Kernels >= 6.1 have the option to use an alternative least-recently- used (LRU) page reclaiming mechanism, called multi-gen LRU (MGLRU) [1]. In short: the kernel used to maintain two LRU lists of "touched" pages: the "active" and "inactive" list. The former contains pages thought to be likely used in the future (working set), while the latter contains pages thought to be less likely used and therefore likely to be reclaimed when needed. Pages accessed more frequently are moved to the active list, while pages accessed less frequently are moved to the inactive list. The MGLRU generalizes this concept into multiple generations, instead of just using two lists. Pages move from older to newer generations when they are accessed and pages from older generations are reclaimed first when memory is needed. Generations age over time with new generations being created as the oldest ones are fully reclaimed. Fedora [2] and Archlinux [3] both have MGLRU enabled by default and there are plans to enable this also in Debian and openSUSE. We should also consider to enable this option across the board for Mantic, considering that in the future MGLRU is likely to become the default page reclaiming policy in the kernel. [1] https://lwn.net/Articles/856931/ [2] https://koji.fedoraproject.org/koji/buildinfo?buildID=2168435 [3] https://archlinux.org/packages/core/x86_64/linux-lts/ [Test case] Apache, MariaDB, memcached, MongoDB, PostreSQL, Redis benchmarks can all show a performance improvement in terms of operations per sec switching to MGLRU. [Fix] Set CONFIG_LRU_GEN_ENABLED=y in config/annotations. [Regression potential] This change is going to affect the page reclaiming policy in the kernel, so a lot of workloads can be potentially affected by this change. We may experience *performance regressions* especially in those systems that are running memory intensive workloads or doing large amount of I/O (page cache being stressed and lots of page reclaiming events are happening in the system). However, considering the benefits of this change, especially in the cloud/server-oriented scenario, and also considering that this option is likely to become the "default" page reclaiming mechanism in the kernel, it makes sense to start using it now so that we can catch potential regressions in advance and act accordingly. Moreover, this option can still be adjusted at run-time via /sys/kernel/mm/lru_gen/enabled, so it's very easy to mitigate any potential regression and rollback to the old behavior if needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023629/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025195] Re: HDMI output with More than one child device for port B in VBT error
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2025195 Title: HDMI output with More than one child device for port B in VBT error Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The HDMI monitor doesn't work, no events while plug/unplug then cable. [Fix] From the bug report[1], skip the return workaround the issue, so I created the DMI quirk to list affected platforms. Intel is submitting patches[2][3] to fix the issue, but it requires to backport huge drm structure changes, too. As there is no regression found with this workaround, it's safer to use the DMI quirk to handle this issue. 1. https://gitlab.freedesktop.org/drm/intel/-/issues/7709 2. https://patchwork.freedesktop.org/series/117641/ 3. https://patchwork.freedesktop.org/series/114200/ [Test] Verified by me, FE, and ODM. [Where problems could occur] I have no idea what might happen, so only make the workaround avaiable on the listed platforms. So far, no regressions have been observed with plug/unplug, switch modes, reboot, and suspend tests. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025538] Re: Unrequested kernel update
This bug was fixed in the package nvidia-graphics-drivers-535 - 535.104.05-0ubuntu4 --- nvidia-graphics-drivers-535 (535.104.05-0ubuntu4) mantic; urgency=medium * debian/rules: - Do not start the systemd services on installation or upgrade, as this can lead to a black screen. -- Alberto Milone Thu, 31 Aug 2023 09:06:31 + ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025265] Re: Remove non-LPAE kernel flavor
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025265 Title: Remove non-LPAE kernel flavor Status in linux package in Ubuntu: Fix Released Bug description: The LPA (large physical address) extension is an optional extension currently supported by the Cortex-A7, Cortex-A12, and Cortex-A15 processors. The main generic Ubuntu armhf kernel is not supposed to run on older 32-bit processors or 32-bit processors that don't have this extension. So let's drop the non-LPAE flavor. We currently provide two armhf flavors: generic (LPAE disabled) and generic-lpae (LPAE enabled). Change the generic flavor to be LAPE- enabled and remove the generic-lpae flavor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025265/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025672] Re: Support Realtek RTL8852CE WiFi 6E/BT Combo
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2025672 Title: Support Realtek RTL8852CE WiFi 6E/BT Combo Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Invalid Status in linux-firmware source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2025672 [Impact] Realtek RTL8852CE WiFi 6E/BT Combo takes new firmware to enable 6E features. [Fix] * Bluetooth - kernel + 8b1d66b50437 Bluetooth: btrtl: Add support for RTL8852C (v5.19-rc1) + 9a24ce5e29b1 Bluetooth: btrtl: Firmware format v2 support (v6.4-rc1) + bd003fb338af Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C (linux-next) - firmware + 8a2d81176 rtl_bt: Add firmware and config files for RTL8852C (jammy) + d3c922805 rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33 (jammy) + cfbd66816 rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A (jammy) + c51488ffb rtl_bt: Update RTL8852C BT USB firmware to 0xD7B8_FABF (lunar) + 55e744853 rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225 (mantic, change binary format) + 7ed62638b Revert "rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225" (mantic) + 42d31f8f6 rtl_bt: Add firmware v2 file for RTL8852C (mantic) * WiFi - kernel + 59b4cc439f18 wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() (linux-next) - firmware + d2aac63b8 rtw89: 8852c: update fw to v0.27.56.1 (jammy) + 9e91f0ce6 rtw89: 8852c: update fw to v0.27.56.8 (lunar) + c9c19583f rtw89: 8852c: update fw to v0.27.56.9 (lunar) + fc5a25fa0 rtw89: 8852c: update fw to v0.27.56.10 (lunar) + b9c8e9f70 rtw89: 8852c: update fw to v0.27.56.13 (mantic) [Test Case] Basic bluetooth, wifi operations. This is verified with all related kernel/series combinations: * linux-hwe5.19/jammy * linux-hwe-6.2/jammy * linux-oem-6.0/jammy * linux-oem-6.1/jammy * linux-oem-6.5/jammy * ilnux/mantic [Where problems could occur] New device firmware blob, even blob format changes. Expect bugs, power consumption issues, etc. [Other Info] Bluetooth V2 firmware support was first landed to v6.4, and the binary rename in linux-next now. To preserve consistency, Unstable, Mantic and OEM-6.5 kernels are nominated for fix. As for linux-firmware, the only target is Jammy. == original bug description == Support Realtek RTL8852CE WiFi 6E/BT Combo * Bluetooth - kernel + 8b1d66b50437 Bluetooth: btrtl: Add support for RTL8852C (v5.19-rc1) + 9a24ce5e29b1 Bluetooth: btrtl: Firmware format v2 support (v6.4-rc1) + bd003fb338af Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C (linux-next) - firmware + 8a2d81176 rtl_bt: Add firmware and config files for RTL8852C (jammy) + d3c922805 rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33 (jammy) + cfbd66816 rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A (jammy) + c51488ffb rtl_bt: Update RTL8852C BT USB firmware to 0xD7B8_FABF (lunar) + 55e744853 rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225 (mantic, change binary format) + 7ed62638b Revert "rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225" (mantic) + 42d31f8f6 rtl_bt: Add firmware v2 file for RTL8852C (mantic) * WiFi - kernel + 59b4cc439f18 wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() (linux-next) - firmware + d2aac63b8 rtw89: 8852c: update fw to v0.27.56.1 (jammy) + 9e91f0ce6 rtw89: 8852c: update fw to v0.27.56.8 (lunar) + c9c19583f rtw89: 8852c: update fw to v0.27.56.9 (lunar) + fc5a25fa0 rtw89: 8852c: update fw to v0.27.56.10 (lunar) + b9c8e9f70 rtw89:
[Kernel-packages] [Bug 2026622] Re: package nvidia-firmware-535-server-535.54.03 (not installed) failed to install/upgrade: a tentar sobre-escrever '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', que
This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.104.05-0ubuntu1
---
nvidia-graphics-drivers-535-server (535.104.05-0ubuntu1) mantic; urgency=medium
[ Alberto Milone ]
* New upstream release (LP: #2025243).
* debian/rules{.defs}:
- Adjust to the changes on the Nvidia servers.
* debian/rules:
- Do not start the systemd services on installation or upgrade, as this can
lead to a black screen.
[ Dimitri John Ledkov ]
* debian/templates/control.in:
- Add breaks on identical firmware files from other flavour.
When 535 & 535-server driver versions happen to be at an identical
upstream version, they both ship identical firmware files on disk at
the same path. When a user attempts to install two drivers at the same
time, this results in dpkg file conflict. Allow replacing one firmware
with another (LP: #2026622).
-- Alberto Milone Wed, 30 Aug 2023
13:35:24 +
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2026622
Title:
package nvidia-firmware-535-server-535.54.03 (not installed) failed to
install/upgrade: a tentar sobre-escrever
'/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', que também está no
pacote nvidia-firmware-535-535.54.03 535.54.03-0ubuntu0.20.04.4
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Fix Released
Bug description:
I tried install the driver : nvidia-driver-535-server-open - distro
non-free recommended using the apt install command, but the error
below returns and the driver install was not complete.
"dpkg: erro ao processar o arquivo
/tmp/apt-dpkg-install-xKiKWI/10-nvidia-firmware-535-server-535.54.03_535.54.03-0ubuntu0.20.04.1_am
d64.deb (--unpack):
a tentar sobre-escrever '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', que
também está no pacote nvidia-firmware-535-535.54.03 535
.54.03-0ubuntu0.20.04.4
dpkg-deb: erro: o subprocesso colar foi morto pelo sinal (Pipe quebrado)
A seleccionar pacote anteriormente não seleccionado
nvidia-kernel-common-535-server.
A preparar para desempacotar
.../11-nvidia-kernel-common-535-server_535.54.03-0ubuntu0.20.04.1_amd64.deb ...
A descompactar nvidia-kernel-common-535-server (535.54.03-0ubuntu0.20.04.1)
...
A seleccionar pacote anteriormente não seleccionado
nvidia-dkms-535-server-open.
A preparar para desempacotar
.../12-nvidia-dkms-535-server-open_535.54.03-0ubuntu0.20.04.1_amd64.deb ...
A descompactar nvidia-dkms-535-server-open (535.54.03-0ubuntu0.20.04.1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-utils-535-server.
A preparar para desempacotar
.../13-nvidia-utils-535-server_535.54.03-0ubuntu0.20.04.1_amd64.deb ...
A descompactar nvidia-utils-535-server (535.54.03-0ubuntu0.20.04.1) ...
A seleccionar pacote anteriormente não seleccionado
xserver-xorg-video-nvidia-535-server.
A preparar para desempacotar
.../14-xserver-xorg-video-nvidia-535-server_535.54.03-0ubuntu0.20.04.1_amd64.deb
...
A descompactar xserver-xorg-video-nvidia-535-server
(535.54.03-0ubuntu0.20.04.1) ...
A seleccionar pacote anteriormente não seleccionado
nvidia-driver-535-server-open.
A preparar para desempacotar
.../15-nvidia-driver-535-server-open_535.54.03-0ubuntu0.20.04.1_amd64.deb ...
A descompactar nvidia-driver-535-server-open (535.54.03-0ubuntu0.20.04.1) ...
Erros foram encontrados durante o processamento de:
/tmp/apt-dpkg-install-xKiKWI/10-nvidia-firmware-535-server-535.54.03_535.54.03-0ubuntu0.20.04.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)"
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-firmware-535-server-535.54.03 (not installed)
ProcVersionSignature: Ubuntu 5.14.0-1044.49-oem 5.14.21
Uname: Linux 5.14.0-1044-oem x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jul 8 12:25:00 2023
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85
ErrorMessage: a tentar sobre-escrever
'/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', que também está no pacote
nvidia-firmware-535-535.54.03 535.54.03-0ubuntu0.20.04.4
InstallationDate: Installed on 2023-06-15 (22 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.19.7ubuntu3.2
apt 2.0.9
SourcePackage:
[Kernel-packages] [Bug 2028122] Re: Fix unreliable ethernet cable detection on I219 NIC
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to 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 Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix 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 2028253] Re: update apparmor and LSM stacking patch set
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028253 Title: update apparmor and LSM stacking patch set Status in linux package in Ubuntu: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] Provide an updated patch set for apparmor / LSM stacking with all the custom features that we need in the Ubuntu kernel. This patch set is required to provide the proper confinement with snaps and other Ubuntu-specific security features. [Fix] Apply the latest updated patch set from: https://gitlab.com/jjohansen/apparmor-kernel [Test case] Run the apparmor test case suite. [Regression potential] This patch set introduces significant non-upstream changes to the security layer, so we may expect generic regressions in the kernel, especially running applications that are stressing the security layer (such as systemd, snapd, lxd, etc.). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028125] Re: Update the NVIDIA 535 series to 535.86.05
This bug was fixed in the package nvidia-graphics-drivers-535 - 535.104.05-0ubuntu4 --- nvidia-graphics-drivers-535 (535.104.05-0ubuntu4) mantic; urgency=medium * debian/rules: - Do not start the systemd services on installation or upgrade, as this can lead to a black screen. -- Alberto Milone Thu, 31 Aug 2023 09:06:31 + ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2028125 Title: Update the NVIDIA 535 series to 535.86.05 Status in fabric-manager-535 package in Ubuntu: Fix Released Status in libnvidia-nscq-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535-server package in Ubuntu: Triaged Status in fabric-manager-535 source package in Focal: New Status in libnvidia-nscq-535 source package in Focal: New Status in nvidia-graphics-drivers-535 source package in Focal: Fix Released Status in nvidia-graphics-drivers-535-server source package in Focal: New Status in fabric-manager-535 source package in Jammy: New Status in libnvidia-nscq-535 source package in Jammy: New Status in nvidia-graphics-drivers-535 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535-server source package in Jammy: New Status in fabric-manager-535 source package in Kinetic: Won't Fix Status in libnvidia-nscq-535 source package in Kinetic: Won't Fix Status in nvidia-graphics-drivers-535 source package in Kinetic: Won't Fix Status in nvidia-graphics-drivers-535-server source package in Kinetic: Won't Fix Status in fabric-manager-535 source package in Lunar: New Status in libnvidia-nscq-535 source package in Lunar: New Status in nvidia-graphics-drivers-535 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-535-server source package in Lunar: New Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2028125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028568] Re: Ship kernel modules Zstd compressed
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028568 Title: Ship kernel modules Zstd compressed Status in linux package in Ubuntu: Fix Released Bug description: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html and https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029281] Re: Soundwire support for Dell SKU0C87 devices
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/2029281 Title: Soundwire support for Dell SKU0C87 devices Status in HWE Next: New Status in firmware-sof package in Ubuntu: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Incomplete Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Mantic: Incomplete Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2029281 [Impact] Missing soundwire support for Dell SKU0C87 deivces. [Fix] * bin: https://github.com/thesofproject/sof/pull/7911 * kernel: https://github.com/thesofproject/linux/pull/4468 [Test Case] Test audio functions on Tributo MTL platforms. [Where problems could occur] New devices, may need further polishments. [Other Info] This is for Intel MTL based platforms, so only OEM-6.5, Mantic, and Unstable are nominated for fix. == original bug description == kernel: sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4 kernel: sof-audio-pci-intel-mtl :00:1f.3: Direct firmware load for intel/sof-ipc4/mtl/sof-mtl.ri failed with error -2 kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof firmware file is missing, you might need to kernel: sof-audio-pci-intel-mtl :00:1f.3: download it from https://github.com/thesofproject/sof-bin/ kernel: sof-audio-pci-intel-mtl :00:1f.3: error: failed to load DSP firmware -2 kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof_probe_work failed err: -2 kernel: kauditd_printk_skb: 33 callbacks suppressed Required fixes: * bin: https://github.com/thesofproject/sof/pull/7911 * kernel: https://github.com/thesofproject/linux/pull/4468 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2029281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030745] Re: Support initrdless boot on default qemu virt models and openstack
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2030745 Title: Support initrdless boot on default qemu virt models and openstack Status in linux package in Ubuntu: Fix Released Bug description: Currently qemu & openstack for the most simple invocations of "virtio" drive type use virtio-blk. One can use virtio-scsi, and many do, but it's not a given. To continue support minimal images without initrd, and enable in-place no-change migration, we should also make virtio-blk builtin. This can be revisited once openstack & qemu defaults change to virtio- scsi (if ever). Test cases: Qemu with `-drive if=virtio,format=$format,file=$image` should work, requires virtio-blk today. Qemu with `-device virtio-scsi-pci,id=scsi0 \ -drive if=none,id=rootfs,format=$format,file=$image -device scsi-hd,drive=rootfs,bus=scsi0.0"` already works, requires virtio-scsi, and should continue to work. Openstack with openstack image create \ --container-format bare \ --disk-format qcow2 \ --file my-minimal.qcow2 should work and currently requires virtio-blk. Openstack with openstack image create \ --container-format bare \ --disk-format qcow2 \ --property hw_disk_bus=scsi \ --property hw_scsi_model=virtio-scsi \ --file my-minimal.qcow2 already works, and should continue to work, requires virtio-scsi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032174] Re: Got soft lockup CPU if dell_uart_backlight is probed
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032174 Title: Got soft lockup CPU if dell_uart_backlight is probed Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] After v6.5, calls tty->driver->ops->chars_in_buffer() may lead to a deadlock and got soft lockup error. [Fix] Do not use this function in dell-uart-backlight driver. Try using tty->driver->ops->flush_chars() to send out the commands. [Test Case] 1. Boot up Dell AIO system with v6.5 kernel. 2. Check dmesg and make sure there is no soft lockup error message in it. [Where problems could occur] There is no functional change, even if uart_flush_chars() doesn't do what we expected, the driver should be able to keep workings, as the backlight commands is only 3 or 4 bytes short and has little chance to stay in the queue partially. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032704] Re: Fix panel brightness issues on HP laptops
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2032704 Title: Fix panel brightness issues on HP laptops Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Brightness can't be changed or can only be changed once on some modern HP laptops. [Fix] BIOS folks identified the issue where the ACPI _PS0 method isn't called for the panel device. On Windows the method is being invoked. This is due to missing _PSC, but since Windows is the de facto spec, we have to perform the same to make the device functional. [Test] Once the fix is applied, the brightness can be changed smoothly. [Where problems could occur] According to BIOS folks, Windows also invokes _PS3 for sleep and shutdown, we need to tackle that in the future. Right now not calling _PS3 has no ill-effect, per BIOS folks. X-HWE-Bug: Bug #2032704 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032959] Re: ceph: support idmapped mounts
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032959 Title: ceph: support idmapped mounts Status in linux package in Ubuntu: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] Now that zfs supports idmapped mounts the only user of shiftfs remains ceph. However a patch set has been posted upstream to enable such feature also in ceph: https://lore.kernel.org/all/20230807132626.182101-1-aleksandr.mikhalit...@canonical.com/ This is also maintained in this github repository: https://github.com/ceph/ceph-client.git Include this patch in our mantic kernel, so that the LXD team can do some testing to see if we can get rid of shiftfs and rely completely on upstream idmapped mounts. [Test case] Create an LXD container using a ceph backend, disable shiftfs and verify if everything is still working (LXD team will provide a proper test case for this). [Fix] Apply idmapped mounts patch set from: https://github.com/ceph/ceph-client.git [Regression potential] This patch set is still not upstream and still experimental, therefore we may experience regression or system crashes in systems that are using the ceph filesystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032959/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032767] Re: Fix ACPI TAD on some Intel based systems
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2032767 Title: Fix ACPI TAD on some Intel based systems Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] ACPI TAD doesn't really work on several systems. When accessing TAD interface via sysfs, like setting/getting realtime, it also causes errors: [ 478.255453] ACPI Error: No handler for Region [RTCM] (a8d2dd39) [SystemCMOS] (20230331/evregion-130) [ 478.255458] ACPI Error: Region SystemCMOS (ID=5) has no handler (20230331/exfldio-261) [ 478.255461] Initialized Local Variables for Method [_GRT]: [ 478.255461] Local1: f182542cInteger [ 478.255464] No Arguments are initialized for method [_GRT] [ 478.255465] ACPI Error: Aborting method \_SB.AWAC._GRT due to previous error (AE_NOT_EXIST) (20230331/psparse-529) [Fix] Let the driver to install a handler for its SystemCMOS region. The spec on whether certain devices can use SystemCMOS or not is quite vague, so follow the de facto implementation, Windows :) [Test] Once the patch is applied, setting and getting realtime through TAD sysfs work, and there's no more error in dmesg. [Where problems could occur] Now ACPI TAD driver also depends on ACPI RTC driver, so the memory usage will go up slightly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033025] Re: Fix numerous AER related issues
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Changed in: linux (Ubuntu Focal) Importance: Medium => High ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => In Progress ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837227 Title: systemd mount units fail during boot, while file system is correctly mounted Status in systemd: New Status in Ubuntu Pro: In Progress Status in Ubuntu Pro 18.04 series: In Progress Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in systemd source package in Bionic: Won't Fix Status in linux source package in Focal: Fix Committed Status in systemd source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] systemd mount units fail during boot, and the system boots into emergency mode [Test Plan] This issue seems to happen randomly, and doesn't seem related to a specific mount unit. We've used a test script with good results during investigation to reproduce similar mount failures in a running system, and have seen a strong correlation between the script failures and the boot time mount failures. The attached 'rep-tmpfs.sh' script should be used to validate that mount points are working correctly under stress. One can run through the different variants as below: # ./rep-tmpfs.sh --variant-0 # ./rep-tmpfs.sh --variant-1 # ./rep-tmpfs.sh --variant-2 # ./rep-tmpfs.sh --variant-3 # ./rep-tmpfs.sh --variant-4 All of these should run successfully without any reported errors. [Where problems could occur] The patches change the way systemd tracks and handles mount points in general, so potential regressions could affect other mount units. We should keep an eye out for any issues with mounting file systems, as well as rapid mount/unmount operations. Successful test runs with the reproducer script should increase reliability in having no new regressions. [Other Info] This has been tackled upstream with several attempts, which have resulted in the final patch from 2022: 01400460ae16 core/mount: adjust deserialized state based on /proc/self/mountinfo For Bionic, systemd requires several dependency patches as below: 6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a new unit cycle 7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the other way round 350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() results 1d086a6e5972 mount: mark an existing "mounting" unit from /proc/self/mountinfo as "just_mounted" Additionally, the kernel also requires the following patches: 28ca0d6d39ab list: introduce list_for_each_continue() 9f6c61f96f2d proc/mounts: add cursor [Original Description] In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode with a failed mount unit (ext4 file system), while the corresponding file system is in fact correctly mounted. It happens roughly once every 1000 reboots. It seems to be related with this bug : https://github.com/systemd/systemd/issues/10872 Is it possible to apply the fix (https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21) in Ubuntu 18.04 ? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1837227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035400] Re: Jammy update: v5.15.124 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/2035400 Title: Jammy update: v5.15.124 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.124 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035398] 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 2035398 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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Incomplete Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 2035400] [NEW] Jammy update: v5.15.124 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.124 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) 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/2035400 Title: Jammy update: v5.15.124 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.124 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035398] [NEW] PM: hibernation: Image mismatch: architecture specific data
Public bug reported: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) ** 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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: New Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29
[Kernel-packages] [Bug 2029905] Re: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS
Previous request
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151
Current driver version in Jammy v5.15 generic kernel with fixes from
above bug report. Any changes on top of it should be inline with SRU
policy and ideally accepted in linux-stable trees if at all possible.
Current driver version in Jammy v6.2-hwe kernel are up to 8.2.0.3.0 and
contain fixes up to the
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025067 which
incorporates fixes up to linux-stable v6.2.15 release
Upcoming Mantic release, and the future Jammy v6.5-hwe kernel will
contain 8.4.1.0.0 with fixes up to f762326b2b ("scsi: mpi3mr: Propagate
sense data for admin queue SCSI I/O") which will be part of the next
22.04 point release.
Everything mentioned in this bug report will be released in Mantic and
hwe kernel in next 22.04 point release.
Thus from Kernel point of view this is all fix-committed and will be
part of the hwe kernel on 22.04. Users that require these changes will
have to use Server Installer and choose hwe kernel, or switch their
installed systems to the hwe kernel.
Individual fixes are suitable for inclusion into the v5.15 generic
kernel, if you provide test-plan, regression risk potential, and
documentation as required at
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Mantic)
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu Mantic)
Milestone: None => ubuntu-23.10
** Changed in: linux (Ubuntu Lunar)
Status: New => Won't Fix
** Changed in: linux (Ubuntu Jammy)
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/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
[Kernel-packages] [Bug 1971151] Re: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971151 Title: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0 7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough 986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs 43ca11005098 scsi: mpi3mr: Add support for PEL commands 506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header f5e6d5a34376 scsi: mpi3mr: Add support for driver commands 4268fa751365 scsi: mpi3mr: Add bsg device support 1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc 4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings 9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails a25eafd13e5f scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() 256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR 2dd8389f96d6 scsi: mpi3mr: Hidden drives not removed during soft reset 1aa529d40025 scsi: mpi3mr: Increase I/O timeout value to 60s [Test Plan] 1. Install and boot kernel 2. Run basic I/O tests [Where problems could occur] Moderate to low regression risk for the kernel as most changes are in the driver [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
Patch submitted for review https://lists.ubuntu.com/archives/kernel- team/2023-September/142739.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
This bug is awaiting verification that the linux-bluefield/5.4.0-1071.77 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-focal-linux-bluefield' to 'verification-done- focal-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-focal-linux-bluefield' to 'verification-failed- focal-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield-v2 verification-needed-focal-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Confirmed Bug description: [Impact] Opened files reported in /proc/pid/map_files can be shows with the wrong mount point using overlayfs with filesystem namspaces. This incorrect behavior is fixed: UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files However, the fix introduced a new regression, the reference to the original file stored in vma->vm_prfile is not properly released when vma->vm_prfile is replaced with a new file. This can cause a reference counter unbalance, leading errors such as "target is busy" when trying to unmount overlayfs, even if the filesystem has not active reference. [Test case] Reproducer provided by original bug reporter: https://launchpadlibrarian.net/663151659/overlayfsscript_example [Fix] Fix by properly releasing the original file stored in vm_prfile. [Regression potential] This fix seems to solve the reported bug (verified with the reproducer) and it doesn't seem to introduce other regressions or behavior change. However, we may experience regressions in overlayfs or potentially other "target is busy" errors when unmounting overlayfs filesystems with this fix applied, if there are still other corner cases not covered properly. [Original bug report] Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem
[Kernel-packages] [Bug 2031022] Re: Fix boot test warning for log_check "CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0"
This bug is awaiting verification that the linux-bluefield/5.4.0-1071.77 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-focal-linux-bluefield' to 'verification-done- focal-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-focal-linux-bluefield' to 'verification-failed- focal-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield-v2 verification-needed-focal-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2031022 Title: Fix boot test warning for log_check "CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0" Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Released Bug description: SRU Justification [Impact] Gather Data Sampling, affecting Intel processors and assigned CVE-2022-40982 introduced this warning.The fix is on microcode, but part of the mitigation on the kernel side is to detect if the microcode update is not there and disable AVX in case it's supported. This needed some reshuffle during initialization so that turning off AVX was possible without it being too late, which also moved the FPU initialization. See commit https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.252=6e60443668978131a442df485db3deccb31d5651 This causes the following warning during boot: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0 Logs: 154609:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.438234] [ cut here ] 154709:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.439198] get of unsupported state 154809:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.439206] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0 154909:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] Modules linked in: 155009:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.4.0-158-lowlatency #175-Ubuntu 155109:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 06/07/2021 155209:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RIP: 0010:get_xsave_addr+0x98/0xb0 155309:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] Code: 7e ff ff ff 48 83 c4 08 5b 5d c3 80 3d ed d8 bc 01 00 75 ae 48 c7 c7 52 76 51 9a 89 75 f4 c6 05 da d8 bc 01 01 e8 1a c8 a7 00 <0f> 0b 8b 75 f4 eb 91 31 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 155409:02:40 INFO | Aug 10 09:01:05 akis systemd-udevd[3200]: enp58s0np0: Process '/usr/bin/killall -SIGHUP irqbalance' failed with exit code 1. 155509:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RSP: :9ac03e80 EFLAGS: 00010282 155609:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RAX: RBX: 9ae47180 RCX: 00032109e11a 155709:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RDX: 0018 RSI: 9bd8c620 RDI: 0246 155809:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RBP: 9ac03e90 R08: 9bd8c620 R09: 74726f707075736e 155909:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] R10: 74726f707075736e R11: 6574617473206465 R12: 9ae47040 156009:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] R13: 0246 R14: 5a1c7469 R15: 5a1d7ee0 156109:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] FS: () GS:a0840040() knlGS: 156209:02:40 INFO | Aug 10 09:01:05 akis systemd[1]: Starting Load Kernel Module pstore_zone... 156309:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] CS: 0010 DS: ES: CR0: 80050033 156409:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] CR2: a146f000 CR3: 00802c80a001 CR4: 007200b0 156509:02:40 INFO | Aug 10
[Kernel-packages] [Bug 2031093] Re: libgnutls report "trap invalid opcode" when trying to install packages over https
This bug is awaiting verification that the linux-bluefield/5.4.0-1071.77 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-focal-linux-bluefield' to 'verification-done- focal-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-focal-linux-bluefield' to 'verification-failed- focal-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield-v2 verification-needed-focal-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2031093 Title: libgnutls report "trap invalid opcode" when trying to install packages over https Status in ubuntu-kernel-tests: New Status in gnutls28 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in gnutls28 source package in Focal: Confirmed Status in linux source package in Focal: Fix Released Status in gnutls28 source package in Jammy: Confirmed Status in linux source package in Jammy: Fix Released Status in gnutls28 source package in Lunar: Confirmed Status in linux source package in Lunar: Fix Released Bug description: [Impact] When booting linux with Gather Data Sampling mitigations without updated microcode on an affected CPU, AVX will be disabled. This will cause programs connecting to https using gnutls on Jammy to break, including apt and git. [Test case] git clone https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] Works fine with the mitigation disabled by default. [Potential regressions] Users booting on affected parts without microcode updates will be subject to Gather Data Sampling attacks (which can be done by local untrusted attackers), which may leak confidential data, including keys. - When trying to install linux-libc-dev on Oracle BM.Standard2.52 (seems to be the only affected instance) with Jammy 5.15.0-81-generic, it will get interrupted with: E: Method https has died unexpectedly! E: Sub-process https received signal 4. $ sudo apt install linux-libc-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-libc-dev 0 upgraded, 1 newly installed, 0 to remove and 54 not upgraded. Need to get 1353 kB of archives. After this operation, 6943 kB of additional disk space will be used. E: Method https has died unexpectedly! E: Sub-process https received signal 4. From dmesg you will see: [ 1078.750067] traps: https[4572] trap invalid opcode ip:7f3c1e6316be sp:7ffea26b61c0 error:0 in libgnutls.so.30.31.0[7f3c1e50f000+129000] Also, git clone is not working as well. $ git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] libgnutls30 version:3.7.3-4ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035390] [NEW] kvm-amd crashes when loaded at svm_init
Public bug reported: [Impact] Loading kvm-amd crashes at svm_init preventing the use of KVM on AMD systems. [Test case] Load kvm_amd and start a KVM guest. [Potential regression] KVM initialization may be broken. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Critical Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035390 Title: kvm-amd crashes when loaded at svm_init Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [Impact] Loading kvm-amd crashes at svm_init preventing the use of KVM on AMD systems. [Test case] Load kvm_amd and start a KVM guest. [Potential regression] KVM initialization may be broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete
yes. just confirms it takes a while. ** Attachment added: "flame2.html" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+attachment/5700645/+files/flame2.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2021571 Title: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete Status in linux-meta package in Ubuntu: Confirmed Bug description: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028217] Update Released
The verification of the Stable Release Update for thermald has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2028217 Title: MTL: Add support for Meteor Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: Fix Released Status in thermald source package in Kinetic: Won't Fix Status in thermald source package in Lunar: Won't Fix Status in thermald source package in Mantic: Fix Released Bug description: [Impact] * Support thermald on Meteor Lake CPU. [Test Plan] * Use a machine with a Meteor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change adds support for Meteor Lake in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2028217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028217] Re: MTL: Add support for Meteor Lake
This bug was fixed in the package thermald - 2.4.9-1ubuntu0.4 --- thermald (2.4.9-1ubuntu0.4) jammy; urgency=medium * Add support for Meteor Lake (LP: #2028217) -- Koba Ko Thu, 10 Aug 2023 15:36:06 +0800 ** Changed in: thermald (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2028217 Title: MTL: Add support for Meteor Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: Fix Released Status in thermald source package in Kinetic: Won't Fix Status in thermald source package in Lunar: Won't Fix Status in thermald source package in Mantic: Fix Released Bug description: [Impact] * Support thermald on Meteor Lake CPU. [Test Plan] * Use a machine with a Meteor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change adds support for Meteor Lake in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2028217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035278] Re: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios
-- 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/2035278 Title: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios Status in linux package in Ubuntu: Invalid Bug description: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm] ring test on 5 succeeded in 1 usecs [ 10.524808] [drm] UVD initialized successfully. [ 10.525029] snd_hda_intel :01:00.1: bound :01:00.0 (ops
[Kernel-packages] [Bug 2031567] Re: NVIDIA pull requests 2023-08-07, 2023-08-11, 2023-08-22
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed -- 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/2031567 Title: NVIDIA pull requests 2023-08-07, 2023-08-11, 2023-08-22 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Bug description: Apply patches from NVIDIA pull requests sent on 2023-08-07 and 2023-08-11 to jammy:linux-nvidia-tegra. 2023-08-07: Johnny Liu (1): UBUNTU: SAUCE: memory: tegra: add nvlink clients for NVGPU Revanth Kumar Uppala (1): UBUNTU: SAUCE: arm64: configs: Disable BRCMFMAC driver Sandipan Patra (1): UBUNTU: SAUCE: arm64: config: Enable ZRAM config as module Sumit Gupta (1): UBUNTU: SAUCE: soc/tegra: cbb: set ERD bit during resume for error interrupt --- 2023-08-11: Kartik (1): UBUNTU: SAUCE: tty/serial: tegra-tcu: skip esc and ccplex_id Rajkumar Kasirajan (1): UBUNTU: SAUCE: ina3221: add support for summation channel control Revanth Kumar Uppala (2): UBUNTU: SAUCE: arm64: configs: Sanitize arm64 defconfig UBUNTU: SAUCE: arm64: config: Enable configs for nf_tables Wayne Chang (1): UBUNTU: SAUCE: arm64: configs: Set USB_CONFIGFS_F_ACC to y --- 2023-08-22: Ankur Pawar (1): NVIDIA: SAUCE: arm64: configs: disable inbuilt IMX219 driver Bharath H S (2): NVIDIA: SAUCE: configs: Sync defconfigs using make defconfig NVIDIA: SAUCE: configs: Enable nvme target, tcp driver Sumit Gupta (1): NVIDIA: SAUCE: driver: cpufreq: use refclk delta based loop instead of udelay Yi-Wei Wang (1): NVIDIA: SAUCE: arm64: defconfig: Enable CONFIG_DEVFREQ_THERMAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2031567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032954] Re: Re-enable CONFIG_MEMCG on the Tegra kernels
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed -- 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/2032954 Title: Re-enable CONFIG_MEMCG on the Tegra kernels Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: For a time, CONFIG_MEMCG had been disabled by the RT patchset to resolve a bug in its interaction with PREEMPT_RT. This has since been resolved and the Ubuntu RT kernel has re-enabled this configuration option, but this has not been reflected in the Tegra kernels. The Tegra kernels will be updated to have this configuration option enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2032954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035374] [NEW] pwr-mlxbf: update Kconfig with upstream changes
Public bug reported: SRU Justification: [Impact] The Mellanox BlueField power driver (pwr-mlxbf) has a dependency on either the BlueField-2 or BlueField-3 GPIO driver. The current Kconfig does not have the BlueField-3 dependency. [Fix] There is an upstream commit that extends the Kconfig to include the GPIO_MLXBF3 dependency. [Test Case] Build the power driver with and without GPIO_MLXBF2 and GPIO_MLXBF3 present in the kernel configuration. Verify power driver is built. [Regression Potential] * none [Other] * none ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2035374 Title: pwr-mlxbf: update Kconfig with upstream changes Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The Mellanox BlueField power driver (pwr-mlxbf) has a dependency on either the BlueField-2 or BlueField-3 GPIO driver. The current Kconfig does not have the BlueField-3 dependency. [Fix] There is an upstream commit that extends the Kconfig to include the GPIO_MLXBF3 dependency. [Test Case] Build the power driver with and without GPIO_MLXBF2 and GPIO_MLXBF3 present in the kernel configuration. Verify power driver is built. [Regression Potential] * none [Other] * none To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2035374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035373] [NEW] Move nbd module into modules (from -extra)
Public bug reported: Would it be possible to move the "nbd" kernel module from linux-modules- extra-raspi into linux-modules-extra? This would enable NBD-based network boot (which has certain advantages over the NFS-based network boot more traditional in the Pi world, such as permitting services that refuse to run on NFS -- like snapd). ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2035373 Title: Move nbd module into modules (from -extra) Status in linux-raspi package in Ubuntu: New Bug description: Would it be possible to move the "nbd" kernel module from linux- modules-extra-raspi into linux-modules-extra? This would enable NBD- based network boot (which has certain advantages over the NFS-based network boot more traditional in the Pi world, such as permitting services that refuse to run on NFS -- like snapd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2035373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033316] Re: UBUNTU: [Config] optee: Adjust CONFIG_OPTEE_SHM_NUM_PRIV_PAGES to 4
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2033316 Title: UBUNTU: [Config] optee: Adjust CONFIG_OPTEE_SHM_NUM_PRIV_PAGES to 4 Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: New Bug description: SRU Justification: [Impact] This change is needed to OPTEE as the FTPM driver requires 2 contiguous SHMEM pages to boot. Without this change the ftpm_tee_probe function will fail. [Fix] Change the CONFIG_OPTEE_SHM_NUM_PRIV_PAGES from 1 to 4. Note that other SHMEM structures are allocated out of this OPTEE pool as well. [Test Case] Verified the Microsoft TPM 2.0 FTPM is fully functional with this change, running the tpm2-tss Test Suite (mandatory & optional) tests as well as many of the TPM2 Command tools. [Regression Potential] This only has an effect if OPTEE is configured/enabled in the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2033316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715552] Re: VMWare does not start
Just an FYI - I finally figured out a way to get the old VMware-Player to start up on Ubuntu 22.04 LTS. The crash (segmentation fault) mentioned above oddly does *not* happen if you launch VMware like this instead: ubuntu@ubuntu:~$ /usr/lib/vmware/bin/vmplayer That's it! The icon can be made to work too if you edit the 'vmware- player.desktop' file in /usr/share/applications to also invoke the application using the full path to the appLoader application. I did not go back and check this on Ubuntu 20.04 LTS, but I expect that it is the same issue and resolution there. -- 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/1715552 Title: VMWare does not start Status in linux package in Ubuntu: Confirmed Bug description: Under Ubuntu 17.10 beta VMWare 12.5.7 cannot be started: /usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux- gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC symbol `clock_gettime' Works under Ubuntu 17.04 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-13-generic 4.12.0-13.14 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 9336 F pulseaudio /dev/snd/controlC0: wolf 9336 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 07:53:43 2017 HibernationDevice: RESUME=UUID=88d69bc7-ac96-42c6-bf6d-5c912964a63b InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.12.0-13-generic N/A linux-backports-modules-4.12.0-13-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 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/1715552/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
The glibc workaround has been removed from the kernel. This patch only affected users of TDX in CVM images on an Azure paravisor with HCL. -- 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/2011421 Title: TDX azure instances crash during boot because of glibc bug Status in glibc package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in glibc source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Invalid Status in glibc source package in Kinetic: Won't Fix Status in linux-azure source package in Kinetic: Won't Fix Status in glibc source package in Lunar: Fix Released Status in linux-azure source package in Lunar: Fix Committed Bug description: [IMPACT] Glibc in jammy and kinetic is affected by the following bug : https://sourceware.org/bugzilla/show_bug.cgi?id=29953 When cpuid reports no information on a shared cache, the x86_non_temporal_threshold will be set to zero, causing memcpy/memset to behave wrong for mid-sized operations. sysdeps/x86/dl-cacheinfo.h indicates that the minimum value must be 0x4040, but this is not enforced for the default value. The issue was reported because jammy tdx instances are failing to boot (crashing) on azure. The bug has been resolved upstream in https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b [TEST CASE] Test case requires an azure tdx instance. Microsoft has tested a test package with the above commit and confirmed that instances boot successfully. [REGRESSION POTENTIAL] The patches have been accepted upstream. They modify code for x86 architecture, so any potential regression would affect x86. [OTHER] Bug upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=29953 Duplicate bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30037 In jammy we need 2 commits : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b446822b6ae4e8149902a78cdd4a886634ad6321 https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b In kinetic we just need : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2011421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035361] [NEW] [jammy:linux-intel-iot-realtime][TSN] Path delay in realtime kernel is not equal to 0
Public bug reported: This is a public version of https://bugs.launchpad.net/bugs/2030480 [Summary] The command `phc2sys` is to sync the system clock and PTP hardware clock on one machine. The output from `phc2sys` command indicate some information including the `delay`. The `delay` should be 0 if the device is using `hardware cross-timestamping`. In realtime kernel, the `delay` is never 0. But it is 0 in generic kernel (which is correct). This issue also happened on EHL and TGL, which means it may be an all-platform issue caused by realtime kernel. output from realtime kernel --- root@u-Alder-Lake-Client-Platform:/home/u# phc2sys -s "$interface" -O 0 -c CLOCK_REALTIME --step_threshold=1 --transportSpecific=1 -w -m --first_step_threshold=0.0 phc2sys[1021.560]: CLOCK_REALTIME phc offset 3251119 s0 freq -85311 delay 3107 phc2sys[1022.560]: CLOCK_REALTIME phc offset 3255144 s2 freq -81287 delay 2936 phc2sys[1023.560]: CLOCK_REALTIME phc offset 3255167 s2 freq +3173880 delay 2907 phc2sys[1024.560]: CLOCK_REALTIME phc offset -10828 s2 freq +884435 delay 2977 phc2sys[1025.561]: CLOCK_REALTIME phc offset -977556 s2 freq -85541 delay 3385 phc2sys[1026.561]: CLOCK_REALTIME phc offset -973361 s2 freq -374613 delay 2921 phc2sys[1027.561]: CLOCK_REALTIME phc offset -680002 s2 freq -373262 delay 2988 phc2sys[1028.561]: CLOCK_REALTIME phc offset -387940 s2 freq -285201 delay 3392 phc2sys[1029.562]: CLOCK_REALTIME phc offset -183974 s2 freq -197617 delay 3361 phc2sys[1030.562]: CLOCK_REALTIME phc offset -67676 s2 freq -136511 delay 2933 phc2sys[1031.562]: CLOCK_REALTIME phc offset -12389 s2 freq -101527 delay 2976 phc2sys[1032.562]: CLOCK_REALTIME phc offset 7914 s2 freq -84940 delay 2973 phc2sys[1033.563]: CLOCK_REALTIME phc offset 11594 s2 freq -78886 delay 2975 phc2sys[1034.563]: CLOCK_REALTIME phc offset 9221 s2 freq -77781 delay 2931 phc2sys[1035.563]: CLOCK_REALTIME phc offset 5824 s2 freq -78412 delay 2996 phc2sys[1036.563]: CLOCK_REALTIME phc offset 2980 s2 freq -79508 delay 3184 phc2sys[1037.564]: CLOCK_REALTIME phc offset 1216 s2 freq -80378 delay 2926 phc2sys[1038.564]: CLOCK_REALTIME phc offset 400 s2 freq -80830 delay 3126 phc2sys[1039.564]: CLOCK_REALTIME phc offset -29 s2 freq -81139 delay 2985 phc2sys[1040.565]: CLOCK_REALTIME phc offset -133 s2 freq -81251 delay 2991 phc2sys[1041.565]: CLOCK_REALTIME phc offset -135 s2 freq -81293 delay 2941 phc2sys[1042.565]: CLOCK_REALTIME phc offset -40 s2 freq -81239 delay 2952 phc2sys[1043.565]: CLOCK_REALTIME phc offset -43 s2 freq -81254 delay 2975 phc2sys[1044.566]: CLOCK_REALTIME phc offset 43 s2 freq -81181 delay 3306 phc2sys[1045.566]: CLOCK_REALTIME phc offset -105 s2 freq -81316 delay 2970 phc2sys[1046.566]: CLOCK_REALTIME phc offset -4 s2 freq -81246 delay 2944 phc2sys[1047.567]: CLOCK_REALTIME phc offset -14 s2 freq -81257 delay 3098 phc2sys[1048.567]: CLOCK_REALTIME phc offset 28 s2 freq -81220 delay 2944 phc2sys[1049.567]: CLOCK_REALTIME phc offset 64 s2 freq -81175 delay 3181 phc2sys[1050.568]: CLOCK_REALTIME phc offset -27 s2 freq -81247 delay 3027 phc2sys[1051.568]: CLOCK_REALTIME phc offset -19 s2 freq -81247 delay 2930 output from generic kernel (5.15.0-1036-intel-iotg) --- root@u-Alder-Lake-Client-Platform:/home/u# phc2sys -s "$interface" -O 0 -c CLOCK_REALTIME --step_threshold=1 --transportSpecific=1 -w -m --first_step_threshold=0.0 phc2sys[378.423]: CLOCK_REALTIME phc offset 266 s0 freq -96482 delay 0 phc2sys[379.423]: CLOCK_REALTIME phc offset 403 s2 freq -96345 delay 0 phc2sys[380.423]: CLOCK_REALTIME phc offset 380 s2 freq -95965 delay 0 phc2sys[381.424]: CLOCK_REALTIME phc offset -3 s2 freq -96234 delay 0 phc2sys[382.424]: CLOCK_REALTIME phc offset -108 s2 freq -96340 delay 0 phc2sys[383.424]: CLOCK_REALTIME phc offset -131 s2 freq -96395 delay 0 phc2sys[384.424]: CLOCK_REALTIME phc offset -73 s2 freq -96377 delay 0 phc2sys[385.424]: CLOCK_REALTIME phc offset -46 s2 freq -96372 delay 0 phc2sys[386.425]: CLOCK_REALTIME phc offset -27 s2 freq -96366 delay 0 phc2sys[387.425]: CLOCK_REALTIME phc offset 1 s2 freq -96346 delay 0 phc2sys[388.425]: CLOCK_REALTIME phc offset -10 s2 freq -96357 delay 0 phc2sys[389.425]: CLOCK_REALTIME phc offset 7 s2 freq -96343 delay 0 phc2sys[390.425]: CLOCK_REALTIME phc offset -3 s2 freq -96351 delay 0 phc2sys[391.425]: CLOCK_REALTIME phc offset 12 s2 freq -96337 delay 0 phc2sys[392.426]: CLOCK_REALTIME phc offset 6 s2 freq -96339 delay 0 phc2sys[393.426]: CLOCK_REALTIME phc offset -9 s2 freq -96353 delay 0 phc2sys[394.426]: CLOCK_REALTIME phc offset -22 s2 freq -96368 delay 0 phc2sys[395.426]: CLOCK_REALTIME phc offset 11 s2 freq -96342 delay 0 phc2sys[396.426]: CLOCK_REALTIME phc offset 1 s2 freq -96349 delay 0 [Steps to reproduce] The below test steps is based on `616446_Linux_Ethernet_TSN_GSG_2.5` on Intel RDC (you can find it here[1]), this test is on page 28. And we do the TSN tests on `i225` ethernet controller. 1. Locate
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
** Changed in: linux-azure (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: linux-azure (Ubuntu Lunar) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/2011421 Title: TDX azure instances crash during boot because of glibc bug Status in glibc package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in glibc source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Invalid Status in glibc source package in Kinetic: Won't Fix Status in linux-azure source package in Kinetic: Won't Fix Status in glibc source package in Lunar: Fix Released Status in linux-azure source package in Lunar: Fix Committed Bug description: [IMPACT] Glibc in jammy and kinetic is affected by the following bug : https://sourceware.org/bugzilla/show_bug.cgi?id=29953 When cpuid reports no information on a shared cache, the x86_non_temporal_threshold will be set to zero, causing memcpy/memset to behave wrong for mid-sized operations. sysdeps/x86/dl-cacheinfo.h indicates that the minimum value must be 0x4040, but this is not enforced for the default value. The issue was reported because jammy tdx instances are failing to boot (crashing) on azure. The bug has been resolved upstream in https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b [TEST CASE] Test case requires an azure tdx instance. Microsoft has tested a test package with the above commit and confirmed that instances boot successfully. [REGRESSION POTENTIAL] The patches have been accepted upstream. They modify code for x86 architecture, so any potential regression would affect x86. [OTHER] Bug upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=29953 Duplicate bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30037 In jammy we need 2 commits : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b446822b6ae4e8149902a78cdd4a886634ad6321 https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b In kinetic we just need : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2011421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035356] [NEW] Jammy update: v6.1.50 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.1.50 upstream stable release
from git://git.kernel.org/
Linux 6.1.50
ASoC: amd: vangogh: select CONFIG_SND_AMD_ACP_CONFIG
maple_tree: disable mas_wr_append() when other readers are possible
ASoC: amd: yc: Fix a non-functional mic on Lenovo 82SJ
gpio: sim: pass the GPIO device's software node to irq domain
gpio: sim: dispose of irq mappings before destroying the irq_sim domain
dma-buf/sw_sync: Avoid recursive lock during fence signal
pinctrl: renesas: rza2: Add lock around
pinctrl_generic{{add,remove}_group,{add,remove}_function}
pinctrl: renesas: rzv2m: Fix NULL pointer dereference in
rzv2m_dt_subnode_to_map()
pinctrl: renesas: rzg2l: Fix NULL pointer dereference in
rzg2l_dt_subnode_to_map()
clk: Fix undefined reference to `clk_rate_exclusive_{get,put}'
scsi: core: raid_class: Remove raid_component_add()
scsi: snic: Fix double free in snic_tgt_create()
madvise:madvise_free_pte_range(): don't use mapcount() against large folio for
sharing check
can: raw: add missing refcount for memory leak fix
ublk: remove check IO_URING_F_SQE128 in ublk_ch_uring_cmd
thunderbolt: Fix Thunderbolt 3 display flickering issue on 2nd hot plug onwards
cgroup/cpuset: Free DL BW in case can_attach() fails
sched/deadline: Create DL BW alloc, free & check overflow interface
cgroup/cpuset: Iterate only if DEADLINE tasks are present
sched/cpuset: Keep track of SCHED_DEADLINE task in cpusets
sched/cpuset: Bring back cpuset_mutex
cgroup/cpuset: Rename functions dealing with DEADLINE accounting
nfsd: use vfs setgid helper
nfs: use vfs setgid helper
selftests/net: mv bpf/nat6to4.c to net folder
hwmon: (aquacomputer_d5next) Add selective 200ms delay after sending ctrl report
x86/fpu: Set X86_FEATURE_OSXSAVE feature after enabling OSXSAVE in CR4
x86/fpu: Invalidate FPU state correctly on exec()
drm/display/dp: Fix the DP DSC Receiver cap size
drm/i915/dgfx: Enable d3cold at s2idle
drm/vmwgfx: Fix shader stage validation
PCI: acpiphp: Use pci_assign_unassigned_bridge_resources() only for non-root bus
media: vcodec: Fix potential array out-of-bounds in encoder queue_setup
pinctrl: amd: Mask wake bits on probe again
of: dynamic: Refactor action prints to not use "%pOF" inside devtree_lock
of: unittest: Fix EXPECT for parse_phandle_with_args_map() test
radix tree: remove unused variable
riscv: Fix build errors using binutils2.37 toolchains
riscv: Handle zicsr/zifencei issue between gcc and binutils
lib/clz_ctz.c: Fix __clzdi2() and __ctzdi2() for 32-bit kernels
batman-adv: Hold rtnl lock during MTU update via netlink
batman-adv: Fix batadv_v_ogm_aggr_send memory leak
batman-adv: Fix TT global entry leak when client roamed back
batman-adv: Do not get eth header before batadv_check_management_packet
batman-adv: Don't increase MTU when set by user
batman-adv: Trigger events for auto adjusted MTU
selinux: set next pointer before attaching to list
nfsd: Fix race to FREE_STATEID and cl_revoked
NFS: Fix a use after free in nfs_direct_join_group()
mm: memory-failure: fix unexpected return value in soft_offline_page()
mm: add a call to flush_cache_vmap() in vmap_pfn()
mm/gup: handle cont-PTE hugetlb pages correctly in gup_must_unshare() via
GUP-fast
ALSA: ymfpci: Fix the missing snd_card_free() call at probe error
shmem: fix smaps BUG sleeping while atomic
mm,ima,kexec,of: use memblock_free_late from ima_free_kexec_buffer
clk: Fix slab-out-of-bounds error in devm_clk_release()
NFSv4: Fix dropped lock for racing OPEN and delegation return
platform/x86: ideapad-laptop: Add support for new hotkeys found on ThinkBook
14s Yoga ITL
wifi: mac80211: limit reorder_buf_filtered to avoid UBSAN warning
ibmveth: Use dcbf rather than dcbfl
ASoC: cs35l41: Correct amp_gain_tlv values
ASoC: amd: yc: Add VivoBook Pro 15 to quirks list for acp6x
io_uring/msg_ring: fix missing lock on overflow for IOPOLL
io_uring/msg_ring: move double lock/unlock helpers higher up
io_uring: extract a io_msg_install_complete helper
io_uring: get rid of double locking
KVM: x86/mmu: Fix an sign-extension bug with mmu_seq that hangs vCPUs
KVM: x86: Preserve TDP MMU roots until they are explicitly invalidated
bonding: fix macvlan over alb bond support
rtnetlink: Reject negative ifindexes in RTM_NEWLINK
netfilter: nf_tables: fix out of memory error handling
netfilter: nf_tables: flush pending destroy work before netlink notifier
i40e: fix potential NULL pointer dereferencing of pf->vf i40e_sync_vsi_filters()
net/sched: fix a qdisc modification with ambiguous command request
igc: Fix the typo
[Kernel-packages] [Bug 2035357] [NEW] Jammy update: v6.1.51 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.51 upstream stable release from git://git.kernel.org/ Linux 6.1.51 thunderbolt: Fix a backport error for display flickering issue kallsyms: Fix kallsyms_selftest failure io_uring/parisc: Adjust pgoff in io_uring mmap() for parisc parisc: sys_parisc: parisc_personality() is called from asm code parisc: Cleanup mmap implementation regarding color alignment lockdep: fix static memory detection even more ARM: module: Use module_init_layout_section() to spot init sections arm64: module: Use module_init_layout_section() to spot init sections arm64: module-plts: inline linux/moduleloader.h module: Expose module_init_layout_section() ACPI: thermal: Drop nocrt parameter ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New -- 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/2035357 Title: Jammy update: v6.1.51 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Confirmed Status in linux-oem-6.1 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.51 upstream stable release from git://git.kernel.org/ Linux 6.1.51 thunderbolt: Fix a backport error for display flickering issue kallsyms: Fix kallsyms_selftest failure io_uring/parisc: Adjust pgoff in io_uring mmap() for parisc parisc: sys_parisc: parisc_personality() is called from asm code parisc: Cleanup mmap implementation regarding color alignment lockdep: fix static memory detection even more ARM: module: Use module_init_layout_section() to spot init sections arm64: module: Use module_init_layout_section() to spot init sections arm64: module-plts: inline linux/moduleloader.h module: Expose module_init_layout_section() ACPI: thermal: Drop nocrt parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2035357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035358] [NEW] Jammy update: v6.1.52 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.52 upstream stable release from git://git.kernel.org/ Linux 6.1.52 pinctrl: amd: Don't show `Invalid config param` errors usb: typec: tcpci: clear the fault status bit nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers() dt-bindings: sc16is7xx: Add property to change GPIO function tcpm: Avoid soft reset when partner does not support get_status fsi: master-ast-cf: Add MODULE_FIRMWARE macro firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe serial: sc16is7xx: fix bug when first setting GPIO direction serial: sc16is7xx: fix broken port 0 uart init serial: qcom-geni: fix opp vote on shutdown wifi: mt76: mt7921: fix skb leak by txs missing in AMSDU wifi: mt76: mt7921: do not support one stream on secondary antenna only Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race condition staging: rtl8712: fix race condition HID: wacom: remove the battery when the EKR is off usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0 usb: dwc3: meson-g12a: do post init to fix broken usb after resumption ALSA: usb-audio: Fix init call orders for UAC1 USB: serial: option: add FOXCONN T99W368/T99W373 product USB: serial: option: add Quectel EM05G variant (0x030e) modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index mmc: au1xmmc: force non-modular build and remove symbol_get usage ARM: pxa: remove use of symbol_get() ksmbd: reduce descriptor size if remaining bytes is less than request size ksmbd: replace one-element array with flex-array member in struct smb2_ea_info ksmbd: fix slub overflow in ksmbd_decode_ntlmssp_auth_blob() ksmbd: fix wrong DataOffset validation of create context erofs: ensure that the post-EOF tails are all zeroed ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New -- 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/2035358 Title: Jammy update: v6.1.52 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Confirmed Status in linux-oem-6.1 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.52 upstream stable release from git://git.kernel.org/ Linux 6.1.52 pinctrl: amd: Don't show `Invalid config param` errors usb: typec: tcpci: clear the fault status bit nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers() dt-bindings: sc16is7xx: Add property to change GPIO function tcpm: Avoid soft reset when partner does not support get_status fsi: master-ast-cf: Add MODULE_FIRMWARE macro firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe serial: sc16is7xx: fix bug when first setting GPIO direction serial: sc16is7xx: fix broken port 0 uart init serial: qcom-geni: fix opp vote on shutdown wifi: mt76: mt7921: fix skb leak by txs missing in AMSDU wifi: mt76: mt7921: do not support one stream on secondary antenna only Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race condition staging: rtl8712: fix race condition HID: wacom: remove the battery when the EKR is off usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0 usb: dwc3: meson-g12a: do post init to fix broken usb after resumption ALSA: usb-audio: Fix init call orders for UAC1 USB: serial: option: add FOXCONN T99W368/T99W373 product USB: serial:
[Kernel-packages] [Bug 2035359] [NEW] Jammy update: v6.1.53 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.53 upstream stable release from git://git.kernel.org/ ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New -- 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/2035359 Title: Jammy update: v6.1.53 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Confirmed Status in linux-oem-6.1 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.53 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2035359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035355] [NEW] Jammy update: v6.1.49 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.49 upstream stable release from git://git.kernel.org/ Linux 6.1.49 Revert "f2fs: fix to do sanity check on direct node in truncate_dnode()" Revert "f2fs: fix to set flush_merge opt and show noflush_merge" Revert "f2fs: don't reset unchangable mount option in f2fs_remount()" objtool/x86: Fix SRSO mess ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New -- 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/2035355 Title: Jammy update: v6.1.49 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Confirmed Status in linux-oem-6.1 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.49 upstream stable release from git://git.kernel.org/ Linux 6.1.49 Revert "f2fs: fix to do sanity check on direct node in truncate_dnode()" Revert "f2fs: fix to set flush_merge opt and show noflush_merge" Revert "f2fs: don't reset unchangable mount option in f2fs_remount()" objtool/x86: Fix SRSO mess To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2035355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035354] [NEW] Jammy update: v6.1.48 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.48 upstream stable release from git://git.kernel.org/ Linux 6.1.48 x86/srso: Correct the mitigation status when SMT is disabled objtool/x86: Fixup frame-pointer vs rethunk x86/retpoline,kprobes: Fix position of thunk sections with CONFIG_LTO_CLANG x86/srso: Disable the mitigation on unaffected configurations x86/CPU/AMD: Fix the DIV(0) initial fix attempt x86/retpoline: Don't clobber RFLAGS during srso_safe_ret() x86/static_call: Fix __static_call_fixup() x86/srso: Explain the untraining sequences a bit more x86/cpu: Cleanup the untrain mess x86/cpu: Rename srso_(.*)_alias to srso_alias_\1 x86/cpu: Rename original retbleed methods x86/cpu: Clean up SRSO return thunk mess x86/alternative: Make custom return thunk unconditional x86/cpu: Fix up srso_safe_ret() and __x86_return_thunk() x86/cpu: Fix __x86_return_thunk symbol type ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New -- 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/2035354 Title: Jammy update: v6.1.48 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Confirmed Status in linux-oem-6.1 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.48 upstream stable release from git://git.kernel.org/ Linux 6.1.48 x86/srso: Correct the mitigation status when SMT is disabled objtool/x86: Fixup frame-pointer vs rethunk x86/retpoline,kprobes: Fix position of thunk sections with CONFIG_LTO_CLANG x86/srso: Disable the mitigation on unaffected configurations x86/CPU/AMD: Fix the DIV(0) initial fix attempt x86/retpoline: Don't clobber RFLAGS during srso_safe_ret() x86/static_call: Fix __static_call_fixup() x86/srso: Explain the untraining sequences a bit more x86/cpu: Cleanup the untrain mess x86/cpu: Rename srso_(.*)_alias to srso_alias_\1 x86/cpu: Rename original retbleed methods x86/cpu: Clean up SRSO return thunk mess x86/alternative: Make custom return thunk unconditional x86/cpu: Fix up srso_safe_ret() and __x86_return_thunk() x86/cpu: Fix __x86_return_thunk symbol type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2035354/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035229] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700607/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev: 2.0
[Kernel-packages] [Bug 2035229] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700609/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev: 2.0
[Kernel-packages] [Bug 2035229] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700608/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev: 2.0
[Kernel-packages] [Bug 2035229] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700602/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver:
[Kernel-packages] [Bug 2035229] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700606/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev: 2.0
[Kernel-packages] [Bug 2035229] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700601/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev:
[Kernel-packages] [Bug 2035229] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700605/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev:
[Kernel-packages] [Bug 2035229] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700600/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev: 2.0
[Kernel-packages] [Bug 2035229] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700604/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs
[Kernel-packages] [Bug 2035229] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700603/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev:
[Kernel-packages] [Bug 2035229] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700599/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev: 2.0
[Kernel-packages] [Bug 2035229] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700598/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev: 2.0
[Kernel-packages] [Bug 2035229] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700597/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev: 2.0
[Kernel-packages] [Bug 2035229] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700596/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev: 2.0
[Kernel-packages] [Bug 2035229] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700595/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev: 2.0
[Kernel-packages] [Bug 2035229] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2035229/+attachment/5700594/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev: 2.0
