[Kernel-packages] [Bug 2011407] Re: Jammy update: v6.1.16 upstream stable release
** Tags removed: verification-needed-jammy ** Tags added: kernel-stable-tracking-bug -- 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/2011407 Title: Jammy update: v6.1.16 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 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: v6.1.16 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2011407/+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
** Tags added: originate-from-2002127 -- 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: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in alsa-ucm-conf source package in Jammy: In Progress 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: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: New Status in alsa-ucm-conf source package in Lunar: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: New 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
** Merge proposal linked: https://code.launchpad.net/~kobako/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/441281 ** Merge proposal linked: https://code.launchpad.net/~kobako/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/441279 ** Merge proposal linked: https://code.launchpad.net/~kobako/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/441282 -- 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 alsa-ucm-conf package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in alsa-ucm-conf source package in Jammy: In Progress 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: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: New Status in alsa-ucm-conf source package in Lunar: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: New 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 2007286] Re: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007286 Title: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed Status in linux package in Ubuntu: Expired Bug description: corrado@corrado-x-kinetic:~$ ls /lib/modules 5.19.0-23-generic 5.19.0-28-generic 5.19.0-29-generic 5.19.0-31-generic corrado@corrado-x-kinetic:~$ ls /boot config-5.19.0-29-generic memtest86+.elf config-5.19.0-31-generic memtest86+_multiboot.bin efi System.map-5.19.0-29-generic grub System.map-5.19.0-31-generic initrd.imgvmlinuz initrd.img-5.19.0-29-generic vmlinuz-5.19.0-29-generic initrd.img-5.19.0-31-generic vmlinuz-5.19.0-31-generic initrd.img.oldvmlinuz.old memtest86+.bin corrado@corrado-x-kinetic:~$ see also https://discourse.ubuntu.com/t/ubuntu-does-not-clean-out-old-kernel-module-files-in-lib-modules-when-old-kernels-are-removed/33906 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apt 2.5.3 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 16:23:49 2023 InstallationDate: Installed on 2022-11-28 (77 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007286/+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 2016045] Re: Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument]
I should have said "the only possible userspace solution". Strictly speaking it's the Intel kernel driver at fault for advertising DRM_CAP_ASYNC_PAGE_FLIP as supported and then rejecting it as invalid in some configurations. The driver has to do that because of hardware limitations, but still chooses to advertise the feature as supported because it's usually supported :S -- 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/2016045 Title: Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument] Status in linux-hwe-5.19 package in Ubuntu: Opinion Status in xorg-server package in Ubuntu: Triaged Bug description: 1/3 times I tab in / out of a app/game, that is running using the nvidia dedicated gpu, the screen freezes forcing me to restart my laptop. The cursor is still "usable" and reboot using SysRq REISUB is possible. This is not tied only to steam games, other apps/games like minecraft also cause this problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 13 00:58:23 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 5.19.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84c1] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:84c1] InstallationDate: Installed on 2023-02-06 (65 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=bd5e3449-4d4f-4ebd-afef-1e4da7b9ec69 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2020 dmi.bios.release: 15.23 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84C1 dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs2xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku7EF01EA#AB7: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs2xxx dmi.product.sku: 7EF01EA#AB7 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+
[Kernel-packages] [Bug 2007001] Re: Blank console display with aarch64 kernel 5.19.0-31
** No longer affects: linux-signed-hwe-5.19 (Ubuntu) ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Matthew Ruffell (mruffell) -- 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/2007001 Title: Blank console display with aarch64 kernel 5.19.0-31 Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: In Progress Bug description: Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion 13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the upgrade and after rebooting the VM no text or graphical console appears on the VM. The VM is running and can be accessed through SSH. Rebooting the VM with kernel 5.19.0-29 - everything is working as expected. Text and graphical consoles now display properly. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Sat Feb 11 13:04:22 2023 InstallationDate: Installed on 2022-09-11 (153 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha arm64 (20220911) IwConfig: lono wireless extensions. ens160no wireless extensions. MachineType: VMware, Inc. VMware20,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=5e9795ee-63e3-4df1-93e9-c36cd88c726c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW201.00V.20904234.BA64.2212051119 dmi.board.name: VBSA dmi.board.vendor: VMware, Inc. dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware, Inc. dmi.chassis.version: VMware20,1 dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW201.00V.20904234.BA64.2212051119:bd12/05/2022:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001: dmi.product.family: VMware dmi.product.name: VMware20,1 dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+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 affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** Changed in: alsa-ucm-conf (Ubuntu Lunar) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Lunar) Assignee: (unassigned) => koba (kobako) ** Changed in: alsa-ucm-conf (Ubuntu Kinetic) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: alsa-ucm-conf (Ubuntu Jammy) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) -- 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 alsa-ucm-conf package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in alsa-ucm-conf source package in Jammy: In Progress 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: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: New Status in alsa-ucm-conf source package in Lunar: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: New 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 2016706] Re: The 5.19 kernel backport is broken
*** This bug is a duplicate of bug 2007001 ***
https://bugs.launchpad.net/bugs/2007001
Hi Zack,
Thanks for the report and the link. I'll get a test kernel building with
a revert and we can get some community users to try it out.
I'll post it in bug 2007001 instead, the existing bug, and mark this one
as a duplicate. I'll post in the VMware forum too.
Thanks,
Matthew
** This bug has been marked a duplicate of bug 2007001
Blank console display with aarch64 kernel 5.19.0-31
--
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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
@mreed8855: We used "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). * https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html ** https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.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/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: New Status in linux source package in Lunar: Incomplete Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+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?)
Yeah, Trying with my own built 6.2 out of https://github.com/torvalds/linux and trying a full run, and after, running `lsmod |grep overlay` and the usage count of the modules is 0 when the script completes, with the distribution 6.2, it was ~1,100, It doesn't seem that the linux package uses debian/patches like other packages do, so I don't know which one to try to eliminate to see what is at fault as to why the mainline kernel doesn't seem to have this issue -- 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:nerdo
[Kernel-packages] [Bug 2012019] Re: Fix E-star testing failure with RTK 8852BE
As per ODM, the proposed kernel is verified. ** 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-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2012019 Title: Fix E-star testing failure with RTK 8852BE Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: New Bug description: [Impact] E-star testing failure on machine with RTK 8852BE configuration. [Fix] 1. Enable CLKREQ to reduce power consumption. 2. release RX standby timer of beamformee to save power [Test Case] 1. Prepare one system with RTK 8852BE WLAN/BT. 2. Run E-star testing. 3. The result must meet PASS criteria. [Where problems could occur] Low, may face the performance issue during throughput verification. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2012019/+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 2016829] [NEW] Completely support vxlan and erspan for flower
Public bug reported: * Explain the bug(s) vxlan and erspan are already supported for flower to allow flower to match vxlan and erspan options. It needs to support vxlan and erspan to act_tunnel_key and related bug fixes for the sake of completeness and to avoid bug in the future. * Brief explanation of fixes Cherry-pick. No adaptation. Add vxlan/erspan support for act_tunnel_key and bug fixes. c96adff95619 cls_flower: call nla_ok() before nla_next() 8e1b3ac47866 net: sched: initialize with 0 before setting erspan md->u e20d4ff2acd7 net: sched: add erspan option support to act_tunnel_key fca3f91cc38a net: sched: add vxlan option support to act_tunnel_key * How to test For vxlan support: It is to allow setting vxlan options using the act_tunnel_key action. Different from geneve options, only one option can be set. And also, geneve options and vxlan options can't be set at the same time. gbp is the only param for vxlan options: # ip link add name vxlan0 type vxlan dstport 0 external # tc qdisc add dev eth0 ingress # tc filter add dev eth0 protocol ip parent : \ flower indev eth0 \ ip_proto udp \ action tunnel_key \ set src_ip 10.0.99.192 \ dst_ip 10.0.99.193 \ dst_port 6081 \ id 11 \ vxlan_opts 01020304 \ action mirred egress redirect dev vxlan0 For erspan support: It is to allow setting erspan options using the act_tunnel_key action. Different from geneve options, only one option can be set. And also, geneve options, vxlan options or erspan options can't be set at the same time. Options are expressed as ver:index:dir:hwid, when ver is set to 1, index will be applied while dir and hwid will be ignored, and when ver is set to 2, dir and hwid will be used while index will be ignored. # ip link add name erspan1 type erspan external # tc qdisc add dev eth0 ingress # tc filter add dev eth0 protocol ip parent : \ flower indev eth0 \ ip_proto udp \ action tunnel_key \ set src_ip 10.0.99.192 \ dst_ip 10.0.99.193 \ dst_port 6081 \ id 11 \ erspan_opts 1:2:0:0 \ action mirred egress redirect dev erspan1 * What it could break. Nothing. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2016829 Title: Completely support vxlan and erspan for flower Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the bug(s) vxlan and erspan are already supported for flower to allow flower to match vxlan and erspan options. It needs to support vxlan and erspan to act_tunnel_key and related bug fixes for the sake of completeness and to avoid bug in the future. * Brief explanation of fixes Cherry-pick. No adaptation. Add vxlan/erspan support for act_tunnel_key and bug fixes. c96adff95619 cls_flower: call nla_ok() before nla_next() 8e1b3ac47866 net: sched: initialize with 0 before setting erspan md->u e20d4ff2acd7 net: sched: add erspan option support to act_tunnel_key fca3f91cc38a net: sched: add vxlan option support to act_tunnel_key * How to test For vxlan support: It is to allow setting vxlan options using the act_tunnel_key action. Different from geneve options, only one option can be set. And also, geneve options and vxlan options can't be set at the same time. gbp is the only param for vxlan options: # ip link add name vxlan0 type vxlan dstport 0 external # tc qdisc add dev eth0 ingress # tc filter add dev eth0 protocol ip parent : \ flower indev eth0 \ ip_proto udp \ action tunnel_key \ set src_ip 10.0.99.192 \ dst_ip 10.0.99.193 \ dst_port 6081 \ id 11 \ vxlan_opts 01020304 \ action mirred egress redirect dev vxlan0 For erspan support: It is to allow setting erspan options using the act_tunnel_key action. Different from geneve options, only one option can be set. And also, geneve options, vxlan options or erspan options can't be set at the same time. Options are expressed as ver:index:dir:hwid, when ver is set to 1, index will be applied while dir and hwid will be ignored, and when ver is set to 2, dir and hwid will be used while index will be ignored. # ip link add name erspan1 type erspan e
[Kernel-packages] [Bug 2015833] Re: ubuntu_bpf/test_verifier failed on B-KVM (bounds check after 32-bit right shift with 64-bit input FAIL)
This issue exist in all bionic kernels: * bionic/linux-aws/4.15.0-1147.159 * bionic/linux-aws-fips/4.15.0-2083.89 * bionic/linux-azure-4.15/4.15.0-1158.173 * bionic/linux-azure-fips/4.15.0-2067.73 * bionic/linux-gcp-4.15/4.15.0-1142.158 * bionic/linux-gcp-fips/4.15.0-2051.56 * bionic/linux-oracle/4.15.0-1109.120 ** Tags added: aws azure fips gcp oracle -- 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/2015833 Title: ubuntu_bpf/test_verifier failed on B-KVM (bounds check after 32-bit right shift with 64-bit input FAIL) Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Bionic: Confirmed Bug description: This is not a regression, we don't test ubuntu_bpf on KVM kernels until we have openstack added recently. Test failed with: #435/u bounds check after 32-bit right shift with 64-bit input FAIL Unexpected error message! 0: (7a) *(u64 *)(r10 -8) = 0 1: (bf) r2 = r10 2: (07) r2 += -8 3: (18) r1 = 0x0 5: (85) call bpf_map_lookup_elem#1 6: (15) if r0 == 0x0 goto pc+6 R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R10=fp0 7: (b7) r1 = 2 8: (67) r1 <<= 31 9: (74) (u32) r1 >>= (u32) 31 10: (14) (u32) r1 -= (u32) 2 11: (0f) r0 += r1 math between map_value pointer and 4294967294 is not allowed #435/p bounds check after 32-bit right shift with 64-bit input FAIL Unexpected error message! 0: (7a) *(u64 *)(r10 -8) = 0 1: (bf) r2 = r10 2: (07) r2 += -8 3: (18) r1 = 0x9fe6065f4c00 5: (85) call bpf_map_lookup_elem#1 6: (15) if r0 == 0x0 goto pc+6 R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R10=fp0 7: (b7) r1 = 2 8: (67) r1 <<= 31 9: (74) (u32) r1 >>= (u32) 31 10: (14) (u32) r1 -= (u32) 2 11: (0f) r0 += r1 math between map_value pointer and 4294967294 is not allowed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2015833/+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 1960640] Re: ubuntu_bpf XDP failures on v4.15
This issue has been fixed in sru-20221114 * bionic/linux-aws/4.15.0-1147.159 * bionic/linux-aws-fips/4.15.0-2083.89 * bionic/linux-azure-4.15/4.15.0-1158.173 * bionic/linux-azure-fips/4.15.0-2067.73 * bionic/linux-gcp-4.15/4.15.0-1142.158 * bionic/linux-gcp-fips/4.15.0-2051.56 * bionic/linux-oracle/4.15.0-1109.120 And the test_verifier is now failing with bug 2015833. Closing this bug and remove hints. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Project changed: linux => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960640 Title: ubuntu_bpf XDP failures on v4.15 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: 2022.01.31/bionic/linux-azure-4.15/4.15.0-1131.144 test: ubuntu_bpf Several XDP failures: 14563 02:11:05 DEBUG| [stdout] #470/p XDP pkt read, pkt_end > pkt_data', good access OK 14564 02:11:05 DEBUG| [stdout] #471/p XDP pkt read, pkt_end > pkt_data', bad access 1 FAIL 14565 02:11:05 DEBUG| [stdout] Unexpected success to load! 14566 02:11:05 DEBUG| [stdout] 0: (61) r2 = *(u32 *)(r1 +0) 14567 02:11:05 DEBUG| [stdout] 1: (61) r3 = *(u32 *)(r1 +4) 14568 02:11:05 DEBUG| [stdout] 2: (bf) r1 = r2 14569 02:11:05 DEBUG| [stdout] 3: (07) r1 += 8 14570 02:11:05 DEBUG| [stdout] 4: (2d) if r3 > r1 goto pc+1 14571 02:11:05 DEBUG| [stdout] R1=pkt(id=0,off=8,r=0,imm=0) R2=pkt(id=0,off=0,r=0,imm=0) R3=pkt_end(id=0,off=0,imm=0) R10=fp0 14572 02:11:05 DEBUG| [stdout] 5: (05) goto pc+1 14573 02:11:05 DEBUG| [stdout] 7: (b7) r0 = 0 14574 02:11:05 DEBUG| [stdout] 8: (95) exit 14575 02:11:05 DEBUG| [stdout] 14576 02:11:05 DEBUG| [stdout] from 4 to 6: R1=pkt(id=0,off=8,r=9,imm=0) R2=pkt(id=0,off=0,r=9,imm=0) R3=pkt_end(id=0,off=0,imm=0) R10=fp0 14577 02:11:05 DEBUG| [stdout] 6: (79) r0 = *(u64 *)(r1 -8) 14578 02:11:05 DEBUG| [stdout] 7: (b7) r0 = 0 14579 02:11:05 DEBUG| [stdout] 8: (95) exit 14580 02:11:05 DEBUG| [stdout] processed 11 insns, stack depth 0 14581 02:11:05 DEBUG| [stdout] #472/p XDP pkt read, pkt_end > pkt_data', bad access 2 OK 14582 02:11:05 DEBUG| [stdout] #473/p XDP pkt read, pkt_data' < pkt_end, good access OK 14583 02:11:05 DEBUG| [stdout] #474/p XDP pkt read, pkt_data' < pkt_end, bad access 1 FAIL 14584 02:11:05 DEBUG| [stdout] Unexpected success to load! 14585 02:11:05 DEBUG| [stdout] 0: (61) r2 = *(u32 *)(r1 +0) 14586 02:11:05 DEBUG| [stdout] 1: (61) r3 = *(u32 *)(r1 +4) 14587 02:11:05 DEBUG| [stdout] 2: (bf) r1 = r2 14588 02:11:05 DEBUG| [stdout] 3: (07) r1 += 8 14589 02:11:05 DEBUG| [stdout] 4: (ad) if r1 < r3 goto pc+1 14590 02:11:05 DEBUG| [stdout] R1=pkt(id=0,off=8,r=0,imm=0) R2=pkt(id=0,off=0,r=0,imm=0) R3=pkt_end(id=0,off=0,imm=0) R10=fp0 14591 02:11:05 DEBUG| [stdout] 5: (05) goto pc+1 14592 02:11:05 DEBUG| [stdout] 7: (b7) r0 = 0 14593 02:11:05 DEBUG| [stdout] 8: (95) exit 14594 02:11:05 DEBUG| [stdout] 14595 02:11:05 DEBUG| [stdout] from 4 to 6: R1=pkt(id=0,off=8,r=9,imm=0) R2=pkt(id=0,off=0,r=9,imm=0) R3=pkt_end(id=0,off=0,imm=0) R10=fp0 14596 02:11:05 DEBUG| [stdout] 6: (79) r0 = *(u64 *)(r1 -8) 14597 02:11:05 DEBUG| [stdout] 7: (b7) r0 = 0 14598 02:11:05 DEBUG| [stdout] 8: (95) exit 14599 02:11:05 DEBUG| [stdout] processed 11 insns, stack depth 0 14600 02:11:05 DEBUG| [stdout] #475/p XDP pkt read, pkt_data' < pkt_end, bad access 2 OK 14601 02:11:05 DEBUG| [stdout] #476/p XDP pkt read, pkt_end < pkt_data', good access OK 14602 02:11:05 DEBUG| [stdout] #477/p XDP pkt read, pkt_end < pkt_data', bad access 1 OK 14603 02:11:05 DEBUG| [stdout] #478/p XDP pkt read, pkt_end < pkt_data', bad access 2 OK 14604 02:11:05 DEBUG| [stdout] #479/p XDP pkt read, pkt_data' >= pkt_end, good access OK 14605 02:11:05 DEBUG| [stdout] #480/p XDP pkt read, pkt_data' >= pkt_end, bad access 1 FAIL 14606 02:11:05 DEBUG| [stdout] Unexpected success to load! 14607 02:11:05 DEBUG| [stdout] 0: (61) r2 = *(u32 *)(r1 +0) 14608 02:11:05 DEBUG| [stdout] 1: (61) r3 = *(u32 *)(r1 +4) 14609 02:11:05 DEBUG| [stdout] 2: (bf) r1 = r2 14610 02:11:05 DEBUG| [stdout] 3: (07) r1 += 8 14611 02:11:05 DEBUG| [stdout] 4: (3d) if r1 >= r3 goto pc+1 14612 02:11:05 DEBUG| [stdout] R1=pkt(id=0,off=8,r=9,imm=0) R2=pkt(id=0,off=0,r=9,imm=0) R3=pkt_end(id=0,off=0,imm=0) R10=fp0 14613 02:11:05 DEB
[Kernel-packages] [Bug 1960640] [NEW] ubuntu_bpf XDP failures on v4.15
You have been subscribed to a public bug:
2022.01.31/bionic/linux-azure-4.15/4.15.0-1131.144
test: ubuntu_bpf
Several XDP failures:
14563 02:11:05 DEBUG| [stdout] #470/p XDP pkt read, pkt_end >
pkt_data', good access OK
14564 02:11:05 DEBUG| [stdout] #471/p XDP pkt read, pkt_end >
pkt_data', bad access 1 FAIL
14565 02:11:05 DEBUG| [stdout] Unexpected success to load!
14566 02:11:05 DEBUG| [stdout] 0: (61) r2 = *(u32 *)(r1 +0)
14567 02:11:05 DEBUG| [stdout] 1: (61) r3 = *(u32 *)(r1 +4)
14568 02:11:05 DEBUG| [stdout] 2: (bf) r1 = r2
14569 02:11:05 DEBUG| [stdout] 3: (07) r1 += 8
14570 02:11:05 DEBUG| [stdout] 4: (2d) if r3 > r1 goto pc+1
14571 02:11:05 DEBUG| [stdout] R1=pkt(id=0,off=8,r=0,imm=0)
R2=pkt(id=0,off=0,r=0,imm=0) R3=pkt_end(id=0,off=0,imm=0) R10=fp0
14572 02:11:05 DEBUG| [stdout] 5: (05) goto pc+1
14573 02:11:05 DEBUG| [stdout] 7: (b7) r0 = 0
14574 02:11:05 DEBUG| [stdout] 8: (95) exit
14575 02:11:05 DEBUG| [stdout]
14576 02:11:05 DEBUG| [stdout] from 4 to 6:
R1=pkt(id=0,off=8,r=9,imm=0) R2=pkt(id=0,off=0,r=9,imm=0)
R3=pkt_end(id=0,off=0,imm=0) R10=fp0
14577 02:11:05 DEBUG| [stdout] 6: (79) r0 = *(u64 *)(r1 -8)
14578 02:11:05 DEBUG| [stdout] 7: (b7) r0 = 0
14579 02:11:05 DEBUG| [stdout] 8: (95) exit
14580 02:11:05 DEBUG| [stdout] processed 11 insns, stack depth 0
14581 02:11:05 DEBUG| [stdout] #472/p XDP pkt read, pkt_end >
pkt_data', bad access 2 OK
14582 02:11:05 DEBUG| [stdout] #473/p XDP pkt read, pkt_data' <
pkt_end, good access OK
14583 02:11:05 DEBUG| [stdout] #474/p XDP pkt read, pkt_data' <
pkt_end, bad access 1 FAIL
14584 02:11:05 DEBUG| [stdout] Unexpected success to load!
14585 02:11:05 DEBUG| [stdout] 0: (61) r2 = *(u32 *)(r1 +0)
14586 02:11:05 DEBUG| [stdout] 1: (61) r3 = *(u32 *)(r1 +4)
14587 02:11:05 DEBUG| [stdout] 2: (bf) r1 = r2
14588 02:11:05 DEBUG| [stdout] 3: (07) r1 += 8
14589 02:11:05 DEBUG| [stdout] 4: (ad) if r1 < r3 goto pc+1
14590 02:11:05 DEBUG| [stdout] R1=pkt(id=0,off=8,r=0,imm=0)
R2=pkt(id=0,off=0,r=0,imm=0) R3=pkt_end(id=0,off=0,imm=0) R10=fp0
14591 02:11:05 DEBUG| [stdout] 5: (05) goto pc+1
14592 02:11:05 DEBUG| [stdout] 7: (b7) r0 = 0
14593 02:11:05 DEBUG| [stdout] 8: (95) exit
14594 02:11:05 DEBUG| [stdout]
14595 02:11:05 DEBUG| [stdout] from 4 to 6:
R1=pkt(id=0,off=8,r=9,imm=0) R2=pkt(id=0,off=0,r=9,imm=0)
R3=pkt_end(id=0,off=0,imm=0) R10=fp0
14596 02:11:05 DEBUG| [stdout] 6: (79) r0 = *(u64 *)(r1 -8)
14597 02:11:05 DEBUG| [stdout] 7: (b7) r0 = 0
14598 02:11:05 DEBUG| [stdout] 8: (95) exit
14599 02:11:05 DEBUG| [stdout] processed 11 insns, stack depth 0
14600 02:11:05 DEBUG| [stdout] #475/p XDP pkt read, pkt_data' <
pkt_end, bad access 2 OK
14601 02:11:05 DEBUG| [stdout] #476/p XDP pkt read, pkt_end <
pkt_data', good access OK
14602 02:11:05 DEBUG| [stdout] #477/p XDP pkt read, pkt_end <
pkt_data', bad access 1 OK
14603 02:11:05 DEBUG| [stdout] #478/p XDP pkt read, pkt_end <
pkt_data', bad access 2 OK
14604 02:11:05 DEBUG| [stdout] #479/p XDP pkt read, pkt_data' >=
pkt_end, good access OK
14605 02:11:05 DEBUG| [stdout] #480/p XDP pkt read, pkt_data' >=
pkt_end, bad access 1 FAIL
14606 02:11:05 DEBUG| [stdout] Unexpected success to load!
14607 02:11:05 DEBUG| [stdout] 0: (61) r2 = *(u32 *)(r1 +0)
14608 02:11:05 DEBUG| [stdout] 1: (61) r3 = *(u32 *)(r1 +4)
14609 02:11:05 DEBUG| [stdout] 2: (bf) r1 = r2
14610 02:11:05 DEBUG| [stdout] 3: (07) r1 += 8
14611 02:11:05 DEBUG| [stdout] 4: (3d) if r1 >= r3 goto pc+1
14612 02:11:05 DEBUG| [stdout] R1=pkt(id=0,off=8,r=9,imm=0)
R2=pkt(id=0,off=0,r=9,imm=0) R3=pkt_end(id=0,off=0,imm=0) R10=fp0
14613 02:11:05 DEBUG| [stdout] 5: (79) r0 = *(u64 *)(r1 -8)
14614 02:11:05 DEBUG| [stdout] 6: (b7) r0 = 0
14615 02:11:05 DEBUG| [stdout] 7: (95) exit
14616 02:11:05 DEBUG| [stdout]
14617 02:11:05 DEBUG| [stdout] from 4 to 6: safe
14618 02:11:05 DEBUG| [stdout] processed 9 insns, stack depth 0
Possible cause:
Insufficient/incorrect backport of commit 2fa7d94afc1a ("bpf: Fix the
off-by-two error in range markings") to v4.15.
Our v4.15 skips entirely test udpate because path does not match
(because oif later commit 48729226238d ("selftests: bpf: break up the
rest of test_verifier")).
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: ubuntu-kernel-tests
Importance: Undecided
Status: Fix Released
** Tags: 4.15 azure bionic sru-20220131 sru-20220221 ubuntu-bpf
--
ubuntu_bpf XDP fail
[Kernel-packages] [Bug 2016826] [NEW] Plugging in Corsair K55 keyboard often doesnt work
Public bug reported: Often, plugging in my corsair K55 keyboard won't work. Sometimes, it works, but for the most part, like 80% of the time, it doesn't. I've had this issue for a while now across different versions. When I plug it in, the lights on the keyboard 'freeze' (keyboard firmware issue?), and no input is received from the keyboard. It seems the black USB 2 ports seem to have this occur less frequently than the blue USB 3 port. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-raspi 6.2.0.1004.6 ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpeisach894 F wireplumber /dev/snd/controlC0: jpeisach894 F wireplumber /dev/snd/seq:jpeisach891 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 17 20:35:32 2023 ImageMediaBuild: 20230417 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller Lsusb: Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 013: ID 1b1c:1b3d Corsair Corsair Corsair Gaming K55 RGB Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:1600x900M@60 smsc95xx.macaddr=DC:A6:32:C9:FA:05 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=zstd dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-6.2.0-1004-raspi N/A linux-backports-modules-6.2.0-1004-raspi N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux-raspi StagingDrivers: bcm2835_isp bcm2835_codec bcm2835_v4l2 snd_bcm2835 bcm2835_mmal_vchiq vc_sm_cma rpivid_hevc UpgradeStatus: No upgrade log present (probably fresh install) acpidump: ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image lunar raspi-image staging wayland-session ** Summary changed: - Plugging in Corsair K55 often doesnt work + Plugging in Corsair K55 keyboard often doesnt work -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2016826 Title: Plugging in Corsair K55 keyboard often doesnt work Status in linux-raspi package in Ubuntu: New Bug description: Often, plugging in my corsair K55 keyboard won't work. Sometimes, it works, but for the most part, like 80% of the time, it doesn't. I've had this issue for a while now across different versions. When I plug it in, the lights on the keyboard 'freeze' (keyboard firmware issue?), and no input is received from the keyboard. It seems the black USB 2 ports seem to have this occur less frequently than the blue USB 3 port. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-raspi 6.2.0.1004.6 ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpeisach894 F wireplumber /dev/snd/controlC0: jpeisach894 F wireplumber /dev/snd/seq:jpeisach891 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 17 20:35:32 2023 ImageMediaBuild: 20230417 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller Lsusb: Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 013: ID 1b1c:1b3d Corsair Corsair Corsair Gaming K55 RGB Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:1600x900M@60 smsc95xx.macaddr=DC:A6:32:C9:FA:05 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 zswap.enabled=1 zswap.zpoo
[Kernel-packages] [Bug 2011616] Re: Connection timeout due to conntrack limits
This issue was originally reported on GKE and verified by the GKE team. We do not have reproduction steps. As it is a change from upstream and a simple constant change, and since it is has already been verified on GKE, I am verifying it on GCP by code inspection. ** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- 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 Committed 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 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
Hi Keng-Yu, In comment #4, you mentioned there was an improvement in the performance on the Sapphire Rapids CPU with HBM, how exactly did you quantify that? -- 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/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: New Status in linux source package in Lunar: Incomplete Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+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 2015307] Re: mmc: sdhci-of-dwcmshc: Add runtime PM operations for BlueField-3
** 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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2015307 Title: mmc: sdhci-of-dwcmshc: Add runtime PM operations for BlueField-3 Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed to avoid unnecessary eMMC GPIO toggling when eMMC is idle [Fix] The fix implements the runtime PM operations for BlueField-3 SoC to disable the card clock when idle. [Test Case] Same functionality and testing as on BlueField-1/2. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2015307/+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 2016706] Re: The 5.19 kernel backport is broken
btw this has been confirmed by many people, e.g:
https://communities.vmware.com/t5/VMware-Fusion-Discussions/EDITED-Workaround-for-Ubuntu-22-10-displaying-blank-screen-after/m-p/2954212
** 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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664781/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664779/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664780/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664777/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664778/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664775/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664776/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664774/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] PaInfo.txt
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664773/+files/PaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664772/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664771/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664770/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664769/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664767/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664768/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664766/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-13 (459 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
IwConfig:
lono wireless extensions.
ens160no wireless extensions.
MachineType: VMware, Inc. VMware20,1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill:
Tags: jammy
Uname: Linux 5.19.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
dmi.board.name: VBSA
dmi.board.vendor: VMware, Inc.
dmi.board.version: 1
dmi.chassis.type: 1
dmi.chassis.vendor: VMware, Inc.
dmi.chassis.version: VMware20,1
dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
dmi.product.family: VMware
dmi.product.name: VMware20,1
dmi.product.sku: 0001
dmi.product.version: 1
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] Re: The 5.19 kernel backport is broken
apport information
** Tags added: apport-collected jammy
** Description changed:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is necessary
for proper drivers to load. Because the backport misses all those other
changes it breaks PCI resource release for efifb and prevents specific
drivers (e.g. vmwgfx) from being loaded. It doesn't affect many other
arm64 systems because most arm64 system don't have dedicated PCI gpu's,
like vmwgfx is, which is presumably why it was missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
- To fix it either the above mentioned change needs to be backed out or
- the rest of the patches from that series needs to be backported as well.
+ To fix it either the above mentioned change needs to be backed out or the
rest of the patches from that series needs to be backported as well.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.4
+ Architecture: arm64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
+ CasperMD5CheckResult: pass
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-01-13 (459 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha arm64 (20220112)
+ IwConfig:
+ lono wireless extensions.
+
+ ens160no wireless extensions.
+ MachineType: VMware, Inc. VMware20,1
+ Package: linux (not installed)
+ ProcEnviron:
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
+ ProcFB:
+
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=cd59243b-41f9-4a96-9a57-315489304b3e ro console=tty0
console=ttyS0,115200n8 drm.debug=0x2 quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
+ RelatedPackageVersions:
+ linux-restricted-modules-5.19.0-38-generic N/A
+ linux-backports-modules-5.19.0-38-generic N/A
+ linux-firmware 20220329.git681281e4-0ubuntu3.12
+ RfKill:
+
+ Tags: jammy
+ Uname: Linux 5.19.0-38-generic aarch64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 03/31/2023
+ dmi.bios.vendor: VMware, Inc.
+ dmi.bios.version: VMW201.00V.21529217.BA64.2303311427
+ dmi.board.name: VBSA
+ dmi.board.vendor: VMware, Inc.
+ dmi.board.version: 1
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: VMware, Inc.
+ dmi.chassis.version: VMware20,1
+ dmi.modalias:
dmi:bvnVMware,Inc.:bvrVMW201.00V.21529217.BA64.2303311427:bd03/31/2023:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
+ dmi.product.family: VMware
+ dmi.product.name: VMware20,1
+ dmi.product.sku: 0001
+ dmi.product.version: 1
+ dmi.sys.vendor: VMware, Inc.
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2016706/+attachment/5664765/+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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Confirmed
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the back
[Kernel-packages] [Bug 2015292] Re: Missing ACPI device info in mlxbf_pka module
Using kernel 5.15.0-1015.17, BlueField ATF version: v2.2(release):4.0.2-12-gdc90016, BlueField UEFI version: 4.0.2-6-ge89d91b, BlueField BSP version: 4.0.2.12660 this issue has been fixed ** 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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2015292 Title: Missing ACPI device info in mlxbf_pka module Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Bluefield 3 ACPI/Window RAM configuration and related code is missing. This affects BF3 functionality w/ PKA Ring character devices being created correctly. [Fix] * Added ACPI config and code to detect BF3 hardware and provision the Ring devices correctly. [Test Case] * Tested on BF3 with mlxbf-pka module load and check the /dev/pka/ Ring char devices are created with correct number of entries. * Tested with "openssl speed -engine pka -async_jobs 8 rsa" and verified the performance number show the PKA acceleration in place. [Potential Regression] * This fix has been tested with varieties of BF3: MB and HB cards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2015292/+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 2016706] 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 2016706
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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Incomplete
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or
the rest of the patches from that series needs to be backported as
well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 2016706] [NEW] The 5.19 kernel backport is broken
Public bug reported:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on arm64.
The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic kernel
repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is necessary
for proper drivers to load. Because the backport misses all those other
changes it breaks PCI resource release for efifb and prevents specific
drivers (e.g. vmwgfx) from being loaded. It doesn't affect many other
arm64 systems because most arm64 system don't have dedicated PCI gpu's,
like vmwgfx is, which is presumably why it was missed.
Without the rest of the changes in that series efifb won't release BAR 2, which
results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first they
unload the legacy fb drivers, in this case efifb, and then they continue their
own initialization. In this case vmwgfx can't initialize because even though
efifb has been unloaded it never released the resource at BAR 2, so vmwgfx
can't claim it. Currently there's no mechanism in the kernel to reload the
original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or
the rest of the patches from that series needs to be backported as well.
** 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/2016706
Title:
The 5.19 kernel backport is broken
Status in linux package in Ubuntu:
Incomplete
Bug description:
The latest 5.19 backport which migrated from 22.10 to 22.04 is broken on
arm64. The kernel team decided to include the following change:
5e0137612430 ("video/aperture: Disable and unregister sysfb devices via
aperture helpers")
it's the change 89314ff239e1933357419fa91b20190150f114a8 in the kinetic
kernel repo.
This change was part of a much larger series that was making sure that
fb devices were properly releasing the pci resources which is
necessary for proper drivers to load. Because the backport misses all
those other changes it breaks PCI resource release for efifb and
prevents specific drivers (e.g. vmwgfx) from being loaded. It doesn't
affect many other arm64 systems because most arm64 system don't have
dedicated PCI gpu's, like vmwgfx is, which is presumably why it was
missed.
Without the rest of the changes in that series efifb won't release BAR 2,
which results in :
vmwgfx :00:0f.0 BAR 2: can't reserve [mem 0x700-0x77ff 64bit pref]
and a black screen on boot. Because the way drm drivers work is that first
they unload the legacy fb drivers, in this case efifb, and then they continue
their own initialization. In this case vmwgfx can't initialize because even
though efifb has been unloaded it never released the resource at BAR 2, so
vmwgfx can't claim it. Currently there's no mechanism in the kernel to reload
the original generic fb driver in case the specific gpu driver fails the
initialization. This results in black screen on booth with vmware hypervisor on
arm64 and Ubuntu's 5.19 kernel.
To fix it either the above mentioned change needs to be backed out or
the rest of the patches from that series needs to be backported as
well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016706/+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 1892860] Re: af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B/F/J
Ran into this on the 2023-03-20 cycle:
SRU Cycle: 2023.03.20
Series: focal
Package:linux-hwe-5.15
Version:5.15.0-70.77~20.04.1
Cloud: metal
Instance: howzit-kernel
Region: serverenablement
Operation: sru
** Tags added: sru-20230320
--
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/1892860
Title:
af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on
B/F/J
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
Issue found on 4.15.0-114.115-generic with ARM64 node appleton-kernel
and wright-kernel.
Looks like this is a new test case added 13 days ago:
https://github.com/linux-test-project/ltp/commit/fdff6139e43aa9b19f27907f6d7f2cb4765632a1#diff-8a83d6b2c6c7d74e750e3af47e3f4a79
The test will fail with:
startup='Fri Aug 14 10:13:27 2020'
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
tst_taint.c:88: CONF: Ignoring already set kernel warning taint
../../../include/tst_fuzzy_sync.h:507: INFO: Minimum sampling period ended
../../../include/tst_fuzzy_sync.h:331: INFO: loop = 1024, delay_bias = 0
../../../include/tst_fuzzy_sync.h:320: INFO: start_a - start_b: { avg =
-2259470ns, avg_dev = 13695382ns, dev_ratio = 6.06 }
../../../include/tst_fuzzy_sync.h:320: INFO: end_a - start_a : { avg =
13968ns, avg_dev = 4310ns, dev_ratio = 0.31 }
../../../include/tst_fuzzy_sync.h:320: INFO: end_b - start_b : { avg =
15975ns, avg_dev = 50ns, dev_ratio = 0.00 }
../../../include/tst_fuzzy_sync.h:320: INFO: end_a - end_b : { avg =
-2261477ns, avg_dev = 13699742ns, dev_ratio = 6.06 }
../../../include/tst_fuzzy_sync.h:320: INFO: spins : { avg = 3575095 ,
avg_dev = 4553 , dev_ratio = 0.00 }
../../../include/tst_fuzzy_sync.h:637: INFO: Exceeded execution time,
requesting exit
af_alg07.c:97: FAIL: fchownat() failed to fail, kernel may be vulnerable
HINT: You _MAY_ be missing kernel fixes, see:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9060cb719e61
HINT: You _MAY_ be vulnerable to CVE(s), see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8912
Summary:
passed 0
failed 1
skipped 1
warnings 0
tag=af_alg07 stime=159747 dur=150 exit=exited stat=33 core=no cu=15051
cs=0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892860/+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 2016388] Re: Kernel Panic on powerdown on NUC8I3BEH1
I was unable to go back to an older version of the BIOS; both BE0088 and BE0089 resulted in the following error: "Incompatible BIOS version, Update Aborted!" This happened both using the built in UEFI BIOS update option and running IFLASH2 in FreeDOS booting in legacy mode. -- 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/2016388 Title: Kernel Panic on powerdown on NUC8I3BEH1 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016700] Re: Add support for X13s wifi
With that commit:
$ strings /lib/firmware/ath11k/WCN6855/hw2.0/board-2.bin | grep -i x13s
bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=2,qmi-board-id=140,variant=LE_X13Smm
bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=18,qmi-board-id=140,variant=LE_X13Sm
bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=2,qmi-board-id=140,variant=LE_X13Smm
bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=18,qmi-board-id=140,variant=LE_X13Sm
** Description changed:
- The Lenovo X13s needs an updated ath11k board-2.bin file.
+ [Impact]
+
+ Wifi on a Lenovo X13s is not coming up. The board ID is unknown.
+
+ [Fix]
+
+ Uptream commit d1dc30480fef ("ath11k: WCN6855 hw2.0: update
+ board-2.bin")
+
+ [Test Case]
+
+ Check that wifi comes up.
+
+ [Where Problems Could Occur]
+
+ ath11k based machines could experince Wifi issues if that upstream
+ binary is broken.
--
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/2016700
Title:
Add support for X13s wifi
Status in linux-firmware package in Ubuntu:
New
Status in linux-firmware source package in Lunar:
New
Bug description:
[Impact]
Wifi on a Lenovo X13s is not coming up. The board ID is unknown.
[Fix]
Uptream commit d1dc30480fef ("ath11k: WCN6855 hw2.0: update
board-2.bin")
[Test Case]
Check that wifi comes up.
[Where Problems Could Occur]
ath11k based machines could experince Wifi issues if that upstream
binary is broken.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2016700/+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 2007857] Re: 5.19.0-1007-allwinner: screen buffer not completely displayed
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2007857 ** Tags added: iso-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner in Ubuntu. https://bugs.launchpad.net/bugs/2007857 Title: 5.19.0-1007-allwinner: screen buffer not completely displayed Status in linux-allwinner package in Ubuntu: New Bug description: I have installed the Kinetic preinstalled image on the Nezha board and upgraded it. With the 5.19 kernel the HDMI console output uses a larger font. Not all columns and not all lines of the screen buffer are visible. So when reaching the lower end of the HDMI output you start typing in the dark. At least 20 lines of output are invisible. At least 80 columns on the right side are not displayed. This renders the HDMI console unusable. $ cat /sys/class/drm/card0-HDMI-A-1/modes 1024x768 800x600 800x600 848x480 640x480 The 1920x1080 mode is not displayed. The screen is actually running in 1024x768 mode while the screen buffer assumes 1920x1080. With the 5.17 allwinner kernel the problem did not exist. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-1007-allwinner 5.19.0-1007.7 ProcVersionSignature: Ubuntu 5.19.0-1007.7-allwinner 5.19.17 Uname: Linux 5.19.0-1007-allwinner riscv64 ApportVersion: 2.23.1-0ubuntu3 Architecture: riscv64 CasperMD5CheckResult: unknown Date: Mon Feb 20 14:21:12 2023 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-allwinner UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: riscv64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 Package: linux-allwinner 5.19.0.1007.7 PackageArchitecture: riscv64 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.19.0-1007.7-allwinner 5.19.17 Tags: kinetic uec-images Uname: Linux 5.19.0-1007-allwinner riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2007857/+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 2015307] Re: mmc: sdhci-of-dwcmshc: Add runtime PM operations for BlueField-3
This bug is awaiting verification that the linux- bluefield/5.15.0-1015.17 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: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2015307 Title: mmc: sdhci-of-dwcmshc: Add runtime PM operations for BlueField-3 Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed to avoid unnecessary eMMC GPIO toggling when eMMC is idle [Fix] The fix implements the runtime PM operations for BlueField-3 SoC to disable the card clock when idle. [Test Case] Same functionality and testing as on BlueField-1/2. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2015307/+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 2015292] Re: Missing ACPI device info in mlxbf_pka module
This bug is awaiting verification that the linux- bluefield/5.15.0-1015.17 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: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2015292 Title: Missing ACPI device info in mlxbf_pka module Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Bluefield 3 ACPI/Window RAM configuration and related code is missing. This affects BF3 functionality w/ PKA Ring character devices being created correctly. [Fix] * Added ACPI config and code to detect BF3 hardware and provision the Ring devices correctly. [Test Case] * Tested on BF3 with mlxbf-pka module load and check the /dev/pka/ Ring char devices are created with correct number of entries. * Tested with "openssl speed -engine pka -async_jobs 8 rsa" and verified the performance number show the PKA acceleration in place. [Potential Regression] * This fix has been tested with varieties of BF3: MB and HB cards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2015292/+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 2016700] [NEW] Add support for X13s wifi
Public bug reported: The Lenovo X13s needs an updated ath11k board-2.bin file. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New -- 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/2016700 Title: Add support for X13s wifi Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Lunar: New Bug description: The Lenovo X13s needs an updated ath11k board-2.bin file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2016700/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@giuliano69 So, "modinfo uvcvideo" output is attached and "sudo modprobe uvcvideo -vv" output is: modprobe: INFO: ../libkmod/libkmod.c:367 kmod_set_log_fn() custom logging function 0x55c27ec1c830 registered insmod /lib/modules/5.15.0-69-generic/kernel/drivers/media/usb/uvc/uvcvideo.ko modprobe: INFO: ../libkmod/libkmod-module.c:892 kmod_module_insert_module() Failed to insert module '/lib/modules/5.15.0-69-generic/kernel/drivers/media/usb/uvc/uvcvideo.ko': Exec format error modprobe: ERROR: could not insert 'uvcvideo': Exec format error modprobe: INFO: ../libkmod/libkmod.c:334 kmod_unref() context 0x55c28075a4a0 released ** Attachment added: "modinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000947/+attachment/5664731/+files/modinfo.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/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:
[Kernel-packages] [Bug 2011738] Re: Add ATX related reporting nodes in mlxbf-ptm debugfs driver
This bug is awaiting verification that the linux- bluefield/5.15.0-1015.17 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: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2011738 Title: Add ATX related reporting nodes in mlxbf-ptm debugfs driver Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] mlxbf-ptm is a kernel driver that provides debufgs interface for system software to monitor Bluefield devices' power and thermal management parameters. [Fix] * This change adds additional debugfs nodes that provide ATX status and power profile data. Replaces S_IRUGO with 0444 inline with checkpatch expectation. [Test Case] * After installing the kernel module, debugfs entry at /sys/kernel/debug/mlxbf-ptm will be created * monitors/status folder contains read-only parameters reported from the Bluefield device [Regression Potential] * Minimal - as these are read-only parameters that report Bluefield device information. [Other] * This code is likely to change depending on feedback we received from maintainers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2011738/+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 2012649] Re: mlxbf_gige: need to replace SAUCE patches with upstream commits
This bug is awaiting verification that the linux-
bluefield/5.15.0-1015.17 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: verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2012649
Title:
mlxbf_gige: need to replace SAUCE patches with upstream commits
Status in linux-bluefield package in Ubuntu:
Invalid
Status in linux-bluefield source package in Jammy:
Fix Committed
Bug description:
SRU Justification:
[Impact]
The GIGE driver ("mlxbf_gige") in the Jammy repo contains SAUCE
patches that enable BlueField-3 support. This same functionality
is contained in upstream commits and Jammy repo should utilize them.
[Fix]
The BlueField-3 support will be provided in the form of a set
of upstream patches, to be sent in as a pull request.
[Test Case]
Should test on both BlueField-2 & BlueField-3:
Boot platform and bring up "oob_net0" interface properly
Test that network traffic works properly
[Regression Potential]
The upstream commits have been reviewed and tested well,
so there should be low risk of regression.
[Other]
n/a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2012649/+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 2012743] Re: Support Nvidia BlueField-3 GPIO driver and pin controller
This bug is awaiting verification that the linux- bluefield/5.15.0-1015.17 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: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2012743 Title: Support Nvidia BlueField-3 GPIO driver and pin controller Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Support the BlueField-3 SoC GPIO driver for handling interrupts and providing the option to change the direction and value of a GPIO. Support the BlueField-3 SoC pin controller driver for allowing a select number of GPIO pins to be manipulated from userspace or the kernel. All these changes have been accepted for upstream but most of them are not yet in the tree/branches. PLEASE NOTE: This change is dependent on changes done in the ACPI tables. So the UEFI image needs to be updated accordingly. [Fix] * Add support for the BlueField-3 SoC GPIO driver. This driver configures and handles GPIO interrupts. It also enables a user to manipulate certain GPIO pins via libgpiod tools or other kernel drivers. The usable pins are defined via the "gpio-reserved-ranges" property. * NVIDIA BlueField-3 SoC has a few pins that can be used as GPIOs or take the default hardware functionality. Add a driver for the pin muxing. * The following gpiolib commits are bug fixes and are required for the gpio driver to work: 443a0a0f0cf4f432c7af6654b7f2f920d411d379 Although the following have been accepted by maintainers, they are not present in any tree/branch yet so these will be pushed as SAUCE for now: [PATCH v4] gpio: mmio: handle "ngpios" properly in bgpio_init() [PATCH v1] gpio: mmio: fix calculation of bgpio_bits [Test Case] * Check if the gpio-mlxbf3 driver is loaded * Check if the pinctrl-mlxbf3 driver is loaded * check if the mlxbf-gige driver is loaded * check if the pwr-mlxbf driver is loaded * Check that the oob_net0 interface is up and operational * Do reset and powercycle and check the oob_net0 interface again * Test power GPIO interrupt on BF3. [Regression Potential] * The Mellanox drivers could fail to be loaded. * The mlxbf-gige PHY interrupt or pwr-mlxbf interrupt could fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2012743/+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 2013383] Re: mlxbf-bootctl: support SMC call for setting ARM boot state
This bug is awaiting verification that the linux- bluefield/5.15.0-1015.17 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: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2013383 Title: mlxbf-bootctl: support SMC call for setting ARM boot state Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: In Progress Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Add a new SMC call which allows setting the ARM boot progress state to "OS is up". [Fix] * Add a new SMC call in mlxbf-bootctl which allows setting the ARM boot progress state to "OS is up". [Test Case] * Check that /sys/devices/platform/MLNXBF04:00/driver/os_up exists [Regression Potential] * No known regression because it is just adding a sysfs entry. It is backward compatible with older TAF images. If the SMC call is not supported by ATF, it is ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2013383/+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 2013743] Re: USB not working on Nezha D1
Kernel 5.19.0-1009-allwinner does not show this issue. ** Changed in: linux-allwinner (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner in Ubuntu. https://bugs.launchpad.net/bugs/2013743 Title: USB not working on Nezha D1 Status in linux-allwinner package in Ubuntu: Fix Released Bug description: I am testing the Allwinner Nezha D1 board according to http://iso.qa.ubuntu.com/qatracker/milestones/444/builds/275098/testcases/1755/results Hitting a key on the USB keyboard (that was plugged in at boot) results in [ 760.275027] usb 3-1: device descriptor read/64, error -71 [ 761.671031] usb 1-1: device descriptor read/64, error -62 [ 761.975011] usb 1-1: device descriptor read/64, error -62 [ 762.466981] usb 1-1: device descriptor read/64, error -62 [ 762.770995] usb 1-1: device descriptor read/64, error -62 [ 763.514994] usb 1-1: device not accepting address 17, error -62 [ 764.122989] usb 1-1: device not accepting address 18, error -62 [ 764.129829] usb usb1-port1: unable to enumerate USB device lsusb does not show the keyboard: $ lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3 ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7 Uname: Linux 5.19.0-1003-allwinner riscv64 ApportVersion: 2.26.0-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230329 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Mar 31 14:31:08 2023 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-allwinner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2013743/+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 2015476] Re: Jammy update: v6.1.23 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid -- 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/2015476 Title: Jammy update: v6.1.23 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 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: v6.1.23 upstream stable release from git://git.kernel.org/ Linux 6.1.23 Revert "cpuidle, intel_idle: Fix CPUIDLE_FLAG_IRQ_ENABLE *again*" x86/PVH: avoid 32-bit build warning when obtaining VGA console info hsr: ratelimit only when errors are printed drm/amdkfd: Get prange->offset after svm_range_vram_node_new usb: ucsi: Fix ucsi->connector race libbpf: Fix btf_dump's packed struct determination selftests/bpf: Add few corner cases to test padding handling of btf_dump libbpf: Fix BTF-to-C converter's padding logic selftests/bpf: Test btf dump for struct with padding only fields net: dsa: mv88e6xxx: replace VTU violation prints with trace points net: dsa: mv88e6xxx: replace ATU violation prints with trace points net: dsa: mv88e6xxx: read FID when handling ATU violations KVM: arm64: Disable interrupts while walking userspace PTs KVM: arm64: PMU: Fix GET_ONE_REG for vPMC regs to return the current value drm/i915: Move CSC load back into .color_commit_arm() when PSR is enabled on skl/glk drm/i915: Disable DC states for all commits drm/i915/dpt: Treat the DPT BO as a framebuffer drm/i915/gem: Flush lmem contents after construction drm/amd/display: Take FEC Overhead into Timeslot Calculation drm/amd/display: Add DSC Support for Synaptics Cascaded MST Hub drm/amdgpu: allow more APUs to do mode2 reset when go to S4 drm/etnaviv: fix reference leak when mmaping imported buffer s390: reintroduce expoline dependence to scripts s390/uaccess: add missing earlyclobber annotations to __clear_user() dt-bindings: mtd: jedec,spi-nor: Document CPOL/CPHA support rcu: Fix rcu_torture_read ftrace event xtensa: fix KASAN report for show_stack ALSA: hda/realtek: Add quirk for Lenovo ZhaoYang CF4620Z ALSA: hda/realtek: Add quirks for some Clevo laptops ALSA: usb-audio: Fix regression on detection of Roland VS-100 ALSA: hda/conexant: Partial revert of a quirk for Lenovo NFSv4: Fix hangs when recovering open state after a server reboot powerpc/64s: Fix __pte_needs_flush() false positive warning powerpc/pseries/vas: Ignore VAS update for DLPAR if copy/paste is not enabled powerpc: Don't try to copy PPR for task with NULL pt_regs platform/x86: ideapad-laptop: Stop sending KEY_TOUCHPAD_TOGGLE pinctrl: at91-pio4: fix domain name assignment pinctrl: amd: Disable and mask interrupts on resume modpost: Fix processing of CRCs on 32-bit build machines net: phy: dp83869: fix default value for tx-/rx-internal-delay xen/netback: don't do grant copy across page boundary can: j1939: prevent deadlock by moving j1939_sk_errqueue() dm: fix __send_duplicate_bios() to always allow for splitting IO zonefs: Always invalidate last cached page on append write vmxnet3: use gro callback when UPT is enabled io_uring: fix poll/netmsg alloc caches io_uring/rsrc: fix rogue rsrc node grabbing io_uring/poll: clear single/double poll flags on poll arming block/io_uring: pass in issue_flags for uring_cmd task_work handling zonefs: Do not propagate iomap_dio_rw() ENOTBLK error to user space btrfs: scan device in non-exclusive mode btrfs: fix race between quota disable and quota assign ioctls btrfs: fix deadlock when aborting transaction during relocation with scrub Input: goodix - add Lenovo Yoga Book X90F to nine_bytes_report DMI table Input: i8042 - add quirk for Fujitsu Lifebook A574/H cifs: fix DFS traversal oops without CONFIG_CIFS_DFS_UPCALL cifs: prevent infinite recursion in CIFSGetDFSRefer() Input: focaltech - use explicitly signed char type Input: alps - fix compatibility with -funsigned-char Input: i8042 - add TUXEDO devices to i8042 quirk tables for partial fix iommu/vt-d: Allow zero SAGAW if second-stage not supported Input: xpad - fix incorrectly applied patch for MAP_PROFILE_BUTTON pinctrl: ocelot: Fix alt mode for ocelot net: ethernet: mtk_eth_soc: add missing ppe cache flush when deleting a flow net: ethernet: mtk_et
[Kernel-packages] [Bug 2016470] Re: Jammy update: v6.1.24 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed -- 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/2016470 Title: Jammy update: v6.1.24 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 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: v6.1.24 upstream stable release from git://git.kernel.org/ Linux 6.1.24 bpftool: Print newline before '}' for struct with padding only fields mm: enable maple tree RCU mode by default. maple_tree: add RCU lock checking to rcu callback functions maple_tree: add smp_rmb() to dead node detection maple_tree: remove extra smp_wmb() from mas_dead_leaves() maple_tree: fix freeing of nodes in rcu mode maple_tree: detect dead nodes in mas_start() maple_tree: refine ma_state init from mas_start() maple_tree: be more cautious about dead nodes maple_tree: fix mas_prev() and mas_find() state handling maple_tree: fix handle of invalidated state in mas_wr_store_setup() maple_tree: reduce user error potential maple_tree: fix potential rcu issue maple_tree: remove GFP_ZERO from kmem_cache_alloc() and kmem_cache_alloc_bulk() mm: take a page reference when removing device exclusive entries drm/i915: Split icl_color_commit_noarm() from skl_color_commit_noarm() drm/i915: Use _MMIO_PIPE() for SKL_BOTTOM_COLOR drm/bridge: lt9611: Fix PLL being unable to lock drm/i915/dp_mst: Fix payload removal during output disabling drm/display/dp_mst: Handle old/new payload states in drm_dp_remove_payload() drm/amdgpu: skip psp suspend for IMU enabled ASICs mode2 reset drm/amdgpu: for S0ix, skip SDMA 5.x+ suspend/resume drm/amd/display: Clear MST topology if it fails to resume blk-throttle: Fix that bps of child could exceed bps limited in parent maple_tree: fix a potential concurrency bug in RCU mode maple_tree: fix get wrong data_end in mtree_lookup_walk() mm/hugetlb: fix uffd wr-protection for CoW optimization path mm/swap: fix swap_info_struct race between swapoff and get_swap_pages() ring-buffer: Fix race while reader and writer are on the same page drm/i915: fix race condition UAF in i915_perf_add_config_ioctl drm/i915: Fix context runtime accounting drm/nouveau/disp: Support more modes by checking with lower bpc drm/panfrost: Fix the panfrost_mmu_map_fault_addr() error path ublk: read any SQE values upfront wifi: mt76: ignore key disable commands mm: vmalloc: avoid warn_alloc noise caused by fatal signal zsmalloc: document freeable stats tracing/synthetic: Make lastcmd_mutex static ASoC: hdac_hdmi: use set_stream() instead of set_tdm_slots() tracing: Free error logs of tracing instances tracing/osnoise: Fix notify new tracing_max_latency tracing/timerlat: Notify new max thread latency tracing/synthetic: Fix races on freeing last_cmd net: stmmac: Add queue reset into stmmac_xdp_open() function ACPI: video: Add acpi_backlight=video quirk for Lenovo ThinkPad W530 ACPI: video: Add acpi_backlight=video quirk for Apple iMac14,1 and iMac14,2 ACPI: video: Make acpi_backlight=video work independent from GPU driver ACPI: video: Add auto_detect arg to __acpi_video_get_backlight_type() can: isotp: isotp_recvmsg(): use sock_recv_cmsgs() to get SOCK_RXQ_OVFL infos can: isotp: isotp_ops: fix poll() to not report false EPOLLOUT events can: isotp: fix race between isotp_sendsmg() and isotp_release() can: j1939: j1939_tp_tx_dat_new(): fix out-of-bounds memory access fs: drop peer group ids under namespace lock ftrace: Fix issue that 'direct->addr' not restored in modify_ftrace_direct() ftrace: Mark get_lock_parent_ip() __always_inline perf/core: Fix the same task check in perf_event_set_output block: don't set GD_NEED_PART_SCAN if scan partition failed block: ublk: make sure that block size is set correctly cifs: sanitize paths in cifs_update_super_prepath. nvme: fix discard support without oncs scsi: iscsi_tcp: Check that sock is valid before iscsi_set_param() scsi: qla2xxx: Fix memory leak in qla2x00_probe_one() io_uring: fix memory leak when removing provided buffers io_uring: fix return value when removing provided buffers iio: adc: ad7791: fix IRQ flags blk-mq: directly poll requests counter: 104-quad-8: Fix
[Kernel-packages] [Bug 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
** Changed in: linux (Ubuntu Kinetic) 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/1893921 Title: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Confirmed Bug description: Testing failed on: s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200901_162956_a95df@/log.gz The ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x: 15:45:23 DEBUG| [stdout] # selftests: net: rtnetlink.sh 15:45:23 DEBUG| [stdout] # PASS: policy routing 15:45:23 DEBUG| [stdout] # PASS: route get 15:45:28 DEBUG| [stdout] # PASS: preferred_lft addresses have expired 15:45:28 DEBUG| [stdout] # PASS: promote_secondaries complete 15:45:28 DEBUG| [stdout] # PASS: tc htb hierarchy 15:45:29 DEBUG| [stdout] # PASS: gre tunnel endpoint 15:45:29 DEBUG| [stdout] # PASS: gretap 15:45:29 DEBUG| [stdout] # PASS: ip6gretap 15:45:29 DEBUG| [stdout] # PASS: erspan 15:45:29 DEBUG| [stdout] # PASS: ip6erspan 15:45:30 DEBUG| [stdout] # PASS: bridge setup 15:45:31 DEBUG| [stdout] # PASS: ipv6 addrlabel 15:45:31 DEBUG| [stdout] # PASS: set ifalias b14b1d80-dc0b-4a9b-9256-3ec3f86aa891 for test-dummy0 15:45:31 DEBUG| [stdout] # PASS: vrf 15:45:31 DEBUG| [stdout] # PASS: vxlan 15:45:31 DEBUG| [stdout] # FAIL: can't add fou port , skipping test 15:45:31 DEBUG| [stdout] # PASS: macsec 15:45:32 DEBUG| [stdout] # PASS: ipsec 15:45:33 DEBUG| [stdout] # 3,7c3,7 15:45:33 DEBUG| [stdout] # < sa[0]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[0]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # < sa[1] rx ipaddr=0x c0a87b03 15:45:33 DEBUG| [stdout] # < sa[1]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[1]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # --- 15:45:33 DEBUG| [stdout] # > sa[0]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[0]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # > sa[1] rx ipaddr=0x 037ba8c0 15:45:33 DEBUG| [stdout] # > sa[1]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[1]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload incorrect driver data 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload 15:45:33 DEBUG| [stdout] # PASS: bridge fdb get 15:45:33 DEBUG| [stdout] # PASS: neigh get 15:45:33 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+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 1999589] Re: net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x Kinetic
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) 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/1999589 Title: net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x Kinetic Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Confirmed Bug description: All of the sm4* ciper testcases are failing in net:tls for kinetic linux 5.19.0-27.28 These seem like new testcases that have not been run before. and this has only been seen as far as I am aware of on s390x - 21:31:48 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendfile ... 21:31:48 DEBUG| [stdout] # # tls.c:314:sendfile:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # sendfile: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendfile 21:31:49 DEBUG| [stdout] # not ok 197 tls.13_sm4_gcm.sendfile 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.send_then_sendfile ... 21:31:49 DEBUG| [stdout] # # tls.c:314:send_then_sendfile:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # send_then_sendfile: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.send_then_sendfile 21:31:49 DEBUG| [stdout] # not ok 198 tls.13_sm4_gcm.send_then_sendfile 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.recv_max ... 21:31:49 DEBUG| [stdout] # # tls.c:314:recv_max:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # recv_max: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.recv_max 21:31:49 DEBUG| [stdout] # not ok 199 tls.13_sm4_gcm.recv_max 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.recv_small ... 21:31:49 DEBUG| [stdout] # # tls.c:314:recv_small:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # recv_small: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.recv_small 21:31:49 DEBUG| [stdout] # not ok 200 tls.13_sm4_gcm.recv_small 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.msg_more ... 21:31:49 DEBUG| [stdout] # # tls.c:314:msg_more:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # msg_more: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.msg_more 21:31:49 DEBUG| [stdout] # not ok 201 tls.13_sm4_gcm.msg_more 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.msg_more_unsent ... 21:31:49 DEBUG| [stdout] # # tls.c:314:msg_more_unsent:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # msg_more_unsent: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.msg_more_unsent 21:31:49 DEBUG| [stdout] # not ok 202 tls.13_sm4_gcm.msg_more_unsent 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_single ... 21:31:49 DEBUG| [stdout] # # tls.c:314:sendmsg_single:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_single: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_single 21:31:50 DEBUG| [stdout] # not ok 203 tls.13_sm4_gcm.sendmsg_single 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_fragmented ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_fragmented:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_fragmented: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_fragmented 21:31:50 DEBUG| [stdout] # not ok 204 tls.13_sm4_gcm.sendmsg_fragmented 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_large ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_large:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_large: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_large 21:31:50 DEBUG| [stdout] # not ok 205 tls.13_sm4_gcm.sendmsg_large 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_multiple ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_multiple:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_multiple: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_multiple 21:31:50 DEBUG| [stdout] # not ok 206 tls.13_sm4_gcm.sendmsg_multiple 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_multiple_stress ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_multiple_stress:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_multiple_stress: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_multiple_stres
[Kernel-packages] [Bug 2009024] Re: Fail to output sound to external monitor which connects via docking station
** 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-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 Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed 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: [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 1923683] Re: ftrace from ubuntu_kernel_selftests failed with "test for function event triggers" on F/G/H/I
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Kinetic)
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/1923683
Title:
ftrace from ubuntu_kernel_selftests failed with "test for function
event triggers" on F/G/H/I
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Confirmed
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
Won't Fix
Status in linux source package in Impish:
Won't Fix
Status in linux source package in Kinetic:
Confirmed
Bug description:
ftrace from ubuntu_kernel_selftests failed with "test for function
event triggers" on Groovy riscv 5.8.0-21.23
This test was recently added, not considering a regression
Log is getting cut off from regression test report. the below is all
that could be retrieved at the moment:
04/13 23:48:00 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 >
/proc/sys/net/ipv4/conf/all/accept_local''
04/13 23:48:00 DEBUG| utils:0116| Running 'sudo make -C
linux/tools/testing/selftests TARGETS=ftrace run_tests'
04/13 23:48:00 DEBUG| utils:0153| [stdout] make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
04/13 23:48:01 DEBUG| utils:0153| [stdout] make --no-builtin-rules
ARCH=riscv -C ../../.. headers_install
04/13 23:48:01 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
04/13 23:48:14 DEBUG| utils:0153| [stdout] INSTALL ./usr/include
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done
for 'all'.
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:16 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:16 DEBUG| utils:0153| [stdout] TAP version 13
04/13 23:48:16 DEBUG| utils:0153| [stdout] 1..1
04/13 23:48:16 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Setting locale
failed.
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Please check
that your locale settings:
04/13 23:48:16 ERROR| utils:0153| [stderr]LANGUAGE = (unset),
04/13 23:48:16 ERROR| utils:0153| [stderr]LC_ALL = (unset),
04/13 23:48:16 ERROR| utils:0153| [stderr]LC_CTYPE = "C.UTF-8",
04/13 23:48:16 ERROR| utils:0153| [stderr]LANG = "en_US.UTF-8"
04/13 23:48:16 ERROR| utils:0153| [stderr] are supported and
installed on your system.
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Falling back to
the standard locale ("C").
04/13 23:48:17 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
04/13 23:48:21 DEBUG| utils:0153| [stdout] # [1] Basic trace file check
[PASS]
04/13 23:49:02 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers
[PASS]
04/13 23:49:09 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test
[PASS]
04/13 23:49:13 DEBUG| utils:0153| [stdout] # [4] Basic event tracing
check[PASS]
04/13 23:49:18 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer
size [PASS]
04/13 23:49:23 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing
setting [PASS]
04/13 23:49:27 DEBUG| utils:0153| [stdout] # [7] trace_pipe and
trace_marker [PASS]
04/13 23:49:32 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct
functions against tracers [UNRESOLVED]
04/13 23:49:33 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct
functions against kprobes [UNSUPPORTED]
04/13 23:49:37 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event -
add/remove kprobe events[FAIL]
04/13 23:49:37 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event -
add/remove synthetic events [UNSUPPORTED]
04/13 23:49:38 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event -
selective clear (compatibility) [UNSUPPORTED]
04/13 23:49:39 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event -
generic clear event [UNSUPPORTED]
04/13 23:49:44 DEBUG| utils:0153| [stdout
[Kernel-packages] [Bug 1950627] 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 1950627 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/1950627 Title: ubuntu_kernel_selftests:net:udpgro_fwd.sh: udpgso_bench_tx: sendmsg: Connection refused Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: This is from ADT testing (amd64) but I believe I occasionally saw this before. It feels like sometimes the receiver does not get ready before the transmission starts. IIRC this goes away when re-trying. 02:52:31 DEBUG| [stdout] # selftests: net: udpgro_fwd.sh 02:52:31 DEBUG| [stdout] # IPv4 02:52:31 DEBUG| [stdout] # No GRO ok 02:52:32 DEBUG| [stdout] # GRO frag listok 02:52:32 DEBUG| [stdout] # GRO fwd ok 02:52:33 DEBUG| [stdout] # UDP fwd perfudp rx: 333 MB/s 271894 calls/s 02:52:33 DEBUG| [stdout] # udp tx:378 MB/s 6422 calls/s 6422 msg/s 02:52:34 DEBUG| [stdout] # udp rx:383 MB/s 312480 calls/s 02:52:34 DEBUG| [stdout] # udp tx:383 MB/s 6506 calls/s 6506 msg/s 02:52:35 DEBUG| [stdout] # udp rx:381 MB/s 310202 calls/s 02:52:35 DEBUG| [stdout] # udp tx:380 MB/s 6458 calls/s 6458 msg/s 02:52:36 DEBUG| [stdout] # UDP GRO fwd perfudp rx: 344 MB/s 280814 calls/s 02:52:36 DEBUG| [stdout] # udp tx:389 MB/s 6612 calls/s 6612 msg/s 02:52:37 DEBUG| [stdout] # udp rx:364 MB/s 297088 calls/s 02:52:37 DEBUG| [stdout] # udp tx:383 MB/s 6512 calls/s 6512 msg/s 02:52:38 DEBUG| [stdout] # udp rx:448 MB/s 365435 calls/s 02:52:38 DEBUG| [stdout] # udp tx:453 MB/s 7686 calls/s 7686 msg/s 02:52:39 DEBUG| [stdout] # GRO frag list over UDP tunnelok 02:52:39 DEBUG| [stdout] # GRO fwd over UDP tunnel ok 02:52:39 DEBUG| [stdout] # UDP tunnel fwd perf ./udpgso_bench_tx: sendmsg: Connection refused 02:52:39 DEBUG| [stdout] # fail client exit code 1, server 0 02:52:40 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx: 236 MB/s 192389 calls/s 02:52:41 DEBUG| [stdout] # udp tx:284 MB/s 4826 calls/s 4826 msg/s 02:52:41 DEBUG| [stdout] # udp rx:295 MB/s 240586 calls/s 02:52:42 DEBUG| [stdout] # udp tx:306 MB/s 5206 calls/s 5206 msg/s 02:52:42 DEBUG| [stdout] # udp rx:306 MB/s 249784 calls/s 02:52:43 DEBUG| [stdout] # udp tx:310 MB/s 5263 calls/s 5263 msg/s 02:52:43 DEBUG| [stdout] # IPv6 02:52:43 DEBUG| [stdout] # No GRO ok 02:52:43 DEBUG| [stdout] # GRO frag listok 02:52:43 DEBUG| [stdout] # GRO fwd ok 02:52:44 DEBUG| [stdout] # UDP fwd perfudp rx: 82 MB/s66844 calls/s 02:52:45 DEBUG| [stdout] # udp tx:334 MB/s 5668 calls/s 5668 msg/s 02:52:45 DEBUG| [stdout] # udp rx:374 MB/s 305206 calls/s 02:52:46 DEBUG| [stdout] # udp tx:375 MB/s 6377 calls/s 6377 msg/s 02:52:46 DEBUG| [stdout] # udp rx:373 MB/s 303948 calls/s 02:52:47 DEBUG| [stdout] # udp tx:371 MB/s 6299 calls/s 6299 msg/s 02:52:48 DEBUG| [stdout] # UDP GRO fwd perfudp rx: 340 MB/s 277046 calls/s 02:52:48 DEBUG| [stdout] # udp tx:389 MB/s 6601 calls/s 6601 msg/s 02:52:49 DEBUG| [stdout] # udp rx:390 MB/s 318311 calls/s 02:52:49 DEBUG| [stdout] # udp tx:391 MB/s 6639 calls/s 6639 msg/s 02:52:50 DEBUG| [stdout] # udp rx:396 MB/s 322528 calls/s 02:52:50 DEBUG| [stdout] # udp tx:406 MB/s 6891 calls/s 6891 msg/s 02:52:50 DEBUG| [stdout] # GRO frag list over UDP tunnelok 02:52:50 DEBUG| [stdout] # GRO fwd over UDP tunnel ok 02:52:52 DEBUG| [stdout] # UDP tunnel fwd perf udp rx: 93 MB/s76354 calls/s 02:52:52 DEBUG| [stdout] # udp tx:257 MB/s 4360 calls/s 4360 msg/s 02:52:53 DEBUG| [stdout] # udp rx:297 MB/s 241883 calls/s 02:52:53 DEBUG| [stdout] # udp tx:
[Kernel-packages] [Bug 2016581] [NEW] ubuntu_kernel_selftests.net:cmsg_ipv6.sh ADT test failure with linux-hwe-5.19
Public bug reported: Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-hwe-5.19/20230402_045240_5691f@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/linux-hwe-5.19/20230402_044546_ce4cd@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/linux-hwe-5.19/20230402_065556_8e8e9@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/linux-hwe-5.19/20230401_232903_1a0c1@/log.gz Some ubuntu_kernel_selftests.net:cmsg_ipv6.sh are failing with linux-hwe-5.19 in Jammy but not with generic 5.19 in Kinetic. Different tests are failing on the different architectures, however all of them are returning the same "packet data returned 1, expected 0" error. Except from amd64 log: == 04:06:25 DEBUG| [stdout] # selftests: net: cmsg_ipv6.sh 04:06:27 DEBUG| [stdout] # Case HOPLIMIT RAW setsock - packet data returned 1, expected 0 04:06:28 DEBUG| [stdout] # FAIL - 1/93 cases failed 04:06:28 DEBUG| [stdout] not ok 1 selftests: net: cmsg_ipv6.sh # exit=1 == ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-hwe-5.19 (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Summary changed: - linux-hwe-5.19 ADT test failure with linux-hwe-5.19/5.19.0-40.41~22.04.1 + ubuntu_kernel_selftests.net:cmsg_ipv6.sh ADT test failure with linux-hwe-5.19 ** Description changed: - This is a scripted bug report about ADT failures while running linux- - hwe-5.19 tests for linux-hwe-5.19/5.19.0-40.41~22.04.1 on jammy. Whether - this is caused by the dep8 tests of the tested source or the kernel has - yet to be determined. + Testing failed on: + amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-hwe-5.19/20230402_045240_5691f@/log.gz + arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/linux-hwe-5.19/20230402_044546_ce4cd@/log.gz + ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/linux-hwe-5.19/20230402_065556_8e8e9@/log.gz + s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/linux-hwe-5.19/20230401_232903_1a0c1@/log.gz - Testing failed on: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-hwe-5.19/20230402_045240_5691f@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/linux-hwe-5.19/20230402_044546_ce4cd@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/linux-hwe-5.19/20230402_065556_8e8e9@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/linux-hwe-5.19/20230401_232903_1a0c1@/log.gz + + Some ubuntu_kernel_selftests.net:cmsg_ipv6.sh are failing with linux-hwe-5.19 in Jammy but not with generic 5.19 in Kinetic. + + Different tests are failing on the different architectures, however all + of them are returning the same "packet data returned 1, expected 0" + error. + + Except from amd64 log: + == + 04:06:25 DEBUG| [stdout] # selftests: net: cmsg_ipv6.sh + 04:06:27 DEBUG| [stdout] # Case HOPLIMIT RAW setsock - packet data returned 1, expected 0 + 04:06:28 DEBUG| [stdout] # FAIL - 1/93 cases failed + 04:06:28 DEBUG| [stdout] not ok 1 selftests: net: cmsg_ipv6.sh # exit=1 + == ** Also affects: linux-hwe-5.19 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-hwe-5.19 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Confirmed -- 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/2016581 Title: ubuntu_kernel_selftests.net:cmsg_ipv6.sh ADT test failure with linux- hwe-5.19 Status in ubuntu-kernel-tests: New Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in linux-hwe-5.19 source package in Jammy: Confirmed Bug description: Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-hwe-5.19/20230402_045240_5691f@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/linux-hwe-5.19/20230402_044546_ce4cd@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest
[Kernel-packages] [Bug 1928890] Re: vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)
This bug is still failing on recent kernels. Jammy 5.15: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux/20230327_235241_c3754@/log.gz Kinetic 5.19: https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux/20230328_203949_367cf@/log.gz ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu Kinetic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928890 Title: vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Won't Fix Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.10 source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Status in linux-oem-5.10 source package in Impish: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.10 source package in Jammy: New Status in linux source package in Kinetic: Confirmed Status in linux-oem-5.10 source package in Kinetic: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 00:09:30 DEBUG| [stdout] # selftests: net: vrf_route_leaking.sh 00:09:30 DEBUG| [stdout] # 00:09:30 DEBUG| [stdout] # ### 00:09:30 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP ttl error route lookup ping 00:09:30 DEBUG| [stdout] # ### 00:09:30 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:32 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded [ OK ] 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP error route lookup traceroute 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP fragmentation error route lookup ping 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # 00:09:34 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:34 DEBUG| [stdout] # TEST: Ping received ICMP Frag needed [ OK ] 00:09:34 DEBUG| [stdout] # 00:09:34 DEBUG| [stdout] # ### 00:09:34 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP ttl error route lookup ping 00:09:34 DEBUG| [stdout] # ### 00:09:34 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:36 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded [ OK ] 00:09:36 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP error route lookup traceroute
[Kernel-packages] [Bug 1950627] Re: ubuntu_kernel_selftests:net:udpgro_fwd.sh: udpgso_bench_tx: sendmsg: Connection refused
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) 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/1950627 Title: ubuntu_kernel_selftests:net:udpgro_fwd.sh: udpgso_bench_tx: sendmsg: Connection refused Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: This is from ADT testing (amd64) but I believe I occasionally saw this before. It feels like sometimes the receiver does not get ready before the transmission starts. IIRC this goes away when re-trying. 02:52:31 DEBUG| [stdout] # selftests: net: udpgro_fwd.sh 02:52:31 DEBUG| [stdout] # IPv4 02:52:31 DEBUG| [stdout] # No GRO ok 02:52:32 DEBUG| [stdout] # GRO frag listok 02:52:32 DEBUG| [stdout] # GRO fwd ok 02:52:33 DEBUG| [stdout] # UDP fwd perfudp rx: 333 MB/s 271894 calls/s 02:52:33 DEBUG| [stdout] # udp tx:378 MB/s 6422 calls/s 6422 msg/s 02:52:34 DEBUG| [stdout] # udp rx:383 MB/s 312480 calls/s 02:52:34 DEBUG| [stdout] # udp tx:383 MB/s 6506 calls/s 6506 msg/s 02:52:35 DEBUG| [stdout] # udp rx:381 MB/s 310202 calls/s 02:52:35 DEBUG| [stdout] # udp tx:380 MB/s 6458 calls/s 6458 msg/s 02:52:36 DEBUG| [stdout] # UDP GRO fwd perfudp rx: 344 MB/s 280814 calls/s 02:52:36 DEBUG| [stdout] # udp tx:389 MB/s 6612 calls/s 6612 msg/s 02:52:37 DEBUG| [stdout] # udp rx:364 MB/s 297088 calls/s 02:52:37 DEBUG| [stdout] # udp tx:383 MB/s 6512 calls/s 6512 msg/s 02:52:38 DEBUG| [stdout] # udp rx:448 MB/s 365435 calls/s 02:52:38 DEBUG| [stdout] # udp tx:453 MB/s 7686 calls/s 7686 msg/s 02:52:39 DEBUG| [stdout] # GRO frag list over UDP tunnelok 02:52:39 DEBUG| [stdout] # GRO fwd over UDP tunnel ok 02:52:39 DEBUG| [stdout] # UDP tunnel fwd perf ./udpgso_bench_tx: sendmsg: Connection refused 02:52:39 DEBUG| [stdout] # fail client exit code 1, server 0 02:52:40 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx: 236 MB/s 192389 calls/s 02:52:41 DEBUG| [stdout] # udp tx:284 MB/s 4826 calls/s 4826 msg/s 02:52:41 DEBUG| [stdout] # udp rx:295 MB/s 240586 calls/s 02:52:42 DEBUG| [stdout] # udp tx:306 MB/s 5206 calls/s 5206 msg/s 02:52:42 DEBUG| [stdout] # udp rx:306 MB/s 249784 calls/s 02:52:43 DEBUG| [stdout] # udp tx:310 MB/s 5263 calls/s 5263 msg/s 02:52:43 DEBUG| [stdout] # IPv6 02:52:43 DEBUG| [stdout] # No GRO ok 02:52:43 DEBUG| [stdout] # GRO frag listok 02:52:43 DEBUG| [stdout] # GRO fwd ok 02:52:44 DEBUG| [stdout] # UDP fwd perfudp rx: 82 MB/s66844 calls/s 02:52:45 DEBUG| [stdout] # udp tx:334 MB/s 5668 calls/s 5668 msg/s 02:52:45 DEBUG| [stdout] # udp rx:374 MB/s 305206 calls/s 02:52:46 DEBUG| [stdout] # udp tx:375 MB/s 6377 calls/s 6377 msg/s 02:52:46 DEBUG| [stdout] # udp rx:373 MB/s 303948 calls/s 02:52:47 DEBUG| [stdout] # udp tx:371 MB/s 6299 calls/s 6299 msg/s 02:52:48 DEBUG| [stdout] # UDP GRO fwd perfudp rx: 340 MB/s 277046 calls/s 02:52:48 DEBUG| [stdout] # udp tx:389 MB/s 6601 calls/s 6601 msg/s 02:52:49 DEBUG| [stdout] # udp rx:390 MB/s 318311 calls/s 02:52:49 DEBUG| [stdout] # udp tx:391 MB/s 6639 calls/s 6639 msg/s 02:52:50 DEBUG| [stdout] # udp rx:396 MB/s 322528 calls/s 02:52:50 DEBUG| [stdout] # udp tx:406 MB/s 6891 calls/s 6891 msg/s 02:52:50 DEBUG| [stdout] # GRO frag list over UDP tunnelok 02:52:50 DEBUG| [stdout] # GRO fwd over UDP tunnel ok 02:52:52 DEBUG| [stdout] # UDP tunnel fwd perf udp rx: 93 MB/s76354 calls/s 02:52:52 DEBUG| [stdout] # udp tx:257 MB/s 4360 calls/s 4360 msg/s 02:52:53 DEBUG| [stdout] # udp rx:297 MB/s 241883 calls/s 02:52:53 DEBUG| [stdout] # udp tx:315 MB/s 5352 calls/s 5352 msg/s 02:52:54 DEBUG| [stdout] # udp rx:286 MB/s 233207 calls/s 02:52:54 DEBUG| [stdout] # udp tx:304 MB/s 5172 calls/s 5172 msg/s 02:52:55 DEBUG| [stdout] # UDP t
[Kernel-packages] [Bug 1987507] Re: Migrate oem-20.04 to hwe-5.15
the nvidia 390 test can be ignored -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987507 Title: Migrate oem-20.04 to hwe-5.15 Status in linux-meta-hwe-5.15 package in Ubuntu: Invalid Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: Invalid Status in linux-meta-hwe-5.15 source package in Focal: New Status in linux-restricted-modules-hwe-5.15 source package in Focal: New Bug description: [Impact] Migrate oem-5.14 to hwe-5.15 now that there should be no functional regressions left anymore. [Test case] Update a machine with oem-5.14 metapackages to the proposed ones, and verify that all packages (including nvidia etc) migrate properly. [Where things could go wrong] In theory we might miss a package to transition, but at this point this is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.15/+bug/1987507/+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 2007904] Re: [Possible Regression] net:reuseaddr_ports_exhausted.sh in ubuntu_kernel_selftests failed on F-oem-5.14 / J-oem-5.17
** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/2007904 Title: [Possible Regression] net:reuseaddr_ports_exhausted.sh in ubuntu_kernel_selftests failed on F-oem-5.14 / J-oem-5.17 Status in ubuntu-kernel-tests: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Fix Released Bug description: Issue found on F-oem-5.14.0-1058.66, it looks like a regression. This failure cannot be reproduced with 5.14.0-1057.64 Test log: TAP version 13 1..3 # Starting 3 tests from 1 test cases. # RUN global.reuseaddr_ports_exhausted_unreusable ... #OK global.reuseaddr_ports_exhausted_unreusable ok 1 global.reuseaddr_ports_exhausted_unreusable # RUN global.reuseaddr_ports_exhausted_reusable_same_euid ... #OK global.reuseaddr_ports_exhausted_reusable_same_euid ok 2 global.reuseaddr_ports_exhausted_reusable_same_euid # RUN global.reuseaddr_ports_exhausted_reusable_different_euid ... # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:Expected -1 (-1) == ret (0) # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:should fail to listen because only one uid reserves the port in TCP_LISTEN. # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:Expected -1 (-1) == ret (0) # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:should fail to listen because only one uid reserves the port in TCP_LISTEN. # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:Expected -1 (-1) == ret (0) # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:should fail to listen because only one uid reserves the port in TCP_LISTEN. # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:Expected -1 (-1) == ret (0) # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:should fail to listen because only one uid reserves the port in TCP_LISTEN. # reuseaddr_ports_exhausted_reusable_different_euid: Test failed at step #13 # FAIL global.reuseaddr_ports_exhausted_reusable_different_euid not ok 3 global.reuseaddr_ports_exhausted_reusable_different_euid # FAILED: 2 / 3 tests passed. # Totals: pass:2 fail:1 xfail:0 xpass:0 skip:0 error:0 Test result with 5.14.0-1057.64 $ sudo ./reuseaddr_ports_exhausted.sh TAP version 13 1..3 # Starting 3 tests from 1 test cases. # RUN global.reuseaddr_ports_exhausted_unreusable ... #OK global.reuseaddr_ports_exhausted_unreusable ok 1 global.reuseaddr_ports_exhausted_unreusable # RUN global.reuseaddr_ports_exhausted_reusable_same_euid ... #OK global.reuseaddr_ports_exhausted_reusable_same_euid ok 2 global.reuseaddr_ports_exhausted_reusable_same_euid # RUN global.reuseaddr_ports_exhausted_reusable_different_euid ... #OK global.reuseaddr_ports_exhausted_reusable_different_euid ok 3 global.reuseaddr_ports_exhausted_reusable_different_euid # PASSED: 3 / 3 tests passed. # Totals: pass:3 fail:0 xfail:0 xpass:0 skip:0 error:0 tests done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2007904/+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 2011379] Re: Speaker / Audio/Mic mute LED don't work on a HP platform
confirmed 1009-oem from jammy-prpoposed fixes this issue. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy ** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2011379 Title: Speaker / Audio/Mic mute LED don't work on a HP platform Status in HWE Next: New Status in OEM Priority Project: Fix Released 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: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The speaker / audio/mic mute LEDs don't work on a HP platform. [Fix] This is HP platform needs ALC245_FIXUP_CS35L41_SPI_2_HP_GPIO_LED quirk to make mic-mute/audio-mute/speaker working. [Test] After applying the fix, the speaker / audio/mic mute LEDs are working. [Where problems could occur] It's low risk as it's specific ID for HP new machines. If the HP ships other machines using same SSID, then these functions may not work on those machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011379/+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 2016045] Re: Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument]
Seems the only possible solution is to fix Xorg to not use DRM_MODE_PAGE_FLIP_ASYNC on single monitor systems. ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Opinion ** Changed in: xorg-server (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg-server (Ubuntu) Status: New => Triaged -- 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/2016045 Title: Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument] Status in linux-hwe-5.19 package in Ubuntu: Opinion Status in xorg-server package in Ubuntu: Triaged Bug description: 1/3 times I tab in / out of a app/game, that is running using the nvidia dedicated gpu, the screen freezes forcing me to restart my laptop. The cursor is still "usable" and reboot using SysRq REISUB is possible. This is not tied only to steam games, other apps/games like minecraft also cause this problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 13 00:58:23 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 5.19.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84c1] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:84c1] InstallationDate: Installed on 2023-02-06 (65 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=bd5e3449-4d4f-4ebd-afef-1e4da7b9ec69 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2020 dmi.bios.release: 15.23 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84C1 dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs2xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku7EF01EA#AB7: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs2xxx dmi.product.sku: 7EF01EA#AB7 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2016045/+subscriptions -- Mailing list: https:/
[Kernel-packages] [Bug 2016045] Re: Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument]
Oops. The fix will only ever support Intel Gen12 GPUs (11th gen CPUs and later). So there won't be a kernel fix you can use. I wonder if Xorg can ever detect and avoid it before it happens... ** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags added: hybrid i915 multigpu nvidia -- 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/2016045 Title: Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument] Status in linux-hwe-5.19 package in Ubuntu: Opinion Status in xorg-server package in Ubuntu: Triaged Bug description: 1/3 times I tab in / out of a app/game, that is running using the nvidia dedicated gpu, the screen freezes forcing me to restart my laptop. The cursor is still "usable" and reboot using SysRq REISUB is possible. This is not tied only to steam games, other apps/games like minecraft also cause this problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 13 00:58:23 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 5.19.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84c1] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:84c1] InstallationDate: Installed on 2023-02-06 (65 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=bd5e3449-4d4f-4ebd-afef-1e4da7b9ec69 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2020 dmi.bios.release: 15.23 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84C1 dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs2xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku7EF01EA#AB7: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs2xxx dmi.product.sku: 7EF01EA#AB7 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2016045/+subscriptions -- Mailing list: http
[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
As described in https://community.intel.com/t5/Blogs/Products-and-Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI-Applications-for/post/1335100, for Intel Sapphire Rapids CPUs with HBM, it is possible to utilize the HBM as cache (so called "2LM mode"). It works in the way to create N fake NUMA domains in a size aligned the HBM so that HBM can act like direct-mapped L4 cache. Since this is not really a "bug" (but is an officially proposed use case from Intel), it's not likely to provide a test case. But from HPE's testing of the test kernel from comment 2, there is improvement to performance on a Sapphire Rapids CPU with HBM. ** Changed in: linux (Ubuntu Jammy) 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/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: New Status in linux source package in Lunar: Incomplete Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+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 2016476] [NEW] casper/1.470.2 ADT test failure with linux-hwe-5.19/5.19.0-40.41~22.04.1
*** This bug is a duplicate of bug 2016477 *** https://bugs.launchpad.net/bugs/2016477 Public bug reported: This is a scripted bug report about ADT failures while running casper tests for linux-hwe-5.19/5.19.0-40.41~22.04.1 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/c/casper/20230403_091405_2f860@/log.gz ** Affects: casper (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** This bug has been marked a duplicate of bug 2016477 casper/1.470.2 ADT test failure with linux-hwe-5.19/5.19.0-40.41~22.04.1 -- 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/2016476 Title: casper/1.470.2 ADT test failure with linux- hwe-5.19/5.19.0-40.41~22.04.1 Status in casper package in Ubuntu: New Status in linux-hwe-5.19 package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running casper tests for linux-hwe-5.19/5.19.0-40.41~22.04.1 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/c/casper/20230403_091405_2f860@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2016476/+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 2016477] [NEW] casper/1.470.2 ADT test failure with linux-hwe-5.19/5.19.0-40.41~22.04.1
Public bug reported: This is a scripted bug report about ADT failures while running casper tests for linux-hwe-5.19/5.19.0-40.41~22.04.1 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/c/casper/20230403_091405_2f860@/log.gz This test seems to have regressed with hwe-5.19 in Jammy when casper got updated from version 1.470.1 to 1.470.2. Latest debug messages from the test log file: = + rm -rf image.img + truncate -s 1G image.img + parted --script --align optimal image.img -- mklabel gpt mkpart primary ext4 1MiB -2048s ++ losetup -Pf --show image.img + dev=/dev/loop0 + mke2fs -L rootfs -q /dev/loop0p1 The file /dev/loop0p1 does not exist and no size was specified. = ** Affects: casper (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: casper (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-hwe-5.19 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Description changed: This is a scripted bug report about ADT failures while running casper tests for linux-hwe-5.19/5.19.0-40.41~22.04.1 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/c/casper/20230403_091405_2f860@/log.gz + amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/c/casper/20230403_091405_2f860@/log.gz + + This test seems to have regressed with hwe-5.19 in Jammy when casper got + updated from version 1.470.1 to 1.470.2. + + Latest debug messages from the test log file: + + = + + rm -rf image.img + + truncate -s 1G image.img + + parted --script --align optimal image.img -- mklabel gpt mkpart primary ext4 1MiB -2048s + ++ losetup -Pf --show image.img + + dev=/dev/loop0 + + mke2fs -L rootfs -q /dev/loop0p1 + The file /dev/loop0p1 does not exist and no size was specified. + = ** Also affects: casper (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-hwe-5.19 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Incomplete ** Changed in: linux-hwe-5.19 (Ubuntu) Status: Incomplete => Invalid -- 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/2016477 Title: casper/1.470.2 ADT test failure with linux- hwe-5.19/5.19.0-40.41~22.04.1 Status in casper package in Ubuntu: New Status in linux-hwe-5.19 package in Ubuntu: Invalid Status in casper source package in Jammy: New Status in linux-hwe-5.19 source package in Jammy: New Bug description: This is a scripted bug report about ADT failures while running casper tests for linux-hwe-5.19/5.19.0-40.41~22.04.1 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/c/casper/20230403_091405_2f860@/log.gz This test seems to have regressed with hwe-5.19 in Jammy when casper got updated from version 1.470.1 to 1.470.2. Latest debug messages from the test log file: = + rm -rf image.img + truncate -s 1G image.img + parted --script --align optimal image.img -- mklabel gpt mkpart primary ext4 1MiB -2048s ++ losetup -Pf --show image.img + dev=/dev/loop0 + mke2fs -L rootfs -q /dev/loop0p1 The file /dev/loop0p1 does not exist and no size was specified. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2016477/+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 2015297] Re: Update GPU F/W for DCN 3.1.4 products to fix S0i3 issue
** Changed in: hwe-next Status: New => Fix Committed -- 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/2015297 Title: Update GPU F/W for DCN 3.1.4 products to fix S0i3 issue Status in HWE Next: Fix Committed Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Invalid Status in linux-firmware source package in Lunar: Fix Committed Bug description: [ Impact ] The current GPU firmware in place for DCN 3.1.4 based products fails to resume from s2idle on newer BIOSes. The following GPU F/W stack is confirmed to fix the problem and works both with the older BIOSes and newer BIOSes: 9ee24ce0 amdgpu: Update SDMA 6.0.1 firmware 7df2a1ae amdgpu: Add PSP 13.0.11 firmware f098803d amdgpu: Update PSP 13.0.4 firmware 2cc9a4d0 amdgpu: Update GC 11.0.1 firmware eb13e669 amdgpu: Update DCN 3.1.4 firmware 898b7def amdgpu: Add GC 11.0.4 firmware Those binaries are part of upstream linux-firmware tag 20230404. [ Test Plan ] * Run s2idle cycle using OEM-6.1 1008 or 1009 kernel on a DCN 3.1.4 platform * Verify that display comes back [ Where problems could occur ] * This GPU F/W is only used for DCN 3.1.4 based products. These aren't yet on the market and there is no risk to regression to any Ubuntu users. * Without this firmware update OEM systems running newer BIOS won't be able to be certified. [ Other Info ] * AMD has found this regression and validated this stack on reference hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2015297/+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 2016469] Re: test_maps in ubuntu_bpf failed on J-oem-6.1 ( run_parallel: Assertion `status == 0' failed.)
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Description changed: Issue found in J-oem-6.1.0-1009.9 after fixing the build issue in bug 2016455. The test_maps in ubuntu_bpf will fail with: - test_maps: test_maps.c:1375: __run_parallel: Assertion `status == 0' failed. + test_maps: test_maps.c:1375: __run_parallel: Assertion `status == 0' failed. Test log: - Running './test_maps' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_hashmap_walk' - Fork 100 tasks to 'test_hashmap' - Fork 100 tasks to 'test_hashmap_percpu' - Fork 100 tasks to 'test_hashmap_sizes' - Fork 100 tasks to 'test_arraymap' - Fork 100 tasks to 'test_arraymap_percpu' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_update_delete' - Fork 100 tasks to 'test_hashmap_walk' - Fork 100 tasks to 'test_hashmap' - Fork 100 tasks to 'test_hashmap_percpu' - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed. - test_maps: test_maps.c:173: test_hashmap_perc
[Kernel-packages] [Bug 2016470] [NEW] Jammy update: v6.1.24 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.24 upstream stable release from git://git.kernel.org/ Linux 6.1.24 bpftool: Print newline before '}' for struct with padding only fields mm: enable maple tree RCU mode by default. maple_tree: add RCU lock checking to rcu callback functions maple_tree: add smp_rmb() to dead node detection maple_tree: remove extra smp_wmb() from mas_dead_leaves() maple_tree: fix freeing of nodes in rcu mode maple_tree: detect dead nodes in mas_start() maple_tree: refine ma_state init from mas_start() maple_tree: be more cautious about dead nodes maple_tree: fix mas_prev() and mas_find() state handling maple_tree: fix handle of invalidated state in mas_wr_store_setup() maple_tree: reduce user error potential maple_tree: fix potential rcu issue maple_tree: remove GFP_ZERO from kmem_cache_alloc() and kmem_cache_alloc_bulk() mm: take a page reference when removing device exclusive entries drm/i915: Split icl_color_commit_noarm() from skl_color_commit_noarm() drm/i915: Use _MMIO_PIPE() for SKL_BOTTOM_COLOR drm/bridge: lt9611: Fix PLL being unable to lock drm/i915/dp_mst: Fix payload removal during output disabling drm/display/dp_mst: Handle old/new payload states in drm_dp_remove_payload() drm/amdgpu: skip psp suspend for IMU enabled ASICs mode2 reset drm/amdgpu: for S0ix, skip SDMA 5.x+ suspend/resume drm/amd/display: Clear MST topology if it fails to resume blk-throttle: Fix that bps of child could exceed bps limited in parent maple_tree: fix a potential concurrency bug in RCU mode maple_tree: fix get wrong data_end in mtree_lookup_walk() mm/hugetlb: fix uffd wr-protection for CoW optimization path mm/swap: fix swap_info_struct race between swapoff and get_swap_pages() ring-buffer: Fix race while reader and writer are on the same page drm/i915: fix race condition UAF in i915_perf_add_config_ioctl drm/i915: Fix context runtime accounting drm/nouveau/disp: Support more modes by checking with lower bpc drm/panfrost: Fix the panfrost_mmu_map_fault_addr() error path ublk: read any SQE values upfront wifi: mt76: ignore key disable commands mm: vmalloc: avoid warn_alloc noise caused by fatal signal zsmalloc: document freeable stats tracing/synthetic: Make lastcmd_mutex static ASoC: hdac_hdmi: use set_stream() instead of set_tdm_slots() tracing: Free error logs of tracing instances tracing/osnoise: Fix notify new tracing_max_latency tracing/timerlat: Notify new max thread latency tracing/synthetic: Fix races on freeing last_cmd net: stmmac: Add queue reset into stmmac_xdp_open() function ACPI: video: Add acpi_backlight=video quirk for Lenovo ThinkPad W530 ACPI: video: Add acpi_backlight=video quirk for Apple iMac14,1 and iMac14,2 ACPI: video: Make acpi_backlight=video work independent from GPU driver ACPI: video: Add auto_detect arg to __acpi_video_get_backlight_type() can: isotp: isotp_recvmsg(): use sock_recv_cmsgs() to get SOCK_RXQ_OVFL infos can: isotp: isotp_ops: fix poll() to not report false EPOLLOUT events can: isotp: fix race between isotp_sendsmg() and isotp_release() can: j1939: j1939_tp_tx_dat_new(): fix out-of-bounds memory access fs: drop peer group ids under namespace lock ftrace: Fix issue that 'direct->addr' not restored in modify_ftrace_direct() ftrace: Mark get_lock_parent_ip() __always_inline perf/core: Fix the same task check in perf_event_set_output block: don't set GD_NEED_PART_SCAN if scan partition failed block: ublk: make sure that block size is set correctly cifs: sanitize paths in cifs_update_super_prepath. nvme: fix discard support without oncs scsi: iscsi_tcp: Check that sock is valid before iscsi_set_param() scsi: qla2xxx: Fix memory leak in qla2x00_probe_one() io_uring: fix memory leak when removing provided buffers io_uring: fix return value when removing provided buffers iio: adc: ad7791: fix IRQ flags blk-mq: directly poll requests counter: 104-quad-8: Fix Synapse action reported for Index signals counter: 104-quad-8: Fix race condition between FLAG and CNTR reads coresight-etm4: Fix for() loop drvdata->nr_addr_cmp range bug coresight: etm4x: Do not access TRCIDR1 for identification mm: kfence: fix handling discontiguous page mm: kfence: fix PG_slab and memcg_data clearing KVM: nVMX: Do not report error code when synthesizing VM-Exit from Real Mode KVM: x86: Clear "has_error_code", not "error_code", for RM exception injection x86/ACPI/boot: Use FADT version to check support for online capable x86/acpi/boot: Correct acpi_is_processor_usable() check ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook
[Kernel-packages] [Bug 1845641] Re: test_maps in ubuntu_bpf failed on i386 Disco ( run_parallel: Assertion `status == 0' failed.)
Disco EOL, and we don't have any hints that is pointing to this. ** Changed in: ubuntu-kernel-tests Status: Triaged => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1845641 Title: test_maps in ubuntu_bpf failed on i386 Disco ( run_parallel: Assertion `status == 0' failed.) Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Won't Fix Bug description: Like bug 1788580 for bionic, the ubuntu_bpf test failed on Disco i386 with: 9965. Fork 100 tasks to 'test_hashmap' 9966. Fork 100 tasks to 'test_hashmap_percpu' 9967. Fork 100 tasks to 'test_hashmap_sizes' 9968. Fork 100 tasks to 'test_hashmap_walk' 9969. helper_fill_hashmap(270):FAIL:failed to create hashmap err: Cannot allocate memory, flags: 0x0 9970. stderr: 9971. test_maps: test_maps.c:1286: __run_parallel: Assertion `status == 0' failed. 9972. 09/26 18:29:41 WARNI| test:0115| Programs crashed during test execution 9973. 09/26 18:29:41 WARNI| test:0117| Please verify /home/ubuntu/autotest/client/results/default/ubuntu_bpf.test_maps/debug/crash.test_maps.11955 for more info 9974. For the complete test log, please refer to the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845641/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
Hi! I have same problem. UVC Quanta 0408:4035 on Acer Nitro 5 AN515-58. Kubuntu 23.04, kernel 6.2.0. I cannot build this patch with 6.2.0 kernel, because of initial driver file uvc_driver.c in 6.2.0 have many changes. I found maybe suitable driver for 6.x kernel (???). https://github.com/Kvalme/uvc But after building it I have only: "modprobe: ERROR: could not insert 'uvcvideo': Exec format error" in dmesg. Maybe it errors in driver, mayby I do something wrong. Can you, please, make correct driver for 6.2 kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 l
[Kernel-packages] [Bug 2006453] Re: Fix selftests/ftracetests/Meta-selftests
There is no test for bluefield. Test passed with J-oem-6.1.0-1009.9 ** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- 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 Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed 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 2013438] Re: Add support for Pensando SoC
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-iot in Ubuntu. https://bugs.launchpad.net/bugs/2013438 Title: Add support for Pensando SoC Status in linux-iot package in Ubuntu: Fix Committed Status in linux-meta-iot package in Ubuntu: Fix Committed Status in linux-iot source package in Focal: Fix Committed Status in linux-meta-iot source package in Focal: Fix Committed Bug description: This bug is for tracking the progress of adding Pensando SoC support in focal:linux-iot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-iot/+bug/2013438/+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 1968604] Re: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug
Update on Ubuntu 23.04 beta with kernel 6.2 Bluetooth works out of the box, no need for the earlier symbolic links anymore! So the rtl8761bu is now used and works with my USB dongle. -- 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/1968604 Title: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug Status in linux-firmware package in Ubuntu: Confirmed Bug description: I have usb bluetooth 5.0 dongle which uses Realtek RTL8761B chip. 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio USB adapter very often stops working, can't connect or find other bluetooth devices. The adapter can't work even after reboots. The following entries appear in the log: апр 11 13:47:14 desktop kernel: Bluetooth: hci0: command 0x2005 tx timeout апр 11 13:47:16 desktop kernel: Bluetooth: hci0: command 0x2041 tx timeout апр 11 13:47:18 desktop kernel: Bluetooth: hci0: command 0x2042 tx timeout Firmware loaded correctly, but something is not working. апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814 1) I use: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) linux-firmware: 20220329.git681281e4-0ubuntu1 3) What you expected to happen? I expect a well working bluetooth adapter. 4) What happened instead? My bluetooth adapter may work, may not. The adapter may stop finding and connecting to other devices. I've found the same bug https://bugzilla.kernel.org/show_bug.cgi?id=214111#c1 I've downloaded Windows's archive http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2021/05/ca0e770c-6a5d-4de0-b37a-f4b91cccd8c3_7778831d2b9d721cf94d5a8d8c0676ff1b96c874.cab I've unpacked file rtl8761b_mp_chip_bt40_fw_asic_rom_patch_new.dll and replaced /usr/lib/firmware/rtl_bt/rtl8761bu_fw.bin and deleted rtl8761bu_config.bin After I changed firmware my usb dongle work fine. Could you change firmware rtl8761bu_fw.bin rtl8761bu_config.bin to other correct version? Could you move Realtek's rtl_bt firmware or RTL8761B's firmware into separate packages. I will remove the RTL8761B firmware package and put them manually. bluetoothctl --version bluetoothctl: 5.64 hci0: Type: Primary Bus: USB BD Address: 00:E0:4C:FC:E2:03 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:5751 acl:49 sco:0 events:489 errors:0 TX bytes:219114 acl:398 sco:0 commands:83 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'desktop' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x97b LMP Version: 5.1 (0xa) Subversion: 0xec43 Manufacturer: Realtek Semiconductor Corporation (93) rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Realtek's worker updated these bad firmware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=45dc5f0b8e2f2d43312d22511cb26658b9ee2c80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1968604/+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
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Un
[Kernel-packages] [Bug 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
I think we might have multiple different bugs here. The log in comment #80 sounds like this kernel bug which might occur on HDMI connections that are not 16:9 aspect: https://gitlab.freedesktop.org/drm/intel/-/issues/6153 But not everyone here seems to have an unusual aspect ratio, or even HDMI. So everyone else please follow the steps in comment #75. ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #6153 https://gitlab.freedesktop.org/drm/intel/-/issues/6153 -- 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/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 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-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2009642] Re: mt7921: add support of MTFG table
** 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2009642 Title: mt7921: add support of MTFG table Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux-firmware source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. Lunar already got the firmware, so SRU for Jammy only. Kernel commit is a new feature and it requests more than 10 unrelated commits when backport to 5.15 and 5.19, so SRU for 6.0+ kernel version. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [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/2009642/+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 2009164] Re: Fix screen that remains blank forever after it gets locked
** 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-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009164 Title: Fix screen that remains blank forever after it gets locked Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] Once screen is locked under gnome-shell, the screen never wakes up and remains in blank forever. [Fix] "drm/i915: Create resized LUTs for ivb+ split gamma mode" makes gamma LUT operations in atomic context, so userspace can no longer misuse libdrm. "drm/i915: Rework legacy LUT handling" starts to use the reworked gamma LUT. Pull the whole series and series they depends upon to properly support gamma LUT. [Test] The easier way to reproduce the issue is to 1) Login under Wayland 2) Logout and login under X 3) Go back to wayland 4) Super + L to screenlock With the LUT reworked series applied, screen can always come back alive. [Where problems could occur] Regression can happen on refactoring patches with "no functional change intended", let alone overhauls like this one. So only OEM-6.1 and Unstable are targeted to contain the potential regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009164/+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 2012846] Re: Fix spurious wakeup from S5 when TBT dock is plugged
** 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-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2012846 Title: Fix spurious wakeup from S5 when TBT dock is plugged Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] When TBT dock is plugged, system wakes up immediately after shutdown. [Fix] "ACPICA: Events: Support fixed PCIe wake event" to properly support fixed PCIe wake event. Opposite to other ACPI events, the PCIe wake event gets enabled during boot up and gets disabled on S states like S5 shutdown. [Test] The spurious wake up is no longer observed when [Where problems could occur] I did some quick tests and didn't see any negative impact. However, since ACPI fixed PCIe event now is enabled when system is running, events like runtime PCIe D3cold wake can be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2012846/+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 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Next please: * More people follow the steps in comment #75. * Some people try newer kernel versions to see if/where the problem was fixed: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D -- 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/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 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-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
This is looking like a kernel bug (comment #81) and increasingly unlike mutter has done anything wrong. Sounds like it is specifically about i915 HDMI handling. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Summary changed: - Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] + [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] ** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Confirmed ** Tags added: i915 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 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-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2016461] 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 2016461 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/2016461 Title: No wifi with AC88 since 5.19.0-40: increase max_flowrings limit 256 to 512 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu can't see my wifi adapter since 5.19.0-40 kernel update (works wih 5.19.0-38) The bug is described in this answer: https://answers.launchpad.net/ubuntu/+question/706179 The cause is that a check has been introduced on max_flowrings > 256 (https://patchwork.kernel.org/project/linux- wireless/patch/20220929031001.9962-3-ian@infineon.com/) being accounted for a faulty device behaviour when it's the default value for the asus AC88 wifi adapter. Can the check be removed or the value increased so that I can use my wifi adapter ? see also: https://www.reddit.com/r/archlinux/comments/104pqv9/no_wifi_since_kernel_update_yesterday/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016461/+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 1827980] Re: hyperv_synic in ubuntu_kvm_unit_tests timeout on B-KVM / openstack instance
** Summary changed: - hyperv_synic in ubuntu_kvm_unit_tests timeout on B-KVM + hyperv_synic in ubuntu_kvm_unit_tests timeout on B-KVM / openstack instance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827980 Title: hyperv_synic in ubuntu_kvm_unit_tests timeout on B-KVM / openstack instance Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: Test timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:36:32 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827980/+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 1827982] Re: hyperv_stimer in ubuntu_kvm_unit_tests timeout on B-KVM / B-Oracle-5.3 / B-Oracle-5.4
This timeout issue can be found on J-oem-6.1 with openstack instance. ** Tags added: 6.1 oem sru-20230320 ** Tags added: openstack ** Summary changed: - hyperv_stimer in ubuntu_kvm_unit_tests timeout on B-KVM / B-Oracle-5.3 / B-Oracle-5.4 + hyperv_stimer in ubuntu_kvm_unit_tests timeout on B-KVM / B-Oracle-5.4 / openstack instance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827982 Title: hyperv_stimer in ubuntu_kvm_unit_tests timeout on B-KVM / B-Oracle-5.4 / openstack instance Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: Test timeouted. # TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # -initrd /tmp/tmp.ouYfwUEdq5 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic cpus = 2 qemu-system-x86_64: terminating on signal 15 from pid 2224 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:39:16 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827982/+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 1827980] Re: hyperv_synic in ubuntu_kvm_unit_tests timeout on B-KVM
This timeout issue can be found on Openstack instances as well. ** Tags added: 6.1 oem sru -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827980 Title: hyperv_synic in ubuntu_kvm_unit_tests timeout on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: Test timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:36:32 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827980/+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 2016461] Re: No wifi with AC88 since 5.19.0-40: increase max_flowrings limit 256 to 512
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: 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/2016461 Title: No wifi with AC88 since 5.19.0-40: increase max_flowrings limit 256 to 512 Status in linux package in Ubuntu: New Bug description: Ubuntu can't see my wifi adapter since 5.19.0-40 kernel update (works wih 5.19.0-38) The bug is described in this answer: https://answers.launchpad.net/ubuntu/+question/706179 The cause is that a check has been introduced on max_flowrings > 256 (https://patchwork.kernel.org/project/linux- wireless/patch/20220929031001.9962-3-ian@infineon.com/) being accounted for a faulty device behaviour when it's the default value for the asus AC88 wifi adapter. Can the check be removed or the value increased so that I can use my wifi adapter ? see also: https://www.reddit.com/r/archlinux/comments/104pqv9/no_wifi_since_kernel_update_yesterday/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016461/+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 2016461] [NEW] No wifi with AC88 since 5.19.0-40: increase max_flowrings limit 256 to 512
You have been subscribed to a public bug: Ubuntu can't see my wifi adapter since 5.19.0-40 kernel update (works wih 5.19.0-38) The bug is described in this answer: https://answers.launchpad.net/ubuntu/+question/706179 The cause is that a check has been introduced on max_flowrings > 256 (https://patchwork.kernel.org/project/linux- wireless/patch/20220929031001.9962-3-ian@infineon.com/) being accounted for a faulty device behaviour when it's the default value for the asus AC88 wifi adapter. Can the check be removed or the value increased so that I can use my wifi adapter ? see also: https://www.reddit.com/r/archlinux/comments/104pqv9/no_wifi_since_kernel_update_yesterday/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- No wifi with AC88 since 5.19.0-40: increase max_flowrings limit 256 to 512 https://bugs.launchpad.net/bugs/2016461 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016202] Re: bluetooth doesnt work properly, honor magicbook 15 amd
Please run 'apport-collect 2016202`. ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Incomplete -- 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/2016202 Title: bluetooth doesnt work properly, honor magicbook 15 amd Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: bluetooth does not work on honor magicbook 15 amd ryzen ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 14 05:10:56 2023 InstallationDate: Installed on 2023-02-20 (52 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) 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-hwe-5.19/+bug/2016202/+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 2016295] Re: WiFi disconnect after every 1-3 mins
Pleas run `apport-collect 2016295`. ** Package changed: linux-signed-hwe-5.15 (Ubuntu) => linux-hwe-5.15 (Ubuntu) ** Changed in: linux-hwe-5.15 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2016295 Title: WiFi disconnect after every 1-3 mins Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: WiFi disconnect automatically after some time then i have to restart my laptop my laptop then it is working fine then again after 1-3 mins it's disconnect ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-69-generic 5.15.0-69.76~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 14 17:39:35 2023 InstallationDate: Installed on 2023-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) SourcePackage: linux-signed-hwe-5.15 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.15/+bug/2016295/+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 2016326] Re: tochpad is not working, and on restarting wifi adaptor is not found
Please run 'apport-collect 2016326'. ** Package changed: linux-signed-hwe-5.19 (Ubuntu) => linux-hwe-5.19 (Ubuntu) ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Incomplete -- 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/2016326 Title: tochpad is not working, and on restarting wifi adaptor is not found Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: My touchpad is not working. It is not showing any cursor or arrow on the screen. When I restart , my wifi adaptor also not found. Then I shut down and open it, it works. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 14 23:36:05 2023 InstallationDate: Installed on 2022-09-12 (214 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) 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-hwe-5.19/+bug/2016326/+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
