[Kernel-packages] [Bug 2001914] [NEW] The gpu hangs and is not possible to work with GPU-envioronment
You have been subscribed to a public bug: When I open the terminal or just browsing, gnom sometimes freezes for a second, but sometimes restart the machine is necessary. The log is: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm]i915 :00:02.0: [drm] GPU HANG: ecode 12:0: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC SLPC: enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: last_user_time (2748010) is greater than comparison timestamp (2743419). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 0xc0003c appears to be one of the offending windows with a timestamp of 2748010. Working around... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Jan 5 12:25:49 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-02 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy wayland-session -- The gpu hangs and is not possible to work with GPU-envioronment https://bugs.launchpad.net/bugs/2001914 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998950] Re: GPU hang on Alder Lake laptop
Yeah I can't see this bug anymore on kinetic with kernel 5.19.0-29-generic. So this is closed and bug 2001914 separated. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** No longer affects: mesa (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/1998950 Title: GPU hang on Alder Lake laptop Status in Linux: New Status in linux package in Ubuntu: Fix Released Bug description: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1998950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001914] Re: The gpu hangs and is not possible to work with GPU-envioronment
Does the bug still happen with the latest kernel update 5.15.0-58.64 ? Try updating: sudo apt update sudo apt full-upgrade and then reboot. ** This bug is no longer a duplicate of bug 1998950 GPU hang on Alder Lake laptop ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2001914 Title: The gpu hangs and is not possible to work with GPU-envioronment Status in linux package in Ubuntu: Incomplete Bug description: When I open the terminal or just browsing, gnom sometimes freezes for a second, but sometimes restart the machine is necessary. The log is: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm]i915 :00:02.0: [drm] GPU HANG: ecode 12:0: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC SLPC: enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: last_user_time (2748010) is greater than comparison timestamp (2743419). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 0xc0003c appears to be one of the offending windows with a timestamp of 2748010. Working around... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Jan 5 12:25:49 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-02 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003348] Comment bridged from LTC Bugzilla
--- Comment From sven.schne...@ibm.com 2023-01-20 03:10 EDT--- A few things to check: - is the dasd parameter given in the command line - is the DASD enabled and detected during boot (i guess not, because of errno == -6) Can you post the full dmesg here in bugzilla? I'm not really keen to have yet another account just to look at the linked pastebin. -- 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/2003348 Title: Kernel 6.2 does not boot on s390x Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The kernel team created a first kernel 6.2 for testing purposes. linux-unstable 6.2.0-4.4 ia available in ppa:canonical-kernel- team/bootstrap However this kernel does not boot on s390x and crashes: https://pastebin.canonical.com/p/qXj4g4bgGH/ or: ... Ý0.408281¨ md: Waiting for all devices to be available before autodetect Ý0.408283¨ md: If you don't use raid, use raid=noautodetect Ý0.408285¨ md: Autodetecting RAID arrays. Ý0.408287¨ md: autorun ... Ý0.408288¨ md: ... autorun DONE. Ý0.408405¨ /dev/root: Can't open blockdev Ý0.408409¨ VFS: Cannot open root device "disk/by-path/ccw-0.0.0400-part1" or unknown-block(0,0): error -6 Ý0.408412¨ Please append a correct "root=" boot option; here are the availa le partitions: Ý0.408415¨ Kernel panic - not syncing: VFS: Unable to mount root fs on unkno wn-block(0,0) Ý0.408418¨ CPU: 2 PID: 1 Comm: swapper/0 Not tainted 6.2.0-4-generic #4-Ubun tu Ý0.408421¨ Hardware name: IBM 2964 N63 400 (z/VM 6.4.0) Ý0.408423¨ Call Trace: Ý0.408425¨ ݨ dump_stack_lvl+0x62/0x90 Ý0.408433¨ Ý ¨ panic+0x174/0x360 Ý0.408438¨ Ý ¨ mount_block_root+0x16e/0x210 Ý0.408444¨ Ý ¨ prepare_namespace+0x168/0x1e0 Ý0.408448¨ Ý ¨ kernel_init_freeable+0x1de/0x1f0 Ý0.408451¨ Ý ¨ kernel_init+0x2e/0x1a0 Ý0.408455¨ Ý ¨ __ret_from_fork+0x40/0x60 Ý0.408459¨ Ý ¨ ret_from_fork+0xa/0x40 02: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 B50E215E or: [8.693187] /dev/root: Can't open blockdev [8.693191] VFS: Cannot open root device "disk/by-path/ccw-0.0.260b-part1" or unknown-block(0,0): error -6 [8.693194] Please append a correct "root=" boot option; here are the available partitions: [8.693198] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Initially we thought it might be related to LVM/DM, but it's not, since it happens also on single DASD disk installation without LVM and also on NVMe disks. It also happens on z15 and on z13. Messages indicate that either the "root=" argument is wrong or not there. I can check /proc/cmdline since the system ends up in a crash for me. However, installing and using 6.1.0-9 works fine. _ Steps to re-create: - Install Ubuntu lunar using: https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/lunar-live-server-s390x.iso or: https://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/lunar-live-server-s390x.iso (- get it updated: sudo apt -y -q update && sudo apt -y -q full-upgrade && sudo apt autoremove --purge ) - sudo add-apt-repository --yes ppa:canonical-kernel-team/bootstrap - $ sudo apt update - $ sudo apt install --yes linux-image-6.2.0-4-generic linux-modules-6.2.0-4-generic linux-modules-extra-6.2.0-4-generic linux-headers-6.2.0-4-generic - $ sudo reboot - open the console (e.g. Operating Systems Messages) and monitor the boot/IPL process, it's fail like above Do the same with kernel 6.1: sudo apt install --yes linux-image-6.1.0-9-generic linux-modules-6.1.0-9-generic linux-modules-extra-6.1.0-9-generic linux-headers-6.1.0-9-generic and the system reboots successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001914] Re: The gpu hangs and is not possible to work with GPU-envioronment
Yes, it does! Sometimes I have to restart the laptop, cause I don't have other terminal to restart the GPU. And the kernel is the same 5.15.0-58.64. Sorry, but for now and for me the problem isn't "Closed". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2001914 Title: The gpu hangs and is not possible to work with GPU-envioronment Status in linux package in Ubuntu: Incomplete Bug description: When I open the terminal or just browsing, gnom sometimes freezes for a second, but sometimes restart the machine is necessary. The log is: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm]i915 :00:02.0: [drm] GPU HANG: ecode 12:0: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC SLPC: enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: last_user_time (2748010) is greater than comparison timestamp (2743419). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 0xc0003c appears to be one of the offending windows with a timestamp of 2748010. Working around... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Jan 5 12:25:49 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-02 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001914] Re: The gpu hangs and is not possible to work with GPU-envioronment
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2001914 Title: The gpu hangs and is not possible to work with GPU-envioronment Status in linux package in Ubuntu: Confirmed Bug description: When I open the terminal or just browsing, gnom sometimes freezes for a second, but sometimes restart the machine is necessary. The log is: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm]i915 :00:02.0: [drm] GPU HANG: ecode 12:0: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC SLPC: enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: last_user_time (2748010) is greater than comparison timestamp (2743419). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 0xc0003c appears to be one of the offending windows with a timestamp of 2748010. Working around... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Jan 5 12:25:49 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-02 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003524] [NEW] amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks
Public bug reported: [Impact] >From "Mario Limonciello mario.limonciello at amd.com" https://lists.ubuntu.com/archives/kernel-team/2023-January/136434.html. There is a problem in amdgpu that if not all of IP blocks are supported or not all of the firmware is present then the framebuffer is destroyed and the screen freezes. In more recent kernels the amdgpu driver loads for all PCI VGA class AMD devices. This effectively means that unless you have all the pieces you need to support a GPU then the installer freezes unless you do nomodeset. This problem is to be fully fixed in kernel 6.3 with a ~47 patch series that is currently in drm-next. This does two basic things: 1) If the IP blocks isn't supported, don't destroy the framebuffer. 2) If firmware for any IP blocks aren't present, don't destroy the framebuffer. The whole patch series still needs more time to back in drm-next, but the most important part of the series is the first patch which accomplishes "1". This patch went out to stable 6.1.y as well: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/amd?h=linux-6.1.y&id=dcfeba477b3e3df526e0f543b58fa71c045dff8b My reasoning is that it will ensure that if someone picks up a newer GPU such as Ryzen 7000 desktop or RDNA3 based they can at least install Ubuntu without needing to use "Safe Graphics Mode" at the installer. Sure; they won't have hardware acceleration without the rest of the kernel and framework, but that's a separate problem to a basic display. [Fix] Cherry-pick/backport commit 1923bc5a56daeeabd7e9093bad2febcd6af2416a "drm/amd: Delay removal of the firmware framebuffer" to Ubuntu Kinetic 5.19 kernel. [Test case] Boot kernel in a system with one of the amdgpu affected adapters. [Where problems can occur] The aforementioned commit could introduce other regressions on the support for AMD GPUs. ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: In Progress ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) 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/2003524 Title: amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks Status in linux package in Ubuntu: In Progress Status in linux source package in Kinetic: In Progress Status in linux source package in Lunar: In Progress Bug description: [Impact] From "Mario Limonciello mario.limonciello at amd.com" https://lists.ubuntu.com/archives/kernel-team/2023-January/136434.html. There is a problem in amdgpu that if not all of IP blocks are supported or not all of the firmware is present then the framebuffer is destroyed and the screen freezes. In more recent kernels the amdgpu driver loads for all PCI VGA class AMD devices. This effectively means that unless you have all the pieces you need to support a GPU then the installer freezes unless you do nomodeset. This problem is to be fully fixed in kernel 6.3 with a ~47 patch series that is currently in drm-next. This does two basic things: 1) If the IP blocks isn't supported, don't destroy the framebuffer. 2) If firmware for any IP blocks aren't present, don't destroy the framebuffer. The whole patch series still needs more time to back in drm-next, but the most important part of the series is the first patch which accomplishes "1". This patch went out to stable 6.1.y as well: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/amd?h=linux-6.1.y&id=dcfeba477b3e3df526e0f543b58fa71c045dff8b My reasoning is that it will ensure that if someone picks up a newer GPU such as Ryzen 7000 desktop or RDNA3 based they can at least install Ubuntu without needing to use "Safe Graphics Mode" at the installer. Sure; they won't have hardware acceleration without the rest of the kernel and framework, but that's a separate problem to a basic display. [Fix] Cherry-pick/backport commit 1923bc5a56daeeabd7e9093bad2febcd6af2416a "drm/amd: Delay removal of the firmware framebuffer" to Ubuntu Kinetic 5.19 kernel. [Test case] Boot kernel in a system with one of the amdgpu affected adapters. [Where problems can occur] The aforementioned commit could introduce other regressions on the support for AMD GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003524/+subscriptions -- Mailing list: https://launchpad.ne
[Kernel-packages] [Bug 1991365] Re: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1991365 Title: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] turbostat doesn't show the correct fields for RPL-S. This's a wrong column. usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,CPU%LPI,SYS%LPI [Fix] Add RPL-S support in turbostat [Test Case] 1. run "turbostat --list" 2. check the output, this is a correct column. usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,SMI,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CPU%c1,CPU%c6,CPU%c7,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,Totl%C0,Any%C0,GFX%C0,CPUGFX%,Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI,PkgWatt,CorWatt,GFXWatt,RAMWatt,PKG_%,RAM_% [Where problems could occur] Low, just add a devcie id to support RPL-S. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987265] Re: drm/i915, turbostat: Support for ADL-N, RPL-P
most of these were already on 5.19, some applied via 1991365 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Kinetic) Status: New => Triaged ** Changed in: linux (Ubuntu Kinetic) Status: Triaged => 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/1987265 Title: drm/i915, turbostat: Support for ADL-N, RPL-P Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] We're missing support for ADL-N/RPL-P and some RPL-S pci-id's. [Test case] Boot a system with these pci-id's, see that graphics now work [What could go wrong] These are new pci-id's, no change for current platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987265/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968016] Re: Use kernel-testing repo from launchpad for ADT tests
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1968016 Title: Use kernel-testing repo from launchpad for ADT tests Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-oem-5.14 source package in Trusty: Invalid Status in linux-oem-5.17 source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-oem-5.14 source package in Xenial: Invalid Status in linux-oem-5.17 source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux-oem-5.17 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: New Status in linux-oem-5.17 source package in Kinetic: New Bug description: In ADT tests, we are still using the kernel-testing repo from kernel.ubuntu.com, it should be migrated to launchpad instead to align with our other testing repos. For autotest-client-tests repo change, it will needs to be handled in the kernel-testing repo directly, see bug 1968257. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003524] Re: amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks
** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => High -- 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/2003524 Title: amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: [Impact] From "Mario Limonciello mario.limonciello at amd.com" https://lists.ubuntu.com/archives/kernel-team/2023-January/136434.html. There is a problem in amdgpu that if not all of IP blocks are supported or not all of the firmware is present then the framebuffer is destroyed and the screen freezes. In more recent kernels the amdgpu driver loads for all PCI VGA class AMD devices. This effectively means that unless you have all the pieces you need to support a GPU then the installer freezes unless you do nomodeset. This problem is to be fully fixed in kernel 6.3 with a ~47 patch series that is currently in drm-next. This does two basic things: 1) If the IP blocks isn't supported, don't destroy the framebuffer. 2) If firmware for any IP blocks aren't present, don't destroy the framebuffer. The whole patch series still needs more time to back in drm-next, but the most important part of the series is the first patch which accomplishes "1". This patch went out to stable 6.1.y as well: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/amd?h=linux-6.1.y&id=dcfeba477b3e3df526e0f543b58fa71c045dff8b My reasoning is that it will ensure that if someone picks up a newer GPU such as Ryzen 7000 desktop or RDNA3 based they can at least install Ubuntu without needing to use "Safe Graphics Mode" at the installer. Sure; they won't have hardware acceleration without the rest of the kernel and framework, but that's a separate problem to a basic display. [Fix] Cherry-pick/backport commit 1923bc5a56daeeabd7e9093bad2febcd6af2416a "drm/amd: Delay removal of the firmware framebuffer" to Ubuntu Kinetic 5.19 kernel. [Test case] Boot kernel in a system with one of the amdgpu affected adapters. [Where problems can occur] The aforementioned commit could introduce other regressions on the support for AMD GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux (Ubuntu Kinetic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002812 Title: Revoke & rotate to new signing key Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: [ Impact ] * Revoke & rotate to new signing key * Update revocations, which match the next Ubuntu shim 15.7 revocations. Specifically - revoke certs that were previously protected with by-hash revocations, revoke lost/unused certificates. * Start using advantage2021v1 and ubuntu2022v1 signing keys. * This is a routine key rotation. [ Test Plan ] * Check that old shim/grub boot this kernel * Check that the upcomming future shim/grub can boot this kernel * Check that these kernels can do signed kexec into itself [ Where problems could occur ] * Kernels with this patch applied should be signed using ubuntu/4 pro/3 core/2 signing streams. [ Other Info ] * TPM PCR values and measurements will change when changing the signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2000110 Title: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] AMD provides a list of commits to fix this issue 1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a 2. drm/amdgpu: Don't enable LTR if not supported https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6 3. Patch series: fix PCI AER issues drm/amdgpu: make sure to init common IP before gmc https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6 drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89 drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06 4. Disable amdgpu runpm, will have a update later. https://patchwork.freedesktop.org/patch/507366/ [Test] Verified on the machine with AMD graphic card, and confirmed the issue is gone. [Where problems could occur] The main idea is to disable BACO on those cards, the fix is quite straightforward with 2 Fixes commits, have impact on limited cards. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999836] Re: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500]
** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1999836 Title: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] SUT can't displayed after resume from WB/CB with dGFX installed. Recovery: SUT can display when the DP cable unplug and plug . [Fix] Use quirk to block the affected SKUes. [Test Case] 1.Install Ubuntu 22.04 on SUT with dGFX card. 2.Connect the DP cable to the dGFX port. 3.SUT do power off/restart. 4.SUT can display. [Where problems could occur] Add SKU's id to a quirk table, the impact would be small. [Other Info] * For the pure Jammy, Confronted the error of compilation. 1. Need 8e794421bc98) drm/amd/display: Fork thread to offload work ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1449:38: error: implicit declaration of function 'hpd_rx_irq_create_ workqueue'; did you mean 'hdcp_create_workqueue'? [-Werror=implicit-function-declaration] 18848 1449 | adev->dm.hpd_rx_offload_wq = hpd_rx_irq_create_workqueue(adev->dm.dc); 18849 | ^~~ 18850 | hdcp_create_workqueue ~~~ 2. Need 3ce51649cdf2) drm/amdgpu/display: add quirk handling for stutter ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1505:13: error: implicit declaration of function 'dm_should_disable_ stutter' [-Werror=implicit-function-declaration] 18838 1505 | if (dm_should_disable_stutter(adev->pdev)) ~~~ * hpd_disconnect_quirk_table is placed to the different location on J/OEM-5.17 and on K/OEM-6.0, so can't use a single patch for all. * Result from CBD ~~~ Jammy, remote: *** kernel-cbd * remote: * Queueing builds (your 'j_gen_nxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-820f542767e6-ESq2 remote: * 192/672 cores busy (2/7 hosts), 0 builds queued remote: 2022-12-15 17:09:15 kobako-jammy-820f542767e6-ESq2/amd64/BUILD-OK remote: 2022-12-15 17:11:13 kobako-jammy-820f542767e6-ESq2/arm64/BUILD-OK remote: 2022-12-15 17:07:30 kobako-jammy-820f542767e6-ESq2/armhf/BUILD-OK remote: 2022-12-15 17:10:17 kobako-jammy-820f542767e6-ESq2/ppc64el/BUILD-OK remote: 2022-12-15 17:04:55 kobako-jammy-820f542767e6-ESq2/s390x/BUILD-OK remote: To 54.69.112.110:jammy.git ~~~ Kinetic remote: *** kernel-cbd * remote: * Queueing builds (your 'k_gen_nxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-kinetic-857358673609-X4Nz remote: * 0/672 cores busy (0/7 hosts), 0 builds queued remote: 2022-12-15 17:41:37 kobako-kinetic-857358673609-X4Nz/amd64/BUILD-OK remote: 2022-12-15 17:42:13 kobako-kinetic-857358673609-X4Nz/arm64/BUILD-OK remote: 2022-12-15 17:35:54 kobako-kinetic-857358673609-X4Nz/armhf/BUILD-OK remote: 2022-12-15 17:40:54 kobako-kinetic-857358673609-X4Nz/ppc64el/BUILD-OK remote: 2022-12-15 17:34:47 kobako-kinetic-857358673609-X4Nz/s390x/BUILD-OK remote: To 54.69.112.110:kinetic.git ~~~ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1999836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998419] Re: Gnome doesn't run smooth when performing normal usage with RPL-P CPU
** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998419 Title: Gnome doesn't run smooth when performing normal usage with RPL-P CPU Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] Gnome desktop doesn't run smooth when performing normal usage, the cursor usually stops working and stuck, and then becomes back to normal. [Fix] Can't reproduce this issue with drm-tip kernel, so found below commit after bisected dc73ac63e63a drm/i915/rpl-p: Add stepping info [Test] Verified on the RPL-P machine and the cursor/window move smoothly. [Where problems could occur] Adding info for new RPL-P chipset should be pretty safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)
included in 6.1 ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1996048 Title: Screen freeze after resuming from suspend (nvme0: I/O timeout) Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ The patch is not finalized, so submit SRU to OEM kernels only, and will submit to other series kernels once the patch is accepted by upstream. [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993561] Re: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1993561 Title: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Incomplete Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] The Screen is shaking connected monitor to Onboard HDMI port. [Fix] The interlaced mode is not supported for Intel Gen 12 onwards. Disable interlaced mode for DP&HDMI on Display >= 12. Due to schedule, SRU for OEM kernels first. After these patches are merged to mainline/drmtip kernel, will SRU for generic kernels. [Test Case] 1.Connected two external Monitor to the onboard HDMI/DP port . 2.Boot OS. 2.set mirror mode. (onboard HDMI / onboard DP) 3.check if screen shakes. [Where problems could occur] Low, Remove interlace support for Display >= 12 so it wouldn't cause a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990161] Re: Fix RPL-S support on powercap/intel_rapl
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1990161 Title: Fix RPL-S support on powercap/intel_rapl Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] proc_thermal driver is not loaded [Fix] Add RPL-S id on device id table of powercap/intel_rapl. [Test Case] 1. sudo checkbox-cli run com.canonical.certification::miscellanea/proc_thermal [Where problems could occur] Low, only add RPL-S id on powercap/intel_rap but may lack of RPL-S features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002523] Re: problem to upgrade linux-firmware package
ignore the problem, was caused from a problem on my pc ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- 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/2002523 Title: problem to upgrade linux-firmware package Status in linux-firmware package in Ubuntu: Invalid Bug description: I am running Ubuntu 22.04 on laptop. from some weeks the upgrade process fail with the following output: Unpacking linux-firmware (20220329.git681281e4-0ubuntu3.9) over (20220329.git681281e4-0ubuntu3.7) ... dpkg: error processing archive /tmp/apt-dpkg-install-dN3Fro/7-linux-firmware_20220329.git681281e4-0ubuntu3.9_a ll.deb (--unpack): unable to open '/lib/firmware/ath11k/IPQ6018/hw1.0/m3_fw.mdt.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Gen erating /boot/initrd.img-5.15.0-57-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. update-initramfs: Generating /boot/initrd.img-5.15.0-56-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Errors were encountered while processing: /tmp/apt-dpkg-install-dN3Fro/7-linux-firmware_20220329.git681281e4-0ubuntu3.9_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I have made some check and i have found that, on my sistem, the file lib/firmware/ath11k/IPQ6018/hw1.0/m3_fw.mdt can not be extracted from the package linux-firmware_20220329.git681281e4-0ubuntu3.9_all.deb either manually Regards --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fgaglianello 2155 F pulseaudio /dev/snd/pcmC1D0p: fgaglianello 2155 F...m pulseaudio /dev/snd/controlC0: fgaglianello 2155 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-04 (99 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer TravelMate P258-M Package: linux-firmware 20220329.git681281e4-0ubuntu3.7 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/04/2016 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA50_SL dmi.board.vendor: Acer dmi.board.version: V1.14 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd03/04/2016:br0.0:efr2.70:svnAcer:pnTravelMateP258-M:pvrV1.14:rvnAcer:rnBA50_SL:rvrV1.14:cvnChassisManufacturer:ct10:cvrChassisVersion:skuTravelMateP258-M_1034_1.14: dmi.product.family: SKL dmi.product.name: TravelMate P258-M dmi.product.sku: TravelMate P258-M_1034_1.14 dmi.product.version: V1.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2002523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002779] Re: Kernels 5.15.0-57-generic and 5.15.0-58-generic kernel panic
** Description changed: I have a GPU workstation with AMD Ryzen™ Threadripper 2950X Processor, - ASUS Zenith Extreme, and four Nvidia GeForce RTX 2080Ti GPUs. My OS is - Ubuntu 22.04.1. I tried updating the by sudo apt update and upgrade. - Kernels 5.15.0-57-generic and 5.15.0-58-generic both have kernel panic. - The only option was to switch to a different kernel i.e., - 5.15.0-56-generic under Advanced Options while booting. + ASUS Zenith Extreme, and four Nvidia GeForce RTX 2080Ti GPUs (Nvidia + driver: 525). My OS is Ubuntu 22.04.1. I tried updating the by sudo apt + update and upgrade. Kernels 5.15.0-57-generic and 5.15.0-58-generic both + have kernel panic. The only option was to switch to a different kernel + i.e., 5.15.0-56-generic, under Advanced Options while booting. Please help and fix this. -- 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/2002779 Title: Kernels 5.15.0-57-generic and 5.15.0-58-generic kernel panic Status in linux package in Ubuntu: Confirmed Bug description: I have a GPU workstation with AMD Ryzen™ Threadripper 2950X Processor, ASUS Zenith Extreme, and four Nvidia GeForce RTX 2080Ti GPUs (Nvidia driver: 525). My OS is Ubuntu 22.04.1. I tried updating the by sudo apt update and upgrade. Kernels 5.15.0-57-generic and 5.15.0-58-generic both have kernel panic. The only option was to switch to a different kernel i.e., 5.15.0-56-generic, under Advanced Options while booting. Please help and fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003524] Re: amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks
** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003524 Title: amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: [Impact] From "Mario Limonciello mario.limonciello at amd.com" https://lists.ubuntu.com/archives/kernel-team/2023-January/136434.html. There is a problem in amdgpu that if not all of IP blocks are supported or not all of the firmware is present then the framebuffer is destroyed and the screen freezes. In more recent kernels the amdgpu driver loads for all PCI VGA class AMD devices. This effectively means that unless you have all the pieces you need to support a GPU then the installer freezes unless you do nomodeset. This problem is to be fully fixed in kernel 6.3 with a ~47 patch series that is currently in drm-next. This does two basic things: 1) If the IP blocks isn't supported, don't destroy the framebuffer. 2) If firmware for any IP blocks aren't present, don't destroy the framebuffer. The whole patch series still needs more time to back in drm-next, but the most important part of the series is the first patch which accomplishes "1". This patch went out to stable 6.1.y as well: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/amd?h=linux-6.1.y&id=dcfeba477b3e3df526e0f543b58fa71c045dff8b My reasoning is that it will ensure that if someone picks up a newer GPU such as Ryzen 7000 desktop or RDNA3 based they can at least install Ubuntu without needing to use "Safe Graphics Mode" at the installer. Sure; they won't have hardware acceleration without the rest of the kernel and framework, but that's a separate problem to a basic display. [Fix] Cherry-pick/backport commit 1923bc5a56daeeabd7e9093bad2febcd6af2416a "drm/amd: Delay removal of the firmware framebuffer" to Ubuntu Kinetic 5.19 kernel. [Test case] Boot kernel in a system with one of the amdgpu affected adapters. [Where problems can occur] The aforementioned commit could introduce other regressions on the support for AMD GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996892] Re: Expose built-in trusted and revoked certificates
** Tags removed: verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-focal verification-done-jammy verification-done-kinetic ** Tags added: kernel-stable-tracking-bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996892 Title: Expose built-in trusted and revoked certificates Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Confirmed Bug description: [ Impact ] * Kernels have a set of builtin trusted and revoked certificates as a bundle * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information [ Test Plan ] * sudo apt install linux-buildinfo-$(uname -r) * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert Example output: $ grep Subject: -r usr/lib/linux usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = Canonical Ltd. Live Patch Signing usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel Module Signing usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical Ltd. Secure Boot Signing [ Where problems could occur ] * buildinfo is an auxiliary package not installed by default, but used by developer tooling and packaging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996198] Re: Fix rfkill causing soft blocked wifi
** Tags removed: verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-focal verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1996198 Title: Fix rfkill causing soft blocked wifi Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.0 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Need this patch in so a BIOS upgrade won't cause issues on HP laptops. commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a Author: Jorge Lopez Date: Fri Oct 28 10:55:27 2022 -0500 platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded strange char "^@" which printed out every second and makes login nearly impossible. Also the below messages were shown both in console and journal/dmesg every second: usb 1-3: Device not responding to setup address. usb 1-3: device not accepting address 4, error -71 usb 1-3: device descriptor read/all, error -71 usb usb1-port3: unable to enumerate USB device Wifi is soft blocked by checking rfkill. When unblocked manually, after few seconds it would be soft blocked again. So I was suspecting something triggered rfkill to soft block wifi. At the end it was fixed by removing hp_wmi module. The root cause is the way hp-wmi driver handles command 1B on post-2009 BIOS. In pre-2009 BIOS, command 1Bh return 0x4 to indicate that BIOS no longer controls the power for the wireless devices. Signed-off-by: Jorge Lopez Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468 Reviewed-by: Mario Limonciello Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com Cc: sta...@vger.kernel.org Reviewed-by: Hans de Goede Signed-off-by: Hans de Goede [Test case] test on a HP laptop with the new BIOS [Where problems could occur] from the commit: * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that * BIOS no longer controls the power for the wireless * devices. All features supported by this command will no * longer be supported. anyone running a laptop with obsolete pre-2009 BIOS probably won't notice the missing feature at this point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
** Tags removed: verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-focal verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003547] [NEW] [UBUNTU 23.04] net/smc: Alibaba patches about tunable buffer sizes may cause errors and need to be removed (kernel 6.2)
You have been subscribed to a public bug: There are two patches about tunable buffer sizes that are changing the conventional behavior in our SMC code. This change of behavior might not be expected by our clients, which could lead to problems. Therefore, we need to remove these two patches from v6.2 / lunar, until we can provide an appropriate solution. The two patches to be removed depend on each other, but don't have any further dependencies to other code/commits. Please remove / revert the following two patches: 0227f058aa29 net/smc: Unbind r/w buffer size from clcsock and make them tunable 77eee3251431 net/smc: Introduce a specific sysctl for TEST_LINK time ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-201316 severity-high targetmilestone-inin--- -- [UBUNTU 23.04] net/smc: Alibaba patches about tunable buffer sizes may cause errors and need to be removed (kernel 6.2) https://bugs.launchpad.net/bugs/2003547 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003547] [NEW] [UBUNTU 23.04] net/smc: Alibaba patches about tunable buffer sizes may cause errors and need to be removed (kernel 6.2)
Public bug reported: There are two patches about tunable buffer sizes that are changing the conventional behavior in our SMC code. This change of behavior might not be expected by our clients, which could lead to problems. Therefore, we need to remove these two patches from v6.2 / lunar, until we can provide an appropriate solution. The two patches to be removed depend on each other, but don't have any further dependencies to other code/commits. Please remove / revert the following two patches: 0227f058aa29 net/smc: Unbind r/w buffer size from clcsock and make them tunable 77eee3251431 net/smc: Introduce a specific sysctl for TEST_LINK time ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-201316 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-201316 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003547 Title: [UBUNTU 23.04] net/smc: Alibaba patches about tunable buffer sizes may cause errors and need to be removed (kernel 6.2) Status in linux package in Ubuntu: New Bug description: There are two patches about tunable buffer sizes that are changing the conventional behavior in our SMC code. This change of behavior might not be expected by our clients, which could lead to problems. Therefore, we need to remove these two patches from v6.2 / lunar, until we can provide an appropriate solution. The two patches to be removed depend on each other, but don't have any further dependencies to other code/commits. Please remove / revert the following two patches: 0227f058aa29 net/smc: Unbind r/w buffer size from clcsock and make them tunable 77eee3251431 net/smc: Introduce a specific sysctl for TEST_LINK time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003547/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003332] Re: jammy linux-riscv-5.19 promote from universe to main
Both should now be in main. ** Changed in: linux-meta-riscv-5.19 (Ubuntu) Status: Triaged => Fix Committed ** Changed in: linux-riscv-5.19 (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2003332 Title: jammy linux-riscv-5.19 promote from universe to main Status in linux-meta-riscv-5.19 package in Ubuntu: Fix Committed Status in linux-riscv-5.19 package in Ubuntu: Fix Committed Bug description: jammy linux-riscv-5.19 promote from universe to main new kernel published in the wrong component. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv-5.19/+bug/2003332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999319] Re: linux-image-oracle missing linux-modules-extra dependency on arm64
See also bug #2000665. Other cloud kernels don't depend directly on extras and instead provide a top level metapackage to track the extras versions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1999319 Title: linux-image-oracle missing linux-modules-extra dependency on arm64 Status in linux-meta-oracle package in Ubuntu: New Bug description: linux-image-oracle 5.15.0.1025.20 on ubuntu 22.04 is missing the linux-modules-extra dependency on arm64. The dependency correctly exists on amd64. This looks like a regression of https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1927704, which was fixed for Ubuntu Focal. I noticed this while looking into DRBD, but assume it affects any module in the dependent package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oracle/+bug/1999319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000665] Re: Missing linux-modules-extra-oracle metapackage
This may be related to bug #1999319 which talks about the extra package being a direct dependency of the linux-image package, which seems wrong; other cloud kernels keep extra separate and use a metapackage to pull it in. So perhaps this only affects arm64 at the moment due to amd64 having the dependency from linux-image, but ideally I think this should be fixed in line with other kernel metapackages and use a top-level metapackage for extras. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2000665 Title: Missing linux-modules-extra-oracle metapackage Status in linux-meta-oracle package in Ubuntu: New Bug description: [Full disclosure: I am an Oracle employee.] There are linux-modules-extra-FOO metapackages for other cloud- oriented images (-azure, -gcp, -aws), but not for -oracle. Another user reported this here: https://askubuntu.com/questions/1414429/no-linux-modules-extra-oracle- package So right now there is no way to track the linux-modules-extra-VERSION- oracle package versions automatically on "apt-get upgrade". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-oracle 5.15.0.1025.20 ProcVersionSignature: User Name 5.15.0-1025.31-oracle 5.15.64 Uname: Linux 5.15.0-1025-oracle aarch64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: arm64 CasperMD5CheckResult: unknown Date: Wed Dec 28 20:37:22 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-meta-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oracle/+bug/2000665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999406] Re: Update firmware for hwe/oem kernel migrations
** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1999406 Title: Update firmware for hwe/oem kernel migrations Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Lunar: Fix Committed Bug description: [SRU Justification] [Impact] When migrating to a new hwe kernel or introduced a oem kernel of a newer version, the firmware blobs might not match the expectation of the new kernel. For example, a hwe-5.15 on Focal may include new drivers that relies on firmware blobs that are only available in Jammy. [Fix] A previously obsoleted (and removed in Kinetic and Lunar) script `list-lts-update-files` is used to enumerate firmware blobs to be backported. It's retored and revised with additional support to pick the right blobs especially in regard to ath and iwlwifi drivers. On Focal, the commits in need are enumerated by: $ debian/scripts/list-lts-update-files focal jammy \ ../jammy/debian.master/abi/fwinfo | \ xargs git log --graph --oneline focal..jammy -- * 36f2ea9f7 ath11k: WCN6855 hw2.0: add WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3 * 05b5dc001 ath11k: WCN6855 hw2.0: add board-2.bin and regdb.bin * 7a3005059 brcm: Add 43455 based AP6255 NVRAM for the ACEPC T8 Mini PC * ad185afa1 cypress: update firmware for cyw4373 sdio * 77d3eb8ef cypress: update firmware for cyw43570 pcie * 92e9acdbd cypress: update firmware for cyw4356 sdio * 5f88084be cypress: update firmware for cyw4354 sdio * f97e31677 cypress: update firmware for cyw43455 sdio * 3df9ea0b9 cypress: update firmware for cyw43430 sdio * 6150015cf cypress: update firmware for cyw43012 sdio * 2548d065b brcm: Add nvram for the Chuwi Hi8 (CWI509) tablet * e45c137e7 brcm: Add nvram for the Predia Basic tablet * d52886242 brcm: Add NVRAM for Vamrs 96boards Rock960 * b503c9660 Merge branch 'ath10k-20201023' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/linux-firmware into main |\ | * 34cb5fce2 ath11k: IPQ8074 hw2.0: add to WLAN.HK.2.1.0.1-01238-QCAHKSWPL_SILICONZ-2 | * c0a8efd24 ath11k: IPQ8074 hw2.0: add board-2.bin | * ac7f5e93f ath11k: IPQ6018 hw1.0: add to WLAN.HK.2.1.0.1-01238-QCAHKSWPL_SILICONZ-2 | * 2594e510a ath11k: IPQ6018 hw1.0: add board-2.bin * 04f71fe56 cypress: add Cypress firmware and clm_blob files Commit 05b5dc001 and 36f2ea9f7 include updates to other existing files, so they are dropped from this SRU. An additional commit that modifies only WHENCE, commit 0b558e8a7, found when resolving conflicts, were also added. On Jammy, $ debian/scripts/list-lts-update-files jammy kinetic \ ../kinetic/debian.master/abi/fwinfo | \ xargs git log --graph --oneline jammy..kinetic -- * 35f8de521 UBUNTU: Add pre-compiled echoaudio firmware * c954892f6 Add initial AzureWave AW-CM256SM NVRAM file * 86f0c5642 ath10k: WCN3990 hw1.0: add board-2.bin * c3624ebd6 Merge branch 'ath10k-20220423' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/linux-firmware into main |\ | * 1962cbab3 ath10k: QCA99X0 hw2.0: add board-2.bin | * 0d5e9f7e0 ath11k: WCN6750 hw1.0: add to WLAN.MSL.1.0.1-00887-QCAMSLSWPLZ-1 | * a50132f7f ath11k: WCN6750 hw1.0: add board-2.bin | * 97f8b7563 ath11k: QCN9074 hw1.0: add to WLAN.HK.2.5.0.1-01208-QCAHKSWPL_SILICONZ-1 | * f56505fe2 ath11k: QCN9074 hw1.0: add board-2.bin * | dfa3c4c30 qcom: add firmware files for Adreno a420 & related generations * | 4a43f1a84 qcom: add firmware files for Adreno a330 * | ac21ab5d1 Mellanox: Add lc_ini_bundle for xx.2010.1006 |/ * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it Commit 4ffcf980a involves rename existing files in WHENCE, so ignored. While Jammy has 3 additional oem kernels, they were also tested: $ debian/scripts/list-lts-update-files jammy kinetic \ ../oem-5.17/debian.oem/abi/fwinfo | \ xargs git log --graph --oneline jammy..kinetic -- (no new commits) $ debian/scripts/list-lts-update-files jammy lunar \ ../oem-6.0/debian.oem/abi/fwinfo | \ xargs git log --graph --oneline jammy..lunar -- * 06dbfbc74 iwlwifi: add new FWs from core69-81 release $ debian/scripts/list-lts-update-files jammy lunar \ ../oem-6.1/debian.oem/abi/fwinfo | \ xargs git log --graph --oneline jammy..lunar -- * 51fff4e69 i915: Add versionless HuC files for current platforms On Lunar, while it's not an LTS series and there will not be any hwe/oem kernel backported, the only
[Kernel-packages] [Bug 1999406] Re: Update firmware for hwe/oem kernel migrations
** Changed in: linux-firmware (Ubuntu Lunar) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1999406 Title: Update firmware for hwe/oem kernel migrations Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Lunar: Fix Committed Bug description: [SRU Justification] [Impact] When migrating to a new hwe kernel or introduced a oem kernel of a newer version, the firmware blobs might not match the expectation of the new kernel. For example, a hwe-5.15 on Focal may include new drivers that relies on firmware blobs that are only available in Jammy. [Fix] A previously obsoleted (and removed in Kinetic and Lunar) script `list-lts-update-files` is used to enumerate firmware blobs to be backported. It's retored and revised with additional support to pick the right blobs especially in regard to ath and iwlwifi drivers. On Focal, the commits in need are enumerated by: $ debian/scripts/list-lts-update-files focal jammy \ ../jammy/debian.master/abi/fwinfo | \ xargs git log --graph --oneline focal..jammy -- * 36f2ea9f7 ath11k: WCN6855 hw2.0: add WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3 * 05b5dc001 ath11k: WCN6855 hw2.0: add board-2.bin and regdb.bin * 7a3005059 brcm: Add 43455 based AP6255 NVRAM for the ACEPC T8 Mini PC * ad185afa1 cypress: update firmware for cyw4373 sdio * 77d3eb8ef cypress: update firmware for cyw43570 pcie * 92e9acdbd cypress: update firmware for cyw4356 sdio * 5f88084be cypress: update firmware for cyw4354 sdio * f97e31677 cypress: update firmware for cyw43455 sdio * 3df9ea0b9 cypress: update firmware for cyw43430 sdio * 6150015cf cypress: update firmware for cyw43012 sdio * 2548d065b brcm: Add nvram for the Chuwi Hi8 (CWI509) tablet * e45c137e7 brcm: Add nvram for the Predia Basic tablet * d52886242 brcm: Add NVRAM for Vamrs 96boards Rock960 * b503c9660 Merge branch 'ath10k-20201023' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/linux-firmware into main |\ | * 34cb5fce2 ath11k: IPQ8074 hw2.0: add to WLAN.HK.2.1.0.1-01238-QCAHKSWPL_SILICONZ-2 | * c0a8efd24 ath11k: IPQ8074 hw2.0: add board-2.bin | * ac7f5e93f ath11k: IPQ6018 hw1.0: add to WLAN.HK.2.1.0.1-01238-QCAHKSWPL_SILICONZ-2 | * 2594e510a ath11k: IPQ6018 hw1.0: add board-2.bin * 04f71fe56 cypress: add Cypress firmware and clm_blob files Commit 05b5dc001 and 36f2ea9f7 include updates to other existing files, so they are dropped from this SRU. An additional commit that modifies only WHENCE, commit 0b558e8a7, found when resolving conflicts, were also added. On Jammy, $ debian/scripts/list-lts-update-files jammy kinetic \ ../kinetic/debian.master/abi/fwinfo | \ xargs git log --graph --oneline jammy..kinetic -- * 35f8de521 UBUNTU: Add pre-compiled echoaudio firmware * c954892f6 Add initial AzureWave AW-CM256SM NVRAM file * 86f0c5642 ath10k: WCN3990 hw1.0: add board-2.bin * c3624ebd6 Merge branch 'ath10k-20220423' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/linux-firmware into main |\ | * 1962cbab3 ath10k: QCA99X0 hw2.0: add board-2.bin | * 0d5e9f7e0 ath11k: WCN6750 hw1.0: add to WLAN.MSL.1.0.1-00887-QCAMSLSWPLZ-1 | * a50132f7f ath11k: WCN6750 hw1.0: add board-2.bin | * 97f8b7563 ath11k: QCN9074 hw1.0: add to WLAN.HK.2.5.0.1-01208-QCAHKSWPL_SILICONZ-1 | * f56505fe2 ath11k: QCN9074 hw1.0: add board-2.bin * | dfa3c4c30 qcom: add firmware files for Adreno a420 & related generations * | 4a43f1a84 qcom: add firmware files for Adreno a330 * | ac21ab5d1 Mellanox: Add lc_ini_bundle for xx.2010.1006 |/ * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it Commit 4ffcf980a involves rename existing files in WHENCE, so ignored. While Jammy has 3 additional oem kernels, they were also tested: $ debian/scripts/list-lts-update-files jammy kinetic \ ../oem-5.17/debian.oem/abi/fwinfo | \ xargs git log --graph --oneline jammy..kinetic -- (no new commits) $ debian/scripts/list-lts-update-files jammy lunar \ ../oem-6.0/debian.oem/abi/fwinfo | \ xargs git log --graph --oneline jammy..lunar -- * 06dbfbc74 iwlwifi: add new FWs from core69-81 release $ debian/scripts/list-lts-update-files jammy lunar \ ../oem-6.1/debian.oem/abi/fwinfo | \ xargs git log --graph --oneline jammy..lunar -- * 51fff4e69 i915: Add versionless HuC files for current platforms On Lunar, while it's not an LTS series and there will not be any hwe/oem kernel backported, the only
[Kernel-packages] [Bug 2003348] Re: Kernel 6.2 does not boot on s390x
Sorry, I used the internal pastebin.
Anyway, we now did some attempts using a z/VM guest with
kernel 5.19, 6.1 and two 6.2 versions (in the attached tgz):
'hwe0009 - bootlog - 5.19.txt'
'hwe0009 - bootlog - 6.1.0-9.txt'
'hwe0009 - bootlog - 6.2.0-4.txt'
'hwe0009 - bootlog - 6.2.0-5.txt'
The 6.2.0-5 has some s390x specific commits reverted, but still has the same
issue.
By diffing these boot logs we found:
"Initramfs unpacking failed: ZSTD-compressed data is corrupt"
which then let's us think that it's maybe related to:
"zstd/zstd-next (2aa14b1ab2c4 zstd: import usptream v1.5.2)"
which is mega HUGE
no obvious s390x specific things though
but quite some bit and byte manipulations (where there's always a nice chance
that it can go wrong on big endian).
Now trying another kernel where 2aa14b1ab2c4 ("zstd: import usptream v1.5.2")
got reverted:
https://kernel.ubuntu.com/~arighi/lunar/linux-unstable/
...
** Attachment added: "boot-logs.tgz"
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003348/+attachment/5642705/+files/boot-logs.tgz
--
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/2003348
Title:
Kernel 6.2 does not boot on s390x
Status in Ubuntu on IBM z Systems:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The kernel team created a first kernel 6.2 for testing purposes.
linux-unstable 6.2.0-4.4 ia available in ppa:canonical-kernel-
team/bootstrap
However this kernel does not boot on s390x and crashes:
https://pastebin.canonical.com/p/qXj4g4bgGH/
or:
...
Ý0.408281¨ md: Waiting for all devices to be available before autodetect
Ý0.408283¨ md: If you don't use raid, use raid=noautodetect
Ý0.408285¨ md: Autodetecting RAID arrays.
Ý0.408287¨ md: autorun ...
Ý0.408288¨ md: ... autorun DONE.
Ý0.408405¨ /dev/root: Can't open blockdev
Ý0.408409¨ VFS: Cannot open root device "disk/by-path/ccw-0.0.0400-part1"
or
unknown-block(0,0): error -6
Ý0.408412¨ Please append a correct "root=" boot option; here are the
availa
le partitions:
Ý0.408415¨ Kernel panic - not syncing: VFS: Unable to mount root fs on
unkno
wn-block(0,0)
Ý0.408418¨ CPU: 2 PID: 1 Comm: swapper/0 Not tainted 6.2.0-4-generic
#4-Ubun
tu
Ý0.408421¨ Hardware name: IBM 2964 N63 400 (z/VM 6.4.0)
Ý0.408423¨ Call Trace:
Ý0.408425¨ ݨ dump_stack_lvl+0x62/0x90
Ý0.408433¨ ݨ panic+0x174/0x360
Ý0.408438¨ ݨ mount_block_root+0x16e/0x210
Ý0.408444¨ ݨ prepare_namespace+0x168/0x1e0
Ý0.408448¨ ݨ kernel_init_freeable+0x1de/0x1f0
Ý0.408451¨ ݨ kernel_init+0x2e/0x1a0
Ý0.408455¨ ݨ __ret_from_fork+0x40/0x60
Ý0.408459¨ ݨ ret_from_fork+0xa/0x40
02: HCPGIR450W CP entered; disabled wait PSW 00020001 8000
B50E215E
or:
[8.693187] /dev/root: Can't open blockdev
[8.693191] VFS: Cannot open root device "disk/by-path/ccw-0.0.260b-part1"
or unknown-block(0,0): error -6
[8.693194] Please append a correct "root=" boot option; here are the
available partitions:
[8.693198] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
Initially we thought it might be related to LVM/DM, but it's not,
since it happens also on single DASD disk installation without LVM and also
on NVMe disks.
It also happens on z15 and on z13.
Messages indicate that either the "root=" argument is wrong or not there.
I can check /proc/cmdline since the system ends up in a crash for me.
However, installing and using 6.1.0-9 works fine.
_
Steps to re-create:
- Install Ubuntu lunar using:
https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/lunar-live-server-s390x.iso
or:
https://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/lunar-live-server-s390x.iso
(- get it updated:
sudo apt -y -q update && sudo apt -y -q full-upgrade && sudo apt autoremove
--purge )
- sudo add-apt-repository --yes ppa:canonical-kernel-team/bootstrap
- $ sudo apt update
- $ sudo apt install --yes linux-image-6.2.0-4-generic
linux-modules-6.2.0-4-generic linux-modules-extra-6.2.0-4-generic
linux-headers-6.2.0-4-generic
- $ sudo reboot
- open the console (e.g. Operating Systems Messages) and monitor the boot/IPL
process, it's fail like above
Do the same with kernel 6.1:
sudo apt install --yes linux-image-6.1.0-9-generic
linux-modules-6.1.0-9-generic linux-modules-extra-6.1.0-9-generic
linux-headers-6.1.0-9-generic
and the system reboots successfully.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003348/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packag
[Kernel-packages] [Bug 1998039] Re: Network Freeze With Broadcom DKMS Wireless Driver
** Description changed: Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset Ubuntu Release: 22.10 Kernel: 5.19.0-23-generic Symptoms: Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly related to suspend/resume). A search found a related issue[1]. $ lsmod | grep wl wl 6467584 0 cfg80211 1040384 1 wl $ dpkg -l | grep -i broadcom ii bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu9 amd64Broadcom 802.11 Linux STA wireless driver source - [1] https://salsa.debian.org/diegoe/broadcom- - sta/-/commit/720ac7c23d78d771219ed4c9228daa2cbb88a4ca + Test Case: + == + This is reproducible by forcing the computer to sleep and then waking it back up. + + + [1] https://salsa.debian.org/diegoe/broadcom-sta/-/commit/720ac7c23d78d771219ed4c9228daa2cbb88a4ca -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1998039 Title: Network Freeze With Broadcom DKMS Wireless Driver Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Jammy: Fix Committed Status in bcmwl source package in Kinetic: Fix Committed Bug description: Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset Ubuntu Release: 22.10 Kernel: 5.19.0-23-generic Symptoms: Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly related to suspend/resume). A search found a related issue[1]. $ lsmod | grep wl wl 6467584 0 cfg80211 1040384 1 wl $ dpkg -l | grep -i broadcom ii bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu9 amd64Broadcom 802.11 Linux STA wireless driver source Test Case: == This is reproducible by forcing the computer to sleep and then waking it back up. [1] https://salsa.debian.org/diegoe/broadcom-sta/-/commit/720ac7c23d78d771219ed4c9228daa2cbb88a4ca To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1998039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003348] Re: Kernel 6.2 does not boot on s390x
I can confirm that a modified kernel with "zstd/zstd-next (2aa14b1ab2c4 zstd: import usptream v1.5.2)" reverted works! -- 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/2003348 Title: Kernel 6.2 does not boot on s390x Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The kernel team created a first kernel 6.2 for testing purposes. linux-unstable 6.2.0-4.4 ia available in ppa:canonical-kernel- team/bootstrap However this kernel does not boot on s390x and crashes: https://pastebin.canonical.com/p/qXj4g4bgGH/ or: ... Ý0.408281¨ md: Waiting for all devices to be available before autodetect Ý0.408283¨ md: If you don't use raid, use raid=noautodetect Ý0.408285¨ md: Autodetecting RAID arrays. Ý0.408287¨ md: autorun ... Ý0.408288¨ md: ... autorun DONE. Ý0.408405¨ /dev/root: Can't open blockdev Ý0.408409¨ VFS: Cannot open root device "disk/by-path/ccw-0.0.0400-part1" or unknown-block(0,0): error -6 Ý0.408412¨ Please append a correct "root=" boot option; here are the availa le partitions: Ý0.408415¨ Kernel panic - not syncing: VFS: Unable to mount root fs on unkno wn-block(0,0) Ý0.408418¨ CPU: 2 PID: 1 Comm: swapper/0 Not tainted 6.2.0-4-generic #4-Ubun tu Ý0.408421¨ Hardware name: IBM 2964 N63 400 (z/VM 6.4.0) Ý0.408423¨ Call Trace: Ý0.408425¨ ݨ dump_stack_lvl+0x62/0x90 Ý0.408433¨ Ý ¨ panic+0x174/0x360 Ý0.408438¨ Ý ¨ mount_block_root+0x16e/0x210 Ý0.408444¨ Ý ¨ prepare_namespace+0x168/0x1e0 Ý0.408448¨ Ý ¨ kernel_init_freeable+0x1de/0x1f0 Ý0.408451¨ Ý ¨ kernel_init+0x2e/0x1a0 Ý0.408455¨ Ý ¨ __ret_from_fork+0x40/0x60 Ý0.408459¨ Ý ¨ ret_from_fork+0xa/0x40 02: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 B50E215E or: [8.693187] /dev/root: Can't open blockdev [8.693191] VFS: Cannot open root device "disk/by-path/ccw-0.0.260b-part1" or unknown-block(0,0): error -6 [8.693194] Please append a correct "root=" boot option; here are the available partitions: [8.693198] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Initially we thought it might be related to LVM/DM, but it's not, since it happens also on single DASD disk installation without LVM and also on NVMe disks. It also happens on z15 and on z13. Messages indicate that either the "root=" argument is wrong or not there. I can check /proc/cmdline since the system ends up in a crash for me. However, installing and using 6.1.0-9 works fine. _ Steps to re-create: - Install Ubuntu lunar using: https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/lunar-live-server-s390x.iso or: https://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/lunar-live-server-s390x.iso (- get it updated: sudo apt -y -q update && sudo apt -y -q full-upgrade && sudo apt autoremove --purge ) - sudo add-apt-repository --yes ppa:canonical-kernel-team/bootstrap - $ sudo apt update - $ sudo apt install --yes linux-image-6.2.0-4-generic linux-modules-6.2.0-4-generic linux-modules-extra-6.2.0-4-generic linux-headers-6.2.0-4-generic - $ sudo reboot - open the console (e.g. Operating Systems Messages) and monitor the boot/IPL process, it's fail like above Do the same with kernel 6.1: sudo apt install --yes linux-image-6.1.0-9-generic linux-modules-6.1.0-9-generic linux-modules-extra-6.1.0-9-generic linux-headers-6.1.0-9-generic and the system reboots successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003547] Re: [UBUNTU 23.04] net/smc: Alibaba patches about tunable buffer sizes may cause errors and need to be removed (kernel 6.2)
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-z-systems Status: New => Confirmed ** 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/2003547 Title: [UBUNTU 23.04] net/smc: Alibaba patches about tunable buffer sizes may cause errors and need to be removed (kernel 6.2) Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: There are two patches about tunable buffer sizes that are changing the conventional behavior in our SMC code. This change of behavior might not be expected by our clients, which could lead to problems. Therefore, we need to remove these two patches from v6.2 / lunar, until we can provide an appropriate solution. The two patches to be removed depend on each other, but don't have any further dependencies to other code/commits. Please remove / revert the following two patches: 0227f058aa29 net/smc: Unbind r/w buffer size from clcsock and make them tunable 77eee3251431 net/smc: Introduce a specific sysctl for TEST_LINK time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003547/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000133] Re: amdgpu: missing firmware for navi31
** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2000133 Title: amdgpu: missing firmware for navi31 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Won't Fix Status in linux-firmware source package in Lunar: Triaged Bug description: [5.232972] amdgpu :03:00.0: Direct firmware load for amdgpu/psp_13_0_0_sos.bin failed with error -2 [5.232974] amdgpu :03:00.0: amdgpu: failed to init sos firmware [5.232975] [drm:psp_sw_init [amdgpu]] *ERROR* Failed to load psp firmware! [5.233097] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -2 [5.233232] amdgpu :03:00.0: amdgpu: amdgpu_device_ip_init failed [5.233233] amdgpu :03:00.0: amdgpu: Fatal error during GPU init [5.233235] amdgpu :03:00.0: amdgpu: amdgpu: finishing device. [5.233459] amdgpu: probe of :03:00.0 failed with error -2 The following new firmware binaries are introduced to linux- firmware.git. 31c57349 amdgpu: add VCN 4.0.0 firmware for amd-5.4 a7351589 amdgpu: add SMU 13.0.0 firmware for amd-5.4 0bef6bb1 amdgpu: Add SDMA 6.0.0 firmware for amd-5.4 bb56d1a7 amdgpu: add PSP 13.0.0 firmware for amd-5.4 e32209f0 amdgpu: add GC 11.0.0 firmware for amd-5.4 613db81f amdgpu: add DCN 3.2.0 firmware for amd-5.4 These are all needed for supporting navi31 dGPU. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1573 F pulseaudio /dev/snd/controlC1: gdm1573 F pulseaudio CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4 [origin: Ubuntu] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish+X12 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-19 (124 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 MachineType: Intel Corporation Raptor Lake Client Platform Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1009-oem root=UUID=1513ef0d-bc45-444e-906e-d81039e5f411 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1009.9-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1009-oem N/A linux-backports-modules-6.0.0-1009-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy third-party-packages Uname: Linux 6.0.0-1009-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/29/2022 dmi.bios.vendor: Intel Corporation dmi.bios.version: RPLSFWI1.R00.3047.A00.2201290228 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: RPL-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnIntelCorporation:bvrRPLSFWI1.R00.3047.A00.2201290228:bd01/29/2022:efr1.51:svnIntelCorporation:pnRaptorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnRPL-SADP-SDDR5UDIMMCRB:rvr1:cvnIntelCorporation:ct3:cvr0.1:sku11390001: dmi.product.family: Raptor Lake Client System dmi.product.name: Raptor Lake Client Platform dmi.product.sku: 11390001 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/2000133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002601] Re: Wireless: Enable RTL8852BE wifi driver
** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Lunar) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2002601 Title: Wireless: Enable RTL8852BE wifi driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998039] Re: Network Freeze With Broadcom DKMS Wireless Driver
Hi Łukasz, The test passes locally for me. My reproducer, which works consistently on this machine, did not reproduce this issue using the new package. Suspending the machine was sufficient to force the error condition, but now that does not happen. Package/Kernel versions: isa~ apt show bcmwl-kernel-source Package: bcmwl-kernel-source Version: 6.30.223.271+bdcom-0ubuntu10~22.10.1 Priority: optional Section: restricted/admin Source: bcmwl Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Alberto Milone Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 8,090 kB Depends: dkms, linux-libc-dev, libc6-dev Conflicts: bcmwl-modaliases Replaces: bcmwl-modaliases Modaliases: wl(pci:v14E4d4311sv*sd*bc02sc80i*, pci:v14E4d4312sv*sd*bc02sc80i*, pci:v14E4d4313sv*sd*bc02sc80i*, pci:v14E4d4315sv*sd*bc02sc80i*, pci:v14E4d4727sv*sd*bc02sc80i*, pci:v14E4d4328sv*sd*bc02sc80i*, pci:v14E4d4328sv*sd*bc02sc80i*, pci:v14E4d4329sv*sd*bc02sc80i*, pci:v14E4d432asv*sd*bc02sc80i*, pci:v14E4d432bsv*sd*bc02sc80i*, pci:v14E4d432csv*sd*bc02sc80i*, pci:v14E4d432dsv*sd*bc02sc80i*, pci:v14E4d4365sv*sd*bc02sc80i*, pci:v14E4d4353sv*sd*bc02sc80i*, pci:v14E4d4357sv*sd*bc02sc80i*, pci:v14E4d4358sv*sd*bc02sc80i*, pci:v14E4d4359sv*sd*bc02sc80i*, pci:v14E4d4331sv*sd*bc02sc80i*, pci:v14E4d43a0sv*sd*bc02sc80i*, pci:v14E4d43B1sv*sd*bc02sc80i*) Download-Size: 1,750 kB APT-Manual-Installed: yes APT-Sources: http://us.archive.ubuntu.com/ubuntu kinetic-proposed/restricted amd64 Packages Description: Broadcom 802.11 Linux STA wireless driver source This package contains Broadcom 802.11 Linux STA wireless driver for use with Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based isa~ uname -a Linux isa 5.19.0-30-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 6 15:40:20 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ** Description changed: Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset Ubuntu Release: 22.10 Kernel: 5.19.0-23-generic Symptoms: Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly related to suspend/resume). - A search found a related issue[1]. + This has been fixed in Arch and Debian already [1]. $ lsmod | grep wl wl 6467584 0 cfg80211 1040384 1 wl $ dpkg -l | grep -i broadcom ii bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu9 amd64Broadcom 802.11 Linux STA wireless driver source Test Case: == This is reproducible by forcing the computer to sleep and then waking it back up. - - [1] https://salsa.debian.org/diegoe/broadcom-sta/-/commit/720ac7c23d78d771219ed4c9228daa2cbb88a4ca + [1] https://salsa.debian.org/diegoe/broadcom- + sta/-/commit/720ac7c23d78d771219ed4c9228daa2cbb88a4ca -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1998039 Title: Network Freeze With Broadcom DKMS Wireless Driver Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Jammy: Fix Committed Status in bcmwl source package in Kinetic: Fix Committed Bug description: Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset Ubuntu Release: 22.10 Kernel: 5.19.0-23-generic Symptoms: Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly related to suspend/resume). This has been fixed in Arch and Debian already [1]. $ lsmod | grep wl wl 6467584 0 cfg80211 1040384 1 wl $ dpkg -l | grep -i broadcom ii bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu9 amd64Broadcom 802.11 Linux STA wireless driver source Test Case: == This is reproducible by forcing the computer to sleep and then waking it back up. [1] https://salsa.debian.org/diegoe/broadcom- sta/-/commit/720ac7c23d78d771219ed4c9228daa2cbb88a4ca To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1998039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998039] Re: Network Freeze With Broadcom DKMS Wireless Driver
** Description changed: Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset Ubuntu Release: 22.10 Kernel: 5.19.0-23-generic Symptoms: Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly related to suspend/resume). This has been fixed in Arch and Debian already [1]. $ lsmod | grep wl wl 6467584 0 cfg80211 1040384 1 wl $ dpkg -l | grep -i broadcom ii bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu9 amd64Broadcom 802.11 Linux STA wireless driver source Test Case: == This is reproducible by forcing the computer to sleep and then waking it back up. + Regression Potential: + = + Since this is due to an intentional ABI change in the upstream kernel, regression potential is low. + [1] https://salsa.debian.org/diegoe/broadcom- sta/-/commit/720ac7c23d78d771219ed4c9228daa2cbb88a4ca -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1998039 Title: Network Freeze With Broadcom DKMS Wireless Driver Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Jammy: Fix Committed Status in bcmwl source package in Kinetic: Fix Committed Bug description: Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset Ubuntu Release: 22.10 Kernel: 5.19.0-23-generic Symptoms: Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly related to suspend/resume). This has been fixed in Arch and Debian already [1]. $ lsmod | grep wl wl 6467584 0 cfg80211 1040384 1 wl $ dpkg -l | grep -i broadcom ii bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu9 amd64Broadcom 802.11 Linux STA wireless driver source Test Case: == This is reproducible by forcing the computer to sleep and then waking it back up. Regression Potential: = Since this is due to an intentional ABI change in the upstream kernel, regression potential is low. [1] https://salsa.debian.org/diegoe/broadcom- sta/-/commit/720ac7c23d78d771219ed4c9228daa2cbb88a4ca To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1998039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003332] Re: jammy linux-riscv-5.19 promote from universe to main
** Changed in: linux-riscv-5.19 (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-meta-riscv-5.19 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2003332 Title: jammy linux-riscv-5.19 promote from universe to main Status in linux-meta-riscv-5.19 package in Ubuntu: Fix Released Status in linux-riscv-5.19 package in Ubuntu: Fix Released Bug description: jammy linux-riscv-5.19 promote from universe to main new kernel published in the wrong component. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv-5.19/+bug/2003332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002664] Re: RM obsolete unsupported v5.17 kernel
Removing packages from lunar: linux-allwinner-5.17 5.17.0-1003.3 in lunar linux-allwinner-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar amd64 linux-allwinner-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar arm64 linux-allwinner-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar armhf linux-allwinner-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar i386 linux-allwinner-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar ppc64el linux-allwinner-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar riscv64 linux-allwinner-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar s390x linux-allwinner-5.17-tools-5.17.0-1003 5.17.0-1003.3 in lunar riscv64 linux-buildinfo-5.17.0-1003-allwinner 5.17.0-1003.3 in lunar riscv64 linux-headers-5.17.0-1003-allwinner 5.17.0-1003.3 in lunar riscv64 linux-image-5.17.0-1003-allwinner 5.17.0-1003.3 in lunar riscv64 linux-modules-5.17.0-1003-allwinner 5.17.0-1003.3 in lunar riscv64 linux-modules-extra-5.17.0-1003-allwinner 5.17.0-1003.3 in lunar riscv64 linux-tools-5.17.0-1003-allwinner 5.17.0-1003.3 in lunar riscv64 linux-meta-oem-5.17 5.17.0.1003.3 in lunar linux-headers-oem-22.04a 5.17.0.1003.3 in lunar amd64 linux-image-oem-22.04a 5.17.0.1003.3 in lunar amd64 linux-oem-22.04a 5.17.0.1003.3 in lunar amd64 linux-tools-oem-22.04a 5.17.0.1003.3 in lunar amd64 linux-oem-5.17 5.17.0-1003.3 in lunar linux-buildinfo-5.17.0-1003-oem 5.17.0-1003.3 in lunar amd64 linux-headers-5.17.0-1003-oem 5.17.0-1003.3 in lunar amd64 linux-image-unsigned-5.17.0-1003-oem 5.17.0-1003.3 in lunar amd64 linux-modules-5.17.0-1003-oem 5.17.0-1003.3 in lunar amd64 linux-oem-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar amd64 linux-oem-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar arm64 linux-oem-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar armhf linux-oem-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar i386 linux-oem-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar ppc64el linux-oem-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar riscv64 linux-oem-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar s390x linux-oem-5.17-tools-5.17.0-1003 5.17.0-1003.3 in lunar amd64 linux-oem-5.17-tools-host 5.17.0-1003.3 in lunar amd64 linux-oem-5.17-tools-host 5.17.0-1003.3 in lunar arm64 linux-oem-5.17-tools-host 5.17.0-1003.3 in lunar armhf linux-oem-5.17-tools-host 5.17.0-1003.3 in lunar i386 linux-oem-5.17-tools-host 5.17.0-1003.3 in lunar ppc64el linux-oem-5.17-tools-host 5.17.0-1003.3 in lunar riscv64 linux-oem-5.17-tools-host 5.17.0-1003.3 in lunar s390x linux-tools-5.17.0-1003-oem 5.17.0-1003.3 in lunar amd64 linux-restricted-signatures-oem-5.17 5.17.0-1003.3+1 in lunar linux-signatures-nvidia-5.17.0-1003-oem 5.17.0-1003.3+1 in lunar amd64 linux-signed-oem-5.17 5.17.0-1003.3 in lunar linux-image-5.17.0-1003-oem 5.17.0-1003.3 in lunar amd64 linux-starfive-5.17 5.17.0-1004.5 in lunar linux-buildinfo-5.17.0-1004-starfive 5.17.0-1004.5 in lunar riscv64 linux-headers-5.17.0-1004-starfive 5.17.0-1004.5 in lunar riscv64 linux-image-5.17.0-1004-starfive 5.17.0-1004.5 in lunar riscv64 linux-modules-5.17.0-1004-starfive 5.17.0-1004.5 in lunar riscv64 linux-modules-extra-5.17.0-1004-starfive 5.17.0-1004.5 in lunar riscv64 linux-starfive-5.17-headers-5.17.0-1004 5.17.0-1004.5 in lunar amd64 linux-starfive-5.17-headers-5.17.0-1004 5.17.0-1004.5 in lunar arm64 linux-starfive-5.17-headers-5.17.0-1004 5.17.0-1004.5 in lunar armhf linux-starfive-5.17-headers-5.17.0-1004 5.17.0-1004.5 in lunar i386 linux-starfive-5.17-headers-5.17.0-1004 5.17.0-1004.5 in lunar ppc64el linux-starfive-5.17-headers-5.17.0-1004 5.17.0-1004.5 in lunar riscv64 linux-starfive-5.17-headers-5.17.0-1004 5.17.0-1004.5 in lunar s390x linux-starfive-5.17-tools-5.17.0-1004 5.17.0-1004.5 in lunar riscv64 linux-tools-5.17.0-1004-starfive 5.17.0-1004.5 in lunar riscv64 Comment: Obsolete kernel version; LP: #2002664 6 packages successfully removed. ** Changed in: linux-allwinner-5.17 (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux-meta-oem-5.17 (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux-oem-5.17 (Ubuntu)
[Kernel-packages] [Bug 2000133] Re: amdgpu: missing firmware for navi31
Uploaded to Lunar now also: https://lists.ubuntu.com/archives/lunar-changes/2023-January/007283.html -- 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/2000133 Title: amdgpu: missing firmware for navi31 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Won't Fix Status in linux-firmware source package in Lunar: Triaged Bug description: [5.232972] amdgpu :03:00.0: Direct firmware load for amdgpu/psp_13_0_0_sos.bin failed with error -2 [5.232974] amdgpu :03:00.0: amdgpu: failed to init sos firmware [5.232975] [drm:psp_sw_init [amdgpu]] *ERROR* Failed to load psp firmware! [5.233097] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -2 [5.233232] amdgpu :03:00.0: amdgpu: amdgpu_device_ip_init failed [5.233233] amdgpu :03:00.0: amdgpu: Fatal error during GPU init [5.233235] amdgpu :03:00.0: amdgpu: amdgpu: finishing device. [5.233459] amdgpu: probe of :03:00.0 failed with error -2 The following new firmware binaries are introduced to linux- firmware.git. 31c57349 amdgpu: add VCN 4.0.0 firmware for amd-5.4 a7351589 amdgpu: add SMU 13.0.0 firmware for amd-5.4 0bef6bb1 amdgpu: Add SDMA 6.0.0 firmware for amd-5.4 bb56d1a7 amdgpu: add PSP 13.0.0 firmware for amd-5.4 e32209f0 amdgpu: add GC 11.0.0 firmware for amd-5.4 613db81f amdgpu: add DCN 3.2.0 firmware for amd-5.4 These are all needed for supporting navi31 dGPU. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1573 F pulseaudio /dev/snd/controlC1: gdm1573 F pulseaudio CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4 [origin: Ubuntu] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish+X12 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-19 (124 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 MachineType: Intel Corporation Raptor Lake Client Platform Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1009-oem root=UUID=1513ef0d-bc45-444e-906e-d81039e5f411 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1009.9-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1009-oem N/A linux-backports-modules-6.0.0-1009-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy third-party-packages Uname: Linux 6.0.0-1009-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/29/2022 dmi.bios.vendor: Intel Corporation dmi.bios.version: RPLSFWI1.R00.3047.A00.2201290228 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: RPL-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnIntelCorporation:bvrRPLSFWI1.R00.3047.A00.2201290228:bd01/29/2022:efr1.51:svnIntelCorporation:pnRaptorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnRPL-SADP-SDDR5UDIMMCRB:rvr1:cvnIntelCorporation:ct3:cvr0.1:sku11390001: dmi.product.family: Raptor Lake Client System dmi.product.name: Raptor Lake Client Platform dmi.product.sku: 11390001 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/2000133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003267] Re: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release
** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003267 Title: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release Status in intel: Fix Released Status in linux package in Ubuntu: In Progress Bug description: Description: Enable Intel_idle for eagle stream. Target Kernel: Backport to 5.15 Target Release: 22.04 Commit Ids: 7eac3bd38d18 intel_idle: Fix SPR C6 optimization (Merged in 5.18 kernel) 39c184a6a9a7 intel_idle: Fix the 'preferred_cstates' module parameter (Merged in 5.18 kernel) 03eb65224e57 cpuidle: intel_idle: Drop redundant backslash at line end (Merged in 5.18 kernel) 3a9cf77b60dc intel_idle: add core C6 optimization for SPR (Merged in 5.18 kernel) da0e58c038e6 intel_idle: add 'preferred_cstates' module argument (Merged in 5.18 kernel) 9edf3c0ffef0 intel_idle: add SPR support(Merged in 5.18 kernel) 1548fac47a11 intel_idle: make SPR C1 and C1E be independent (Merged in 6.0 kernel) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2003267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003267] Re: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003267 Title: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release Status in intel: Fix Released Status in linux package in Ubuntu: In Progress Bug description: Description: Enable Intel_idle for eagle stream. Target Kernel: Backport to 5.15 Target Release: 22.04 Commit Ids: 7eac3bd38d18 intel_idle: Fix SPR C6 optimization (Merged in 5.18 kernel) 39c184a6a9a7 intel_idle: Fix the 'preferred_cstates' module parameter (Merged in 5.18 kernel) 03eb65224e57 cpuidle: intel_idle: Drop redundant backslash at line end (Merged in 5.18 kernel) 3a9cf77b60dc intel_idle: add core C6 optimization for SPR (Merged in 5.18 kernel) da0e58c038e6 intel_idle: add 'preferred_cstates' module argument (Merged in 5.18 kernel) 9edf3c0ffef0 intel_idle: add SPR support(Merged in 5.18 kernel) 1548fac47a11 intel_idle: make SPR C1 and C1E be independent (Merged in 6.0 kernel) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2003267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003267] Re: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release
I backported the 7 requested patches to Jammy and built a test kernel. The test kernel can be downloaded from: https://people.canonical.com/~jsalisbury/lp2003267/ Can you test this kernel and confirm it adds the functionality you require? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003267 Title: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release Status in intel: Fix Released Status in linux package in Ubuntu: In Progress Bug description: Description: Enable Intel_idle for eagle stream. Target Kernel: Backport to 5.15 Target Release: 22.04 Commit Ids: 7eac3bd38d18 intel_idle: Fix SPR C6 optimization (Merged in 5.18 kernel) 39c184a6a9a7 intel_idle: Fix the 'preferred_cstates' module parameter (Merged in 5.18 kernel) 03eb65224e57 cpuidle: intel_idle: Drop redundant backslash at line end (Merged in 5.18 kernel) 3a9cf77b60dc intel_idle: add core C6 optimization for SPR (Merged in 5.18 kernel) da0e58c038e6 intel_idle: add 'preferred_cstates' module argument (Merged in 5.18 kernel) 9edf3c0ffef0 intel_idle: add SPR support(Merged in 5.18 kernel) 1548fac47a11 intel_idle: make SPR C1 and C1E be independent (Merged in 6.0 kernel) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2003267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003596] [NEW] Bionic update: upstream stable patchset 2023-01-20
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-01-20 Ported from the following upstream stable releases: v4.14.299, v4.19.265 v4.19.266 v4.14.300, v4.19.267 v4.14.301, v4.19.268 v4.14.302, v4.19.269 from git://git.kernel.org/ NFSv4.1: Handle RECLAIM_COMPLETE trunking errors NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot nfs4: Fix kmemleak when allocate slot failed net: dsa: Fix possible memory leaks in dsa_loop_init() nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() net: fec: fix improper use of NETDEV_TX_BUSY ata: pata_legacy: fix pdc20230_set_piomode() net: sched: Fix use after free in red_enqueue() ipvs: use explicitly signed chars rose: Fix NULL pointer dereference in rose_send_frame() mISDN: fix possible memory leak in mISDN_register_device() isdn: mISDN: netjet: fix wrong check of device registration btrfs: fix inode list leak during backref walking at resolve_indirect_refs() btrfs: fix ulist leaks in error paths of qgroup self tests Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() net: mdio: fix undefined behavior in bit shift for __mdiobus_register net, neigh: Fix null-ptr-deref in neigh_table_clear() media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE media: dvb-frontends/drxk: initialize err to 0 i2c: xiic: Add platform module alias Bluetooth: L2CAP: Fix attempting to access uninitialized memory block, bfq: protect 'bfqd->queued' by 'bfqd->lock' btrfs: fix type of parameter generation in btrfs_get_dentry tcp/udp: Make early_demux back namespacified. capabilities: fix potential memleak on error path from vfs_getxattr_alloc() ALSA: usb-audio: Add quirks for MacroSilicon MS2100/MS2106 devices efi: random: reduce seed size to 32 bytes parisc: Make 8250_gsc driver dependend on CONFIG_PARISC parisc: Export iosapic_serial_irq() symbol for serial port driver ext4: fix warning in 'ext4_da_release_space' KVM: x86: Mask off reserved bits in CPUID.8008H KVM: x86: emulator: em_sysexit should update ctxt->mode KVM: x86: emulator: introduce emulator_recalc_and_set_mode KVM: x86: emulator: update the emulation mode after CR0 write linux/const.h: prefix include guard of uapi/linux/const.h with _UAPI linux/const.h: move UL() macro to include/linux/const.h linux/bits.h: make BIT(), GENMASK(), and friends available in assembly wifi: brcmfmac: Fix potential buffer overflow in brcmf_fweh_event_worker() RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() net: tun: fix bugs for oversize packet when napi frags enabled ipvs: fix WARNING in __ip_vs_cleanup_batch() ipvs: fix WARNING in ip_vs_app_net_cleanup() ipv6: fix WARNING in ip6_route_net_exit_late() parisc: Avoid printing the hardware path twice UBUNTU: Upstream stable to v4.14.299, v4.19.265 HID: hyperv: fix possible memory leak in mousevsc_probe() net: gso: fix panic on frag_list with mixed head alloc types bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer net: fman: Unregister ethernet device on removal capabilities: fix undefined behavior in bit shift for CAP_TO_MASK net: lapbether: fix issue of dev reference count leakage in lapbeth_device_event() hamradio: fix issue of dev reference count leakage in bpq_device_event() drm/vc4: Fix missing platform_unregister_drivers() call in vc4_drm_register() ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network tipc: fix the msg->req tlv len check in tipc_nl_compat_name_table_dump_header dmaengine: mv_xor_v2: Fix a resource leak in mv_xor_v2_remove() drivers: net: xgene: disable napi when register irq failed in xgene_enet_open() net: cxgb3_main: disable napi when bind qsets failed in cxgb_up() ethernet: s2io: disable napi when start nic failed in s2io_card_up() net: mv643xx_eth: disable napi when init rxq or txq failed in mv643xx_eth_open() net: macvlan: fix memory leaks of macvlan_common_newlink arm64: efi: Fix handling of misaligned runtime regions and drop warning ALSA: hda: fix potential memleak in 'add_widget_node' ALSA: usb-audio: Add quirk entry for M-Audio Micro nilfs2: fix deadlock in nilfs_count_free_blocks() drm/i915/dmabuf: fix sg_table handling in map_dma_buf platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi btrfs: selftests: fix wrong error check in btrfs_free_dummy_root() udf: Fix a slab-out-of-bounds write bug in udf_find_entry() cert host
[Kernel-packages] [Bug 2003588] Re: CVE 2022-4378 fix is in Kinetic, needed on Lunar
** Information type changed from Private Security to Public Security -- 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/2003588 Title: CVE 2022-4378 fix is in Kinetic, needed on Lunar Status in linux package in Ubuntu: New Bug description: This and many other CVE's are still unfixed on Lunar. No sign of a tracking bug on Lunar Is there a reason the Kinetic kernel can't be pushed to lunar? Priority is high: https://ubuntu.com/security/CVE-2022-4378 Can the lunar livecd automatically get all linux package updates when they hit kinetic? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003588] Re: CVE 2022-4378 fix is in Kinetic, needed on Lunar
Hello Charles, the development release isn't intended for production use; a lot of the things common to security updates in supported releases just won't be present for the development release. It'll eventually get a new kernel package based on a new upstream series and we'll address whatever remains to be fixed nearer to release. You can of course try to use the kinetic kernels on your own systems; the pull-lp-debs command from the ubuntu-dev-tools package might be more convenient than looking up URLs on launchpad manually or trying to manage installing the kinetic repositories on your lunar system. Thanks ** Changed in: linux (Ubuntu) Status: New => Won't Fix -- 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/2003588 Title: CVE 2022-4378 fix is in Kinetic, needed on Lunar Status in linux package in Ubuntu: Won't Fix Bug description: This and many other CVE's are still unfixed on Lunar. No sign of a tracking bug on Lunar Is there a reason the Kinetic kernel can't be pushed to lunar? Priority is high: https://ubuntu.com/security/CVE-2022-4378 Can the lunar livecd automatically get all linux package updates when they hit kinetic? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
