[Kernel-packages] [Bug 2004531] Re: Touchpad stops working after login when using latest kernel (5.15.0-58-generic)
A few things: 1. The linux-firmware thing might be a red herring; I downgraded the package to the old version (20220329.git681281e4-0ubuntu3.9) and restarted (choosing kernel version 5.15.0-57-generic), and the problem persisted. 2. I noticed that, even when the touchpad wasn’t working, it could still be found using “xinput list” (listed as “SynPS/2 Synaptics TouchPad”) and tested using “sudo evtest”. (Remember, I made sure that the touchpad wasn’t disabled, either by the hardware switch or in “Mouse Preferences.”) This made me wonder if this all was a kernel bug at all (but that was still my best guess, given that previously my touchpad worked under 5.15.0-57-generic but not 5.15.0-58-generic). 3. Finally, I found a fix for my use-case: https://askubuntu.com/questions/815569/ubuntu-16-04-touchpad-stops- working-after-login/1338177#1338177 I tried using “xinput --list-props 'SynPS/2 Synaptics TouchPad'”, and indeed, one of the results displayed was “Synaptics Off (295): 1”. By using “xinput --set-prop 'SynPS/2 Synaptics TouchPad' 'Synaptics Off' 0”, I was able to get the touchpad working again instantly. Just to make sure, I updated linux-firmware to the latest version (20220329.git681281e4-0ubuntu3.10) and restarted into the latest kernel (5.15.0-60-generic), and once again, the touchpad stopped working after login; but once again, I was able to use “xinput --set-prop 'SynPS/2 Synaptics TouchPad' 'Synaptics Off' 0” in the terminal to restore touchpad functionality. (I’ll put that line in my .profile, so that hopefully I won’t have to do it manually again.) So I guess this bug report is now a matter of what disabled the touchpad in the first place using that obscure flag. H… -- 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/2004531 Title: Touchpad stops working after login when using latest kernel (5.15.0-58-generic) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to the latest kernel (5.15.0-58-generic), my laptop’s touchpad has stopped working after the login screen. That is, it works on the login screen, but as soon as I log in (in fact, the moment I press enter after entering my password), the mouse cursor no longer responds to touchpad input. (I’ve made sure that my touchpad is enabled, both by using the touchpad enable/disable button on my laptop, and by checking in “Mouse Preferences” (Preferences → Mouse in the main menu) that the “Enable Touchpad” box is checked.) The mouse buttons below the touchpad, however, still work, and if I plug in a USB mouse, that will work as well. When I restart and select the previous kernel version (5.15.0-57-generic) on boot, the touchpad works again, on the login screen and after. Nevertheless, I’d really appreciate a fix; this laptop is dear to me, and I’d like to be able to use it with the latest kernel updates. I’m using Ubuntu MATE 22.04.01 LTS on a Compaq Presario CQ60. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 2670 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Wed Feb 1 18:36:00 2023 HibernationDevice: RESUME=UUID=3e371ef8-1061-4c6d-b9ab-a072575893c9 InstallationDate: Installed on 2018-05-24 (1715 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard Compaq Presario CQ60 Notebook PC ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=1e6f5cc4-d098-4aaa-9a26-4f3808cfd68d ro quiet splash vt.handoff=7 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.9 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-01-11 (21 days ago) dmi.bios.date: 02/04/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.33 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3617 dmi.board.vendor: Wistron dmi.board.version: 09.48 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Wistron dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.33:bd02/04/2009:svnHewlett-Packard:pnCompaqPresarioCQ60NotebookPC:pvrF.33:rvnWistron:rn3617:rvr09.48:cvnWistron:ct10:cvrChassisVersion:skuNL058PA#AB2: dmi.product.family: 103C_5335KV dmi.product.name: Compaq Presario CQ60 Notebook PC dmi.product.sku: NL058PA#AB2 dmi.product.version: F.33 dmi.sys.vendor: Hewlett-Packard To manage
[Kernel-packages] [Bug 1990876] Re: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module
[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/1990876 Title: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module Status in linux package in Ubuntu: Expired Bug description: Using Ubuntu 22.04, as of yesterday night upon rebooting the framework laptop (which had not been rebooted for several weeks), the fans come on strong and I see, with top, a kworker process at nearly 100% CPU utilization, which makes the laptop unusable. I have an early Framework laptop with an 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz. I removed all USB-c expansion cards except for one with an USB-c pass through, to no avail. With perf I have been able to determine that the xhci_hub_control and perhaps xhci_bus_suspend are at fault. As a matter of fact, the laptop cannot suspend any more, when it was working flawlessly until the reboot. $ sudo apt install linux-tools-common linux-tools-$(uname -r) $ sudo -i # echo -1 > /proc/sys/kernel/perf_event_paranoid # perf record control-c # perf report Samples: 125K of event 'cycles', Event count (approx.): 142991820424 Overhead Command Shared Object Symbol 54.11% kworker/5:2+usb [kernel.kallsyms] [k] xhci_hub_control ◆ 7.94% kworker/5:2+usb [kernel.kallsyms] [k] xhci_bus_suspend ▒ 0.98% kworker/5:2+usb [kernel.kallsyms] [k] kfree ▒ 0.86% kworker/5:2+usb [kernel.kallsyms] [k] _raw_spin_lock_irqsave ... What can be done to address this issue with a kworker? I suspect perhaps the new kernel is at fault. I tried rebooting to the prior kernel 5.15.0-47-generic and 5.15.0-46-generic, but with the same result. What has changed? What can be done about this kworker and the xchi_hub_control? A temporary solution: $ sudo modprobe -r xhci_pci … which results in the kworker process disappearing from `top` (reduced CPU usage to near zero), the fans wind down, and unfortunately the ethernet expansion bay doesn’t work anymore but at least wifi does. Keyboard and touchpad also work. And suspend with deep also work well, just tested it. I assume other expansion bays will stop working too, but the laptop is at least charging: the USB-c pass-through works. See also: https://community.frame.work/t/kworker-stuck-at-near-100-cpu-usage-with-ubuntu-22-04/23053/2 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: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 4870 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 18:14:26 2022 InstallationDate: Installed on 2022-03-11 (199 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 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.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (150 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0B dmi.product.version: AB dmi.sys.vendor: Framework To manage notifications about this bug go
[Kernel-packages] [Bug 2007772] 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/2007772 Title: 7392:c611 Edimax Technology Co., Ltd EdimaxBluetooth Adapter is not currently supported by the installed kernel (5.15) Status in linux package in Ubuntu: Confirmed Bug description: Hi, I wanted to connect my bluetooth headset to my Ubuntu 22.04 LTS system. I purchased a Edimax usb bluetooth dongle (BT8500 with rtl8761b chipset) which has a ubuntu driver for a supportted kernal version of 2.6.32 – 5.3. (apparently) BT USB CHIPS rtl8761bu_fw BTCOEX_20190327-0202 FW_VER= 0x999646b BT UART CHIPS rtl8761b_fw BTCOEX_20190327-0202 FW_VER= 0xd99646b However This device 7392:c611 Edimax Technology Co., Ltd Edimax Bluetooth Adapter is not currently supported by the installed kernel (5.15), neither it is supported by the next 5.19 Ubuntu kernel. Support for this device has been added by this patch to Linux mainline. If you install a recent mainline kernel, the device should work. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/bluetooth/btusb.c?h=v6.1.12=c7577014b74c5369490715015db096182f1a2a23 systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2023-02-09 21:22:48 NZDT; 28min ago Docs: man:bluetoothd(8) Main PID: 1006 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38335) Memory: 2.0M CPU: 133ms CGroup: /system.slice/bluetooth.service └─1006 /usr/lib/bluetooth/bluetoothd Feb 09 21:22:48 Edward bluetoothd[1006]: Starting SDP server Feb 09 21:22:48 Edward bluetoothd[1006]: Bluetooth management interface 1.21 initialized Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 [86619.755586] rtk_btcoex: Close BTCOEX [86619.755592] rtk_btcoex: -x [86619.857321] rtk_btusb: btusb_open start [86619.857326] rtk_btusb: btusb_open hdev->promisc ==0 [86619.857329] rtk_btusb: download_patch start [86619.857331] rtk_btusb: chip type value: 0x74 systemctl status bluetooth.service 13/02 ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2023-02-12 22:01:25 NZDT; 22h ago Docs: man:bluetoothd(8) Main PID: 1008 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38335) Memory: 2.2M CPU: 180ms CGroup: /system.slice/bluetooth.service └─1008 /usr/lib/bluetooth/bluetoothd Feb 13 19:39:54 Edward bluetoothd[1008]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL
[Kernel-packages] [Bug 2007772] [NEW] 7392:c611 Edimax Technology Co., Ltd Edimax Bluetooth Adapter is not currently supported by the installed kernel (5.15)
Public bug reported: Hi, I wanted to connect my bluetooth headset to my Ubuntu 22.04 LTS system. I purchased a Edimax usb bluetooth dongle (BT8500 with rtl8761b chipset) which has a ubuntu driver for a supportted kernal version of 2.6.32 – 5.3. (apparently) BT USB CHIPS rtl8761bu_fw BTCOEX_20190327-0202 FW_VER= 0x999646b BT UART CHIPS rtl8761b_fw BTCOEX_20190327-0202 FW_VER= 0xd99646b However This device 7392:c611 Edimax Technology Co., Ltd Edimax Bluetooth Adapter is not currently supported by the installed kernel (5.15), neither it is supported by the next 5.19 Ubuntu kernel. Support for this device has been added by this patch to Linux mainline. If you install a recent mainline kernel, the device should work. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/bluetooth/btusb.c?h=v6.1.12=c7577014b74c5369490715015db096182f1a2a23 systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2023-02-09 21:22:48 NZDT; 28min ago Docs: man:bluetoothd(8) Main PID: 1006 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38335) Memory: 2.0M CPU: 133ms CGroup: /system.slice/bluetooth.service └─1006 /usr/lib/bluetooth/bluetoothd Feb 09 21:22:48 Edward bluetoothd[1006]: Starting SDP server Feb 09 21:22:48 Edward bluetoothd[1006]: Bluetooth management interface 1.21 initialized Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 [86619.755586] rtk_btcoex: Close BTCOEX [86619.755592] rtk_btcoex: -x [86619.857321] rtk_btusb: btusb_open start [86619.857326] rtk_btusb: btusb_open hdev->promisc ==0 [86619.857329] rtk_btusb: download_patch start [86619.857331] rtk_btusb: chip type value: 0x74 systemctl status bluetooth.service 13/02 ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2023-02-12 22:01:25 NZDT; 22h ago Docs: man:bluetoothd(8) Main PID: 1008 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38335) Memory: 2.2M CPU: 180ms CGroup: /system.slice/bluetooth.service └─1008 /usr/lib/bluetooth/bluetoothd Feb 13 19:39:54 Edward bluetoothd[1008]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down systemctl status snap.bluez.bluez.service × snap.bluez.bluez.service - Service for snap application bluez.bluez Loaded: loaded (/etc/systemd/system/snap.bluez.bluez.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2023-02-08 19:28:26 NZDT; 20min ago Main PID: 1541 (code=exited, status=1/FAILURE) CPU: 32ms Feb 08 19:28:26 Edward systemd[1]: snap.bluez.bluez.service: Failed with result 'exit-code'. Feb 08 19:28:26 Edward bluetoothd[1541]: Unable to get on D-Bus Feb 08
[Kernel-packages] [Bug 2007654] Re: enable Rust support in the kernel
** Changed in: linux (Ubuntu Lunar)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2007654
Title:
enable Rust support in the kernel
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Lunar:
Confirmed
Bug description:
[Impact]
Rust support has been merged starting with linux 6.1.
This support allows to write external kernel modules using the Rust
language. Modules written in this way are linked against the linux
kernel and can be loaded/unloaded like any other .ko module.
Main advantages of writing modules in Rust are:
- memory safety:
- no out of bounds accesses
- no use after free
- data race safety
- strongly typed and statically typed
- code extremely compact
Roughly 70% of the security issues that the MSRC assigns a CVE to are memory
safety issues:
- Rust allows to write more secure and robust kernel code (reduce kernel
CVEs)
We should provide a Rust-enabled kernel so that people have the
possibility to implement their own external kernel modules in Rust.
[Test case]
Build the following "hello world" test module:
== hello_rust.rs ==
// SPDX-License-Identifier: GPL-2.0
//! Rust hello world example.
use kernel::prelude::*;
module! {
type: HelloRust,
name: "hello_rust",
author: "Andrea Righi ",
description: "Rust hello world example",
license: "GPL",
}
struct HelloRust {
}
impl kernel::Module for HelloRust {
fn init(_module: &'static ThisModule) -> Result {
pr_info!("Hello from Rust\n");
Ok(HelloRust { })
}
}
impl Drop for HelloRust {
fn drop( self) {
pr_info!("Goodbye from Rust\n");
}
}
== Makefile ==
NAME=hello_rust
ifndef KERNELRELEASE
ifndef KDIR
KDIR:=/lib/modules/`uname -r`/build
endif
PWD := $(shell pwd)
all:
$(MAKE) -C $(KDIR) M=$(PWD) modules
install:
$(MAKE) -C $(KDIR) M=$(PWD) modules_install
clean:
rm -f *.o *.ko *.mod* .*.cmd *.d Module.symvers modules.order
rm -rf .tmp_versions
else
obj-m := $(NAME).o
endif
[Fix]
Building the Rust support in the kernel requires specific versions of the
Rust compiler and bindgen utility, same to build the external modules in Rust):
- rustc 1.62.0
- bindgen 0.56.0
- clang/llvm (already required by BPF)
Archive should provide these versions (ideally with a version suffix
to avoid conflicting with the stock versions, e.g., rustc-1.62 and
bindgen-0.56).
In addition to that the kernel needs some packaging adjustments to use
these special toolchain binaries and some special (not yet upstream)
patches that would allow to enable mandatory features required in our
generic kernel, such as:
UBUNTU: SAUCE: allows to enable Rust with modversions
UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion
UBUNTU: SAUCE: scripts: Exclude Rust CUs with pahole
UBUNTU: SAUCE: rust: allow to use INIT_STACK_ALL_ZERO
With all of the above we can enable CONFIG_RUST in the kernel and
provide support to build external modules (.ko) using Rust.
[Regression potential]
We may see build regressions due to the inavailability of the proper
toolchain versions. Moreover these toolchain dependencies need to be
maintained, making sure to be always aligned with upstream
requirements, when stable updates are applied to the kernel.
Moreover, hwe kernels require special attention, since this feature
won't be available in old releases (unless the proper toolchain
requirements are met).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007654/+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 2007769] 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/2007769 Title: 7392:c611 Edimax Technology Co., Ltd EdimaxBluetooth Adapter is not currently supported by the installed kernel (5.15) Status in linux package in Ubuntu: Confirmed Bug description: Hi, I wanted to connect my bluetooth headset to my Ubuntu 22.04 LTS system. I purchased a Edimax usb bluetooth dongle (BT8500 with rtl8761b chipset) which has a ubuntu driver for a supportted kernal version of 2.6.32 – 5.3. BT USB CHIPS rtl8761bu_fw BTCOEX_20190327-0202 FW_VER= 0x999646b BT UART CHIPS rtl8761b_fw BTCOEX_20190327-0202 FW_VER= 0xd99646b systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2023-02-09 21:22:48 NZDT; 28min ago Docs: man:bluetoothd(8) Main PID: 1006 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38335) Memory: 2.0M CPU: 133ms CGroup: /system.slice/bluetooth.service └─1006 /usr/lib/bluetooth/bluetoothd Feb 09 21:22:48 Edward bluetoothd[1006]: Starting SDP server Feb 09 21:22:48 Edward bluetoothd[1006]: Bluetooth management interface 1.21 initialized Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 [86619.755586] rtk_btcoex: Close BTCOEX [86619.755592] rtk_btcoex: -x [86619.857321] rtk_btusb: btusb_open start [86619.857326] rtk_btusb: btusb_open hdev->promisc ==0 [86619.857329] rtk_btusb: download_patch start [86619.857331] rtk_btusb: chip type value: 0x74 systemctl status bluetooth.service 13/02 ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2023-02-12 22:01:25 NZDT; 22h ago Docs: man:bluetoothd(8) Main PID: 1008 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38335) Memory: 2.2M CPU: 180ms CGroup: /system.slice/bluetooth.service └─1008 /usr/lib/bluetooth/bluetoothd Feb 13 19:39:54 Edward bluetoothd[1008]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down systemctl status snap.bluez.bluez.service × snap.bluez.bluez.service - Service for snap application bluez.bluez Loaded: loaded (/etc/systemd/system/snap.bluez.bluez.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2023-02-08 19:28:26 NZDT; 20min ago Main PID: 1541 (code=exited, status=1/FAILURE) CPU: 32ms Feb 08 19:28:26 Edward systemd[1]: snap.bluez.bluez.service: Failed with result 'exit-code'. Feb 08
[Kernel-packages] [Bug 2007769] [NEW] 7392:c611 Edimax Technology Co., Ltd Edimax Bluetooth Adapter is not currently supported by the installed kernel (5.15)
Public bug reported: Hi, I wanted to connect my bluetooth headset to my Ubuntu 22.04 LTS system. I purchased a Edimax usb bluetooth dongle (BT8500 with rtl8761b chipset) which has a ubuntu driver for a supportted kernal version of 2.6.32 – 5.3. BT USB CHIPS rtl8761bu_fw BTCOEX_20190327-0202 FW_VER= 0x999646b BT UART CHIPS rtl8761b_fw BTCOEX_20190327-0202 FW_VER= 0xd99646b systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2023-02-09 21:22:48 NZDT; 28min ago Docs: man:bluetoothd(8) Main PID: 1006 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38335) Memory: 2.0M CPU: 133ms CGroup: /system.slice/bluetooth.service └─1006 /usr/lib/bluetooth/bluetoothd Feb 09 21:22:48 Edward bluetoothd[1006]: Starting SDP server Feb 09 21:22:48 Edward bluetoothd[1006]: Bluetooth management interface 1.21 initialized Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 [86619.755586] rtk_btcoex: Close BTCOEX [86619.755592] rtk_btcoex: -x [86619.857321] rtk_btusb: btusb_open start [86619.857326] rtk_btusb: btusb_open hdev->promisc ==0 [86619.857329] rtk_btusb: download_patch start [86619.857331] rtk_btusb: chip type value: 0x74 systemctl status bluetooth.service 13/02 ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2023-02-12 22:01:25 NZDT; 22h ago Docs: man:bluetoothd(8) Main PID: 1008 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38335) Memory: 2.2M CPU: 180ms CGroup: /system.slice/bluetooth.service └─1008 /usr/lib/bluetooth/bluetoothd Feb 13 19:39:54 Edward bluetoothd[1008]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down systemctl status snap.bluez.bluez.service × snap.bluez.bluez.service - Service for snap application bluez.bluez Loaded: loaded (/etc/systemd/system/snap.bluez.bluez.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2023-02-08 19:28:26 NZDT; 20min ago Main PID: 1541 (code=exited, status=1/FAILURE) CPU: 32ms Feb 08 19:28:26 Edward systemd[1]: snap.bluez.bluez.service: Failed with result 'exit-code'. Feb 08 19:28:26 Edward bluetoothd[1541]: Unable to get on D-Bus Feb 08 19:28:26 Edward systemd[1]: snap.bluez.bluez.service: Scheduled restart job, restart counter is at 5. Feb 08 19:28:26 Edward systemd[1]: Stopped Service for snap application bluez.bluez. Feb 08 19:28:26 Edward systemd[1]: snap.bluez.bluez.service: Start request repeated too quickly. Feb 08 19:28:26 Edward systemd[1]: snap.bluez.bluez.service: Failed with result 'exit-code'. Feb 08 19:28:26 Edward systemd[1]: Failed to start Service for snap application bluez.bluez. neale@Edward:~$ ProblemType:
[Kernel-packages] [Bug 2004531] Re: Touchpad stops working after login when using latest kernel (5.15.0-58-generic)
After restarting my laptop recently, the touchpad no longer works under kernel version 5.15.0-57-generic. (Same symptoms: the touchpad works in the login screen, but the moment I log in, it stops working.) My best guess is that this happened because of the linux-firmware update (20220329.git681281e4-0ubuntu3.10, from 20220329.git681281e4-0ubuntu3.9), which of course regenerated the initramfs for each kernel installed. (I installed this update before restarting the computer.) But, that's only my best guess. Let me know if I should mark this bug as affecting linux-firmware, or if you need any other information. Oh, and just to be thorough, I did try the newest kernel (5.15.0-60-generic, newer than my original bug report), and the touchpad still doesn't work (same symptoms as before). This was after installing that linux-firmware update. -- 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/2004531 Title: Touchpad stops working after login when using latest kernel (5.15.0-58-generic) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to the latest kernel (5.15.0-58-generic), my laptop’s touchpad has stopped working after the login screen. That is, it works on the login screen, but as soon as I log in (in fact, the moment I press enter after entering my password), the mouse cursor no longer responds to touchpad input. (I’ve made sure that my touchpad is enabled, both by using the touchpad enable/disable button on my laptop, and by checking in “Mouse Preferences” (Preferences → Mouse in the main menu) that the “Enable Touchpad” box is checked.) The mouse buttons below the touchpad, however, still work, and if I plug in a USB mouse, that will work as well. When I restart and select the previous kernel version (5.15.0-57-generic) on boot, the touchpad works again, on the login screen and after. Nevertheless, I’d really appreciate a fix; this laptop is dear to me, and I’d like to be able to use it with the latest kernel updates. I’m using Ubuntu MATE 22.04.01 LTS on a Compaq Presario CQ60. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 2670 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Wed Feb 1 18:36:00 2023 HibernationDevice: RESUME=UUID=3e371ef8-1061-4c6d-b9ab-a072575893c9 InstallationDate: Installed on 2018-05-24 (1715 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard Compaq Presario CQ60 Notebook PC ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=1e6f5cc4-d098-4aaa-9a26-4f3808cfd68d ro quiet splash vt.handoff=7 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.9 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-01-11 (21 days ago) dmi.bios.date: 02/04/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.33 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3617 dmi.board.vendor: Wistron dmi.board.version: 09.48 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Wistron dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.33:bd02/04/2009:svnHewlett-Packard:pnCompaqPresarioCQ60NotebookPC:pvrF.33:rvnWistron:rn3617:rvr09.48:cvnWistron:ct10:cvrChassisVersion:skuNL058PA#AB2: dmi.product.family: 103C_5335KV dmi.product.name: Compaq Presario CQ60 Notebook PC dmi.product.sku: NL058PA#AB2 dmi.product.version: F.33 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004531/+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 2007759] 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/2007759 Title: Spotify freezes my entire system Status in linux package in Ubuntu: Confirmed Bug description: When I open spotify and have it open for a while my system freezes and I need to hard reset afterwards. ubuntu 22.10 spotify version 1.1.84.716.gc5f8b819 The main error that I always get aren't included in any txt files but here is the one error I copy paste from askubuntu: retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: RW: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: RW: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) -- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1576 F wireplumber /dev/snd/controlC0: adrian 1576 F wireplumber /dev/snd/seq:adrian 1573 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 18 20:11:39 2023 InstallationDate: Installed on 2023-01-27 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 81W1 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=683321d2-f902-45fc-86c5-b0d4410e061a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2023-01-27 (21 days ago) dmi.bios.date: 04/18/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ADA05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE8CN34WW:bd04/18/2022:br1.34:efr1.34:svnLENOVO:pn81W1:pvrIdeaPad315ADA05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315ADA05:skuLENOVO_MT_81W1_BU_idea_FM_IdeaPad315ADA05: dmi.product.family: IdeaPad 3 15ADA05 dmi.product.name: 81W1 dmi.product.sku: LENOVO_MT_81W1_BU_idea_FM_IdeaPad 3 15ADA05 dmi.product.version: IdeaPad 3 15ADA05 dmi.sys.vendor: LENOVO To
[Kernel-packages] [Bug 2007759] Re: Spotify freezes my entire system
** Description changed: When I open spotify and have it open for a while my system freezes and I need to hard reset afterwards. ubuntu 22.10 spotify version 1.1.84.716.gc5f8b819 + + The main error that I always get aren't included in any txt files but + here is the one error I copy paste from askubuntu: + + retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: RW: 0x1 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: RW: 0x1 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) + + -- + ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: adrian 1576 F wireplumber - /dev/snd/controlC0: adrian 1576 F wireplumber - /dev/snd/seq:adrian 1573 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC1: adrian 1576 F wireplumber + /dev/snd/controlC0: adrian 1576 F wireplumber + /dev/snd/seq:adrian 1573 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 18 20:11:39 2023 InstallationDate: Installed on 2023-01-27 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 81W1 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=683321d2-f902-45fc-86c5-b0d4410e061a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-5.19.0-31-generic N/A - linux-backports-modules-5.19.0-31-generic N/A - linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 + 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.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2023-01-27 (21 days ago) dmi.bios.date: 04/18/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ADA05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE8CN34WW:bd04/18/2022:br1.34:efr1.34:svnLENOVO:pn81W1:pvrIdeaPad315ADA05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315ADA05:skuLENOVO_MT_81W1_BU_idea_FM_IdeaPad315ADA05: dmi.product.family: IdeaPad 3 15ADA05 dmi.product.name: 81W1 dmi.product.sku: LENOVO_MT_81W1_BU_idea_FM_IdeaPad 3 15ADA05 dmi.product.version:
[Kernel-packages] [Bug 2007759] [NEW] Spotify freezes my entire system
Public bug reported: When I open spotify and have it open for a while my system freezes and I need to hard reset afterwards. ubuntu 22.10 spotify version 1.1.84.716.gc5f8b819 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1576 F wireplumber /dev/snd/controlC0: adrian 1576 F wireplumber /dev/snd/seq:adrian 1573 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 18 20:11:39 2023 InstallationDate: Installed on 2023-01-27 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 81W1 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=683321d2-f902-45fc-86c5-b0d4410e061a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2023-01-27 (21 days ago) dmi.bios.date: 04/18/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ADA05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE8CN34WW:bd04/18/2022:br1.34:efr1.34:svnLENOVO:pn81W1:pvrIdeaPad315ADA05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315ADA05:skuLENOVO_MT_81W1_BU_idea_FM_IdeaPad315ADA05: dmi.product.family: IdeaPad 3 15ADA05 dmi.product.name: 81W1 dmi.product.sku: LENOVO_MT_81W1_BU_idea_FM_IdeaPad 3 15ADA05 dmi.product.version: IdeaPad 3 15ADA05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007759 Title: Spotify freezes my entire system Status in linux package in Ubuntu: New Bug description: When I open spotify and have it open for a while my system freezes and I need to hard reset afterwards. ubuntu 22.10 spotify version 1.1.84.716.gc5f8b819 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1576 F wireplumber /dev/snd/controlC0: adrian 1576 F wireplumber /dev/snd/seq:adrian 1573 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 18 20:11:39 2023 InstallationDate: Installed on 2023-01-27 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 81W1 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=683321d2-f902-45fc-86c5-b0d4410e061a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2023-01-27 (21 days ago) dmi.bios.date: 04/18/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ADA05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE8CN34WW:bd04/18/2022:br1.34:efr1.34:svnLENOVO:pn81W1:pvrIdeaPad315ADA05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315ADA05:skuLENOVO_MT_81W1_BU_idea_FM_IdeaPad315ADA05: dmi.product.family: IdeaPad 3 15ADA05 dmi.product.name: 81W1 dmi.product.sku: LENOVO_MT_81W1_BU_idea_FM_IdeaPad 3 15ADA05 dmi.product.version: IdeaPad 3 15ADA05 dmi.sys.vendor: LENOVO To manage
[Kernel-packages] [Bug 1986623] Re: cryptsetup fails to decrypt root partion during boot
Searching the web I found and wonder if it is related: https://unix.stackexchange.com/questions/708445/etc-crypttab-not-updating-in-initramfs -- 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. # Running keyslot key derivation. # Reading keyslot area [0x8000]. # 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. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock released. # Verifying key from keyslot 0, digest 0. # Digest 0 (pbkdf2) verify failed with -1. # Trying to open LUKS2 keyslot 1. # Running keyslot key derivation. # Reading keyslot area [0x47000]. # 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. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock released. #
[Kernel-packages] [Bug 2007038] Re: 22.04 ib_mthca BUG: kernel NULL pointer, but had worked in 20.04
I'll note that the infiniband interface is pretty old. It is DDR data rate, while modern ones might use QDR, FDR, HDR, EDR. It might be that the ib_mthca driver has a regression relative to old hardware that isn't noticeable on more recent hardware. Confirmed that this 22.04 system, changed only by running a 5.4.0-139 kernel from 20.04, works fine with this infiniband device. I do have Qlogic IBA7322 IB hardware (ib_qib driver) on other machines here. Will update this thread if I find whether the 5.15.0 kernel appears to work with 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/2007038 Title: 22.04 ib_mthca BUG: kernel NULL pointer, but had worked in 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I run some x86_64 machines with Infiniband interfaces (Mellanox MT25204, ib_mthca driver + ib_ipoib for IP-over-IB). This had worked fine for years under Ubuntu 20.04.1 LTS and under RHEL6 before it. But as soon as I updated to 22.04.1 LTS -- with both its default 5.15.0-60-generic kernel and also 6.1.0-1006-oem (the latest packaged one I could find), the IB interface doesn't work. dmesg shows some UBSAN shift-out-of-bounds warnings in mthca modules, e.g. "shift exponent -25557 is negative". That's a bizarre number - maybe a hint of something uninitialized? The crippling symptom shows up within a second after that: a NULL dereference within the ib_mthca driver -- the "BUG: kernel NULL pointer dereference", in mthca_poll_one. The interface never sets its RUNNING flag (as shown by ifconfig). The rest of the system remains usable after the "BUG" message -- the ethernet, disk, etc. drivers and other functions work as expected. Attempting to unload the ib_mthca driver causes a kernel panic. Is there anything I should try? Should I build a kernel from source with debugging? I could try installing the 5.4.0 kernel from 20.04, but would rather use something that will continue to get security patches. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 12 14:12 seq crw-rw+ 1 root audio 116, 33 Feb 12 14:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Sun Feb 12 14:17:28 2023 InstallationDate: Installed on 2020-11-22 (812 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro X7DBR-8 PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=8624cf02-e743-4da6-9209-14ef2c2abd10 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-60-generic N/A linux-backports-modules-5.15.0-60-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-02-10 (2 days ago) dmi.bios.date: 12/03/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: X7DBR-8 dmi.board.vendor: Supermicro dmi.board.version: PCB Version dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/03/2007:svnSupermicro:pnX7DBR-8:pvr0123456789:rvnSupermicro:rnX7DBR-8:rvrPCBVersion:cvnSupermicro:ct1:cvr0123456789:sku: dmi.product.name: X7DBR-8 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007038/+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 1986623] Re: cryptsetup fails to decrypt root partion during boot
(Correction: previously it asked to decrypt sda3_crypt, not /dev/sda3.) -- 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. # Running keyslot key derivation. # Reading keyslot area [0x8000]. # 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. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock released. # Verifying key from keyslot 0, digest 0. # Digest 0 (pbkdf2) verify failed with -1. # Trying to open LUKS2 keyslot 1. # Running keyslot key derivation. # Reading keyslot area [0x47000]. # 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. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock released. # Verifying key from keyslot 1, digest 0. # Digest 0 (pbkdf2) verify
[Kernel-packages] [Bug 1986623] Re: cryptsetup fails to decrypt root partion during boot
Success?
Based only on the error message, I tried defining tmpData in
/etc/crypttab. Previously, the file consisted of one line:
sda6_crypt UUID={uuid} none luks,discard
I added a second line:
tmpData UUID={uuid} none luks,discard
and re-ran update-initramfs. It still produced the other messages above
(lines starting with I:), but on reboot it did not drop me into a
busybox shell.
Note that it did ask me for the password for tmpData, where before it
was asking for the password for /dev/sda3 (the encrypted partition), but
otherwise it appears to have booted normally.
So, not entirely sure if this is a solution or a kludge.
--
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.
# Running keyslot key derivation.
# Reading keyslot area [0x8000].
# 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.
# Reusing open ro fd on device /dev/nvme0n1p3
# Device /dev/nvme0n1p3 READ lock
[Kernel-packages] [Bug 1986623] Re: cryptsetup fails to decrypt root partion during boot
I'm getting a bit over my head, but it is seeming like there's a problem with creating a new initrd. When I decrypt (using unmkinitramfs) the initrd.img file, I see that the "good" version has a /main/cryptroot/crypttab file which appears identical to /etc/crypttab. The "bad" version has an empty file there (0 bytes). Attempting to manually repair (using sudo update-initramfs -u) gives the following error: cryptsetup: WARNING: target 'tmpData' not found in /etc/crypttab I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set RESUME variable to override this. The file thus generated has a zero-byte crypttab file as before. Therefore, I'm thinking the problem is here, in the generation of the initramfs. Anyone have a clue from the above? Should I be posting a new bug report indicating that update-initramfs is failing? -- 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. # Running keyslot key derivation. # Reading keyslot area [0x8000]. # Acquiring read lock for device /dev/nvme0n1p3.
[Kernel-packages] [Bug 1564463] Re: Joystick Dragonrise Axes confused in Ubuntu 14.04
Hello, I sadly can confirm that this issue still do exist. Ubuntu 22.04.1 LTS Linux version 6.1.12-x64v3-xanmod1 The axis 2 is bounded to horizontal movement in left stick and vertical movement in right stick. -- 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/1564463 Title: Joystick Dragonrise Axes confused in Ubuntu 14.04 Status in linux package in Ubuntu: Fix Released Status in linux package in Debian: Fix Released Bug description: In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly working. Its conflicting and superimposed by axis 0 (left-right of the left joystick) Axis 2 was allready behaving bad in eralier versions now its completly broken. Also jscal complains when applying stored settings from earlier ubuntu versions as the joystick now has 6 axes [0-5] and used to have 7, but this seems correct. The Dragonrise chip seems to be very widespread among different speedlink and LinQ models There is a related bugreport in Debian Bug-Tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606 that makes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+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 2007717] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648237/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648236/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648241/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648238/+files/PulseList.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/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 2007717] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648242/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648240/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648239/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648235/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648234/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648229/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648233/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648228/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648232/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648231/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648230/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648227/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648226/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648225/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%
apport information ** Tags added: apport-collected jammy wayland-session ** Description changed: 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. + 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. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648223/+files/AlsaInfo.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/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:
[Kernel-packages] [Bug 2007717] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/2007717/+attachment/5648224/+files/AudioDevicesInUse.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/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 2007745] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2007745 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007745 Title: [hwe-5.15] CONFIG_PCI_MESON not enabled Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: New Bug description: The PCI driver for the amlogic-based Meson platforms (CONFIG_PCI_MESON) is not enabled as a module in the 5.15 HWE kernel configuration: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/tree/debian.hwe-5.15/config/config.common.ubuntu?h=Ubuntu- hwe-5.15-5.15.0-66.73_20.04.1#n7702 This driver is important for systems like the ODROID HC4, which uses a PCIE-SATA bridge to provide a storage interface. This system is fully supported by the kernel (including a device tree), except for the fact that this PCI driver is disabled. Please look into enabling this for future releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007745] [NEW] [hwe-5.15] CONFIG_PCI_MESON not enabled
Public bug reported: The PCI driver for the amlogic-based Meson platforms (CONFIG_PCI_MESON) is not enabled as a module in the 5.15 HWE kernel configuration: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/tree/debian.hwe-5.15/config/config.common.ubuntu?h=Ubuntu- hwe-5.15-5.15.0-66.73_20.04.1#n7702 This driver is important for systems like the ODROID HC4, which uses a PCIE-SATA bridge to provide a storage interface. This system is fully supported by the kernel (including a device tree), except for the fact that this PCI driver is disabled. Please look into enabling this for future releases. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-hwe-5.15 (Ubuntu) ** Summary changed: - [hwe-5.15] CONFIG_PCI_MESON not enabled + CONFIG_PCI_MESON not enabled ** Summary changed: - CONFIG_PCI_MESON not enabled + [hwe-5.15] CONFIG_PCI_MESON not enabled ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007745 Title: [hwe-5.15] CONFIG_PCI_MESON not enabled Status in linux package in Ubuntu: New Status in linux-hwe-5.15 package in Ubuntu: New Bug description: The PCI driver for the amlogic-based Meson platforms (CONFIG_PCI_MESON) is not enabled as a module in the 5.15 HWE kernel configuration: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/tree/debian.hwe-5.15/config/config.common.ubuntu?h=Ubuntu- hwe-5.15-5.15.0-66.73_20.04.1#n7702 This driver is important for systems like the ODROID HC4, which uses a PCIE-SATA bridge to provide a storage interface. This system is fully supported by the kernel (including a device tree), except for the fact that this PCI driver is disabled. Please look into enabling this for future releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-intel-iotg/5.15.0.1026.25)
All autopkgtests for the newly accepted linux-meta-intel-iotg (5.15.0.1026.25) for jammy have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.35-0ubuntu3.1 (amd64) linux-intel-iotg/5.15.0-1026.31 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-intel-iotg [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key
This bug is awaiting verification that the linux-raspi2/4.15.0-1128.136 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-bionic-linux-raspi2 -- 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/2002812 Title: Revoke & rotate to new signing key Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * Revoke & rotate to new signing key * Update revocations, which match the next Ubuntu shim 15.7 revocations. Specifically - revoke certs that were previously protected with by-hash revocations, revoke lost/unused certificates. * Start using advantage2021v1 and ubuntu2022v1 signing keys. * This is a routine key rotation. [ Test Plan ] * Check that old shim/grub boot this kernel * Check that the upcomming future shim/grub can boot this kernel * Check that these kernels can do signed kexec into itself [ Where problems could occur ] * Kernels with this patch applied should be signed using ubuntu/4 pro/3 core/2 signing streams. [ Other Info ] * TPM PCR values and measurements will change when changing the signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002812/+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
