[Kernel-packages] [Bug 1964711] Re: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked
blacklist-amdgpu.conf doesn't appear to be installed by default in Ubuntu. My best guess is that it might have come from installing a proprietary driver package from AMD at some point? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: After locking Ubuntu and leaving it unattended for a while, the operating system cannot be unlocked anymore. No means of user input (e.g. typing on the keyboard, moving the mouse) produce the lock screen and I have to shut down my computer by pressing down the power button. The attached monitor does not receive a signal from the computer during these attempts. This started to happen several weeks ago and worked without a problem before then. Due to the nature of this issue, I can neither report any errors occurring nor can I observe any other out of the ordinary things from happening. Thus, I don’t know which package is causing the issue. Also, this issue happens every time I leave the computer unattended for a longer time and lock it. However, locking it and triggering an input immediately after does produce the lock screen, so the lock screen seems to work in principle. Description: Ubuntu 20.04.4 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+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 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** Tags added: resume suspend-resume -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 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.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+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 1896350] Re: nbd locks system?
Hi Dan, Thank you for your bug report. I just came across it now, as I just ran into same issue too. Your reproducer works great, and I have started debugging the issue. At this stage it doesn't seem to be a kernel bug, or a qemu-nbd bug. I think the culprit is systemd-udevd or multipathd, as when I disable systemd-udevd, things work fine. I will add more details to the bug report in a few days or so, once I have determined the root cause and come up with a fix. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896350 Title: nbd locks system? Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to use nbd on ubuntu 20.04 like so: qemu-img create -f qcow2 foo.img 500M sudo modprobe nbd sudo qemu-nbd --disconnect /dev/nbd15 || true sudo qemu-nbd --connect=/dev/nbd15 --cache=writeback --format=qcow2 foo.img sudo mkfs.ext4 -L root -O "^64bit" -E nodiscard /dev/nbd15 sudo qemu-nbd --disconnect /dev/nbd15 It seems to work on some systems, but even on those systems, strange things show up in syslog, e.g. Sep 19 15:46:02 thinky kernel: [27042.757768] block nbd15: Possible stuck request dd2d7f93: control (read@135168,126976B). Runtime 450 seconds Sep 19 15:46:26 thinky kernel: [27067.333867] INFO: task systemd-udevd:17364 blocked for more than 241 seconds. and in kern.log, e.g. ... Sep 19 16:17:27 thinky kernel: [ 71.676026] Buffer I/O error on dev nbd15, logical block 7, async page read Sep 19 16:17:27 thinky kernel: [ 71.676049] blk_update_request: I/O error, dev nbd15, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 19 16:17:27 thinky kernel: [ 71.676051] Buffer I/O error on dev nbd15, logical block 0, async page read Sep 19 16:17:27 thinky kernel: [ 71.676061] blk_update_request: I/O error, dev nbd15, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 19 16:17:27 thinky kernel: [ 71.676063] Buffer I/O error on dev nbd15, logical block 1, async page read Sep 19 16:17:27 thinky kernel: [ 71.676147] ldm_validate_partition_table(): Disk read failed. Sep 19 16:17:27 thinky kernel: [ 71.676324] Dev nbd15: unable to read RDB block 0 Sep 19 16:17:27 thinky kernel: [ 71.676473] nbd15: unable to read partition table Sep 19 16:17:27 thinky kernel: [ 71.678340] nbd15: detected capacity change from 0 to 524288000 Sep 19 16:17:27 thinky kernel: [ 71.678536] ldm_validate_partition_table(): Disk read failed. Sep 19 16:17:27 thinky kernel: [ 71.678719] Dev nbd15: unable to read RDB block 0 Sep 19 16:17:27 thinky kernel: [ 71.678947] nbd15: unable to read partition table Sep 19 16:17:27 thinky kernel: [ 71.679985] ldm_validate_partition_table(): Disk read failed. Sep 19 16:17:27 thinky kernel: [ 71.680172] Dev nbd15: unable to read RDB block 0 Sep 19 16:17:27 thinky kernel: [ 71.680366] nbd15: unable to read partition table Sep 19 16:17:27 thinky kernel: [ 71.680647] block nbd15: Attempted send on invalid socket and the system seems to hang on reboot. Also, on another system (an up to date mac, running ubuntu 20.04 in virtualbox), the mkfs.ext4 fails, complaining the device is zero size. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dank 2948 F pulseaudio /dev/snd/controlC2: dank 2948 F pulseaudio /dev/snd/controlC0: dank 2948 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 16:28:43 2020 HibernationDevice: RESUME=UUID=7aecd5d3-2f5b-4c07-8867-801e63868a0f InstallationDate: Installed on 2017-04-29 (1239 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO ThinkServer TS140 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=ff9a24e4-277d-4baf-819b-826a33d5bb5e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-01 (141 days ago) dmi.bios.date: 09/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: FBKT99AUS dmi.board.name: ThinkServer TS140 dmi.board.vendor: LENOVO dmi.board.version: Not Defined
[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
See also bug 1855757. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 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.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+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 1967456] Re: Jammy didn't use nvidia driver when executing firefox
** Summary changed: - Jammy didn't use nvidia driver whne executing firefox + Jammy didn't use nvidia driver when executing firefox -- 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/1967456 Title: Jammy didn't use nvidia driver when executing firefox Status in linux package in Ubuntu: Confirmed Bug description: [Reproduce step] 1. Install Jammy beta. 2. Install Nvidia driver by ubuntu-driver install. 3. Connect monitor to dGPU output port. 4. Run firefox, type "about:support" in url, and check column "GPU #1" [Expected result] should see nvidia driver info. [Actual result] still use llvmpipe [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1186 F pulseaudio /dev/snd/controlC1: u 1186 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 00:07:47 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: HP HP Z2 Mini G5 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 0.1 dmi.bios.vendor: HP dmi.bios.version: S50 Ver. 01.00.01 dmi.board.name: 8754 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.03 dmi.chassis.type: 2 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV: dmi.product.family: 103C_53335X HP Workstation dmi.product.name: HP Z2 Mini G5 Workstation dmi.product.sku: 9JD38AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967456/+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 1967456] Re: Jammy didn't use nvidia driver whne executing firefox
how about launch Terminal and then issue: $ glxinfo | grep -i opengl -- 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/1967456 Title: Jammy didn't use nvidia driver whne executing firefox Status in linux package in Ubuntu: Confirmed Bug description: [Reproduce step] 1. Install Jammy beta. 2. Install Nvidia driver by ubuntu-driver install. 3. Connect monitor to dGPU output port. 4. Run firefox, type "about:support" in url, and check column "GPU #1" [Expected result] should see nvidia driver info. [Actual result] still use llvmpipe [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1186 F pulseaudio /dev/snd/controlC1: u 1186 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 00:07:47 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: HP HP Z2 Mini G5 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 0.1 dmi.bios.vendor: HP dmi.bios.version: S50 Ver. 01.00.01 dmi.board.name: 8754 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.03 dmi.chassis.type: 2 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV: dmi.product.family: 103C_53335X HP Workstation dmi.product.name: HP Z2 Mini G5 Workstation dmi.product.sku: 9JD38AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967456/+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 1967456] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967456 Title: Jammy didn't use nvidia driver whne executing firefox Status in linux package in Ubuntu: Confirmed Bug description: [Reproduce step] 1. Install Jammy beta. 2. Install Nvidia driver by ubuntu-driver install. 3. Connect monitor to dGPU output port. 4. Run firefox, type "about:support" in url, and check column "GPU #1" [Expected result] should see nvidia driver info. [Actual result] still use llvmpipe [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1186 F pulseaudio /dev/snd/controlC1: u 1186 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 00:07:47 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: HP HP Z2 Mini G5 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 0.1 dmi.bios.vendor: HP dmi.bios.version: S50 Ver. 01.00.01 dmi.board.name: 8754 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.03 dmi.chassis.type: 2 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV: dmi.product.family: 103C_53335X HP Workstation dmi.product.name: HP Z2 Mini G5 Workstation dmi.product.sku: 9JD38AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967456/+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 1967456] [NEW] Jammy didn't use nvidia driver whne executing firefox
Public bug reported: [Reproduce step] 1. Install Jammy beta. 2. Install Nvidia driver by ubuntu-driver install. 3. Connect monitor to dGPU output port. 4. Run firefox, type "about:support" in url, and check column "GPU #1" [Expected result] should see nvidia driver info. [Actual result] still use llvmpipe [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1186 F pulseaudio /dev/snd/controlC1: u 1186 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 00:07:47 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: HP HP Z2 Mini G5 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 0.1 dmi.bios.vendor: HP dmi.bios.version: S50 Ver. 01.00.01 dmi.board.name: 8754 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.03 dmi.chassis.type: 2 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV: dmi.product.family: 103C_53335X HP Workstation dmi.product.name: HP Z2 Mini G5 Workstation dmi.product.sku: 9JD38AV dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy jiayi oem-priority wayland-session ** Attachment added: "Screenshot from 2022-03-31 23-57-25.png" https://bugs.launchpad.net/bugs/1967456/+attachment/5575464/+files/Screenshot%20from%202022-03-31%2023-57-25.png ** Tags added: jiayi oem-priority -- 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/1967456 Title: Jammy didn't use nvidia driver whne executing firefox Status in linux package in Ubuntu: Confirmed Bug description: [Reproduce step] 1. Install Jammy beta. 2. Install Nvidia driver by ubuntu-driver install. 3. Connect monitor to dGPU output port. 4. Run firefox, type "about:support" in url, and check column "GPU #1" [Expected result] should see nvidia driver info. [Actual result] still use llvmpipe [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1186 F pulseaudio /dev/snd/controlC1: u 1186 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 00:07:47 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: HP HP Z2 Mini G5 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 0.1 dmi.bios.vendor: HP dmi.bios.version: S50 Ver. 01.00.01 dmi.board.name: 8754 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.03 dmi.chassis.type: 2 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8
[Kernel-packages] [Bug 1965496] Re: alsa: enable the cirrus-logic side-codec to make the speaker output sound
Installed the linux-oem-5.14/5.14.0-1032.35 on the lenovo machine which has the cirrus-logic side codec, the speaker could output sound with the proposed kernel. Verification done. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965496 Title: alsa: enable the cirrus-logic side-codec to make the speaker output sound Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] We have a couple of lenovo latops models which have cirrus-logic side codec between realtek codec and speaker, it plays a role as amplifier, we need to enable this side-codec, otherwise the speaker can't output sound. [Fix] Backport codec patches and some i2c and acpi detection patches from mainline kernel and linux-next [Test] boot the patched kernel, run speaker test, both left and right channel could work well. [Where problems could occur] If it could introduce regression, it will be on soc wm_adsp codec drivers, since most of patch are adding new codec drivers, it will not touch existing codec drivers. If a machine with wm_adsp codec can't output sound or record sound, it means this SRU introduce the regression on wm_adsp driver, but this possibility is very low, since all patches are picked from mainline kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1965496/+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 1966007] Re: Flood of Bluetooth Malicious advertisind data
I also notice it seems fixed in 5.4.0-107-generic, Thanks for the quick fix now I concentrate on debugging Bluetooth problems with my Logitech M590 moues. Regards Stephen Carr -- 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/1966007 Title: Flood of Bluetooth Malicious advertisind data Status in linux-signed package in Ubuntu: Confirmed Bug description: This problem occurred with the ugrade of the kernel to patch level 105. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174 Uname: Linux 5.4.0-105-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 12:48:22 2022 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2018-06-21 (1370 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_AU.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1966007/+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 1966007] Re: Flood of Bluetooth Malicious advertisind data
seems fixed on 5.4.0-107-generic: frankzhou@pluto:~$ dmesg | grep Bluetooth | wc -l 62 frankzhou@pluto:~$ uptime 11:06:54 up 3:58, 2 users, load average: 0.28, 0.23, 0.25 frankzhou@pluto:~$ uname -a Linux pluto 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 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-signed in Ubuntu. https://bugs.launchpad.net/bugs/1966007 Title: Flood of Bluetooth Malicious advertisind data Status in linux-signed package in Ubuntu: Confirmed Bug description: This problem occurred with the ugrade of the kernel to patch level 105. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174 Uname: Linux 5.4.0-105-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 12:48:22 2022 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2018-06-21 (1370 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_AU.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1966007/+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 1967078] Re: Firefox snap install fails due to disabled networking in upgrade process
*** This bug is a duplicate of bug 1966589 *** https://bugs.launchpad.net/bugs/1966589 ** Package changed: linux (Ubuntu) => ubuntu-release-upgrader (Ubuntu) ** This bug has been marked a duplicate of bug 1966589 release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1` -- 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/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) dmi.bios.date: 04/25/2008 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB7WW (2.17 ) dmi.board.name: 6465CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T61 dmi.product.name: 6465CTO dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Package: ubuntu-release-upgrader-core 1:22.04.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Tags: jammy dist-upgrade Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1967078/+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 1965846] Re: Enable the mic-mute led on Dell XPS 9315
Verify on PORT-DVT2-D1 with BIOS 0.2.31. The kernel 5.14.0-1032-oem can make mic-mute led work. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965846 Title: Enable the mic-mute led on Dell XPS 9315 Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] On Dell's XPS 9315, the MIC-Mute function is working but the LED(on F4) state is not changed accordingly. [Fix] Dell's mic mute support in privacy mode has been upstream, but the the mic-mute led support is still SAUCE patch which is maintained with DMI based quirk. Add a new SKU for XPS 9315 until Dell's official fix for the mic-mute led. [Test Case] 1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only working on the particular SKU defined in DMI table. Will need to drop it when Dell release the official solution. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1965846/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Looks linux-hwe-5.4/5.4.0-107.121~18.04.1 contains security fix without patch for this issue. I will wait for testing linux-hwe-5.4/5.4.0-108 ** Tags removed: verification-needed-bionic ** Tags added: verification-failed-bionic -- 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1943301] Re: 【sec-0911】 fail to reset sec module
Looks linux-hwe-5.4/5.4.0-107.121~18.04.1 contains security fix without patch for this issue. I will wait for testing linux-hwe-5.4/5.4.0-108 ** Tags removed: verification-needed-bionic ** Tags added: verification-failed-bionic -- 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/1943301 Title: 【sec-0911】 fail to reset sec module Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [Impact] The crypto accelerator in Hi1620 SoC can not be reset. [Test Plan] 1) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3) busybox devmem 0x200141B01018 32 0x1 4) dmesg | grep "FLR resetting" [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] [Steps to Reproduce] 1、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3、busybox devmem 0x200141B01018 32 0x1, [Actual Results] root@root:~# busybox devmem 0x200141B01018 32 0x1 root@root:~# dmesg root@root:~# [Expected Results] reset ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): OS: ubuntu 20.04.2 DRV（driver version）: vermagic: 5.8.0-59-generic SMP mod_unload aarch64 [Resolution] [v2,3/5] crypto: hisilicon/sec2 - update SEC initialization and reset 此patch未合入 https://patchwork.kernel.org/project/linux-crypto/patch/1594084541-22177-4-git-send-email-liulongf...@huawei.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1943301/+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 1964983] Re: IPU6 camera has no function on Andrews MLK
Using kernel 5.14.0-1032-oem, the camera sensor and ipu6 driver was working correctly. I can get camera working with userspace stack in ppa:oem-solutions-engineers/intel-ipu6. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1964983 Title: IPU6 camera has no function on Andrews MLK Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Confirmed Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Bug description: [SRU Justification] [Impact] New Andrews MLK equips yet another new I2C sensor and takes a few driver updates to function normally. [Fix] Upstream driver commit: https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e [Test Case] To verify by following steps: 1. disable secure boot 2. $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel 3. $ sudo add-apt-repository ppa:kchsieh/ipu6 4. $ sudo apt install linux-oem-5.14 version 5.14.0-9029-oem or newer 6. $ sudo apt install libipu6ep 7. $ sudo apt install libcamhal-ipu6ep-common 8. $ sudo apt install libcamhal-ipu6ep0 9. $ sudo apt install libgsticamerainterface-1.0-1 10. $ sudo apt install gstreamer1.0-icamera 11. $ sudo vim /etc/v4l2-relayd -FORMAT=YUY2 +FORMAT=NV12 12. $ sudo reboot [Where problems could occur] Intel IPU6 platform is still under development and is not capable of advanced power management features and may still suffer from stability issues. [Other Info] Nomination for 5.15 is necessary for oem-5.14 to hwe-5.15 migration and will depend on previous SRU proposal in bug 1955383 (https://lists.ubuntu.com/archives/kernel-team/2022-March/128922.html). Nomination for generic-5.17 and oem-5.17 is still under planning. == original bug description == The new platform uses yet another ov sensor OV02C10. Prerequisites: * kernel fix: https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e * ipu6-camera-bins: https://github.com/intel/ipu6-camera-bins/commit/7cc1dc2d9ab2b0766e034edf808d751bd25b42cc * ipu6-camera-hal: https://github.com/intel/ipu6-camera-hal/commit/b9b56de11de70b7c4520595176e4831bacf4a7fe * icamerasrc: https://github.com/intel/icamerasrc/commit/a35978264002acaad72bb9956238ccaef3743932 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964983/+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 1966680] Re: Revert drm/amd/pm: enable ASPM by default
have verified with 5.14-oem-1032.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1966680
Title:
Revert drm/amd/pm: enable ASPM by default
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[Impact]
With WX3200 and 20.04d kernel the unit freezes on resume
[Fix]
commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
by default but a variety of hardware configurations it turns out that this
caused a regression.
Multiple SKUs with wx3200 gpus encounter the resume issue.
Before the real fix is landed, revert commit 0064b0ce85bb first.
[Test Case]
1. plug wx3200 on the adl machine and make it as a output.
2. suspend machine
3. check if machine could resume successfully
[Where problems could occur]
Low, don't make AMDGPU ASPM by default.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1966680/+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 1967439] Re: Impish update: upstream stable patchset 2022-03-31
** 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 2022-03-31 -upstream stable patchset 2022-03-31 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v5.10.101, v5.15.24 + + from git://git.kernel.org/ + + integrity: check the return value of audit_log_start() + ima: Remove ima_policy file before directory + ima: Allow template selection with ima_template[_fmt]= after ima_hash= + mmc: sdhci-of-esdhc: Check for error num after setting mask + can: isotp: fix potential CAN frame reception race in isotp_rcv() + net: phy: marvell: Fix RGMII Tx/Rx delays setting in 88e1121-compatible PHYs + net: phy: marvell: Fix MDI-x polarity setting in 88e1118-compatible PHYs + NFS: Fix initialisation of nfs_client cl_flags field + NFSD: Clamp WRITE offsets + NFSD: Fix offset type in I/O trace points + tracing: Propagate is_signed to expression + NFS: change nfs_access_get_cached to only report the mask + NFSv4 only print the label when its queried + nfs: nfs4clinet: check the return value of kstrdup() + NFSv4.1: Fix uninitialised variable in devicenotify + NFSv4 remove zero number of fs_locations entries error check + NFSv4 expose nfs_parse_server_name function + NFSv4 handle port presence in fs_location server string + x86/perf: Avoid warning for Arch LBR without XSAVE + drm: panel-orientation-quirks: Add quirk for the 1Netbook OneXPlayer + net: sched: Clarify error message when qdisc kind is unknown + powerpc/fixmap: Fix VM debug warning on unmap + scsi: target: iscsi: Make sure the np under each tpg is unique + scsi: ufs: ufshcd-pltfrm: Check the return value of devm_kstrdup() + scsi: qedf: Add stag_work to all the vports + scsi: qedf: Fix refcount issue when LOGO is received during TMF + scsi: pm8001: Fix bogus FW crash for maxcpus=1 + scsi: ufs: Treat link loss as fatal error + scsi: myrs: Fix crash in error case + PM: hibernate: Remove register_nosave_region_late() + usb: dwc2: gadget: don't try to disable ep0 in dwc2_hsotg_suspend + perf: Always wake the parent event + nvme-pci: add the IGNORE_DEV_SUBNQN quirk for Intel P4500/P4600 SSDs + net: stmmac: dwmac-sun8i: use return val of readl_poll_timeout() + KVM: eventfd: Fix false positive RCU usage warning + KVM: nVMX: eVMCS: Filter out VM_EXIT_SAVE_VMX_PREEMPTION_TIMER + KVM: nVMX: Also filter MSR_IA32_VMX_TRUE_PINBASED_CTLS when eVMCS + KVM: SVM: Don't kill SEV guest if SMAP erratum triggers in usermode + KVM: VMX: Set vmcs.PENDING_DBG.BS on #DB in STI/MOVSS blocking shadow + riscv: fix build with binutils 2.38 + ARM: dts: imx23-evk: Remove MX23_PAD_SSP1_DETECT from hog group + ARM: dts: Fix boot regression on Skomer + ARM: socfpga: fix missing RESET_CONTROLLER + nvme-tcp: fix bogus request completion when failing to send AER + ACPI/IORT: Check node revision for PMCG resources + drm/rockchip: vop: Correct RK3399 VOP register fields + ARM: dts: Fix timer regression for beagleboard revision c + ARM: dts: meson: Fix the UART compatible strings + ARM: dts: meson8: Fix the UART device-tree schema validation + ARM: dts: meson8b: Fix the UART device-tree schema validation + staging: fbtft: Fix error path in fbtft_driver_module_init() + ARM: dts: imx6qdl-udoo: Properly describe the SD card detect + phy: xilinx: zynqmp: Fix bus width setting for SGMII + ARM: dts: imx7ulp: Fix 'assigned-clocks-parents' typo + usb: f_fs: Fix use-after-free for epfile + gpio: aggregator: Fix calling into sleeping GPIO controllers + drm/vc4: hdmi: Allow DBLCLK modes even if horz timing is odd. + misc: fastrpc: avoid double fput() on failed usercopy + netfilter: ctnetlink: disable helper autoassign + arm64: dts: meson-g12b-odroid-n2: fix typo 'dio2133' + ixgbevf: Require large buffers for build_skb on 82599VF + drm/panel: simple: Assign data from panel_dpi_probe() correctly + gpio: sifive: use the correct register to read output values + bonding: pair enable_port with slave_arr_updates + net: dsa: mv88e6xxx: don't use devres for mdiobus + net: dsa: ar9331: register the mdiobus
[Kernel-packages] [Bug 1967439] [NEW] Impish update: upstream stable patchset 2022-03-31
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 2022-03-31 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Impish) 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 Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1967439 Title: Impish update: upstream stable patchset 2022-03-31 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: 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 2022-03-31 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967439/+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 1964335] Re: Excessive size of kernel modules on RISC-V - modules unstripped
This bug was fixed in the package linux-riscv - 5.15.0-1005.5
---
linux-riscv (5.15.0-1005.5) jammy; urgency=medium
* jammy/linux-riscv: 5.15.0-1005.5 -proposed tracker (LP: #1965783)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
* dependency on crda obsolete according to Debian (LP: #1958918)
- [Packaging] switch dependency from crda to wireless-regdb
* Excessive size of kernel modules on RISC-V - modules unstripped
(LP: #1964335)
- SAUCE: scripts/Makefile.modinst discard-locals from modules
* Cherrypick features and fixes from v5.17 for sifive dtbs (LP: #1962010)
- riscv: dts: sifive: use only generic JEDEC SPI NOR flash compatible
- riscv: dts: sifive: fix Unleashed board compatible
- Revert "SiFive HiFive Unleashed: Add PWM LEDs (D1, D2, D3, D4)"
- riscv: dts: sifive: drop duplicated nodes and properties in sifive
- riscv: dts: sifive: add missing compatible for plic
- riscv: dts: sifive unmatched: Name gpio lines
- riscv: dts: sifive unmatched: Expose the board ID eeprom
- riscv: dts: sifive unmatched: Expose the PMIC sub-functions
- Revert "riscv: sifive: unmatched: update for 16GB rev3"
- riscv: dts: sifive unmatched: Fix regulator for board rev3
- riscv: dts: sifive unmatched: Link the tmp451 with its power supply
- riscv: dts: sifive: Group tuples in interrupt properties
- riscv: dts: sifive: Group tuples in register properties
- riscv: dts: sifive: fu540-c000: Drop bogus soc node compatible values
- riscv: dts: sifive: fu540-c000: Fix PLIC node
- riscv: dts: sifive unmatched: Add gpio poweroff
* riscv: backport support for SiFive Unmatched (LP: #1910965)
- SiFive HiFive Unleashed: Add PWM LEDs (D1, D2, D3, D4)
* Miscellaneous Ubuntu changes
- [Config] update configs and annotations after rebase
* Miscellaneous upstream changes
- RISC-V: Use SBI SRST extension when available
[ Ubuntu: 5.15.0-23.23 ]
* jammy/linux: 5.15.0-23.23 -proposed tracker (LP: #1964573)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/master)
* [22.04 FEAT] KVM: Enable GISA support for Secure Execution guests
(LP: #1959977)
- KVM: s390: pv: make use of ultravisor AIV support
* intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16
(LP: #1958004)
- SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs
* CVE-2022-23960
- ARM: report Spectre v2 status through sysfs
- ARM: early traps initialisation
- ARM: use LOADADDR() to get load address of sections
- ARM: Spectre-BHB workaround
- ARM: include unprivileged BPF status in Spectre V2 reporting
- arm64: Add Neoverse-N2, Cortex-A710 CPU part definition
- arm64: Add HWCAP for self-synchronising virtual counter
- arm64: Add Cortex-X2 CPU part definition
- arm64: add ID_AA64ISAR2_EL1 sys register
- arm64: cpufeature: add HWCAP for FEAT_AFP
- arm64: cpufeature: add HWCAP for FEAT_RPRES
- arm64: entry.S: Add ventry overflow sanity checks
- arm64: spectre: Rename spectre_v4_patch_fw_mitigation_conduit
- KVM: arm64: Allow indirect vectors to be used without SPECTRE_V3A
- arm64: entry: Make the trampoline cleanup optional
- arm64: entry: Free up another register on kpti's tramp_exit path
- arm64: entry: Move the trampoline data page before the text page
- arm64: entry: Allow tramp_alias to access symbols after the 4K boundary
- arm64: entry: Don't assume tramp_vectors is the start of the vectors
- arm64: entry: Move trampoline macros out of ifdef'd section
- arm64: entry: Make the kpti trampoline's kpti sequence optional
- arm64: entry: Allow the trampoline text to occupy multiple pages
- arm64: entry: Add non-kpti __bp_harden_el1_vectors for mitigations
- arm64: entry: Add vectors that have the bhb mitigation sequences
- arm64: entry: Add macro for reading symbol addresses from the trampoline
- arm64: Add percpu vectors for EL1
- arm64: proton-pack: Report Spectre-BHB vulnerabilities as part of
Spectre-v2
- arm64: Mitigate spectre style branch history side channels
- KVM: arm64: Allow SMCCC_ARCH_WORKAROUND_3 to be discovered and migrated
- arm64: Use the clearbhb instruction in mitigations
- arm64: proton-pack: Include unprivileged eBPF status in Spectre v2
mitigation reporting
- ARM: fix build error when BPF_SYSCALL is disabled
* CVE-2021-26401
- x86/speculation: Use generic retpoline by default on AMD
- x86/speculation: Update link to AMD speculation whitepaper
- x86/speculation: Warn about Spectre v2 LFENCE mitigation
- x86/speculation: Warn about eIBRS + LFENCE + Unprivileged eBPF + SMT
* CVE-2022-0001
- x86,bugs: Unconditionally allow spectre_v2=retpoline,amd
- x86/speculation: Rename RETPOLINE_AMD to
[Kernel-packages] [Bug 1962010] Re: Cherrypick features and fixes from v5.17 for sifive dtbs
This bug was fixed in the package linux-riscv - 5.15.0-1005.5
---
linux-riscv (5.15.0-1005.5) jammy; urgency=medium
* jammy/linux-riscv: 5.15.0-1005.5 -proposed tracker (LP: #1965783)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
* dependency on crda obsolete according to Debian (LP: #1958918)
- [Packaging] switch dependency from crda to wireless-regdb
* Excessive size of kernel modules on RISC-V - modules unstripped
(LP: #1964335)
- SAUCE: scripts/Makefile.modinst discard-locals from modules
* Cherrypick features and fixes from v5.17 for sifive dtbs (LP: #1962010)
- riscv: dts: sifive: use only generic JEDEC SPI NOR flash compatible
- riscv: dts: sifive: fix Unleashed board compatible
- Revert "SiFive HiFive Unleashed: Add PWM LEDs (D1, D2, D3, D4)"
- riscv: dts: sifive: drop duplicated nodes and properties in sifive
- riscv: dts: sifive: add missing compatible for plic
- riscv: dts: sifive unmatched: Name gpio lines
- riscv: dts: sifive unmatched: Expose the board ID eeprom
- riscv: dts: sifive unmatched: Expose the PMIC sub-functions
- Revert "riscv: sifive: unmatched: update for 16GB rev3"
- riscv: dts: sifive unmatched: Fix regulator for board rev3
- riscv: dts: sifive unmatched: Link the tmp451 with its power supply
- riscv: dts: sifive: Group tuples in interrupt properties
- riscv: dts: sifive: Group tuples in register properties
- riscv: dts: sifive: fu540-c000: Drop bogus soc node compatible values
- riscv: dts: sifive: fu540-c000: Fix PLIC node
- riscv: dts: sifive unmatched: Add gpio poweroff
* riscv: backport support for SiFive Unmatched (LP: #1910965)
- SiFive HiFive Unleashed: Add PWM LEDs (D1, D2, D3, D4)
* Miscellaneous Ubuntu changes
- [Config] update configs and annotations after rebase
* Miscellaneous upstream changes
- RISC-V: Use SBI SRST extension when available
[ Ubuntu: 5.15.0-23.23 ]
* jammy/linux: 5.15.0-23.23 -proposed tracker (LP: #1964573)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/master)
* [22.04 FEAT] KVM: Enable GISA support for Secure Execution guests
(LP: #1959977)
- KVM: s390: pv: make use of ultravisor AIV support
* intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16
(LP: #1958004)
- SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs
* CVE-2022-23960
- ARM: report Spectre v2 status through sysfs
- ARM: early traps initialisation
- ARM: use LOADADDR() to get load address of sections
- ARM: Spectre-BHB workaround
- ARM: include unprivileged BPF status in Spectre V2 reporting
- arm64: Add Neoverse-N2, Cortex-A710 CPU part definition
- arm64: Add HWCAP for self-synchronising virtual counter
- arm64: Add Cortex-X2 CPU part definition
- arm64: add ID_AA64ISAR2_EL1 sys register
- arm64: cpufeature: add HWCAP for FEAT_AFP
- arm64: cpufeature: add HWCAP for FEAT_RPRES
- arm64: entry.S: Add ventry overflow sanity checks
- arm64: spectre: Rename spectre_v4_patch_fw_mitigation_conduit
- KVM: arm64: Allow indirect vectors to be used without SPECTRE_V3A
- arm64: entry: Make the trampoline cleanup optional
- arm64: entry: Free up another register on kpti's tramp_exit path
- arm64: entry: Move the trampoline data page before the text page
- arm64: entry: Allow tramp_alias to access symbols after the 4K boundary
- arm64: entry: Don't assume tramp_vectors is the start of the vectors
- arm64: entry: Move trampoline macros out of ifdef'd section
- arm64: entry: Make the kpti trampoline's kpti sequence optional
- arm64: entry: Allow the trampoline text to occupy multiple pages
- arm64: entry: Add non-kpti __bp_harden_el1_vectors for mitigations
- arm64: entry: Add vectors that have the bhb mitigation sequences
- arm64: entry: Add macro for reading symbol addresses from the trampoline
- arm64: Add percpu vectors for EL1
- arm64: proton-pack: Report Spectre-BHB vulnerabilities as part of
Spectre-v2
- arm64: Mitigate spectre style branch history side channels
- KVM: arm64: Allow SMCCC_ARCH_WORKAROUND_3 to be discovered and migrated
- arm64: Use the clearbhb instruction in mitigations
- arm64: proton-pack: Include unprivileged eBPF status in Spectre v2
mitigation reporting
- ARM: fix build error when BPF_SYSCALL is disabled
* CVE-2021-26401
- x86/speculation: Use generic retpoline by default on AMD
- x86/speculation: Update link to AMD speculation whitepaper
- x86/speculation: Warn about Spectre v2 LFENCE mitigation
- x86/speculation: Warn about eIBRS + LFENCE + Unprivileged eBPF + SMT
* CVE-2022-0001
- x86,bugs: Unconditionally allow spectre_v2=retpoline,amd
- x86/speculation: Rename RETPOLINE_AMD to
[Kernel-packages] [Bug 1967186] Re: ezcap u2 card error
Last working kernel 5.13.27, and its with almost any usb uvc compliant device.. -- 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/1967186 Title: ezcap u2 card error Status in linux package in Ubuntu: Confirmed Bug description: I have a ezcap u3 internal hdmi capture and displays this message, also takes upt to 5 minutes to boot, i tried on windows and works well, if i unplug it, boot normally This is the message.. usb 11-1: Failed to query (GET_DEF) UVC control 11 on unit 1: -32 (exp. 2). ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-lowlatency 5.13.0.39.48 ProcVersionSignature: Ubuntu 5.13.0-39.44-lowlatency 5.13.19 Uname: Linux 5.13.0-39-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: cjdg 4203 F pulseaudio /dev/snd/controlC2: cjdg 4203 F pulseaudio /dev/snd/controlC1: cjdg 4203 F pulseaudio /dev/snd/controlC0: cjdg 4203 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 16:54:18 2022 HibernationDevice: RESUME=UUID=7a2c1228-23b3-4579-90e4-ba6e209dd9d4 resume_offset=34816 InstallationDate: Installed on 2021-04-29 (335 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Gigabyte Technology Co., Ltd. GA-970A-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-lowlatency root=UUID=5bf8e992-a5cc-4b4b-b331-69111d42c8f3 ro threadirqs quiet splash resume=UUID=7a2c1228-23b3-4579-90e4-ba6e209dd9d4 resume_offset=34816 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.13.0-39-lowlatency N/A linux-backports-modules-5.13.0-39-lowlatency N/A linux-firmware1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-14 (167 days ago) dmi.bios.date: 10/22/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: GA-970A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd10/22/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: GA-970A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967186/+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 1956467] Re: powerlight stays on after shutdown
Can confirm same issue with following setup AMD® A12-9720p Ubuntu 20.04 LTS. Suspend is broken in 5.13.0-39-generic and 5.13.0-37-generic, it only works in 5.13.0-35-generic. -- 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/1956467 Title: powerlight stays on after shutdown Status in linux package in Ubuntu: Confirmed Bug description: After kernel upgrade from 5.11.0.40 to versions 5.11.0.41, 5.11.0.43, 5.11.0.44 power-button light fails to switch off, after shutdown. shutdown can be triggered from command line or via desktop menu, result is the same. After rebooting from 5.11.0.40 normal functionality is restored. systemd appears to complete shutdown looking at the logs (see attached) Switching to suspend mode (sleep) functions as expected (power light blinks) and stays permanently on after wake-up. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christian 1896 F pulseaudio /dev/snd/controlC0: christian 1896 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (609 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81MT Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.24 Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/09/2019 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN23WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.23 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN23WW(V2.02):bd05/09/2019:br2.23:efr2.23:svnLENOVO:pn81MT:pvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956467/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I've also got an Avantree DG80 as a workaround and I can confirm it works with my Trekz OpenComm headset. It supports sounds up to 8 kHz (corresponding to mSBC with a 16 kHz sampling frequency) with the mic enabled, while anything connected directly to Linux bluetooth only goes up to 4 kHz in HSP/HFP mode (CVSD). The sound with mSBC is still noticeably worse than in A2DP mode when listening to music, but a lot better than CVSD. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
found some other reports that claim i915.fastboot=0 is a workaround, and can confirm it does work around the issue on jammy's current 5.15 kernel. https://www.reddit.com/r/pop_os/comments/scqr4n/dell_xps_15_9575_screen_flickering_upon_boot/ https://bugs.archlinux.org/task/72134 https://gitlab.freedesktop.org/drm/intel/-/issues/4952 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #4952 https://gitlab.freedesktop.org/drm/intel/-/issues/4952 -- 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/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash 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.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+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 1966010] Re: Fix audio on Zbook Studio G9
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1032.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966010 Title: Fix audio on Zbook Studio G9 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Cirrus Logic AMP still doesn't work on Zbook Studio G9. Moreoever, The audio mute LEDs stop working after the said SRU. [Fix] Correcly interpret the debounce time from ACPI to gpiolib, and apply the correct quirk for the audio mute LEDs. [Where problems could occur] It's possible that some hardwares rely on the "wrong" debounce time to work, however the fix is to increase the debounce time, so it's more forgiving than decreasing. The LED fix is only applied to one system, so it's specifi and won't cause too much trouble. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966010/+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 1965846] Re: Enable the mic-mute led on Dell XPS 9315
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1032.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965846 Title: Enable the mic-mute led on Dell XPS 9315 Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] On Dell's XPS 9315, the MIC-Mute function is working but the LED(on F4) state is not changed accordingly. [Fix] Dell's mic mute support in privacy mode has been upstream, but the the mic-mute led support is still SAUCE patch which is maintained with DMI based quirk. Add a new SKU for XPS 9315 until Dell's official fix for the mic-mute led. [Test Case] 1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only working on the particular SKU defined in DMI table. Will need to drop it when Dell release the official solution. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1965846/+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 1966680] Re: Revert drm/amd/pm: enable ASPM by default
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1032.35
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1966680
Title:
Revert drm/amd/pm: enable ASPM by default
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[Impact]
With WX3200 and 20.04d kernel the unit freezes on resume
[Fix]
commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
by default but a variety of hardware configurations it turns out that this
caused a regression.
Multiple SKUs with wx3200 gpus encounter the resume issue.
Before the real fix is landed, revert commit 0064b0ce85bb first.
[Test Case]
1. plug wx3200 on the adl machine and make it as a output.
2. suspend machine
3. check if machine could resume successfully
[Where problems could occur]
Low, don't make AMDGPU ASPM by default.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1966680/+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 1964983] Re: IPU6 camera has no function on Andrews MLK
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1032.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1964983 Title: IPU6 camera has no function on Andrews MLK Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Confirmed Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Bug description: [SRU Justification] [Impact] New Andrews MLK equips yet another new I2C sensor and takes a few driver updates to function normally. [Fix] Upstream driver commit: https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e [Test Case] To verify by following steps: 1. disable secure boot 2. $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel 3. $ sudo add-apt-repository ppa:kchsieh/ipu6 4. $ sudo apt install linux-oem-5.14 version 5.14.0-9029-oem or newer 6. $ sudo apt install libipu6ep 7. $ sudo apt install libcamhal-ipu6ep-common 8. $ sudo apt install libcamhal-ipu6ep0 9. $ sudo apt install libgsticamerainterface-1.0-1 10. $ sudo apt install gstreamer1.0-icamera 11. $ sudo vim /etc/v4l2-relayd -FORMAT=YUY2 +FORMAT=NV12 12. $ sudo reboot [Where problems could occur] Intel IPU6 platform is still under development and is not capable of advanced power management features and may still suffer from stability issues. [Other Info] Nomination for 5.15 is necessary for oem-5.14 to hwe-5.15 migration and will depend on previous SRU proposal in bug 1955383 (https://lists.ubuntu.com/archives/kernel-team/2022-March/128922.html). Nomination for generic-5.17 and oem-5.17 is still under planning. == original bug description == The new platform uses yet another ov sensor OV02C10. Prerequisites: * kernel fix: https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e * ipu6-camera-bins: https://github.com/intel/ipu6-camera-bins/commit/7cc1dc2d9ab2b0766e034edf808d751bd25b42cc * ipu6-camera-hal: https://github.com/intel/ipu6-camera-hal/commit/b9b56de11de70b7c4520595176e4831bacf4a7fe * icamerasrc: https://github.com/intel/icamerasrc/commit/a35978264002acaad72bb9956238ccaef3743932 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964983/+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 1965496] Re: alsa: enable the cirrus-logic side-codec to make the speaker output sound
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1032.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965496 Title: alsa: enable the cirrus-logic side-codec to make the speaker output sound Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] We have a couple of lenovo latops models which have cirrus-logic side codec between realtek codec and speaker, it plays a role as amplifier, we need to enable this side-codec, otherwise the speaker can't output sound. [Fix] Backport codec patches and some i2c and acpi detection patches from mainline kernel and linux-next [Test] boot the patched kernel, run speaker test, both left and right channel could work well. [Where problems could occur] If it could introduce regression, it will be on soc wm_adsp codec drivers, since most of patch are adding new codec drivers, it will not touch existing codec drivers. If a machine with wm_adsp codec can't output sound or record sound, it means this SRU introduce the regression on wm_adsp driver, but this possibility is very low, since all patches are picked from mainline kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1965496/+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 1966835] Re: e1000e reports hardware hang
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1032.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966835 Title: e1000e reports hardware hang Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Bug description: [Impact] Encounter the e1000e h/w hang while doing suspend/resume test kernel: e1000e :00:1f.6 enp0s31f6: Detected Hardware Unit Hang: TDH <4> TDT <9> next_to_use <9> next_to_clean <4> buffer_info[next_to_clean]: time_stamp <100056968> next_to_watch <4> jiffies <100056c40> next_to_watch.status <0> MAC Status <40080283> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status <3000> PCI Status <10> [Fix] Intel provides a patch to fix this issue which is landed in v5.17-rc7 1866aa0d0d64 e1000e: Fix possible HW unit hang after an s0ix exit [Test] Verified by ODM on Dell machines [Where problems could occur] The fix disable PHY reset when runtime suspended, the PHY will be reset after resumed. So, it should not introduce any regression. [Misc] Jammy(5.15) has this fix through stable update. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966835/+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 1946303] Re: No video after wake from S3 due to Nvidia driver crash
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 nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+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 1967434] [NEW] nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: I attempted an upgrade a few weeks ago and have been receiving repeated errors since. I'm not sure what version I upgraded to or where to find that information, but this may be the upgrade error listed on the previous page of reported bugs. I am operating Ubuntu 20.04.2 LTS. I apologize for my limited knowledge. I am a Windows Refugee, who migrated before forced obsolescence of Windows 7. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-39-generic Date: Wed Mar 30 15:07:03 2022 DuplicateSignature: dkms:nvidia-dkms-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-03-06 (390 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1967434 Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: I attempted an upgrade a few weeks ago and have been receiving repeated errors since. I'm not sure what version I upgraded to or where to find that information, but this may be the upgrade error listed on the previous page of reported bugs. I am operating Ubuntu 20.04.2 LTS. I apologize for my limited knowledge. I am a Windows Refugee, who migrated before forced obsolescence of Windows 7. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-39-generic Date: Wed Mar 30 15:07:03 2022 DuplicateSignature: dkms:nvidia-dkms-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-03-06 (390 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build 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-460/+bug/1967434/+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 1967338] 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 1967338 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/1967338 Title: linux: CONFIG_SERIAL_8250_MID=y Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: SRU Justification [Impact] See discussion at https://lists.ubuntu.com/archives/kernel- team/2022-March/128690.html [Test Plan] Boot with serial console connected [Where things could go wrong] Not really a lot of opportunity for regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338/+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 1967338] [NEW] linux: CONFIG_SERIAL_8250_MID=y
Public bug reported: SRU Justification [Impact] See discussion at https://lists.ubuntu.com/archives/kernel- team/2022-March/128690.html [Test Plan] Boot with serial console connected [Where things could go wrong] Not really a lot of opportunity for regression ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) 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/1967338 Title: linux: CONFIG_SERIAL_8250_MID=y Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: SRU Justification [Impact] See discussion at https://lists.ubuntu.com/archives/kernel- team/2022-March/128690.html [Test Plan] Boot with serial console connected [Where things could go wrong] Not really a lot of opportunity for regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338/+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 1967336] Re: linux-azure: CONFIG_HIBERNATION=y
https://lists.ubuntu.com/archives/kernel-team/2022-March/129080.html ** Description changed: SRU Justification [Impact] - Azure arm64 tuned kernels do not hibernation. + Azure arm64 tuned kernels do not support hibernation. [Test Plan] Microsoft tested [Where things could go wrong] Hibernation may fail. -- 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/1967336 Title: linux-azure: CONFIG_HIBERNATION=y Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Impish: In Progress Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Azure arm64 tuned kernels do not support hibernation. [Test Plan] Microsoft tested [Where things could go wrong] Hibernation may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967336/+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 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #5534 https://gitlab.freedesktop.org/drm/intel/-/issues/5534 ** Also affects: linux via https://gitlab.freedesktop.org/drm/intel/-/issues/5534 Importance: Unknown Status: Unknown -- 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/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash 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.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+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 1967336] Re: linux-azure: CONFIG_HIBERNATION=y
** Changed in: linux-azure (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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1967336 Title: linux-azure: CONFIG_HIBERNATION=y Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Impish: In Progress Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Azure arm64 tuned kernels do not hibernation. [Test Plan] Microsoft tested [Where things could go wrong] Hibernation may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967336/+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 1967336] [NEW] linux-azure: CONFIG_HIBERNATION=y
Public bug reported: SRU Justification [Impact] Azure arm64 tuned kernels do not hibernation. [Test Plan] Microsoft tested [Where things could go wrong] Hibernation may fail. ** Affects: linux-azure (Ubuntu) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Focal) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Impish) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Also affects: linux-azure (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Impish) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1967336 Title: linux-azure: CONFIG_HIBERNATION=y Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Impish: In Progress Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] Azure arm64 tuned kernels do not hibernation. [Test Plan] Microsoft tested [Where things could go wrong] Hibernation may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967336/+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 1964711] Re: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked
After the things I did in https://bugs.launchpad.net/ubuntu/+source/linux- hwe-5.13/+bug/1964711/comments/7, I am now facing a worse problem. My computer no longer recognizes my display correctly. Since the boot screen, the resolution is the minimum available (1024x768). I think my system no longer selects the correct driver for my graphics card. Running "sudo lshw -c video" yields the following: ``` *-display UNCLAIMED description: VGA compatible controller product: Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:03:00.0 version: ca width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list configuration: latency=0 resources: memory:4000-4fff memory:5000-501f ioport:3000(size=256) memory:5030-5037 memory:c-d ``` Running "lsmod | grep amd" prints nothing (it used to before) and "dkms status amdgpu" also prints nothing. I tried uninstalling the drivers I installed and also tried installing drivers from different source. I tried to look for issues in my BIOS settings. All to no avail. If I don’t find a solution to this, I will resort to completely re-installing Ubuntu 20.04. I have luckily completed a full backup before. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: After locking Ubuntu and leaving it unattended for a while, the operating system cannot be unlocked anymore. No means of user input (e.g. typing on the keyboard, moving the mouse) produce the lock screen and I have to shut down my computer by pressing down the power button. The attached monitor does not receive a signal from the computer during these attempts. This started to happen several weeks ago and worked without a problem before then. Due to the nature of this issue, I can neither report any errors occurring nor can I observe any other out of the ordinary things from happening. Thus, I don’t know which package is causing the issue. Also, this issue happens every time I leave the computer unattended for a longer time and lock it. However, locking it and triggering an input immediately after does produce the lock screen, so the lock screen seems to work in principle. Description: Ubuntu 20.04.4 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+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 1939638] Re: [regression] USB device is not detected during boot
Hi, would it be possible to provide the dmesg output after boot?
Could you also provide the output of 'lspci -nn | grep USB' since since a lot
of these issues seem to be USB card specific and I am unfamiliar with your
hardware.
As Jarkko mentioned, in 5.4.0-90 there were some patches that were
reverted to do with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945211 that might
be now affecting your machines.
Thanks,
- Luke
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939638
Title:
[regression] USB device is not detected during boot
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-intel package in Ubuntu:
Confirmed
Status in linux-intel-5.13 package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux-intel source package in Focal:
Confirmed
Status in linux-intel-5.13 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in linux-intel source package in Hirsute:
Invalid
Status in linux-intel-5.13 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
The USB devices (keyboard, storage...) are failed to be detected when
connecting to the problematic root hubs which need longer PowerOn-to-PowerGood
delay than it claims in the hub descriptor. It's caused by the upstream fix
90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub").
[Fix]
Reverting the upstream fix until a formal fix been placed.
[Test Case]
1. Plug the USB device to the ports of problematic root hub.
2. Power on the machine.
3. Check if the USB device can work or not after boot.
[Regression Potential]
Low. The longer delay is proven safe in old kernels.
== Original Bug Description ==
[Summary]
The USB devices (keyboard, storage...) are failed to be detected during boot
after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However,
they will be detected and working ok after re-plugging. The kernel output shows
as down below during boot
[ 39.350435] hub 1-0:1.0: USB hub found
[ 39.398835] hub 1-0:1.0: 12 ports detected
[ 39.622744] usb usb1-port3: couldn't allocate usb_device
And when I plug out then plug in the same device, it shows
[57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd
[57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099,
bcdDevice= 1.14
[57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
After doing kernel bisecting, we found the upstream commit
https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2
makes the difference. It indicates that the delay for the root hub from
power_on to power_good is not long enough. There was no problem if the delay is
100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2
milliseconds. And the XHCI spec also says in section 5.4.8
"""
The host is required to have power stable to the port within 20 milliseconds
of the '0' to '1' transition of PP. If PPC = '1', software is responsible for
waiting 20ms.
"""
The commit seems to follow the SPEC but could cause problems on some
hubs.
[Reproduce Steps]
1. Plug the USB device to the physical port #1 and #4 which belongs to
high-speed hub.
2. Power on the machine.
3. Check if the USB device can work or not after boot.
[Results]
Expected:
All usb devices connect to the hub should work OK.
Actual:
USB devices connects to high-speed hub can not be probed.
[Additional Information]
Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26
[Upstream bug]
https://bugzilla.kernel.org/show_bug.cgi?id=214021
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1939638/+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 1966090] Re: Linux 5.4.0-105 breaks Bluetooth and makes system too slow to use
Fixed in 5.4.0-107 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966090 Title: Linux 5.4.0-105 breaks Bluetooth and makes system too slow to use Status in linux package in Ubuntu: Fix Released Bug description: Currently running this kernel which is working fine: Linux 5.4.0-104-generic #118-Ubuntu SMP Wed Mar 2 19:02:41 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Immediately after installing the latest kernel update to Linux 5.4.0-105 and rebooting, the following error is printed endlessly to console multiple times per second by Bluetooth hci: Malicious advertising data. Stopping processing I don't have the exact log because my system was unusable beyond reading the console and I had to force reboot, but that was definitely the message that was printed. I have no Bluetooth devices powered on when booting (just my laptop's adapter I guess). The system is also too slow to do anything, I have to force reboot. Reverted to kernel 5.4.0-104 and problems are gone. See the lspci-vnvn.log but keep in mind that I generated it on the working 5.4.0-104 kernel, as it was impossible to do anything on 5.4.0-105. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966090/+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
Re: [Kernel-packages] [Bug 1964333] Re: window decoration glitch with nvidia driver 495 and 510
Well it doesn't work: user@computer:~$ apport-collect 1964333 Package nvidia-graphics-drivers-495 not installed and no hook available, ignoring Package nvidia-graphics-drivers-510 not installed and no hook available, ignoring *** Updating problem report No additional information collected. Press any key to continue... No pending crash reports. Try --help for more information. user@computer:~$ sudo apt install nvidia-graphics-drivers-510 [sudo] password for lacki: Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package nvidia-graphics-drivers-510 Best, Mateusz On Tue, 2022-03-29 at 19:55 +, Paul White wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. > > Please execute the following command only once, as it will > automatically > gather debugging information, in a terminal: > > apport-collect 1964333 > > and than change the status of each bug task back to 'New'. > > When reporting bugs in the future please use apport by using 'ubuntu- > bug' and the name of the package affected. You can learn more about > this > functionality at https://wiki.ubuntu.com/ReportingBugs. > > ** Package changed: ubuntu => nvidia-graphics-drivers-510 (Ubuntu) > > ** Also affects: nvidia-graphics-drivers-495 (Ubuntu) > Importance: Undecided > Status: New > > ** Tags added: impish > > ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) > Status: New => Incomplete > > ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-495 in Ubuntu. https://bugs.launchpad.net/bugs/1964333 Title: window decoration glitch with nvidia driver 495 and 510 Status in nvidia-graphics-drivers-495 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Bug description: With Ubuntu 21.10, with nvidia driver package 495 and 510 I have the graphics glitch after each login. The icons in the top bad of the window seem distorted by their upscaled "shadows" This can be removed by restarting the gnome-shell (alt+f2 and then "r" command). Under 470 no such error exist, Description: Ubuntu 21.10 Release: 21.10 PS. It seems to me attaching two files to a bug report is not possible. Can it be added? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-495/+bug/1964333/+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 1944574] Re: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
I believe the "EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary" that was reported on this bug is not what is preventing the VM from booting. If you look into the full log you provided, that message is logged both on the boot that succeeded and in the one that got stuck. I believe whatever was done in the VM in between these reboots, might have caused the problem you are observing. There's also a known problem on linux-oracle kernel that prevents you from seeing the serial console. That is being fixed for Focal images on the linux-oracle 5.13.0.1023.28~20.04.1 kernel, which is currenlty in focal-proposed. If this is something you can reproduce with Focal images, using the kernel from proposed might help you see what is really preventing the VM from starting. We'll review the 'kernel image not aligned on 64k boundary' error anyway to assess what might be causing it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1944574 Title: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary Status in linux-oracle package in Ubuntu: Confirmed Bug description: While reviewing some dkms failures on arm64 impish/linux-oracle, i noticed this: ... EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... ... and the VM doesn't come back. Full log here: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/arm64/b/backport-iwlwifi- dkms/20210921_165307_4f8e0@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1944574/+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 1960322] Re: linux-azure: net: mana: Add handling of CQE_RX_TRUNCATED
This bug was fixed in the package linux-azure - 5.13.0-1021.24 --- linux-azure (5.13.0-1021.24) impish; urgency=medium * impish/linux-azure: 5.13.0-1021.24 -proposed tracker (LP: #1966226) [ Ubuntu: 5.13.0-39.44 ] * impish/linux: 5.13.0-39.44 -proposed tracker (LP: #1966236) * CVE-2022-27666 - sock: remove one redundant SKB_FRAG_PAGE_ORDER macro - esp: Fix possible buffer overflow in ESP transformation * CVE-2022-1055 - net: sched: fix use-after-free in tc_new_tfilter() -- Ian May Mon, 28 Mar 2022 15:40:30 -0500 ** Changed in: linux-azure (Ubuntu Impish) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1055 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-27666 -- 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/1960322 Title: linux-azure: net: mana: Add handling of CQE_RX_TRUNCATED Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Released Status in linux-azure source package in Impish: Fix Released Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested the addition of [1] in order to better account for dropped packets. Patch [2] is not strictly required, but will prevent context adjustments with future patches. [1] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=e4b7621982d29f26ff4d39af389e5e675a4ffed4 [2] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=68f831355052 [Test Plan] Microsoft tested [Where things could go wrong] RX dropped statistics could be in error. [Other Info] SF: #00327708 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960322/+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 1960539] Re: linux-azure: Add Azure Blob driver to Ubuntu 18.04 image
This bug was fixed in the package linux-azure - 5.13.0-1021.24 --- linux-azure (5.13.0-1021.24) impish; urgency=medium * impish/linux-azure: 5.13.0-1021.24 -proposed tracker (LP: #1966226) [ Ubuntu: 5.13.0-39.44 ] * impish/linux: 5.13.0-39.44 -proposed tracker (LP: #1966236) * CVE-2022-27666 - sock: remove one redundant SKB_FRAG_PAGE_ORDER macro - esp: Fix possible buffer overflow in ESP transformation * CVE-2022-1055 - net: sched: fix use-after-free in tc_new_tfilter() -- Ian May Mon, 28 Mar 2022 15:40:30 -0500 ** Changed in: linux-azure (Ubuntu Impish) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1055 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-27666 -- 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/1960539 Title: linux-azure: Add Azure Blob driver to Ubuntu 18.04 image Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Released Status in linux-azure source package in Impish: Fix Released Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Azure blob driver adds support for accelerated access to Azure Blob storage for Azure VMs. Azure host uses its native network to perform Blob requests directly to Blob servers. [Test Case] Microsoft tested [Where things could go wrong] There should be little chance of regression since this is an elective module. [Other Info] SF: #00327792 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960539/+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 1961300] Re: linux-azure: Fix NUMA node assignment when kernel boots with custom NUMA topology
This bug was fixed in the package linux-azure - 5.13.0-1021.24
---
linux-azure (5.13.0-1021.24) impish; urgency=medium
* impish/linux-azure: 5.13.0-1021.24 -proposed tracker (LP: #1966226)
[ Ubuntu: 5.13.0-39.44 ]
* impish/linux: 5.13.0-39.44 -proposed tracker (LP: #1966236)
* CVE-2022-27666
- sock: remove one redundant SKB_FRAG_PAGE_ORDER macro
- esp: Fix possible buffer overflow in ESP transformation
* CVE-2022-1055
- net: sched: fix use-after-free in tc_new_tfilter()
-- Ian May Mon, 28 Mar 2022 15:40:30 -0500
** Changed in: linux-azure (Ubuntu Impish)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1055
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-27666
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1961300
Title:
linux-azure: Fix NUMA node assignment when kernel boots with custom
NUMA topology
Status in linux-azure package in Ubuntu:
Fix Committed
Status in linux-hwe-5.11 package in Ubuntu:
Invalid
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-hwe-5.11 source package in Focal:
In Progress
Status in linux-azure source package in Impish:
Fix Released
Status in linux-hwe-5.11 source package in Impish:
Invalid
Status in linux-azure source package in Jammy:
Fix Committed
Status in linux-hwe-5.11 source package in Jammy:
Invalid
Bug description:
SRU Justification
[Impact]
When kernel boots with a NUMA topology with some NUMA nodes offline, the PCI
driver should only set an online NUMA node on the device. This can happen
during KDUMP where some NUMA nodes are not made online by the KDUMP kernel.
This patch also fixes the case where kernel is booting with "numa=off".
Fixes: 999dd956d838 ("PCI: hv: Add support for protocol 1.3 and
support PCI_BUS_RELATIONS2")
[Test Case]
Microsoft tested.
[Where things could go wrong]
NUMA node assignments could be wrong.
[Other Info]
SF: #00323281
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1961300/+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 1966098] Re: linux-azure: arm64 network performance improvement
This bug was fixed in the package linux-azure - 5.13.0-1021.24 --- linux-azure (5.13.0-1021.24) impish; urgency=medium * impish/linux-azure: 5.13.0-1021.24 -proposed tracker (LP: #1966226) [ Ubuntu: 5.13.0-39.44 ] * impish/linux: 5.13.0-39.44 -proposed tracker (LP: #1966236) * CVE-2022-27666 - sock: remove one redundant SKB_FRAG_PAGE_ORDER macro - esp: Fix possible buffer overflow in ESP transformation * CVE-2022-1055 - net: sched: fix use-after-free in tc_new_tfilter() -- Ian May Mon, 28 Mar 2022 15:40:30 -0500 ** Changed in: linux-azure (Ubuntu Impish) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1055 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-27666 -- 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/1966098 Title: linux-azure: arm64 network performance improvement Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Impish: Fix Released Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] The Microsoft validation team found the issue on arm64 Hyperv where server throughput was reduced by < 50%. [Fix] https://lore.kernel.org/lkml/1647533563-2170-1-git-send-email- mikel...@microsoft.com/T/#t [Where things could go wrong] Network performance could get worse, or data could be corrupted. [Other Info] SF: #00310705 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1966098/+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 1966499] Re: Recent 5.13 kernel has broken KVM support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Impish) 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/1966499 Title: Recent 5.13 kernel has broken KVM support Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: Upgrading to 5.13.0-37 or 5.13.0-39 immediately crashes my production servers as they hit: https://lore.kernel.org/all/f1ea22d3-cff8-406a-ad6a-cb8e0124a...@leemhuis.info/T/#md1f5c8c4aa01130a449a47f3e7559f06b0372f55 It looks like we need to get e90e51d5f01d included in those kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+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 1967141] Re: [FFe] [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core (openssl-ibmca)
** Package changed: linux (Ubuntu) => openssl-ibmca (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/1967141
Title:
[FFe] [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd
dumps core (openssl-ibmca)
Status in Ubuntu on IBM z Systems:
In Progress
Status in openssl-ibmca package in Ubuntu:
New
Bug description:
Dear Ubuntu Reelase Team, please consider the acceptance this feature
freeze exception about a new openssl-ibmca-2.2.3-0ubuntu1 package for
jammy, because:
Rationale for the exception:
- a severe issue is fixed (sshd core dump while using hw crypto)
6563dd2 ("use correct libica for ibmca_mechaList_test")
- another segmentation fault is fixed by:
e91e179 ("PKEY: Fix usage of ECX keys")
- and since these are the only two fixes between 2.2.2 and 2.2.3:
93a12d3 (tag: v2.2.3) Update to version 2.2.3
6563dd2 use correct libica for ibmca_mechaList_test
e91e179 PKEY: Fix usage of ECX keys
fae4490 (tag: v2.2.2) Update to version 2.2.2
the version 2.2.3 is a bug-fix only release,
and could be acceptable for a FFe
(according to https://wiki.ubuntu.com/FreezeExceptionProcess)
- But to get the new version compiled (esp. with e91e179) a backport of
e59cce5 ("Fix compilation for OpenSSL 3.0")
was needed on top.
- To me it wouldn't make sense to add the 3 commits above to v2.2.2,
since it would then be a package version that's a super-set
of upstream 2.2.3 anyway, hence asking for the FFe.
- The package now ships a sample config
(as well as the script to generate it,
in case one wants/needs to re-generate it).
upstream ChangeLog diff:
$ diff -u openssl-ibmca-2.2.2/ChangeLog openssl-ibmca-2.2.3/ChangeLog
--- openssl-ibmca-2.2.2/ChangeLog 2022-01-27 17:23:55.0 +0100
+++ openssl-ibmca-2.2.3/ChangeLog 2022-03-31 10:32:20.935374435 +0200
@@ -1,3 +1,6 @@
+* openssl-ibmca 2.2.3
+- Fix PKEY segfault with OpenSSL 3.0
+
* openssl-ibmca 2.2.2
- Fix tests with OpenSSL 3.0
- Build against libica 4.0
News:
-
There is no upstream NEWS file (or suchlike - the README.md is unchanged).
build log:
--
https://launchpadlibrarian.net/594086046/buildlog_ubuntu-jammy-s390x.openssl-ibmca_2.2.3-0ubuntu1_BUILDING.txt.gz
Install log:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967141/+attachment/5575230/+files/install-log_and_virification.txt
Testing:
The previous link also includes the testing and verification that I did,
hence I can confirm that the reported problem is solved.
On top a testsuite is executed when the package is build.
Local build:
Testsuite summary for openssl-ibmca 2.2.3
# TOTAL: 34
# PASS: 28
# SKIP: 6
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
PPA:
Testsuite summary for openssl-ibmca 2.2.3
# TOTAL: 34
# PASS: 26
# SKIP: 8
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
(Two more tests are (auto-)skipped when running a PPA build, because the
builder does not have access to the s390x crypto hardware.
(The other skipped tests are skipped by upstream, since they are known to
cause issues on openssl 3 systems).
description of proposed changes:
"PKEY: Fix usage of ECX keys" - the usage of ECX keys was fixed by using
proper missing set/get methods for opaque types.
New file src/openssl-compat.h introduced that holds the specific ossl_ecx*
function.
All this only effects ED25519, ED448, X25519 and X448 using s390x hardware
crypto.
"use correct libica for ibmca_mechaList_test" - the Makefile for
ibmca_mechaList_test is now generated during the configure run, to
make sure it links with the same libica variant as used by the
ibmca.so module.
"Fix compilation for OpenSSL 3.0" - the API used in the above commit
is not public (and introduces a line "include " that
cannot be resolved all the time - only compile if the OpenSSL 3.0
source tree is present). Hence the defines to be used are now copied
over, which makes the engine compile even without OpenSSL 3.0 source
tree.
In addition a sample config that allows to be simply copied over is
added to the package, as well as the script that generates it. That is
done for convenience reasons and reduces the configuration time to
just seconds.
[Kernel-packages] [Bug 1967141] Re: [FFe] [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core (openssl-ibmca)
** Description changed:
- Please consider to accept the integration of this new openssl-
- ibmca-2.2.3-0ubuntu1 package for jammy under the 'Freeze Exception
- Process', because:
+ Dear Ubuntu Reelase Team, please consider the acceptance this feature
+ freeze exception about a new openssl-ibmca-2.2.3-0ubuntu1 package for
+ jammy, because:
+ Rationale for the exception:
+
- a severe issue is fixed (sshd core dump while using hw crypto)
6563dd2 ("use correct libica for ibmca_mechaList_test")
- another segmentation fault is fixed by:
e91e179 ("PKEY: Fix usage of ECX keys")
- and since these are the only two fixes between 2.2.2 and 2.2.3:
93a12d3 (tag: v2.2.3) Update to version 2.2.3
6563dd2 use correct libica for ibmca_mechaList_test
e91e179 PKEY: Fix usage of ECX keys
fae4490 (tag: v2.2.2) Update to version 2.2.2
the version 2.2.3 is a bug-fix only release,
and could be acceptable for a FFe
(according to https://wiki.ubuntu.com/FreezeExceptionProcess)
- But to get the new version compiled (esp. with e91e179) a backport of
e59cce5 ("Fix compilation for OpenSSL 3.0")
was needed on top.
- To me it wouldn't make sense to add the 3 commits above to v2.2.2,
- since it would then be a package version that's a super-set
- of upstream 2.2.3 anyway, hence asking for the FFe.
+ since it would then be a package version that's a super-set
+ of upstream 2.2.3 anyway, hence asking for the FFe.
- The package now ships a sample config
(as well as the script to generate it,
in case one wants/needs to re-generate it).
- Here is the diff of the upstream ChangeLog:
+ upstream ChangeLog diff:
+
$ diff -u openssl-ibmca-2.2.2/ChangeLog openssl-ibmca-2.2.3/ChangeLog
--- openssl-ibmca-2.2.2/ChangeLog 2022-01-27 17:23:55.0 +0100
+++ openssl-ibmca-2.2.3/ChangeLog 2022-03-31 10:32:20.935374435 +0200
@@ -1,3 +1,6 @@
+* openssl-ibmca 2.2.3
+- Fix PKEY segfault with OpenSSL 3.0
+
* openssl-ibmca 2.2.2
- Fix tests with OpenSSL 3.0
- Build against libica 4.0
- There is no upstream NEWS file (or suchlike - the README.md is
- unchanged).
+ News:
+ -
+ There is no upstream NEWS file (or suchlike - the README.md is unchanged).
- The buildlog:
+ build log:
+ --
https://launchpadlibrarian.net/594086046/buildlog_ubuntu-jammy-s390x.openssl-ibmca_2.2.3-0ubuntu1_BUILDING.txt.gz
- The installlog:
+ Install log:
+
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967141/+attachment/5575230/+files/install-log_and_virification.txt
+ Testing:
+
The previous link also includes the testing and verification that I did,
hence I can confirm that the reported problem is solved.
On top a testsuite is executed when the package is build.
Local build:
Testsuite summary for openssl-ibmca 2.2.3
# TOTAL: 34
# PASS: 28
# SKIP: 6
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
PPA:
Testsuite summary for openssl-ibmca 2.2.3
# TOTAL: 34
# PASS: 26
# SKIP: 8
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
(Two more tests are (auto-)skipped when running a PPA build, because the
builder does not have access to the s390x crypto hardware.
(The other skipped tests are skipped by upstream, since they are known to
cause issues on openssl 3 systems).
+
+ description of proposed changes:
+
+
+ "PKEY: Fix usage of ECX keys" - the usage of ECX keys was fixed by using
proper missing set/get methods for opaque types.
+ New file src/openssl-compat.h introduced that holds the specific ossl_ecx*
function.
+ All this only effects ED25519, ED448, X25519 and X448 using s390x hardware
crypto.
+
+ "use correct libica for ibmca_mechaList_test" - the Makefile for
+ ibmca_mechaList_test is now generated during the configure run, to make
+ sure it links with the same libica variant as used by the ibmca.so
+ module.
+
+ "Fix compilation for OpenSSL 3.0" - the API used in the above commit is
+ not public (and introduces a line "include " that cannot
+ be resolved all the time - only compile if the OpenSSL 3.0 source tree
+ is present). Hence the defines to be used are now copied over, which
+ makes the engine compile even without OpenSSL 3.0 source tree.
+
+ In addition a sample config that allows to be simply copied over is
+ added to the package, as well as the script that generates it. That is
+ done for convenience reasons and reduces
[Kernel-packages] [Bug 1967141] Re: [FFe] [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core (openssl-ibmca)
** Description changed:
+ Please consider to accept the integration of this new openssl-
+ ibmca-2.2.3-0ubuntu1 package for jammy under the 'Freeze Exception
+ Process', because:
+
+ - a severe issue is fixed (sshd core dump while using hw crypto)
+ 6563dd2 ("use correct libica for ibmca_mechaList_test")
+
+ - another segmentation fault is fixed by:
+ e91e179 ("PKEY: Fix usage of ECX keys")
+
+ - and since these are the only two fixes between 2.2.2 and 2.2.3:
+ 93a12d3 (tag: v2.2.3) Update to version 2.2.3
+ 6563dd2 use correct libica for ibmca_mechaList_test
+ e91e179 PKEY: Fix usage of ECX keys
+ fae4490 (tag: v2.2.2) Update to version 2.2.2
+ the version 2.2.3 is a bug-fix only release,
+ and could be acceptable for a FFe
+ (according to https://wiki.ubuntu.com/FreezeExceptionProcess)
+
+ - But to get the new version compiled (esp. with e91e179) a backport of
+ e59cce5 ("Fix compilation for OpenSSL 3.0")
+ was needed on top.
+
+ - The package now ships a sample config
+ (as well as the script to generate it,
+in case one wants/needs to re-generate it).
+
+ Here is the diff of the upstream ChangeLog:
+ $ diff -u openssl-ibmca-2.2.2/ChangeLog openssl-ibmca-2.2.3/ChangeLog
+ --- openssl-ibmca-2.2.2/ChangeLog 2022-01-27 17:23:55.0 +0100
+ +++ openssl-ibmca-2.2.3/ChangeLog 2022-03-31 10:32:20.935374435 +0200
+ @@ -1,3 +1,6 @@
+ +* openssl-ibmca 2.2.3
+ +- Fix PKEY segfault with OpenSSL 3.0
+ +
+ * openssl-ibmca 2.2.2
+ - Fix tests with OpenSSL 3.0
+ - Build against libica 4.0
+
+ There is no upstream NEWS file (or suchlike - the README.md is
+ unchanged).
+
+ The buildlog:
+
https://launchpadlibrarian.net/594086046/buildlog_ubuntu-jammy-s390x.openssl-ibmca_2.2.3-0ubuntu1_BUILDING.txt.gz
+
+ The installlog:
+
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967141/+attachment/5575230/+files/install-log_and_virification.txt
+
+ The previous link also includes the testing and verification that I did,
+ hence I can confirm that the reported problem is solved.
+ On top a testsuite is executed when the package is build.
+ Local build:
+
+ Testsuite summary for openssl-ibmca 2.2.3
+
+ # TOTAL: 34
+ # PASS: 28
+ # SKIP: 6
+ # XFAIL: 0
+ # FAIL: 0
+ # XPASS: 0
+ # ERROR: 0
+
+ PPA:
+
+ Testsuite summary for openssl-ibmca 2.2.3
+
+ # TOTAL: 34
+ # PASS: 26
+ # SKIP: 8
+ # XFAIL: 0
+ # FAIL: 0
+ # XPASS: 0
+ # ERROR: 0
+
+ (Two more tests are (auto-)skipped when running a PPA build, because the
builder does not have access to the s390x crypto hardware.
+ (The other skipped tests are skipped by upstream, since they are known to
cause issues on openssl 3 systems).
+
+ _
+
+
---Problem Description---
Summary
===
New IBM HW with Crypto Accelerator cards attached
- Kernel level: 5.14
+ Kernel level: 5.14
Core dump when configuring the ibmca engine with libica = libica.so.4 in the
openssl.cnf file in the engine section.
The problem only occurs with OpenSSL 3.0 and is immediately reproducible.
-
Details
===
HINT: To be able to receive core dump files at all it is needed to change the
/etc/systemd/system.conf file entry DefaultLimitCORE=0:infinity to read
- DefaultLimitCORE=infinity:infinity
+ DefaultLimitCORE=infinity:infinity
On a system with ibmca engine configured system wide, when trying to use
the libica.so.4 to support the ibmca engine the sshd daemon dumps core
upon the first login attempt.
# openssl engine -c
(dynamic) Dynamic engine loading support
(ibmca) Ibmca hardware engine support
- [RSA, DSA, DH]
-
+ [RSA, DSA, DH]
Debug Data
==
core dump file in the attachments.
-
- Contact Information = christian.r...@de.ibm.com
-
+
+ Contact Information = christian.r...@de.ibm.com
+
---uname output---
Linux system 5.14.
-
+
---Debugger---
A debugger is not configured
-
+
---Steps to Reproduce---
1.) Edit /etc/systemd/system.conf file to allow core dumps:
- Change the line DefaultLimitCORE=0:infinity
- to read DefaultLimitCORE=infinity:infinity
+ Change the line DefaultLimitCORE=0:infinity
+ to read DefaultLimitCORE=infinity:infinity
2.) run: systemctl daemon-reload
- systemctl restart systemd-coredump.socket
+ systemctl restart systemd-coredump.socket
3.) Run the /usr/share/doc/openssl-ibmca/ibmca-engine-opensslconfig perl
script
4.) Edit the /etc/pki/tls file near the end to contain the line
- to back the ibmca engine by the
[Kernel-packages] [Bug 1967141] Re: [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core (openssl-ibmca)
Install-log and functional verification of the new package. ** Attachment added: "install-log_and_virification.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967141/+attachment/5575230/+files/install-log_and_virification.txt ** Summary changed: - [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core (openssl-ibmca) + [FFe] [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core (openssl-ibmca) -- 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/1967141 Title: [FFe] [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core (openssl-ibmca) Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: ---Problem Description--- Summary === New IBM HW with Crypto Accelerator cards attached Kernel level: 5.14 Core dump when configuring the ibmca engine with libica = libica.so.4 in the openssl.cnf file in the engine section. The problem only occurs with OpenSSL 3.0 and is immediately reproducible. Details === HINT: To be able to receive core dump files at all it is needed to change the /etc/systemd/system.conf file entry DefaultLimitCORE=0:infinity to read DefaultLimitCORE=infinity:infinity On a system with ibmca engine configured system wide, when trying to use the libica.so.4 to support the ibmca engine the sshd daemon dumps core upon the first login attempt. # openssl engine -c (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support [RSA, DSA, DH] Debug Data == core dump file in the attachments. Contact Information = christian.r...@de.ibm.com ---uname output--- Linux system 5.14. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1.) Edit /etc/systemd/system.conf file to allow core dumps: Change the line DefaultLimitCORE=0:infinity to read DefaultLimitCORE=infinity:infinity 2.) run: systemctl daemon-reload systemctl restart systemd-coredump.socket 3.) Run the /usr/share/doc/openssl-ibmca/ibmca-engine-opensslconfig perl script 4.) Edit the /etc/pki/tls file near the end to contain the line to back the ibmca engine by the libica.so.4 library as outlined in the /usr/share/doc/openssl-ibmca/README.md file 5.) Run: openssl engine -c 6.) Keep the current session open for subsequently stepping back to the original openssl.cnf! 7.) Open up a new ssh session to the system under test and watch the login to fail with broken pipe 8.) On the remaining session, run coreumpctl list / coredumpctl dump Userspace tool common name: openssl-ibmca Userspace rpm: openssl-ibmca-2.2.2-1.el9.s390x The userspace tool has the following bit modes: 64bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1967141/+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 1964756] Re: The nvidia debian/rules mis-compiles Modaliases
** Also affects: nvidia-graphics-drivers-510 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1964756 Title: The nvidia debian/rules mis-compiles Modaliases Status in OEM Priority Project: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: New Status in nvidia-graphics-drivers-510 source package in Impish: New Bug description: Although adding support GPU list here: https://github.com/tseliot/nvidia-graphics-drivers/commit/d2533550bc88ef00d6a56f71c4c09e43026a93d7 They are only show in "Pmaliases:" but "Modaliases:". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964756/+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 1967292] [NEW] net/mlx5e: Fix page DMA map/unmap attributes
Public bug reported: SRU Justification [Impact] Upstream commit 0b7cfa4082fbf550595bc0e40f05614bd83bf0cd is a fix to the Mellanox mlx5 driver that we would like to have you pick up. It fixes a bug that was introduced in the 4.7 kernel, so it should be applicable to pretty much every Linux distribution. The bug causes a Linux panic when a Mellanox CX-4 VF is present in the VM (for AccelNet) and swiotlb=force used on the kernel boot line. swiotlb=force would not normally be used, which is why we haven’t seen the problem reported previously, but it cropped up during some internal testing. We are trying to head off a potential problem in a future scenario for Confidential VMs. Primarily we want to ensure that any CVMs images have this fix, as we don’t want CVM images to exist in the wild that would fail in the future when CVMs with AccelNet are offered. Business Impact This scenario could also exist in non-Azure instances. [Test Case] Microsoft tested. [Where problems could appear] Weird DMA and data corruption issues might crop up. [Other Info] SF: #00328938 ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => Fix Released ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967292 Title: net/mlx5e: Fix page DMA map/unmap attributes Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Upstream commit 0b7cfa4082fbf550595bc0e40f05614bd83bf0cd is a fix to the Mellanox mlx5 driver that we would like to have you pick up. It fixes a bug that was introduced in the 4.7 kernel, so it should be applicable to pretty much every Linux distribution. The bug causes a Linux panic when a Mellanox CX-4 VF is present in the VM (for AccelNet) and swiotlb=force used on the kernel boot line. swiotlb=force would not normally be used, which is why we haven’t seen the problem reported previously, but it cropped up during some internal testing. We are trying to head off a potential problem in a future scenario for Confidential VMs. Primarily we want to ensure that any CVMs images have this fix, as we don’t want CVM images to exist in the wild that would fail in the future when CVMs with AccelNet are offered. Business Impact This scenario could also exist in non-Azure instances. [Test Case] Microsoft tested. [Where problems could appear] Weird DMA and data corruption issues might crop up. [Other Info] SF: #00328938 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967292/+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 1967141] Re: [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core (openssl-ibmca)
diff between openssl-ibmca_2.2.2-0ubuntu1 and openssl-ibmca_2.2.3-0ubuntu1 debdiff_openssl-ibmca_from_2.2.2-0ubuntu1_to_2.2.3-0ubuntu1.diff ** Patch added: "debdiff_openssl-ibmca_from_2.2.2-0ubuntu1_to_2.2.3-0ubuntu1.diff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967141/+attachment/5575218/+files/debdiff_openssl-ibmca_from_2.2.2-0ubuntu1_to_2.2.3-0ubuntu1.diff ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-z-systems 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/1967141 Title: [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core (openssl-ibmca) Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: ---Problem Description--- Summary === New IBM HW with Crypto Accelerator cards attached Kernel level: 5.14 Core dump when configuring the ibmca engine with libica = libica.so.4 in the openssl.cnf file in the engine section. The problem only occurs with OpenSSL 3.0 and is immediately reproducible. Details === HINT: To be able to receive core dump files at all it is needed to change the /etc/systemd/system.conf file entry DefaultLimitCORE=0:infinity to read DefaultLimitCORE=infinity:infinity On a system with ibmca engine configured system wide, when trying to use the libica.so.4 to support the ibmca engine the sshd daemon dumps core upon the first login attempt. # openssl engine -c (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support [RSA, DSA, DH] Debug Data == core dump file in the attachments. Contact Information = christian.r...@de.ibm.com ---uname output--- Linux system 5.14. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1.) Edit /etc/systemd/system.conf file to allow core dumps: Change the line DefaultLimitCORE=0:infinity to read DefaultLimitCORE=infinity:infinity 2.) run: systemctl daemon-reload systemctl restart systemd-coredump.socket 3.) Run the /usr/share/doc/openssl-ibmca/ibmca-engine-opensslconfig perl script 4.) Edit the /etc/pki/tls file near the end to contain the line to back the ibmca engine by the libica.so.4 library as outlined in the /usr/share/doc/openssl-ibmca/README.md file 5.) Run: openssl engine -c 6.) Keep the current session open for subsequently stepping back to the original openssl.cnf! 7.) Open up a new ssh session to the system under test and watch the login to fail with broken pipe 8.) On the remaining session, run coreumpctl list / coredumpctl dump Userspace tool common name: openssl-ibmca Userspace rpm: openssl-ibmca-2.2.2-1.el9.s390x The userspace tool has the following bit modes: 64bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1967141/+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 1953340] Re: kernel revocation list check during boot fails on Trusty (old keyctl?)
A manual test shows it's failing because:
$ sudo keyctl list %:.blacklist
Unparsable key: '%:.blacklist'
$ keyctl --version
keyctl from keyutils-1.5.6 (Built 2013-10-21)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1953340
Title:
kernel revocation list check during boot fails on Trusty (old keyctl?)
Status in ubuntu-kernel-tests:
New
Status in linux-kvm package in Ubuntu:
New
Bug description:
Boot test of 2021.11.29/trusty/linux-azure/4.15.0-1128.141~14.04.1
failed on kernel_revocation_list check with:
-
19:21:35 INFO | STARTubuntu_boot.kernel_revocation_list
ubuntu_boot.kernel_revocation_listtimestamp=1638559295timeout=300
localtime=Dec 03 19:21:35
19:21:35 DEBUG| Persistent state client._record_indent now set to 2
19:21:35 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_boot.kernel_revocation_list', 'ubuntu_boot.kernel_revocation_list')
19:21:35 DEBUG| Waiting for pid 2224 for 300 seconds
19:21:36 INFO | Checking kernel revocation list
19:21:36 DEBUG| Running 'python3
/home/azure/autotest/client/tests/ubuntu_boot/kernel_revocation_list.py'
19:21:36 DEBUG| [stderr] test_revocations (__main__.TestRevocationList) ...
Unparsable key: '%:.blacklist'
19:21:36 DEBUG| [stderr] ERROR
19:21:36 DEBUG| [stderr]
19:21:36 DEBUG| [stderr]
==
19:21:36 DEBUG| [stderr] ERROR: test_revocations (__main__.TestRevocationList)
19:21:36 DEBUG| [stderr]
--
19:21:36 DEBUG| [stderr] Traceback (most recent call last):
19:21:36 DEBUG| [stderr] File
"/home/azure/autotest/client/tests/ubuntu_boot/kernel_revocation_list.py", line
27, in test_revocations
19:21:36 DEBUG| [stderr] ["keyctl", "list", "%:.blacklist"],
universal_newlines=True
19:21:36 DEBUG| [stderr] File "/usr/lib/python3.4/subprocess.py", line 620,
in check_output
19:21:36 DEBUG| [stderr] raise CalledProcessError(retcode, process.args,
output=output)
19:21:36 DEBUG| [stderr] subprocess.CalledProcessError: Command '['keyctl',
'list', '%:.blacklist']' returned non-zero exit status 2
19:21:36 DEBUG| [stderr]
19:21:36 DEBUG| [stderr]
--
19:21:36 DEBUG| [stderr] Ran 1 test in 0.013s
19:21:36 DEBUG| [stderr]
19:21:36 DEBUG| [stderr] FAILED (errors=1)
19:21:36 ERROR| Exception escaping from test:
Traceback (most recent call last):
File "/home/azure/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/azure/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/azure/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/azure/autotest/client/shared/test.py", line 212, in _call_run_once
self.run_once(*args, **dargs)
File "/home/azure/autotest/client/tests/ubuntu_boot/ubuntu_boot.py", line 79,
in run_once
raise error.TestFail()
TestFail
-
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953340/+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 1966499] Re: Recent 5.13 kernel has broken KVM support
Hello,
this patch e90e51d5f01d ("KVM: VMX: clear vmx_x86_ops.sync_pir_to_irr if APICv
is disabled") has been applied to our master-next branch of Impish tree.
commit 1b611352fd6fd42a5a672f52f5f3035d48b3cd13
Author: Paolo Bonzini
Date: Tue Nov 30 07:36:41 2021 -0500
KVM: VMX: clear vmx_x86_ops.sync_pir_to_irr if APICv is disabled
BugLink: https://bugs.launchpad.net/bugs/1958287
[ Upstream commit e90e51d5f01d2baae5dcce280866bbb96816e978 ]
There is nothing to synchronize if APICv is disabled, since neither
other vCPUs nor assigned devices can set PIR.ON.
Signed-off-by: Paolo Bonzini
Signed-off-by: Sasha Levin
Signed-off-by: Kamal Mostafa
Signed-off-by: Stefan Bader
It should be included in 5.13.0-40.45 of SRU cycle 2022 03/21 (tracking bug
lp:1966701)
I would suggest you to give this proposed kernel a try.
Also,
can you provide us the step to reproduce this?
I can't reproduce this on an clean Impish bare-metal system running with
5.13.0-39-generic with our KVM smoke test (which utilize uvt-kvm to create the
KVM instance).
It would be nice to improve the test coverage with it.
Thanks!
--
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/1966499
Title:
Recent 5.13 kernel has broken KVM support
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Impish:
New
Bug description:
Upgrading to 5.13.0-37 or 5.13.0-39 immediately crashes my production servers
as they hit:
https://lore.kernel.org/all/f1ea22d3-cff8-406a-ad6a-cb8e0124a...@leemhuis.info/T/#md1f5c8c4aa01130a449a47f3e7559f06b0372f55
It looks like we need to get e90e51d5f01d included in those kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+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 1964796] Re: Fix unmatched ASMedia ASM2824 PCIe link training
Submitted that patch that is now in linus' tree to stable https://lore.kernel.org/stable/20220331115345.117662-1-dimitri.led...@canonical.com/T/#u NAK'ed previous path. Will submit to apply this new patch to our linux-riscv trees, ahead of inclusion in kernel.org's stable trees. ** Changed in: linux-riscv (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: linux-riscv (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1964796 Title: Fix unmatched ASMedia ASM2824 PCIe link training Status in linux-riscv package in Ubuntu: In Progress Bug description: https://lore.kernel.org/all/alpine.deb.2.21.2202010240190.58...@angie.orcam.me.uk/raw It has been discovered that Unmatched board ships ASMedia ASM2824 PCIe which frequently fails to complete link training and negotiate stable and fast speeds. To ensure PCIe devices on Unmatched board can operate with stable and predictable link speeds cherry-pick upstream submitted patch that resolves the issue. It is currently applied as a SAUCE patch, whilst the upstream inclusion review is ongoing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964796/+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 1967141] Re: [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core (openssl-ibmca)
I've noticed that v2.2.3 is obviously a bugfix-only release: ... 93a12d3 (tag: v2.2.3) Update to version 2.2.3 6563dd2 use correct libica for ibmca_mechaList_test e91e179 PKEY: Fix usage of ECX keys fae4490 (tag: v2.2.2) Update to version 2.2.2 ... and according to the FFe definition, bugfix-only updates might be acceptable, so I will follow that route. I've created such a package: openssl-ibmca (2.2.3-0ubuntu1) jammy; urgency=medium * New upstream release. LP: #1967141 * The difference between 2.2.2 and 2.2.3 includes just these two fixes: - "PKEY: Fix usage of ECX keys" - "use correct libica for ibmca_mechaList_test" Rather than adding these as quilt patches, raising the package to the bugfix-only version that incl. them is preferable. * For "PKEY: Fix usage of ECX keys" a backport of "Fix compilation for OpenSSL 3.0" was needed: d/p/e59cce5-Fix-compilation-for-OpenSSL-3.0.patch * For convenience reasons a generated sample config is now included in the package, but also the optional configuration generator Perl script 'ibmca-engine-opensslconfig'. It built fine locally (on s390x - it's an s390x-only package). In addition I've did a PPA build of this package which is available here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1967141 The build includes a run of the test suite: local build: Testsuite summary for openssl-ibmca 2.2.3 # TOTAL: 34 # PASS: 28 # SKIP: 6 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 PPA: Testsuite summary for openssl-ibmca 2.2.3 # TOTAL: 34 # PASS: 26 # SKIP: 8 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 (Two more tests are (auto-)skipped, because the builder does not have access to the s390x crypto hardware. (The other skipped tests are skipped by upstream, since they are known to cause issues on openssl 3 systems). On top I installed, tested ad verified the package on an s390x system: $ uname -a Linux s1lp15 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:53:58 UTC 2022 s390x s390x s390x GNU/Linux $ apt-cache policy openssl-ibmca openssl-ibmca: Installed: 2.2.3-0ubuntu1 Candidate: 2.2.3-0ubuntu1 Version table: *** 2.2.3-0ubuntu1 100 100 /var/lib/dpkg/status 2.2.2-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/universe s390x Packages And I can confirm that sshd does NOT core dump. -- 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/1967141 Title: [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core (openssl-ibmca) Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Summary === New IBM HW with Crypto Accelerator cards attached Kernel level: 5.14 Core dump when configuring the ibmca engine with libica = libica.so.4 in the openssl.cnf file in the engine section. The problem only occurs with OpenSSL 3.0 and is immediately reproducible. Details === HINT: To be able to receive core dump files at all it is needed to change the /etc/systemd/system.conf file entry DefaultLimitCORE=0:infinity to read DefaultLimitCORE=infinity:infinity On a system with ibmca engine configured system wide, when trying to use the libica.so.4 to support the ibmca engine the sshd daemon dumps core upon the first login attempt. # openssl engine -c (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support [RSA, DSA, DH] Debug Data == core dump file in the attachments. Contact Information = christian.r...@de.ibm.com ---uname output--- Linux system 5.14. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1.) Edit /etc/systemd/system.conf file to allow core dumps: Change the line DefaultLimitCORE=0:infinity to read DefaultLimitCORE=infinity:infinity 2.) run: systemctl daemon-reload systemctl restart systemd-coredump.socket 3.) Run the /usr/share/doc/openssl-ibmca/ibmca-engine-opensslconfig perl script 4.) Edit the /etc/pki/tls file near the end to contain the line to back the ibmca engine by the libica.so.4 library as outlined in the /usr/share/doc/openssl-ibmca/README.md file 5.) Run: openssl engine -c 6.) Keep the current session open for subsequently stepping back to the original openssl.cnf! 7.) Open up a new ssh session to the system under test
[Kernel-packages] [Bug 1964983] Re: IPU6 camera has no function on Andrews MLK
** Changed in: linux-oem-5.14 (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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1964983 Title: IPU6 camera has no function on Andrews MLK Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Confirmed Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Bug description: [SRU Justification] [Impact] New Andrews MLK equips yet another new I2C sensor and takes a few driver updates to function normally. [Fix] Upstream driver commit: https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e [Test Case] To verify by following steps: 1. disable secure boot 2. $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel 3. $ sudo add-apt-repository ppa:kchsieh/ipu6 4. $ sudo apt install linux-oem-5.14 version 5.14.0-9029-oem or newer 6. $ sudo apt install libipu6ep 7. $ sudo apt install libcamhal-ipu6ep-common 8. $ sudo apt install libcamhal-ipu6ep0 9. $ sudo apt install libgsticamerainterface-1.0-1 10. $ sudo apt install gstreamer1.0-icamera 11. $ sudo vim /etc/v4l2-relayd -FORMAT=YUY2 +FORMAT=NV12 12. $ sudo reboot [Where problems could occur] Intel IPU6 platform is still under development and is not capable of advanced power management features and may still suffer from stability issues. [Other Info] Nomination for 5.15 is necessary for oem-5.14 to hwe-5.15 migration and will depend on previous SRU proposal in bug 1955383 (https://lists.ubuntu.com/archives/kernel-team/2022-March/128922.html). Nomination for generic-5.17 and oem-5.17 is still under planning. == original bug description == The new platform uses yet another ov sensor OV02C10. Prerequisites: * kernel fix: https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e * ipu6-camera-bins: https://github.com/intel/ipu6-camera-bins/commit/7cc1dc2d9ab2b0766e034edf808d751bd25b42cc * ipu6-camera-hal: https://github.com/intel/ipu6-camera-hal/commit/b9b56de11de70b7c4520595176e4831bacf4a7fe * icamerasrc: https://github.com/intel/icamerasrc/commit/a35978264002acaad72bb9956238ccaef3743932 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964983/+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 1965496] Re: alsa: enable the cirrus-logic side-codec to make the speaker output sound
** Changed in: linux-oem-5.14 (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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965496 Title: alsa: enable the cirrus-logic side-codec to make the speaker output sound Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] We have a couple of lenovo latops models which have cirrus-logic side codec between realtek codec and speaker, it plays a role as amplifier, we need to enable this side-codec, otherwise the speaker can't output sound. [Fix] Backport codec patches and some i2c and acpi detection patches from mainline kernel and linux-next [Test] boot the patched kernel, run speaker test, both left and right channel could work well. [Where problems could occur] If it could introduce regression, it will be on soc wm_adsp codec drivers, since most of patch are adding new codec drivers, it will not touch existing codec drivers. If a machine with wm_adsp codec can't output sound or record sound, it means this SRU introduce the regression on wm_adsp driver, but this possibility is very low, since all patches are picked from mainline kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1965496/+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 1966010] Re: Fix audio on Zbook Studio G9
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966010 Title: Fix audio on Zbook Studio G9 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Cirrus Logic AMP still doesn't work on Zbook Studio G9. Moreoever, The audio mute LEDs stop working after the said SRU. [Fix] Correcly interpret the debounce time from ACPI to gpiolib, and apply the correct quirk for the audio mute LEDs. [Where problems could occur] It's possible that some hardwares rely on the "wrong" debounce time to work, however the fix is to increase the debounce time, so it's more forgiving than decreasing. The LED fix is only applied to one system, so it's specifi and won't cause too much trouble. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966010/+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 1909005] Re: Ubuntu does not resume (wake up) from suspend
This basic usability issue has been outstanding for over year. Not a word from anyone. Has it even been accepted as a problem? Do you not care? What? I'd honestly prefer to be told to piss off and stop bothering you than just be ignored. At least we'd know where we stand. -- 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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1967257] Re: Ubuntu Server lose connection when download >1G large file
** Tags added: austin oem-priority originate-from-1957729 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1967257 Title: Ubuntu Server lose connection when download >1G large file Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: New Bug description: [Impact] WW Field test reported Foxconn T99W175 5G module lose connection issue when download > 1G large file. Similar issue can also be reproduced on Quectel EM160 4G test. [Where problems could occur] This issue will randomly occur when device download speed reach to a certain value (60Mbps ~ 100Mbps) in Linux host. And once the issue happened, need to reboot system to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967257/+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 1967257] [NEW] Ubuntu Server lose connection when download >1G large file
Public bug reported: [Impact] WW Field test reported Foxconn T99W175 5G module lose connection issue when download > 1G large file. Similar issue can also be reproduced on Quectel EM160 4G test. [Where problems could occur] This issue will randomly occur when device download speed reach to a certain value (60Mbps ~ 100Mbps) in Linux host. And once the issue happened, need to reboot system to recover. ** Affects: linux-intel-5.13 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1967257 Title: Ubuntu Server lose connection when download >1G large file Status in linux-intel-5.13 package in Ubuntu: New Bug description: [Impact] WW Field test reported Foxconn T99W175 5G module lose connection issue when download > 1G large file. Similar issue can also be reproduced on Quectel EM160 4G test. [Where problems could occur] This issue will randomly occur when device download speed reach to a certain value (60Mbps ~ 100Mbps) in Linux host. And once the issue happened, need to reboot system to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-5.13/+bug/1967257/+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 1966499] Re: Recent 5.13 kernel has broken KVM support
** Also affects: linux (Ubuntu Impish) 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/1966499 Title: Recent 5.13 kernel has broken KVM support Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: New Bug description: Upgrading to 5.13.0-37 or 5.13.0-39 immediately crashes my production servers as they hit: https://lore.kernel.org/all/f1ea22d3-cff8-406a-ad6a-cb8e0124a...@leemhuis.info/T/#md1f5c8c4aa01130a449a47f3e7559f06b0372f55 It looks like we need to get e90e51d5f01d included in those kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+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 1966671] Re: package linux-firmware 1.187.26 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal
*** This bug is a duplicate of bug 1965307 *** https://bugs.launchpad.net/bugs/1965307 Opening multiple tickets for the same problem is not going to speed things up. -- 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/1966671 Title: package linux-firmware 1.187.26 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in linux-firmware package in Ubuntu: New Bug description: Remove this package is not possible. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.26 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: sirenux1758 F pulseaudio /dev/snd/controlC2: sirenux1758 F pulseaudio /dev/snd/controlC1: sirenux1758 F pulseaudio /dev/snd/controlC0: sirenux1758 F pulseaudio CasperMD5CheckResult: skip Date: Mon Mar 28 12:37:44 2022 Dependencies: DuplicateSignature: package:linux-firmware:1.187.26 Removing linux-image-generic-hwe-20.04 (5.13.0.30.33~20.04.17) ... dpkg: error processing package linux-firmware (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2022-01-19 (67 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp27s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7B07 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=c0e47fc1-d36a-4d49-a7fb-c934c673b142 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. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.26 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M PRO-VH PLUS (MS-7B07) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.C0:bd11/06/2018:br5.13:svnMicro-StarInternationalCo.,Ltd:pnMS-7B07:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnA320MPRO-VHPLUS(MS-7B07):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B07 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 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-firmware/+bug/1966671/+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 1966671] Re: package linux-firmware 1.187.26 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal
*** This bug is a duplicate of bug 1965307 *** https://bugs.launchpad.net/bugs/1965307 Please see my comment/request in bug 1965307. ** This bug has been marked a duplicate of bug 1965307 package linux-firmware 1.187.26 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal -- 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/1966671 Title: package linux-firmware 1.187.26 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in linux-firmware package in Ubuntu: New Bug description: Remove this package is not possible. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.26 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: sirenux1758 F pulseaudio /dev/snd/controlC2: sirenux1758 F pulseaudio /dev/snd/controlC1: sirenux1758 F pulseaudio /dev/snd/controlC0: sirenux1758 F pulseaudio CasperMD5CheckResult: skip Date: Mon Mar 28 12:37:44 2022 Dependencies: DuplicateSignature: package:linux-firmware:1.187.26 Removing linux-image-generic-hwe-20.04 (5.13.0.30.33~20.04.17) ... dpkg: error processing package linux-firmware (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2022-01-19 (67 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp27s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7B07 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=c0e47fc1-d36a-4d49-a7fb-c934c673b142 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. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.26 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M PRO-VH PLUS (MS-7B07) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.C0:bd11/06/2018:br5.13:svnMicro-StarInternationalCo.,Ltd:pnMS-7B07:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnA320MPRO-VHPLUS(MS-7B07):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B07 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 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-firmware/+bug/1966671/+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 1966935] Re: USB audio playback scratchy after kernel 5.13.0-30
*** This bug is a duplicate of bug 1966066 *** https://bugs.launchpad.net/bugs/1966066 ** This bug has been marked a duplicate of bug 1966066 audio from external sound card is distorted -- 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/1966935 Title: USB audio playback scratchy after kernel 5.13.0-30 Status in linux package in Ubuntu: Incomplete Bug description: Audio playback through a USB device (Focusrite Scarlett) is scratchy or overdriven and clearly slowed. I noticed this happened sometime after kernel 5.13.0-30-lowlatency (5.13.0-32 is certainly impacted). Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966935/+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 1956413] Re: Intel EHL: Two of the on-board ethernet ports don't work
** Changed in: linux-intel-5.13 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956413 Title: Intel EHL: Two of the on-board ethernet ports don't work Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Fix Released Status in linux-intel-5.13 source package in Focal: Fix Released Bug description: == Impact == Only one of the three on-board ethernet ports works. The other two can't get IP addresses. == Fix == commit 884d2b845477cd0a18302444dc20fe2d9a01743e Author: David Wu Date: Mon Dec 13 19:15:15 2021 +0800 net: stmmac: Add GFP_DMA32 for rx buffers if no 64 capability Use page_pool_alloc_pages instead of page_pool_dev_alloc_pages, which can give the gfp parameter, in the case of not supporting 64-bit width, using 32-bit address memory can reduce a copy from swiotlb. Signed-off-by: David Wu Signed-off-by: David S. Miller == Risk of Regression == Low. The commit changes gfp parameter only when there's no 64-bit capability, and it is already in mainline. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956413/+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 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
> Having the same problem, running on a Dell XPS 13 9310. https://www.dell.com/community/XPS/XPS-13-9310-Ubuntu-deep-sleep- missing/m-p/8056343/highlight/true#M91204 says that deep sleep isn't supported on the 9310 so what you describe is actually expected supposedly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+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 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
Hm. That commit has too many dependencies to cherry-pick (or even cherry-pick a small series) without significant conflicts. It might be still possible to *understand* the patch and write an equivalent for 5.15. -- 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/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash 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.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1966147] Re: 5.13.0-37.42 terrible sound via usb
*** This bug is a duplicate of bug 1966066 *** https://bugs.launchpad.net/bugs/1966066 Thank **you** -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966147 Title: 5.13.0-37.42 terrible sound via usb Status in linux package in Ubuntu: Incomplete Bug description: updated yesterday to kernel 5.13.0-37.42 and sound from usb is awfully distorted, while from bluetooth and hdmi is unaltered. reverted to 5.13.0-35.40 via grub and sound via usb is back to normal. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: vinz 2684 F pulseaudio /dev/snd/controlC2: vinz 2684 F pulseaudio /dev/snd/controlC1: vinz 2684 F pulseaudio /dev/snd/controlC0: vinz 2684 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: Unity DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-10-24 (518 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=fcdf975b-fa37-4978-8a4b-e452f2f74512 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: Upgraded to impish on 2022-01-27 (58 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F30 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA 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: dmi:bvnAmericanMegatrendsInc.:bvrF30:bd09/15/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966147/+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 1966066] Re: audio from external sound card is distorted
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1966066
Title:
audio from external sound card is distorted
Status in linux package in Ubuntu:
Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-signed-hwe-5.13 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
Invalid
Bug description:
[Impact]
Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
next packet size") landed in 5.13.0-35 introduced regression to USB
audio device.
It's because this patch introduced the available frame size check, but
the conversion forgot to initialize the temporary variable properly.
A workaround is to modify /etc/pulse/daemon.conf, set the
default-sample-rate to 48000, uncomment it by removing the semicolon
at the beginning of the line. And restart pulseaudio with:
systemctl --user restart pulseaudio.service
[Fix]
* 23939115 ALSA: usb-audio: Fix packet size calculation regression
This patch can be cherry-picked into Impish kernel, and it's already in
the master-next branch of Jammy tree.
[Test]
Test kernels built with 5.13.0-37 + this patch, can be found in:
* Focal-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
* Impish-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/
Both kernels were tested by affected users and they're working as
expected.
[Where problems could occur]
If this patch is incorrect, it might affect USB audio devices.
[Original Bug Report]
The sound card is a Focusrite Scarlett 2i2.
The sound is distorted everywhere.
Sound via HDMI works.
Seen others having the same problem:
(Edit because of previously wrong link here)
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card
ubuntu release: Ubuntu 20.04.4 LTS
package name involved in bug: linux-image-5.13.0-37-generic
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 23 12:56:02 2022
InstallationDate: Installed on 2020-12-18 (459 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066/+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 1966969] Re: linux-aws: Xen: Issues with detaching volume
** Also affects: linux-aws (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux-aws (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Impish) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-aws (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1966969 Title: linux-aws: Xen: Issues with detaching volume Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Impish: In Progress Bug description: SRU Justification [Impact] We are observing issue with the secondary volume stuck in detaching. This is observed with the latest Canonical, Ubuntu EKS Node OS (k8s_1.19), 20.04 LTS, amd64 focal image build on 2022-03-08 and Xen instance type( for eg : m4, t2 instance type ) AMI in eu-west-1 : ami-0f4ffbcba23a6c434 AMI in us-east-1 : ami-021feb4aa3b3c59c3 When terminating an instance with a stuck volume the shutdown process is interrupted by a xen task hanging: [ 847.895334] INFO: task xenwatch:188 blocked for more than 483 seconds. [ 847.901573] Not tainted 5.13.0-1017-aws #19~20.04.1-Ubuntu [ 847.907144] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 847.914462] task:xenwatch state:D stack: 0 pid: 188 ppid: 2 flags:0x4000 [ 847.914467] Call Trace: [ 847.914469] [ 847.914472] __schedule+0x2ee/0x900 [ 847.914478] schedule+0x4f/0xc0 [ 847.914479] schedule_preempt_disabled+0xe/0x10 [ 847.914482] __mutex_lock.isra.0+0x183/0x4d0 [ 847.914486] __mutex_lock_slowpath+0x13/0x20 [ 847.914487] mutex_lock+0x32/0x40 [ 847.914489] del_gendisk+0x90/0x200 [ 847.914493] xlvbd_release_gendisk+0x72/0xc0 [ 847.914499] blkback_changed+0x101/0x210 [ 847.914502] xenbus_otherend_changed+0x8f/0x130 [ 847.914507] backend_changed+0x13/0x20 [ 847.914510] xenwatch_thread+0xa6/0x180 [ 847.914513] ? wait_woken+0x80/0x80 [ 847.914517] ? test_reply.isra.0+0x40/0x40 [ 847.914520] kthread+0x12b/0x150 [ 847.914523] ? set_kthread_struct+0x40/0x40 [ 847.914525] ret_from_fork+0x22/0x30 [ 847.914531] this looks like it's waiting on a xen block device to be released. Following steps used to reproduce the issue: * Created a m4,t2(xen) instance with the latest ami for latest Canonical, Ubuntu EKS Node OS (k8s_1.19), 20.04 LTS, amd64 * Created a filesystem on volume * Mounted volume through OS * Unmounted volume in OS * Detached volume from AWS console * Volume gets stuck. We at the internal team observed this commit upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05d69d950d9d84218fc9beafd02dea1f6a70e09e [...] and a del_gendisk from the block device release method, which will deadlock. It has a Fixes: tag referring to a commit from 5.13 so this could be the root-cause. While testing, we observed this commit is fixing the issue. [Test Plan] Amazon tested [Where things could go wrong] Detaching volumes could fail in new and bizarre ways [Other Info] SF: #00331175 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1966969/+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 1967223] [NEW] nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: Firefox window crashes and any newly open window clones infinitely ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-35-generic Date: Sun Mar 13 11:55:57 2022 DuplicateSignature: dkms:nvidia-dkms-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-03-24 (371 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1967223 Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: Firefox window crashes and any newly open window clones infinitely ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-35-generic Date: Sun Mar 13 11:55:57 2022 DuplicateSignature: dkms:nvidia-dkms-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-03-24 (371 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build 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-460/+bug/1967223/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
** Tags added: originate-from-1966018 stella ** Tags added: originate-from-1966011 -- 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 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.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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 1966870] Re: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs
FYI for a different test I upgraded the system to Impish and on the 5.13.0-39-generic there neither of the two kernel bugs happens. -- 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/1966870 Title: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs Status in linux package in Ubuntu: Confirmed Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs
