[Kernel-packages] [Bug 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
I have this happened to me in the Kubuntu 23.04 Live installer also. nvidia 3060ti ko. Safe graphics works as a workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+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 2019076] [NEW] Raptor Lake S/P Audio Enablement
Public bug reported: [Summary] Support audio on Raptor Lake S/P ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided Assignee: Jian Hui Lee (jianhuilee) Status: New ** Also affects: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-intel-iotg (Ubuntu) Status: New => Invalid ** Changed in: linux-intel-iotg (Ubuntu Jammy) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2019076 Title: Raptor Lake S/P Audio Enablement Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: New Bug description: [Summary] Support audio on Raptor Lake S/P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2019076/+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 1942260] Re: compress firmware in /lib/firmware
Fedora's individual binary firmware xz compression plans seem to be a success. They kept going and divided the package into many different firmware packages. https://packages.fedoraproject.org/pkgs/linux-firmware/ https://packages.fedoraproject.org/pkgs/linux-firmware/intel-gpu- firmware/fedora-38-updates.html#files -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1942260 Title: compress firmware in /lib/firmware Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware-raspi2 package in Ubuntu: Confirmed Bug description: -- initramfs-tools [Impact] * linux supports xz compressed linux-firmware which saves disk space. In focal, initramfs-tools only knows how to included uncompressed firmware files (even when kernel supports loading compressed ones). Newer releases of linux-firmware may use compressed firmware files only, in such cases it would be nice for focal's initramfs-tools to support compressed firmware files in case of partial or incomplete upgrades (i.e. linux-firmware force installed or upgraded, without newer initramfs-tools). The proposed changes to initramfs-tools are backwards and forwards compatible, they prefer to include uncompressed firmware files; and if missing, include compressed firmware files in their uncompressed form. Thus maintaining compatibility with any kernels, irrespective of compressed/uncompressed firmware inputs. [Test Plan] * Compress all files shipped by linux-firmware with xz * Rebuild initrd * Check that all the same firmware files are still included in the initramfs, in their uncompressed form as before [Where problems could occur] * This SRU is precautionary to prevent accidental installation of compressed linux-firmware from generating incorrect initramfs. It should be noted that whilst initramfs-tools would create a compatible initramfs with any kernels, pre-v5.3 kernels do not support xz compressed firmware files at runtime. Mixing this new initramfs with compressed firmwares and pre 5.3 kernels may lead to expectations of supporting compressed firmware files with them only working at initrd stage and not at runtime. [Other Info] Original bug report Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019000] Re: Use new annotations model
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Low ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019000 Title: Use new annotations model Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Confirmed Bug description: [Impact] Starting with lunar we have introduced a new way to manage kernel configs, unifying the duplicated information defined in the annotations file + config chunks into an annotations-only model. [Test case] A kernel build can be considered a valid test case, in particular the specific command that is used to update the .config's for all the supported architectures and flavours: $ fakeroot debian/rules updateconfigs [Fix] Import the required changes in debian/ from lunar (with the required adjustments) to support the annotations-only model also in all the previous releases. [Regression potential] We may experience regressions during the updateconfigs step, especially with derivatives. Moreover, derivatives that want to transition to the new annotations model require to adjust the header in the annotations file as following (make sure to define the corresponding architectures and flavours): # FORMAT: 4 # ARCH: amd64 arm64 armhf ppc64el s390x # FLAVOUR: amd64-generic amd64-lowlatency arm64-generic arm64-generic-64k arm64-lowlatency arm64-lowlatency-64k armhf-generic armhf-generic-lpae ppc64el-generic s390x-generic After adjusting the header a special command is provided to transition to the new annotations-only model: $ fakeroot debian/rules migrateconfigs This command should automatically import the old configs into the new annotations file. A kernel with this change applied can still support the old annotations+configs model, the transition to the new model is not mandatory. Basically without using `fakeroot debian/rules migrateconfigs` the updateconfigs step will continue to use the old model and the old scripts (that is the safest approach to avoid potential unexpected .config changes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019000/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015498] Re: Debian autoreconstruct Fix restoration of execute permissions
** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-bionic verification-done-focal verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015498 Title: Debian autoreconstruct Fix restoration of execute permissions Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Confirmed Bug description: SRU justification [Impact] Debian source package diffs cannot represent that a file should be executable. gen-auto-reconstruct detects when a commit adds a script that is supposed to be invoked during the build and restores the execute permissions in the reconstruct script by adding `chmod +x $file`. But, if a file removes its execute permission, this will change it back. This happened in the last jammy release (version 5.15.0-70.77) where a commit from upstream removed the execute permission for a header file but then our scripts brought it back. [Fix] Andy proposed the following fix https://dpaste.com/6SJ8YR3BM Basically it checks if the permission was added or removed and uses either +x or -x. [Test plan] Easily tested with jammy-kvm, latest release where a rebase picked this commit "treewide: fix up files incorrectly marked executable" where `drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 644 (removed execute). When debian packages are prepared, you'll notice the file has changed its permission back to 755. With the fix, it should be the same. [Regression potential] Low, it is a small fix. Scripts will still have execute permission. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015498/+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 1499869] Re: maas wily deployment to HP Proliant m400 arm64 server cartridge fails
Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/2586 ** Bug watch added: github.com/canonical/cloud-init/issues #2586 https://github.com/canonical/cloud-init/issues/2586 -- 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/1499869 Title: maas wily deployment to HP Proliant m400 arm64 server cartridge fails Status in cloud-init: Fix Released Status in curtin: Invalid Status in cloud-init package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in cloud-init source package in Wily: Fix Released Status in linux source package in Wily: Fix Released Bug description: This is the error seen on the console: [ 64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]: Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin [ 124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2427570/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect timeout=50.0)'))] [ 124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds [ 124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 - url_helper.py[WARNING]: Calling 'http:///latest/meta-data/instance-id' failed [0/120s]: bad status code [404] This times out eventually and the node is left at the login prompt. I can install wily via netboot without issue and some time back, wily was deployable to this node from MAAS. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1499869/+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 2013209] Re: expoline.o is packaged unconditionally for s390x
> While this works as expected on Jammy, ... Do we need to test it for jammy, then? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2013209 Title: expoline.o is packaged unconditionally for s390x Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.15 package in Ubuntu: New Status in linux-hwe-5.15 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: https://bugs.launchpad.net/bugs/1639924 enabled CONFIG_EXPOLINE_EXTERN for s390x in Jammy. While this works as expected on Jammy, it won't work on some derivatives of it: for example focal:hwe-5.15. On Focal, this config can't be enabled due to the GCC version it comes with. CONFIG_EXPOLINE_EXTERN requires >= 110200 while Focal comes with 90400. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013209/+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 2008774] Re: Ubuntu 22.04 not waking up after second suspend
In response to #11, I installed the mainline software (https://github.com/bkw777/mainline) and installed kernel 6.2.14, the newest of version 6.2, and restarted with this new kernel version. Unfortunately, kernel 6.2.14 does not fix the suspend issue. I remind you that I made this test with ubuntu 20.04 LTS. A few days ago I downgraded from 22.04 LTS as a test against message #7. Do you consider that installing kernel 6.2.14 with a newer ubuntu version would solve the problem? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015972] Re: Dell: Enable speaker mute hotkey LED indicator
I see this is verified against the proposed kernel for Jammy. But Lunar and Kinetic look like they have been tested only against locally patched kernels, rather than the Ubuntu archive. I would expect SRU verifications for hardware enablements to be tested exclusively against the Ubuntu archive before releasing them into -updates. What's the plan for Lunar and Kinetic, please? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2015972 Title: Dell: Enable speaker mute hotkey LED indicator Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: Invalid Status in alsa-ucm-conf source package in Lunar: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2015972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015972] Re: Dell: Enable speaker mute hotkey LED indicator
Also is there any testing being done to ensure that other use cases of alsa-ucm-conf haven't regressed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2015972 Title: Dell: Enable speaker mute hotkey LED indicator Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: Invalid Status in alsa-ucm-conf source package in Lunar: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2015972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015972] Re: Dell: Enable speaker mute hotkey LED indicator
@Robie, let me check it, I SRUed for L/K/J/OEM-6.1 and got ACKed. https://lists.ubuntu.com/archives/kernel-team/2023-April/138680.html i verified on machines, one equipped mute-led and another is w/o. Is there any issues you are facing? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2015972 Title: Dell: Enable speaker mute hotkey LED indicator Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: Invalid Status in alsa-ucm-conf source package in Lunar: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2015972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1551747] Re: ubuntu-fan causes issues during network configuration
Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/2623 ** Bug watch added: github.com/canonical/cloud-init/issues #2623 https://github.com/canonical/cloud-init/issues/2623 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1551747 Title: ubuntu-fan causes issues during network configuration Status in cloud-init: Invalid Status in Snappy: Invalid Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: Fix Released Status in ubuntu-fan source package in Yakkety: Fix Released Bug description: it seems that ubuntu-fan is causing issues with network configuration. On 16.04 daily image: root@localhost:~# snappy list NameDate Version Developer canonical-pi2 2016-02-02 3.0 canonical canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical ubuntu-core 2016-02-22 16.04.0-10.armhf canonical I see this when I'm activating a wifi card on a raspberry pi 2. root@localhost:~# ifdown wlan0 ifdown: interface wlan0 not configured root@localhost:~# ifup wlan0 Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/wlan0/c4:e9:84:17:31:9b Sending on LPF/wlan0/c4:e9:84:17:31:9b Sending on Socket/fallback DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x81c0c95e) DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x81c0c95e) DHCPREQUEST of 192.168.0.170 on wlan0 to 255.255.255.255 port 67 (xid=0x5ec9c081) DHCPOFFER of 192.168.0.170 from 192.168.0.251 DHCPACK of 192.168.0.170 from 192.168.0.251 RTNETLINK answers: File exists bound to 192.168.0.170 -- renewal in 17145 seconds. run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1 Failed to bring up wlan0. === [Impact] Installing ubuntu-fan can trigger error messages when initialising with no fan configuration. [Test Case] As above. [Regression Potential] Low, suppresses errorneous error messages. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1551747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
I narrowed this issue down to *not* being downstream, and I narrowed this down to a particular commit, along with a script that replicates the issue. I hope this information is helpful. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Bug description: Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem actually results in success I then built a Kubuntu Lunar VM, and was able to replicate it on not just my system. When I built and install the vanilla kernel with bindeb-pkg, and then I boot the vanilla kernel, I can't replicate it, the second filesystem unmounts. When I reboot the VM, and start the default distribution kernel, I am able to replicate the issue, the second filesystem being unable to unmount, with "target is busy" with no files open according to standard usermode tools, when chroot is called on it I tried to look at patches in git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar and git log --oneline --grep="sauce" but none of them really look relevant. I could be VERY wrong in this matter though SUMMARY: Long story short, (I am VERY sorry about the length:) I make an overlayfs, I make a second overlayfs with the first overlayfs as the second one's lowerdir, I chroot into the second overlayfs, and then later I can't unmount the second one as it says "Target is busy", but the user mode tools don't show any files open at all. If I mount the second overlayfs, and then unmount it without ever chroot-ing into it I AM able to unmount it The attached script should replicate the issue This doesn't seem to happen on the vanilla Linux kernel, with the same as close as possible config that Ubuntu uses Thanks ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nerdopolis 3007 F wireplumber /dev/snd/controlC0: nerdopolis 3007 F wireplumber /dev/snd/seq:nerdopolis 3003 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Apr 15 19:08:48 2023 InstallationDate: Installed on 2023-04-09 (6 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230408) MachineType: ASRock B650M PG Ri
[Kernel-packages] [Bug 2019076] Re: Raptor Lake S/P Audio Enablement
** Tags added: lookout-canyon oem-priority originate-from-2000203 ** Tags added: originate-from-2011689 ** Tags added: originate-from-2012910 ** Tags added: originate-from-2013018 ** Tags added: originate-from-2013020 ** Tags added: originate-from-2013028 ** Tags added: originate-from-2013435 ** No longer affects: hwe-next -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2019076 Title: Raptor Lake S/P Audio Enablement Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: New Bug description: [Summary] Support audio on Raptor Lake S/P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2019076/+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 1628204] Re: linux: 4.4.0-41.61 -proposed tracker
thanks for sharing https://7dstierlister.com/7ds-tier-list-jp/ -- 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/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 2019108] [NEW] XSAVE consistency problem preventing avx on KVM guests
Public bug reported: On an openstack KVM guest VM the following kernel message is displayed: "XSAVE consistency problem: size 2560 != kernel_size 0" (see further traces collected through "ubuntu-bug linux" command) As a result, the avx feature isn't enabled in the kernel, failing some programs that require it (e.g mongodb requires avx instruction set). This problem reproduces on 23.04 Lua kernel (6.2.0-20), 22.04 Jammy HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). I'm suspecting a kernel regression since v>5.15 that would be more strict with possibly QEMU emulated XSAVE CPUID features. Related yet unanswered support question: https://askubuntu.com/questions/1467238/xsave-consistency-problem- preventing-avx-on-kvm-guests-running-jammy-hwe This looks similar to the following kernel thread https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/ Although I don't yet have access to the KVM hypervisor host, I'd like to know if there is a possible workaround by fixing KVM/QEMU configuration possibly enabling XSAVEC in addition to XSAVES feature in the KVM guest, for upgrading KVM/QEMU version. Full diagnostics performed so far at https://github.com/orange- cloudfoundry/paas-templates/issues/1960#issuecomment-1534484042 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 10 12:31:18 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=03a4e7a1-715a-4ceb-8fa6-d86a817a7092 ro vconsole.keymap=us net.ifnames=0 biosdevname=0 crashkernel=auto selinux=0 plymouth.enable=0 console=ttyS0,115200n8 earlyprintk=ttyS0 rootdelay=300 ipv6.disable=1 audit=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=false quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1:bd04/01/2014:br0.0:svnOpenStackFoundation:pnOpenStackNova:pvr13.2.1-20220808115737_bd245dd:cvnQEMU:ct1:cvrpc-i440fx-2.8:sku: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 13.2.1-20220808115737_bd245dd dmi.sys.vendor: OpenStack Foundation ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug lunar -- 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/2019108 Title: XSAVE consistency problem preventing avx on KVM guests Status in linux package in Ubuntu: Incomplete Bug description: On an openstack KVM guest VM the following kernel message is displayed: "XSAVE consistency problem: size 2560 != kernel_size 0" (see further traces collected through "ubuntu-bug linux" command) As a result, the avx feature isn't enabled in the kernel, failing some programs that require it (e.g mongodb requires avx instruction set). This problem reproduces on 23.04 Lua kernel (6.2.0-20), 22.04 Jammy HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). I'm suspecting a kernel regression since v>5.15 that would be more strict with possibly QEMU emulated XSAVE CPUID features. Related yet unanswered support question: https://askubuntu.com/questions/1467238/xsave-consistency-problem- preventing-avx-on-kvm-guests-running-jammy-hwe This looks similar to the following kernel thread https://lore.kernel.o
[Kernel-packages] [Bug 2018438] Re: Jammy update: v5.15.99 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018438 Title: Jammy update: v5.15.99 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.99 upstream stable release from git://git.kernel.org/ HID: asus: use spinlock to protect concurrent accesses HID: asus: use spinlock to safely schedule workers powerpc/mm: Rearrange if-else block to avoid clang warning ARM: OMAP2+: Fix memory leak in realtime_counter_init() arm64: dts: qcom: qcs404: use symbol names for PCIe resets arm64: dts: qcom: msm8996-tone: Fix USB taking 6 minutes to wake up arm64: dts: qcom: sm8150-kumano: Panel framebuffer is 2.5k instead of 4k arm64: dts: qcom: sm6125: Reorder HSUSB PHY clocks to match bindings arm64: dts: imx8m: Align SoC unique ID node unit address ARM: zynq: Fix refcount leak in zynq_early_slcr_init arm64: dts: mediatek: mt8183: Fix systimer 13 MHz clock description arm64: dts: qcom: sdm845-db845c: fix audio codec interrupt pin name arm64: dts: qcom: sc7180: correct SPMI bus address cells arm64: dts: qcom: sc7280: correct SPMI bus address cells arm64: dts: meson-gx: Fix Ethernet MAC address unit name arm64: dts: meson-g12a: Fix internal Ethernet PHY unit name arm64: dts: meson-gx: Fix the SCPI DVFS node name and unit address arm64: dts: msm8992-bullhead: add memory hole region arm64: dts: qcom: msm8992-bullhead: Fix cont_splash_mem size arm64: dts: qcom: msm8992-bullhead: Disable dfps_data_mem arm64: dts: qcom: ipq8074: correct USB3 QMP PHY-s clock output names arm64: dts: qcom: Fix IPQ8074 PCIe PHY nodes arm64: dts: qcom: ipq8074: fix PCIe PHY serdes size arm64: dts: qcom: ipq8074: fix Gen3 PCIe QMP PHY arm64: dts: qcom: ipq8074: correct Gen2 PCIe ranges arm64: dts: qcom: ipq8074: fix Gen3 PCIe node arm64: dts: qcom: ipq8074: correct PCIe QMP PHY output clock names arm64: dts: meson: remove CPU opps below 1GHz for G12A boards ARM: OMAP1: call platform_device_put() in error case in omap1_dm_timer_init() ARM: bcm2835_defconfig: Enable the framebuffer ARM: s3c: fix s3c64xx_set_timer_source prototype arm64: dts: ti: k3-j7200: Fix wakeup pinmux range ARM: dts: exynos: correct wr-active property in Exynos3250 Rinato ARM: imx: Call ida_simple_remove() for ida_simple_get arm64: dts: amlogic: meson-gx: fix SCPI clock dvfs node name arm64: dts: amlogic: meson-axg: fix SCPI clock dvfs node name arm64: dts: amlogic: meson-gx: add missing SCPI sensors compatible arm64: dts: amlogic: meson-gxl-s905d-sml5442tw: drop invalid clock-names property arm64: dts: amlogic: meson-gx: add missing unit address to rng node name arm64: dts: amlogic: meson-gxl: add missing unit address to eth-phy-mux node name arm64: dts: amlogic: meson-gx-libretech-pc: fix update button name arm64: dts: amlogic: meson-sm1-bananapi-m5: fix adc keys node names arm64: dts: amlogic: meson-gxl-s905d-phicomm-n1: fix led node name arm64: dts: amlogic: meson-gxbb-kii-pro: fix led node name arm64: dts: amlogic: meson-sm1-odroid-hc4: fix active fan thermal trip locking/rwsem: Optimize down_read_trylock() under highly contended case locking/rwsem: Disable preemption in all down_read*() and up_read() code paths arm64: dts: renesas: beacon-renesom: Fix gpio expander reference arm64: dts: meson: bananapi-m5: switch VDDIO_C pin to OPEN_DRAIN ARM: dts: sun8i: nanopi-duo2: Fix regulator GPIO reference ARM: dts: imx7s: correct iomuxc gpr mux controller cells arm64: dts: mt8192: Fix CPU map for single-cluster SoC arm64: dts: mediatek: mt7622: Add missing pwm-cells to pwm node blk-mq: avoid sleep in blk_mq_alloc_request_hctx blk-mq: remove stale comment for blk_mq_sched_mark_restart_hctx blk-mq: correct stale comment of .get_budget arm64: dts: qcom: msm8992-lg-bullhead: Correct memory overlaps with the SMEM and MPSS memory regions s390/dasd: Fix potential memleak in dasd_eckd_init() sched/deadline,rt: Remove unused parameter from pick_next_[rt|dl]_entity() sched/rt: pick_next_rt_entity(): check list_entry x86/perf/zhaoxin: Add stepping check for ZXC KEYS: asymmetric: Fix ECDSA use via keyctl uapi arm64: dts: qcom: pmk8350: Specify PBS register for PON arm64: dts: qcom: pmk8350: Use the correct PON com
[Kernel-packages] [Bug 2019108] 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 2019108 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/2019108 Title: XSAVE consistency problem preventing avx on KVM guests Status in linux package in Ubuntu: Incomplete Bug description: On an openstack KVM guest VM the following kernel message is displayed: "XSAVE consistency problem: size 2560 != kernel_size 0" (see further traces collected through "ubuntu-bug linux" command) As a result, the avx feature isn't enabled in the kernel, failing some programs that require it (e.g mongodb requires avx instruction set). This problem reproduces on 23.04 Lua kernel (6.2.0-20), 22.04 Jammy HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). I'm suspecting a kernel regression since v>5.15 that would be more strict with possibly QEMU emulated XSAVE CPUID features. Related yet unanswered support question: https://askubuntu.com/questions/1467238/xsave-consistency-problem- preventing-avx-on-kvm-guests-running-jammy-hwe This looks similar to the following kernel thread https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/ Although I don't yet have access to the KVM hypervisor host, I'd like to know if there is a possible workaround by fixing KVM/QEMU configuration possibly enabling XSAVEC in addition to XSAVES feature in the KVM guest, for upgrading KVM/QEMU version. Full diagnostics performed so far at https://github.com/orange- cloudfoundry/paas-templates/issues/1960#issuecomment-1534484042 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 10 12:31:18 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=03a4e7a1-715a-4ceb-8fa6-d86a817a7092 ro vconsole.keymap=us net.ifnames=0 biosdevname=0 crashkernel=auto selinux=0 plymouth.enable=0 console=ttyS0,115200n8 earlyprintk=ttyS0 rootdelay=300 ipv6.disable=1 audit=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=false quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1:bd04/01/2014:br0.0:svnOpenStackFoundation:pnOpenStackNova:pvr13.2.1-20220808115737_bd245dd:cvnQEMU:ct1:cvrpc-i440fx-2.8:sku: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 13.2.1-20220808115737_bd245dd dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https
[Kernel-packages] [Bug 2015097] Re: Kernel crash during Mellanox performance testing
Tested with 5.15.0-72.79: [ Test Case ] * Boot testing passed * IBM tested functionality indirectly through derivative IBM kernel that got same patch ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015097 Title: Kernel crash during Mellanox performance testing Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: [Impact] * When performance testing using Mellanox driver, an early decrement within an if condition rather than as a result of an if condition is causing null pointer crashes. [Fix] * Clean cherry-pick from upstream (https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/) * Change landed v5.19 upstream, Kinetic onward not affected [Test Case] * Compile test * Boot test * Performance test [Where things could go wrong] * Regression risk is low, localized fix, purely fixes incorrect logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015097/+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 2019108] Re: XSAVE consistency problem preventing avx on KVM guests
This looks similar to the following kernel thread
https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/
> Apparently "size 832 != kernel_size 0" so let the debugging continue...
[...]
> So we've actually found and fixed the issue, but XSAVE and therefore
automatically gnarly.
> https://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=c3bd0b83ea5b7c0da6542687436042eeea1e7909
>
>There is no real hardware with XSAVEC but not XSAVES; the spec does try
>to distinguish the two, and it's useful for virt to offer XSAVEC without
>XSAVES.
>
>CPUID.0xd[1].ebx is spec'd as the total size for XSAVES of all current
>XCR0|XSS states. This is known dodgy already for native, as it leaks
>the current MSR_XSS setting into userspace.
>
>I had written the logic originally to hide this dynamic field if XSAVES
>wasn't enumerated, but Linux now uses it if XSAVEC is enumerated, to
>cross-check what it can see elsewhere in the CPUID state.
On a guest VM running the same hypervisor, we see the xsavec feature is present
but not xsaves.
https://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=c3bd0b83ea5b7c0da6542687436042eeea1e7909
mentions
> While the SDM isn't very clear about this, our present behavior make
> Linux 5.19 unhappy. As of commit 8ad7e8f69695 ("x86/fpu/xsave: Support
> XSAVEC in the kernel") they're using this CPUID output also to size
> the compacted area used by XSAVEC. Getting back zero there isn't really
> liked, yet for PV that's the default on capable hardware: XSAVES isn't
> exposed to PV domains.
>
> Considering that the size reported is that of the compacted save area,
> I view Linux'es assumption as appropriate (short of the SDM properly
> considering the case). Therefore we need to populate the field also when
> only XSAVEC is supported for a guest.
--
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/2019108
Title:
XSAVE consistency problem preventing avx on KVM guests
Status in linux package in Ubuntu:
Incomplete
Bug description:
On an openstack KVM guest VM the following kernel message is
displayed: "XSAVE consistency problem: size 2560 != kernel_size 0"
(see further traces collected through "ubuntu-bug linux" command)
As a result, the avx feature isn't enabled in the kernel, failing some
programs that require it (e.g mongodb requires avx instruction set).
This problem reproduces on 23.04 Lua kernel (6.2.0-20), 22.04 Jammy
HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78).
I'm suspecting a kernel regression since v>5.15 that would be more
strict with possibly QEMU emulated XSAVE CPUID features.
Related yet unanswered support question:
https://askubuntu.com/questions/1467238/xsave-consistency-problem-
preventing-avx-on-kvm-guests-running-jammy-hwe
This looks similar to the following kernel thread
https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/
Although I don't yet have access to the KVM hypervisor host, I'd like
to know if there is a possible workaround by fixing KVM/QEMU
configuration possibly enabling XSAVEC in addition to XSAVES feature
in the KVM guest, for upgrading KVM/QEMU version.
Full diagnostics performed so far at https://github.com/orange-
cloudfoundry/paas-templates/issues/1960#issuecomment-1534484042
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-20-generic 6.2.0-20.20
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 10 09:35 seq
crw-rw 1 root audio 116, 33 May 10 09:35 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Wed May 10 12:31:18 2023
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci: Error: [Errno 2] No such file or directory: 'lspci'
Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
MachineType: OpenStack Foundation OpenStack Nova
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic
root=UUID=03a4e7a1-715a-4ceb-8fa6-d86a817a7092 ro vconsole.keymap=us
net.ifnames=0 biosdevname=0 crashkernel=auto selinux=0 plymouth.enable=0
console=ttyS0,115200n8 earlyprintk=ttyS0 rootdelay=300 ipv6.disable=1 audit=1
cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=false quiet
splash vt.handoff=7
Related
[Kernel-packages] [Bug 2016269] Re: conntrack mark is not advertised via netlink
** Description changed:
+ SRU justification sent to ML:
+
+ [Impact]
+ There was a commit 95fcb42e5f20
+ ("netfilter: ctnetlink: fix compilation warning after data race fixes in ct
mark")
+ that introduces a regression where the "mark" variable is no longer
+ dumped in netlink netfilter conntrack messages, which userspace tools use
+ to mark and track connections.
+
+ [Fix]
+ Introduce the upstream fix 9f7dd42f0db1
+ ("netfilter: ctnetlink: revert to dumping mark regardless of event type")
+ that always dumps the 'mark' variable for conntrack entries.
+ This fix has also landed in 5.15 upstream stable.
+
+ [Test]
+ Run 'conntrack -E' and check the output of connection entries.
+
+ The 'mark' variable should now be present in connection entries after
+ the fix.
+
+ before fix:
+ > tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
+ after fix:
+ > tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1
+
+ [Where problems could occur]
+ The fixes are pretty straight forward so regression potential should be
+ minimal.
+
+
+
+
+
[Impact]
The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix
compilation warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter:
ctnetlink: revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backported in v5.15.103:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c
[Test Case]
Run 'conntrack -E' and check the output.
Before the problematic commit:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED]
mark=0 use=1
'mark=' is seen on connrtack event
after:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
=> 'mark=' is not seen.
[Regression Potential]
The patch is quite simple. It has been backported in the official 5.15
stable. The risk of regression should be contained.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016269
Title:
conntrack mark is not advertised via netlink
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
New
Status in linux source package in Kinetic:
New
Bug description:
SRU justification sent to ML:
[Impact]
There was a commit 95fcb42e5f20
("netfilter: ctnetlink: fix compilation warning after data race fixes in ct
mark")
that introduces a regression where the "mark" variable is no longer
dumped in netlink netfilter conntrack messages, which userspace tools use
to mark and track connections.
[Fix]
Introduce the upstream fix 9f7dd42f0db1
("netfilter: ctnetlink: revert to dumping mark regardless of event type")
that always dumps the 'mark' variable for conntrack entries.
This fix has also landed in 5.15 upstream stable.
[Test]
Run 'conntrack -E' and check the output of connection entries.
The 'mark' variable should now be present in connection entries after
the fix.
before fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
after fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1
[Where problems could occur]
The fixes are pretty straight forward so regression potential should be
minimal.
[Impact]
The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix
compilation warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter:
ctnetlink: revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backp
[Kernel-packages] [Bug 2019108] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2019108/+attachment/5672184/+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/2019108 Title: XSAVE consistency problem preventing avx on KVM guests Status in linux package in Ubuntu: Confirmed Bug description: On an openstack KVM guest VM the following kernel message is displayed: "XSAVE consistency problem: size 2560 != kernel_size 0" (see further traces collected through "ubuntu-bug linux" command) As a result, the avx feature isn't enabled in the kernel, failing some programs that require it (e.g mongodb requires avx instruction set). This problem reproduces on 23.04 Lunar kernel (6.2.0-20), 22.04 Jammy HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). I'm suspecting a kernel regression since v>5.15 that would be more strict with possibly QEMU emulated XSAVE CPUID features. Related yet unanswered support question: https://askubuntu.com/questions/1467238/xsave-consistency-problem- preventing-avx-on-kvm-guests-running-jammy-hwe This looks similar to the following kernel thread https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/ Although I don't yet have access to the KVM hypervisor host, I'd like to know if there is a possible workaround by fixing KVM/QEMU configuration possibly enabling XSAVEC in addition to XSAVES feature in the KVM guest, for upgrading KVM/QEMU version. Full diagnostics performed so far at https://github.com/orange- cloudfoundry/paas-templates/issues/1960#issuecomment-1534484042 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 10 12:31:18 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=03a4e7a1-715a-4ceb-8fa6-d86a817a7092 ro vconsole.keymap=us net.ifnames=0 biosdevname=0 crashkernel=auto selinux=0 plymouth.enable=0 console=ttyS0,115200n8 earlyprintk=ttyS0 rootdelay=300 ipv6.disable=1 audit=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=false quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1:bd04/01/2014:br0.0:svnOpenStackFoundation:pnOpenStackNova:pvr13.2.1-20220808115737_bd245dd:cvnQEMU:ct1:cvrpc-i440fx-2.8:sku: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 13.2.1-20220808115737_bd245dd dmi.sys.vendor: OpenStack Foundation --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No
[Kernel-packages] [Bug 2019108] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2019108/+attachment/5672185/+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/2019108 Title: XSAVE consistency problem preventing avx on KVM guests Status in linux package in Ubuntu: Confirmed Bug description: On an openstack KVM guest VM the following kernel message is displayed: "XSAVE consistency problem: size 2560 != kernel_size 0" (see further traces collected through "ubuntu-bug linux" command) As a result, the avx feature isn't enabled in the kernel, failing some programs that require it (e.g mongodb requires avx instruction set). This problem reproduces on 23.04 Lunar kernel (6.2.0-20), 22.04 Jammy HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). I'm suspecting a kernel regression since v>5.15 that would be more strict with possibly QEMU emulated XSAVE CPUID features. Related yet unanswered support question: https://askubuntu.com/questions/1467238/xsave-consistency-problem- preventing-avx-on-kvm-guests-running-jammy-hwe This looks similar to the following kernel thread https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/ Although I don't yet have access to the KVM hypervisor host, I'd like to know if there is a possible workaround by fixing KVM/QEMU configuration possibly enabling XSAVEC in addition to XSAVES feature in the KVM guest, for upgrading KVM/QEMU version. Full diagnostics performed so far at https://github.com/orange- cloudfoundry/paas-templates/issues/1960#issuecomment-1534484042 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 10 12:31:18 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=03a4e7a1-715a-4ceb-8fa6-d86a817a7092 ro vconsole.keymap=us net.ifnames=0 biosdevname=0 crashkernel=auto selinux=0 plymouth.enable=0 console=ttyS0,115200n8 earlyprintk=ttyS0 rootdelay=300 ipv6.disable=1 audit=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=false quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1:bd04/01/2014:br0.0:svnOpenStackFoundation:pnOpenStackNova:pvr13.2.1-20220808115737_bd245dd:cvnQEMU:ct1:cvrpc-i440fx-2.8:sku: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 13.2.1-20220808115737_bd245dd dmi.sys.vendor: OpenStack Foundation --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 2019108] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2019108/+attachment/5672190/+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/2019108 Title: XSAVE consistency problem preventing avx on KVM guests Status in linux package in Ubuntu: Confirmed Bug description: On an openstack KVM guest VM the following kernel message is displayed: "XSAVE consistency problem: size 2560 != kernel_size 0" (see further traces collected through "ubuntu-bug linux" command) As a result, the avx feature isn't enabled in the kernel, failing some programs that require it (e.g mongodb requires avx instruction set). This problem reproduces on 23.04 Lunar kernel (6.2.0-20), 22.04 Jammy HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). I'm suspecting a kernel regression since v>5.15 that would be more strict with possibly QEMU emulated XSAVE CPUID features. Related yet unanswered support question: https://askubuntu.com/questions/1467238/xsave-consistency-problem- preventing-avx-on-kvm-guests-running-jammy-hwe This looks similar to the following kernel thread https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/ Although I don't yet have access to the KVM hypervisor host, I'd like to know if there is a possible workaround by fixing KVM/QEMU configuration possibly enabling XSAVEC in addition to XSAVES feature in the KVM guest, for upgrading KVM/QEMU version. Full diagnostics performed so far at https://github.com/orange- cloudfoundry/paas-templates/issues/1960#issuecomment-1534484042 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 10 12:31:18 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=03a4e7a1-715a-4ceb-8fa6-d86a817a7092 ro vconsole.keymap=us net.ifnames=0 biosdevname=0 crashkernel=auto selinux=0 plymouth.enable=0 console=ttyS0,115200n8 earlyprintk=ttyS0 rootdelay=300 ipv6.disable=1 audit=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=false quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1:bd04/01/2014:br0.0:svnOpenStackFoundation:pnOpenStackNova:pvr13.2.1-20220808115737_bd245dd:cvnQEMU:ct1:cvrpc-i440fx-2.8:sku: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 13.2.1-20220808115737_bd245dd dmi.sys.vendor: OpenStack Foundation --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or direct
[Kernel-packages] [Bug 2019108] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2019108/+attachment/5672187/+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/2019108 Title: XSAVE consistency problem preventing avx on KVM guests Status in linux package in Ubuntu: Confirmed Bug description: On an openstack KVM guest VM the following kernel message is displayed: "XSAVE consistency problem: size 2560 != kernel_size 0" (see further traces collected through "ubuntu-bug linux" command) As a result, the avx feature isn't enabled in the kernel, failing some programs that require it (e.g mongodb requires avx instruction set). This problem reproduces on 23.04 Lunar kernel (6.2.0-20), 22.04 Jammy HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). I'm suspecting a kernel regression since v>5.15 that would be more strict with possibly QEMU emulated XSAVE CPUID features. Related yet unanswered support question: https://askubuntu.com/questions/1467238/xsave-consistency-problem- preventing-avx-on-kvm-guests-running-jammy-hwe This looks similar to the following kernel thread https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/ Although I don't yet have access to the KVM hypervisor host, I'd like to know if there is a possible workaround by fixing KVM/QEMU configuration possibly enabling XSAVEC in addition to XSAVES feature in the KVM guest, for upgrading KVM/QEMU version. Full diagnostics performed so far at https://github.com/orange- cloudfoundry/paas-templates/issues/1960#issuecomment-1534484042 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 10 12:31:18 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=03a4e7a1-715a-4ceb-8fa6-d86a817a7092 ro vconsole.keymap=us net.ifnames=0 biosdevname=0 crashkernel=auto selinux=0 plymouth.enable=0 console=ttyS0,115200n8 earlyprintk=ttyS0 rootdelay=300 ipv6.disable=1 audit=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=false quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1:bd04/01/2014:br0.0:svnOpenStackFoundation:pnOpenStackNova:pvr13.2.1-20220808115737_bd245dd:cvnQEMU:ct1:cvrpc-i440fx-2.8:sku: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 13.2.1-20220808115737_bd245dd dmi.sys.vendor: OpenStack Foundation --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 2019108] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2019108/+attachment/5672186/+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/2019108 Title: XSAVE consistency problem preventing avx on KVM guests Status in linux package in Ubuntu: Confirmed Bug description: On an openstack KVM guest VM the following kernel message is displayed: "XSAVE consistency problem: size 2560 != kernel_size 0" (see further traces collected through "ubuntu-bug linux" command) As a result, the avx feature isn't enabled in the kernel, failing some programs that require it (e.g mongodb requires avx instruction set). This problem reproduces on 23.04 Lunar kernel (6.2.0-20), 22.04 Jammy HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). I'm suspecting a kernel regression since v>5.15 that would be more strict with possibly QEMU emulated XSAVE CPUID features. Related yet unanswered support question: https://askubuntu.com/questions/1467238/xsave-consistency-problem- preventing-avx-on-kvm-guests-running-jammy-hwe This looks similar to the following kernel thread https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/ Although I don't yet have access to the KVM hypervisor host, I'd like to know if there is a possible workaround by fixing KVM/QEMU configuration possibly enabling XSAVEC in addition to XSAVES feature in the KVM guest, for upgrading KVM/QEMU version. Full diagnostics performed so far at https://github.com/orange- cloudfoundry/paas-templates/issues/1960#issuecomment-1534484042 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 10 12:31:18 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=03a4e7a1-715a-4ceb-8fa6-d86a817a7092 ro vconsole.keymap=us net.ifnames=0 biosdevname=0 crashkernel=auto selinux=0 plymouth.enable=0 console=ttyS0,115200n8 earlyprintk=ttyS0 rootdelay=300 ipv6.disable=1 audit=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=false quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1:bd04/01/2014:br0.0:svnOpenStackFoundation:pnOpenStackNova:pvr13.2.1-20220808115737_bd245dd:cvnQEMU:ct1:cvrpc-i440fx-2.8:sku: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 13.2.1-20220808115737_bd245dd dmi.sys.vendor: OpenStack Foundation --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such fi
[Kernel-packages] [Bug 2019108] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2019108/+attachment/5672189/+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/2019108 Title: XSAVE consistency problem preventing avx on KVM guests Status in linux package in Ubuntu: Confirmed Bug description: On an openstack KVM guest VM the following kernel message is displayed: "XSAVE consistency problem: size 2560 != kernel_size 0" (see further traces collected through "ubuntu-bug linux" command) As a result, the avx feature isn't enabled in the kernel, failing some programs that require it (e.g mongodb requires avx instruction set). This problem reproduces on 23.04 Lunar kernel (6.2.0-20), 22.04 Jammy HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). I'm suspecting a kernel regression since v>5.15 that would be more strict with possibly QEMU emulated XSAVE CPUID features. Related yet unanswered support question: https://askubuntu.com/questions/1467238/xsave-consistency-problem- preventing-avx-on-kvm-guests-running-jammy-hwe This looks similar to the following kernel thread https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/ Although I don't yet have access to the KVM hypervisor host, I'd like to know if there is a possible workaround by fixing KVM/QEMU configuration possibly enabling XSAVEC in addition to XSAVES feature in the KVM guest, for upgrading KVM/QEMU version. Full diagnostics performed so far at https://github.com/orange- cloudfoundry/paas-templates/issues/1960#issuecomment-1534484042 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 10 12:31:18 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=03a4e7a1-715a-4ceb-8fa6-d86a817a7092 ro vconsole.keymap=us net.ifnames=0 biosdevname=0 crashkernel=auto selinux=0 plymouth.enable=0 console=ttyS0,115200n8 earlyprintk=ttyS0 rootdelay=300 ipv6.disable=1 audit=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=false quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1:bd04/01/2014:br0.0:svnOpenStackFoundation:pnOpenStackNova:pvr13.2.1-20220808115737_bd245dd:cvnQEMU:ct1:cvrpc-i440fx-2.8:sku: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 13.2.1-20220808115737_bd245dd dmi.sys.vendor: OpenStack Foundation --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or di
[Kernel-packages] [Bug 2019108] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2019108/+attachment/5672188/+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/2019108 Title: XSAVE consistency problem preventing avx on KVM guests Status in linux package in Ubuntu: Confirmed Bug description: On an openstack KVM guest VM the following kernel message is displayed: "XSAVE consistency problem: size 2560 != kernel_size 0" (see further traces collected through "ubuntu-bug linux" command) As a result, the avx feature isn't enabled in the kernel, failing some programs that require it (e.g mongodb requires avx instruction set). This problem reproduces on 23.04 Lunar kernel (6.2.0-20), 22.04 Jammy HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). I'm suspecting a kernel regression since v>5.15 that would be more strict with possibly QEMU emulated XSAVE CPUID features. Related yet unanswered support question: https://askubuntu.com/questions/1467238/xsave-consistency-problem- preventing-avx-on-kvm-guests-running-jammy-hwe This looks similar to the following kernel thread https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/ Although I don't yet have access to the KVM hypervisor host, I'd like to know if there is a possible workaround by fixing KVM/QEMU configuration possibly enabling XSAVEC in addition to XSAVES feature in the KVM guest, for upgrading KVM/QEMU version. Full diagnostics performed so far at https://github.com/orange- cloudfoundry/paas-templates/issues/1960#issuecomment-1534484042 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 10 12:31:18 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=03a4e7a1-715a-4ceb-8fa6-d86a817a7092 ro vconsole.keymap=us net.ifnames=0 biosdevname=0 crashkernel=auto selinux=0 plymouth.enable=0 console=ttyS0,115200n8 earlyprintk=ttyS0 rootdelay=300 ipv6.disable=1 audit=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=false quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1:bd04/01/2014:br0.0:svnOpenStackFoundation:pnOpenStackNova:pvr13.2.1-20220808115737_bd245dd:cvnQEMU:ct1:cvrpc-i440fx-2.8:sku: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 13.2.1-20220808115737_bd245dd dmi.sys.vendor: OpenStack Foundation --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 2019108] Re: XSAVE consistency problem preventing avx on KVM guests
apport information ** Description changed: On an openstack KVM guest VM the following kernel message is displayed: "XSAVE consistency problem: size 2560 != kernel_size 0" (see further traces collected through "ubuntu-bug linux" command) As a result, the avx feature isn't enabled in the kernel, failing some programs that require it (e.g mongodb requires avx instruction set). - This problem reproduces on 23.04 Lua kernel (6.2.0-20), 22.04 Jammy HWE - kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). + This problem reproduces on 23.04 Lunar kernel (6.2.0-20), 22.04 Jammy + HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). I'm suspecting a kernel regression since v>5.15 that would be more strict with possibly QEMU emulated XSAVE CPUID features. Related yet unanswered support question: https://askubuntu.com/questions/1467238/xsave-consistency-problem- preventing-avx-on-kvm-guests-running-jammy-hwe This looks similar to the following kernel thread https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/ Although I don't yet have access to the KVM hypervisor host, I'd like to know if there is a possible workaround by fixing KVM/QEMU configuration possibly enabling XSAVEC in addition to XSAVES feature in the KVM guest, for upgrading KVM/QEMU version. Full diagnostics performed so far at https://github.com/orange- cloudfoundry/paas-templates/issues/1960#issuecomment-1534484042 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 May 10 09:35 seq - crw-rw 1 root audio 116, 33 May 10 09:35 timer + total 0 + crw-rw 1 root audio 116, 1 May 10 09:35 seq + crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 10 12:31:18 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: - + ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=03a4e7a1-715a-4ceb-8fa6-d86a817a7092 ro vconsole.keymap=us net.ifnames=0 biosdevname=0 crashkernel=auto selinux=0 plymouth.enable=0 console=ttyS0,115200n8 earlyprintk=ttyS0 rootdelay=300 ipv6.disable=1 audit=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=false quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-6.2.0-20-generic N/A - linux-backports-modules-6.2.0-20-generic N/A - linux-firmware20230323.gitbcdcfbcf-0ubuntu1 + linux-restricted-modules-6.2.0-20-generic N/A + linux-backports-modules-6.2.0-20-generic N/A + linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1:bd04/01/2014:br0.0:svnOpenStackFoundation:pnOpenStackNova:pvr13.2.1-20220808115737_bd245dd:cvnQEMU:ct1:cvrpc-i440fx-2.8:sku: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 13.2.1-20220808115737_bd245dd dmi.sys.vendor: OpenStack Foundation ** Tags added: apport-collected ** Description changed: On an openstack KVM guest VM the following kernel message is displayed: "XSAVE consistency problem: size 2560 != kernel_size 0" (see further traces collected through "ubuntu-bug linux" command) As a result, the avx feature isn't enabled in the kernel, failing some programs that require it (e.g mongodb requires avx instruction set). This problem reproduces on 23.04 Lunar kernel (6.2.0-20), 22.04 Jammy HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). I'm suspecting a kernel regression since v>5.15 that would be more strict with possibly QEMU emulated X
[Kernel-packages] [Bug 2019108] Re: XSAVE consistency problem preventing avx on KVM guests
> 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' I'm running a vm image optimized for use within cloudfoundry (see https://bosh.io/stemcells/#ubuntu-jammy) for Jammy 22.04 and then upgraded to Lunar 23.04. I'm suspecting this breaks some reports, althrough I have run again the `apport-collect 2019108` command ** Changed in: linux (Ubuntu) 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/2019108 Title: XSAVE consistency problem preventing avx on KVM guests Status in linux package in Ubuntu: Confirmed Bug description: On an openstack KVM guest VM the following kernel message is displayed: "XSAVE consistency problem: size 2560 != kernel_size 0" (see further traces collected through "ubuntu-bug linux" command) As a result, the avx feature isn't enabled in the kernel, failing some programs that require it (e.g mongodb requires avx instruction set). This problem reproduces on 23.04 Lunar kernel (6.2.0-20), 22.04 Jammy HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). I'm suspecting a kernel regression since v>5.15 that would be more strict with possibly QEMU emulated XSAVE CPUID features. Related yet unanswered support question: https://askubuntu.com/questions/1467238/xsave-consistency-problem- preventing-avx-on-kvm-guests-running-jammy-hwe This looks similar to the following kernel thread https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/ Although I don't yet have access to the KVM hypervisor host, I'd like to know if there is a possible workaround by fixing KVM/QEMU configuration possibly enabling XSAVEC in addition to XSAVES feature in the KVM guest, for upgrading KVM/QEMU version. Full diagnostics performed so far at https://github.com/orange- cloudfoundry/paas-templates/issues/1960#issuecomment-1534484042 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 10 12:31:18 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=03a4e7a1-715a-4ceb-8fa6-d86a817a7092 ro vconsole.keymap=us net.ifnames=0 biosdevname=0 crashkernel=auto selinux=0 plymouth.enable=0 console=ttyS0,115200n8 earlyprintk=ttyS0 rootdelay=300 ipv6.disable=1 audit=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=false quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1:bd04/01/2014:br0.0:svnOpenStackFoundation:pnOpenStackNova:pvr13.2.1-20220808115737_bd245dd:cvnQEMU:ct1:cvrpc-i440fx-2.8:sku: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 13.2.1-20220808115737_bd245dd dmi.sys.vendor: OpenStack Foundation --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'areco
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@blindbO hello! I meet the same problem , my computer is same with you , and also is ubuntu 23.04. but when I compile the https://github.com/Kvalme/uvc , there is an error occur. "fatal error: linux/usb/uvc.h: no such file or directory" and i also put the "uvc" directory into the linux-6.2.0/media/usb/. and the compile , but still is the same error. -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dm
[Kernel-packages] [Bug 2019108] Re: XSAVE consistency problem preventing avx on KVM guests
** Description changed: On an openstack KVM guest VM the following kernel message is displayed: "XSAVE consistency problem: size 2560 != kernel_size 0" (see further traces collected through "ubuntu-bug linux" command) As a result, the avx feature isn't enabled in the kernel, failing some programs that require it (e.g mongodb requires avx instruction set). This problem reproduces on 23.04 Lunar kernel (6.2.0-20), 22.04 Jammy HWE kernel (5.19.0-35) but not on Jammy GA kernel (5.15.0-71.78). I'm suspecting a kernel regression since v>5.15 that would be more strict with possibly QEMU emulated XSAVE CPUID features. Related yet unanswered support question: https://askubuntu.com/questions/1467238/xsave-consistency-problem- preventing-avx-on-kvm-guests-running-jammy-hwe This looks similar to the following kernel thread https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/ Although I don't yet have access to the KVM hypervisor host, I'd like to know if there is a possible workaround by fixing KVM/QEMU configuration - possibly enabling XSAVEC in addition to XSAVES feature in the KVM guest, - for upgrading KVM/QEMU version. + or by upgrading KVM/QEMU version. Full diagnostics performed so far at https://github.com/orange- cloudfoundry/paas-templates/issues/1960#issuecomment-1534484042 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 09:35 seq crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 10 12:31:18 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=03a4e7a1-715a-4ceb-8fa6-d86a817a7092 ro vconsole.keymap=us net.ifnames=0 biosdevname=0 crashkernel=auto selinux=0 plymouth.enable=0 console=ttyS0,115200n8 earlyprintk=ttyS0 rootdelay=300 ipv6.disable=1 audit=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=false quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.10.2-0-g5f4c7b1-20181220_00-szxrtosci1:bd04/01/2014:br0.0:svnOpenStackFoundation:pnOpenStackNova:pvr13.2.1-20220808115737_bd245dd:cvnQEMU:ct1:cvrpc-i440fx-2.8:sku: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 13.2.1-20220808115737_bd245dd dmi.sys.vendor: OpenStack Foundation - --- + --- ProblemType: Bug AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 May 10 09:35 seq - crw-rw 1 root audio 116, 33 May 10 09:35 timer + total 0 + crw-rw 1 root audio 116, 1 May 10 09:35 seq + crw-rw 1 root audio 116, 33 May 10 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: OpenStack Foundatio
[Kernel-packages] [Bug 2019040] Re: linux-kvm: please enable dm-verity kconfigs
Also, please enable CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING on the cloud kernels - especially I am interested in the Azure one. Same reason as above - the other options are already enabled there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2019040 Title: linux-kvm: please enable dm-verity kconfigs Status in linux-meta-kvm package in Ubuntu: New Bug description: The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_IMA_ARCH_POLICY (The latter is needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-kvm/+bug/2019040/+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 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Fix Released Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
[Kernel-packages] [Bug 2009118] Re: Fix mediatek wifi driver crash when loading wrong SAR table
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009118 Title: Fix mediatek wifi driver crash when loading wrong SAR table Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009118/+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 2009024] Re: Fail to output sound to external monitor which connects via docking station
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009024 Title: Fail to output sound to external monitor which connects via docking station Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] No sound output from the external monitor which connect via some docking station. It only happens when user boot the system with docking station connected. Re-plug the docking station can fix this issue. Or plug the docking station later won't trigger this problem. [Fix] Turn on the CONFIG_SND_HDA_INTEL_HDMI_SILENT in kernel config. It will start sending an "audio keepalive" to the monitor as soon as it is connected. [Test] Connect the external monitor to the Atomic Type-C Dock (HD22Q) and boot the system with the dock connected. Play sound via HDMI/DP port and check if there's any audio output from the external monitor. [Where problems could occur] It sends the "audio keepalive"(silent stream) to the monitor when connected. Doesn't affect original workflow of the audio system. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009024/+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 2008971] Re: Do not sort the task scan result from /proc when synthesizing perf events
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp
verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2008971
Title:
Do not sort the task scan result from /proc when synthesizing perf
events
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
The perf tool use scandir() to iterate threads and sort in alphabetical order
when synthesizing PERF_RECORD_ events.
If the process ID is and it has one thread (tid = 1), the thread
will be processed before the process.
It results in PERF_RECORD_FORK events that come before PERF_RECORD_MMAP2
events.
The callstack will have missing symbols for threads where `PERF_RECORD_FORK`
events are processed before the `PERF_RECORD_MMAP2` event for the corresponding
process.
[Fix]
Do not use alphasort when calling scandir()
363afa3aef24f5e08df6a539f5dc3aae4cddcc1a (perf synthetic-events: Don't
sort the task scan result from /proc)
[Test Plan]
function update_last_pid()
local file = io.open("/proc/sys/kernel/ns_last_pid", "w")
file:write(9997)
end
update_last_pid()
os.execute("~/reproducer")
#include
#include
#include
constexpr int kThreadNum = 10;
void thread_job() { sleep(30); }
int main(void) {
std::thread threads[kThreadNum];
std::cout << "Parent process with pid " << getpid() << std::endl;
for (int i = 0; i < kThreadNum; ++i) {
threads[i] = std::thread(thread_job);
}
for (int i = 0; i < kThreadNum; ++i) {
threads[i].join();
}
std::cout << "All threads have finished" << std::endl;
return 0;
}
The flow is to set /proc/sys/kernel/ns_last_pid first, which represents the
last pid allocated in the current pid namespace.
The script (test.lua) sets ns_last_pid to 9997 and executes the reproducer
(reproducer.cpp).
After the reproducer creates ten threads, we execute the perf command as
follows: perf record -F 49 -e cpu-clock -a -g sleep 20.
Here is the result of command: perf report -f --tasks --mmaps -D | egrep -i
'perf_record_fork|perf_record_mmap' | grep
Before applying the patch, the output of the perf command was as follows:
0 0 0x34910 [0x40]: PERF_RECORD_FORK(:1):(:)
0 0 0x34990 [0x40]: PERF_RECORD_FORK(:10001):(:)
0 0 0x34a10 [0x40]: PERF_RECORD_FORK(:10002):(:)
0 0 0x34a90 [0x40]: PERF_RECORD_FORK(:10003):(:)
0 0 0x34b10 [0x40]: PERF_RECORD_FORK(:10004):(:)
0 0 0x34b90 [0x40]: PERF_RECORD_FORK(:10005):(:)
0 0 0x34c10 [0x40]: PERF_RECORD_FORK(:10006):(:)
0 0 0x34c90 [0x40]: PERF_RECORD_FORK(:10007):(:)
0 0 0x34d10 [0x40]: PERF_RECORD_FORK(:10008):(:)
0 0 0x34d90 [0x40]: PERF_RECORD_FORK(:10009):(:)
0 0 0x34e10 [0x40]: PERF_RECORD_FORK(:):(9998:9998)
0 0 0x34e90 [0x80]: PERF_RECORD_MMAP2 /: [0x555de0159000(0x1000) @
0x1000 fd:00 2097758 0]: r-xp /root/reproducer
0 0 0x34f10 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd17f8000(0x7c000) @
0xe000 fd:00 1055098 0]: r-xp /usr/lib/x86_64-linux-gnu/libm.so.6
0 0 0x34fa0 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd18f9000(0x195000) @
0x28000 fd:00 1054988 0]: r-xp /usr/lib/x86_64-linux-gnu/libc.so.6
0 0 0x35030 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd1afc000(0x17000) @
0x3000 fd:00 1054745 0]: r-xp /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
0 0 0x350c0 [0x98]: PERF_RECORD_MMAP2 /: [0x7f9cd1bb3000(0x11) @
0x9a000 fd:00 1068050 0]: r-xp /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30
0 0 0x35158 [0x98]: PERF_RECORD_MMAP2 /: [0x7f9cd1d4e000(0x2a000) @
0x2000 fd:00 1054949 0]: r-xp /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
0 0 0x351f0 [0x70]: PERF_RECORD_MMAP2 /: [0x7ffc983bb000(0x2000) @ 0
00:00 0 0]: r-xp [vdso]
0 0 0x35260 [0x78]: PERF_RECORD_MMAP2 /: [0xff60(0x1000)
@ 0 00:00 0 0]: --xp [vsyscall]
After applying the patch, the output of the perf command is as follows:
0 0 0x30c28 [0x40]: PERF_RECORD_FORK(:):(9998:9998)
0 0 0x30ca8 [0x80]: PERF_RECORD_MMA
[Kernel-packages] [Bug 2008519] Re: cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- 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/2008519 Title: cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [SRU Justification] == Impact == See original description. The goal is to adjust the behavior of the balanced governor for certain Xeon CPUs (those are CPUs rather seen in servers so there should be no impact on laptop users). While the initial request was Jammy/5.15 only we should do this to Kinetic and Lunar as well so the experience is the same regardless of release. == Fix == This picks one change from v6.3-rc1 which tweaks the intel_idle driver for a specific CPU model. For Jammy/5.15 this requires one additional change which introduces the EPP tweak for Alderlake. == Test case == == Regression Potential == The change modifies how quickly CPUs scale up (and probably down) depending on workload. Power usage unlikely is of that much concern in server space. Maybe increased heat would be observed. For Jammy there is the additional risk of havind a different power usage on Alderlake which is a Laptop CPU. However that change is part of v5.17 and thus would already be in effect with current 22.04 HWE. == Original description == [Feature Description] Ubuntu uses powersave governor as the default.While the powersave governor has much lower power, the performance is lower than +25% for several workloads compared to performance governor. Report is published: www.Phoronix.com showing difference of 37% The goal here is to keep mean performance delta of powersave governor from performance governor around 10% to 12% by running wide variety of server workloads. For some bursty workload, this delta can be still large, as ramp up of frequency will still lag with powersave governor irrespective of EPP setting. The performance governor always requests maximum frequency. Based on experiments, EPP of 0x00, 0x10, 0x20, the performance delta for powersave governor is around 12%. But the EPP 0x20 has 18% lower average power. Also experiments are done by raising intel_pstate sysfs min_perf_pct as high as 50%. This didn't bring in any additional improvements compared to just changing EPP. Target Kernel: 6.3 Target Release: 22.04 (5.15 kernel) [HW/SW Information] Sapphire Rapids [Business Justification] Performance Improvements Upstream: Merged 6.3 Commit ID: 60675225ebeecea248035fd3a0efc82ae9038a98 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2008519/+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 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007798 Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: == SRU Justification == [Impact] Audio playback becomes silent on some Intel SoF systems. [Fix] Revert offending commit. [Test] The speaker can always play sound after the commit gets reverted. [Where problems could occur] Audio on linux 5.15 has been working fine without the patch for a long time, so this only restore it to where it was. == Original Bug Report == [Summary] During the kernel SRU testing on focal-hwe, I found the audio output of some machines are broken. I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and haven't seen this happened. The volume bars in settings react to what sound is played correctly and device is detected as well. [Reproduce steps] 1. install focal 2. enable -proposed 3. run apt dist-upgrade. 4. reboot. 5. press fn keys to volume up then volume down or play a short youtube video. 6. after a while can't hear any sound from the speaker. [Failure rate] 10/10 [Additional info] If I run "sudo alsa force-reload" can make audio work again, but after a while it breaks again. These are machines that impacted by this bug: https://certification.canonical.com/hardware/202007-28045/ https://certification.canonical.com/hardware/201906-27109/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/202007-28047/ https://certification.canonical.com/hardware/202007-28055/ https://certification.canonical.com/hardware/202005-27899/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1303 F pulseaudio CasperMD5CheckResult: skip Date: Sun Feb 19 21:24:59 2023 InstallationDate: Installed on 2020-08-03 (930 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Feb 19 20:53:23 dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.product.sku: 0922 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007798/+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 2006692] Re: net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006692 Title: net:fcnal-test.sh didn't return a non-zero value even with some sub- tests failed Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] The net/fcnal-test.sh on F/J won't return a non-zero value even with some sub test cases failed, here is an example on Jammy: # Tests passed: 857 # Tests failed: 5 ok 1 selftests: net: fcnal-test.sh Therefore it's marked as PASSED on our report and making it difficult to spot these failures: # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL] [Fix] * 0f8a3b48f9 selftests: net/fcnal-test.sh: add exit code This patch can be cherry-picked into Focal and Jammy kernel. We don't have this test in Bionic, and this patch has already landed on Kinetic and OEM-5.17 [Test] Run the patched test, the return value will be 1 whenever the number of failed test cases is not 0. [Where problems could occur] Change limited to testing tools, but we're expected to see new failures in Jammy. With bug 2006391 fixed later on, we will see failures reported in F/K as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006692/+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 2006453] Re: Fix selftests/ftracetests/Meta-selftests
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2006453 Title: Fix selftests/ftracetests/Meta-selftests Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-6.1 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [SRU Justification] == Impact == This subtest checks for bashisms in the test scripts of ftracetests. A recent stable change added such a case. This is harmless but causes the Meta-selftests to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer for test_event_enable" which adds: + if [ "$e" == $val ]; then == Fix == Replace the test with + if [ "$e" = $val ]; then == Testcase == Running the kernel selftests/ftracetest (done in ADT and RT) should no longer show "Meta-selftests" as FAILed. == Regression Potential == This affects only the selftest suite and only ftrace subtests. Any change would only be observable there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006077] Re: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- 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/2006077 Title: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] Some machines which have dynamically loaded SSDT tables, will not be loaded and get the CPPC not worked. [Fix] Fix the regression by some load supports for CPPC from an SSDT dynamically when _OSC reports CPPC v2. And make the "[\_SB.PR00._CPC], AE_NOT_FOUND" gone. [Test] Verified all the OEM dynamic table loaded or the "[\_SB.PR00._CPC], AE_NOT_FOUND" error exist or not on demesg . [Where problems could occur] Low risk, It only helps to CPPC support loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006077/+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 2003267] Re: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp
--
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/2003267
Title:
[EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04
release
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
== SRU Justification ==
Intel has requested the following patches which enable enable Intel_idle for
eagle stream.
Intel has customers that would like to use the intel_idle driver on latest
SPR (Sapphire Rapids).
These patches have all landed upstream, but are not in Jammy.
These patches will enable customers to use Ubuntu 22.04 on new hardware
from Intel.
== Fixes ==
9edf3c0ffef0 ("intel_idle: add SPR support")
da0e58c038e6 ("intel_idle: add 'preferred_cstates' module argument")
3a9cf77b60dc ("intel_idle: add core C6 optimization for SPR")
03eb65224e57 ("cpuidle: intel_idle: Drop redundant backslash at line end")
39c184a6a9a7 ("intel_idle: Fix the 'preferred_cstates' module parameter")
7eac3bd38d18 ("intel_idle: Fix SPR C6 optimization")
1548fac47a11 ("intel_idle: make SPR C1 and C1E be independent")
== Regression Potential ==
Medium. These patches are specific to enable intel_idle support for Sapphire
Rapids. Changes
are specific to Intel and tested by Intel.
== Test Case ==
A test kernel was built with these patches and tested by Intel.
Intel tested on SPR-SP machine and see the correct 190us and 600us residency
for the C6 state.
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2003267/+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 2003816] Re: Regression in ext4 during online resize
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2003816 Title: Regression in ext4 during online resize Status in cloud-init package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in cloud-init source package in Jammy: Invalid Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in cloud-init source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux-azure source package in Kinetic: Fix Released Status in linux-gcp source package in Kinetic: Fix Released Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+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 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2003161 Title: Fix speaker mute hotkey doesn't work on Dell G16 series Status in HWE Next: New Status in HWE Next lunar series: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Speaker mute and Mic mute hotkey no function on the G16. [Fix] speaker mute event is sent by EC then dell-wmi can't recognize it. Add a new keymap for KEY_MUTE. Send for OEM kernels first then will SRU for generic kernel once the patch is merged. [Test Case] 1. boot-up with the kernel applied the fix. 2. Play video/audio. 3. Press the speak-mute hotkey 4. can't hear any sounds. [Where problems could occur] Low, only add a keymap the affect would be very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2003161/+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 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- 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/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed 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] Xen guests will not have network access. This fixes a regression due to the fix for CVE-2022-3643. [Testing] This has only been build-tested. [Potential regression] Xen guests might not have network access. -- With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+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 2003053] Re: NFS: client permission error after adding user to permissible group
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- 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/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: Fix Committed 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 Status in linux source package in Lunar: Fix Committed Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+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 2000299] Re: Fix W6400 hang after resume of S3 stress
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- 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/2000299 Title: Fix W6400 hang after resume of S3 stress Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: [Impact] amdgpu hang when stress S3 on AMD W6400 GPU. [Fix] Add a WA to manually adjust strobe calculation using FCLK restrict. [Test] Suspend AMD W6400 for 40 times, it works fine. [Where problems could occur] Low risk, upstream fix. It may cause AMD GPU hang. The patch is in 5.16, only Jammy kernel needs it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000299/+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 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1998905 Title: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic) Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] On the development, we found sometimes there is no audio output device when headphone is connected to the rear audio jack. [Fix] Cirrus Logic provides a patch to fix this https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ The patch is included in v6.2-rc1 9fb9fa18fb50 ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock. [Test] Verified by our QA and ODM. [Where problems could occur] It extends the delay time, should be no harm for existing platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998905/+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 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1996048 Title: Screen freeze after resuming from suspend (nvme0: I/O timeout) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ Included in v6.2-rc1 d899aa668498 PCI: vmd: Disable MSI remapping after suspend [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996048/+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 1993561] Re: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1993561 Title: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The Screen is shaking connected monitor to Onboard HDMI port. [Fix] The interlaced mode is not supported for Intel Gen 12 onwards. Disable interlaced mode for DP&HDMI on Display >= 12. Due to schedule, SRU for OEM kernels first. After these patches are merged to mainline/drmtip kernel, will SRU for generic kernels. [Test Case] 1.Connected two external Monitor to the onboard HDMI/DP port . 2.Boot OS. 2.set mirror mode. (onboard HDMI / onboard DP) 3.check if screen shakes. [Where problems could occur] Low, Remove interlace support for Display >= 12 so it wouldn't cause a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993561/+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 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987430 Title: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: Since updating to kernel 5.15.0-46-generic (package version 5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel memory; our first server with 8 GB of RAM just fatally OOMed, causing us to detect this. Inspection of OOM reports, /proc/meminfo, and /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k slabs: Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab info: Aug 23 12:51:11 cluster kernel: [361299.864757] Name Used Total [...] Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k 6676584KB6676596KB Most of our machines appear to be leaking slab memory at a rate of around 20 to 40 Mbytes/hour, with some machines leaking much faster; the champions are leaking kernel memory at 145 Mbytes/hour and 237 Mbytes/hour. We aren't running any proprietary kernel modules and our only unusual kernel configuration is that we've disabled AppArmor with 'apparmor=0' on the kernel command line. /proc/version_signature: Ubuntu 5.15.0-46.49-generic 5.15.39 Full kernel command line from the Dell R240 system that fatally OOMd: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 console=tty0 apparmor=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Released Status in zfs-linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Fix Released Status in zfs-linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Fix Released Status in zfs-linux source package in Lunar: Confirmed Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. 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: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+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 1971151] Re: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971151 Title: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0 7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough 986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs 43ca11005098 scsi: mpi3mr: Add support for PEL commands 506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header f5e6d5a34376 scsi: mpi3mr: Add support for driver commands 4268fa751365 scsi: mpi3mr: Add bsg device support 1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc 4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings 9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails a25eafd13e5f scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() 256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR 2dd8389f96d6 scsi: mpi3mr: Hidden drives not removed during soft reset 1aa529d40025 scsi: mpi3mr: Increase I/O timeout value to 60s [Test Plan] 1. Install and boot kernel 2. Run basic I/O tests [Where problems could occur] Moderate to low regression risk for the kernel as most changes are in the driver [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951447] Re: ubuntu_kernel_selftests: net:udpgso_bench.sh failed
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951447 Title: ubuntu_kernel_selftests: net:udpgso_bench.sh failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress 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: 04:41:59 DEBUG| [stdout] # selftests: net: udpgso_bench.sh 04:41:59 DEBUG| [stdout] # ipv4 04:41:59 DEBUG| [stdout] # tcp 04:42:00 DEBUG| [stdout] # tcp tx: 2736 MB/s46415 calls/s 46415 msg/s 04:42:00 DEBUG| [stdout] # tcp rx: 2737 MB/s46161 calls/s 04:42:01 DEBUG| [stdout] # tcp tx: 2735 MB/s46392 calls/s 46392 msg/s 04:42:01 DEBUG| [stdout] # tcp rx: 2739 MB/s46226 calls/s 04:42:02 DEBUG| [stdout] # tcp tx: 2717 MB/s46092 calls/s 46092 msg/s 04:42:02 DEBUG| [stdout] # tcp zerocopy 04:42:02 DEBUG| [stdout] # ./udpgso_bench_tx: connect: Connection refused 04:42:54 DEBUG| [stdout] # udpgso_bench.sh: PASS=17 SKIP=0 FAIL=1 04:42:54 DEBUG| [stdout] # udpgso_bench.sh: ^[[0;31mFAIL^[[0m 04:42:54 DEBUG| [stdout] not ok 1 selftests: net: udpgso_bench.sh # exit=1 04:42:54 DEBUG| [stdout] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 04:42:54 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py", line 252, in run_once raise error.TestError(test_name + ' failed.') TestError: net:udpgso_bench.sh failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1951447/+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 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- 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/1814234 Title: rtcpie in timers from ubuntu_kernel_selftests randomly failing Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed 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 Status in linux source package in Lunar: Fix Released Bug description: Node: Standard_D11_v2 Kernel: 4.18.0-1008.8~18.04.1 selftests: timers: rtcpie Periodic IRQ rate is 1024Hz. Counting 20 interrupts at: 2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 32Hz:1 2 3 4 5 6 7 PIE delta error: 0.034667 should be close to 0.031250 181. 01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: timers: rtcpie [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814234/+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 1642368] Re: linux: Staging modules should be unsigned
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642368 Title: linux: Staging modules should be unsigned Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Released Status in linux source package in Impish: Won't Fix Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: Modules under the drivers/staging hierarchy get little attention when it comes to vulnerabilities. It is possible that memory mapping tricks that expose kernel internals would go unnoticed. Therefore, do not sign staging modules so that they cannot be loaded in a secure boot environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642368/+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 1639924] Re: Kernel livepatch support for for s390x
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- 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/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: Fix Released Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: Invalid Status in linux source package in Jammy: Fix Released Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels. * This SRU is to enable s390x builds of kpatch on kinetic & jammy. * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches. [ Test Plan ] * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on: - amd64 jammy v5.15 - amd64 & s390x jammy v5.19 - amd64 & s390x kinetic v5.19 [ Where problems could occur ] * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains. * This is a fairly large upstream update to the tooling. * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot- module'. And '--ott-module-src' becomes mandatory in such cases, previously '--sourcedire' was required. Additional command line options added '--oot-module-src, -R|--non- replace'. '--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'. kpatch-cc utility is added, which is a toolchain wrapper. Thus adjustments might be needed to scripts used to invoke and create kpatch modules. * Majority of non-test/non-doc changes are to do with: - add support for s390x and 32bit powerpc - add support for newer kernels and compilers (support & bugfixes to various sections and symbols) - more strict checking and bugfixes w.r.t. livepatch generation - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. * Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels. $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch- build/ > shortlog.txt d46fea98ef kpatch-build: strengthen conditions for changed sections 9fac261ed0 kpatch-build: rela section could disappear after patched fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support 07433e98c0 kpatch-cc: fix stripping of source tree prefix 33368a88cd create-diff-object: add support for .return_sites section (x86) e921c557f9 macros: tweak syscall patching macros a1171b112e create-diff-object: Create missing section symbol 0308d52bcd kpatch/s390: Enable kpatch build support b0330ab18e kpatch/s390: Add additional bundled symbols. eb4a85f778 kpatch/s390: Add exclusion lists f0d00a9290 kpatch/s390: Add initial support for kpatch 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch c6d0b5450b lookup: fix symtab parsing 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() 017015a725 create-diff-object: make kpatch_check_relocations() more precise f0e3da336c create-diff-object: fix string extraction 86d5208b46 create-diff-object: error on symbol conversion failure 325bccd89d create-diff-object: skip conversion for sections which never have symbols 8
[Kernel-packages] [Bug 2009442] Re: glibc fails for bionic-kvm 4.15.0-1136.141
Both focal and bionic passed glibc tests for linux-kvm: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/g/glibc/20230428_090153_8d77a@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/g/glibc/20230428_162353_fc51a@/log.gz Marking as verified. ** Tags removed: verification-needed-bionic verification-needed-focal ** Tags added: verification-done-bionic verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2009442 Title: glibc fails for bionic-kvm 4.15.0-1136.141 Status in autopkgtest package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in autopkgtest source package in Bionic: Invalid Status in linux-kvm source package in Bionic: Fix Committed Status in autopkgtest source package in Focal: Invalid Status in linux-kvm source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] bionic linux-kvm failure https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/g/glibc/20230213_154436_b51c9@/log.gz From logs FAIL: misc/tst-bz21269 original exit status 1 error: ../sysdeps/unix/sysv/linux/i386/tst-bz21269.c:55: not true: syscall (SYS_modify_ldt, 1, ptr, bytecount) == 0 error: 1 test failures Syscall modify_ldt is not enabled because CONFIG_MODIFY_LDT_SYSCALL=n for bionic-kvm, even though generic and newer versions (even kvm derivativatives) have it enabled. [Fix] Custom patch to bionic-kvm to enable CONFIG_MODIFY_LDT_SYSCALL [Test Plan] Before the fix, autopkgtest for glibc will fail with +-+ | Encountered regressions that don't match expected failures. | +-+ FAIL: misc/tst-bz21269 After the fix, it should pass [Where problems could occur] Regression probability is pretty low, we are adding functionality not previously present but looking at focal,jammy this test was fine. Note: Not sure why this was not enabled for bionic-kvm, even though newer versions of linux kvm has it enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2009442/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019000] Re: Use new annotations model
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019000 Title: Use new annotations model Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Confirmed Bug description: [Impact] Starting with lunar we have introduced a new way to manage kernel configs, unifying the duplicated information defined in the annotations file + config chunks into an annotations-only model. [Test case] A kernel build can be considered a valid test case, in particular the specific command that is used to update the .config's for all the supported architectures and flavours: $ fakeroot debian/rules updateconfigs [Fix] Import the required changes in debian/ from lunar (with the required adjustments) to support the annotations-only model also in all the previous releases. [Regression potential] We may experience regressions during the updateconfigs step, especially with derivatives. Moreover, derivatives that want to transition to the new annotations model require to adjust the header in the annotations file as following (make sure to define the corresponding architectures and flavours): # FORMAT: 4 # ARCH: amd64 arm64 armhf ppc64el s390x # FLAVOUR: amd64-generic amd64-lowlatency arm64-generic arm64-generic-64k arm64-lowlatency arm64-lowlatency-64k armhf-generic armhf-generic-lpae ppc64el-generic s390x-generic After adjusting the header a special command is provided to transition to the new annotations-only model: $ fakeroot debian/rules migrateconfigs This command should automatically import the old configs into the new annotations file. A kernel with this change applied can still support the old annotations+configs model, the transition to the new model is not mandatory. Basically without using `fakeroot debian/rules migrateconfigs` the updateconfigs step will continue to use the old model and the old scripts (that is the safest approach to avoid potential unexpected .config changes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019000/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016269] Re: conntrack mark is not advertised via netlink
Fix sent to ML
https://lists.ubuntu.com/archives/kernel-team/2023-May/139327.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016269
Title:
conntrack mark is not advertised via netlink
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
New
Status in linux source package in Kinetic:
New
Bug description:
SRU justification sent to ML:
[Impact]
There was a commit 95fcb42e5f20
("netfilter: ctnetlink: fix compilation warning after data race fixes in ct
mark")
that introduces a regression where the "mark" variable is no longer
dumped in netlink netfilter conntrack messages, which userspace tools use
to mark and track connections.
[Fix]
Introduce the upstream fix 9f7dd42f0db1
("netfilter: ctnetlink: revert to dumping mark regardless of event type")
that always dumps the 'mark' variable for conntrack entries.
This fix has also landed in 5.15 upstream stable.
[Test]
Run 'conntrack -E' and check the output of connection entries.
The 'mark' variable should now be present in connection entries after
the fix.
before fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
after fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1
[Where problems could occur]
The fixes are pretty straight forward so regression potential should be
minimal.
[Impact]
The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix
compilation warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter:
ctnetlink: revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backported in v5.15.103:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c
[Test Case]
Run 'conntrack -E' and check the output.
Before the problematic commit:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED]
mark=0 use=1
'mark=' is seen on connrtack event
after:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
=> 'mark=' is not seen.
[Regression Potential]
The patch is quite simple. It has been backported in the official 5.15
stable. The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016269/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011616] Re: Connection timeout due to conntrack limits
As this change doesent have reproducers and was verified by the GKE team I will mark it verified in kinetic and jammy. ** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2011616 Title: Connection timeout due to conntrack limits Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-gcp source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-gcp source package in Lunar: New Bug description: Customers of GKE 1.25 and 1.26 are affected by the conntrack performance issue that causes random connection timeouts. The fix has been committed to to the upstream's net git repo and to prodkernel and needs to be backported to Ubuntu versions with kernel 5.15. https://partnerissuetracker.corp.google.com/issues/272090522 Fix: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=c77737b736ceb50fdf150434347dbd81ec76dbb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019131] [NEW] Add PPIN support for Intel EMR cpu
Public bug reported: SRU Justification [Impact] Intel has introduced support for their new Emerald Rapids CPU. It was backported to Jammy in #lp2015372 and in #lp2015855. The remaining feature needed to fully support EMR is PPIN (the Protected Processor Inventory/Identification Number). This was recently pushed to upstream in 6.4 in commit 36168bc061b4368ad19e82b06a6463c95d3bb9a7. The change is very straightforward, it adds a new entry for EMERALDRAPIDS_X in the cpuids table where cpus that support ppin are listed. The table is then used in `ppin_init`. In Jammy, this implementation is missing. Both Amd and Intel have their own implementation which is doing pretty much the same. Instead of a list of cpus supported, a switch case is used instead in their init functions (amd_detect_ppin and intel_ppin_init). To reduce duplication of code and to help backport smoothly the new addition of EMR, commit 0dcab41d3487acadf64d0667398e032341bd9918 “x86/cpu: Merge Intel and AMD ppin_init() functions” was backported too. Thus commits: - 0dcab41d3487acadf64d0667398e032341bd9918: "x86/cpu: Merge Intel and AMD ppin_init() functions" - 36168bc061b4368ad19e82b06a6463c95d3bb9a7: "x86/cpu: Add Xeon Emerald Rapids to list of CPUs that support PPIN" are needed to support PPIN for EMR. [Testing] Kernel was built on cbd and boot tested on a VM. [Regression potential] Very low, it is a small refactor that removes duplication and it should not affect the functionality. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Roxana Nicolescu (roxanan) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Roxana Nicolescu (roxanan) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Summary changed: - Enable PPIN for Intel EMR cpu + Add PPIN support for Intel EMR cpu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019131 Title: Add PPIN support for Intel EMR cpu Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: New Bug description: SRU Justification [Impact] Intel has introduced support for their new Emerald Rapids CPU. It was backported to Jammy in #lp2015372 and in #lp2015855. The remaining feature needed to fully support EMR is PPIN (the Protected Processor Inventory/Identification Number). This was recently pushed to upstream in 6.4 in commit 36168bc061b4368ad19e82b06a6463c95d3bb9a7. The change is very straightforward, it adds a new entry for EMERALDRAPIDS_X in the cpuids table where cpus that support ppin are listed. The table is then used in `ppin_init`. In Jammy, this implementation is missing. Both Amd and Intel have their own implementation which is doing pretty much the same. Instead of a list of cpus supported, a switch case is used instead in their init functions (amd_detect_ppin and intel_ppin_init). To reduce duplication of code and to help backport smoothly the new addition of EMR, commit 0dcab41d3487acadf64d0667398e032341bd9918 “x86/cpu: Merge Intel and AMD ppin_init() functions” was backported too. Thus commits: - 0dcab41d3487acadf64d0667398e032341bd9918: "x86/cpu: Merge Intel and AMD ppin_init() functions" - 36168bc061b4368ad19e82b06a6463c95d3bb9a7: "x86/cpu: Add Xeon Emerald Rapids to list of CPUs that support PPIN" are needed to support PPIN for EMR. [Testing] Kernel was built on cbd and boot tested on a VM. [Regression potential] Very low, it is a small refactor that removes duplication and it should not affect the functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019131/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006716] Re: 5 failures reported in net:fcnal-test.sh on Jammy
** Tags added: sru-20230417 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2006716 Title: 5 failures reported in net:fcnal-test.sh on Jammy Status in ubuntu-kernel-tests: New Status in linux-hwe-5.15 package in Ubuntu: New Status in linux-hwe-5.15 source package in Focal: New Bug description: This is not a regression, but something covered by bug 2006692 There are 5 sub-test failures reported in this test on Jammy: # Tests passed: 857 # Tests failed: 5 # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL] We might see failure came up in F/K after bug 2006391 being fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016269] Re: conntrack mark is not advertised via netlink
** Changed in: linux (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: linux (Ubuntu Kinetic)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Kinetic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016269
Title:
conntrack mark is not advertised via netlink
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
In Progress
Bug description:
SRU justification sent to ML:
[Impact]
There was a commit 95fcb42e5f20
("netfilter: ctnetlink: fix compilation warning after data race fixes in ct
mark")
that introduces a regression where the "mark" variable is no longer
dumped in netlink netfilter conntrack messages, which userspace tools use
to mark and track connections.
[Fix]
Introduce the upstream fix 9f7dd42f0db1
("netfilter: ctnetlink: revert to dumping mark regardless of event type")
that always dumps the 'mark' variable for conntrack entries.
This fix has also landed in 5.15 upstream stable.
[Test]
Run 'conntrack -E' and check the output of connection entries.
The 'mark' variable should now be present in connection entries after
the fix.
before fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
after fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1
[Where problems could occur]
The fixes are pretty straight forward so regression potential should be
minimal.
[Impact]
The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix
compilation warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter:
ctnetlink: revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backported in v5.15.103:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c
[Test Case]
Run 'conntrack -E' and check the output.
Before the problematic commit:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED]
mark=0 use=1
'mark=' is seen on connrtack event
after:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
=> 'mark=' is not seen.
[Regression Potential]
The patch is quite simple. It has been backported in the official 5.15
stable. The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016269/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013209] Re: expoline.o is packaged unconditionally for s390x
verified that there are no build issues with jammy or kinetic and everything is building as expected, marking verification-passed ** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2013209 Title: expoline.o is packaged unconditionally for s390x Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.15 package in Ubuntu: New Status in linux-hwe-5.15 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: https://bugs.launchpad.net/bugs/1639924 enabled CONFIG_EXPOLINE_EXTERN for s390x in Jammy. While this works as expected on Jammy, it won't work on some derivatives of it: for example focal:hwe-5.15. On Focal, this config can't be enabled due to the GCC version it comes with. CONFIG_EXPOLINE_EXTERN requires >= 110200 while Focal comes with 90400. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013209/+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 2019140] [NEW] package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-comm
Public bug reported: ramslab@ramslab:~$ sudo apt-get check [sudo] password for ramslab: Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-realtime-tools-5.15.0-1037 : Depends: linux-tools-common but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-tools-common The following NEW packages will be installed: linux-tools-common 0 upgraded, 1 newly installed, 0 to remove and 11 not upgraded. 2 not fully installed or removed. Need to get 0 B/290 kB of archives. After this operation, 823 kB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 215696 files and directories currently installed.) Preparing to unpack .../linux-tools-common_5.15.0-71.78_all.deb ... Unpacking linux-tools-common (5.15.0-71.78) ... dpkg: error processing archive /var/cache/apt/archives/linux-tools-common_5.15.0 -71.78_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-io tg-tools-common 5.15.0-1028.33 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/linux-tools-common_5.15.0-71.78_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 5.15.0-1037.40-realtime 5.15.92 Uname: Linux 5.15.0-1037-realtime x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: linux-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ramslab2044 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Wed May 10 18:06:06 2023 DpkgTerminalLog: Preparing to unpack .../linux-tools-common_5.15.0-72.79_all.deb ... Unpacking linux-tools-common (5.15.0-72.79) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-common_5.15.0-72.79_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1028.33 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1028.33 InstallationDate: Installed on 2023-04-21 (19 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: LENOVO 20S40009IX ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1037-realtime root=UUID=8374d98a-f4a8-4c09-869c-4e6f33ccff6c ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1028.33 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S40009IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.6:svnLENOVO:pn20S40009IX:pvrThinkPadP14sGen1:rvnLENOVO:rn20S40009IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20S4_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20S40009IX dmi.product.sku: LENOVO_MT_20S4_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019140 Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1028.33 Status in linux package in Ubuntu: New Bug description: ramslab@ramslab:~$ sudo apt-get check [sudo] password for ramslab: Reading package lists... Done Building
[Kernel-packages] [Bug 2019140] 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/2019140 Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1028.33 Status in linux package in Ubuntu: Confirmed Bug description: ramslab@ramslab:~$ sudo apt-get check [sudo] password for ramslab: Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-realtime-tools-5.15.0-1037 : Depends: linux-tools-common but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-tools-common The following NEW packages will be installed: linux-tools-common 0 upgraded, 1 newly installed, 0 to remove and 11 not upgraded. 2 not fully installed or removed. Need to get 0 B/290 kB of archives. After this operation, 823 kB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 215696 files and directories currently installed.) Preparing to unpack .../linux-tools-common_5.15.0-71.78_all.deb ... Unpacking linux-tools-common (5.15.0-71.78) ... dpkg: error processing archive /var/cache/apt/archives/linux-tools-common_5.15.0 -71.78_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-io tg-tools-common 5.15.0-1028.33 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/linux-tools-common_5.15.0-71.78_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 5.15.0-1037.40-realtime 5.15.92 Uname: Linux 5.15.0-1037-realtime x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: linux-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ramslab2044 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Wed May 10 18:06:06 2023 DpkgTerminalLog: Preparing to unpack .../linux-tools-common_5.15.0-72.79_all.deb ... Unpacking linux-tools-common (5.15.0-72.79) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-common_5.15.0-72.79_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1028.33 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1028.33 InstallationDate: Installed on 2023-04-21 (19 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: LENOVO 20S40009IX ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1037-realtime root=UUID=8374d98a-f4a8-4c09-869c-4e6f33ccff6c ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1028.33 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S40009IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.6:svnLENOVO:pn20S40009IX:pvrThinkPadP14sGen1:rvnLENOVO:rn20S40009IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20S4_BU_Think_FM_ThinkPadP14sGen1: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20S40009IX dmi.product.sku: LENOVO_MT_20S4_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen
[Kernel-packages] [Bug 2019011] Re: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Patch added: "0001-net-mlx5-cmdif-Avoid-skipping-reclaim-pages-if-FW-is.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019011/+attachment/5672245/+files/0001-net-mlx5-cmdif-Avoid-skipping-reclaim-pages-if-FW-is.patch -- 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/2019011 Title: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver Status in linux package in Ubuntu: New Status in linux source package in Focal: In Progress Bug description: ---Problem Description--- Kernel panic with "refcount_t: underflow" in kernel log Contact Information = rijo...@ibm.com, vineeth.vija...@ibm.com ---uname output--- 5.4.0-128-generic Machine Type = s390x ---System Hang--- Kernel panic and stack-trace as below ---Debugger--- A debugger is not configured Stack trace output: [Sat Apr 8 17:52:21 UTC 2023] Call Trace: [Sat Apr 8 17:52:21 UTC 2023] ([<002a5939a286>] refcount_warn_saturate+0xce/0x140) [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f861e>] cmd_ent_put+0xe6/0xf8 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9b6a>] mlx5_cmd_comp_handler+0x102/0x4f0 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9f8a>] cmd_comp_notifier+0x32/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff805fe4fc>] mlx5_eq_async_int+0x13c/0x200 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff8061318e>] mlx5_irq_int_handler+0x2e/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e960ce>] zpci_floating_irq_handler+0xe6/0x1b8 [Sat Apr 8 17:52:21 UTC 2023] [<002a594f54a6>] do_airq_interrupt+0x96/0x130 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e30e42>] do_IRQ+0x7a/0xb0 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a408>] io_int_handler+0x12c/0x294 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e2752e>] enabled_wait+0x46/0xd8 [Sat Apr 8 17:52:21 UTC 2023] ([<002a58e2752e>] enabled_wait+0x46/0xd8) [Sat Apr 8 17:52:21 UTC 2023] [<002a58e278aa>] arch_cpu_idle+0x2a/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee1536>] do_idle+0xee/0x1b0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee17a6>] cpu_startup_entry+0x36/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3ab38>] smp_init_secondary+0xc8/0xe8 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3a770>] smp_start_secondary+0x88/0x90 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a09c>] kernel_thread_starter+0x0/0x10 [Sat Apr 8 17:52:21 UTC 2023] Last Breaking-Event-Address: [Sat Apr 8 17:52:21 UTC 2023] [<002a5939a286>] refcount_warn_saturate+0xce/0x140 [Sat Apr 8 17:52:21 UTC 2023] ---[ end trace 6ec6f9c6f666ca2d ]--- [Sat Apr 8 17:52:21 UTC 2023] specification exception: 0006 ilc:3 [#1] SMP [Sat Apr 8 17:52:21 UTC 2023] Modules linked in: sysdigcloud_probe(OE) vhost_net vhost macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache ebtable_broute binfmt_misc nbd veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle ip6table_mangle ip6table_nat xt_mark sunrpc lcs ctcm fsm zfcp scsi_transport_fc dasd_fba_mod dasd_eckd_mod dasd_mod nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_multiport xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core xt_MASQUERADE iptable_nat xt_addrtype xt_conntrack br_netfilter bridge stp llc aufs ebtable_filter ebtables ip6tabl
[Kernel-packages] [Bug 2019011] Re: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver
** Patch added: "0002-net-mlx5-Fix-handling-of-entry-refcount-when-command.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019011/+attachment/5672246/+files/0002-net-mlx5-Fix-handling-of-entry-refcount-when-command.patch -- 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/2019011 Title: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver Status in linux package in Ubuntu: New Status in linux source package in Focal: In Progress Bug description: ---Problem Description--- Kernel panic with "refcount_t: underflow" in kernel log Contact Information = rijo...@ibm.com, vineeth.vija...@ibm.com ---uname output--- 5.4.0-128-generic Machine Type = s390x ---System Hang--- Kernel panic and stack-trace as below ---Debugger--- A debugger is not configured Stack trace output: [Sat Apr 8 17:52:21 UTC 2023] Call Trace: [Sat Apr 8 17:52:21 UTC 2023] ([<002a5939a286>] refcount_warn_saturate+0xce/0x140) [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f861e>] cmd_ent_put+0xe6/0xf8 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9b6a>] mlx5_cmd_comp_handler+0x102/0x4f0 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9f8a>] cmd_comp_notifier+0x32/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff805fe4fc>] mlx5_eq_async_int+0x13c/0x200 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff8061318e>] mlx5_irq_int_handler+0x2e/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e960ce>] zpci_floating_irq_handler+0xe6/0x1b8 [Sat Apr 8 17:52:21 UTC 2023] [<002a594f54a6>] do_airq_interrupt+0x96/0x130 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e30e42>] do_IRQ+0x7a/0xb0 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a408>] io_int_handler+0x12c/0x294 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e2752e>] enabled_wait+0x46/0xd8 [Sat Apr 8 17:52:21 UTC 2023] ([<002a58e2752e>] enabled_wait+0x46/0xd8) [Sat Apr 8 17:52:21 UTC 2023] [<002a58e278aa>] arch_cpu_idle+0x2a/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee1536>] do_idle+0xee/0x1b0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee17a6>] cpu_startup_entry+0x36/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3ab38>] smp_init_secondary+0xc8/0xe8 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3a770>] smp_start_secondary+0x88/0x90 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a09c>] kernel_thread_starter+0x0/0x10 [Sat Apr 8 17:52:21 UTC 2023] Last Breaking-Event-Address: [Sat Apr 8 17:52:21 UTC 2023] [<002a5939a286>] refcount_warn_saturate+0xce/0x140 [Sat Apr 8 17:52:21 UTC 2023] ---[ end trace 6ec6f9c6f666ca2d ]--- [Sat Apr 8 17:52:21 UTC 2023] specification exception: 0006 ilc:3 [#1] SMP [Sat Apr 8 17:52:21 UTC 2023] Modules linked in: sysdigcloud_probe(OE) vhost_net vhost macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache ebtable_broute binfmt_misc nbd veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle ip6table_mangle ip6table_nat xt_mark sunrpc lcs ctcm fsm zfcp scsi_transport_fc dasd_fba_mod dasd_eckd_mod dasd_mod nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_multiport xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core xt_MASQUERADE iptable_nat xt_addrtype xt_conntrack br_netfilter bridge stp llc aufs ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfr m_algo bonding s390_trng [Sat Apr 8
[Kernel-packages] [Bug 2019011] Re: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver
The change requires the backport of one additional patch (both are provided above). We created a test kernel with those changes for validation and you can find the debian packages at https://people.canonical.com/~mhcerri/lp2019011/s390x_debs.tgz Please let us know if the test kernel works as expected. Thank you! -- 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/2019011 Title: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver Status in linux package in Ubuntu: New Status in linux source package in Focal: In Progress Bug description: ---Problem Description--- Kernel panic with "refcount_t: underflow" in kernel log Contact Information = rijo...@ibm.com, vineeth.vija...@ibm.com ---uname output--- 5.4.0-128-generic Machine Type = s390x ---System Hang--- Kernel panic and stack-trace as below ---Debugger--- A debugger is not configured Stack trace output: [Sat Apr 8 17:52:21 UTC 2023] Call Trace: [Sat Apr 8 17:52:21 UTC 2023] ([<002a5939a286>] refcount_warn_saturate+0xce/0x140) [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f861e>] cmd_ent_put+0xe6/0xf8 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9b6a>] mlx5_cmd_comp_handler+0x102/0x4f0 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9f8a>] cmd_comp_notifier+0x32/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff805fe4fc>] mlx5_eq_async_int+0x13c/0x200 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff8061318e>] mlx5_irq_int_handler+0x2e/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e960ce>] zpci_floating_irq_handler+0xe6/0x1b8 [Sat Apr 8 17:52:21 UTC 2023] [<002a594f54a6>] do_airq_interrupt+0x96/0x130 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e30e42>] do_IRQ+0x7a/0xb0 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a408>] io_int_handler+0x12c/0x294 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e2752e>] enabled_wait+0x46/0xd8 [Sat Apr 8 17:52:21 UTC 2023] ([<002a58e2752e>] enabled_wait+0x46/0xd8) [Sat Apr 8 17:52:21 UTC 2023] [<002a58e278aa>] arch_cpu_idle+0x2a/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee1536>] do_idle+0xee/0x1b0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee17a6>] cpu_startup_entry+0x36/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3ab38>] smp_init_secondary+0xc8/0xe8 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3a770>] smp_start_secondary+0x88/0x90 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a09c>] kernel_thread_starter+0x0/0x10 [Sat Apr 8 17:52:21 UTC 2023] Last Breaking-Event-Address: [Sat Apr 8 17:52:21 UTC 2023] [<002a5939a286>] refcount_warn_saturate+0xce/0x140 [Sat Apr 8 17:52:21 UTC 2023] ---[ end trace 6ec6f9c6f666ca2d ]--- [Sat Apr 8 17:52:21 UTC 2023] specification exception: 0006 ilc:3 [#1] SMP [Sat Apr 8 17:52:21 UTC 2023] Modules linked in: sysdigcloud_probe(OE) vhost_net vhost macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache ebtable_broute binfmt_misc nbd veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle ip6table_mangle ip6table_nat xt_mark sunrpc lcs ctcm fsm zfcp scsi_transport_fc dasd_fba_mod dasd_eckd_mod dasd_mod nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_multiport xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core xt_MASQUERADE iptable_nat xt_addrtype xt_conntrack br_netfilter bridge stp llc aufs ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter xfrm_user xfrm4_tunnel tunnel4 i
[Kernel-packages] [Bug 2019143] [NEW] xdg-desktop-portal.service
Public bug reported: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] 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 2019143 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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] Re: xdg-desktop-portal.service
apport information ** Tags added: apport-collected mantic wayland-session ** Description changed: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. + --- + ProblemType: Bug + ApportVersion: 2.26.1-0ubuntu3 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: sway + DistroRelease: Ubuntu 23.10 + InstallationDate: Installed on 2021-01-13 (847 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 + RelatedPackageVersions: + linux-restricted-modules-6.2.0-1003-lowlatency N/A + linux-backports-modules-6.2.0-1003-lowlatency N/A + linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 + Tags: wayland-session mantic + Uname: Linux 6.2.0-1003-lowlatency x86_64 + UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) + UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark + _MarkForUpload: True + dmi.bios.date: 12/08/2020 + dmi.bios.release: 5.16 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: N.1.07.A02 + dmi.board.asset.tag: Standard + dmi.board.name: PF5NU1G + dmi.board.vendor: SchenkerTechnologiesGmbH + dmi.board.version: Standard + dmi.chassis.asset.tag: Standard + dmi.chassis.type: 10 + dmi.chassis.vendor: SchenkerTechnologiesGmbH + dmi.chassis.version: Standard + dmi.ec.firmware.release: 1.4 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: + dmi.product.family: RENOIR + dmi.product.name: SCHENKER VIA 15 Pro + dmi.product.sku: SVI15PM20 + dmi.product.version: Standard + dmi.sys.vendor: SchenkerTechnologiesGmbH ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672280/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[250
[Kernel-packages] [Bug 2019143] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672281/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672282/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672284/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672283/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672285/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672286/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672287/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672289/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672288/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672291/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672290/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672292/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672293/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672295/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672294/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672296/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672297/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019143] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2019143/+attachment/5672298/+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/2019143 Title: xdg-desktop-portal.service Status in linux package in Ubuntu: Incomplete Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019143/+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 2019011] Comment bridged from LTC Bugzilla
--- Comment From vineeth.vija...@ibm.com 2023-05-10 15:31 EDT--- Hi, Thank you very much for the quick support. Is this kernel (5.4.0.149) and the package attached corresponds to 20.04 or 20.04 HWE ? -- 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/2019011 Title: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver Status in linux package in Ubuntu: New Status in linux source package in Focal: In Progress Bug description: ---Problem Description--- Kernel panic with "refcount_t: underflow" in kernel log Contact Information = rijo...@ibm.com, vineeth.vija...@ibm.com ---uname output--- 5.4.0-128-generic Machine Type = s390x ---System Hang--- Kernel panic and stack-trace as below ---Debugger--- A debugger is not configured Stack trace output: [Sat Apr 8 17:52:21 UTC 2023] Call Trace: [Sat Apr 8 17:52:21 UTC 2023] ([<002a5939a286>] refcount_warn_saturate+0xce/0x140) [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f861e>] cmd_ent_put+0xe6/0xf8 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9b6a>] mlx5_cmd_comp_handler+0x102/0x4f0 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9f8a>] cmd_comp_notifier+0x32/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff805fe4fc>] mlx5_eq_async_int+0x13c/0x200 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff8061318e>] mlx5_irq_int_handler+0x2e/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e960ce>] zpci_floating_irq_handler+0xe6/0x1b8 [Sat Apr 8 17:52:21 UTC 2023] [<002a594f54a6>] do_airq_interrupt+0x96/0x130 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e30e42>] do_IRQ+0x7a/0xb0 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a408>] io_int_handler+0x12c/0x294 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e2752e>] enabled_wait+0x46/0xd8 [Sat Apr 8 17:52:21 UTC 2023] ([<002a58e2752e>] enabled_wait+0x46/0xd8) [Sat Apr 8 17:52:21 UTC 2023] [<002a58e278aa>] arch_cpu_idle+0x2a/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee1536>] do_idle+0xee/0x1b0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee17a6>] cpu_startup_entry+0x36/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3ab38>] smp_init_secondary+0xc8/0xe8 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3a770>] smp_start_secondary+0x88/0x90 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a09c>] kernel_thread_starter+0x0/0x10 [Sat Apr 8 17:52:21 UTC 2023] Last Breaking-Event-Address: [Sat Apr 8 17:52:21 UTC 2023] [<002a5939a286>] refcount_warn_saturate+0xce/0x140 [Sat Apr 8 17:52:21 UTC 2023] ---[ end trace 6ec6f9c6f666ca2d ]--- [Sat Apr 8 17:52:21 UTC 2023] specification exception: 0006 ilc:3 [#1] SMP [Sat Apr 8 17:52:21 UTC 2023] Modules linked in: sysdigcloud_probe(OE) vhost_net vhost macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache ebtable_broute binfmt_misc nbd veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle ip6table_mangle ip6table_nat xt_mark sunrpc lcs ctcm fsm zfcp scsi_transport_fc dasd_fba_mod dasd_eckd_mod dasd_mod nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_multiport xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core xt_MASQUERADE iptable_nat xt_addrtype xt_conntrack br_netfilter bridge stp llc aufs ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfr m_algo bonding s390_trng [Sat Apr 8 17:52:21 UTC 2023] vfio_ccw
[Kernel-packages] [Bug 2019011] Re: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver
Hi, Vineeth. These packages are for the 20.04 LTS Kernel. BR, pprincipeza -- 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/2019011 Title: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver Status in linux package in Ubuntu: New Status in linux source package in Focal: In Progress Bug description: ---Problem Description--- Kernel panic with "refcount_t: underflow" in kernel log Contact Information = rijo...@ibm.com, vineeth.vija...@ibm.com ---uname output--- 5.4.0-128-generic Machine Type = s390x ---System Hang--- Kernel panic and stack-trace as below ---Debugger--- A debugger is not configured Stack trace output: [Sat Apr 8 17:52:21 UTC 2023] Call Trace: [Sat Apr 8 17:52:21 UTC 2023] ([<002a5939a286>] refcount_warn_saturate+0xce/0x140) [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f861e>] cmd_ent_put+0xe6/0xf8 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9b6a>] mlx5_cmd_comp_handler+0x102/0x4f0 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9f8a>] cmd_comp_notifier+0x32/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff805fe4fc>] mlx5_eq_async_int+0x13c/0x200 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff8061318e>] mlx5_irq_int_handler+0x2e/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e960ce>] zpci_floating_irq_handler+0xe6/0x1b8 [Sat Apr 8 17:52:21 UTC 2023] [<002a594f54a6>] do_airq_interrupt+0x96/0x130 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e30e42>] do_IRQ+0x7a/0xb0 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a408>] io_int_handler+0x12c/0x294 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e2752e>] enabled_wait+0x46/0xd8 [Sat Apr 8 17:52:21 UTC 2023] ([<002a58e2752e>] enabled_wait+0x46/0xd8) [Sat Apr 8 17:52:21 UTC 2023] [<002a58e278aa>] arch_cpu_idle+0x2a/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee1536>] do_idle+0xee/0x1b0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee17a6>] cpu_startup_entry+0x36/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3ab38>] smp_init_secondary+0xc8/0xe8 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3a770>] smp_start_secondary+0x88/0x90 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a09c>] kernel_thread_starter+0x0/0x10 [Sat Apr 8 17:52:21 UTC 2023] Last Breaking-Event-Address: [Sat Apr 8 17:52:21 UTC 2023] [<002a5939a286>] refcount_warn_saturate+0xce/0x140 [Sat Apr 8 17:52:21 UTC 2023] ---[ end trace 6ec6f9c6f666ca2d ]--- [Sat Apr 8 17:52:21 UTC 2023] specification exception: 0006 ilc:3 [#1] SMP [Sat Apr 8 17:52:21 UTC 2023] Modules linked in: sysdigcloud_probe(OE) vhost_net vhost macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache ebtable_broute binfmt_misc nbd veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle ip6table_mangle ip6table_nat xt_mark sunrpc lcs ctcm fsm zfcp scsi_transport_fc dasd_fba_mod dasd_eckd_mod dasd_mod nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_multiport xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core xt_MASQUERADE iptable_nat xt_addrtype xt_conntrack br_netfilter bridge stp llc aufs ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfr m_algo bonding s390_trng [Sat Apr 8 17:52:21 UTC 2023] vfio_ccw chsc_sch vfio_mdev mdev vfio_iommu_type1 eadm_sch vfio sch_fq_codel ip_tables x_tables overlay raid10 raid456 async_raid6_recov asy
[Kernel-packages] [Bug 2019011] Re: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver
** Tags added: patch -- 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/2019011 Title: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver Status in linux package in Ubuntu: New Status in linux source package in Focal: In Progress Bug description: ---Problem Description--- Kernel panic with "refcount_t: underflow" in kernel log Contact Information = rijo...@ibm.com, vineeth.vija...@ibm.com ---uname output--- 5.4.0-128-generic Machine Type = s390x ---System Hang--- Kernel panic and stack-trace as below ---Debugger--- A debugger is not configured Stack trace output: [Sat Apr 8 17:52:21 UTC 2023] Call Trace: [Sat Apr 8 17:52:21 UTC 2023] ([<002a5939a286>] refcount_warn_saturate+0xce/0x140) [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f861e>] cmd_ent_put+0xe6/0xf8 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9b6a>] mlx5_cmd_comp_handler+0x102/0x4f0 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9f8a>] cmd_comp_notifier+0x32/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff805fe4fc>] mlx5_eq_async_int+0x13c/0x200 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff8061318e>] mlx5_irq_int_handler+0x2e/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e960ce>] zpci_floating_irq_handler+0xe6/0x1b8 [Sat Apr 8 17:52:21 UTC 2023] [<002a594f54a6>] do_airq_interrupt+0x96/0x130 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e30e42>] do_IRQ+0x7a/0xb0 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a408>] io_int_handler+0x12c/0x294 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e2752e>] enabled_wait+0x46/0xd8 [Sat Apr 8 17:52:21 UTC 2023] ([<002a58e2752e>] enabled_wait+0x46/0xd8) [Sat Apr 8 17:52:21 UTC 2023] [<002a58e278aa>] arch_cpu_idle+0x2a/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee1536>] do_idle+0xee/0x1b0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee17a6>] cpu_startup_entry+0x36/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3ab38>] smp_init_secondary+0xc8/0xe8 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3a770>] smp_start_secondary+0x88/0x90 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a09c>] kernel_thread_starter+0x0/0x10 [Sat Apr 8 17:52:21 UTC 2023] Last Breaking-Event-Address: [Sat Apr 8 17:52:21 UTC 2023] [<002a5939a286>] refcount_warn_saturate+0xce/0x140 [Sat Apr 8 17:52:21 UTC 2023] ---[ end trace 6ec6f9c6f666ca2d ]--- [Sat Apr 8 17:52:21 UTC 2023] specification exception: 0006 ilc:3 [#1] SMP [Sat Apr 8 17:52:21 UTC 2023] Modules linked in: sysdigcloud_probe(OE) vhost_net vhost macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache ebtable_broute binfmt_misc nbd veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle ip6table_mangle ip6table_nat xt_mark sunrpc lcs ctcm fsm zfcp scsi_transport_fc dasd_fba_mod dasd_eckd_mod dasd_mod nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_multiport xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core xt_MASQUERADE iptable_nat xt_addrtype xt_conntrack br_netfilter bridge stp llc aufs ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfr m_algo bonding s390_trng [Sat Apr 8 17:52:21 UTC 2023] vfio_ccw chsc_sch vfio_mdev mdev vfio_iommu_type1 eadm_sch vfio sch_fq_codel ip_tables x_tables overlay raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq rai
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-fde-5.15/5.15.0.1038.45~20.04.1.17)
All autopkgtests for the newly accepted linux-meta-azure-fde-5.15 (5.15.0.1038.45~20.04.1.17) for focal have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (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/focal/update_excuses.html#linux-meta-azure-fde-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4
Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/2858 ** Bug watch added: github.com/canonical/cloud-init/issues #2858 https://github.com/canonical/cloud-init/issues/2858 -- 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/1682871 Title: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4 Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in linux source package in Xenial: Fix Released Status in cloud-init source package in Yakkety: Fix Released Status in linux source package in Yakkety: Fix Released Status in cloud-init source package in Zesty: Fix Released Status in linux source package in Zesty: Fix Released Bug description: [Impact] * When vlan interfaces are created, their mac address is copied from the underlying interface, but it is not marked by kernel as stolen. * When underlying interface MAC address is changed, it does not propagate to the vlan interfaces. [Test Case] * Create vlan interface, check the addr_assign_type sysfs attribute, it should be 2, not 0. * Update the base interface mac address, the mac address of the vlan interface should change too. * cloud-init test case wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/get-proposed-cloudimg; chmod 755 get-proposed-cloudimg; for release in xenial yakkety zesty; do ./get-proposed-cloudimg $release; MODE=vlan ./btest-launch.sh $release-server-cloudimg-amd64-proposed.img ; # ubuntu/passw0rd python3 -c 'from cloudinit.net import get_interfaces_by_mac; print(get_interfaces_by_mac())'; # results in no runtime error and doesn't report vlan interface name done [Regression Potential] * Userspace may rely on non-propagating MAC addresses, and the fact that vlan mac address type is wrongly stated as non-stolen; however this behaviour will be consistent with 4.7+ kernels. [Other Info] * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into v4.4 kernels commit 308453aa9156a3b8ee382c0949befb507a32b0c1 Author: Mike Manning Date: Fri May 27 17:45:07 2016 +0100 vlan: Propagate MAC address to VLANs The MAC address of the physical interface is only copied to the VLAN when it is first created, resulting in an inconsistency after MAC address changes of only newly created VLANs having an up-to-date MAC. The VLANs should continue inheriting the MAC address of the physical interface until the VLAN MAC address is explicitly set to any value. This allows IPv6 EUI64 addresses for the VLAN to reflect any changes to the MAC of the physical interface and thus for DAD to behave as expected. Signed-off-by: Mike Manning Signed-off-by: David S. Miller * Original bug report When attempting to verify sru for bug 1669860, I found that vlans are not properly filtered out by 'get_interfaces_by_mac'. That means that the bug is still present with vlans. The reason for this is that /sys/class/net//addr_assign_type shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8. See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net for doc on addr_assign_type. Related bugs: * bug 1669860: cloud-init attempts to rename bonds To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1682871/+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 2019164] [NEW] Frequently failed to boot up Ubuntu
Public bug reported: Ubuntu frequently fails to boot up, it hangs between GRUB and login splash screen. I need to force turn off the computer and restart repeatedly to get it success. Sometimes I need to select older kernel to succeed, sometimes selecting older kernel doesn't help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-headers-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 11 08:39:48 2023 InstallationDate: Installed on 2021-06-05 (704 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2019164 Title: Frequently failed to boot up Ubuntu Status in linux-hwe-5.19 package in Ubuntu: New Bug description: Ubuntu frequently fails to boot up, it hangs between GRUB and login splash screen. I need to force turn off the computer and restart repeatedly to get it success. Sometimes I need to select older kernel to succeed, sometimes selecting older kernel doesn't help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-headers-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 11 08:39:48 2023 InstallationDate: Installed on 2021-06-05 (704 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2019164/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs
Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/2936 ** Bug watch added: github.com/canonical/cloud-init/issues #2936 https://github.com/canonical/cloud-init/issues/2936 -- 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/1701297 Title: NTP reload failure (unable to read library) on overlayfs Status in cloud-init: Won't Fix Status in apparmor package in Ubuntu: Invalid Status in cloud-init package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Fix Released Bug description: After update [1] of cloud-init in Ubuntu (which landed in xenial- updates on 2017-06-27), it is causing NTP reload failures. https://launchpad.net/ubuntu/+source/cloud- init/0.7.9-153-g16a7302f-0ubuntu1~16.04.1 In MAAS scenarios, this is causing the machine to fail to deploy. Related bugs: * bug 1645644: cloud-init ntp not using expected servers To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 2013198] Re: Fix (+follow-up) needed for SEV-SNP vulnerability
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oracle (Ubuntu) ** No longer affects: linux-oracle (Ubuntu Jammy) ** No longer affects: linux-oracle (Ubuntu Kinetic) ** No longer affects: linux-oracle (Ubuntu Lunar) ** No longer affects: linux-gcp (Ubuntu Kinetic) ** No longer affects: linux-gcp (Ubuntu Lunar) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2013198 Title: Fix (+follow-up) needed for SEV-SNP vulnerability Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Bug description: From email discussions with Dionna Glazee from Google: > This email details a critical vulnerability in SEV-SNP attestation > report integrity protection that must be patched in SEV-SNP-enabled > kernels. > > I'm reaching out since I've been tracking our progress towards a > stable offering of customer access to SEV-SNP "guest requests". I'd > like to know how or if y'all test the /dev/sev-guest driver. > > The reason I ask is because our host KVM injects failures into the > guest if requests come too frequently. Test suites that request > attestation reports in quick succession will fail without very recent > patches or workaround code in user space. > > Technical details, tl;dr > * Nov 21, 2022: Linux Kernel 6.1 included a security patch 47894e0fa > that will cause attestation to fail frequently (in GCE). Peter found > and patched this vulnerability. > > Details of security patch 47894e0fa: > This patch to sev-guest causes more fail-closed situations. All VMM > errors other than INVALID_LEN will wipe out the VMPCK and close the > guest's ability to communicate with the security processor. > Ratelimit failures will also cause a fail-closed situation. > > As you may know, guest requests are encrypted by the guest with > AES_GCM (not AES_GCM_SIV) and then passed through unencrypted memory > to the host's KVM. KVM forwards that to the crypto/ccp driver to > deliver to the AMD secure processor to respond to. When the VMM > returns an error instead of forwarding a request to the secure > processor, then the guest driver *does not* increment its IV. It can > therefore reuse an IV on multiple messages with different contents. > This breaks AES_GCM's security guarantees. > > Ratelimiting looks to the guest not as a stalled vCPU, but rather a > special error response that AMD will include in their next published > version of the GHCB protocol (I believe v2.02). This allows the guest > VM to schedule other threads and remain productive while waiting up to > 2 seconds for a request to be serviced. The special error code to an > unpatched kernel is just forwarded to the guest as an EIO. User space > may continue to issue requests, even if it is unsafe to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2013198/+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
