[Kernel-packages] [Bug 1999731] Re: disk stress test failing with code 7
Thanks Colin, For your information, I ran a loop test[1] on each of stress-ng tags since V0.12.00, with 100 times lockofd run and see the return value. This issue starts to be seen since V0.12.09 (or maybe early because the reprudce chance is very low). Full console log is attached for your information. -- #!/bin/bash for i in `cat gittag.txt`; do echo $i cd /home/ubuntu/stress-ng make clean git reset --hard git checkout $i make clean make cd /home/ubuntu for j in `seq 1 100`; do ./stress-ng/stress-ng --lockofd 0 -t 240 echo == $? == done done ** Attachment added: "screenlog.0.gz" https://bugs.launchpad.net/stress-ng/+bug/1999731/+attachment/5652313/+files/screenlog.0.gz -- 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/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: Invalid Status in stress-ng package in Ubuntu: Fix Released Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+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 1975650] Re: Nvidia kernel driver stops loading after kernel update (needs manual reinstallation)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975650 Title: Nvidia kernel driver stops loading after kernel update (needs manual reinstallation) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Bug description: I often have to forcibly power down my PC because of this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the most recent time I did that, when the computer restarted, the resolution is stuck on 1024x768 even though I am on a 1920x1080 monitor. I restarted my PC again and it is still stuck on the low resolution. This Ask Ubuntu answer (https://askubuntu.com/a/1167437/1589552) did allow me to force my resolution to 1920x1080, but a few things still seemed off: - The display settings page in the Gnome settings app still showed my display as "unknown display" and did not have any options for changing the resolution. - A WebGL-based application I use for work was very slow compared to normal. I reverted the change to my Grub config and now I'm back to 1024x768. I have an Nvidia GTX 1060 connected to a 1920x1080 monitor via HDMI. Let me know of any other information I can provide that would be helpful. Also let me know if there is a workaround other than reinstalling the OS. Edit: I have a Windows dual boot on this PC, with Windows installed on a separate SSD. I booted into Windows and everything seems completely fine. This provides further evidence that this is a software issue, not a hardware one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 24 20:14:55 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3287] InstallationDate: Installed on 2022-04-23 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975650/+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 1975650] Re: Nvidia kernel driver stops loading after kernel update (needs manual reinstallation)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975650 Title: Nvidia kernel driver stops loading after kernel update (needs manual reinstallation) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Bug description: I often have to forcibly power down my PC because of this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the most recent time I did that, when the computer restarted, the resolution is stuck on 1024x768 even though I am on a 1920x1080 monitor. I restarted my PC again and it is still stuck on the low resolution. This Ask Ubuntu answer (https://askubuntu.com/a/1167437/1589552) did allow me to force my resolution to 1920x1080, but a few things still seemed off: - The display settings page in the Gnome settings app still showed my display as "unknown display" and did not have any options for changing the resolution. - A WebGL-based application I use for work was very slow compared to normal. I reverted the change to my Grub config and now I'm back to 1024x768. I have an Nvidia GTX 1060 connected to a 1920x1080 monitor via HDMI. Let me know of any other information I can provide that would be helpful. Also let me know if there is a workaround other than reinstalling the OS. Edit: I have a Windows dual boot on this PC, with Windows installed on a separate SSD. I booted into Windows and everything seems completely fine. This provides further evidence that this is a software issue, not a hardware one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 24 20:14:55 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3287] InstallationDate: Installed on 2022-04-23 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975650/+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 1999731] Re: disk stress test failing with code 7
** Changed in: linux (Ubuntu) Status: In Progress => 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/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: Invalid Status in stress-ng package in Ubuntu: Fix Released Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993561] Re: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode
as per Cyrus, ''' SRU kernel 5.19.0-37.38 verified pass. ''' Thanks Cyrus. ** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1993561 Title: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The Screen is shaking connected monitor to Onboard HDMI port. [Fix] The interlaced mode is not supported for Intel Gen 12 onwards. Disable interlaced mode for DP on Display >= 12. Due to schedule, SRU for OEM kernels first. After these patches are merged to mainline/drmtip kernel, will SRU for generic kernels. [Test Case] 1.Connected two external Monitor to the onboard HDMI/DP port . 2.Boot OS. 2.set mirror mode. (onboard HDMI / onboard DP) 3.check if screen shakes. [Where problems could occur] Low, Remove interlace support for Display >= 12 so it wouldn't cause a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009355] Re: linux-libc-dev is no longer multi-arch safe
** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- 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/2009355 Title: linux-libc-dev is no longer multi-arch safe Status in linux package in Ubuntu: Confirmed Bug description: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/i386/b/binutils/20230305_112702_eba45@/log.gz dpkg: error processing archive /tmp/apt-dpkg-install-9IkDRS/098-linux-libc-dev_6.1.0-16.16_i386.deb (--unpack): trying to overwrite shared '/arch/x86/include/generated/asm/.syscalls_32.h.cmd', which is different from other instances of package linux-libc-dev:i386 I'm not sure why linux-libc-dev_6.1.0-16.16 has files in /arch /install /scripts. But these files are different on different arch (or different build, since it embeds build path) ==> amd64/arch/x86/include/generated/asm/.syscalls_32.h.cmd <== cmd_arch/x86/include/generated/asm/syscalls_32.h := sh /build/linux-1t584m/linux-6.1.0/scripts/syscalltbl.sh --abis i386 /build/linux-1t584m/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl arch/x86/include/generated/asm/syscalls_32.h ==> i386/arch/x86/include/generated/asm/.syscalls_32.h.cmd <== cmd_arch/x86/include/generated/asm/syscalls_32.h := sh /build/linux-f194dh/linux-6.1.0/scripts/syscalltbl.sh --abis i386 /build/linux-f194dh/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl arch/x86/include/generated/asm/syscalls_32.h To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009355/+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 2009449] Re: linux-libc-dev creates top level directories /arch /install /include
*** This bug is a duplicate of bug 2009355 *** https://bugs.launchpad.net/bugs/2009355 (Want to add the duplication link, but mistakenly click the security button) ** This bug has been marked a duplicate of bug 2009355 linux-libc-dev is no longer multi-arch safe -- 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/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Confirmed Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf InstallationDate: Installed on 2015-12-23 (2630 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) IwConfig: lono wireless extensions. enp0s3no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device
[Kernel-packages] [Bug 2008951] Re: Ubuntu 22.04 on Lenovo Legion 5 Laptop occasional boot freeze and and unexpected reboots
Comment #3 looks like a freeze in the NVIDIA open kernel driver. ** Package changed: ubuntu => nvidia-graphics-drivers-525 (Ubuntu) ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2008951 Title: Ubuntu 22.04 on Lenovo Legion 5 Laptop occasional boot freeze and and unexpected reboots Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: Problem occurs with "ubuntu-drivers install" beforehand, and in trying to resolve resorted to manual nvidia drivers install approach. Problem recurs anyway. Now not sure is nvidia issue as sometimes bluetooth does not get recognized as now (in this session). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 1 18:33:58 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-18 (103 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2008951/+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 2001914] Re: [i915] [drm] GPU HANG: ecode 12:0:00000000
** Summary changed: - The gpu hangs and is not possible to work with GPU-envioronment + [i915] [drm] GPU HANG: ecode 12:0: ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2001914 Title: [i915] [drm] GPU HANG: ecode 12:0: Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Confirmed Bug description: When I open the terminal or just browsing, gnom sometimes freezes for a second, but sometimes restart the machine is necessary. The log is: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm]i915 :00:02.0: [drm] GPU HANG: ecode 12:0: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC SLPC: enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: last_user_time (2748010) is greater than comparison timestamp (2743419). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 0xc0003c appears to be one of the offending windows with a timestamp of 2748010. Working around... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Jan 5 12:25:49 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-02 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001914/+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 2008951] [NEW] Ubuntu 22.04 on Lenovo Legion 5 Laptop occasional boot freeze and and unexpected reboots
You have been subscribed to a public bug: Problem occurs with "ubuntu-drivers install" beforehand, and in trying to resolve resorted to manual nvidia drivers install approach. Problem recurs anyway. Now not sure is nvidia issue as sometimes bluetooth does not get recognized as now (in this session). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 1 18:33:58 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-18 (103 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 amdgpu apport-bug jammy -- Ubuntu 22.04 on Lenovo Legion 5 Laptop occasional boot freeze and and unexpected reboots https://bugs.launchpad.net/bugs/2008951 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 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 1970957] Re: suspend problem
+1 for turning off 'Always on USB', seems to work for me on Ubuntu 22.04.2 LTS. This bug also affects me, using a Lenovo ThinkPad P16s Gen 1 with an amd 6850u. -- 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/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006077] Re: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares
Verify passed by checking the linux/5.15.0-68.75 kernel in -proposed dmesg, The "[\_SB.PR00._CPC], AE_NOT_FOUND" is gone and the dinamic ssdt table(such as ApHwp etc.) are loaded. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006077 Title: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Some machines which have dynamically loaded SSDT tables, will not be loaded and get the CPPC not worked. [Fix] Fix the regression by some load supports for CPPC from an SSDT dynamically when _OSC reports CPPC v2. And make the "[\_SB.PR00._CPC], AE_NOT_FOUND" gone. [Test] Verified all the OEM dynamic table loaded or the "[\_SB.PR00._CPC], AE_NOT_FOUND" error exist or not on demesg . [Where problems could occur] Low risk, It only helps to CPPC support loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008245] Re: zfs-dkms: support linux 6.2
This bug was fixed in the package zfs-linux - 2.1.9-2ubuntu1 --- zfs-linux (2.1.9-2ubuntu1) lunar; urgency=medium * Merge from Debian Unstable (LP: #2008245), remaining changes: - debian/control: + drop dependencies on "zfs-modules | zfs-dkms" such that all packages can be installed in containers, on hosts that have zfs module loaded. + change initramfs/dracut packages to only Ubuntu-64bit architectures, zfs is not well supported on 32bit arches - debian/rules: + enforce abi check on Ubuntu amd64 - debian/tests/control: + reduce testing to smoketest only + Ubuntu Kernel regression testing covers zfs testsuite - debian/patches: + Apply Ubuntu patchset to integrate with zsys -- Andrea Righi Fri, 03 Mar 2023 07:18:14 + ** Changed in: zfs-linux (Ubuntu Lunar) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2008245 Title: zfs-dkms: support linux 6.2 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Lunar: Fix Released Bug description: [Impact] The current version of zfs-dkms available in lunar fails to build with kernels >= 6.2, reporting the following configure error: configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.7-1ubuntu1 *** Compatible Kernels: 3.10 - 6.0 [Test case] $ apt install zfs-dkms [Fix] Resync with zfs version in Debian (2.1.9) and apply the usual Ubuntu specific changes. [Regression potential] We may experience zfs regressions due to a new major version, especially on zfs volumes / filesystems created with the previous versions. However this goes in pair with the new major kernel version and we need to upgrade the version of zfs to properly support the new kernel 6.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2008245/+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 2002842] Re: UBSAN: array-index-out-of-bounds in drivers/scsi/megaraid/megaraid_sas_fp.c:151:32
There is a ticket upstream that might be related to this issue : https://bugzilla.kernel.org/show_bug.cgi?id=215943 >From the comments, there is possibly a patch merged in kernel 6.1 to fix this problem. -- 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/2002842 Title: UBSAN: array-index-out-of-bounds in drivers/scsi/megaraid/megaraid_sas_fp.c:151:32 Status in linux package in Ubuntu: Confirmed Bug description: I'm getting UBSAN complains every boot, this issue exists for years, but I was lazy to report it as everything works. However, not sure if it is security issue: [1.866789] [1.866992] [1.867187] UBSAN: array-index-out-of-bounds in /build/linux-oKJrrr/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:151:32 [1.867454] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]' [1.867608] CPU: 0 PID: 203 Comm: kworker/0:1H Tainted: G I 5.15.0-58-generic #64-Ubuntu [1.867612] Hardware name: Gigabyte Technology Co., Ltd. X299 UD4/X299 UD4-CF, BIOS F6p 12/06/2021 [1.867614] Workqueue: kblockd blk_mq_run_work_fn [1.867620] Call Trace: [1.867621] [1.867623] show_stack+0x52/0x5c [1.867628] dump_stack_lvl+0x4a/0x63 [1.867635] dump_stack+0x10/0x16 [1.867641] ubsan_epilogue+0x9/0x49 [1.867647] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.867653] ? _printk+0x58/0x73 [1.867658] MR_GetPhyParams+0x487/0x700 [megaraid_sas] [1.867675] MR_BuildRaidContext+0x402/0xb50 [megaraid_sas] [1.867693] megasas_build_ldio_fusion+0x5b9/0x9a0 [megaraid_sas] [1.867710] megasas_build_io_fusion+0x412/0x450 [megaraid_sas] [1.867725] megasas_build_and_issue_cmd_fusion+0xa5/0x380 [megaraid_sas] [1.867739] megasas_queue_command+0x1be/0x200 [megaraid_sas] [1.867753] ? ktime_get+0x43/0xc0 [1.867759] scsi_dispatch_cmd+0x93/0x200 [1.867764] scsi_queue_rq+0x2d5/0x690 [1.867771] blk_mq_dispatch_rq_list+0x13c/0x680 [1.867779] ? sbitmap_get+0x1/0xe0 [1.867786] __blk_mq_do_dispatch_sched+0xba/0x2e0 [1.867792] blk_mq_do_dispatch_sched+0x40/0x70 [1.867797] __blk_mq_sched_dispatch_requests+0x105/0x150 [1.867802] blk_mq_sched_dispatch_requests+0x35/0x70 [1.867806] __blk_mq_run_hw_queue+0x34/0xc0 [1.867812] blk_mq_run_work_fn+0x1f/0x30 [1.867818] process_one_work+0x228/0x3d0 [1.867823] worker_thread+0x53/0x420 [1.867826] ? process_one_work+0x3d0/0x3d0 [1.867830] kthread+0x127/0x150 [1.867836] ? set_kthread_struct+0x50/0x50 [1.867843] ret_from_fork+0x1f/0x30 [1.867852] [1.867853] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: vsukhoml 2725 F pulseaudio /dev/snd/controlC0: vsukhoml 2725 F pulseaudio /dev/snd/controlC1: vsukhoml 2725 F pulseaudio /dev/snd/controlC2: vsukhoml 2725 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jan 13 11:12:10 2023 InstallationDate: Installed on 2020-05-03 (985 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X299 UD4 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-58-generic root=UUID=9f617cba-f115-4ee3-ad8e-de95fcd2ca03 ro quiet splash nomodeset RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-07-15 (182 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6p dmi.board.asset.tag: Default string dmi.board.name: X299 UD4-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 2006370] Re: [nouveau] Terribly flicking and blicking HDMI-port display
** Changed in: linux (Ubuntu) Status: Confirmed => 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/2006370 Title: [nouveau] Terribly flicking and blicking HDMI-port display Status in linux package in Ubuntu: Incomplete Bug description: Hi, I have HP15 Gaming Pavilion bought 2-3 years ago. I had Windows 10 before (not it is the second OS due to this bug [I can't use Ubuntu with this bug]), and Win 10 has no problems. No solution [that I found over the internet] worked. I have to have at least two displays. My connection technology: PC HDMI output -> HDMI-VGA(+audio) transmitter -> LED 20' Display (external monitor) Win 10 have never had any problems with it (it has good drivers). When I add any input to the second screen - it blinks and flickers so terrible that I can see nothing - a white screen problem. If I do nothing - it will turn to some picture in some time, but if I make any action at the second monitor - flickering and the white screen problem appears again. I think these are drivers. I tested the equipment in Win 10 after I found this bug - and it works perfectly (so, the hardware is good). It is a typical notebook and this bug is crucial. I use two monitors to type codes and work on PC. I can't survive with just one monitor. Right now when I am typing you this message the second monitor became white again for quite a long time (I did nothing there). I hope you will be able to fix this bug :) Best wishes, Alex, Prague, Czech Republic, EU PS: When typing this message I found another bug compared to MS Windows. When making screenshots (Alt/Shift + Print Screen) - it makes perfect picture even when you actually have the second monitor white all the time (so the screenshot is not how it is). I made an actual photo (and deleted some parts of the background not related to the monitors/computer). You can see a white screen, but the screenshot shows a "perfect world" with a perfect picture which is not how it is on the screen. Windows, on the contrary, makes actual screenshots. And Win 10 test of this monitor never have this white screen or any other monitor problems. Moreover, when the monitors stops to be white for a second it depicts different picture (more terrible image; it is disproportional, with font heavily readable, but the screenshot functions shows an "ideal world" a user can never see :) I made this detailed description to help Ubuntu. I think the project is great in concept, but poor in realization. Such bugs make it impossible for users to use Ubuntu (who can work on just one monitor? Who do not wish to make screenshots with what he/she actually sees on the monitor [rather than modified images with the pictures users do not actually see]?). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 6 19:45:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117M [103c:87b1] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87b1] InstallationDate: Installed on 2023-02-04 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=30f188c5-d67f-4f68-ba6d-6995864ff95e ro quiet splash loglevel=3 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2021 dmi.bios.release: 15.25 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87B1 dmi.board.vendor: HP dmi.board.version: 31.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.23 dmi.modalias: dmi:bvnAMI:bvrF.25:bd08/18/2021:br15.25:efr31.23:svnHP:pnHPPavilionGamingLaptop15-ec1xxx:pvr:rvnHP:rn87B1:rvr31.23:cvnHP:ct10:cvrChassisVersion:sku1N3L2EA#ACB: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec1xxx dmi.product.sku: 1N3L2EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
[Kernel-packages] [Bug 2007530] Re: Built-in camera device dies after runtime suspended
Fixed in BIOS. ** Changed in: hwe-next Status: New => Invalid ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => 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/2007530 Title: Built-in camera device dies after runtime suspended Status in HWE Next: Invalid Status in linux 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-oem-6.1 source package in Jammy: Invalid Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When the xHC host controller[1022:1505] is runtime suspended, it can't be waken up and the devices connect to it will be lost. [Fix] Add the xHC ID to an existing quirk fixes the issue https://www.spinics.net/lists/kernel/msg4689370.html [Test] Verified by me and QA. [Where problems could occur] It disables disable a bit which is enable in sparse controller and do reset on resume. The impact should be minimun. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007530/+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 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs
** Tags added: fixed-in-linux-6.1 fixed-upstream -- 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/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. UPDATE: See attached log. This may not be a case of the laptop failing to resume, but a case of the laptop not suspending properly! What happened was the following. When packing in my things, I closed the laptop and put it in my bag. At home I picked it up again, and immediately noticed how unusually hot it was. The laptop didn't resume properly on opening the lid, but was frozen as before. So this might actually be a case of the laptop FAILING TO SUSPEND properly, instead of failing to wake up. UPDATE: I just noticed the battery was down to the low 40% from at least 80%. Given the temperature on opening the laption I suspect the CPU has been working hard during "sleep time". EDIT: Changed title after confirmation for earlier Ryzen 5000 CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
HDMI video does not work for me on this kernel. 5.19.0-31 works fine. I'm running ubuntu DISTRIB_RELEASE=22.10 on and HP Fury 16 G9 laptop with 12th Gen Intel(R) Core(TM) i9-12950HX. It also causes the fan to come on. Logging in is very slugging. 5.19.0.31 is very responsive and does not force the fan on under casual use. -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+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 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system
Ubuntu 22.04 users can install this kernel to get the fix: sudo apt install linux-oem-22.04c ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Fix Released ** Changed in: linux-oem-6.1 (Ubuntu) Importance: Undecided => High -- 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/1995956 Title: amdgpu no-retry page fault resulting in black screen and unresponsive system Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Triaged Status in linux-oem-6.1 package in Ubuntu: Fix Released Status in linux source package in Kinetic: Triaged Bug description: When using Skype in snap, amdgpu crashed, resulting in black screen and unresponsive system. Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu firmware. Affected laptop is T14 with Ryzen 5850U. Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 This happens in a loop and eventually leads to GPU reset, which fails. Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=211509,
[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system
Sorry, I was looking at the wrong commit. The fix is not in 5.19 yet. It should look like this: https://gitlab.freedesktop.org/agd5f/linux/-/commit/7259d1c92f03d27d913f2c35968e70117e6fc98f https://gitlab.freedesktop.org/agd5f/linux/-/commit/8a1a7d7445c925acc6aec4de163ff91616653aaa ** Changed in: linux-hwe-5.19 (Ubuntu) Status: Fix Released => Triaged ** Changed in: linux-hwe-5.19 (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu Kinetic) Status: Fix Released => 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/1995956 Title: amdgpu no-retry page fault resulting in black screen and unresponsive system Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Triaged Status in linux-oem-6.1 package in Ubuntu: Fix Released Status in linux source package in Kinetic: Triaged Bug description: When using Skype in snap, amdgpu crashed, resulting in black screen and unresponsive system. Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu firmware. Affected laptop is T14 with Ryzen 5850U. Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 This
[Kernel-packages] [Bug 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently
If the firmware still crash, please try the latest release from upstream by. $ sudo apt install git make autoconf dkms $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git $ cd backport-iwlwifi/ $ git checkout release/core72 $ make $ sudo make install $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git $ cd linux-firmware $ git checkout iwlwifi-fw-2023-03-06 $ sudo cp iwlwifi-so-a0-gf-a0-74.ucode /lib/firmware/ $ sudo cp iwlwifi-so-a0-gf-a0.pnvm /lib/firmware/ $ sudo reboot Check journalctl -k -b, should see info as attachment ** Attachment added: "iwlwifi-core72.log" https://bugs.launchpad.net/ubuntu/+source/oem-somerville-tentacool-meta/+bug/2007875/+attachment/5652221/+files/iwlwifi-core72.log -- 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/2007875 Title: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently Status in linux-firmware package in Ubuntu: Fix Released Status in oem-somerville-tentacool-meta package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in oem-somerville-tentacool-meta source package in Jammy: New Status in linux-firmware source package in Kinetic: Fix Released Status in oem-somerville-tentacool-meta source package in Kinetic: Invalid Status in linux-firmware source package in Lunar: Fix Released Status in oem-somerville-tentacool-meta source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and -73 firmware are supported bug missing. On one user reported issue, this fixes WiFi stability on 5G band. [Fix] New upstreamed firmware revision fixes this issue. [Test Case] 1. Boot hwe-5.19 kernel 2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded 3. Browse the web, usually takes between 1 and 5 minutes 4. Networking will cut out [Where problems could occur] This affects only users need both backport-iwlwifi-dkms and hwe-5.19 kernel on WiFi stability. [Other Info] While Kinetic and above have them all, only Jammy is nominated. == original bug report == I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320). Recently I received some kernel updates, the 5.19 kernel used in 22.10 and a 6.0 oem kernel. Both updates break wifi. It seems to only do so on newer 5.7 GHz access points. 1. Boot latest 6.0 oem kernel 2. Browse the web, usually takes between 1 and 5 minutes. 3. Networking will cut out. Disabling networking and starting again will fix it until it happens again in a few minutes. This will repeat indefinitely, essentially making wireless useless. The attached dmesg log reliably shows up when it fails, showing iwlwifi failing and a (network?) hardware reset request. It witnessed this happen months ago on 22.10, which led me to using the Dell stock 22.04 image. But it seems even the newer OEM kernel is affected. A workaround is to select the older 5.15 kernel in grub. I find on this laptop, one must hit escape precisely 1 second after seeing the Dell logo on boot. Alternatively one could edit /etc/grub/default and set a longer timeout. Let me know if this bug report would be better to go to Dell as a support request instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+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 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently
-- 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/2007875 Title: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently Status in linux-firmware package in Ubuntu: Fix Released Status in oem-somerville-tentacool-meta package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in oem-somerville-tentacool-meta source package in Jammy: New Status in linux-firmware source package in Kinetic: Fix Released Status in oem-somerville-tentacool-meta source package in Kinetic: Invalid Status in linux-firmware source package in Lunar: Fix Released Status in oem-somerville-tentacool-meta source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and -73 firmware are supported bug missing. On one user reported issue, this fixes WiFi stability on 5G band. [Fix] New upstreamed firmware revision fixes this issue. [Test Case] 1. Boot hwe-5.19 kernel 2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded 3. Browse the web, usually takes between 1 and 5 minutes 4. Networking will cut out [Where problems could occur] This affects only users need both backport-iwlwifi-dkms and hwe-5.19 kernel on WiFi stability. [Other Info] While Kinetic and above have them all, only Jammy is nominated. == original bug report == I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320). Recently I received some kernel updates, the 5.19 kernel used in 22.10 and a 6.0 oem kernel. Both updates break wifi. It seems to only do so on newer 5.7 GHz access points. 1. Boot latest 6.0 oem kernel 2. Browse the web, usually takes between 1 and 5 minutes. 3. Networking will cut out. Disabling networking and starting again will fix it until it happens again in a few minutes. This will repeat indefinitely, essentially making wireless useless. The attached dmesg log reliably shows up when it fails, showing iwlwifi failing and a (network?) hardware reset request. It witnessed this happen months ago on 22.10, which led me to using the Dell stock 22.04 image. But it seems even the newer OEM kernel is affected. A workaround is to select the older 5.15 kernel in grub. I find on this laptop, one must hit escape precisely 1 second after seeing the Dell logo on boot. Alternatively one could edit /etc/grub/default and set a longer timeout. Let me know if this bug report would be better to go to Dell as a support request instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+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 2009546] Re: Kinetic update: upstream stable patchset 2023-03-06
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2023-03-06 + from git://git.kernel.org/ -upstream stable patchset 2023-03-06 -from git://git.kernel.org/ + usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init + cifs: fix oops during encryption + nvme-pci: fix doorbell buffer value endianness + nvme-pci: fix mempool alloc size + nvme-pci: fix page size checks + ACPI: resource: do IRQ override on LENOVO IdeaPad + ACPI: resource: do IRQ override on XMG Core 15 + ACPI: resource: do IRQ override on Lenovo 14ALC7 + block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq + ata: ahci: Fix PCS quirk application for suspend + nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition + nvmet: don't defer passthrough commands with trivial effects to the workqueue + fs/ntfs3: Validate BOOT record_size + fs/ntfs3: Add overflow check for attribute size + fs/ntfs3: Validate data run offset + fs/ntfs3: Add null pointer check to attr_load_runs_vcn + fs/ntfs3: Fix memory leak on ntfs_fill_super() error path + fs/ntfs3: Add null pointer check for inode operations + fs/ntfs3: Validate attribute name offset + fs/ntfs3: Validate buffer length while parsing index + fs/ntfs3: Validate resident attribute name + fs/ntfs3: Fix slab-out-of-bounds read in run_unpack + soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 + fs/ntfs3: Validate index root when initialize NTFS security + fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() + fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() + fs/ntfs3: Delete duplicate condition in ntfs_read_mft() + fs/ntfs3: Fix slab-out-of-bounds in r_page + objtool: Fix SEGFAULT + powerpc/rtas: avoid device tree lookups in rtas_os_term() + powerpc/rtas: avoid scheduling in rtas_os_term() + HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint + HID: plantronics: Additional PIDs for double volume key presses quirk + pstore: Properly assign mem_type property + pstore/zone: Use GFP_ATOMIC to allocate zone buffer + hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount + binfmt: Fix error return code in load_elf_fdpic_binary() + ovl: Use ovl mounter's fsuid and fsgid in ovl_link() + ALSA: line6: correct midi status byte when receiving data from podxt + ALSA: line6: fix stack overflow in line6_midi_transmit + pnode: terminate at peers of source + mfd: mt6360: Add bounds checking in Regmap read/write call-backs + md: fix a crash in mempool_free + mm, compaction: fix fast_isolate_around() to stay within boundaries + f2fs: should put a page when checking the summary info + f2fs: allow to read node block after shutdown + mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING + tpm: acpi: Call acpi_put_table() to fix memory leak + tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak + tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak + SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails + kcsan: Instrument memcpy/memset/memmove with newer Clang + media: stv0288: use explicitly signed char + soc: qcom: Select REMAP_MMIO for LLCC driver + kest.pl: Fix grub2 menu handling for rebooting + ktest.pl minconfig: Unset configs instead of just removing them + jbd2: use the correct print format + perf/x86/intel/uncore: Disable I/O stacks to PMU mapping on ICX-D + perf/x86/intel/uncore: Clear attr_update properly + arm64: dts: qcom: sdm845-db845c: correct SPI2 pins drive strength + mmc: sdhci-sprd: Disable CLK_AUTO when the clock is less than 400K + btrfs: fix resolving backrefs for inline extent followed by prealloc + ARM: ux500: do not directly dereference __iomem + arm64: dts: qcom: sdm850-lenovo-yoga-c630: correct I2C12 pins drive strength + selftests: Use optional USERCFLAGS and USERLDFLAGS + PM/devfreq: governor: Add a private governor_data for governor + cpufreq: Init completion before kobject_init_and_add() + ALSA: patch_realtek: Fix Dell Inspiron Plus 16 + ALSA: hda/realtek: Apply dual codec fixup for Dell Latitude laptops + fs: dlm: fix sock release if listen
[Kernel-packages] [Bug 2009546] [NEW] Kinetic update: upstream stable patchset 2023-03-06
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: upstream stable patchset 2023-03-06 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Kinetic) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009546 Title: Kinetic update: upstream stable patchset 2023-03-06 Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-03-06 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009546/+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 2009542] [NEW] Can not select HDMI or Displayport as audio output device.
Public bug reported: After I installed "linux-image-5.19.0-35-generic" package, I can not select HDMI or Displayport as audio output device in gnome setting. When I am using "linux-image-5.19.0-32-generic" package, I can select that. My PC also have S/PDIF as audio output device, I can select it. My environment is follows. Description:Ubuntu 22.04.2 LTS Release:22.04 Graphics board: Radeon RX6600 Graphics driver:amdgpu ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New -- 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/2009542 Title: Can not select HDMI or Displayport as audio output device. Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After I installed "linux-image-5.19.0-35-generic" package, I can not select HDMI or Displayport as audio output device in gnome setting. When I am using "linux-image-5.19.0-32-generic" package, I can select that. My PC also have S/PDIF as audio output device, I can select it. My environment is follows. Description: Ubuntu 22.04.2 LTS Release: 22.04 Graphics board: Radeon RX6600 Graphics driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009542/+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 added: seg -- 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed 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 Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 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.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware
[Kernel-packages] [Bug 2009269] Re: Nvidia MX350 card dissapears on ubuntu kernel 5.19.0-35-generic update
My bad, this ticket should be closed, i found the root cause. Looks like due an internet shortage linux-modules-nvidia-525-generic- hwe-22.04:amd64 5.19.0-35.36 was not completely downloaded, so it didn't installed the corresponding kernel module and the drivers package into the kernel version 35. Running the software updater noticed me that a pending update was not completely installed. Letting it manage the updates solved the problem, i was updating always the system packages by the updates popup. For the future let the user know in the popup that there are pending / broken packages and that the user should attempt an clean (when i excecuted that manually one of the buttons said continue and the other said something as clean / dist upgrade, not sure as i use the system in spanish). -- 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/2009269 Title: Nvidia MX350 card dissapears on ubuntu kernel 5.19.0-35-generic update Status in linux package in Ubuntu: Confirmed Bug description: After upgrading the kernel to the version 5.19.0-35-generic the notebook is not recognizing that there is present in it a Nvidia card, so it doesn't tries to load any modules for it and it even isn't listed in lspci command. The Nvidia Card is an MX350 dedicated graphics. As a side note it detects ok the integrated one (AMD integrated in the ryzen apu, RADV renoir) This is not happening when i boot with older versions of the kernel like 5.19.0-31-generic. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leo2402 F wireplumber /dev/snd/controlC0: leo2402 F wireplumber /dev/snd/seq:leo2399 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 12:16:00 2023 InstallationDate: Installed on 2022-10-31 (123 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: ASUSTeK COMPUTER INC. ZenBook UX434IQ_Q407IQ ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=b5a4c9e8-00ac-4ef5-9c8c-dc552f8b9e69 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434IQ_Q407IQ.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434IQ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434IQ_Q407IQ.302:bd07/10/2020:br5.16:svnASUSTeKCOMPUTERINC.:pnZenBookUX434IQ_Q407IQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434IQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX434IQ_Q407IQ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-fde-5.15/5.15.0.1035.42~20.04.1.14)
All autopkgtests for the newly accepted linux-meta-azure-fde-5.15 (5.15.0.1035.42~20.04.1.14) for focal have finished running. The following regressions have been reported in tests triggered by the package: lttng-modules/2.12.5-1ubuntu2~20.04.4 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64) nvidia-graphics-drivers-525/525.85.05-0ubuntu0.20.04.1 (amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure-fde-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009065] Re: overlayfs mounts as R/O over idmapped mount
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
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/2009065
Title:
overlayfs mounts as R/O over idmapped mount
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.19 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-5.19 source package in Jammy:
In Progress
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.19 source package in Kinetic:
Invalid
Bug description:
Reproducer:
create unprivileged LXC container
$ lxc launch ubuntu:22.04 idmap-test
$ lxc exec idmap-test bash
check that root is idmapped by:
$ cat /proc/self/mountinfo | grep idmap
780 675 8:1 /var/snap/lxd/common/lxd/storage-
pools/default/containers/idmap-test/rootfs / rw,relatime,idmapped
shared:323 master:319 - ext4 /dev/sda1 rw,discard,errors=remount-ro
$ mkdir {work,upper,lower,ovl}
$ mount -t overlay overlay -o lowerdir=lower,upperdir=upper,workdir=work ovl
$ touch ovl/test
touch: cannot touch 'ovl/test': Read-only file system
The problem is in __vfs_removexattr_noperm() function that called from
ovl_workdir_create().
In dmesg I can see an error:
overlayfs: failed to create directory work/work (errno: 1); mounting read-only
Reproducible on:
# uname -a
Linux ubuntu 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan
30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
Suspicious commit:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/fs/overlayfs/overlayfs.h?h=Ubuntu-hwe-5.19-5.19.0-32.33_22.04.1=3418435738af5730918fafbdfe2905a98ce2ef05
Chunk:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(_user_ns, dentry, name, value, size,
flags);
+ inode_unlock(inode);
should be:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(ovl_upper_mnt_userns(ofs), dentry, name,
value, size, flags);
+ inode_unlock(inode);
I'll send a patch soon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009065/+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 2008523] Re: Make kexec work by default on secureboot systems
This bug was fixed in the package kexec-tools - 1:2.0.22-2ubuntu3 --- kexec-tools (1:2.0.22-2ubuntu3) lunar; urgency=medium * Change kexec default from --kexec-syscall to --kexec-syscall-all to make kexec work on secureboot systems by default. LP: #2008523 -- Dimitri John Ledkov Fri, 24 Feb 2023 20:47:39 + ** Changed in: kexec-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2008523 Title: Make kexec work by default on secureboot systems Status in kexec-tools package in Ubuntu: Fix Released Bug description: Make kexec work by default on secureboot systems Lots of people are confused by kexec failing on secureboot systems, without realising that on Ubuntu one needs to use the option to use a modern syscall that works on secureboot systems since like forever. Let's make the mode that works the default one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/2008523/+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 2009522] [NEW] Upgrade Kernel 5.19.0-35-generic [Sound Blaster Recon3D / Z-Series] not detected anymore
Public bug reported: Upgrade Kernel 5.19.0-35-generic [Sound Blaster Recon3D / Z-Series] not detected anymore Operating System: Kubuntu 22.10 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i9-9900KF CPU @ 3.60GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z390 UD See also https://askubuntu.com/questions/1457574/upgrade- kernel-5-19-0-35-generic-sound-blaster-recon3d-z-series-not-detected ** Affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New -- 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/2009522 Title: Upgrade Kernel 5.19.0-35-generic [Sound Blaster Recon3D / Z-Series] not detected anymore Status in linux-hwe-5.19 package in Ubuntu: New Bug description: Upgrade Kernel 5.19.0-35-generic [Sound Blaster Recon3D / Z-Series] not detected anymore Operating System: Kubuntu 22.10 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i9-9900KF CPU @ 3.60GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z390 UD See also https://askubuntu.com/questions/1457574/upgrade- kernel-5-19-0-35-generic-sound-blaster-recon3d-z-series-not-detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009522/+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 2008832] Re: Kinetic update: upstream stable patchset 2023-02-28
** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008832 Title: Kinetic update: upstream stable patchset 2023-02-28 Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: 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: upstream stable patchset 2023-02-28 Ported from the following upstream stable releases: v5.15.86, v6.0.16 from git://git.kernel.org/ [Massive list of 883 included patches is Comment #1 below.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008832/+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 2009287] Re: When using this kernel, the HDMI audio output dissapears
I thought I could fix it with a new install and therefore tried installing a daily build of 23.04. The live USB audio worked, and audio was working on first boot of the new system, but after running updates and rebooting, sound was broken again. At the time that I tried this (last night) I wasn't yet aware that it was a kernel issue, so I wasn't watching logs or kernel versions or anything. If needed, I can repeat the test and retrieve any logs that you need, but I'm back to 22.04.2 for the time being, now that I know the workaround. -- 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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: Confirmed Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009287/+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 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently
Unfortunately, I had the same issue again today. [88124.716563] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [88124.716667] iwlwifi :00:14.3: Start IWL Error Log Dump: [88124.716668] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [88124.716670] iwlwifi :00:14.3: Loaded firmware version: 73.35c0a2c6.0 so-a0-gf-a0-73.ucode [88124.716672] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [88124.716673] iwlwifi :00:14.3: 0x8210 | trm_hw_status0 [88124.716674] iwlwifi :00:14.3: 0x | trm_hw_status1 [88124.716675] iwlwifi :00:14.3: 0x004DA772 | branchlink2 [88124.716676] iwlwifi :00:14.3: 0x00013D26 | interruptlink1 [88124.716677] iwlwifi :00:14.3: 0x00013D26 | interruptlink2 [88124.716678] iwlwifi :00:14.3: 0xB860 | data1 [88124.716679] iwlwifi :00:14.3: 0x0010 | data2 [88124.716680] iwlwifi :00:14.3: 0x | data3 [88124.716681] iwlwifi :00:14.3: 0xCE0153BE | beacon time [88124.716682] iwlwifi :00:14.3: 0x5D30FC49 | tsf low [88124.716683] iwlwifi :00:14.3: 0x08DB | tsf hi [88124.716683] iwlwifi :00:14.3: 0x | time gp1 [88124.716684] iwlwifi :00:14.3: 0xBABFA40A | time gp2 [88124.716685] iwlwifi :00:14.3: 0x0001 | uCode revision type [88124.716686] iwlwifi :00:14.3: 0x0049 | uCode version major [88124.716687] iwlwifi :00:14.3: 0x35C0A2C6 | uCode version minor [88124.716688] iwlwifi :00:14.3: 0x0370 | hw version [88124.716689] iwlwifi :00:14.3: 0x00480002 | board version [88124.716690] iwlwifi :00:14.3: 0x80D7FC03 | hcmd [88124.716691] iwlwifi :00:14.3: 0x2402 | isr0 [88124.716691] iwlwifi :00:14.3: 0x | isr1 [88124.716692] iwlwifi :00:14.3: 0x48F80002 | isr2 [88124.716693] iwlwifi :00:14.3: 0x00C34C0C | isr3 [88124.716694] iwlwifi :00:14.3: 0x | isr4 [88124.716695] iwlwifi :00:14.3: 0x0557001C | last cmd Id [88124.716696] iwlwifi :00:14.3: 0xB860 | wait_event [88124.716696] iwlwifi :00:14.3: 0x0080 | l2p_control [88124.716697] iwlwifi :00:14.3: 0x00010034 | l2p_duration [88124.716698] iwlwifi :00:14.3: 0x003F | l2p_mhvalid [88124.716699] iwlwifi :00:14.3: 0x1800 | l2p_addr_match [88124.716700] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel [88124.716701] iwlwifi :00:14.3: 0x | timestamp [88124.716701] iwlwifi :00:14.3: 0xE8D8 | flow_handler [88124.716812] iwlwifi :00:14.3: Start IWL Error Log Dump: [88124.716812] iwlwifi :00:14.3: Transport status: 0x004A, valid: 7 [88124.716813] iwlwifi :00:14.3: 0x20003463 | ADVANCED_SYSASSERT [88124.716815] iwlwifi :00:14.3: 0x | umac branchlink1 [88124.716815] iwlwifi :00:14.3: 0x8045F8F8 | umac branchlink2 [88124.716816] iwlwifi :00:14.3: 0xC00814F8 | umac interruptlink1 [88124.716817] iwlwifi :00:14.3: 0x | umac interruptlink2 [88124.716818] iwlwifi :00:14.3: 0x5D30FC3B | umac data1 [88124.716819] iwlwifi :00:14.3: 0xBABFA3FB | umac data2 [88124.716820] iwlwifi :00:14.3: 0xA34AC3D6 | umac data3 [88124.716821] iwlwifi :00:14.3: 0x0049 | umac major [88124.716821] iwlwifi :00:14.3: 0x35C0A2C6 | umac minor [88124.716822] iwlwifi :00:14.3: 0xBABFA403 | frame pointer [88124.716823] iwlwifi :00:14.3: 0xC0885DF8 | stack pointer [88124.716824] iwlwifi :00:14.3: 0x0037010D | last host cmd [88124.716825] iwlwifi :00:14.3: 0x | isr status reg [88124.716864] iwlwifi :00:14.3: IML/ROM dump: [88124.716865] iwlwifi :00:14.3: 0x0B03 | IML/ROM error/state [88124.716873] iwlwifi :00:14.3: 0x7159 | IML/ROM data1 [88124.716882] iwlwifi :00:14.3: 0x0080 | IML/ROM WFPM_AUTH_KEY_0 [88124.716888] iwlwifi :00:14.3: Fseq Registers: [88124.716891] iwlwifi :00:14.3: 0x6000 | FSEQ_ERROR_CODE [88124.716893] iwlwifi :00:14.3: 0x803E0001 | FSEQ_TOP_INIT_VERSION [88124.716896] iwlwifi :00:14.3: 0x00190002 | FSEQ_CNVIO_INIT_VERSION [88124.716899] iwlwifi :00:14.3: 0xA652 | FSEQ_OTP_VERSION [88124.716902] iwlwifi :00:14.3: 0x0003 | FSEQ_TOP_CONTENT_VERSION [88124.716905] iwlwifi :00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN [88124.716907] iwlwifi :00:14.3: 0x00080400 | FSEQ_CNVI_ID [88124.716910] iwlwifi :00:14.3: 0x00400410 | FSEQ_CNVR_ID [88124.716913] iwlwifi :00:14.3: 0x00080400 | CNVI_AUX_MISC_CHIP [88124.716920] iwlwifi :00:14.3: 0x00400410 | CNVR_AUX_MISC_CHIP [88124.716964] iwlwifi :00:14.3: 0x9061 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [88124.716972] iwlwifi :00:14.3: 0x0061 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [88124.717162] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 4 fired (delay=0ms). [88124.717168] ieee80211 phy0: Hardware restart was requested [88202.645822] usb 3-1.2: USB disconnect, device number 21 [88856.851319] perf: interrupt took too long (3195 > 3173), lowering
[Kernel-packages] [Bug 2009269] Re: Nvidia MX350 card dissapears on ubuntu kernel 5.19.0-35-generic update
** Summary changed: - Nvidia MX350 card dissapears on ubuntu kernel update + Nvidia MX350 card dissapears on ubuntu kernel 5.19.0-35-generic update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009269 Title: Nvidia MX350 card dissapears on ubuntu kernel 5.19.0-35-generic update Status in linux package in Ubuntu: Confirmed Bug description: After upgrading the kernel to the version 5.19.0-35-generic the notebook is not recognizing that there is present in it a Nvidia card, so it doesn't tries to load any modules for it and it even isn't listed in lspci command. The Nvidia Card is an MX350 dedicated graphics. As a side note it detects ok the integrated one (AMD integrated in the ryzen apu, RADV renoir) This is not happening when i boot with older versions of the kernel like 5.19.0-31-generic. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leo2402 F wireplumber /dev/snd/controlC0: leo2402 F wireplumber /dev/snd/seq:leo2399 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 12:16:00 2023 InstallationDate: Installed on 2022-10-31 (123 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: ASUSTeK COMPUTER INC. ZenBook UX434IQ_Q407IQ ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=b5a4c9e8-00ac-4ef5-9c8c-dc552f8b9e69 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434IQ_Q407IQ.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434IQ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434IQ_Q407IQ.302:bd07/10/2020:br5.16:svnASUSTeKCOMPUTERINC.:pnZenBookUX434IQ_Q407IQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434IQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX434IQ_Q407IQ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009269/+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 2008142] Re: bcmwl driver not installed
Sure, this is the scenario that we were considering for handling of MOK key enrollment, which isn't implemented yet. I think something else may be going on though. With the 22.04.2 desktop ISO, I can go to a command line and "sudo ubuntu-drivers install", and when it's done I have a wireless interface. I cannot do the same with lunar desktop dailies, instead I get the "All the available drivers are already installed" comment. "mokutil --sb-state" reports "This system doesn't support Secure Boot". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to broadcom-sta in Ubuntu. https://bugs.launchpad.net/bugs/2008142 Title: bcmwl driver not installed Status in ubuntu-desktop-installer: New Status in broadcom-sta package in Ubuntu: New Status in subiquity package in Ubuntu: New Status in broadcom-sta source package in Lunar: New Status in subiquity source package in Lunar: New Bug description: I was testing an installation in qemu and shared a broadcom wireless device with the virtual machine and the drivers for it were not installed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-desktop-installer (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 16:23:38 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-desktop-installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2008142/+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
We see this problem too on focal clients with ans without HWE. The server seems to be not affected. Downgrading the clients to 5.15.0-60 or 5.4.0-139 solves the problem here. Best regards. -- 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed 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 Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 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.modalias:
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
Hello, We have the same behavior on 22.04 and 18.04 servers. This behavior affect us on different on many of our customers web servers with different platforms AWS, Azure and Nutanix (KVM virt) VMs. The used kernel was : linux-image-5.15.0-67-generic linux-image-5.4.0-1097-aws linux-image-5.4.0-1104-azure We have also now booted our web servers on an older kernel version and the problem was mostly gone. We have also tried with the 5.15.0-68-generic on a test server on the https://launchpad.net/%7Ecanonical-kernel-team/+archive/ubuntu/ppa this issue affect also this next kernel. Best Regards, -- 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed 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 Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
Same symptoms here. In our case, five 22.04LTS servers with the 5.15.0-60-generic kernel running a web service, all five with an NFS-mounted volume. After updating some of them with the 5.15.0-67-generic kernel, the traffic on the interface with which the NFS server is accessed increases for no apparent reason. Both output and input packets per second go from about 2k/s to a continuous 12k/s. The context switch rate per second increases by the same ratio. As a result, operations against the NFS volume are slowed down and the user experience is noticeably worse. In the meantime, systems running 5.15.0-60-generic are working as usual. As in the case of the reporter, booting the systems with 5.15.0-60-generic returns us to the original state. -- 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed 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':
[Kernel-packages] [Bug 2009496] Re: Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic.
** Description changed: Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic. - My laptop is under `Software Rendering`, after I upgraded Ubuntu 22.10 - to 23.04, the brightness adjusting is unavailable and my monitor is much - bright. However I change the Kernel to `linux-image-5.19.0-35-generic`, - the backlight adjusting works normally, + My laptop is under `Software Rendering`(GPU: llvmpipe (LLVM 15.0.7, 256 + bits)), after I upgraded Ubuntu 22.10 to 23.04, the brightness adjusting + is unavailable and my monitor is much bright. However I change the + Kernel to `linux-image-5.19.0-35-generic`, the backlight adjusting works + normally, The `lshw display` information: $ sudo lshw -c display *-display UNCLAIMED description: VGA compatible controller product: ZX-E C-960 GPU vendor: Zhaoxin physical id: 1 bus info: pci@:00:01.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list configuration: latency=0 resources: memory:c010-c017 memory:a000-bfff memory:c-d *-graphics product: EFI VGA physical id: 2 logical name: /dev/fb0 capabilities: fb configuration: depth=32 resolution=1920,1080 Hope I can get some help. Regards， larryw3i -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2009496 Title: Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic. Status in linux-signed package in Ubuntu: New Bug description: Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic. My laptop is under `Software Rendering`(GPU: llvmpipe (LLVM 15.0.7, 256 bits)), after I upgraded Ubuntu 22.10 to 23.04, the brightness adjusting is unavailable and my monitor is much bright. However I change the Kernel to `linux-image-5.19.0-35-generic`, the backlight adjusting works normally, The `lshw display` information: $ sudo lshw -c display *-display UNCLAIMED description: VGA compatible controller product: ZX-E C-960 GPU vendor: Zhaoxin physical id: 1 bus info: pci@:00:01.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list configuration: latency=0 resources: memory:c010-c017 memory:a000-bfff memory:c-d *-graphics product: EFI VGA physical id: 2 logical name: /dev/fb0 capabilities: fb configuration: depth=32 resolution=1920,1080 Hope I can get some help. Regards， larryw3i To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2009496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-intel-iotg-5.15/5.15.0.1026.31~20.04.18)
All autopkgtests for the newly accepted linux-meta-intel-iotg-5.15 (5.15.0.1026.31~20.04.18) for focal have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.31-0ubuntu9.9 (amd64) linux-intel-iotg-5.15/5.15.0-1026.31~20.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-intel-iotg-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008142] Re: bcmwl driver not installed
With secureboot, the live session install of that module should trigger installer questions w.r.t. MOK key enrollment. Post installer reboot, should trigger MOK interface to complete the mok key enrollment prior to OS loading. Once OS is loaded, the driver should work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to broadcom-sta in Ubuntu. https://bugs.launchpad.net/bugs/2008142 Title: bcmwl driver not installed Status in ubuntu-desktop-installer: New Status in broadcom-sta package in Ubuntu: New Status in subiquity package in Ubuntu: New Status in broadcom-sta source package in Lunar: New Status in subiquity source package in Lunar: New Bug description: I was testing an installation in qemu and shared a broadcom wireless device with the virtual machine and the drivers for it were not installed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-desktop-installer (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 16:23:38 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-desktop-installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2008142/+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 2009496] [NEW] Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic.
Public bug reported: Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic. My laptop is under `Software Rendering`, after I upgraded Ubuntu 22.10 to 23.04, the brightness adjusting is unavailable and my monitor is much bright. However I change the Kernel to `linux-image-5.19.0-35-generic`, the backlight adjusting works normally, The `lshw display` information: $ sudo lshw -c display *-display UNCLAIMED description: VGA compatible controller product: ZX-E C-960 GPU vendor: Zhaoxin physical id: 1 bus info: pci@:00:01.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list configuration: latency=0 resources: memory:c010-c017 memory:a000-bfff memory:c-d *-graphics product: EFI VGA physical id: 2 logical name: /dev/fb0 capabilities: fb configuration: depth=32 resolution=1920,1080 Hope I can get some help. Regards， larryw3i ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Backlight Adjusting doesn't for linux-image-6.1.0-16-generic. + Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic. ** Description changed: - Backlight Adjusting doesn't for linux-image-6.1.0-16-generic. + Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic. My laptop is under `Software Rendering`, after I upgraded Ubuntu 22.10 to 23.04, the brightness adjusting is unavailable and my monitor is much bright. However I change the Kernel to `linux-image-5.19.0-35-generic`, the backlight adjusting works normally, - The `lshw display` information: + The `lshw display` information: $ sudo lshw -c display - *-display UNCLAIMED -description: VGA compatible controller -product: ZX-E C-960 GPU -vendor: Zhaoxin -physical id: 1 -bus info: pci@:00:01.0 -version: 00 -width: 64 bits -clock: 33MHz -capabilities: pm msi vga_controller bus_master cap_list -configuration: latency=0 -resources: memory:c010-c017 memory:a000-bfff memory:c-d - *-graphics -product: EFI VGA -physical id: 2 -logical name: /dev/fb0 -capabilities: fb -configuration: depth=32 resolution=1920,1080 + *-display UNCLAIMED + description: VGA compatible controller + product: ZX-E C-960 GPU + vendor: Zhaoxin + physical id: 1 + bus info: pci@:00:01.0 + version: 00 + width: 64 bits + clock: 33MHz + capabilities: pm msi vga_controller bus_master cap_list + configuration: latency=0 + resources: memory:c010-c017 memory:a000-bfff memory:c-d + *-graphics + product: EFI VGA + physical id: 2 + logical name: /dev/fb0 + capabilities: fb + configuration: depth=32 resolution=1920,1080 Hope I can get some help. Regards， larryw3i -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2009496 Title: Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic. Status in linux-signed package in Ubuntu: New Bug description: Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic. My laptop is under `Software Rendering`, after I upgraded Ubuntu 22.10 to 23.04, the brightness adjusting is unavailable and my monitor is much bright. However I change the Kernel to `linux- image-5.19.0-35-generic`, the backlight adjusting works normally, The `lshw display` information: $ sudo lshw -c display *-display UNCLAIMED description: VGA compatible controller product: ZX-E C-960 GPU vendor: Zhaoxin physical id: 1 bus info: pci@:00:01.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list configuration: latency=0 resources: memory:c010-c017 memory:a000-bfff memory:c-d *-graphics product: EFI VGA physical id: 2 logical name: /dev/fb0 capabilities: fb configuration: depth=32 resolution=1920,1080 Hope I can get some help. Regards， larryw3i To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2009496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-fde/5.15.0.1035.42.12)
All autopkgtests for the newly accepted linux-meta-azure-fde (5.15.0.1035.42.12) for jammy have finished running. The following regressions have been reported in tests triggered by the package: lttng-modules/2.13.1-1ubuntu0.22.04.3 (amd64) glibc/2.35-0ubuntu3.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-azure-fde [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009495] [NEW] [Ubuntu 22.04] smc_run does not work, libsmc-preload.so cannot be preloaded
Public bug reported: ---Problem Description--- [Ubuntu 22.04] smc_run does not work, libsmc-preload.so cannot be preloaded === The reason for this is that the aforementioned shared object is installed under: /usr/lib64/libsmc-preload.so Which is AFAICT not what we want, because AFAIU it violates the Debian Policy Manual (https://www.debian.org/doc/debian-policy/ch- opersys.html#s-fhs), and ld.so in Ubuntu has a default search path that understandably does not cover /usr/lib64. Interestingly the upstream Make file does try to detect if we are run on Ubuntu, and choose the install path accordingly. Hereby it relies on "lsb_release -si" returning "Ubuntu", which may or may not be a good idea -- I don't know. In any case if the upstream Makefile does not suit Ubuntu/Debian, then the packager is ought to patch it. Thus in my opinion this is a packaging problem. Contact Information = pa...@de.ibm.com ---uname output--- Linux t3545018.lnxne.boe 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:30:43 UTC 2023 s390x s390x s390x GNU/Linux Machine Type = LPAR ---Debugger--- A debugger is not configured ---Steps to Reproduce--- $ smc_run ping 172.18.39.17 ERROR: ld.so: object 'libsmc-preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. PING 172.18.39.17 (172.18.39.17) 56(84) bytes of data. BTW $ LD_PRELOAD=libsmc-preload.so LD_DEBUG=libs LD_LIBRARY_PATH=/usr/lib64/ ping 172.18.39.17 does work as expected. Userspace tool common name: smc_run The userspace tool has the following bit modes: na Userspace rpm: smc-tools_1.7.0-0ubuntu1_s390x.deb Userspace tool obtained from project website: na *Additional Instructions for pa...@de.ibm.com: -Attach ltrace and strace of userspace application. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-201924 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-201924 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009495 Title: [Ubuntu 22.04] smc_run does not work, libsmc-preload.so cannot be preloaded Status in linux package in Ubuntu: New Bug description: ---Problem Description--- [Ubuntu 22.04] smc_run does not work, libsmc-preload.so cannot be preloaded === The reason for this is that the aforementioned shared object is installed under: /usr/lib64/libsmc-preload.so Which is AFAICT not what we want, because AFAIU it violates the Debian Policy Manual (https://www.debian.org/doc/debian-policy/ch- opersys.html#s-fhs), and ld.so in Ubuntu has a default search path that understandably does not cover /usr/lib64. Interestingly the upstream Make file does try to detect if we are run on Ubuntu, and choose the install path accordingly. Hereby it relies on "lsb_release -si" returning "Ubuntu", which may or may not be a good idea -- I don't know. In any case if the upstream Makefile does not suit Ubuntu/Debian, then the packager is ought to patch it. Thus in my opinion this is a packaging problem. Contact Information = pa...@de.ibm.com ---uname output--- Linux t3545018.lnxne.boe 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:30:43 UTC 2023 s390x s390x s390x GNU/Linux Machine Type = LPAR ---Debugger--- A debugger is not configured ---Steps to Reproduce--- $ smc_run ping 172.18.39.17 ERROR: ld.so: object 'libsmc-preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. PING 172.18.39.17 (172.18.39.17) 56(84) bytes of data. BTW $ LD_PRELOAD=libsmc-preload.so LD_DEBUG=libs LD_LIBRARY_PATH=/usr/lib64/ ping 172.18.39.17 does work as expected. Userspace tool common name: smc_run The userspace tool has the following bit modes: na Userspace rpm: smc-tools_1.7.0-0ubuntu1_s390x.deb Userspace tool obtained from project website: na *Additional Instructions for pa...@de.ibm.com: -Attach ltrace and strace of userspace application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009495/+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 2009495] [NEW] [Ubuntu 22.04] smc_run does not work, libsmc-preload.so cannot be preloaded
You have been subscribed to a public bug: ---Problem Description--- [Ubuntu 22.04] smc_run does not work, libsmc-preload.so cannot be preloaded === The reason for this is that the aforementioned shared object is installed under: /usr/lib64/libsmc-preload.so Which is AFAICT not what we want, because AFAIU it violates the Debian Policy Manual (https://www.debian.org/doc/debian-policy/ch- opersys.html#s-fhs), and ld.so in Ubuntu has a default search path that understandably does not cover /usr/lib64. Interestingly the upstream Make file does try to detect if we are run on Ubuntu, and choose the install path accordingly. Hereby it relies on "lsb_release -si" returning "Ubuntu", which may or may not be a good idea -- I don't know. In any case if the upstream Makefile does not suit Ubuntu/Debian, then the packager is ought to patch it. Thus in my opinion this is a packaging problem. Contact Information = pa...@de.ibm.com ---uname output--- Linux t3545018.lnxne.boe 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:30:43 UTC 2023 s390x s390x s390x GNU/Linux Machine Type = LPAR ---Debugger--- A debugger is not configured ---Steps to Reproduce--- $ smc_run ping 172.18.39.17 ERROR: ld.so: object 'libsmc-preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. PING 172.18.39.17 (172.18.39.17) 56(84) bytes of data. BTW $ LD_PRELOAD=libsmc-preload.so LD_DEBUG=libs LD_LIBRARY_PATH=/usr/lib64/ ping 172.18.39.17 does work as expected. Userspace tool common name: smc_run The userspace tool has the following bit modes: na Userspace rpm: smc-tools_1.7.0-0ubuntu1_s390x.deb Userspace tool obtained from project website: na *Additional Instructions for pa...@de.ibm.com: -Attach ltrace and strace of userspace application. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-201924 severity-high targetmilestone-inin--- -- [Ubuntu 22.04] smc_run does not work, libsmc-preload.so cannot be preloaded https://bugs.launchpad.net/bugs/2009495 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 2008946] Re: Focal update: v5.4.230 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008946 Title: Focal update: v5.4.230 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.230 upstream stable release from git://git.kernel.org/ pNFS/filelayout: Fix coalescing test for single DS net/ethtool/ioctl: return -EOPNOTSUPP if we have no phy stats RDMA/srp: Move large values to a new enum for gcc13 f2fs: let's avoid panic if extent_tree is not created wifi: brcmfmac: fix regression for Broadcom PCIe wifi devices Add exception protection processing for vd in axi_chan_handle_err function nilfs2: fix general protection fault in nilfs_btree_insert() efi: fix userspace infinite retry read efivars after EFI runtime services page fault drm/i915/gt: Reset twice ALSA: hda/realtek - Turn on power early xhci-pci: set the dma max_seg_size usb: xhci: Check endpoint is valid before dereferencing it xhci: Fix null pointer dereference when host dies xhci: Add update_hub_device override for PCI xHCI hosts xhci: Add a flag to disable USB3 lpm on a xhci root port level. usb: acpi: add helper to check port lpm capability using acpi _DSM xhci: Detect lpm incapable xHC USB3 roothub ports from ACPI tables prlimit: do_prlimit needs to have a speculation check USB: serial: option: add Quectel EM05-G (GR) modem USB: serial: option: add Quectel EM05-G (CS) modem USB: serial: option: add Quectel EM05-G (RS) modem USB: serial: option: add Quectel EC200U modem USB: serial: option: add Quectel EM05CN (SG) modem USB: serial: option: add Quectel EM05CN modem USB: misc: iowarrior: fix up header size for USB_DEVICE_ID_CODEMERCS_IOW100 misc: fastrpc: Don't remove map on creater_process and device_release misc: fastrpc: Fix use-after-free race condition for maps usb: core: hub: disable autosuspend for TI TUSB8041 comedi: adv_pci1760: Fix PWM instruction handling mmc: sunxi-mmc: Fix clock refcount imbalance during unbind btrfs: fix race between quota rescan and disable leading to NULL pointer deref cifs: do not include page data when checking signature USB: serial: cp210x: add SCALANCE LPE-9000 device id usb: host: ehci-fsl: Fix module alias usb: typec: altmodes/displayport: Add pin assignment helper usb: typec: altmodes/displayport: Fix pin assignment calculation usb: gadget: g_webcam: Send color matching descriptor per frame usb: gadget: f_ncm: fix potential NULL ptr deref in ncm_bitrate() usb-storage: apply IGNORE_UAS only for HIKSEMI MD202 on RTL9210 dt-bindings: phy: g12a-usb3-pcie-phy: fix compatible string documentation serial: pch_uart: Pass correct sg to dma_unmap_sg() dmaengine: tegra210-adma: fix global intr clear serial: atmel: fix incorrect baudrate setup gsmi: fix null-deref in gsmi_get_variable drm/i915: re-disable RC6p on Sandy Bridge drm/amd/display: Fix set scaling doesn's work drm/amd/display: Fix COLOR_SPACE_YCBCR2020_TYPE matrix x86/fpu: Use _Alignof to avoid undefined behavior in TYPE_ALIGN mm/khugepaged: fix collapse_pte_mapped_thp() to allow anon_vma Linux 5.4.230 UBUNTU: Upstream stable to v5.4.230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008946/+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 2008929] Re: Jammy update: v5.15.89 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008929 Title: Jammy update: v5.15.89 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.89 upstream stable release from git://git.kernel.org/ ALSA: control-led: use strscpy in set_led_id() ALSA: hda/realtek - Turn on power early ALSA: hda/realtek: Enable mute/micmute LEDs on HP Spectre x360 13-aw0xxx KVM: arm64: Fix S1PTW handling on RO memslots KVM: arm64: nvhe: Fix build with profile optimization selftests: kvm: Fix a compile error in selftests/kvm/rseq_test.c efi: tpm: Avoid READ_ONCE() for accessing the event log docs: Fix the docs build with Sphinx 6.0 net: stmmac: add aux timestamps fifo clearance wait perf auxtrace: Fix address filter duplicate symbol selection s390/kexec: fix ipl report address for kdump ASoC: qcom: lpass-cpu: Fix fallback SD line index handling s390/cpum_sf: add READ_ONCE() semantics to compare and swap loops s390/percpu: add READ_ONCE() to arch_this_cpu_to_op_simple() drm/virtio: Fix GEM handle creation UAF drm/i915/gt: Reset twice net/mlx5e: Set action fwd flag when parsing tc action goto cifs: Fix uninitialized memory read for smb311 posix symlink create platform/x86: dell-privacy: Only register SW_CAMERA_LENS_COVER if present platform/surface: aggregator: Ignore command messages not intended for us platform/x86: dell-privacy: Fix SW_CAMERA_LENS_COVER reporting dt-bindings: msm: dsi-controller-main: Fix operating-points-v2 constraint drm/msm/adreno: Make adreno quirks not overwrite each other dt-bindings: msm: dsi-controller-main: Fix power-domain constraint dt-bindings: msm: dsi-controller-main: Fix description of core clock dt-bindings: msm: dsi-phy-28nm: Add missing qcom, dsi-phy-regulator-ldo-mode platform/x86: ideapad-laptop: Add Legion 5 15ARH05 DMI id to set_fn_lock_led_list[] drm/msm/dp: do not complete dp_aux_cmd_fifo_tx() if irq is not for aux transfer dt-bindings: msm/dsi: Don't require vdds-supply on 10nm PHY dt-bindings: msm/dsi: Don't require vcca-supply on 14nm PHY platform/x86: sony-laptop: Don't turn off 0x153 keyboard backlight during probe ixgbe: fix pci device refcount leak ipv6: raw: Deduct extension header length in rawv6_push_pending_frames bus: mhi: host: Fix race between channel preparation and M0 event usb: ulpi: defer ulpi_register on ulpi_read_id timeout iommu/iova: Fix alloc iova overflows issue iommu/mediatek-v1: Fix an error handling path in mtk_iommu_v1_probe() sched/core: Fix use-after-free bug in dup_user_cpus_ptr() netfilter: ipset: Fix overflow before widen in the bitmap_ip_create() function. powerpc/imc-pmu: Fix use of mutex in IRQs disabled section x86/boot: Avoid using Intel mnemonics in AT syntax asm EDAC/device: Fix period calculation in edac_device_reset_delay_period() x86/resctrl: Fix task CLOSID/RMID update race regulator: da9211: Use irq handler when ready scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile scsi: ufs: Stop using the clock scaling lock in the error handler scsi: ufs: core: WLUN suspend SSU/enter hibern8 fail recovery ASoC: wm8904: fix wrong outputs volume after power reactivation ALSA: usb-audio: Make sure to stop endpoints before closing EPs ALSA: usb-audio: Relax hw constraints for implicit fb sync tipc: fix unexpected link reset due to discovery messages octeontx2-af: Fix LMAC config in cgx_lmac_rx_tx_enable hvc/xen: lock console list traversal nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame() af_unix: selftest: Fix the size of the parameter to connect() tools/nolibc: x86: Remove `r8`, `r9` and `r10` from the clobber list tools/nolibc: x86-64: Use `mov $60,%eax` instead of `mov $60,%rax` tools/nolibc: use pselect6 on RISCV tools/nolibc/std: move the standard type definitions to std.h tools/nolibc/types: split syscall-specific definitions into their own files tools/nolibc/arch: split arch-specific code into individual files tools/nolibc/arch: mark the _start symbol as weak tools/nolibc: Remove .global _start from the entry point code tools/nolibc: restore mips branch ordering in the _start block tools/nolibc: fix the O_* fcntl/open macro definitions for riscv
[Kernel-packages] [Bug 2008933] Re: Jammy update: v5.15.90 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008933 Title: Jammy update: v5.15.90 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.90 upstream stable release from git://git.kernel.org/ btrfs: fix trace event name typo for FLUSH_DELAYED_REFS pNFS/filelayout: Fix coalescing test for single DS tools/virtio: initialize spinlocks in vring_test.c virtio_pci: modify ENOENT to EINVAL vduse: Validate vq_num in vduse_validate_config() net/ethtool/ioctl: return -EOPNOTSUPP if we have no phy stats r8169: move rtl_wol_enable_rx() and rtl_prepare_power_down() RDMA/srp: Move large values to a new enum for gcc13 btrfs: always report error in run_one_delayed_ref() x86/asm: Fix an assembler warning with current binutils f2fs: let's avoid panic if extent_tree is not created perf/x86/rapl: Treat Tigerlake like Icelake fbdev: omapfb: avoid stack overflow warning Bluetooth: hci_qca: Fix driver shutdown on closed serdev wifi: brcmfmac: fix regression for Broadcom PCIe wifi devices wifi: mac80211: sdata can be NULL during AMPDU start Add exception protection processing for vd in axi_chan_handle_err function zonefs: Detect append writes at invalid locations nilfs2: fix general protection fault in nilfs_btree_insert() efi: fix userspace infinite retry read efivars after EFI runtime services page fault ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook ALSA: hda/realtek: fix mute/micmute LEDs don't work for a HP platform drm/amdgpu: disable runtime pm on several sienna cichlid cards(v2) drm/amd: Delay removal of the firmware framebuffer hugetlb: unshare some PMDs when splitting VMAs io_uring: don't gate task_work run on TIF_NOTIFY_SIGNAL eventpoll: add EPOLL_URING_WAKE poll wakeup flag eventfd: provide a eventfd_signal_mask() helper io_uring: pass in EPOLL_URING_WAKE for eventfd signaling and wakeups io_uring: improve send/recv error handling io_uring: ensure recv and recvmsg handle MSG_WAITALL correctly io_uring: add flag for disabling provided buffer recycling io_uring: support MSG_WAITALL for IORING_OP_SEND(MSG) io_uring: allow re-poll if we made progress io_uring: fix async accept on O_NONBLOCK sockets io_uring: ensure that cached task references are always put on exit io_uring: remove duplicated calls to io_kiocb_ppos io_uring: update kiocb->ki_pos at execution time io_uring: do not recalculate ppos unnecessarily io_uring/rw: defer fsnotify calls to task context xhci-pci: set the dma max_seg_size usb: xhci: Check endpoint is valid before dereferencing it xhci: Fix null pointer dereference when host dies xhci: Add update_hub_device override for PCI xHCI hosts xhci: Add a flag to disable USB3 lpm on a xhci root port level. usb: acpi: add helper to check port lpm capability using acpi _DSM xhci: Detect lpm incapable xHC USB3 roothub ports from ACPI tables prlimit: do_prlimit needs to have a speculation check USB: serial: option: add Quectel EM05-G (GR) modem USB: serial: option: add Quectel EM05-G (CS) modem USB: serial: option: add Quectel EM05-G (RS) modem USB: serial: option: add Quectel EC200U modem USB: serial: option: add Quectel EM05CN (SG) modem USB: serial: option: add Quectel EM05CN modem staging: vchiq_arm: fix enum vchiq_status return types USB: misc: iowarrior: fix up header size for USB_DEVICE_ID_CODEMERCS_IOW100 misc: fastrpc: Don't remove map on creater_process and device_release misc: fastrpc: Fix use-after-free race condition for maps usb: core: hub: disable autosuspend for TI TUSB8041 comedi: adv_pci1760: Fix PWM instruction handling ACPI: PRM: Check whether EFI runtime is available mmc: sunxi-mmc: Fix clock refcount imbalance during unbind mmc: sdhci-esdhc-imx: correct the tuning start tap and step setting btrfs: do not abort transaction on failure to write log tree when syncing log btrfs: fix race between quota rescan and disable leading to NULL pointer deref cifs: do not include page data when checking signature thunderbolt: Use correct function to calculate maximum USB3 link rate riscv: dts: sifive: fu740: fix size of pcie 32bit memory bpf: restore the ebpf program ID for BPF_AUDIT_UNLOAD and
[Kernel-packages] [Bug 2008927] Re: Jammy update: v5.15.88 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008927 Title: Jammy update: v5.15.88 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.88 upstream stable release from git://git.kernel.org/ parisc: Align parisc MADV_XXX constants with all other architectures serial: fixup backport of "serial: Deassert Transmit Enable on probe in driver-specific way" net: sched: disallow noqueue for qdisc classes ALSA: hda/hdmi: Add a HP device 0x8715 to force connect list ALSA: hda - Enable headset mic on another Dell laptop with ALC3254 Linux 5.15.88 UBUNTU: Upstream stable to v5.15.88 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008927/+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 2009449] Re: linux-libc-dev creates top level directories /arch /install /include
** 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/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Confirmed Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf InstallationDate: Installed on 2015-12-23 (2630 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) IwConfig: lono wireless extensions. enp0s3no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port
[Kernel-packages] [Bug 2009449] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2009449/+attachment/5652114/+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/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Confirmed Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf InstallationDate: Installed on 2015-12-23 (2630 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) IwConfig: lono wireless extensions. enp0s3no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus
[Kernel-packages] [Bug 2009449] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2009449/+attachment/5652113/+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/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Confirmed Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf InstallationDate: Installed on 2015-12-23 (2630 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) IwConfig: lono wireless extensions. enp0s3no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus
[Kernel-packages] [Bug 2009449] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2009449/+attachment/5652112/+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/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Confirmed Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf InstallationDate: Installed on 2015-12-23 (2630 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) IwConfig: lono wireless extensions. enp0s3no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port
[Kernel-packages] [Bug 2009449] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2009449/+attachment/5652111/+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/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Confirmed Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf InstallationDate: Installed on 2015-12-23 (2630 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) IwConfig: lono wireless extensions. enp0s3no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /:
[Kernel-packages] [Bug 2009449] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2009449/+attachment/5652110/+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/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Confirmed Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf InstallationDate: Installed on 2015-12-23 (2630 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) IwConfig: lono wireless extensions. enp0s3no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t:
[Kernel-packages] [Bug 2009449] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2009449/+attachment/5652107/+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/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Confirmed Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf InstallationDate: Installed on 2015-12-23 (2630 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) IwConfig: lono wireless extensions. enp0s3no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus
[Kernel-packages] [Bug 2009449] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2009449/+attachment/5652108/+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/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Confirmed Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf InstallationDate: Installed on 2015-12-23 (2630 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) IwConfig: lono wireless extensions. enp0s3no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[Kernel-packages] [Bug 2009449] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2009449/+attachment/5652109/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Confirmed Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf InstallationDate: Installed on 2015-12-23 (2630 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) IwConfig: lono wireless extensions. enp0s3no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /:
[Kernel-packages] [Bug 2009449] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2009449/+attachment/5652106/+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/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Confirmed Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf InstallationDate: Installed on 2015-12-23 (2630 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) IwConfig: lono wireless extensions. enp0s3no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus
[Kernel-packages] [Bug 2009449] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2009449/+attachment/5652103/+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/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Confirmed Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf InstallationDate: Installed on 2015-12-23 (2630 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) IwConfig: lono wireless extensions. enp0s3no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1:
[Kernel-packages] [Bug 2009449] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2009449/+attachment/5652105/+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/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Confirmed Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf InstallationDate: Installed on 2015-12-23 (2630 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) IwConfig: lono wireless extensions. enp0s3no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1:
[Kernel-packages] [Bug 2009449] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2009449/+attachment/5652104/+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/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Confirmed Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf InstallationDate: Installed on 2015-12-23 (2630 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) IwConfig: lono wireless extensions. enp0s3no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /:
[Kernel-packages] [Bug 2009449] Re: linux-libc-dev creates top level directories /arch /install /include
apport information ** Tags added: apport-collected ** Description changed: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... + --- + ProblemType: Bug + ApportVersion: 2.26.0-0ubuntu2 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 23.04 + HibernationDevice: RESUME=UUID=cbc2edd0-9886-40c6-bf14-d75f638fc4cf + InstallationDate: Installed on 2015-12-23 (2630 days ago) + InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) + IwConfig: + lono wireless extensions. + + enp0s3no wireless extensions. + + docker0 no wireless extensions. + Lsusb: + Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Lsusb-t: + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + MachineType: innotek GmbH VirtualBox + Package: linux (not installed) + ProcFB: 0 svgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=07e383b5-7e12-4530-8ae0-75c104f67e2b ro
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure-cvm/5.4.0-1105.111+cvm1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-cvm (5.4.0-1105.111+cvm1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-azure-cvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-azure-cvm/5.4.0-1105.111+cvm1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-cvm (5.4.0-1105.111+cvm1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-azure-cvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009449] 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 2009449 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/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: Incomplete Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 2009449] Re: linux-libc-dev creates top level directories /arch /install /include
'apt show linux-libc-dev' shows that the source package is 'linux' so moving to the linux source package. ** Package changed: ubuntu => linux (Ubuntu) ** Tags added: lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009449 Title: linux-libc-dev creates top level directories /arch /install /include Status in linux package in Ubuntu: New Bug description: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009449/+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 2009449] [NEW] linux-libc-dev creates top level directories /arch /install /include
You have been subscribed to a public bug: In what package did you find this bug? linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the package name in the editbox, i.e. it says "linux-libc-dev" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Todays lunar update installed a new version von linux-libc-dev. $ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 $ dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 6.1.0-16.16 amd64Linux Kernel Headers for development Now I have directories /arch /include /install at top level of the file system. $ ls / arch boot include lib lost+found proc scripts usr backup dev initrd.img lib32 media root srv var backup2 etc initrd.img.old lib64 mnt run sys vmlinuz bin home install libx32 opt sbin tmp vmlinuz.old $ dpkg -L linux-libc-dev /. /arch /arch/x86 /arch/x86/entry /arch/x86/entry/syscalls /arch/x86/include /arch/x86/include/generated /arch/x86/include/generated/asm /arch/x86/include/generated/asm/.syscalls_32.h.cmd /arch/x86/include/generated/asm/syscalls_32.h /arch/x86/include/generated/uapi /arch/x86/include/generated/uapi/asm /arch/x86/include/generated/uapi/asm/.unistd_32.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_64.h.cmd /arch/x86/include/generated/uapi/asm/.unistd_x32.h.cmd /arch/x86/include/generated/uapi/asm/bpf_perf_event.h /arch/x86/include/generated/uapi/asm/errno.h /arch/x86/include/generated/uapi/asm/fcntl.h /arch/x86/include/generated/uapi/asm/ioctl.h /arch/x86/include/generated/uapi/asm/ioctls.h /arch/x86/include/generated/uapi/asm/ipcbuf.h /arch/x86/include/generated/uapi/asm/param.h /arch/x86/include/generated/uapi/asm/poll.h /arch/x86/include/generated/uapi/asm/resource.h /arch/x86/include/generated/uapi/asm/socket.h /arch/x86/include/generated/uapi/asm/sockios.h /arch/x86/include/generated/uapi/asm/termbits.h /arch/x86/include/generated/uapi/asm/termios.h /arch/x86/include/generated/uapi/asm/types.h /arch/x86/include/generated/uapi/asm/unistd_32.h /arch/x86/include/generated/uapi/asm/unistd_64.h /arch/x86/include/generated/uapi/asm/unistd_x32.h /arch/x86/tools /arch/x86/tools/.relocs.cmd /arch/x86/tools/.relocs_32.o.cmd /arch/x86/tools/.relocs_64.o.cmd /arch/x86/tools/.relocs_common.o.cmd /arch/x86/tools/relocs /arch/x86/tools/relocs_32.o /arch/x86/tools/relocs_64.o /arch/x86/tools/relocs_common.o /include /include/generated /include/generated/uapi /include/generated/uapi/linux /include/generated/uapi/linux/version.h /install /install/include /install/include/asm /install/include/asm/a.out.h /install/include/asm/amd_hsmp.h /install/include/asm/auxvec.h /install/include/asm/bitsperlong.h /install/include/asm/boot.h /install/include/asm/bootparam.h /install/include/asm/bpf_perf_event.h /install/include/asm/byteorder.h /install/include/asm/debugreg.h /install/include/asm/e820.h /install/include/asm/errno.h /install/include/asm/fcntl.h /install/include/asm/hw_breakpoint.h /install/include/asm/hwcap2.h /install/include/asm/ioctl.h /install/include/asm/ioctls.h /install/include/asm/ipcbuf.h /install/include/asm/ist.h /install/include/asm/kvm.h /install/include/asm/kvm_para.h /install/include/asm/kvm_perf.h /install/include/asm/ldt.h /install/include/asm/mce.h /install/include/asm/mman.h /install/include/asm/msgbuf.h /install/include/asm/msr.h /install/include/asm/mtrr.h /install/include/asm/param.h ... ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- linux-libc-dev creates top level directories /arch /install /include https://bugs.launchpad.net/bugs/2009449 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 2009271] Re: Too many BDL entries regression
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009271 Title: Too many BDL entries regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: New Bug description: Hello, Thanks for your hard work :) I got this error after kernel update to 5.19.0-35 as explained here : https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log and here : https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u A load of syslog "Too many BDL entries" appears. Have a nice week-end, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5004 F wireplumber /dev/snd/controlC1: laurent5004 F wireplumber /dev/snd/seq:laurent5000 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 16:47:55 2023 InstallationDate: Installed on 2020-07-01 (976 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009271/+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 2006744] Re: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict
mesa needs a fix too to add a Replaces/Breaks ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to mesa-amber in Ubuntu. https://bugs.launchpad.net/bugs/2006744 Title: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict Status in mesa package in Ubuntu: In Progress Status in mesa-amber package in Ubuntu: Fix Released Bug description: I enabled lunar-proposed today (with APT::Default-Release "lunar- proposed";) and got the error below during update: Preparing to unpack .../39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-AkyzpG/39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Then it will be broken: root@deleteme-lunar:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libglapi-mesa (= 22.2.5-0ubuntu1) but 22.3.4-1ubuntu1 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@deleteme-lunar:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libicu71 libpython3.10-minimal libpython3.10-stdlib python3.10 python3.10-minimal Use 'apt autoremove' to remove them. The following additional packages will be installed: libgl1-mesa-dri The following packages will be upgraded: libgl1-mesa-dri 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62 not fully installed or removed. Need to get 0 B/7806 kB of archives. After this operation, 809 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 81205 files and directories currently installed.) Preparing to unpack .../libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Errors were encountered while processing: /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) How to reproduce: 1. Spin up a Lunar VM 2. Enable -proposed 3. Install libgl1-mesa-dri and libgl1-amber-dri 4. Add APT::Default-Release "lunar-proposed"; to /etc/apt/apt.conf.d/somefile 5. Try to upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006744/+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 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs
Just to give another data point, I've been running 5.19 from hwe-edge (instead of hwe) for some time but I realized this suspend issue after updating hwe-edge from 5.19.0.28.29~22.04.6 to 5.19.0.32.33~22.04.9. So I went back and tested it as follows. It looks like it's a regression within 5.19. My 2 cents. machine: ThinkPad T14 Gen 3 (21CFCTO1WW) CPU: AMD Ryzen 7 PRO 6850U Ubuntu release: jammy Please note that I tested it with Secure boot *disabled* since 5.19.0-28 wouldn't boot somehow (I believe it was working fine with Secure boot enabled before). $ uname -rv 5.19.0-35-generic #36~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 17 15:17:25 UTC 2 -> stuck at the second attempt of suspend $ uname -rv 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 -> stuck at the second attempt of suspend $ uname -rv 5.19.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 15 12:05:40 UTC 2 -> 10/10 suspend-resume cycles succeeded -- 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/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. UPDATE: See attached log. This may not be a case of the laptop failing to resume, but a case of the laptop not suspending properly! What happened was the following. When packing in my things, I closed the laptop and put it in my bag. At home I picked it up again, and immediately noticed how unusually hot it was. The laptop didn't resume properly on opening the lid, but was frozen as before. So this might actually be a case of the laptop FAILING TO SUSPEND properly, instead of failing to wake up. UPDATE: I just noticed the battery was down to the low 40% from at least 80%. Given the temperature on opening the laption I suspect the CPU has been working hard during "sleep time". EDIT: Changed title after confirmation for earlier Ryzen 5000 CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718/+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 2003596] Re: Bionic update: upstream stable patchset 2023-01-20
This bug was fixed in the package linux-snapdragon - 4.15.0-1146.156 --- linux-snapdragon (4.15.0-1146.156) bionic; urgency=medium * bionic/linux-snapdragon: 4.15.0-1146.156 -proposed tracker (LP: #2004412) * Bionic update: upstream stable patchset 2023-01-20 (LP: #2003596) - [Config] updateconfigs following Ubuntu-4.15.0-204.215 rebase [ Ubuntu: 4.15.0-206.217 ] * bionic/linux: 4.15.0-206.217 -proposed tracker (LP: #2004655) * CVE-2023-0461 - SAUCE: Fix inet_csk_listen_start after CVE-2023-0461 [ Ubuntu: 4.15.0-205.216 ] * bionic/linux: 4.15.0-205.216 -proposed tracker (LP: #2004414) * Bionic update: upstream stable patchset 2023-01-20 (LP: #2003596) - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - ipvs: use explicitly signed chars - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix ulist leaks in error paths of qgroup self tests - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - net, neigh: Fix null-ptr-deref in neigh_table_clear() - media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE - media: dvb-frontends/drxk: initialize err to 0 - i2c: xiic: Add platform module alias - Bluetooth: L2CAP: Fix attempting to access uninitialized memory - block, bfq: protect 'bfqd->queued' by 'bfqd->lock' - btrfs: fix type of parameter generation in btrfs_get_dentry - tcp/udp: Make early_demux back namespacified. - capabilities: fix potential memleak on error path from vfs_getxattr_alloc() - ALSA: usb-audio: Add quirks for MacroSilicon MS2100/MS2106 devices - efi: random: reduce seed size to 32 bytes - parisc: Make 8250_gsc driver dependend on CONFIG_PARISC - parisc: Export iosapic_serial_irq() symbol for serial port driver - ext4: fix warning in 'ext4_da_release_space' - KVM: x86: Mask off reserved bits in CPUID.8008H - KVM: x86: emulator: em_sysexit should update ctxt->mode - KVM: x86: emulator: introduce emulator_recalc_and_set_mode - KVM: x86: emulator: update the emulation mode after CR0 write - linux/const.h: prefix include guard of uapi/linux/const.h with _UAPI - linux/const.h: move UL() macro to include/linux/const.h - linux/bits.h: make BIT(), GENMASK(), and friends available in assembly - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: tun: fix bugs for oversize packet when napi frags enabled - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - ipv6: fix WARNING in ip6_route_net_exit_late() - parisc: Avoid printing the hardware path twice - HID: hyperv: fix possible memory leak in mousevsc_probe() - net: gso: fix panic on frag_list with mixed head alloc types - bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer - net: fman: Unregister ethernet device on removal - capabilities: fix undefined behavior in bit shift for CAP_TO_MASK - net: lapbether: fix issue of dev reference count leakage in lapbeth_device_event() - hamradio: fix issue of dev reference count leakage in bpq_device_event() - drm/vc4: Fix missing platform_unregister_drivers() call in vc4_drm_register() - ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network - tipc: fix the msg->req tlv len check in tipc_nl_compat_name_table_dump_header - dmaengine: mv_xor_v2: Fix a resource leak in mv_xor_v2_remove() - drivers: net: xgene: disable napi when register irq failed in xgene_enet_open() - net: cxgb3_main: disable napi when bind qsets failed in cxgb_up() - ethernet: s2io: disable napi when start nic failed in s2io_card_up() - net: mv643xx_eth: disable napi when init rxq or txq failed in mv643xx_eth_open() - net: macvlan: fix memory leaks of macvlan_common_newlink - arm64: efi: Fix handling of misaligned runtime regions and drop warning - ALSA: hda: fix potential memleak in 'add_widget_node' - ALSA: usb-audio: Add quirk entry for M-Audio Micro - nilfs2: fix deadlock in nilfs_count_free_blocks() - drm/i915/dmabuf: fix sg_table handling in map_dma_buf - platform/x86: hp_wmi: Fix
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws-5.15/5.15.0.1032.36~20.04.21)
All autopkgtests for the newly accepted linux-meta-aws-5.15 (5.15.0.1032.36~20.04.21) for focal have finished running. The following regressions have been reported in tests triggered by the package: lttng-modules/2.12.5-1ubuntu2~20.04.4 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-aws-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs
Same issue on Ubuntu 22.10 running kernel 5.19.0-35-generic, on a Lenovo IdeaPad 5 14ARE05 with an AMD Ryzen 7 4700U. The power light is not pulsing when the problem occurs, which indicates the system is not suspended. I also have not been able to discern a pattern as to when the problem does or does not occur. -- 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/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. UPDATE: See attached log. This may not be a case of the laptop failing to resume, but a case of the laptop not suspending properly! What happened was the following. When packing in my things, I closed the laptop and put it in my bag. At home I picked it up again, and immediately noticed how unusually hot it was. The laptop didn't resume properly on opening the lid, but was frozen as before. So this might actually be a case of the laptop FAILING TO SUSPEND properly, instead of failing to wake up. UPDATE: I just noticed the battery was down to the low 40% from at least 80%. Given the temperature on opening the laption I suspect the CPU has been working hard during "sleep time". EDIT: Changed title after confirmation for earlier Ryzen 5000 CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718/+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 1937133] Re: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour')
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937133 Title: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour') Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Won't Fix Bug description: Failing on hirsute/linux 5.11.0-26.28 host s2lp4 Not a regression as this is also failing on 5.11.0-24.25 17:16:32 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:16:32 DEBUG| [stdout] # Traceback (most recent call last): 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 283, in 17:16:32 DEBUG| [stdout] # main() 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 256, in main 17:16:32 DEBUG| [stdout] # ports = devlink_ports(dev) 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 70, in __init__ 17:16:32 DEBUG| [stdout] # self.if_names = devlink_ports.get_if_names(dev) 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 64, in get_if_names 17:16:32 DEBUG| [stdout] # if ports[port]['flavour'] == 'physical': 17:16:32 DEBUG| [stdout] # KeyError: 'flavour' 17:16:32 DEBUG| [stdout] not ok 44 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Fix Committed Status in zfs-linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in zfs-linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Fix Released Status in zfs-linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Fix Committed Status in zfs-linux source package in Lunar: Confirmed Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key
** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-bionic verification-done-focal verification-done-jammy verification-done-kinetic ** Tags added: kernel-stable-tracking-bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002812 Title: Revoke & rotate to new signing key Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * Revoke & rotate to new signing key * Update revocations, which match the next Ubuntu shim 15.7 revocations. Specifically - revoke certs that were previously protected with by-hash revocations, revoke lost/unused certificates. * Start using advantage2021v1 and ubuntu2022v1 signing keys. * This is a routine key rotation. [ Test Plan ] * Check that old shim/grub boot this kernel * Check that the upcomming future shim/grub can boot this kernel * Check that these kernels can do signed kexec into itself [ Where problems could occur ] * Kernels with this patch applied should be signed using ubuntu/4 pro/3 core/2 signing streams. [ Other Info ] * TPM PCR values and measurements will change when changing the signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009441] [NEW] Kernel oops after inactivity; then panic
Public bug reported: Every night, after 1 ~ 2 hours of inactivity, I get a Kernel Oops and a subsequent hang: ``` Mar 06 01:29:37 ike3 kernel: BUG: unable to handle page fault for address: d5d84a5c5b90 Mar 06 01:29:37 ike3 kernel: #PF: supervisor read access in kernel mode Mar 06 01:29:37 ike3 kernel: #PF: error_code(0x) - not-present page Mar 06 01:29:37 ike3 kernel: PGD 0 P4D 0 Mar 06 01:29:37 ike3 kernel: Oops: [#1] SMP NOPTI Mar 06 01:29:37 ike3 kernel: CPU: 0 PID: 3376 Comm: Isolated Web Co Not tainted 5.14.0-1058-oem #66-Ubuntu Mar 06 01:29:37 ike3 kernel: Hardware name: LENOVO 21CB007CUK/21CB007CUK, BIOS N3AET71W (1.36 ) 01/31/2023 Mar 06 01:29:37 ike3 kernel: RIP: 0010:__vma_adjust+0x55c/0x970 Mar 06 01:29:37 ike3 kernel: Code: 0f 92 c2 48 29 c8 48 85 d2 74 4f 31 c0 48 8b 53 10 48 85 d2 74 0b 48 8b 52 18 48 39 d0 48 0f 42 c2 48 8b 53 08 48 85 d2 74 0b <48> 8b 52 18 48 39 d0 48 0f 42 c2 48 39 43 18 0f 84 5b ff ff ff 48 Mar 06 01:29:37 ike3 kernel: RSP: 0018:a67d035efd58 EFLAGS: 00010286 Mar 06 01:29:37 ike3 kernel: RAX: RBX: 95dba45b9218 RCX: 0010 Mar 06 01:29:37 ike3 kernel: RDX: d5d84a5c5b78 RSI: RDI: Mar 06 01:29:37 ike3 kernel: RBP: a67d035efde0 R08: 0001 R09: a76a1900 Mar 06 01:29:37 ike3 kernel: R10: 0001 R11: R12: 95dba45b91f8 Mar 06 01:29:37 ike3 kernel: R13: 95d9171112d8 R14: R15: 95d91369bd50 Mar 06 01:29:37 ike3 kernel: FS: 7f3ffa2ca780() GS:95e03f40() knlGS: Mar 06 01:29:37 ike3 kernel: CS: 0010 DS: ES: CR0: 80050033 Mar 06 01:29:37 ike3 kernel: CR2: d5d84a5c5b90 CR3: 00018fba8003 CR4: 00770ef0 Mar 06 01:29:37 ike3 kernel: PKRU: 5554 Mar 06 01:29:37 ike3 kernel: Call Trace: Mar 06 01:29:37 ike3 kernel: Mar 06 01:29:37 ike3 kernel: vma_merge+0x27d/0x400 Mar 06 01:29:37 ike3 kernel: mprotect_fixup+0x139/0x2e0 Mar 06 01:29:37 ike3 kernel: ? security_file_mprotect+0x4e/0x60 Mar 06 01:29:37 ike3 kernel: do_mprotect_pkey+0x203/0x3a0 Mar 06 01:29:37 ike3 kernel: __x64_sys_mprotect+0x1f/0x30 Mar 06 01:29:37 ike3 kernel: do_syscall_64+0x38/0xc0 Mar 06 01:29:37 ike3 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Mar 06 01:29:37 ike3 kernel: RIP: 0033:0x7f3ffa43c9ab Mar 06 01:29:37 ike3 kernel: Code: 73 01 c3 48 8b 0d e5 34 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 0a 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 34 0d 00 f7 d8 64 89 01 48 Mar 06 01:29:37 ike3 kernel: RSP: 002b:7ffd5f5c4b08 EFLAGS: 0293 ORIG_RAX: 000a Mar 06 01:29:37 ike3 kernel: RAX: ffda RBX: 21a1dc482000 RCX: 7f3ffa43c9ab Mar 06 01:29:37 ike3 kernel: RDX: 0003 RSI: 2000 RDI: 21a1dc482000 Mar 06 01:29:37 ike3 kernel: RBP: 21a1dc484000 R08: R09: 0003 Mar 06 01:29:37 ike3 kernel: R10: 7ffd5f5c4e50 R11: 0293 R12: 7ffd5f5c4bb8 Mar 06 01:29:37 ike3 kernel: R13: 0470 R14: 0001 R15: 0470 Mar 06 01:29:37 ike3 kernel: Mar 06 01:29:37 ike3 kernel: Modules linked in: xt_nat xt_tcpudp veth snd_usb_audio snd_usbmidi_lib snd_seq_dummy xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_addrtype iptable> Mar 06 01:29:37 ike3 kernel: snd_pcm_dmaengine mei_hdcp intel_rapl_msr snd_hda_intel snd_intel_dspcfg mac80211 kvm_intel snd_intel_sdw_acpi libarc4 snd_hda_codec kvm btusb snd_hda_core btrtl snd_hwdep rapl btbcm btintel iwlwifi think_lmi binfmt_misc intel_cstate serio_raw firmware_> Mar 06 01:29:37 ike3 kernel: parport_pc ppdev lp parport pstore_blk ramoops pstore_zone reed_solomon efi_pstore ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj usbhid dm_crypt spi_ljca gpio_ljca i2c_ljca ljca hid_generic i915 i2c_algo_bit ttm drm_kms_helper syscopyare> Mar 06 01:29:37 ike3 kernel: CR2: d5d84a5c5b90 Mar 06 01:29:37 ike3 kernel: ---[ end trace 73ac121002a31968 ]--- Mar 06 01:29:37 ike3 kernel: RIP: 0010:__vma_adjust+0x55c/0x970 Mar 06 01:29:37 ike3 kernel: Code: 0f 92 c2 48 29 c8 48 85 d2 74 4f 31 c0 48 8b 53 10 48 85 d2 74 0b 48 8b 52 18 48 39 d0 48 0f 42 c2 48 8b 53 08 48 85 d2 74 0b <48> 8b 52 18 48 39 d0 48 0f 42 c2 48 39 43 18 0f 84 5b ff ff ff 48 Mar 06 01:29:37 ike3 kernel: RSP: 0018:a67d035efd58 EFLAGS: 00010286 Mar 06 01:29:37 ike3 kernel: RAX: RBX: 95dba45b9218 RCX: 0010 Mar 06 01:29:37 ike3 kernel: RDX: d5d84a5c5b78 RSI: RDI: Mar 06 01:29:37 ike3 kernel: RBP: a67d035efde0 R08: 0001 R09: a76a1900 Mar 06 01:29:37 ike3 kernel: R10: 0001 R11: R12: 95dba45b91f8 Mar 06 01:29:37 ike3 kernel: R13:
[Kernel-packages] [Bug 2008882] Re: Remove all other acpi_video backlight interface on Dell AIO platforms
Hopeful! My screen is much bright and I have to stop my job!
--
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/2008882
Title:
Remove all other acpi_video backlight interface on Dell AIO platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
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:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
[Impact]
There are acpi_video* sysfs backlight interface in the system which are not
working.
For Dell AIO platforms, we use dell_uart_backlight to control the display
brightness.
The old way to fix this is to unregister acpi backlight interfaces in the
backlight driver, but it may lead to some issues and the unregister function
has been removed since v6.1-rc1
77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")
[Fix]
The new way to do this is to collect all the quirk and auto detection method
in video_detect.c
I added an audo detection for the Dell AIO platoform to the driver which
should do the same thing as the old way.
[Test]
Verified on the Dell AIO platform and confirmed there is only on
dell_uart_backlight in the sysfs, and no acpi_video* interface.
[Where problems could occur]
There should be no regression potential, it uses different way to do the same
thing, should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2008882/+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
What I have noticed now only occurs at NFS clients, not with the NFS server. NFS Client Server that create a large amount of simultaneous accesses have the problem. NFS Client Server that create few accesses do not have the problem. We have now booted our web servers on an older kernel version and the problem was gone. Even if the NFS Server servers have the current 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed 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 Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 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:
[Kernel-packages] [Bug 2008882] Re: Remove all other acpi_video backlight interface on Dell AIO platforms
Verified the backlight interface is correct with 6.1.0-1008-oem.
** 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/2008882
Title:
Remove all other acpi_video backlight interface on Dell AIO platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
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:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
[Impact]
There are acpi_video* sysfs backlight interface in the system which are not
working.
For Dell AIO platforms, we use dell_uart_backlight to control the display
brightness.
The old way to fix this is to unregister acpi backlight interfaces in the
backlight driver, but it may lead to some issues and the unregister function
has been removed since v6.1-rc1
77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")
[Fix]
The new way to do this is to collect all the quirk and auto detection method
in video_detect.c
I added an audo detection for the Dell AIO platoform to the driver which
should do the same thing as the old way.
[Test]
Verified on the Dell AIO platform and confirmed there is only on
dell_uart_backlight in the sysfs, and no acpi_video* interface.
[Where problems could occur]
There should be no regression potential, it uses different way to do the same
thing, should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2008882/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-lowlatency/5.19.0-1020.21)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency (5.19.0-1020.21) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules- lowlatency [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008871] Re: Screen backlight keeps in minimized and can't change it with amdgpu
Confirmed there is only one backlight interface amdgpu_bl0 in the system with 6.1.0-1008-oem ** Tags removed: oem-priority originate-from-2007527 somerville 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/2008871 Title: Screen backlight keeps in minimized and can't change it with amdgpu Status in HWE Next: New Status in linux package in Ubuntu: In Progress 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: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Sometimes the system boots up with both acpi_video0 and amdgpu_bl0 sysfs interfaces and the acpi_video0 doesn't work. [Fix] Add this machine to the video_detect_dmi_table to force it uses native backlight interface which is amdgpu_bl0. https://lkml.org/lkml/2023/3/2/187 [Verify] Verified by our QA and ODM. [Where problems could occur] Pretty safe to add the DMI quirk, won't affect other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008871/+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 2008871] Re: Screen backlight keeps in minimized and can't change it with amdgpu
** Tags added: oem-priority originate-from-2007527 somerville -- 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/2008871 Title: Screen backlight keeps in minimized and can't change it with amdgpu Status in HWE Next: New Status in linux package in Ubuntu: In Progress 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: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Sometimes the system boots up with both acpi_video0 and amdgpu_bl0 sysfs interfaces and the acpi_video0 doesn't work. [Fix] Add this machine to the video_detect_dmi_table to force it uses native backlight interface which is amdgpu_bl0. https://lkml.org/lkml/2023/3/2/187 [Verify] Verified by our QA and ODM. [Where problems could occur] Pretty safe to add the DMI quirk, won't affect other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008871/+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 2008882] Re: Remove all other acpi_video backlight interface on Dell AIO platforms
Hi Larry,
You have to wait the new kernel for Lunar, should be available soon.
The OEM kernel is in -proposed(6.1.0-1008.8-oem) now which contains the fix if
you want to try.
--
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/2008882
Title:
Remove all other acpi_video backlight interface on Dell AIO platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
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:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
[Impact]
There are acpi_video* sysfs backlight interface in the system which are not
working.
For Dell AIO platforms, we use dell_uart_backlight to control the display
brightness.
The old way to fix this is to unregister acpi backlight interfaces in the
backlight driver, but it may lead to some issues and the unregister function
has been removed since v6.1-rc1
77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")
[Fix]
The new way to do this is to collect all the quirk and auto detection method
in video_detect.c
I added an audo detection for the Dell AIO platoform to the driver which
should do the same thing as the old way.
[Test]
Verified on the Dell AIO platform and confirmed there is only on
dell_uart_backlight in the sysfs, and no acpi_video* interface.
[Where problems could occur]
There should be no regression potential, it uses different way to do the same
thing, should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2008882/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009024] Re: Fail to output sound to external monitor which connects via docking station
is there a tradeoff after enabling this, like for instance increased power consumption or such? ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Incomplete -- 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: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-6.1 source package in Jammy: Incomplete Status in linux source package in Lunar: Incomplete 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 2009437] 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 2009437
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
** Changed in: linux (Ubuntu Kinetic)
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/2009437
Title:
apply the latest TDX attestation driver from Intel
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Kinetic:
Incomplete
Bug description:
[Impact]
TDX guest attestation has been merged as SAUCE patches in the kinetic
kernel with the following commits:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next=285d6d8136ebadcee7fd6452b9e4223996a2a0af
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next=0b78a71c7d7630ab7c3c8a03cbe4f78f1361fb45
However, Intel released a new TDX attestation driver that will be
submitted upstream. We should align with the new version that will
likely end upstream.
See also LP: #1971027
[Test case]
Testing this feature requires a special hardware in the host, special
firmware and special configuration of a guest. Right now it can only
be tested by Intel.
[Fix]
Apply the new driver provided by Intel in LP: #1971027.
[Regression potential]
The new driver can potentially break user-space applications that are
relying on the TDX attestation feature. This is because of this struct
(used in the user-space/kernel communication, via ioctl):
+ * Used in TDX_CMD_GET_REPORT IOCTL request.
+ */
+struct tdx_report_req {
+ __u8 subtype;
+ __u64 reportdata;
+ __u32 rpd_len;
+ __u64 tdreport;
+ __u32 tdr_len;
+};
The new patch changed the struct as following:
+struct tdx_report_req {
+ __u8 reportdata[TDX_REPORTDATA_LEN];
+ __u8 tdreport[TDX_REPORT_LEN];
+};
In general we should never apply changes that are breaking user-space like
this (especially for non-devel kernels), but realistically we can probably say
that nobody is using this feature yet, so nobody has any user-space program
that is relying on the old struct (and if they do,
they're probably in touch with Intel, so they're aware of this change).
In conclusion, this change should be considered pretty safe, despite
the potential user-space brekage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009437/+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 1914774] Re: Some derivative kernel tools packages don't depend on linux-tools-common
This bug was fixed in the package linux-ibm - 5.15.0-1026.29 --- linux-ibm (5.15.0-1026.29) jammy; urgency=medium * jammy/linux-ibm: 5.15.0-1026.29 -proposed tracker (LP: #2004318) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.01.30) * Some derivative kernel tools packages don't depend on linux-tools-common (LP: #1914774) - [Packaging] ibm: linux-tools-common and linux-cloud-tools-common are one per series [ Ubuntu: 5.15.0-66.73 ] * jammy/linux: 5.15.0-66.73 -proposed tracker (LP: #2004636) * CVE-2023-0461 - SAUCE: Fix inet_csk_listen_start after CVE-2023-0461 [ Ubuntu: 5.15.0-65.72 ] * jammy/linux: 5.15.0-65.72 -proposed tracker (LP: #2004344) * Packaging resync (LP: #1786013) - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/2023.01.30) * NFS: client permission error after adding user to permissible group (LP: #2003053) - NFS: Clear the file access cache upon login - NFS: Judge the file access cache's timestamp in rcu path - NFS: Fix up a sparse warning * Fix W6400 hang after resume of S3 stress (LP: #2000299) - drm/amd/display: Manually adjust strobe for DCN303 * Rear Audio port sometimes has no audio output after reboot(Cirrus Logic) (LP: #1998905) - ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock. * CVE-2022-20369 - NFSD: fix use-after-free in __nfs42_ssc_open() * CVE-2023-0461 - net/ulp: prevent ULP without clone op from entering the LISTEN status - net/ulp: use consistent error code when blocking ULP * CVE-2023-0179 - netfilter: nft_payload: incorrect arithmetics when fetching VLAN header bits * Jammy update: v5.15.85 upstream stable release (LP: #2003139) - udf: Discard preallocation before extending file with a hole - udf: Fix preallocation discarding at indirect extent boundary - udf: Do not bother looking for prealloc extents if i_lenExtents matches i_size - udf: Fix extending file within last block - usb: gadget: uvc: Prevent buffer overflow in setup handler - USB: serial: option: add Quectel EM05-G modem - USB: serial: cp210x: add Kamstrup RF sniffer PIDs - USB: serial: f81232: fix division by zero on line-speed change - USB: serial: f81534: fix division by zero on line-speed change - xhci: Apply XHCI_RESET_TO_DEFAULT quirk to ADL-N - igb: Initialize mailbox message for VF reset - usb: dwc3: pci: Update PCIe device ID for USB3 controller on CPU sub-system for Raptor Lake - HID: uclogic: Add HID_QUIRK_HIDINPUT_FORCE quirk - selftests: net: Use "grep -E" instead of "egrep" - net: loopback: use NET_NAME_PREDICTABLE for name_assign_type - Linux 5.15.85 * Jammy update: v5.15.84 upstream stable release (LP: #2003137) - x86/vdso: Conditionally export __vdso_sgx_enter_enclave() - vfs: fix copy_file_range() averts filesystem freeze protection - ASoC: fsl_micfil: explicitly clear software reset bit - ASoC: fsl_micfil: explicitly clear CHnF flags - ASoC: ops: Check bounds for second channel in snd_soc_put_volsw_sx() - libbpf: Use page size as max_entries when probing ring buffer map - pinctrl: meditatek: Startup with the IRQs disabled - can: sja1000: fix size of OCR_MODE_MASK define - can: mcba_usb: Fix termination command argument - net: fec: don't reset irq coalesce settings to defaults on "ip link up" - ASoC: cs42l51: Correct PGA Volume minimum value - perf: Fix perf_pending_task() UaF - nvme-pci: clear the prp2 field when not used - ASoC: ops: Correct bounds check for second channel on SX controls - net: fec: properly guard irq coalesce setup - Linux 5.15.84 * Jammy update: v5.15.83 upstream stable release (LP: #2003134) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator:
[Kernel-packages] [Bug 2001914] Re: The gpu hangs and is not possible to work with GPU-envioronment
user@host:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS" user@host:~$ uname -a Linux host 5.17.0-1028-oem #29-Ubuntu SMP PREEMPT Fri Feb 10 10:28:20 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux -- 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/2001914 Title: The gpu hangs and is not possible to work with GPU-envioronment Status in linux package in Ubuntu: Confirmed Bug description: When I open the terminal or just browsing, gnom sometimes freezes for a second, but sometimes restart the machine is necessary. The log is: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm]i915 :00:02.0: [drm] GPU HANG: ecode 12:0: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC SLPC: enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: last_user_time (2748010) is greater than comparison timestamp (2743419). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 0xc0003c appears to be one of the offending windows with a timestamp of 2748010. Working around... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Jan 5 12:25:49 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-02 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001914/+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 2001914] Re: The gpu hangs and is not possible to work with GPU-envioronment
I have the same issue. I got this output from dmesg: [14591.143452] i915 :00:02.0: [drm] GPU HANG: ecode 12:0: [14591.143865] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [14591.147696] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled [14591.147702] i915 :00:02.0: [drm] GuC SLPC: enabled [14591.147705] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes Seems like this is a common issue: https://gitlab.freedesktop.org/drm/intel/-/issues/6916 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #6916 https://gitlab.freedesktop.org/drm/intel/-/issues/6916 -- 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/2001914 Title: The gpu hangs and is not possible to work with GPU-envioronment Status in linux package in Ubuntu: Confirmed Bug description: When I open the terminal or just browsing, gnom sometimes freezes for a second, but sometimes restart the machine is necessary. The log is: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm]i915 :00:02.0: [drm] GPU HANG: ecode 12:0: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC SLPC: enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: last_user_time (2748010) is greater than comparison timestamp (2743419). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 0xc0003c appears to be one of the offending windows with a timestamp of 2748010. Working around... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Jan 5 12:25:49 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-02 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001914/+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 2009437] [NEW] apply the latest TDX attestation driver from Intel
Public bug reported:
[Impact]
TDX guest attestation has been merged as SAUCE patches in the kinetic
kernel with the following commits:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next=285d6d8136ebadcee7fd6452b9e4223996a2a0af
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next=0b78a71c7d7630ab7c3c8a03cbe4f78f1361fb45
However, Intel released a new TDX attestation driver that will be
submitted upstream. We should align with the new version that will
likely end upstream.
See also LP: #1971027
[Test case]
Testing this feature requires a special hardware in the host, special
firmware and special configuration of a guest. Right now it can only be
tested by Intel.
[Fix]
Apply the new driver provided by Intel in LP: #1971027.
[Regression potential]
The new driver can potentially break user-space applications that are
relying on the TDX attestation feature. This is because of this struct
(used in the user-space/kernel communication, via ioctl):
+ * Used in TDX_CMD_GET_REPORT IOCTL request.
+ */
+struct tdx_report_req {
+ __u8 subtype;
+ __u64 reportdata;
+ __u32 rpd_len;
+ __u64 tdreport;
+ __u32 tdr_len;
+};
The new patch changed the struct as following:
+struct tdx_report_req {
+ __u8 reportdata[TDX_REPORTDATA_LEN];
+ __u8 tdreport[TDX_REPORT_LEN];
+};
In general we should never apply changes that are breaking user-space like this
(especially for non-devel kernels), but realistically we can probably say that
nobody is using this feature yet, so nobody has any user-space program that is
relying on the old struct (and if they do,
they're probably in touch with Intel, so they're aware of this change).
In conclusion, this change should be considered pretty safe, despite the
potential user-space brekage.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2009437
Title:
apply the latest TDX attestation driver from Intel
Status in linux package in Ubuntu:
New
Status in linux source package in Kinetic:
New
Bug description:
[Impact]
TDX guest attestation has been merged as SAUCE patches in the kinetic
kernel with the following commits:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next=285d6d8136ebadcee7fd6452b9e4223996a2a0af
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next=0b78a71c7d7630ab7c3c8a03cbe4f78f1361fb45
However, Intel released a new TDX attestation driver that will be
submitted upstream. We should align with the new version that will
likely end upstream.
See also LP: #1971027
[Test case]
Testing this feature requires a special hardware in the host, special
firmware and special configuration of a guest. Right now it can only
be tested by Intel.
[Fix]
Apply the new driver provided by Intel in LP: #1971027.
[Regression potential]
The new driver can potentially break user-space applications that are
relying on the TDX attestation feature. This is because of this struct
(used in the user-space/kernel communication, via ioctl):
+ * Used in TDX_CMD_GET_REPORT IOCTL request.
+ */
+struct tdx_report_req {
+ __u8 subtype;
+ __u64 reportdata;
+ __u32 rpd_len;
+ __u64 tdreport;
+ __u32 tdr_len;
+};
The new patch changed the struct as following:
+struct tdx_report_req {
+ __u8 reportdata[TDX_REPORTDATA_LEN];
+ __u8 tdreport[TDX_REPORT_LEN];
+};
In general we should never apply changes that are breaking user-space like
this (especially for non-devel kernels), but realistically we can probably say
that nobody is using this feature yet, so nobody has any user-space program
that is relying on the old struct (and if they do,
they're probably in touch with Intel, so they're aware of this change).
In conclusion, this change should be considered pretty safe, despite
the potential user-space brekage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009437/+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 1964992] Re: ZFS ignores ARC sizes below allmem/32
Hello, I just wanted to clarify the changes in the two commits that were backported. For commit 36a6e2335c45, the main features that were backported were the warnings generated when ARC fails to set the max and min value to the user specified values. Although this commit has a fix for the zfs_arc_max size below allmem/32, it does have a major regression where the issue gets essentially flipped and will cause zfs_arc_min not to accept any value above allmem/2. Commit e945e8d7f4fc although mainly a FreeBSD patch, does fix the regression created by the previous commit and assures that the user cannot set the value of zfs_arc_max below the maximum transaction size of 64MB. All other FreeBSD specific changes were ignored. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964992 Title: ZFS ignores ARC sizes below allmem/32 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: In Progress Bug description: [Impact] ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. This prevents users from properly restraining ARC sizes, and can cause increased memory contention in some systems. [Test Plan] 1. Deploy test system with ZFS storage and 32GB RAM 2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf # cat /etc/modprobe.d/99-zfs-arc.conf options zfs zfs_arc_min=536870912 options zfs zfs_arc_max=966367641 3. Reboot system 4. Verify ARC sizes through "arc_summary" # arc_summary | grep -A3 "ARC size" ARC size (current): < 0.1 %1.3 MiB Target size (adaptive): 100.0 % 15.7 GiB Min size (hard limit): 3.2 % 512.0 MiB Max size (high water): 31:1 15.7 GiB For a 32GB test system, we should be able to set max ARC sizes below 1GB. [Fix] This has been fixed by upstream commit: - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32" - e945e8d7f4fc "Restore FreeBSD sysctl processing for arc.min and arc.max" The commit has been introduced in upstream zfs-2.0.0, so it's needed for Bionic and Focal. Releases starting with Impish already have this commit by default: $ git describe --contains 36a6e2335c45 zfs-2.0.0-rc1~332 $ rmadison zfs-linux zfs-linux | 0.7.5-1ubuntu15| bionic | source zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates | source zfs-linux | 0.8.3-1ubuntu12| focal | source zfs-linux | 0.8.3-1ubuntu12.9 | focal-security | source zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates | source zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed | source zfs-linux | 2.0.6-1ubuntu2 | impish | source zfs-linux | 2.0.6-1ubuntu2.1 | impish-updates | source zfs-linux | 2.1.2-1ubuntu3 | jammy | source [Regression Potential] The introduced commit essentially removes the limitation of setting ARC tunables below allmem/32, and re-arranges the order of how some of the tunables are parsed. Regressions would possibly show up as other tunables being ignored or not being set correctly due to parsing errors. We should validate whether other ARC related tunables are still being set correctly, and whether ZFS is using the set values for the ARC memory thresholds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+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 1953058] Re: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion even
Tried to deploy and wait for 100min to see if soft lockup shows. Deploy focal and I can reproduce 5 times in 8 deploy test. Deploy jammy and it passes 20 deploy and everything looks good. It looks more and more like a focal kernel issue to me. -- 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/1953058 Title: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9") Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Confirmed Bug description: The regression boot test running with bionic:linux-hwe-5.4 5.4.0-92.103~18.04.2 failed because of the following hung task: Dec 2 12:17:12 appleton-kernel kernel: [ 64.281447] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0] Dec 2 12:17:12 appleton-kernel kernel: [ 64.288573] Modules linked in: ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib hid_generic ses usbhid enclosure hid ib_uverbs ib_core marvell hibmc_drm drm_vram_helper ttm drm_kms_helper crct10dif_ce ghash_ce syscopyarea sysfillrect sha2_ce mlx5_core sysimgblt sha256_arm64 ixgbe hisi_sas_v2_hw fb_sys_fops nvme sha1_ce hisi_sas_main tls xfrm_algo drm megaraid_sas nvme_core mdio mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher Dec 2 12:17:12 appleton-kernel kernel: [ 64.288629] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-91-generic #102~18.04.1-Ubuntu Dec 2 12:17:12 appleton-kernel kernel: [ 64.288630] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288632] pstate: 4045 (nZcv daif +PAN -UAO) Dec 2 12:17:12 appleton-kernel kernel: [ 64.288640] pc : __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288644] lr : irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288645] sp : 800011ee3ef0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288646] x29: 800011ee3ef0 x28: 002fb71a2d00 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288649] x27: x26: 800011ee4000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288650] x25: 800011ee x24: 001fba073600 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288652] x23: 80001234bdb0 x22: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288654] x21: 0282 x20: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288656] x19: 8000116b3000 x18: 800011267510 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288658] x17: x16: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288659] x15: 0001 x14: 002fbb9f21c8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288661] x13: 0004 x12: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288663] x11: x10: 0040 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288665] x9 : 800011bbf228 x8 : 800011bbf220 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288666] x7 : 001fb9002270 x6 : 0002c07fa07f Dec 2 12:17:12 appleton-kernel kernel: [ 64.288668] x5 : 00c1 x4 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288670] x3 : 8000116b3780 x2 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288672] x1 : 00e0 x0 : 8000116b3780 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288675] Call trace: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288677] __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288679] irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288683] __handle_domain_irq+0x6c/0xc0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288685] gic_handle_irq+0x84/0x2c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288687] el1_irq+0x104/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288690] arch_cpu_idle+0x34/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288694] default_idle_call+0x24/0x60 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288696] do_idle+0x1d8/0x2b8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288699] cpu_startup_entry+0x28/0xb0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288702] secondary_start_kernel+0x198/0x288 Dec 2
[Kernel-packages] [Bug 1964992] Re: ZFS ignores ARC sizes below allmem/32
** Description changed: [Impact] ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. This prevents users from properly restraining ARC sizes, and can cause increased memory contention in some systems. [Test Plan] 1. Deploy test system with ZFS storage and 32GB RAM 2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf # cat /etc/modprobe.d/99-zfs-arc.conf options zfs zfs_arc_min=536870912 options zfs zfs_arc_max=966367641 3. Reboot system 4. Verify ARC sizes through "arc_summary" # arc_summary | grep -A3 "ARC size" ARC size (current): < 0.1 %1.3 MiB Target size (adaptive): 100.0 % 15.7 GiB Min size (hard limit): 3.2 % 512.0 MiB Max size (high water): 31:1 15.7 GiB For a 32GB test system, we should be able to set max ARC sizes below 1GB. [Fix] This has been fixed by upstream commit: - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32" + - e945e8d7f4fc "Restore FreeBSD sysctl processing for arc.min and arc.max" The commit has been introduced in upstream zfs-2.0.0, so it's needed for Bionic and Focal. Releases starting with Impish already have this commit by default: $ git describe --contains 36a6e2335c45 zfs-2.0.0-rc1~332 $ rmadison zfs-linux zfs-linux | 0.7.5-1ubuntu15| bionic | source zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates | source zfs-linux | 0.8.3-1ubuntu12| focal | source zfs-linux | 0.8.3-1ubuntu12.9 | focal-security | source zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates | source zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed | source zfs-linux | 2.0.6-1ubuntu2 | impish | source zfs-linux | 2.0.6-1ubuntu2.1 | impish-updates | source zfs-linux | 2.1.2-1ubuntu3 | jammy | source [Regression Potential] The introduced commit essentially removes the limitation of setting ARC tunables below allmem/32, and re-arranges the order of how some of the tunables are parsed. Regressions would possibly show up as other tunables being ignored or not being set correctly due to parsing errors. We should validate whether other ARC related tunables are still being set correctly, and whether ZFS is using the set values for the ARC memory thresholds. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964992 Title: ZFS ignores ARC sizes below allmem/32 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: In Progress Bug description: [Impact] ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. This prevents users from properly restraining ARC sizes, and can cause increased memory contention in some systems. [Test Plan] 1. Deploy test system with ZFS storage and 32GB RAM 2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf # cat /etc/modprobe.d/99-zfs-arc.conf options zfs zfs_arc_min=536870912 options zfs zfs_arc_max=966367641 3. Reboot system 4. Verify ARC sizes through "arc_summary" # arc_summary | grep -A3 "ARC size" ARC size (current): < 0.1 %1.3 MiB Target size (adaptive): 100.0 % 15.7 GiB Min size (hard limit): 3.2 % 512.0 MiB Max size (high water): 31:1 15.7 GiB For a 32GB test system, we should be able to set max ARC sizes below 1GB. [Fix] This has been fixed by upstream commit: - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32" - e945e8d7f4fc "Restore FreeBSD sysctl processing for arc.min and arc.max" The commit has been introduced in upstream zfs-2.0.0, so it's needed for Bionic and Focal. Releases starting with Impish already have this commit by default: $ git describe --contains 36a6e2335c45 zfs-2.0.0-rc1~332 $ rmadison zfs-linux zfs-linux | 0.7.5-1ubuntu15| bionic | source zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates | source zfs-linux | 0.8.3-1ubuntu12| focal | source zfs-linux | 0.8.3-1ubuntu12.9 | focal-security | source zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates | source zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed | source zfs-linux | 2.0.6-1ubuntu2 | impish | source zfs-linux | 2.0.6-1ubuntu2.1 | impish-updates | source zfs-linux | 2.1.2-1ubuntu3 | jammy | source [Regression Potential] The introduced commit essentially removes the limitation of setting ARC tunables below allmem/32, and re-arranges the order of how some of the tunables are parsed.
[Kernel-packages] [Bug 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently
** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2007875 Title: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently Status in linux-firmware package in Ubuntu: Fix Released Status in oem-somerville-tentacool-meta package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in oem-somerville-tentacool-meta source package in Jammy: New Status in linux-firmware source package in Kinetic: Fix Released Status in oem-somerville-tentacool-meta source package in Kinetic: Invalid Status in linux-firmware source package in Lunar: Fix Released Status in oem-somerville-tentacool-meta source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and -73 firmware are supported bug missing. On one user reported issue, this fixes WiFi stability on 5G band. [Fix] New upstreamed firmware revision fixes this issue. [Test Case] 1. Boot hwe-5.19 kernel 2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded 3. Browse the web, usually takes between 1 and 5 minutes 4. Networking will cut out [Where problems could occur] This affects only users need both backport-iwlwifi-dkms and hwe-5.19 kernel on WiFi stability. [Other Info] While Kinetic and above have them all, only Jammy is nominated. == original bug report == I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320). Recently I received some kernel updates, the 5.19 kernel used in 22.10 and a 6.0 oem kernel. Both updates break wifi. It seems to only do so on newer 5.7 GHz access points. 1. Boot latest 6.0 oem kernel 2. Browse the web, usually takes between 1 and 5 minutes. 3. Networking will cut out. Disabling networking and starting again will fix it until it happens again in a few minutes. This will repeat indefinitely, essentially making wireless useless. The attached dmesg log reliably shows up when it fails, showing iwlwifi failing and a (network?) hardware reset request. It witnessed this happen months ago on 22.10, which led me to using the Dell stock 22.04 image. But it seems even the newer OEM kernel is affected. A workaround is to select the older 5.15 kernel in grub. I find on this laptop, one must hit escape precisely 1 second after seeing the Dell logo on boot. Alternatively one could edit /etc/grub/default and set a longer timeout. Let me know if this bug report would be better to go to Dell as a support request instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+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 2006458] Re: Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm FastConnect 6900
** Changed in: linux-firmware (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-firmware (Ubuntu Kinetic) Status: New => Fix Committed ** Changed in: linux-firmware (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2006458 Title: Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm FastConnect 6900 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-firmware source package in Lunar: Fix Released Bug description: [Impact] To whom it may concern: I was experiencing frequent wake-ups from s0i3x on a HP Pro 435 G9 convertible [1] using the Qualcomm FastConnect 6900 Soc [2]. The issue is related to FW revision WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 that comes bundled with Ubuntu 22.10. It appears the SoC increasingly triggering wake-ups after being suspended for approx. 4 hrs. Read the full story at [4]. The solution is to upgrade SoC firmware to rev WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23/ [3] Best regards,Carsten [1] https://support.hp.com/us-en/product/hp-pro-x360-435-13.3-inch-g9-notebook-pc/2101144107/document/ish_6053745-6053789-16 [2] https://www.qualcomm.com/products/technology/wi-fi/fastconnect/fastconnect-6900 [3] https://github.com/kvalo/ath11k-firmware/tree/master/WCN6855/hw2.0/1.1/WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23 [4] https://gitlab.freedesktop.org/drm/amd/-/issues/2377 [Fix] Upgrade firmware, as mentioned above. [Test case] TBD. [Where Problems might occur] It's firmware, what could possibly go wrong? If so, connectivity issues wit ath11k based NICs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2006458/+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 2009355] Re: linux-libc-dev is no longer multi-arch safe
** 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/2009355 Title: linux-libc-dev is no longer multi-arch safe Status in linux package in Ubuntu: Confirmed Bug description: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/i386/b/binutils/20230305_112702_eba45@/log.gz dpkg: error processing archive /tmp/apt-dpkg-install-9IkDRS/098-linux-libc-dev_6.1.0-16.16_i386.deb (--unpack): trying to overwrite shared '/arch/x86/include/generated/asm/.syscalls_32.h.cmd', which is different from other instances of package linux-libc-dev:i386 I'm not sure why linux-libc-dev_6.1.0-16.16 has files in /arch /install /scripts. But these files are different on different arch (or different build, since it embeds build path) ==> amd64/arch/x86/include/generated/asm/.syscalls_32.h.cmd <== cmd_arch/x86/include/generated/asm/syscalls_32.h := sh /build/linux-1t584m/linux-6.1.0/scripts/syscalltbl.sh --abis i386 /build/linux-1t584m/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl arch/x86/include/generated/asm/syscalls_32.h ==> i386/arch/x86/include/generated/asm/.syscalls_32.h.cmd <== cmd_arch/x86/include/generated/asm/syscalls_32.h := sh /build/linux-f194dh/linux-6.1.0/scripts/syscalltbl.sh --abis i386 /build/linux-f194dh/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl arch/x86/include/generated/asm/syscalls_32.h To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009355/+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 2009358] [NEW] Lunar update: v6.2.2 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.2.2 upstream stable release from git://git.kernel.org/ Linux 6.2.2 USB: core: Don't hold device lock while reading the "descriptors" sysfs file usb: typec: pd: Remove usb_suspend_supported sysfs from sink PDO arm64: dts: uniphier: Fix property name in PXs3 USB node usb: gadget: u_serial: Add null pointer check in gserial_resume USB: serial: option: add support for VW/Skoda "Carstick LTE" usb: dwc3: pci: add support for the Intel Meteor Lake-M wifi: rtw88: usb: drop now unnecessary URB size check wifi: rtw88: usb: send Zero length packets if necessary wifi: rtw88: usb: Set qsel correctly scripts/tags.sh: fix incompatibility with PCRE2 drm/amd/display: Properly reuse completion structure drm/amd/display: Move DCN314 DOMAIN power control to DMCUB vc_screen: don't clobber return value in vcs_read bpf: bpf_fib_lookup should not return neigh in NUD_FAILED state crypto: arm64/sm4-gcm - Fix possible crash in GCM cryption ALSA: hda: cs35l41: Correct error condition handling ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: 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/2009358 Title: Lunar update: v6.2.2 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Lunar: Confirmed 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.2.2 upstream stable release from git://git.kernel.org/ Linux 6.2.2 USB: core: Don't hold device lock while reading the "descriptors" sysfs file usb: typec: pd: Remove usb_suspend_supported sysfs from sink PDO arm64: dts: uniphier: Fix property name in PXs3 USB node usb: gadget: u_serial: Add null pointer check in gserial_resume USB: serial: option: add support for VW/Skoda "Carstick LTE" usb: dwc3: pci: add support for the Intel Meteor Lake-M wifi: rtw88: usb: drop now unnecessary URB size check wifi: rtw88: usb: send Zero length packets if necessary wifi: rtw88: usb: Set qsel correctly scripts/tags.sh: fix incompatibility with PCRE2 drm/amd/display: Properly reuse completion structure drm/amd/display: Move DCN314 DOMAIN power control to DMCUB vc_screen: don't clobber return value in vcs_read bpf: bpf_fib_lookup should not return neigh in NUD_FAILED state crypto: arm64/sm4-gcm - Fix possible crash in GCM cryption ALSA: hda: cs35l41: Correct error condition handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009358/+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
