[Kernel-packages] [Bug 2006942] Re: With linux kernel 5.19.0-31 amd_pstate is not used, while with 5.19.0-29 and lower does
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2006942 Title: With linux kernel 5.19.0-31 amd_pstate is not used, while with 5.19.0-29 and lower does Status in linux package in Ubuntu: Confirmed Status in linux-signed package in Ubuntu: Confirmed Bug description: After upgrading to 5.19.0-31 (two of my systems) CPU driver changes to acpi-cpufreq. instead of amd_pstate. This causes cpu to keep higher frequency and increased consumption. ``` root@zeus:/sys/devices/system/cpu/cpufreq/policy0# ls -l total 0 -r--r--r-- 1 root root 4096 Feb 10 13:27 affected_cpus -r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_highest_perf -r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_lowest_nonlinear_freq -r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_max_freq -r--r--r-- 1 root root 4096 Feb 10 12:54 cpuinfo_max_freq -r--r--r-- 1 root root 4096 Feb 10 13:27 cpuinfo_min_freq -r--r--r-- 1 root root 4096 Feb 10 13:27 cpuinfo_transition_latency -r--r--r-- 1 root root 4096 Feb 10 13:27 related_cpus -r--r--r-- 1 root root 4096 Feb 10 12:54 scaling_available_governors -r--r--r-- 1 root root 4096 Feb 10 13:27 scaling_cur_freq -r--r--r-- 1 root root 4096 Feb 10 13:27 scaling_driver -rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_governor -rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_max_freq -rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_min_freq -rw-r--r-- 1 root root 4096 Feb 10 13:28 scaling_setspeed root@zeus:/sys/devices/system/cpu/cpufreq/policy0# ``` with newer kernel also policy files for amd_pstate Tried it on 2 Asus PN51-S1 systems with AMD Ryzen 7 5700U I am currently staying at 5.19.0-29 as it is working better. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-31-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-11-18 (85 days ago) InstallationMedia: Ubuntu-Server 22.10 "Kinetic Kudu" - Release amd64 (20221019) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-S1 Package: linux-signed (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic root=/dev/mapper/system-root ro ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.19.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/10/2022 dmi.bios.release: 1.12 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0112 dmi.board.asset.tag: Default string dmi.board.name: PN51-S1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0112:bd08/10/2022:br1.12:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-S1:pvr0112:rvnASUSTeKCOMPUTERINC.:rnPN51-S1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-S1 dmi.product.version: 0112 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpa
[Kernel-packages] [Bug 2006453] Re: Fix selftests/ftracetests/Meta-selftests in Focal
** Tags added: 5.4 bionic focal ubuntu-kernel-selftests -- 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/2006453 Title: Fix selftests/ftracetests/Meta-selftests in Focal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [SRU Justification] == Impact == This subtest checks for bashisms in the test scripts of ftracetests. A recent stable change added such a case. This is harmless but causes the Meta-selftests to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer for test_event_enable" which adds: + if [ "$e" == $val ]; then == Fix == Replace the test with + if [ "$e" = $val ]; then == Testcase == Running the kernel selftests/ftracetest (done in ADT and RT) should no longer show "Meta-selftests" as FAILed. == Regression Potential == This affects only the selftest suite and only ftrace subtests. Any change would only be observable there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003995] Re: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic
No regression found. Test result is available at https://docs.google.com/spreadsheets/d/15x8EIBt60Wd2YemL0XrjQnw2VheC0FCbwDGZ37-IpVo/edit?usp=share_link -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2003995 Title: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic Status in fabric-manager-515 package in Ubuntu: Fix Released Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-515 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: New Status in linux-restricted-modules-hwe package in Ubuntu: New Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-525 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-515 source package in Bionic: Triaged Status in fabric-manager-525 source package in Bionic: Triaged Status in libnvidia-nscq-515 source package in Bionic: Triaged Status in libnvidia-nscq-525 source package in Bionic: Triaged Status in linux-restricted-modules source package in Bionic: New Status in linux-restricted-modules-hwe source package in Bionic: New Status in nvidia-graphics-drivers-515-server source package in Bionic: Triaged Status in nvidia-graphics-drivers-525 source package in Bionic: Triaged Status in nvidia-graphics-drivers-525-server source package in Bionic: Triaged Status in fabric-manager-515 source package in Focal: Triaged Status in fabric-manager-525 source package in Focal: Triaged Status in libnvidia-nscq-515 source package in Focal: Triaged Status in libnvidia-nscq-525 source package in Focal: Triaged Status in linux-restricted-modules source package in Focal: New Status in linux-restricted-modules-hwe source package in Focal: New Status in nvidia-graphics-drivers-515-server source package in Focal: Triaged Status in nvidia-graphics-drivers-525 source package in Focal: Triaged Status in nvidia-graphics-drivers-525-server source package in Focal: Triaged Status in fabric-manager-515 source package in Jammy: Triaged Status in fabric-manager-525 source package in Jammy: Triaged Status in libnvidia-nscq-515 source package in Jammy: Triaged Status in libnvidia-nscq-525 source package in Jammy: Triaged Status in linux-restricted-modules source package in Jammy: New Status in linux-restricted-modules-hwe source package in Jammy: New Status in nvidia-graphics-drivers-515-server source package in Jammy: Triaged Status in nvidia-graphics-drivers-525 source package in Jammy: Triaged Status in nvidia-graphics-drivers-525-server source package in Jammy: Triaged Status in fabric-manager-515 source package in Kinetic: Triaged Status in fabric-manager-525 source package in Kinetic: Triaged Status in libnvidia-nscq-515 source package in Kinetic: Triaged Status in libnvidia-nscq-525 source package in Kinetic: Triaged Status in linux-restricted-modules source package in Kinetic: New Status in linux-restricted-modules-hwe source package in Kinetic: New Status in nvidia-graphics-drivers-515-server source package in Kinetic: Triaged Status in nvidia-graphics-drivers-525 source package in Kinetic: Triaged Status in nvidia-graphics-drivers-525-server source package in Kinetic: Triaged 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] 525 * New upstream release (LP: #2003995): - Improved the reliability of suspend and resume on UEFI systems when using certain display panels. - Fixed a bug that could cause VK_ERROR_DEVICE_LOST when using VK_MEMORY_ALLOCATE_DEVICE_ADDRESS_CAPTURE_REPLAY_BIT to allocate memory. - Disabled Fixed Rate Link (FRL) when using passive DisplayPort to HDMI dongles, which are incompatible with FRL. * debian/templates/control.in: - Add Conflicts, Replaces, Provides
[Kernel-packages] [Bug 2006453] Re: Fix selftests/ftracetests/Meta-selftests in Focal
** Also affects: ubuntu-kernel-tests 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/2006453 Title: Fix selftests/ftracetests/Meta-selftests in Focal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [SRU Justification] == Impact == This subtest checks for bashisms in the test scripts of ftracetests. A recent stable change added such a case. This is harmless but causes the Meta-selftests to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer for test_event_enable" which adds: + if [ "$e" == $val ]; then == Fix == Replace the test with + if [ "$e" = $val ]; then == Testcase == Running the kernel selftests/ftracetest (done in ADT and RT) should no longer show "Meta-selftests" as FAILed. == Regression Potential == This affects only the selftest suite and only ftrace subtests. Any change would only be observable there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007668] Re: glitch on screen
I experience the same bug on Intel 12th gen. Please try adding kernel parameter: i915.enable_psr=0 which has fixed it for me on a different laptop. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - glitch on screen + Noisy screen corruption during some cursor movement -- 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/2007668 Title: Noisy screen corruption during some cursor movement Status in linux package in Ubuntu: Incomplete Bug description: This always happens when the cursor sweeps over a height range (approximately 960px ~ 990px from the top). Even when watching a video, the top of the screen sometimes glitches. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 16:24:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:46aa] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b14] InstallationDate: Installed on 2022-08-13 (187 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=3ba28059-7aea-46a5-bf4e-44dd0203b83d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 02GGG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn02GGG1:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007668] [NEW] glitch on screen
You have been subscribed to a public bug: This always happens when the cursor sweeps over a height range (approximately 960px ~ 990px from the top). Even when watching a video, the top of the screen sometimes glitches. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 16:24:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:46aa] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b14] InstallationDate: Installed on 2022-08-13 (187 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=3ba28059-7aea-46a5-bf4e-44dd0203b83d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 02GGG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn02GGG1:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug corruption jammy ubuntu wayland-session -- glitch on screen https://bugs.launchpad.net/bugs/2007668 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 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs
Hi JianlinLV, I tried the latest 5.15.0-60-generic kernel from -updates, and I couldn't reproduce the issue anymore. Can you try 5.15.0-60-generic and let me know? I bisected it down to 5.15.0-52-generic being broken, and it being fixed in 5.15.0-53-generic. Still trying to find the commit which fixed the issue. I had a read of your patch, and it fixes a part of the Apparmor LSM Stacking patchset that Ubuntu carries out of tree. The upstream code has changed a bit from what is found in the 5.15.0-x-generic kernel in Jammy. https://patchew.org/linux/20220927195421.14713-1-casey@schaufler- ca.com/ Let me know how 5.15.0-60-generic goes. Thanks, Matthew -- 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/1987430 Title: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: Since updating to kernel 5.15.0-46-generic (package version 5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel memory; our first server with 8 GB of RAM just fatally OOMed, causing us to detect this. Inspection of OOM reports, /proc/meminfo, and /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k slabs: Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab info: Aug 23 12:51:11 cluster kernel: [361299.864757] Name Used Total [...] Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k 6676584KB6676596KB Most of our machines appear to be leaking slab memory at a rate of around 20 to 40 Mbytes/hour, with some machines leaking much faster; the champions are leaking kernel memory at 145 Mbytes/hour and 237 Mbytes/hour. We aren't running any proprietary kernel modules and our only unusual kernel configuration is that we've disabled AppArmor with 'apparmor=0' on the kernel command line. /proc/version_signature: Ubuntu 5.15.0-46.49-generic 5.15.39 Full kernel command line from the Dell R240 system that fatally OOMd: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 console=tty0 apparmor=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006042] 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/2006042 Title: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram Status in linux package in Ubuntu: Confirmed Bug description: Hi, After waking up from suspend to RAM, my computer actually wakes up but can sometimes then hang on a black screen (no prompt, nothing displayed, screen is active). This issue happens quite frequently but seems rather random. I think certain circumstances lower the frequency (I'll elaborate in the report). First of all, I'm not exactly sure when it started but I would say first notable frequent occurrences were around summer 2021 (yes, I'm late, sorry for that). When this happens, Algr+SysRQ+[usb] is unresponsive. Or at least that's what I used to believe as it used to be true as I always tried from the laptop integrated keyboard. Until I connected an USB-C mechanical keyboard, from which I'm *sometimes* able to use the magic keys (not always, and with a lot of lag, but still). If magic keys are unresponsive, I need to hard reset/long press power. There is nothing unusual before that in syslog nor kern.log, at least not that I know of. Except the ^@^@^@ characters when I had to hard reset the computer. If I leave the laptop like that for a while, it eventually reboots by itself and stays on the FDE passphrase prompt (which is not nice as the screen can then stay on for a very long like that if I did not notice). I'm running KDE/Plasma desktop, and this issue has happened regardless of the display manager. I used to run Xorg but now I'm on wayland flavor (mostly to alleviate firefox rendering/compositing issues). This also seems unrelated to external screen being connected or not, as it happened in the past regardless of that parameter. Although, it *seems* frequency has lowered a bit since I changed the way I wake up my laptop. Higher frequency (almost every day): - no external screen or external screen connected to HDMI port - waking up from integrated keyboard power button short press Lower frequency (one to multiple times a week, but somewhat irregular, since ~ 2 months ago): - external screen connected to USB-C port - mechanical keyboard connected to USB-C port of screen - waking up from the mechanical keyboard It also seems to happen more frequently if I wake up the computer, do some very fast task and send it to sleep in under a few minutes. It's not guaranteed to happen, but seems to highly increase the probability. Also, this might be related so I'm adding that bit: I had to disable shutting the screen Off in energy saving settings, as enabling that option would trigger a similar behavior after a break long enough for that setting to trigger. I would come back on a laptop having self-rebooted and waiting for my input on the FDE passphrase prompt. During ACPI options testing, I noticed that setting might cause the sleep order to get cancelled. From that, I suspect in that case the laptop would go to sleep, then wake up immediately, which could have been triggering the bug as I described previously that rapid state changes would increase probability. Then as I described earlier, if I do nothing when this happens, the computer eventually reboots. This is only speculation as I'm usually not here to observe the behavior (this mostly happened during lunch breaks, which are long enough for all of these steps to happen). I disabled screen turn-off energy saving option a long while ago and have taken the habit of manually suspending to RAM when I intend on going away from the computer for more than a few minutes. As I described above, I've tried a few changes to check for behavior but that was a few months ago and I don't clearly remember all scenario. What I remember is that changing any of these did not resolve my issue and some even prevented my computer to even suspend to RAM properly (waking up immediately after). Among the options I tried is: - booting with a previous kernel, but then it's been happening for so long this would obviously not work (just for the sake of completion) - booting on latest mainstream kernel (tested linux-image-unsigned-6.0.9-060009-generic, this was the latest version when I tried a while ago) - booting with i915.enable_dpcd_backlight=3 (I think this one triggered the immediate wake up) - booting with nolapic, noapic (didn't try acpi=off nor acpi=ht as it seems to me it would disable suspend to RAM feature, right?) I think that's about it, and I'd be happy to try any suggestion. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generi
[Kernel-packages] [Bug 2000265] Re: Keyboard and mouse not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/2000265 Title: Keyboard and mouse not working Status in linux package in Ubuntu: Expired Bug description: I have installed ubuntu on my laptop, Ubuntu version is 18.04, after installing that my keyboard and mouse have stopped working, but they are working in windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000265/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006042] Re: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram
** Changed in: linux (Ubuntu) Status: Incomplete => 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/2006042 Title: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram Status in linux package in Ubuntu: New Bug description: Hi, After waking up from suspend to RAM, my computer actually wakes up but can sometimes then hang on a black screen (no prompt, nothing displayed, screen is active). This issue happens quite frequently but seems rather random. I think certain circumstances lower the frequency (I'll elaborate in the report). First of all, I'm not exactly sure when it started but I would say first notable frequent occurrences were around summer 2021 (yes, I'm late, sorry for that). When this happens, Algr+SysRQ+[usb] is unresponsive. Or at least that's what I used to believe as it used to be true as I always tried from the laptop integrated keyboard. Until I connected an USB-C mechanical keyboard, from which I'm *sometimes* able to use the magic keys (not always, and with a lot of lag, but still). If magic keys are unresponsive, I need to hard reset/long press power. There is nothing unusual before that in syslog nor kern.log, at least not that I know of. Except the ^@^@^@ characters when I had to hard reset the computer. If I leave the laptop like that for a while, it eventually reboots by itself and stays on the FDE passphrase prompt (which is not nice as the screen can then stay on for a very long like that if I did not notice). I'm running KDE/Plasma desktop, and this issue has happened regardless of the display manager. I used to run Xorg but now I'm on wayland flavor (mostly to alleviate firefox rendering/compositing issues). This also seems unrelated to external screen being connected or not, as it happened in the past regardless of that parameter. Although, it *seems* frequency has lowered a bit since I changed the way I wake up my laptop. Higher frequency (almost every day): - no external screen or external screen connected to HDMI port - waking up from integrated keyboard power button short press Lower frequency (one to multiple times a week, but somewhat irregular, since ~ 2 months ago): - external screen connected to USB-C port - mechanical keyboard connected to USB-C port of screen - waking up from the mechanical keyboard It also seems to happen more frequently if I wake up the computer, do some very fast task and send it to sleep in under a few minutes. It's not guaranteed to happen, but seems to highly increase the probability. Also, this might be related so I'm adding that bit: I had to disable shutting the screen Off in energy saving settings, as enabling that option would trigger a similar behavior after a break long enough for that setting to trigger. I would come back on a laptop having self-rebooted and waiting for my input on the FDE passphrase prompt. During ACPI options testing, I noticed that setting might cause the sleep order to get cancelled. From that, I suspect in that case the laptop would go to sleep, then wake up immediately, which could have been triggering the bug as I described previously that rapid state changes would increase probability. Then as I described earlier, if I do nothing when this happens, the computer eventually reboots. This is only speculation as I'm usually not here to observe the behavior (this mostly happened during lunch breaks, which are long enough for all of these steps to happen). I disabled screen turn-off energy saving option a long while ago and have taken the habit of manually suspending to RAM when I intend on going away from the computer for more than a few minutes. As I described above, I've tried a few changes to check for behavior but that was a few months ago and I don't clearly remember all scenario. What I remember is that changing any of these did not resolve my issue and some even prevented my computer to even suspend to RAM properly (waking up immediately after). Among the options I tried is: - booting with a previous kernel, but then it's been happening for so long this would obviously not work (just for the sake of completion) - booting on latest mainstream kernel (tested linux-image-unsigned-6.0.9-060009-generic, this was the latest version when I tried a while ago) - booting with i915.enable_dpcd_backlight=3 (I think this one triggered the immediate wake up) - booting with nolapic, noapic (didn't try acpi=off nor acpi=ht as it seems to me it would disable suspend to RAM feature, right?) I think that's about it, and I'd be happy to try any suggestion. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-ge
[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault in Kinetic Kudu
** Changed in: linux (Ubuntu) Status: Triaged => Fix Committed ** Tags added: jammy ** Tags added: regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995956 Title: amdgpu no-retry page fault in Kinetic Kudu Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Triaged Bug description: When using Skype in snap, amdgpu crashed, resulting in black screen and unresponsive system. Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu firmware. Affected laptop is T14 with Ryzen 5850U. Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 This happens in a loop and eventually leads to GPU reset, which fails. Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=211509, emitted seq=211512 Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process skypeforlinux pid 154554 thread skypeforli:cs0 pid 154558 Nov 03 16:35:55 laptop kernel: amdgpu :07:00.0: amdgpu: GPU reset begin! Nov 03 16:35:55 laptop kernel: [drm] free PSP TMR buffer Nov 03 16:35:55 laptop kernel: CPU: 15
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
version 2.13.8-1~ubuntu22.10.0 tested on Kinetic 5.19.0-31, test passed without any issue. version 2.13.8-1~ubuntu22.04.0 tested on Jammy 5.15.0-60, test passed without any issue ** Tags removed: verification-needed verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-jammy verification-done-kinetic -- 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/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in lttng-modules source package in Bionic: In Progress Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: Fix Committed Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: Fix Committed Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: previous definition of ‘trace_jbd2_run_stats’ was here 778 21:14:39 DEBUG| [stdout] 243 | static inline void trace_##name(proto) \ 779 21:14:39 DEBUG| [stdout] | ^~ 780 21:14:39 DEBUG| [stdout] ./include/linux/t
[Kernel-packages] [Bug 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%
bonnie++ runs apparently proportional with installed RAM size, which means on my machine it takes forever and does considerable SSD wear (I cancelled it after a few minutes). I could run something less punishing like maybe fio, with some parameters of your choosing. -- 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/2007717 Title: Kernel linux-image-5.19.0-32 regression, compile speed down by 33% Status in linux package in Ubuntu: Incomplete Bug description: I just yesterday and the day before made some benchmark tests for a comparison between ext4 and zfs. I ran repeated builds of a large software package and it always came out to 45s. Now today I ran the same test a few times and it was always 60s. I noticed that today an update ran and that kernel 5.19.0-32 was installed. So just now I booted back to 5.15.0-60-generic:amd64 and ran the test again: back to 45s. I am running Ubuntu 22.04.1 LTS on a AMD Ryzen 3970X with 128GB RAM otherwise there is nothing very special going on. I ran the tests on ZFS and ext4, it makes no difference. To reproduce, I would think that compiling any decent sized software package one on 5.15 and then on 5.19 whould yield the same results. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-15 (217 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=c1b17af6-e10d-4836-a5d0-aa0c25802bca ro mitigations=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: wayland-session jammy Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom davfs2 dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/01/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: TRX40 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd06/01/2020:br5.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006042] Re: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram
Sorry for the delay, was off computers for a few days. Here it is! ** Attachment added: "/proc/acpi/wakeup" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006042/+attachment/5648518/+files/proc-acpi-wakeup.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/2006042 Title: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram Status in linux package in Ubuntu: Incomplete Bug description: Hi, After waking up from suspend to RAM, my computer actually wakes up but can sometimes then hang on a black screen (no prompt, nothing displayed, screen is active). This issue happens quite frequently but seems rather random. I think certain circumstances lower the frequency (I'll elaborate in the report). First of all, I'm not exactly sure when it started but I would say first notable frequent occurrences were around summer 2021 (yes, I'm late, sorry for that). When this happens, Algr+SysRQ+[usb] is unresponsive. Or at least that's what I used to believe as it used to be true as I always tried from the laptop integrated keyboard. Until I connected an USB-C mechanical keyboard, from which I'm *sometimes* able to use the magic keys (not always, and with a lot of lag, but still). If magic keys are unresponsive, I need to hard reset/long press power. There is nothing unusual before that in syslog nor kern.log, at least not that I know of. Except the ^@^@^@ characters when I had to hard reset the computer. If I leave the laptop like that for a while, it eventually reboots by itself and stays on the FDE passphrase prompt (which is not nice as the screen can then stay on for a very long like that if I did not notice). I'm running KDE/Plasma desktop, and this issue has happened regardless of the display manager. I used to run Xorg but now I'm on wayland flavor (mostly to alleviate firefox rendering/compositing issues). This also seems unrelated to external screen being connected or not, as it happened in the past regardless of that parameter. Although, it *seems* frequency has lowered a bit since I changed the way I wake up my laptop. Higher frequency (almost every day): - no external screen or external screen connected to HDMI port - waking up from integrated keyboard power button short press Lower frequency (one to multiple times a week, but somewhat irregular, since ~ 2 months ago): - external screen connected to USB-C port - mechanical keyboard connected to USB-C port of screen - waking up from the mechanical keyboard It also seems to happen more frequently if I wake up the computer, do some very fast task and send it to sleep in under a few minutes. It's not guaranteed to happen, but seems to highly increase the probability. Also, this might be related so I'm adding that bit: I had to disable shutting the screen Off in energy saving settings, as enabling that option would trigger a similar behavior after a break long enough for that setting to trigger. I would come back on a laptop having self-rebooted and waiting for my input on the FDE passphrase prompt. During ACPI options testing, I noticed that setting might cause the sleep order to get cancelled. From that, I suspect in that case the laptop would go to sleep, then wake up immediately, which could have been triggering the bug as I described previously that rapid state changes would increase probability. Then as I described earlier, if I do nothing when this happens, the computer eventually reboots. This is only speculation as I'm usually not here to observe the behavior (this mostly happened during lunch breaks, which are long enough for all of these steps to happen). I disabled screen turn-off energy saving option a long while ago and have taken the habit of manually suspending to RAM when I intend on going away from the computer for more than a few minutes. As I described above, I've tried a few changes to check for behavior but that was a few months ago and I don't clearly remember all scenario. What I remember is that changing any of these did not resolve my issue and some even prevented my computer to even suspend to RAM properly (waking up immediately after). Among the options I tried is: - booting with a previous kernel, but then it's been happening for so long this would obviously not work (just for the sake of completion) - booting on latest mainstream kernel (tested linux-image-unsigned-6.0.9-060009-generic, this was the latest version when I tried a while ago) - booting with i915.enable_dpcd_backlight=3 (I think this one triggered the immediate wake up) - booting with nolapic, noapic (didn't try acpi=off nor acpi=ht as it seems to me it would disable suspend to RAM feature, right?) I think that's about it, and I'd be happy to try any suggestion.
[Kernel-packages] [Bug 2006042] Re: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram
** Attachment added: "proc-acpi-wakeup.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006042/+attachment/5648517/+files/proc-acpi-wakeup.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/2006042 Title: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram Status in linux package in Ubuntu: Incomplete Bug description: Hi, After waking up from suspend to RAM, my computer actually wakes up but can sometimes then hang on a black screen (no prompt, nothing displayed, screen is active). This issue happens quite frequently but seems rather random. I think certain circumstances lower the frequency (I'll elaborate in the report). First of all, I'm not exactly sure when it started but I would say first notable frequent occurrences were around summer 2021 (yes, I'm late, sorry for that). When this happens, Algr+SysRQ+[usb] is unresponsive. Or at least that's what I used to believe as it used to be true as I always tried from the laptop integrated keyboard. Until I connected an USB-C mechanical keyboard, from which I'm *sometimes* able to use the magic keys (not always, and with a lot of lag, but still). If magic keys are unresponsive, I need to hard reset/long press power. There is nothing unusual before that in syslog nor kern.log, at least not that I know of. Except the ^@^@^@ characters when I had to hard reset the computer. If I leave the laptop like that for a while, it eventually reboots by itself and stays on the FDE passphrase prompt (which is not nice as the screen can then stay on for a very long like that if I did not notice). I'm running KDE/Plasma desktop, and this issue has happened regardless of the display manager. I used to run Xorg but now I'm on wayland flavor (mostly to alleviate firefox rendering/compositing issues). This also seems unrelated to external screen being connected or not, as it happened in the past regardless of that parameter. Although, it *seems* frequency has lowered a bit since I changed the way I wake up my laptop. Higher frequency (almost every day): - no external screen or external screen connected to HDMI port - waking up from integrated keyboard power button short press Lower frequency (one to multiple times a week, but somewhat irregular, since ~ 2 months ago): - external screen connected to USB-C port - mechanical keyboard connected to USB-C port of screen - waking up from the mechanical keyboard It also seems to happen more frequently if I wake up the computer, do some very fast task and send it to sleep in under a few minutes. It's not guaranteed to happen, but seems to highly increase the probability. Also, this might be related so I'm adding that bit: I had to disable shutting the screen Off in energy saving settings, as enabling that option would trigger a similar behavior after a break long enough for that setting to trigger. I would come back on a laptop having self-rebooted and waiting for my input on the FDE passphrase prompt. During ACPI options testing, I noticed that setting might cause the sleep order to get cancelled. From that, I suspect in that case the laptop would go to sleep, then wake up immediately, which could have been triggering the bug as I described previously that rapid state changes would increase probability. Then as I described earlier, if I do nothing when this happens, the computer eventually reboots. This is only speculation as I'm usually not here to observe the behavior (this mostly happened during lunch breaks, which are long enough for all of these steps to happen). I disabled screen turn-off energy saving option a long while ago and have taken the habit of manually suspending to RAM when I intend on going away from the computer for more than a few minutes. As I described above, I've tried a few changes to check for behavior but that was a few months ago and I don't clearly remember all scenario. What I remember is that changing any of these did not resolve my issue and some even prevented my computer to even suspend to RAM properly (waking up immediately after). Among the options I tried is: - booting with a previous kernel, but then it's been happening for so long this would obviously not work (just for the sake of completion) - booting on latest mainstream kernel (tested linux-image-unsigned-6.0.9-060009-generic, this was the latest version when I tried a while ago) - booting with i915.enable_dpcd_backlight=3 (I think this one triggered the immediate wake up) - booting with nolapic, noapic (didn't try acpi=off nor acpi=ht as it seems to me it would disable suspend to RAM feature, right?) I think that's about it, and I'd be happy to try any suggestion. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:
[Kernel-packages] [Bug 2007783] Re: MIPI kernel drivers fail to work due to I2C conflict
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007783 Title: MIPI kernel drivers fail to work due to I2C conflict Status in linux-meta-hwe-5.19 package in Ubuntu: New Bug description: On my Lenovo ThinkPad X1 Nano Gen2 (and apparently some other laptops?), there is a Lattice Semiconductor I2C firmware update endpoint that prevents the MIPI camera drivers from communicating and working. After applying a small patch and building the kernel locally (which blacklists the Lattice device, which is apparently not actually supported anyway), I'm able to get the MIPI camera functioning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2007783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007783] Re: MIPI kernel drivers fail to work due to I2C conflict
** Package changed: initramfs-tools (Ubuntu) => linux-meta-hwe-5.19 (Ubuntu) ** Patch added: "latt2021.diff" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2007783/+attachment/5648511/+files/latt2021.diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007783 Title: MIPI kernel drivers fail to work due to I2C conflict Status in linux-meta-hwe-5.19 package in Ubuntu: New Bug description: On my Lenovo ThinkPad X1 Nano Gen2 (and apparently some other laptops?), there is a Lattice Semiconductor I2C firmware update endpoint that prevents the MIPI camera drivers from communicating and working. After applying a small patch and building the kernel locally (which blacklists the Lattice device, which is apparently not actually supported anyway), I'm able to get the MIPI camera functioning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2007783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007783] [NEW] MIPI kernel drivers fail to work due to I2C conflict
You have been subscribed to a public bug: On my Lenovo ThinkPad X1 Nano Gen2 (and apparently some other laptops?), there is a Lattice Semiconductor I2C firmware update endpoint that prevents the MIPI camera drivers from communicating and working. After applying a small patch and building the kernel locally (which blacklists the Lattice device, which is apparently not actually supported anyway), I'm able to get the MIPI camera functioning. ** Affects: linux-meta-hwe-5.19 (Ubuntu) Importance: Undecided Status: New -- MIPI kernel drivers fail to work due to I2C conflict https://bugs.launchpad.net/bugs/2007783 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.19 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 1995956] Re: amdgpu no-retry page fault in Kinetic Kudu
This is also affecting Ubuntu 22.04 now that the 5.19 kernel is rolling out as the HWE kernel. It's quite a severe bug, and I ended up switching to the linux-oem-22.04c kernel instead to get around it. -- 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/1995956 Title: amdgpu no-retry page fault in Kinetic Kudu Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Status in linux source package in Kinetic: Triaged Bug description: When using Skype in snap, amdgpu crashed, resulting in black screen and unresponsive system. Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu firmware. Affected laptop is T14 with Ryzen 5850U. Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 This happens in a loop and eventually leads to GPU reset, which fails. Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=211509, emitted seq=211512 Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process skypeforlinux pid 154554 thread skypeforli:cs0 pid 154558 Nov 03 16:35:55 laptop kernel: amdgpu :07:00.0: amdgpu: GPU reset begin! Nov 03 16:35:55 laptop kernel
[Kernel-packages] [Bug 2007788] [NEW] Exporting a logical volume via NBD leads to kernel crashes
Public bug reported: I'm exporting a logical volume via nbd-server to a raspberry pi which uses the nbd device as a physical volume for its own LVM stack. Some operations such as running mkfs.ext2 on a logical volume inside the raspberry pi crash the exporting server. I have seen various messages from the kernel in the syslog & dmesg and experienced lock-ups etc. The operations that cause this cause the issues consistently. For instance the mkfs.ext2 on the RPI cause this to appear in dmesg on the server exporting the NBD: [ 1188.468279] [ cut here ] [ 1188.468282] kernel BUG at include/linux/highmem.h:279! [ 1188.468289] invalid opcode: [#1] PREEMPT SMP NOPTI [ 1188.468292] CPU: 2 PID: 4944 Comm: pool Not tainted 5.19.0-32-generic #33~22.04.1-Ubuntu [ 1188.468295] Hardware name: Gigabyte Technology Co., Ltd. X570 GAMING X/X570 GAMING X, BIOS F37 12/26/2022 [ 1188.468296] RIP: 0010:zero_user_segments.constprop.0+0x15c/0x1a0 [ 1188.468303] Code: ff 48 8b 57 48 f6 c2 01 0f 84 00 ff ff ff 48 83 ea 01 48 39 d7 0f 84 f3 fe ff ff 41 be 00 10 00 00 4c 39 f0 0f 86 03 ff ff ff <0f> 0b f7 c3 ff 0f 00 00 0f 85 04 ff ff ff 48 8b 03 a9 00 00 01 00 [ 1188.468305] RSP: 0018:be5984817be8 EFLAGS: 00010206 [ 1188.468308] RAX: fae0 RBX: f46887f2f800 RCX: [ 1188.468309] RDX: 0017c0020037 RSI: RDI: f46887f2f800 [ 1188.468311] RBP: be5984817c20 R08: f4688000 R09: [ 1188.468312] R10: R11: R12: fae0 [ 1188.468314] R13: R14: 1000 R15: 977ac000 [ 1188.468315] FS: 7fd36bfff640() GS:9782dea8() knlGS: [ 1188.468317] CS: 0010 DS: ES: CR0: 80050033 [ 1188.468319] CR2: 04c500e89000 CR3: 000114472000 CR4: 00350ee0 [ 1188.468321] Call Trace: [ 1188.468323] [ 1188.468325] truncate_inode_partial_folio+0xce/0x240 [ 1188.468329] truncate_inode_pages_range+0x237/0x650 [ 1188.468332] ? hrtimer_cancel+0x21/0x50 [ 1188.468335] ? futex_wait+0x238/0x260 [ 1188.468339] ? __hrtimer_init+0x120/0x120 [ 1188.468342] ? rseq_get_rseq_cs.isra.0+0x1b/0x270 [ 1188.468345] ? bd_prepare_to_claim+0x131/0x150 [ 1188.468349] ? rseq_ip_fixup+0x72/0x1b0 [ 1188.468351] truncate_bdev_range+0x4f/0x120 [ 1188.468354] blkdev_common_ioctl+0x479/0x980 [ 1188.468358] blkdev_ioctl+0x133/0x2a0 [ 1188.468360] __x64_sys_ioctl+0x9a/0xe0 [ 1188.468363] do_syscall_64+0x59/0x90 [ 1188.468367] ? syscall_exit_to_user_mode+0x2a/0x50 [ 1188.468370] ? do_syscall_64+0x69/0x90 [ 1188.468372] ? do_syscall_64+0x69/0x90 [ 1188.468375] ? syscall_exit_to_user_mode+0x2a/0x50 [ 1188.468377] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 1188.468380] RIP: 0033:0x7fd371d1aaff [ 1188.468383] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00 [ 1188.468385] RSP: 002b:7fd36bffeb00 EFLAGS: 0246 ORIG_RAX: 0010 [ 1188.468387] RAX: ffda RBX: 7fd36bffebb0 RCX: 7fd371d1aaff [ 1188.468389] RDX: 7fd36bffebb0 RSI: 1277 RDI: 0007 [ 1188.468390] RBP: 7fd36bffec00 R08: R09: 0001 [ 1188.468391] R10: fffbfae0 R11: 0246 R12: 557743114ea0 [ 1188.468393] R13: 557743114e40 R14: 5577431117d0 R15: 0007 [ 1188.468395] [ 1188.468396] Modules linked in: rfcomm snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi bridge stp snd_hda_intel llc snd_intel_dspcfg cmac snd_intel_sdw_acpi algif_hash snd_hda_codec algif_skcipher snd_hda_core af_alg snd_hwdep intel_rapl_msr snd_pcm intel_rapl_common bnep snd_seq_midi btusb snd_seq_midi_event btrtl snd_rawmidi edac_mce_amd btbcm sch_fq_codel snd_seq kvm_amd btintel btmtk msr snd_seq_device binfmt_misc kvm bluetooth snd_timer parport_pc ftdi_sio nls_iso8859_1 snd ecdh_generic rapl ppdev serio_raw gigabyte_wmi wmi_bmof usbserial joydev input_leds k10temp ccp ecc soundcore lp ramoops mac_hid pstore_blk parport reed_solomon pstore_zone efi_pstore ip_tables x_tables autofs4 amdgpu iommu_v2 gpu_sched i2c_algo_bit dm_thin_pool drm_ttm_helper hid_generic dm_persistent_data ttm usbhid dm_bio_prison drm_display_helper hid dm_bufio cec libcrc32c rc_core drm_kms_helper syscopyarea sysfillrect crct10dif_pclmul sysimgblt crc32_pclmul ghash_clmulni_in tel [ 1188.468452] aesni_intel crypto_simd fb_sys_fops nvme ahci xhci_pci r8169 cryptd psmouse drm i2c_piix4 nvme_core libahci xhci_pci_renesas realtek wmi [ 1188.468463] ---[ end trace ]--- [ 1188.614812] RIP: 0010:zero_user_segments.constprop.0+0x15c/0x1a0 [ 1188.614818] Code: ff 48 8b 57 48 f6 c2 01 0f 84 00 ff ff ff 48 83 ea 01 48 39 d7 0f 84 f3 fe ff ff 41 be 00 10 00 00 4c 39 f0 0f 86 03 ff ff ff <0f> 0
[Kernel-packages] [Bug 2007633] Re: amdgpu fails to init with kernel 5.19.0
I'm having the same problem with one of my systems. Same family of GPU, Tahiti. This bug https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953249 is very similar to what is happening. However, I'm able to get all the way to an X session, but functionality of the card is affected (can't change display refresh rate). Something must have changed, because the machine has the relevant firmware files in /lib/firmware/amdgpu. -- 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/2007633 Title: amdgpu fails to init with kernel 5.19.0 Status in linux package in Ubuntu: Confirmed Bug description: I recently installed apt upgrades, and among the upgrades, was the 5.19.0-32-generic kernel. I also still have installed the 5.15.0-58-generic kernel. Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280 GPU fails to init. This results in the computer effectively getting 'hung' part way through the kernel boot as X or Wayland, whatever should start up, doesn't. The kernel keeps running (I can see the hard drive light occasionally flash on my case, and the kernel logs continue after the point of the apparent hang - although kernel messages stop getting output to the console - to see the messages, I have to reboot with 5.15 then use journalctl to review the previous boot messages). It inits fine with the older kernel. Not sure what the root cause of the failure is. Found this in kernel boot logs (via "journalctl -b -1" to get the logs for the previous boot, that failed), which I think is indicative of the problem: Feb 16 21:37:17 jeff-linux kernel: status: Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 Family ID: 13 Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy unavailable Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -19 Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init failed Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error during GPU init Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: finishing device. Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, address: 0090 -- version signature info (line 2 from kernel boot log): Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17) - root@jeff-linux:/home/jeff# lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 See attached lspci-vnvn.log --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jeff 1525 F pulseaudio /dev/snd/controlC0: jeff 1525 F pulseaudio /dev/snd/controlC1: jeff 1525 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-27 (355 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Q77-M dmi.board.vendor: ASUSTeK COMPUTER INC.
[Kernel-packages] [Bug 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%
To further isolate the nature of the slowdown, we should figure out if this is caused by disk I/O degradation, CPU frequency scaling, or something else. Can you use the bonnie++ package to check the disk throughput under the old and new kernels? -- 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/2007717 Title: Kernel linux-image-5.19.0-32 regression, compile speed down by 33% Status in linux package in Ubuntu: Incomplete Bug description: I just yesterday and the day before made some benchmark tests for a comparison between ext4 and zfs. I ran repeated builds of a large software package and it always came out to 45s. Now today I ran the same test a few times and it was always 60s. I noticed that today an update ran and that kernel 5.19.0-32 was installed. So just now I booted back to 5.15.0-60-generic:amd64 and ran the test again: back to 45s. I am running Ubuntu 22.04.1 LTS on a AMD Ryzen 3970X with 128GB RAM otherwise there is nothing very special going on. I ran the tests on ZFS and ext4, it makes no difference. To reproduce, I would think that compiling any decent sized software package one on 5.15 and then on 5.19 whould yield the same results. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-15 (217 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=c1b17af6-e10d-4836-a5d0-aa0c25802bca ro mitigations=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: wayland-session jammy Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom davfs2 dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/01/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: TRX40 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd06/01/2020:br5.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007781] 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/2007781 Title: Wifi occasionally doesn't work aynmore before turning it off and on again Status in linux package in Ubuntu: Confirmed Bug description: My wifi randomly gets not recognized anymore, by that I mean there is a question mark appearing on the wifi symbol, whcih means that it doesn't connect me to the internet. Only when I turn it off and on again it works again for a while. I tried to fix the problem by installing dhcpd5 and changing the network.config file, but it didn't work sadly. journalctl gives the following output: Feb 19 15:00:02 adrian-IdeaPad-3-15ADA05 dhcpcd[708]: wlp2s0: part of a Router Advertisement expired Feb 19 15:00:05 adrian-IdeaPad-3-15ADA05 rtkit-daemon[1103]: Supervising 8 threads of 5 processes of 1 users. Feb 19 15:00:05 adrian-IdeaPad-3-15ADA05 rtkit-daemon[1103]: Supervising 8 threads of 5 processes of 1 users. Feb 19 15:00:14 adrian-IdeaPad-3-15ADA05 firefox_firefox.desktop[14211]: [2023-02-19T14:00:14Z ERROR mp4parse] Found 2 nul bytes in "\0\0" Feb 19 15:00:14 adrian-IdeaPad-3-15ADA05 firefox_firefox.desktop[14211]: [2023-02-19T14:00:14Z ERROR mp4parse] Found 2 nul bytes in "\0\0" Feb 19 15:00:14 adrian-IdeaPad-3-15ADA05 firefox_firefox.desktop[14211]: [2023-02-19T14:00:14Z ERROR mp4parse] Found 2 nul bytes in "\0\0" Feb 19 15:00:14 adrian-IdeaPad-3-15ADA05 firefox_firefox.desktop[14211]: [2023-02-19T14:00:14Z ERROR mp4parse] Found 2 nul bytes in "\0\0" Feb 19 15:00:18 adrian-IdeaPad-3-15ADA05 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 19 15:00:18 adrian-IdeaPad-3-15ADA05 systemd-resolved[605]: wlp2s0: Bus client set DNS server list to: fe80::1 Feb 19 15:00:19 adrian-IdeaPad-3-15ADA05 systemd[1]: Starting Load/Save RF Kill Switch Status... Feb 19 15:00:19 adrian-IdeaPad-3-15ADA05 systemd[1]: Started Load/Save RF Kill Switch Status. Feb 19 15:00:19 adrian-IdeaPad-3-15ADA05 kernel: wlp2s0: deauthenticating from 60:8d:26:17:13:f0 by local choice (Reason: 3=DEAUTH_LEAVING) Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 kernel: ath10k_pci :02:00.0: failed to install key for vdev 0 peer 60:8d:26:17:13:f0: -110 Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 kernel: wlp2s0: failed to remove key (0, 60:8d:26:17:13:f0) from hardware (-110) Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 wpa_supplicant[744]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=60:8d:26:17:13:f0 reason=3 locally_generated=1 Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 wpa_supplicant[744]: BSSID 60:8d:26:17:13:f0 ignore list count incremented to 2, ignoring for 10 seconds Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::7c95:24aa:4e04:9716. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3395] manager: rfkill: Wi-Fi hardware radio set disabled Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 dhcpcd[708]: wlp2s0: carrier lost Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3396] device (wlp2s0): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed') Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3400] dhcp4 (wlp2s0): canceled DHCP transaction Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.2.175. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3401] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Withdrawing address record for fe80::9fcf:9cfa:e273:e098 on wlp2s0. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3401] dhcp4 (wlp2s0): state changed no lease Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Withdrawing address record for fe80::7c95:24aa:4e04:9716 on wlp2s0. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Withdrawing address record for 192.168.2.178 on wlp2s0. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Withdrawing address record for 192.168.2.175 on wlp2s0. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 wpa_supplicant[744]: rfkill: WLAN soft blocked Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 wpa_supplicant[744]: rfkill: WLAN soft blocked Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 systemd-resolved[605]: wlp2s0: Bus client set default route setting
[Kernel-packages] [Bug 2007781] [NEW] Wifi occasionally doesn't work aynmore before turning it off and on again
Public bug reported: My wifi randomly gets not recognized anymore, by that I mean there is a question mark appearing on the wifi symbol, whcih means that it doesn't connect me to the internet. Only when I turn it off and on again it works again for a while. I tried to fix the problem by installing dhcpd5 and changing the network.config file, but it didn't work sadly. journalctl gives the following output: Feb 19 15:00:02 adrian-IdeaPad-3-15ADA05 dhcpcd[708]: wlp2s0: part of a Router Advertisement expired Feb 19 15:00:05 adrian-IdeaPad-3-15ADA05 rtkit-daemon[1103]: Supervising 8 threads of 5 processes of 1 users. Feb 19 15:00:05 adrian-IdeaPad-3-15ADA05 rtkit-daemon[1103]: Supervising 8 threads of 5 processes of 1 users. Feb 19 15:00:14 adrian-IdeaPad-3-15ADA05 firefox_firefox.desktop[14211]: [2023-02-19T14:00:14Z ERROR mp4parse] Found 2 nul bytes in "\0\0" Feb 19 15:00:14 adrian-IdeaPad-3-15ADA05 firefox_firefox.desktop[14211]: [2023-02-19T14:00:14Z ERROR mp4parse] Found 2 nul bytes in "\0\0" Feb 19 15:00:14 adrian-IdeaPad-3-15ADA05 firefox_firefox.desktop[14211]: [2023-02-19T14:00:14Z ERROR mp4parse] Found 2 nul bytes in "\0\0" Feb 19 15:00:14 adrian-IdeaPad-3-15ADA05 firefox_firefox.desktop[14211]: [2023-02-19T14:00:14Z ERROR mp4parse] Found 2 nul bytes in "\0\0" Feb 19 15:00:18 adrian-IdeaPad-3-15ADA05 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 19 15:00:18 adrian-IdeaPad-3-15ADA05 systemd-resolved[605]: wlp2s0: Bus client set DNS server list to: fe80::1 Feb 19 15:00:19 adrian-IdeaPad-3-15ADA05 systemd[1]: Starting Load/Save RF Kill Switch Status... Feb 19 15:00:19 adrian-IdeaPad-3-15ADA05 systemd[1]: Started Load/Save RF Kill Switch Status. Feb 19 15:00:19 adrian-IdeaPad-3-15ADA05 kernel: wlp2s0: deauthenticating from 60:8d:26:17:13:f0 by local choice (Reason: 3=DEAUTH_LEAVING) Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 kernel: ath10k_pci :02:00.0: failed to install key for vdev 0 peer 60:8d:26:17:13:f0: -110 Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 kernel: wlp2s0: failed to remove key (0, 60:8d:26:17:13:f0) from hardware (-110) Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 wpa_supplicant[744]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=60:8d:26:17:13:f0 reason=3 locally_generated=1 Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 wpa_supplicant[744]: BSSID 60:8d:26:17:13:f0 ignore list count incremented to 2, ignoring for 10 seconds Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::7c95:24aa:4e04:9716. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3395] manager: rfkill: Wi-Fi hardware radio set disabled Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 dhcpcd[708]: wlp2s0: carrier lost Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3396] device (wlp2s0): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed') Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3400] dhcp4 (wlp2s0): canceled DHCP transaction Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.2.175. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3401] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Withdrawing address record for fe80::9fcf:9cfa:e273:e098 on wlp2s0. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3401] dhcp4 (wlp2s0): state changed no lease Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Withdrawing address record for fe80::7c95:24aa:4e04:9716 on wlp2s0. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Withdrawing address record for 192.168.2.178 on wlp2s0. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Withdrawing address record for 192.168.2.175 on wlp2s0. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 wpa_supplicant[744]: rfkill: WLAN soft blocked Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 wpa_supplicant[744]: rfkill: WLAN soft blocked Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 systemd-resolved[605]: wlp2s0: Bus client set default route setting: no Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 systemd-resolved[605]: wlp2s0: Bus client reset DNS server list. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3735] manager: NetworkManager state is now DISCONNECTED Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3764] audit: op="radio-control" arg="wireless-enabled:off" pid=1804 uid=1000 result="success" Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 wpa_supplic
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
I came across a similar problem in the following situation. Maybe it can help you move forward quickly. Because it is base on docker and cross compile. git clone https://github.com/ros-realtime/linux-real-time-kernel- builder.git $ cd linux-real-time-kernel-builder $ docker build --no-cache --build-arg UBUNTU_VERSION=focal --build-arg KERNEL_VERSION=5.4.0 --build-arg RT_PATCH=5.4.230-rt80 --build-arg LTTNG_VERSION=2.13 -t rtwg-image . After that the Docker image is prepared and ready to run $ docker run -it rtwg-image bash and then inside the docker $ cd $HOME/linux_build/linux-raspi $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- LOCALVERSION=-raspi -j `nproc` bindeb-pkg A error part of screen out; make KERNELRELEASE=5.4.229-rt80-raspi ARCH=arm64KBUILD_BUILD_VERSION=1 -f ./Makefile CALLscripts/atomic/check-atomics.sh CALLscripts/checksyscalls.sh CHK include/generated/compile.h CC lttng/src/lttng-ring-buffer-client-discard.o CC lttng/src/lttng-ring-buffer-client-overwrite.o CC lttng/src/probes/lttng-probe-jbd2.o CC lttng/src/probes/lttng-probe-scsi.o CC lttng/src/probes/lttng-probe-vmscan.o In file included from lttng/src/probes/../../include/lttng/define_trace.h:87, from lttng/src/probes/../../include/instrumentation/events/jbd2.h:293, from lttng/src/probes/lttng-probe-jbd2.c:29: lttng/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6: error: conflicting types for ‘trace_jbd2_run_stats’ 133 | void trace_##_name(_proto); | ^~ lttng/src/probes/../../include/lttng/tracepoint-event-impl.h:45:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 45 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) | ^~~ lttng/src/probes/../../include/lttng/tracepoint-event-impl.h:87:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 87 | LTTNG_TRACEPOINT_EVENT_MAP(name, name,\ | ^~ -- 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/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in lttng-modules source package in Bionic: In Progress Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: Fix Committed Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: Fix Committed Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’
[Kernel-packages] [Bug 1986623] Re: cryptsetup fails to decrypt root partion during boot
It seems like my problem may have been a different underlying cause with
similar symptoms.
In my case, the entry in /etc/crypttab didn't match the location of the
encrypted partition. Partition is on sda3, but /etc/crypttab read:
sda6_crypt UUID={uuid} none luks,discard
It appears that when the initramfs image is generated (as when a new
kernel is installed, but also on other updates), a mismatch between the
naming in /etc/crypttab and the actual partition causes an error (which
of course I didn't see) such that the file in the initramfs (located at
/cryptroot/crypttab) was empty (zero bytes). This lack of a file is
what causes the boot process to hang.
Correcting /etc/crypttab to:
sda3_crypt UUID={uuid} none luks,discard
solves the problem. Of course, if your initramfs is already honked it
needs to be regenerated:
sudo update-initramfs -u
But future updates should proceed normally. Thanks to everyone who
provided pointers/thoughts that helped me track this down.
--
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/1986623
Title:
cryptsetup fails to decrypt root partion during boot
Status in cryptsetup package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Incomplete
Bug description:
During boot, cryptsetup fails to decrypt the root partition in a,
seemingly, non-deterministic fashion. I know that the password is
correct and that the keymap is not a fault either, because I have
specifically chosen the very weak password "123456" for testing
purposes. A hardware defect seems also rather unlikely as this
behavior does not affect other Linux distributions or FreeBSD. Earlier
Ubuntu versions do not seem to be affected either, as this bug appears
to have been introduced during a kernel update in 20.04 and persists
throughout 20.04-22.04. Unfortunately I cannot pinpoint the exact
kernel update that introduced this bug. I have appended the output of
cryptsetup when manually called from the initramfs shell. Here the
second attempt succeeded in decrypting the root partition, however, it
usually takes a lot more attempts to do so.
As for some additional information, I can decrypt the same luks
partition from a live USB without any problems whatsoever.
echo 123456 | cryptsetup open --type luks --debug /dev/nvme0n1p3
nvme0n1p3_crypt
# cryptsetup 2.4.3 processing "cryptsetup open --type luks --debug
/dev/nvme0n1p3 nvme0n1p3_crypt"
# Running command open.
# Locking memory.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
# Allocating context for crypt device /dev/nvme0n1p3.
# Trying to open and read device /dev/nvme0n1p3 with direct-io.
# Initialising device-mapper backend library.
# Trying to load any crypt type from device /dev/nvme0n1p3.
# Crypto backend (OpenSSL 3.0.2 15 Mar 2022 [default]) initialized in
cryptsetup library version 2.4.3.
# Detected kernel Linux 5.15.0-46-generic x86_64.
# Loading LUKS2 header (repair disabled).
# Acquiring read lock for device /dev/nvme0n1p3.
# Opening lock resource file /run/cryptsetup/L_259:3
# Verifying lock handle for /dev/nvme0n1p3.
# Device /dev/nvme0n1p3 READ lock taken.
# Trying to read primary LUKS2 header at offset 0x0.
# Opening locked device /dev/nvme0n1p3
# Verifying locked device handle (bdev)
# LUKS2 header version 2 of size 16384 bytes, checksum sha256.
# Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc
(on-disk)
# Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc
(in-memory)
# Trying to read secondary LUKS2 header at offset 0x4000.
# Reusing open ro fd on device /dev/nvme0n1p3
# LUKS2 header version 2 of size 16384 bytes, checksum sha256.
# Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c
(on-disk)
# Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c
(in-memory)
# Device size 497776852992, offset 16777216.
# Device /dev/nvme0n1p3 READ lock released.
# PBKDF argon2id, time_ms 2000 (iterations 0), max_memory_kb 1048576,
parallel_threads 4.
# Activating volume nvme0n1p3_crypt using token (any type) -1.
# dm version [ opencount flush ] [16384] (*1)
# dm versions [ opencount flush ] [16384] (*1)
# Detected dm-ioctl version 4.45.0.
# Detected dm-crypt version 1.23.0.
# Device-mapper backend running with UDEV support enabled.
# dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1)
No usable token is available.
# STDIN descriptor passphrase entry requested.
# Activating volume nvme0n1p3_crypt [keyslot -1] using passphrase.
# dm versions [ opencount flush ] [16384] (*1)
# dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1)
# Keyslot 0 priority 1 != 2 (required), skipped.
# Keyslot 1 priority 1 != 2 (required), skipped.
# Trying to open LUKS2 keyslot 0.
# Run
[Kernel-packages] [Bug 1998689] Re: Ubuntu 22.04.1 LTS does not boot after update 5.15.0-48 -> 5.15.0-56 - old kernel boots fine
Apparently this has been fixed in `5.19.0-32-generic`. The automatic update to this kernel version did install the proper nvidia drivers without manual interaction. I am not 100% sure, though, if this is possibly an effect of installing the missing modules manually in the previous version. Possibly these then just get updated on their own right rather than as some dependency or so. I don't know much about how this works exactly. -- 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/1998689 Title: Ubuntu 22.04.1 LTS does not boot after update 5.15.0-48 -> 5.15.0-56 - old kernel boots fine Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu 22.04.1 LTS auto updated from kernel 5.15.0-48 to 5.15.0-56. The new kernel does not boot. It stops right after it says the disk is clean. The cursor stops blinking less than 1 second after that and there is no additional message. The old kernel boots fine. The "ubuntu-bug" report was done with the old kernel. I am new to Ubuntu bug reporting and hope the information created by `ubuntu-bug` is added, even though I can't see it here. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2477 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 11:13:53 2022 InstallationDate: Installed on 2022-09-19 (75 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Supermicro M12SWA-TF ProcFB: 0 EFI VGA 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=33a91d45-6bee-4e70-bc21-7956db527e81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2022 dmi.bios.release: 2.10 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: M12SWA-TF dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.0a:bd03/18/2022:br2.10:svnSupermicro:pnM12SWA-TF:pvr123456789:rvnSupermicro:rnM12SWA-TF:rvr1.01:cvnSupermicro:ct17:cvr0123456789:sku091715D9: dmi.product.family: SMC M12 dmi.product.name: M12SWA-TF dmi.product.sku: 091715D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)
Hi, another peculiarity is that the modem pretends not to support 5G networks, although according to the manufacturer it should - supported modes: General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: 82abc72cff5381e11a96d650c8cfdcf1ae4d838e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_VF | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 862146050381233 System | device: /sys/devices/pci:00/:00:1c.5/:58:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin2 (3) |state: registered | power state: on | access tech: lte | signal quality: 64% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: --- |enabled locks: fixed-dialing | operator id: 23003 |operator name: Vodafone CZ | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 (active) | slot 2: /org/freedesktop/ModemManager1/SIM/1 -- 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/1990700 Title: Fibocom WWAN FM350-GL suspend error (notebook not suspend) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 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 Bug description: [SRU Justification] [Impact] Fibocom WWAN FM350-GL equipped platform fails to suspend. [Fix] Full t7xx driver is still under development and some of them have already accepted and merged in mainline kernel. The following commits are once in the mainline and are reverted in v6.0: d20ef656f994 net: wwan: t7xx: Add AP CLDMA 007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration 140424d90165 net: wwan: t7xx: PCIe reset rescan 87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and coredump collection The first patch implemented the other AP-CLDMA, and with that applied, platforms in question may suspend and resume normally as every bits are in position. However, while these patches had been reverted for another revision that is still being worked on by the hardware vendor, a minimum, sauced patch is created to work-around this first to meet project schedules, and will be reverted and superseded with a final, mainline landing revision. [Test Case] Trigger suspend and there should be no more suspend errors from t7xx: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 [Where problems could occur] The t7xx driver is still incomplete and we're staging aforementioned 4 patches in internal experimental kernels for development use. [Other Info] This affects Kinetic and above, so only Unstable, Kinetic and OEM-6.0 are nominated for fix. == original bug report == Hi, I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module mtk_t7xx . Power management for this modem is bad. When the notebook goes to sleep/suspend, kernel modul
[Kernel-packages] [Bug 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)
Hi, after testing fixed kernels (v6.xx+) I have still same problem - notebook cannot go to sleep/suspend mode. Error mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 is gone. When I suspend my notebook, it will wake up in a moment. It must be the modem because when I replace it with another one everything works fine. Can I provide any additional information to possibly resolve this issue? Thank you. With best regards, John -- 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/1990700 Title: Fibocom WWAN FM350-GL suspend error (notebook not suspend) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 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 Bug description: [SRU Justification] [Impact] Fibocom WWAN FM350-GL equipped platform fails to suspend. [Fix] Full t7xx driver is still under development and some of them have already accepted and merged in mainline kernel. The following commits are once in the mainline and are reverted in v6.0: d20ef656f994 net: wwan: t7xx: Add AP CLDMA 007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration 140424d90165 net: wwan: t7xx: PCIe reset rescan 87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and coredump collection The first patch implemented the other AP-CLDMA, and with that applied, platforms in question may suspend and resume normally as every bits are in position. However, while these patches had been reverted for another revision that is still being worked on by the hardware vendor, a minimum, sauced patch is created to work-around this first to meet project schedules, and will be reverted and superseded with a final, mainline landing revision. [Test Case] Trigger suspend and there should be no more suspend errors from t7xx: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 [Where problems could occur] The t7xx driver is still incomplete and we're staging aforementioned 4 patches in internal experimental kernels for development use. [Other Info] This affects Kinetic and above, so only Unstable, Kinetic and OEM-6.0 are nominated for fix. == original bug report == Hi, I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module mtk_t7xx . Power management for this modem is bad. When the notebook goes to sleep/suspend, kernel module mtk_t7xx return an error: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 So power management failed to suspend: PM: Some devices failed to suspend, or early wake event detected And the notebook not suspend and wake up again. It must be this module, because if I remove the module first (modprobe -r), the laptop goes to sleep and wakes up normally. However, after reinserting the module, the modem no longer appears in the system. Expected state: sleep occurs when the device is put to sleep - including the modem. When you wake up, you will wake up, including activating the modem and logging into the operator's network. Description:Ubuntu 20.04.5 LTS Release:20.04 lspci -v: 58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01) Subsystem: Device 1cf8:3500 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at 601e80 (64-bit, prefetchable) [size=32K] Memory at 5e80 (64-bit, non-prefetchable) [size=8M] Memory at 601e00 (64-bit, prefetchable) [size=8M] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [d0] MSI-X: Enable+ Count=34 Masked- Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [f8] Power Management version 3 Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 Capabilities: [108] Latency Tolerance Reporting Capabilities: [110] L1 PM Substates Capabilities: [200] Advanced Error Reporting
[Kernel-packages] [Bug 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%
I should add that I am using cmake/ninja. Ninja is usually better at maximizing the CPU load than make and my system has 32 true CPU cores and 64 hyperthreading ones. -- 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/2007717 Title: Kernel linux-image-5.19.0-32 regression, compile speed down by 33% Status in linux package in Ubuntu: Incomplete Bug description: I just yesterday and the day before made some benchmark tests for a comparison between ext4 and zfs. I ran repeated builds of a large software package and it always came out to 45s. Now today I ran the same test a few times and it was always 60s. I noticed that today an update ran and that kernel 5.19.0-32 was installed. So just now I booted back to 5.15.0-60-generic:amd64 and ran the test again: back to 45s. I am running Ubuntu 22.04.1 LTS on a AMD Ryzen 3970X with 128GB RAM otherwise there is nothing very special going on. I ran the tests on ZFS and ext4, it makes no difference. To reproduce, I would think that compiling any decent sized software package one on 5.15 and then on 5.19 whould yield the same results. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-15 (217 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=c1b17af6-e10d-4836-a5d0-aa0c25802bca ro mitigations=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: wayland-session jammy Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom davfs2 dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/01/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: TRX40 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd06/01/2020:br5.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
