[Kernel-packages] [Bug 2007321] Re: Kernel 5.15.0-60-generic kernel panic
** 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/2007321 Title: Kernel 5.15.0-60-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: 525m CUDA version: 12.0). My OS is Ubuntu 22.04.1. I tried updating by sudo apt update and upgrade. Kernel 5.15.0-60-generic has a kernel panic. The only option was to switch to a different kernel, i.e., Kernel 5.15.0-56-generic, under Advanced Options while booting. Previously, the same issue existed with Kernels 5.15.0-57-generic and 5.15.0-58-generic. Please let me know your thoughts on this issue and fixes if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)
Also fixed in linux-hwe-5.19 for Ubuntu 22.04 per comment #104. So I guess you just need: sudo apt install linux-generic-hwe-22.04-edge ** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Fix Released ** Changed in: linux-hwe-5.19 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb 00000000f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed)
Sounds like the kernel error message is harmless: https://lists.freedesktop.org/archives/dri-devel/2022-February/342776.html So just correlated with other USB-C dock issues, not the cause of them. -- 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/1970495 Title: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed) Status in GNOME Shell: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: 1. Problem DOES appear on Lenovo T470s (Intel). 2. Problem DOES appear on Lenovo T14 Gen2 (AMD). 3. Problem does NOT appear on either of the above *when in the Live Installer*. I specifically checked that my dock behaved well under the Live Installer before deciding to move my workstations to Jammy. Upon logging into a fresh Jammy install, I found the following problem behavior: When the dock is plugged in, the built-in display freezes and the dock-attached displays power up but never render anything (ie, they stay black). Unplugging the USB-C cable gets mouse/keyboard response back on the built-in display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 18:32:35 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1970495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000299] Re: Fix W6400 hang after resume of S3 stress
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000299 Title: Fix W6400 hang after resume of S3 stress Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] amdgpu hang when stress S3 on AMD W6400 GPU. [Fix] Add a WA to manually adjust strobe calculation using FCLK restrict. [Test] Suspend AMD W6400 for 40 times, it works fine. [Where problems could occur] Low risk, upstream fix. It may cause AMD GPU hang. The patch is in 5.16, only Jammy kernel needs it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007180] Re: 3rd Monitor detected but not activated (two connected via USB-C dock)
Plugging one of the monitors into the laptop directly might be a workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007180 Title: 3rd Monitor detected but not activated (two connected via USB-C dock) Status in linux package in Ubuntu: Incomplete Bug description: I have 2 external monitors, both external monitors are detected but the display is allowing only 1 to be activated. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 01:42:11 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-05 (344 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-10 (156 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007180] Re: 3rd Monitor detected but not activated (two connected via USB-C dock)
I don't know the capabilities of the USB-C port you're using, or the model of dock you're using. But I would not be surprised if this is some bottleneck whereby the combination of this particular USB-C port and this particular dock do not have enough bandwidth to drive two 3440x1440 monitors at the same time. Maybe it works on Windows due to better bandwidth management or just because this is a Linux bug that we haven't narrowed down yet. -- 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/2007180 Title: 3rd Monitor detected but not activated (two connected via USB-C dock) Status in linux package in Ubuntu: Incomplete Bug description: I have 2 external monitors, both external monitors are detected but the display is allowing only 1 to be activated. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 01:42:11 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-05 (344 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-10 (156 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
** Tags added: oem-priority originate-from-1998757 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Status in linux-oem-6.0 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Confirmed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Confirmed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Confirmed Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007180] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2007180 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007180 Title: 3rd Monitor detected but not activated (two connected via USB-C dock) Status in linux package in Ubuntu: Incomplete Bug description: I have 2 external monitors, both external monitors are detected but the display is allowing only 1 to be activated. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 01:42:11 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-05 (344 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-10 (156 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006955] Re: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works)
If 'Additional Drivers' doesn't mention them then try: ubuntu-drivers list although I expect that should be the same. Sorry, I'm out of ideas at that point. Since this bug was caused by software from outside of Ubuntu it will be marked as Invalid, but can still be discussed here. ** Package changed: linux (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006955 Title: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works) Status in Ubuntu: Invalid Bug description: I have 3 monitors, but since very recently (yesterday or so), only 1 of them seems to be detected. In the Settings app, under "Screen Display", I used to have a place where I can move my monitors relatively to each other, and adjust each of their settings. Now, I no longer have the monitor drag-and-drop zone, I only have one detected "Unknown display", fixed at 1920x1080 77.00 Hz (physically, it's a 1920x1080 144Hz) and I cannot change any setting except orientation, scaling, and fractional scaling. The bug started happening just when the kernel was auto-updated to 5.15.0-60-generic from 5.15.0-58-generic. `uname -a` reports: `Linux user-desktop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux`. When I reboot with 5.15.0-58-generic, all of my 3 displays are detected and working fine. I also noticed the same problem happened when I installed 5.15.0-58-lowlatency. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 10 11:00:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-57-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:3816] InstallationDate: Installed on 2021-01-27 (743 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B550 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd08/13/2020:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2006955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007180] Re: 3rd Monitor detected but not activated
Thanks. This sounds like a kernel bug relating to Multi-Stream Transport (MST) over your USB-C dock. So I can only suggest two more ideas right now: * Avoid plugging the monitors into that dock; or * Experiment with newer kernel versions. ** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Summary changed: - 3rd Monitor detected but not activated + 3rd Monitor detected but not activated (two connected via USB-C dock) ** Tags added: mst -- 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/2007180 Title: 3rd Monitor detected but not activated (two connected via USB-C dock) Status in linux package in Ubuntu: New Bug description: I have 2 external monitors, both external monitors are detected but the display is allowing only 1 to be activated. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 01:42:11 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-05 (344 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-10 (156 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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]
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/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: 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] 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 2006517] Re: Bluetooth works on desktop but not on ubuntu core
Are you sure the function is lost? Looks like the Adv Monitor is running even the features callback returns an invalid value. Feb 07 23:50:34 ubuntu bluetoothd[1562]: src/advertising.c:read_adv_features_callback() Failed to read advertising features: Not Supported (0x0c) Feb 07 23:50:34 ubuntu bluetoothd[1562]: Adv Monitor Manager created with supported features:0x0001, enabled features:0x0001, max number of supported monitors:32, max number of supported patterns:16 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007180] [NEW] 3rd Monitor detected but not activated
You have been subscribed to a public bug: I have 2 external monitors, both external monitors are detected but the display is allowing only 1 to be activated. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 01:42:11 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-05 (344 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-10 (156 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hybrid i915 jammy multigpu multimonitor nvidia -- 3rd Monitor detected but not activated https://bugs.launchpad.net/bugs/2007180 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 2007331] [NEW] Fix HFP mSBC support on Realtek Bluetooth USB controller
Public bug reported: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: pulseaudio (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Affects: pulseaudio (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Affects: pulseaudio (Ubuntu Kinetic) Importance: Medium Status: Confirmed ** Affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Affects: pulseaudio (Ubuntu Lunar) Importance: Medium Status: Confirmed ** Package changed: linux (Ubuntu) => linux-oem-6.1 (Ubuntu) ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Low => Medium ** Also affects: pulseaudio (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: pulseaudio (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu Jammy) Status: New => Confirmed ** Changed in: pulseaudio (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu Kinetic) Status: New => Confirmed ** Changed in: pulseaudio (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu Lunar) 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/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Status in linux-oem-6.0 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Confirmed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Confirmed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Confirmed Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected
[Kernel-packages] [Bug 2007328] [NEW] [ADL-N] HDMI port through type-c stops working after reboot
Public bug reported: [Impact] HDMI port through type-c stops working after reboot [Fix] adding the correct ddc pin mapping and eliminate the warn log about ownership. [Test Case] 1.Connected the external monitor to the onboard HDMI port which comes from type-c. 2.Boot OS. 3.Check the monitor to see if [Where problems could occur] Low, the fix limits to adl-n (adl-p) series. ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2007328 Title: [ADL-N] HDMI port through type-c stops working after reboot Status in linux-intel-iotg package in Ubuntu: New Bug description: [Impact] HDMI port through type-c stops working after reboot [Fix] adding the correct ddc pin mapping and eliminate the warn log about ownership. [Test Case] 1.Connected the external monitor to the onboard HDMI port which comes from type-c. 2.Boot OS. 3.Check the monitor to see if [Where problems could occur] Low, the fix limits to adl-n (adl-p) series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2007328/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws-5.15/5.15.0-1031.35~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.15 (5.15.0-1031.35~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-aws-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency-hwe-5.15/5.15.0.66.73~20.04.24)
All autopkgtests for the newly accepted linux-meta-lowlatency-hwe-5.15 (5.15.0.66.73~20.04.24) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-lowlatency-hwe-5.15/5.15.0-66.73~20.04.1 (arm64) dpdk/19.11.13-0ubuntu0.20.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-lowlatency-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.15/5.15.0-1031.35~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.15 (5.15.0-1031.35~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-aws-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007321] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2007321 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007321 Title: Kernel 5.15.0-60-generic kernel panic Status in linux package in Ubuntu: Incomplete 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: 525m CUDA version: 12.0). My OS is Ubuntu 22.04.1. I tried updating by sudo apt update and upgrade. Kernel 5.15.0-60-generic has a kernel panic. The only option was to switch to a different kernel, i.e., Kernel 5.15.0-56-generic, under Advanced Options while booting. Previously, the same issue existed with Kernels 5.15.0-57-generic and 5.15.0-58-generic. Please let me know your thoughts on this issue and fixes if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007321] [NEW] Kernel 5.15.0-60-generic kernel panic
Public bug reported: I have a GPU workstation with AMD Ryzen™ Threadripper 2950X Processor, ASUS Zenith Extreme, and four Nvidia GeForce RTX 2080Ti GPUs (Nvidia driver: 525m CUDA version: 12.0). My OS is Ubuntu 22.04.1. I tried updating by sudo apt update and upgrade. Kernel 5.15.0-60-generic has a kernel panic. The only option was to switch to a different kernel, i.e., Kernel 5.15.0-56-generic, under Advanced Options while booting. Previously, the same issue existed with Kernels 5.15.0-57-generic and 5.15.0-58-generic. Please let me know your thoughts on this issue and fixes if possible. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug ** Tags added: kernel-bug ** Tags removed: kernel-bug ** Tags added: kernel-panic ** Tags removed: kernel-panic ** Tags added: kernel- ** Tags removed: kernel- ** Tags added: kernel-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/2007321 Title: Kernel 5.15.0-60-generic kernel panic Status in linux package in Ubuntu: New 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: 525m CUDA version: 12.0). My OS is Ubuntu 22.04.1. I tried updating by sudo apt update and upgrade. Kernel 5.15.0-60-generic has a kernel panic. The only option was to switch to a different kernel, i.e., Kernel 5.15.0-56-generic, under Advanced Options while booting. Previously, the same issue existed with Kernels 5.15.0-57-generic and 5.15.0-58-generic. Please let me know your thoughts on this issue and fixes if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007050] Re: Microsoft Surface keyboard not available during initrd
Thanks to oerheks for pointing me to a related (though AMD there) report at https://github.com/linux-surface/linux-surface/issues/839#issuecomment-1140287888 Placing the following in /etc/initramfs-tools/modules #-- Starts here -- surface_hid_core surface_hid surface_aggregator_registry surface_aggregator pinctrl_tigerlake 8250_dw #-- Ends here -- then running sudo update-initramfs -c -k $(uname -r) and finally rebooting works around it for me. It appears that whatever detects the modules to be included in the (default) "MOST" set when generating an initrd will need updating. (It may be possible to reduce the above list of modules to specifically include in the initrd can be reduced, yet - let me know if you want me to work this out.) ** Bug watch added: github.com/linux-surface/linux-surface/issues #839 https://github.com/linux-surface/linux-surface/issues/839 ** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu) ** Summary changed: - Microsoft Surface keyboard not available during initrd + Check for Microsoft Surface keyboard modules when generating initrd -- 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/2007050 Title: Check for Microsoft Surface keyboard modules when generating initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. -- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3 libpam-modules-bin 1.4.0-11ubuntu2.3 libpam0g 1.4.0-11ubuntu2.3 libpcre2-8-0 10.39-3ubuntu0.1 libpng16-16 1.6.37-3build5 libseccomp2 2.5.3-2ubuntu2 libselinux1 3.3-1build2 libsemanage-common 3.3-1build2 libsemanage2 3.3-1build2 libsepol2 3.3-1build1 libsmartcols1 2.37.2-4ubuntu3 libssl3 3.0.2-0ubuntu1.8 libstdc++6 12.1.0-2ubuntu1~22.04 libsystemd0 249.11-0ubuntu3.6 libtasn1-6 4.18.0-4build1 libtext-charwidth-perl 0.04-10build3 libtext-iconv-perl 1.7-7build3 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.3-2 libtirpc-common 1.3.2-2ubuntu0.1 libtirpc3 1.3.2-2ubuntu0.1 libudev1 249.11-0ubuntu3.6 libunistring2 1.0-1 libuuid1 2.37.2-4ubuntu3 libxxhash0 0.8.1-1 libzstd1 1.4.8+dfsg-3build1 linux-base 4.5ubuntu9
[Kernel-packages] [Bug 1986717] Re: [SRU]Update ice driver to support E823 devices
This has been Acked on the kernel team mailing list https://lists.ubuntu.com/archives/kernel-team/2023-February/137062.html When this hits proposed please verify it works. ** Tags added: verification-needed-focal -- 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/1986717 Title: [SRU]Update ice driver to support E823 devices Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: SRU Justification: [Impact] Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. [Fix] e36aeec0f4e5 ice: add support for E823 devices 5d9e618cbb54 ice: Add device ids for E822 devices [Testcase] Load ice driver on system with E823 device present and ensure the device is seen by the system [Where problems could occur] The regression risk is low These patches did not cherry pick cleanly I had to make some minor changes. Other Info: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e823_intel_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
@Daniel, Those denials should be resolved by this PR (https://github.com/snapcore/snapd/pull/12496). The problem is if we run this snap in devmode, skipping over apparmor entirely, the root problem still exists. Namely, bluetooth does not function on the device. With the relevant interface changes made and the snap installed fully confined on the two devices Alex mentions above, the snap in question works fine. This indicates to me that this is more a problem with something in the pc-kernel snap. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006942] Re: With linux kernel 5.19.0-31 amd_pstate is not used, while with 5.19.0-29 and lower does
** 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-signed in Ubuntu. https://bugs.launchpad.net/bugs/2006942 Title: With linux kernel 5.19.0-31 amd_pstate is not used, while with 5.19.0-29 and lower does Status in linux package in Ubuntu: Confirmed Status in linux-signed package in Ubuntu: New Bug description: After upgrading to 5.19.0-31 (two of my systems) CPU driver changes to acpi-cpufreq. instead of amd_pstate. This causes cpu to keep higher frequency and increased consumption. ``` root@zeus:/sys/devices/system/cpu/cpufreq/policy0# ls -l total 0 -r--r--r-- 1 root root 4096 Feb 10 13:27 affected_cpus -r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_highest_perf -r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_lowest_nonlinear_freq -r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_max_freq -r--r--r-- 1 root root 4096 Feb 10 12:54 cpuinfo_max_freq -r--r--r-- 1 root root 4096 Feb 10 13:27 cpuinfo_min_freq -r--r--r-- 1 root root 4096 Feb 10 13:27 cpuinfo_transition_latency -r--r--r-- 1 root root 4096 Feb 10 13:27 related_cpus -r--r--r-- 1 root root 4096 Feb 10 12:54 scaling_available_governors -r--r--r-- 1 root root 4096 Feb 10 13:27 scaling_cur_freq -r--r--r-- 1 root root 4096 Feb 10 13:27 scaling_driver -rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_governor -rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_max_freq -rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_min_freq -rw-r--r-- 1 root root 4096 Feb 10 13:28 scaling_setspeed root@zeus:/sys/devices/system/cpu/cpufreq/policy0# ``` with newer kernel also policy files for amd_pstate Tried it on 2 Asus PN51-S1 systems with AMD Ryzen 7 5700U I am currently staying at 5.19.0-29 as it is working better. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-31-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-11-18 (85 days ago) InstallationMedia: Ubuntu-Server 22.10 "Kinetic Kudu" - Release amd64 (20221019) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-S1 Package: linux-signed (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic root=/dev/mapper/system-root ro ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.19.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/10/2022 dmi.bios.release: 1.12 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0112 dmi.board.asset.tag: Default string dmi.board.name: PN51-S1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0112:bd08/10/2022:br1.12:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-S1:pvr0112:rvnASUSTeKCOMPUTERINC.:rnPN51-S1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-S1 dmi.product.version: 0112 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Re: linux-tools-common: bpftool wrapper causes build failure for xdp-tools
** Also affects: xdp-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007306] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007306 Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools-common 5.15.0-1023.28~20.04.1 Status in linux package in Ubuntu: Confirmed Bug description: Ran into this on Ubuntu 20.04 while running "sudo apt install linux- tools-generic". ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 AptOrdering: linux-tools-common:amd64: Install linux-tools-5.4.0-139:amd64: Install linux-tools-5.4.0-139-generic:amd64: Install linux-tools-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evan 2001 F pulseaudio /dev/snd/controlC2: evan 2001 F pulseaudio /dev/snd/pcmC0D0p: evan 2001 F...m pulseaudio /dev/snd/controlC1: evan 2001 F pulseaudio CasperMD5CheckResult: skip Date: Tue Feb 14 13:45:48 2023 DpkgTerminalLog: Preparing to unpack .../linux-tools-common_5.4.0-139.156_all.deb ... Unpacking linux-tools-common (5.4.0-139.156) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-common_5.4.0-139.156_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools-common 5.15.0-1023.28~20.04.1 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools-common 5.15.0-1023.28~20.04.1 InstallationDate: Installed on 2022-12-08 (68 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: LENOVO 30B4S28S0F ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=4244e522-14d4-4ec0-aa65-59cc1f57ff19 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 RfKill: SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools-common 5.15.0-1023.28~20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2017 dmi.bios.release: 0.38 dmi.bios.vendor: LENOVO dmi.bios.version: S00KT38A dmi.board.name: 102F dmi.board.vendor: LENOVO dmi.board.version: SBB0J05441 WIN 3305049314784 dmi.chassis.asset.tag: MJ05C51F dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 16.19 dmi.modalias: dmi:bvnLENOVO:bvrS00KT38A:bd03/02/2017:br0.38:efr16.19:svnLENOVO:pn30B4S28S0F:pvrThinkStationP510:rvnLENOVO:rn102F:rvrSBB0J05441WIN3305049314784:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_30B4_BU_LENOVO_FM_ThinkStationP510: dmi.product.family: ThinkStation P510 dmi.product.name: 30B4S28S0F dmi.product.sku: LENOVO_MT_30B4_BU_LENOVO_FM_ThinkStation P510 dmi.product.version: ThinkStation P510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647168/+files/UdevDb.txt ** Description changed: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 - --- + + For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. + --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: - /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M - /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=C.UTF-8 + TERM=xterm-256color + PATH=(custom, no user) + LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: - linux-restricted-modules-5.4.0-139-generic N/A - linux-backports-modules-5.4.0-139-generic N/A - linux-firmware N/A + linux-restricted-modules-5.4.0-139-generic N/A + linux-backports-modules-5.4.0-139-generic N/A + linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: - + dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU -- 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/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls:
[Kernel-packages] [Bug 2007308] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647165/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] NonfreeKernelModules.txt
apport information ** Attachment added: "NonfreeKernelModules.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647163/+files/NonfreeKernelModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647167/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647166/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647164/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647162/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647161/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647160/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647159/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647158/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647157/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] [NEW] linux-tools-common: bpftool wrapper causes build failure for xdp-tools
Public bug reported: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU ** Affects: launchpad Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: xdp-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected lunar package-from-proposed uec-images ** Also affects: launchpad Importance: Undecided Status: New ** Tags added: apport-collected lunar package-from-proposed uec-images ** Description changed: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 + --- + ProblemType: Bug + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.24.0-0ubuntu2 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + CRDA: N/A + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 23.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Lsusb-t: + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M + MachineType: QEMU Standard PC (Q35 + ICH9, 2009) + Package: linux-tools-common 6.1.0-14.14 + PackageArchitecture: all + PciMultimedia: + +
[Kernel-packages] [Bug 2007306] [NEW] package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools
Public bug reported: Ran into this on Ubuntu 20.04 while running "sudo apt install linux- tools-generic". ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 AptOrdering: linux-tools-common:amd64: Install linux-tools-5.4.0-139:amd64: Install linux-tools-5.4.0-139-generic:amd64: Install linux-tools-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evan 2001 F pulseaudio /dev/snd/controlC2: evan 2001 F pulseaudio /dev/snd/pcmC0D0p: evan 2001 F...m pulseaudio /dev/snd/controlC1: evan 2001 F pulseaudio CasperMD5CheckResult: skip Date: Tue Feb 14 13:45:48 2023 DpkgTerminalLog: Preparing to unpack .../linux-tools-common_5.4.0-139.156_all.deb ... Unpacking linux-tools-common (5.4.0-139.156) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-common_5.4.0-139.156_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools-common 5.15.0-1023.28~20.04.1 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools-common 5.15.0-1023.28~20.04.1 InstallationDate: Installed on 2022-12-08 (68 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: LENOVO 30B4S28S0F ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=4244e522-14d4-4ec0-aa65-59cc1f57ff19 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 RfKill: SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools-common 5.15.0-1023.28~20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2017 dmi.bios.release: 0.38 dmi.bios.vendor: LENOVO dmi.bios.version: S00KT38A dmi.board.name: 102F dmi.board.vendor: LENOVO dmi.board.version: SBB0J05441 WIN 3305049314784 dmi.chassis.asset.tag: MJ05C51F dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 16.19 dmi.modalias: dmi:bvnLENOVO:bvrS00KT38A:bd03/02/2017:br0.38:efr16.19:svnLENOVO:pn30B4S28S0F:pvrThinkStationP510:rvnLENOVO:rn102F:rvrSBB0J05441WIN3305049314784:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_30B4_BU_LENOVO_FM_ThinkStationP510: dmi.product.family: ThinkStation P510 dmi.product.name: 30B4S28S0F dmi.product.sku: LENOVO_MT_30B4_BU_LENOVO_FM_ThinkStation P510 dmi.product.version: ThinkStation P510 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/2007306 Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools-common 5.15.0-1023.28~20.04.1 Status in linux package in Ubuntu: New Bug description: Ran into this on Ubuntu 20.04 while running "sudo apt install linux- tools-generic". ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 AptOrdering: linux-tools-common:amd64: Install linux-tools-5.4.0-139:amd64: Install linux-tools-5.4.0-139-generic:amd64: Install linux-tools-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evan 2001 F pulseaudio /dev/snd/controlC2: evan 2001 F pulseaudio /dev/snd/pcmC0D0p: evan 2001 F...m pulseaudio /dev/snd/controlC1: evan 2001 F pulseaudio CasperMD5CheckResult: skip Date: Tue Feb 14 13:45:48 2023 DpkgTerminalLog: Preparing to unpack .../linux-tools-common_5.4.0-139.156_all.deb ... Unpacking linux-tools-common (5.4.0-139.156) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-common_5.4.0-139.156_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools-common 5.15.0-1023.28~20.04.1 ErrorMessage: trying to overwrite
[Kernel-packages] [Bug 2007286] Re: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed
Actually let me reassign to Linux and mark 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/2007286 Title: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed Status in linux package in Ubuntu: Incomplete Bug description: corrado@corrado-x-kinetic:~$ ls /lib/modules 5.19.0-23-generic 5.19.0-28-generic 5.19.0-29-generic 5.19.0-31-generic corrado@corrado-x-kinetic:~$ ls /boot config-5.19.0-29-generic memtest86+.elf config-5.19.0-31-generic memtest86+_multiboot.bin efi System.map-5.19.0-29-generic grub System.map-5.19.0-31-generic initrd.imgvmlinuz initrd.img-5.19.0-29-generic vmlinuz-5.19.0-29-generic initrd.img-5.19.0-31-generic vmlinuz-5.19.0-31-generic initrd.img.oldvmlinuz.old memtest86+.bin corrado@corrado-x-kinetic:~$ see also https://discourse.ubuntu.com/t/ubuntu-does-not-clean-out-old-kernel-module-files-in-lib-modules-when-old-kernels-are-removed/33906 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apt 2.5.3 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 16:23:49 2023 InstallationDate: Installed on 2022-11-28 (77 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007286] Re: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed
There can be many reasons why files remain. Did you purge the packages for those Linux versions? Did you do any dkms modules. This is not a bug in apt, apt is not responsible for those files. ** Changed in: apt (Ubuntu) Status: New => Invalid ** Package changed: apt (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Invalid => 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/2007286 Title: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed Status in linux package in Ubuntu: Incomplete Bug description: corrado@corrado-x-kinetic:~$ ls /lib/modules 5.19.0-23-generic 5.19.0-28-generic 5.19.0-29-generic 5.19.0-31-generic corrado@corrado-x-kinetic:~$ ls /boot config-5.19.0-29-generic memtest86+.elf config-5.19.0-31-generic memtest86+_multiboot.bin efi System.map-5.19.0-29-generic grub System.map-5.19.0-31-generic initrd.imgvmlinuz initrd.img-5.19.0-29-generic vmlinuz-5.19.0-29-generic initrd.img-5.19.0-31-generic vmlinuz-5.19.0-31-generic initrd.img.oldvmlinuz.old memtest86+.bin corrado@corrado-x-kinetic:~$ see also https://discourse.ubuntu.com/t/ubuntu-does-not-clean-out-old-kernel-module-files-in-lib-modules-when-old-kernels-are-removed/33906 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apt 2.5.3 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 16:23:49 2023 InstallationDate: Installed on 2022-11-28 (77 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007286] [NEW] Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed
You have been subscribed to a public bug: corrado@corrado-x-kinetic:~$ ls /lib/modules 5.19.0-23-generic 5.19.0-28-generic 5.19.0-29-generic 5.19.0-31-generic corrado@corrado-x-kinetic:~$ ls /boot config-5.19.0-29-generic memtest86+.elf config-5.19.0-31-generic memtest86+_multiboot.bin efi System.map-5.19.0-29-generic grub System.map-5.19.0-31-generic initrd.imgvmlinuz initrd.img-5.19.0-29-generic vmlinuz-5.19.0-29-generic initrd.img-5.19.0-31-generic vmlinuz-5.19.0-31-generic initrd.img.oldvmlinuz.old memtest86+.bin corrado@corrado-x-kinetic:~$ see also https://discourse.ubuntu.com/t/ubuntu-does-not-clean-out-old-kernel-module-files-in-lib-modules-when-old-kernels-are-removed/33906 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apt 2.5.3 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 16:23:49 2023 InstallationDate: Installed on 2022-11-28 (77 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug kinetic wayland-session -- Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed https://bugs.launchpad.net/bugs/2007286 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 2006895] Re: kernel 5.15.0-60-generic out of memory on boot
It seems that my bug is a duplicate of https://bugs.launchpad.net/oem-priority/+bug/1842320 . I too have nvidia-525 drivers installed. Especially, I'm referring to https://bugs.launchpad.net/oem-priority/+bug/1842320/comments/156 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2006895 Title: kernel 5.15.0-60-generic out of memory on boot Status in linux-signed package in Ubuntu: New Bug description: Using kubuntu 22.04, and after a kernel update and after a reboot, the machine just spits out the "out of memory" message. The 5.15.0-58-generic works just fine. For what it's worth, I had the similar issue with the kernel prior to 58. Additionally, grub-efi-amd64-bin, grub-efi-amd64-signed, ubuntu-advantage-tools, update-notifier-common, software-properties-common and software-properties-qt updates are held back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2006895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914881] Re: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,
I have an HP Envy x360 15-ew0023dx with the same issue. Internal speaker sound doesn't work on 22.04 or 22.10. Also doesn't work when updating kernel to 6.1.11. I found someone that says they have a kernel patch for their model of HP Envy x360 15-ey0013dx. https://unix.stackexchange.com/a/730868 -- 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/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Status in linux package in Ubuntu: Confirmed Bug description: There is no sound output from the laptop internal speakers when running Ubuntu 20.10. This is a dual-boot system; - Booting Windows first and then rebooting to Ubuntu -> sound works fine - Booting Ubuntu first and then rebooting to Windows -> Windows identifies sound as not enables and runs its troubleshooter to enable it The card seems to be recognised OK (system sound settings report output device as Speaker - Tiger Lake-LP Smart Sound technology Audio Controller. VU meters etc all appear as if sound is playing, but no sound. Headphone socket works perfectly. Similar bug reports for different laptops in the HP x360 series suggest this is a pinning problem and that the extract below from the boot logs may support this. lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 extract from journalctl -b kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:> kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 kernel: snd_hda_codec_realtek ehdaudio0D0:inputs: kernel: snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 20:48:52 2021 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1481 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic
[Kernel-packages] [Bug 2007290] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2007290 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Focal) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007290 Title: ubuntu_kernel_selftests.ftrace:ftracetest new failures in focal -143/144 compared to -139 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: The following tests are failing in focal -143/144 11:12:47 DEBUG| [stdout] # [22] ftrace - test for function event triggers[FAIL] 11:15:51 DEBUG| [stdout] # [50] Meta-selftest[FAIL] 11:19:39 DEBUG| [stdout] # [82] (instance) ftrace - test for function event triggers[FAIL] This seems to be a regression from -139. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2007290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007290] Re: ubuntu_kernel_selftests.ftrace:ftracetest new failures in focal -143/144 compared to -139
** Tags added: sru-20230130 -- 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/2007290 Title: ubuntu_kernel_selftests.ftrace:ftracetest new failures in focal -143/144 compared to -139 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: The following tests are failing in focal -143/144 11:12:47 DEBUG| [stdout] # [22] ftrace - test for function event triggers[FAIL] 11:15:51 DEBUG| [stdout] # [50] Meta-selftest[FAIL] 11:19:39 DEBUG| [stdout] # [82] (instance) ftrace - test for function event triggers[FAIL] This seems to be a regression from -139. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2007290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007290] [NEW] ubuntu_kernel_selftests.ftrace:ftracetest new failures in focal -143/144 compared to -139
Public bug reported: The following tests are failing in focal -143/144 11:12:47 DEBUG| [stdout] # [22] ftrace - test for function event triggers[FAIL] 11:15:51 DEBUG| [stdout] # [50] Meta-selftest[FAIL] 11:19:39 DEBUG| [stdout] # [82] (instance) ftrace - test for function event triggers[FAIL] This seems to be a regression from -139. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Tags: sru-20230130 ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007290 Title: ubuntu_kernel_selftests.ftrace:ftracetest new failures in focal -143/144 compared to -139 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: The following tests are failing in focal -143/144 11:12:47 DEBUG| [stdout] # [22] ftrace - test for function event triggers[FAIL] 11:15:51 DEBUG| [stdout] # [50] Meta-selftest[FAIL] 11:19:39 DEBUG| [stdout] # [82] (instance) ftrace - test for function event triggers[FAIL] This seems to be a regression from -139. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2007290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002834] Re: Network bridge issue after updating kernel to 5.4.0-137
looks like the missing cherry picked xen/netback patches have only been merged 13 days ago. https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/log/?h=master-next=grep=netback vs https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=v5.15.88=grep=netback -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2002834 Title: Network bridge issue after updating kernel to 5.4.0-137 Status in linux-meta package in Ubuntu: Confirmed Bug description: Hello, After updating the kernel from 5.4.0-136 to 5.4.0-137 network bridge are not working any more. I can see the bridge with "ip add show" or "brctl show". Network is up and I can reach the full network from the host through the bridge. VM on the host can not reach network or host and host can not reach the VM through the bridge. We have bonded interface used in the bridge and one bridge without IP and one with an IP. DHCP is off on booth bridge. Downgrading the kernel to 5.4.136 (Ubuntu 5.4.0-136.153-generic 5.4.218) seem to work fine. Thank you for your help. Details Description: Ubuntu 20.04.5 LTS Release: 20.04 Not working version => Ubuntu 5.4.0-137.154-generic 5.4.218 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2002834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-gcp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2003816 Title: Regression in ext4 during online resize Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
Same problema here! I bougth a new Acer Nitro 5, and this problem is very boring. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ignis_ADH dmi.board.vendor: ADL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
Kinetic debdiff ** Patch added: "kinetic.debdiff" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644/+attachment/5647087/+files/kinetic.debdiff -- 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/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in linux source package in Bionic: Incomplete Status in lttng-modules source package in Bionic: In Progress Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: New Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: previous definition of ‘trace_jbd2_run_stats’ was here 778 21:14:39 DEBUG| [stdout] 243 | static inline void trace_##name(proto) \ 779 21:14:39 DEBUG| [stdout] | ^~ 780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: in expansion of macro ‘__DECLARE_TRACE’ 781 21:14:39 DEBUG| [stdout] 406 | __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
Jammy debdiff ** Patch added: "jammy.debdiff" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644/+attachment/5647086/+files/jammy.debdiff -- 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/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in linux source package in Bionic: Incomplete Status in lttng-modules source package in Bionic: In Progress Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: New Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: previous definition of ‘trace_jbd2_run_stats’ was here 778 21:14:39 DEBUG| [stdout] 243 | static inline void trace_##name(proto) \ 779 21:14:39 DEBUG| [stdout] | ^~ 780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: in expansion of macro ‘__DECLARE_TRACE’ 781 21:14:39 DEBUG| [stdout] 406 | __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \
[Kernel-packages] [Bug 2006955] Re: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works)
`sudo modprobe amdgpu` and my problem seems to be fixed. Indeed I looked in /etc/modprobe.d, and found a file called `blacklist- amdgpu.conf` containing just `blacklist amdgpu`. I removed it. Thanks for helping, and sorry for the erroneous report. I needed to install AMD's driver because Blender requires it to allow me to render with my GPU. Specifically, it says it needs the AMD driver version 22.10 or newer. I do admit I'm not the most experienced user with drivers, so I may have installed more than necessary. I followed the instructions at https://docs.blender.org/manual/en/latest/troubleshooting/gpu/linux/amd.html. Is there a better way to install them? -- 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/2006955 Title: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works) Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors, but since very recently (yesterday or so), only 1 of them seems to be detected. In the Settings app, under "Screen Display", I used to have a place where I can move my monitors relatively to each other, and adjust each of their settings. Now, I no longer have the monitor drag-and-drop zone, I only have one detected "Unknown display", fixed at 1920x1080 77.00 Hz (physically, it's a 1920x1080 144Hz) and I cannot change any setting except orientation, scaling, and fractional scaling. The bug started happening just when the kernel was auto-updated to 5.15.0-60-generic from 5.15.0-58-generic. `uname -a` reports: `Linux user-desktop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux`. When I reboot with 5.15.0-58-generic, all of my 3 displays are detected and working fine. I also noticed the same problem happened when I installed 5.15.0-58-lowlatency. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 10 11:00:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-57-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:3816] InstallationDate: Installed on 2021-01-27 (743 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B550 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd08/13/2020:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
@roxana for the new upstream version backports, the debdiff is normally provided against the version that is being backported e.g. relative 2.13.8-1 Also when doing backport / any ubuntu change, the version string must include ubuntu in it, so something like ~ubuntu22.10.0 is best. -- 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/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in linux source package in Bionic: Incomplete Status in lttng-modules source package in Bionic: In Progress Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: New Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: previous definition of ‘trace_jbd2_run_stats’ was here 778 21:14:39 DEBUG| [stdout] 243 | static inline void trace_##name(proto) \ 779 21:14:39 DEBUG| [stdout] | ^~ 780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: in expansion
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
$ dput ubuntu lttng-modules_2.10.8-1ubuntu2~18.04.5_source.changes D: Setting host argument. Checking signature on .changes gpg: /tmp/lttng-modules_2.10.8-1ubuntu2~18.04.5_source.changes: Valid signature from 9B8EC849D5EF70ED Checking signature on .dsc gpg: /tmp/lttng-modules_2.10.8-1ubuntu2~18.04.5.dsc: Valid signature from 9B8EC849D5EF70ED Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading lttng-modules_2.10.8-1ubuntu2~18.04.5.dsc: done. Uploading lttng-modules_2.10.8-1ubuntu2~18.04.5.debian.tar.xz: done. Uploading lttng-modules_2.10.8-1ubuntu2~18.04.5_source.buildinfo: done. Uploading lttng-modules_2.10.8-1ubuntu2~18.04.5_source.changes: done. Successfully uploaded packages. ** Changed in: lttng-modules (Ubuntu Bionic) 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/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in linux source package in Bionic: Incomplete Status in lttng-modules source package in Bionic: In Progress Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: New Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
** Changed in: lttng-modules (Ubuntu) Status: Invalid => Fix Committed ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: Incomplete ** Also affects: lttng-modules (Ubuntu Lunar) Importance: Undecided Status: 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/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in linux source package in Bionic: Incomplete Status in lttng-modules source package in Bionic: New Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: New Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: previous definition of ‘trace_jbd2_run_stats’ was here 778 21:14:39 DEBUG| [stdout] 243 | static inline void trace_##name(proto) \ 779 21:14:39 DEBUG| [stdout] | ^~ 780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: in expansion of macro
[Kernel-packages] [Bug 1980484] Re: temporarily disable CONFIG_X86_KERNEL_IBT
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1980484 Title: temporarily disable CONFIG_X86_KERNEL_IBT Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in v4l2loopback package in Ubuntu: Fix Released Status in v4l2loopback source package in Jammy: Fix Committed Status in backport-iwlwifi-dkms source package in Kinetic: Fix Released Status in linux source package in Kinetic: Fix Released Status in v4l2loopback source package in Kinetic: Fix Released Bug description: Enabling IBT in the kernel is going to be problematic at the moment, because dkms' that have a precompiled binary need to be linked against non-IBT kernels and IBT kernels (see nvidia drivers for example). For this reason it's safer to keep IBT disabled at the moment, until all the kernels will have IBT enabled and the kernel modules / binaries will use the proper flags to generate IBT-compliant binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1980484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980484] Re: temporarily disable CONFIG_X86_KERNEL_IBT
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980484 Title: temporarily disable CONFIG_X86_KERNEL_IBT Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in v4l2loopback package in Ubuntu: Fix Released Status in v4l2loopback source package in Jammy: Fix Committed Status in backport-iwlwifi-dkms source package in Kinetic: Fix Released Status in linux source package in Kinetic: Fix Released Status in v4l2loopback source package in Kinetic: Fix Released Bug description: Enabling IBT in the kernel is going to be problematic at the moment, because dkms' that have a precompiled binary need to be linked against non-IBT kernels and IBT kernels (see nvidia drivers for example). For this reason it's safer to keep IBT disabled at the moment, until all the kernels will have IBT enabled and the kernel modules / binaries will use the proper flags to generate IBT-compliant binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1980484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
** Tags removed: sru-2023-01-30 ** Tags added: sru-20230130 -- 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/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Invalid Status in linux source package in Bionic: Incomplete Status in lttng-modules source package in Bionic: New Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: New Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: previous definition of ‘trace_jbd2_run_stats’ was here 778 21:14:39 DEBUG| [stdout] 243 | static inline void trace_##name(proto) \ 779 21:14:39 DEBUG| [stdout] | ^~ 780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: in expansion of macro ‘__DECLARE_TRACE’ 781 21:14:39 DEBUG| [stdout] 406 | __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \ 782 21:14:39 DEBUG| [stdout] | ^~~ 783 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:542:2: note: in expansion of macro ‘DECLARE_TRACE’ 784 21:14:39 DEBUG| [stdout] 542 |
[Kernel-packages] [Bug 1950952] Re: user_notification_addfd in seccomp/seccomp_bpf of ubuntu_kernel_selftests failed on F-OEM-5.14
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Won't Fix -- 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/1950952 Title: user_notification_addfd in seccomp/seccomp_bpf of ubuntu_kernel_selftests failed on F-OEM-5.14 Status in ubuntu-kernel-tests: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Won't Fix Bug description: Issue found on Focal OEM 5.14.0-1008.8 with node spitfire I think this is a new case, probably introduced by this commit: https://github.com/torvalds/linux/commit/e540ad97e73cefb41e93d0c06d0fe6a8620a77e0 Test log: # # RUN global.user_notification_addfd ... # # seccomp_bpf.c:3989:user_notification_addfd:Expected listener (18) == nextfd++ (9) # # user_notification_addfd: Test terminated by assertion # # FAIL global.user_notification_addfd # not ok 49 global.user_notification_addfd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968310] Re: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-hwe-5.17 (Ubuntu Jammy) Status: In Progress => Won't Fix -- 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/1968310 Title: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-hwe-5.17 source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-hwe-5.17 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In selftests: net: arp_ndisc_evict_nocarrier.sh, even all of the sub-tests from this script have passed, the overall test result is still a fail. # selftests: net: arp_ndisc_evict_nocarrier.sh # run arp_evict_nocarrier=1 test # ok # run arp_evict_nocarrier=0 test # ok # run all.arp_evict_nocarrier=0 test # ok # run ndisc_evict_nocarrier=1 test # ok # run ndisc_evict_nocarrier=0 test # ok # run all.ndisc_evict_nocarrier=0 test # ok not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255 This is caused by the cleanup() in the script, as it's trying to access a non-existing file. [Fix] * 9c4d7f45d6 selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier This patch can be cherry-picked into all affected kernels. [Test] Run the patched test and the test will pass. [Where problems could occur] Change limited to testing tools, no impact to real kernel function or test performances. [Original Bug Report] Issue found on Jammy OEM 5.17.0-1003.3 It looks like all the sub-tests has passed, but the final return value is not 0. Running 'make run_tests -C net TEST_PROGS=arp_ndisc_evict_nocarrier.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: arp_ndisc_evict_nocarrier.sh # run arp_evict_nocarrier=1 test # ok # run arp_evict_nocarrier=0 test # ok # run all.arp_evict_nocarrier=0 test # ok # run ndisc_evict_nocarrier=1 test # ok # run ndisc_evict_nocarrier=0 test # ok # run all.ndisc_evict_nocarrier=0 test # ok not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255 make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985901] Re: kernel hang when connecting monitor
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Triaged => Won't Fix -- 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/1985901 Title: kernel hang when connecting monitor Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Won't Fix Status in linux source package in Jammy: Triaged Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: When I connected the ThinkVision 24i monitor on ThinkPad L14, we found below issue. Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ... kernel:[ 77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! [Xorg:1829] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 50s! [Xorg:1829] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport ip_tables x_tables 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core realtek wmi video 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg Tainted: G L5.14.0-1048-oem #55-Ubuntu 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 08 00 00 45 8b 6d 00 12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 c5 66 90 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 EFLAGS: 0282 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 9ab39d00 RCX: 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX: RSI: 6741 RDI: 9ab39d00 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 9ab39d00 R09: 1140 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10: R11: 9ab389c9c400 R12: 6741 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13: R14: 0008 R15: 9ab389c9d400 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS: 7f9d97924a40() GS:9ab466e0() knlGS: 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS: 0010 DS: ES: CR0: 80050033 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 00010c878000 CR4: 00750ef0 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace: 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: amdgpu_device_rreg+0x17/0x20 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: amdgpu_cgs_read_register+0x14/0x20 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: dm_read_reg_func+0x3e/0xa0 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: dmub_srv_wait_for_idle+0x17/0x20 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3
[Kernel-packages] [Bug 1991664] Re: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler
v4l2loopback tested 0.12.7-2ubuntu2~22.04.1 to build on ga & hwe kernels in jammy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1991664 Title: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in ipu6-drivers package in Ubuntu: New Status in ivsc-driver package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in v4l2loopback package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in backport-iwlwifi-dkms source package in Jammy: New Status in dkms source package in Jammy: Fix Released Status in ipu6-drivers source package in Jammy: New Status in ivsc-driver source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in v4l2loopback source package in Jammy: Fix Committed Status in zfs-linux source package in Jammy: New Bug description: tl; dr this has proven to be a bit futile, and instead we went ahead with changing the default kernel makefiles to default to the correct toolchain and we have reverted hwe-5.19 kernel to use stock gcc on jammy for now. So the things described here are not strictly even needed in jammy for now. [ Impact ] * hwe-5.19 kernel has to be compiled with gcc-12+ for the new security kernel config options that have been enabled in that kernel (init zero structs). * dkms needs to be patched to attempt to use the same compiler as was used to build the kernel, specifically use gcc for v5.15 but gcc-12 for v5.19+ in jammy * dkms autopkgtests also need to be improved to ensure there are no false negatives when kernel has module under test already built-in at the same version. * because linux-headers packages in Ubuntu do not depend on a toolchain, and it is very hard to correctly depend on a native or cross-toolchain, add gcc-12 dependency in the dkms package. [ Test Plan ] * Retrigger dkms module test for a built-in package of the same version as already built into the kernel, for example zfs-linux dkms. It should pass. * Attempt to build dkms modules against v5.15 kernel and v5.19 kernel from proposed. dkms module should be built with gcc and gcc-12 respectively. [ Where problems could occur ] * New gcc-12 dependency on the dkms package may result in two compilers being installed in the Ubuntu Desktop Live image * New gcc-12 dependency may prevent automatic upgrade/installation of the dkms package update via unattended upgrades. [ Other Info ] * It is questionable for dkms to depend on any c-compiler, given that a module for a given kernel can really be built with the same toolchain and the same compiler features. * In debian, linux kernel packages ship and extra configuration file in the kernel headers, dkms uses said configuration file to use a matching compiler, and linux-headers packages depend on the toolchain used to build a given kernel. Maybe in the future Ubuntu could consider using the same packaging. * Some DKMS modules need further fixes to preserve and not loose the compiler setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1991664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991664] Re: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler
tl; dr this has proven to be a bit futile, and instead we went ahead with changing the default kernel makefiles to default to the correct toolchain and we have reverted hwe-5.19 kernel to use stock gcc on jammy for now. So the things described here are not strictly even needed in jammy for now. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy ** Description changed: + + tl; dr + + this has proven to be a bit futile, and instead we went ahead with + changing the default kernel makefiles to default to the correct + toolchain and we have reverted hwe-5.19 kernel to use stock gcc on jammy + for now. + + So the things described here are not strictly even needed in jammy for + now. + + [ Impact ] * hwe-5.19 kernel has to be compiled with gcc-12+ for the new security kernel config options that have been enabled in that kernel (init zero structs). * dkms needs to be patched to attempt to use the same compiler as was used to build the kernel, specifically use gcc for v5.15 but gcc-12 for v5.19+ in jammy * dkms autopkgtests also need to be improved to ensure there are no false negatives when kernel has module under test already built-in at the same version. * because linux-headers packages in Ubuntu do not depend on a toolchain, and it is very hard to correctly depend on a native or cross- toolchain, add gcc-12 dependency in the dkms package. [ Test Plan ] * Retrigger dkms module test for a built-in package of the same version as already built into the kernel, for example zfs-linux dkms. It should pass. * Attempt to build dkms modules against v5.15 kernel and v5.19 kernel from proposed. dkms module should be built with gcc and gcc-12 respectively. [ Where problems could occur ] * New gcc-12 dependency on the dkms package may result in two compilers being installed in the Ubuntu Desktop Live image * New gcc-12 dependency may prevent automatic upgrade/installation of the dkms package update via unattended upgrades. [ Other Info ] * It is questionable for dkms to depend on any c-compiler, given that a module for a given kernel can really be built with the same toolchain and the same compiler features. * In debian, linux kernel packages ship and extra configuration file in the kernel headers, dkms uses said configuration file to use a matching compiler, and linux-headers packages depend on the toolchain used to build a given kernel. Maybe in the future Ubuntu could consider using the same packaging. - * Some DKMS modules need further fixes to preserve and not loose the + * Some DKMS modules need further fixes to preserve and not loose the compiler setting -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1991664 Title: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in ipu6-drivers package in Ubuntu: New Status in ivsc-driver package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in v4l2loopback package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in backport-iwlwifi-dkms source package in Jammy: New Status in dkms source package in Jammy: Fix Released Status in ipu6-drivers source package in Jammy: New Status in ivsc-driver source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in v4l2loopback source package in Jammy: Fix Committed Status in zfs-linux source package in Jammy: New Bug description: tl; dr this has proven to be a bit futile, and instead we went ahead with changing the default kernel makefiles to default to the correct toolchain and we have reverted hwe-5.19 kernel to use stock gcc on jammy for now. So the things described here are not strictly even needed in jammy for now. [ Impact ] * hwe-5.19 kernel has to be compiled with gcc-12+ for the new security kernel config options that have been enabled in that kernel (init zero structs). * dkms needs to be patched to attempt to use the same compiler as was used to build the kernel, specifically use gcc for v5.15 but gcc-12 for v5.19+ in jammy * dkms autopkgtests also need to be improved to ensure there are no false negatives when kernel has module under test already built-in at the same version. * because linux-headers packages in Ubuntu do not depend on a toolchain, and it is very hard to correctly depend on a native or cross-toolchain, add gcc-12 dependency in the dkms package. [ Test Plan ] * Retrigger dkms module test for a built-in package of the same version as already built into the kernel, for
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
** Tags added: 5.4.0-144.161 ** Tags added: sru-2023-01-30 -- 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/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Invalid Status in linux source package in Bionic: Incomplete Status in lttng-modules source package in Bionic: New Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: New Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: previous definition of ‘trace_jbd2_run_stats’ was here 778 21:14:39 DEBUG| [stdout] 243 | static inline void trace_##name(proto) \ 779 21:14:39 DEBUG| [stdout] | ^~ 780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: in expansion of macro ‘__DECLARE_TRACE’ 781 21:14:39 DEBUG| [stdout] 406 | __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \ 782 21:14:39 DEBUG| [stdout] | ^~~ 783 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:542:2: note: in expansion of macro ‘DECLARE_TRACE’ 784 21:14:39 DEBUG| [stdout] 542 |
[Kernel-packages] [Bug 1987595] Re: Support Intel IPU6 MIPI camera
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Won't Fix -- 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/1987595 Title: Support Intel IPU6 MIPI camera Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Incomplete Status in linux-firmware source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Incomplete Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [SRU Justfication:linux-firmware] [Impact] Need new firmware updates for additional camera senesors. [Fix] Firmware updates for Intel IPU6/VSC drivers, as well as new firmware blobs for hi556/ovti02c1. [Test Case] The driver will prompt for missed firmware blobs for a given platform. [Where problems could occur] There is still no suspend support for the camera driver, and user sessions across system suspend have to be restarted. [Other Info] New sensors are introduced in Jammy oem kernels only, and kinetic is nominated for future hwe migration. = original bug report == This is a follow-up for bug 1964983 but on different platforms that runs linux-oem-5.17 or newer. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982749] Re: New device IDs for Intel Raptor Lake S platform
** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Incomplete => Won't Fix -- 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/1982749 Title: New device IDs for Intel Raptor Lake S platform Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Feature Description] This task is to identify what new device IDs are required for RPL-S. Placeholder for RPL-S IDs that should be published. USB device/xDCI 0x7a61 038438a25c45 v5.17-rc6 SMBus 0x7a23 9c02d4011e92 v5.18-rc1 I²C 0x7a4c 0x7a4d 0x7a4e 0x7a4f 0x7a7c 0x7a7d 8c70bd5802f4 v5.18-rc1 HS-UART 0x7a28 0x7a29 0x7a5c 0x7a7e 8c70bd5802f4 v5.18-rc1 SPI 0x7a2a 0x7a2b 0x7a79 0x7a7b 8c70bd5802f4 v5.18-rc1 SPI Flash Controller 0x7a24 299d8b74519d v5.18-rc4 GPIO INTC1085 ddfdd1304e59 v5.18-rc1 NPK 0x7a26 23e2de5826e2f v6.0-rc1 NPK/CPU 0xA76Fh ff46a601afc5a v6.0-rc1 TBT AHCI Binds by PCI Class XHCI Binds by PCI Class To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987987] Re: thinkbook 14 Gen4+. screen flickering when logging in.
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Won't Fix -- 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/1987987 Title: thinkbook 14 Gen4+. screen flickering when logging in. Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Won't Fix Bug description: linux-headers-5.17.0-1015-oem linux-image-5.17.0-1015-oem linux-modules-5.17.0-1015-oem linux-oem-22.04 After I `apt install linux-oem-22.04`, it seems that my kernel has been updated to 5.17.0 version. After reboot, I get screen flickering when I move my mouse. But when I use 5.15.0-46-generic version linux kernel to boot, no problems occur. So, is there any problem with the kernel 5.17.0 in my new laptop thinkbook 14 Gen4+? information about my laptop uname -a Linux lqw-ThinkBook-14-G4-IAP 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 apt-cache policy linux-modules-5.17.0-1015-oem linux-modules-5.17.0-1015-oem: 已安装：(无) 候选： 5.17.0-1015.16 版本列表： 5.17.0-1015.16 500 500 https://mirrors.ustc.edu.cn/ubuntu jammy-security/main amd64 Packages 500 https://mirrors.ustc.edu.cn/ubuntu jammy-updates/main amd64 Packages apt-cache policy linux-oem-5.17-headers-5.17.0-1015 linux-oem-5.17-headers-5.17.0-1015: 已安装：(无) 候选： 5.17.0-1015.16 版本列表： 5.17.0-1015.16 500 500 https://mirrors.ustc.edu.cn/ubuntu jammy-security/main amd64 Packages 500 https://mirrors.ustc.edu.cn/ubuntu jammy-security/main i386 Packages 500 https://mirrors.ustc.edu.cn/ubuntu jammy-updates/main amd64 Packages 500 https://mirrors.ustc.edu.cn/ubuntu jammy-updates/main i386 Packages expected to happen: no screen flickering when logging and moving mouse. What happended instead: screen flickering when logging and moving mouse. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-headers-5.17.0-1015-oem (not installed) ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 29 00:26:02 2022 InstallationDate: Installed on 2022-08-28 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-oem-5.17 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1987987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990931] Re: Fix AMD W6800: kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0
still a bug in 6.1 or up? ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu) Status: In Progress => 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/1990931 Title: Fix AMD W6800: kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0 Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] kernel: WARNING: CPU: 2 PID: 504 at arch/x86/kernel/fpu/core.c:159 kernel_fpu_begin_mask+0xa4/0xb0 [Fix] Remove FPU codes from AMD DCN folder. [Test Case] 1. check the dmesg if the warning exist. [Where problems could occur] Low, the FPU codes are moved to DML folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006546] Re: Improve arp_ndisc_evict_nocarrier.sh test result processing
** Changed in: linux-oem-5.17 (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-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2006546 Title: Improve arp_ndisc_evict_nocarrier.sh test result processing 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 Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 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 Bug description: [Impact] The arp_ndisc_evict_nocarrier.sh in selftests/net didn't pass a proper return value for failed test cases. Thus we might get false negatives if the last command runs successfully. [Fix] * 1856628baa selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier This patch can be cherry-picked into affected kernels. Lunar has been patched already. J-hwe-5.17 will be deprecated thus it will be skipped. [Test] Run the patched test, this should not cause any regression as sub tests are good with our kernels (except there is a cleanup issue in bug 1968310) One can deliberately fail a test by hijacking the if statement for the return value check to make sure this patch is working as expected. [Where problems could occur] This patch improves the result interpretation, we might see new failures being reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002674] Re: Jammy update: v6.0.15 upstream stable release
** Changed in: linux-oem-6.0 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Won't Fix -- 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/2002674 Title: Jammy update: v6.0.15 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.15 upstream stable release from git://git.kernel.org/ Linux 6.0.15 net: loopback: use NET_NAME_PREDICTABLE for name_assign_type selftests: net: Use "grep -E" instead of "egrep" Bluetooth: L2CAP: Fix u8 overflow KEYS: encrypted: fix key instantiation with user-provided data usb: dwc3: pci: Update PCIe device ID for USB3 controller on CPU sub-system for Raptor Lake usb: typec: ucsi: Resume in separate work igb: Initialize mailbox message for VF reset xhci: Apply XHCI_RESET_TO_DEFAULT quirk to ADL-N ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook USB: serial: f81534: fix division by zero on line-speed change USB: serial: f81232: fix division by zero on line-speed change USB: serial: cp210x: add Kamstrup RF sniffer PIDs USB: serial: option: add Quectel EM05-G modem usb: gadget: uvc: Prevent buffer overflow in setup handler udf: Fix extending file within last block udf: Do not bother looking for prealloc extents if i_lenExtents matches i_size udf: Fix preallocation discarding at indirect extent boundary udf: Discard preallocation before extending file with a hole selftests/bpf: Add kprobe_multi kmod attach api tests selftests/bpf: Add kprobe_multi check to module attach test selftests/bpf: Add bpf_testmod_fentry_* functions selftests/bpf: Add load_kallsyms_refresh function bpf: Take module reference on kprobe_multi link bpf: Rename __bpf_kprobe_multi_cookie_cmp to bpf_kprobe_multi_addrs_cmp ftrace: Add support to resolve module symbols in ftrace_lookup_symbols kallsyms: Make module_kallsyms_on_each_symbol generally available PCI: mt7621: Add sentinel to quirks table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/2002674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987998] Re: LSM: Configuring Too Many LSMs Causes Kernel Panic on Boot
** Changed in: linux-oem-6.0 (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-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1987998
Title:
LSM: Configuring Too Many LSMs Causes Kernel Panic on Boot
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:
Fix Released
Status in linux-oem-6.0 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Released
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Bug description:
BugLink: https://bugs.launchpad.net/bugs/1987998
[Impact]
The Ubuntu kernel carries an out of tree patchet, known as "LSM:
Module stacking for AppArmor" upstream, to enable stackable LSMs for
containers. The revision the Ubuntu kernel carries is an older one,
from 2020, and has some slight divergences from the latest revision in
development.
One such divergence, is support for Landlock as a stackable LSM. When
the stackable LSM patchset was applied, Landlock was still in
development and not mainlined yet, and wasn't present in the earlier
revision of the "LSM: Module stacking for AppArmor" patchset. Support
for this was added by us.
There was a minor omission made during enabling support for Landlock.
The LSM slot type was marked as LSMBLOB_NEEDED, when it should have
been LSMBLOB_NOT_NEEDED.
Landlock itself does not provide any of the hooks that use a struct
lsmblob, such as secid_to_secctx, secctx_to_secid, inode_getsecid,
cred_getsecid, kernel_act_as task_getsecid_subj task_getsecid_obj and
ipc_getsecid.
When we set .slot = LSMBLOB_NEEDED, this indicates that we need an
entry in struct lsmblob, and we need to increment LSMBLOB_ENTRIES by
one to fit the entry into the secid array:
#define LSMBLOB_ENTRIES ( \
(IS_ENABLED(CONFIG_SECURITY_SELINUX) ? 1 : 0) + \
(IS_ENABLED(CONFIG_SECURITY_SMACK) ? 1 : 0) + \
(IS_ENABLED(CONFIG_SECURITY_APPARMOR) ? 1 : 0) + \
(IS_ENABLED(CONFIG_BPF_LSM) ? 1 : 0))
struct lsmblob {
u32 secid[LSMBLOB_ENTRIES];
};
Currently, we don't increment LSMBLOB_ENTRIES by one to make an entry
for Landlock, so for the Ubuntu kernel, we can fit a maximum of two
entries, one for Apparmor and one for bpf.
If you try and configure three LSMs like so and reboot:
GRUB_CMDLINE_LINUX_DEFAULT="lsm=landlock,bpf,apparmor"
You will receive the following panic:
LSM: Security Framework initializing
landlock: Up and running.
LSM support for eBPF active
Kernel panic - not syncing: security_add_hooks Too many LSMs registered.
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-46-generic #49-Ubuntu
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
Call Trace:
show_stack+0x52/0x5c
dump_stack_lvl+0x4a/0x63
dump_stack+0x10/0x16
panic+0x149/0x321
security_add_hooks+0x45/0x13a
apparmor_init+0x189/0x1ef
initialize_lsm+0x54/0x74
ordered_lsm_init+0x379/0x392
security_init+0x40/0x49
start_kernel+0x466/0x4dc
x86_64_start_reservations+0x24/0x2a
x86_64_start_kernel+0xe4/0xef
secondary_startup_64_no_verify+0xc2/0xcb
---[ end Kernel panic - not syncing: security_add_hooks Too many LSMs
registered. ]---
There is a check added in security_add_hooks() that makes sure that
you cannot configure too many LSMs:
if (lsmid->slot == LSMBLOB_NEEDED) {
if (lsm_slot >= LSMBLOB_ENTRIES)
panic("%s Too many LSMs registered.\n", __func__);
lsmid->slot = lsm_slot++;
init_debug("%s assigned lsmblob slot %d\n", lsmid->lsm,
lsmid->slot);
}
A workaround is to enable no more than 2 LSMs until this is fixed.
[Fix]
If you read the following mailing list thread on linux-security-
modules from May 2021:
https://lore.kernel.org/selinux/202105141224.942DE93@keescook/T/
It is explained that Landlock does not provide any of the hooks that
use a struct lsmblob, such as secid_to_secctx, secctx_to_secid,
inode_getsecid, cred_getsecid, kernel_act_as task_getsecid_subj
task_getsecid_obj and ipc_getsecid.
I verified this with:
ubuntu-jammy$ grep -Rin "secid_to_secctx" security/landlock/
ubuntu-jammy$ grep -Rin "secctx_to_secid" security/landlock/
ubuntu-jammy$ grep -Rin "inode_getsecid" security/landlock/
ubuntu-jammy$ grep -Rin "cred_getsecid" security/landlock/
ubuntu-jammy$ grep -Rin "kernel_act_as" security/landlock/
ubuntu-jammy$ grep -Rin "task_getsecid_subj" security/landlock/
ubuntu-jammy$ grep -Rin "task_getsecid_obj" security/landlock/
ubuntu-jammy$ grep -Rin "ipc_getsecid" security/landlock/
The fix is to change Landlock from LSMBLOB_NEEDED to
LSMBLOB_NOT_NEEDED.
Due to the "LSM: Module stacking for AppArmor" patchset being 25
patches long, it was impractical to revert just the
[Kernel-packages] [Bug 1997757] Re: No more sound after upgrade to linux-image-6.0.0-1007-oem
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Incomplete => Won't Fix -- 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/1997757 Title: No more sound after upgrade to linux-image-6.0.0-1007-oem Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Bug description: Description:KDE neon 5.26 Release:22.04 After upgrade from linux-image-6.0.0-1006-oem to linux-image-6.0.0-1007-oem I don't have sound anymore. I believe that the relevant dmesg message is this one, as it is not printed with the linux-image-6.0.0-1006-oem version: I think this bug is connected with this bub from Debian. https://lists.debian.org/debian-kernel/2022/10/msg00301.html Log: [5.535620] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [5.535644] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [5.535650] sof-audio-pci-intel-tgl :00:1f.3: enabling device ( -> 0002) [5.535784] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [5.535850] sof-audio-pci-intel-tgl :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [5.544186] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [5.605507] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 5 [5.605509] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [5.605511] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [5.606867] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:0:0-b678a [5.606869] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:20:0 Kernel ABI 3:23:0 [5.606872] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [5.613329] iwlwifi :00:14.3: Detected RF HR B3, rfid=0x10a100 [5.679733] iwlwifi :00:14.3: base HW address: 8c:1d:96:08:c0:32 [5.691036] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:0:0-b678a [5.691039] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:20:0 Kernel ABI 3:23:0 [5.695325] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0 [5.703514] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:20:0 Kernel ABI 3:23:0 [5.703670] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: Parent card not yet available, widget card binding deferred [5.706576] snd_hda_codec_hdmi ehdaudio0D2: failed to create hda codec -12 [5.706661] snd_hda_codec_hdmi ehdaudio0D2: ASoC: error at snd_soc_component_probe on ehdaudio0D2: -12 [5.706676] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to instantiate card -12 [5.706767] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1997757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002676] Re: Jammy update: v6.0.17 upstream stable release
** Changed in: linux-oem-6.0 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Won't Fix -- 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/2002676 Title: Jammy update: v6.0.17 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.17 upstream stable release from git://git.kernel.org/ Linux 6.0.17 kcsan: Instrument memcpy/memset/memmove with newer Clang SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak tpm: acpi: Call acpi_put_table() to fix memory leak mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING block: Do not reread partition table on exclusively open device f2fs: allow to read node block after shutdown f2fs: should put a page when checking the summary info mm, compaction: fix fast_isolate_around() to stay within boundaries md: fix a crash in mempool_free mfd: mt6360: Add bounds checking in Regmap read/write call-backs pnode: terminate at peers of source ALSA: hda/hdmi: Static PCM mapping again with AMD HDMI codecs ALSA: line6: fix stack overflow in line6_midi_transmit ALSA: line6: correct midi status byte when receiving data from podxt ovl: update ->f_iocb_flags when ovl_change_flags() modifies ->f_flags ovl: Use ovl mounter's fsuid and fsgid in ovl_link() binfmt: Fix error return code in load_elf_fdpic_binary() io_uring: dont remove file from msg_ring reqs eventfd: provide a eventfd_signal_mask() helper eventpoll: add EPOLL_URING_WAKE poll wakeup flag hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount pstore/zone: Use GFP_ATOMIC to allocate zone buffer pstore: Properly assign mem_type property mm/mempolicy: fix memory leak in set_mempolicy_home_node system call rtmutex: Add acquire semantics for rtmutex lock acquisition slow path futex: Fix futex_waitv() hrtimer debug object leak on kcalloc error HID: plantronics: Additional PIDs for double volume key presses quirk HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint kprobes: kretprobe events missing on 2-core KVM guest rtc: msc313: Fix function prototype mismatch in msc313_rtc_probe() powerpc/rtas: avoid scheduling in rtas_os_term() powerpc/rtas: avoid device tree lookups in rtas_os_term() iommu/mediatek: Fix crash on isr after kexec() objtool: Fix SEGFAULT fs/ntfs3: Fix slab-out-of-bounds in r_page fs/ntfs3: Delete duplicate condition in ntfs_read_mft() fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() fs/ntfs3: Validate index root when initialize NTFS security soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 fs/ntfs3: Fix slab-out-of-bounds read in run_unpack fs/ntfs3: Validate resident attribute name fs/ntfs3: Validate buffer length while parsing index fs/ntfs3: Validate attribute name offset fs/ntfs3: Add null pointer check for inode operations fs/ntfs3: Fix memory leak on ntfs_fill_super() error path fs/ntfs3: Add null pointer check to attr_load_runs_vcn fs/ntfs3: Validate data run offset fs/ntfs3: Add overflow check for attribute size fs/ntfs3: Validate BOOT record_size nvmet: don't defer passthrough commands with trivial effects to the workqueue nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition ata: ahci: Fix PCS quirk application for suspend block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq ACPI: resource: do IRQ override on Lenovo 14ALC7 ACPI: resource: do IRQ override on XMG Core 15 ACPI: resource: do IRQ override on LENOVO IdeaPad ACPI: resource: Skip IRQ override on Asus Vivobook K3402ZA/K3502ZA nvme-pci: fix page size checks nvme-pci: fix mempool alloc size nvme-pci: fix doorbell buffer value endianness cifs: don't leak -ENOMEM in smb2_open_file() cifs: fix static checker warning blk-iolatency: Fix memory leak on add_disk() failures blk-cgroup: pass a gendisk to blkg_destroy_all blk-throttle: pass a gendisk to blk_throtl_init and blk_throtl_exit blk-cgroup: pass a gendisk to blkcg_init_queue and blkcg_exit_queue blk-cgroup: cleanup the
[Kernel-packages] [Bug 2002675] Re: Jammy update: v6.0.16 upstream stable release
** Changed in: linux-oem-6.0 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Won't Fix -- 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/2002675 Title: Jammy update: v6.0.16 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-01-12 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/2002675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002677] Re: Jammy update: v6.0.18 upstream stable release
** Changed in: linux-oem-6.0 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Invalid -- 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/2002677 Title: Jammy update: v6.0.18 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.18 upstream stable release from git://git.kernel.org/ Linux 6.0.18 cifs: prevent copying past input buffer boundaries drm/amd/pm: correct the fan speed retrieving in PWM for some SMU13 asics drm/amd/pm: bump SMU13.0.0 driver_if header to version 0x34 drm/amd/pm: add missing SMU13.0.7 mm_dpm feature mapping drm/amd/pm: add missing SMU13.0.0 mm_dpm feature mapping drm/i915/migrate: Account for the reserved_space drm/i915: improve the catch-all evict to handle lock contention drm/amdgpu: make display pinning more flexible (v2) drm/amdgpu: handle polaris10/11 overlap asics (v2) drm/amd/display: Add DCN314 display SG Support drm/i915/ttm: consider CCS for backup objects ext4: allocate extended attribute value in vmalloc area ext4: avoid unaccounted block allocation when expanding inode ext4: initialize quota before expanding inode in setproject ioctl ext4: fix inode leak in ext4_xattr_inode_create() on an error path ext4: fix kernel BUG in 'ext4_write_inline_data_end()' ext4: fix deadlock due to mbcache entry corruption ext4: avoid BUG_ON when creating xattrs ext4: fix corrupt backup group descriptors after online resize ext4: dont return EINVAL from GETFSUUID when reporting UUID length ext4: fix bad checksum after online resize ext4: fix error code return to user-space in ext4_get_branch() ext4: fix corruption when online resizing a 1K bigalloc fs ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline ext4: don't fail GETFSUUID when the caller provides a long buffer ext4: init quota for 'old.inode' in 'ext4_rename' ext4: fix uninititialized value in 'ext4_evict_inode' ext4: fix off-by-one errors in fast-commit block filling ext4: fix unaligned memory access in ext4_fc_reserve_space() ext4: add missing validation of fast-commit record lengths ext4: don't set up encryption key during jbd2 transaction ext4: fix leaking uninitialized memory in fast-commit journal ext4: disable fast-commit of encrypted dir operations ext4: don't allow journal inode to have encrypt flag ext4: fix bug_on in __es_tree_search caused by bad boot loader inode ext4: check and assert if marking an no_delete evicting inode dirty ext4: journal_path mount options should follow links ext4: fix reserved cluster accounting in __es_remove_extent() ext4: fix bug_on in __es_tree_search caused by bad quota inode ext4: add helper to check quota inums ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode ext4: fix undefined behavior in bit shift for ext4_check_flag_values ext4: fix use-after-free in ext4_orphan_cleanup fs: ext4: initialize fsdata in pagecache_write() ext4: remove trailing newline from ext4_msg() message ext4: add inode table check in __ext4_get_inode_loc to aovid possible infinite loop ext4: silence the warning when evicting inode with dioread_nolock drm/etnaviv: reap idle mapping if it doesn't match the softpin address drm/ingenic: Fix missing platform_driver_unregister() call in ingenic_drm_init() drm/i915/dsi: fix VBT send packet port selection for dual link DSI drm/etnaviv: move idle mapping reaping into separate function drm/vmwgfx: Validate the box size for the snooped cursor drm/connector: send hotplug uevent on connector cleanup device_cgroup: Roll back to original exceptions after copy failure parisc: Drop PMD_SHIFT from calculation in pgtable.h parisc: Add missing FORCE prerequisites in Makefile parisc: Fix locking in pdc_iodc_print() firmware call parisc: led: Fix potential null-ptr-deref in start_task() remoteproc: imx_rproc: Correct i.MX93 DRAM mapping remoteproc: core: Do pm_relax when in RPROC_OFFLINE state remoteproc: imx_dsp_rproc: Add mutex protection for workqueue test_kprobes: Fix implicit declaration error of test_kprobes iommu/amd: Fix ill-formed ivrs_ioapic, ivrs_hpet and ivrs_acpihid options iommu/amd: Fix ivrs_acpihid cmdline parsing code phy:
[Kernel-packages] [Bug 2002678] Re: Jammy update: v6.0.19 upstream stable release
** Changed in: linux-oem-6.0 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux-oem-6.0 (Ubuntu) Status: Won't Fix => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Won't Fix -- 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/2002678 Title: Jammy update: v6.0.19 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.19 upstream stable release from git://git.kernel.org/ Linux 6.0.19 drm/mgag200: Fix PLL setup for G200_SE_A rev >=4 efi: random: combine bootloader provided RNG seed with RNG protocol output btrfs: make thaw time super block check to also verify checksum ksmbd: check nt_len to be at least CIFS_ENCPWD_SIZE in ksmbd_decode_ntlmssp_auth_blob ksmbd: send proper error response in smb2_tree_connect() ksmbd: fix infinite loop in ksmbd_conn_handler_loop() btrfs: handle case when repair happens with dev-replace virtio_blk: Fix signedness bug in virtblk_prep_rq() virtio-blk: use a helper to handle request queuing errors drm/i915/gvt: fix vgpu debugfs clean in remove drm/i915/gvt: fix gvt debugfs destroy drm/amdkfd: Fix kernel warning during topology setup of/fdt: run soc memory setup when early_init_dt_scan_memory fails riscv, kprobes: Stricter c.jr/c.jalr decoding riscv: uaccess: fix type of 0 variable on error in get_user() thermal: int340x: Add missing attribute for data rate base vhost_vdpa: fix the crash in unmap a large memory io_uring: fix CQ waiting timeout handling block: don't allow splitting of a REQ_NOWAIT bio net: dsa: tag_qca: fix wrong MGMT_DATA2 size net: dsa: qca8k: fix wrong length value for mgmt eth packet Revert "net: dsa: qca8k: cache lo and hi for mdio write" Revert "drm/amd/display: Enable Freesync Video Mode by default" bpf: Fix panic due to wrong pageattr of im->image fbdev: matroxfb: G200eW: Increase max memory from 1 MB to 16 MB nfsd: fix handling of readdir in v4root vs. mount upcall timeout x86/bugs: Flush IBP in ib_prctl_set() x86/kexec: Fix double-free of elf header buffer btrfs: fix compat_ro checks against remount btrfs: relax block-group-tree feature dependency checks btrfs: separate BLOCK_GROUP_TREE compat RO flag from EXTENT_TREE_V2 btrfs: don't save block group root into super block btrfs: check superblock to ensure the fs was not modified at thaw time ASoC: SOF: Intel: pci-tgl: unblock S5 entry if DMA stop has failed" nvme: also return I/O command effects from nvme_command_effects nvmet: use NVME_CMD_EFFECTS_CSUPP instead of open coding it io_uring: check for valid register opcode earlier nvme: fix multipath crash caused by flush request when blktrace is enabled drm/amdkfd: Fix double release compute pasid drm/amdkfd: Fix kfd_process_device_init_vm error handling drm/amdgpu: Fix size validation for non-exclusive domains (v4) ASoC: SOF: mediatek: initialize panic_info to zero ASoC: Intel: bytcr_rt5640: Add quirk for the Advantech MICA-071 tablet 9p/client: fix data race on req->status ASoC: SOF: Revert: "core: unregister clients and machine drivers in .shutdown" hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling usb: dwc3: xilinx: include linux/gpio/consumer.h udf: Fix extension of the last extent in the file caif: fix memory leak in cfctrl_linkup_request() net/ulp: prevent ULP without clone op from entering the LISTEN status qed: allow sleep in qed_mcp_trace_dump() ublk: honor IO_URING_F_NONBLOCK for handling control command drm/i915/gvt: fix double free bug in split_2MB_gtt_entry drm/i915: unpin on error in intel_vgpu_shadow_mm_pin() perf stat: Fix handling of --for-each-cgroup with --bpf-counters to match non BPF mode perf stat: Fix handling of unsupported cgroup events when using BPF counters perf lock contention: Fix core dump related to not finding the "__sched_text_end" symbol on s/390 usb: rndis_host: Secure rndis_query check against int overflow octeontx2-pf: Fix lmtst ID used in aura free drivers/net/bonding/bond_3ad: return when there's no aggregator fs/ntfs3: don't hold ni_lock when calling truncate_setsize() drm/imx: ipuv3-plane: Fix overlay plane width perf tools: Fix resources leak in perf_data__open_dir() netfilter: ipset: Rework
[Kernel-packages] [Bug 1980484] Re: temporarily disable CONFIG_X86_KERNEL_IBT
I performed a smoke test with v4l2loopback-dkms in jammy, everything looks good. Test case: $ sudo apt install v4l2loopback-dkms ... $ sudo modprobe v4l2loopback devices=1 video_nr=8 exclusive_caps=1 max_buffers=2 $ sudo v4l2loopback-ctl set-fps 60 /dev/video8 OK $ sudo v4l2-ctl --list-devices Dummy video device (0x) (platform:v4l2loopback-000): /dev/video8 This works both with 5.15 and the new 5.19 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980484 Title: temporarily disable CONFIG_X86_KERNEL_IBT Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in v4l2loopback package in Ubuntu: Fix Released Status in v4l2loopback source package in Jammy: Fix Committed Status in backport-iwlwifi-dkms source package in Kinetic: Fix Released Status in linux source package in Kinetic: Fix Released Status in v4l2loopback source package in Kinetic: Fix Released Bug description: Enabling IBT in the kernel is going to be problematic at the moment, because dkms' that have a precompiled binary need to be linked against non-IBT kernels and IBT kernels (see nvidia drivers for example). For this reason it's safer to keep IBT disabled at the moment, until all the kernels will have IBT enabled and the kernel modules / binaries will use the proper flags to generate IBT-compliant binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1980484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)
I report my strange experience with flickering. I had the problem as described on Dell Inspiron 1764/Ubuntu 20.04 with 50% of occurence at boot with the screen flickering indefinitely, Linux version 5.15.0-60-generic (buildd@lcy02-amd64-017). I suspected HW but nevertheless tried GRUB configuration modification with no success. I installed Ubuntu 22.04 and now I have the flicker just during 30seconds of boot. The kernel is the same only the build is different, Linux version 5.15.0-60-generic (buildd@lcy02-amd64-054). Perhaps the build may modify some timings during the boot. -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later) Status in linux package in Ubuntu: Fix Released Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998510] Re: Jammy update: v6.0.10 upstream stable release
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Won't Fix -- 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/1998510 Title: Jammy update: v6.0.10 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.10 upstream stable release from git://git.kernel.org/ Linux 6.0.10 ntfs: check overflow when iterating ATTR_RECORDs ntfs: fix out-of-bounds read in ntfs_attr_find() ntfs: fix use-after-free in ntfs_attr_find() bpf: Prevent bpf program recursion for raw tracepoint probes net/9p: use a dedicated spinlock for trans_fd mm: fs: initialize fsdata passed to write_begin/write_end interface rseq: Use pr_warn_once() when deprecated/unknown ABI flags are encountered wifi: wext: use flex array destination for memcpy() netlink: Bounds-check struct nlmsgerr creation 9p/trans_fd: always use O_NONBLOCK read/write gfs2: Switch from strlcpy to strscpy gfs2: Check sb_bsize_shift after reading superblock 9p: trans_fd/p9_conn_cancel: drop client lock earlier KVM: x86/xen: Fix eventfd error handling in kvm_xen_eventfd_assign() kcm: avoid potential race in kcm_tx_work tcp: cdg: allow tcp_cdg_release() to be called multiple times macvlan: enforce a consistent minimal mtu Input: i8042 - fix leaking of platform device on module removal arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud tracing: Fix potential null-pointer-access of entry in list 'tr->err_log' kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case scsi: scsi_debug: Fix possible UAF in sdebug_add_host_helper() scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus() net: use struct_group to copy ip/ipv6 header addresses net: usb: smsc95xx: fix external PHY reset tracing: Fix warning on variable 'struct trace_array' ring-buffer: Include dropped pages in counting dirty patches perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling vfio: Split the register_device ops call into functions vfio: Rename vfio_ioctl_check_extension() perf: Improve missing SIGTRAP checking ASoC: SOF: topology: No need to assign core ID if token parsing failed nvme: ensure subsystem reset is single threaded nvme: restrict management ioctls to admin perf/x86/intel/pt: Fix sampling using single range output perf/x86/amd/uncore: Fix memory leak for events array x86/fpu: Drop fpregs lock before inheriting FPU permissions x86/sgx: Add overflow check in sgx_validate_offset_length() blk-cgroup: properly pin the parent in blkcg_css_online misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() s390/dcssblk: fix deadlock when adding a DCSS docs/driver-api/miscellaneous: Remove kernel-doc of serial_core.c docs: update mediator contact information in CoC doc mmc: sdhci-pci: Fix possible memory leak caused by missing pci_dev_put() mmc: sdhci-pci-o2micro: fix card detect fail issue caused by CD# debounce timeout mmc: core: properly select voltage range without power cycle firmware: coreboot: Register bus in module init iommu/vt-d: Set SRE bit only when hardware has SRS cap iommu/vt-d: Preset Access bit for IOVA in FL non-leaf paging entries scsi: zfcp: Fix double free of FSF request when qdio send fails net: phy: marvell: add sleep time after enabling the loopback bit maccess: Fix writing offset in case of fault in strncpy_from_kernel_nofault() Input: iforce - invert valid length check when fetching device IDs ceph: avoid putting the realm twice when decoding snaps fails io_uring: disallow self-propelled ring polling io_uring: fix multishot recv request leaks io_uring: fix multishot accept request leaks io_uring: fix tw losing poll events serial: 8250_lpss: Use 16B DMA burst with Elkhart Lake serial: 8250_lpss: Configure DMA also w/o DMA filter serial: 8250: Flush DMA Rx on RLSI serial: 8250: Fall back to non-DMA Rx if IIR_RDI occurs dm ioctl: fix misbehavior if list_versions races with module loading dm bufio: Fix missing decrement of no_sleep_enabled if dm_bufio_client_create failed iio: pressure: ms5611: changed hardcoded SPI speed to value limited iio: pressure: ms5611: fixed value compensation bug iio: adc: mp2629: fix potential array out of bound
[Kernel-packages] [Bug 2002669] Re: Jammy update: v6.0.11 upstream stable release
** Changed in: linux-oem-6.0 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Won't Fix -- 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/2002669 Title: Jammy update: v6.0.11 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.11 upstream stable release from git://git.kernel.org/ Linux 6.0.11 bpf: Add explicit cast to 'void *' for __BPF_DISPATCHER_UPDATE() drm/i915: fix TLB invalidation for Gen12 video and compute engines drm/amdgpu: Partially revert "drm/amdgpu: update drm_display_info correctly when the edid is read" drm/amdgpu: always register an MMU notifier for userptr drm/amd/display: Update soc bounding box for dcn32/dcn321 drm/amd/amdgpu: reserve vm invalidation engine for firmware drm/amdgpu: Enable Aldebaran devices to report CU Occupancy drm/amdgpu/psp: don't free PSP buffers on suspend drm/amd/display: No display after resume from WB/CB drm/amd/dc/dce120: Fix audio register mapping, stop triggering KASAN drm/display/dp_mst: Fix drm_dp_mst_add_affected_dsc_crtcs() return code drm/i915/ttm: never purge busy objects btrfs: do not modify log tree while holding a leaf from fs tree locked btrfs: sysfs: normalize the error handling branch in btrfs_init_sysfs() btrfs: use kvcalloc in btrfs_get_dev_zone_info btrfs: zoned: fix missing endianness conversion in sb_write_pointer btrfs: free btrfs_path before copying subvol info to userspace btrfs: free btrfs_path before copying fspath to userspace btrfs: free btrfs_path before copying inodes to userspace btrfs: free btrfs_path before copying root refs to userspace wifi: wilc1000: validate number of channels wifi: wilc1000: validate length of IEEE80211_P2P_ATTR_CHANNEL_LIST attribute wifi: wilc1000: validate length of IEEE80211_P2P_ATTR_OPER_CHANNEL attribute wifi: wilc1000: validate pairwise and authentication suite offsets fuse: lock inode unconditionally in fuse_fallocate() dm integrity: clear the journal on suspend dm integrity: flush the journal on suspend gpu: host1x: Avoid trying to use GART on Tegra20 scsi: iscsi: Fix possible memory leak when device_register() failed scsi: mpi3mr: Suppress command reply debug prints net: usb: qmi_wwan: add Telit 0x103a composition dm-log-writes: set dma_alignment limit in io_hints dm-integrity: set dma_alignment limit in io_hints block: make blk_set_default_limits() private tcp: configurable source port perturb table size platform/x86: ideapad-laptop: Add module parameters to match DMI quirk tables platform/x86: ideapad-laptop: Fix interrupt storm on fn-lock toggle on some Yoga laptops platform/x86: hp-wmi: Ignore Smart Experience App event platform/surface: aggregator_registry: Add support for Surface Laptop 5 zonefs: fix zone report size in __zonefs_io_error() drm/amdkfd: Fix a memory limit issue drm/amdgpu: disable BACO support on more cards drm/amd/display: use uclk pstate latency for fw assisted mclk validation dcn32 platform/surface: aggregator_registry: Add support for Surface Pro 9 platform/x86: acer-wmi: Enable SW_TABLET_MODE on Switch V 10 (SW5-017) platform/x86: asus-wmi: add missing pci_dev_put() in asus_wmi_set_xusb2pr() platform/x86: thinkpad_acpi: Enable s2idle quirk for 21A1 machine type xen/platform-pci: add missing free_irq() in error path xen-pciback: Allow setting PCI_MSIX_FLAGS_MASKALL too ASoC: stm32: dfsdm: manage cb buffers cleanup Input: i8042 - apply probe defer to more ASUS ZenBook models pinctrl: qcom: sc8280xp: Rectify UFS reset pins Input: soc_button_array - add Acer Switch V 10 to dmi_use_low_level_irq[] Input: soc_button_array - add use_low_level_irq module parameter ASoC: sof_es8336: reduce pop noise on speaker bpf: Convert BPF_DISPATCHER to use static_call() (not ftrace) Input: goodix - try resetting the controller when no config is set Revert "tty: n_gsm: replace kicktimer with delayed_work" Revert "tty: n_gsm: avoid call of sleeping functions from atomic context" serial: 8250: 8250_omap: Avoid RS485 RTS glitch on ->set_termios() ASoC: SOF: ipc3-topology: use old pipeline teardown flow with SOF2.1 and older ASoC: hda: intel-dsp-config: add ES83x6 quirk for IceLake tools:
[Kernel-packages] [Bug 2002670] Re: Jammy update: v6.0.12 upstream stable release
** Changed in: linux-oem-6.0 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Won't Fix -- 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/2002670 Title: Jammy update: v6.0.12 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.12 upstream stable release from git://git.kernel.org/ Linux 6.0.12 proc: proc_skip_spaces() shouldn't think it is working on C strings proc: avoid integer type confusion in get_proc_long ipc/sem: Fix dangling sem_array access in semtimedop race powerpc/bpf/32: Fix Oops on tail call tests Input: raydium_ts_i2c - fix memory leak in raydium_i2c_send() char: tpm: Protect tpm_pm_suspend with locks Revert "clocksource/drivers/riscv: Events are stopped during CPU suspend" ACPI: HMAT: Fix initiator registration for single-initiator systems ACPI: HMAT: remove unnecessary variable initialization i2c: imx: Only DMA messages with I2C_M_DMA_SAFE flag set i2c: qcom-geni: fix error return code in geni_i2c_gpi_xfer i2c: npcm7xx: Fix error handling in npcm_i2c_init() i2c: Restore initial power state if probe fails mm/damon/sysfs: fix wrong empty schemes assumption under online tuning in damon_sysfs_set_schemes() mm/damon: introduce struct damos_access_pattern ipv4: Fix route deletion when nexthop info is not specified ipv4: Handle attempt to delete multipath route when fib_info contains an nh reference iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init() iommu/vt-d: Fix PCI device refcount leak in has_external_pci() nvme: fix SRCU protection of nvme_ns_head list riscv: kexec: Fixup irq controller broken in kexec crash path riscv: fix race when vmap stack overflow riscv: Sync efi page table's kernel mappings before switching pinctrl: single: Fix potential division by zero ASoC: tlv320adc3xxx: Fix build error for implicit function declaration ASoC: ops: Fix bounds check for _sx controls tracing: Free buffers when a used dynamic event is removed tracing: Fix race where histograms can be called before the event tracing/osnoise: Fix duration type drm/i915: Never return 0 if not all requests retired drm/i915: Fix negative value passed as remaining time drm/amdgpu: enable Vangogh VCN indirect sram mode drm/amdgpu: temporarily disable broken Clang builds due to blown stack-frame Kconfig.debug: provide a little extra FRAME_WARN leeway when KASAN is enabled mmc: sdhci: Fix voltage switch delay mmc: sdhci-sprd: Fix no reset data and command after voltage switch mmc: sdhci-esdhc-imx: correct CQHCI exit halt state check mmc: core: Fix ambiguous TRIM and DISCARD arg mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() mmc: mmc_test: Fix removal of debugfs file net: stmmac: Set MAC's flow control register to reflect current settings mm: migrate: fix THP's mapcount on isolation v4l2: don't fall back to follow_pfn() if pin_user_pages_fast() fails pinctrl: intel: Save and restore pins in "direct IRQ" mode x86/bugs: Make sure MSR_SPEC_CTRL is updated properly upon resume from S3 nilfs2: fix NULL pointer dereference in nilfs_palloc_commit_free_entry() tools/vm/slabinfo-gnuplot: use "grep -E" instead of "egrep" error-injection: Add prompt for function error injection can: can327: can327_feed_frame_to_netdev(): fix potential skb leak when netdev is down ALSA: dice: fix regression for Lexicon I-ONIX FW810S riscv: mm: Proper page permissions after initmem free riscv: vdso: fix section overlapping under some conditions hwmon: (asus-ec-sensors) Add checks for devm_kcalloc hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() hwmon: (coretemp) Check for null before removing sysfs attrs afs: Fix server->active leak in afs_put_server net: ethernet: renesas: ravb: Fix promiscuous mode after system resumed sctp: fix memory leak in sctp_stream_outq_migrate() packet: do not set TP_STATUS_CSUM_VALID on CHECKSUM_COMPLETE net/mlx5: Lag, Fix for loop when checking lag net: tun: Fix use-after-free in tun_detach() afs: Fix fileserver probe RTT handling net: mdiobus: fix unbalanced node reference count net: hsr: Fix potential use-after-free tipc: re-fetch skb cb after
[Kernel-packages] [Bug 2002671] Re: Jammy update: v6.0.13 upstream stable release
** Changed in: linux-oem-6.0 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux-oem-6.0 (Ubuntu) Status: Won't Fix => Invalid -- 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/2002671 Title: Jammy update: v6.0.13 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.13 upstream stable release from git://git.kernel.org/ Linux 6.0.13 drm/amdgpu/vcn: update vcn4 fw shared data structure s390/qeth: fix use-after-free in hsci macsec: add missing attribute validation for offload net: mvneta: Fix an out of bounds check net: thunderbolt: fix memory leak in tbnet_open() ipv6: avoid use-after-free in ip6_fragment() net: plip: don't call kfree_skb/dev_kfree_skb() under spin_lock_irq() net: phy: mxl-gpy: add MDINT workaround net: dsa: mv88e6xxx: accept phy-mode = "internal" for internal PHY ports xen/netback: fix build warning dpaa2-switch: Fix memory leak in dpaa2_switch_acl_entry_add() and dpaa2_switch_acl_entry_remove() ethernet: aeroflex: fix potential skb leak in greth_init_rings() tipc: call tipc_lxc_xmit without holding node_read_lock net: dsa: sja1105: fix memory leak in sja1105_setup_devlink_regions() ipv4: Fix incorrect route flushing when table ID 0 is used ipv4: Fix incorrect route flushing when source address is deleted bonding: get correct NA dest address tipc: Fix potential OOB in tipc_link_proto_rcv() net: hisilicon: Fix potential use-after-free in hix5hd2_rx() net: mdio: fix unbalanced fwnode reference count in mdio_device_release() net: hisilicon: Fix potential use-after-free in hisi_femac_rx() net: thunderx: Fix missing destroy_workqueue of nicvf_rx_mode_wq ravb: Fix potential use-after-free in ravb_rx_gbeth() net: microchip: sparx5: Fix missing destroy_workqueue of mact_queue ip_gre: do not report erspan version on GRE interface net: wwan: iosm: fix memory leak in ipc_mux_init() net: stmmac: fix "snps,axi-config" node property parsing gpio/rockchip: fix refcount leak in rockchip_gpiolib_register() nvme initialize core quirks before calling nvme_init_subsystem NFC: nci: Bounds check struct nfc_target arrays i40e: Disallow ip4 and ip6 l4_4_bytes i40e: Fix for VF MAC address 0 i40e: Fix not setting default xps_cpus after reset net: mvneta: Prevent out of bounds read in mvneta_config_rss() xen-netfront: Fix NULL sring after live migration net: microchip: sparx5: correctly free skb in xmit octeontx2-pf: Fix potential memory leak in otx2_init_tc() net: mdiobus: fix double put fwnode in the error path net: mdiobus: fwnode_mdiobus_register_phy() rework error handling net: encx24j600: Fix invalid logic in reading of MISTAT register net: encx24j600: Add parentheses to fix precedence mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add() nfp: correct desc type when header dma len is 4096 selftests: rtnetlink: correct xfrm policy rule in kci_test_ipsec_offload net: dsa: sja1105: Check return value net: dsa: hellcreek: Check return value net: dsa: ksz: Check return value Bluetooth: Fix not cleanup led when bt_init fails Bluetooth: Fix support for Read Local Supported Codecs V2 Bluetooth: Remove codec id field in vendor codec definition Bluetooth: hci_conn: add missing hci_dev_put() in iso_listen_bis() Bluetooth: 6LoWPAN: add missing hci_dev_put() in get_l2cap_conn() vmxnet3: use correct intrConf reference when using extended queues vmxnet3: correctly report encapsulated LRO packet inet: ping: use hlist_nulls rcu iterator during lookup af_unix: Get user_ns from in_skb in unix_diag_get_exact(). drm: bridge: dw_hdmi: fix preference of RGB modes over YUV420 net: ethernet: ti: am65-cpsw: Fix RGMII configuration at SPEED_10 net: broadcom: Add PTP_1588_CLOCK_OPTIONAL dependency for BCMGENET under ARCH_BCM2835 igb: Allocate MSI-X vector when testing e1000e: Fix TX dispatch condition gpio: amd8111: Fix PCI device reference count leak drm/bridge: ti-sn65dsi86: Fix output polarity setting bug netfilter: ctnetlink: fix compilation warning after data race fixes in ct mark netfilter: conntrack: fix using __this_cpu_add in preemptible ca8210: Fix crash by zero
[Kernel-packages] [Bug 2002673] Re: Jammy update: v6.0.14 upstream stable release
** Changed in: linux-oem-6.0 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Won't Fix -- 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/2002673 Title: Jammy update: v6.0.14 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.14 upstream stable release from git://git.kernel.org/ Linux 6.0.14 net: fec: properly guard irq coalesce setup ASoC: ops: Correct bounds check for second channel on SX controls nvme-pci: clear the prp2 field when not used perf: Fix perf_pending_task() UaF ASoC: cs42l51: Correct PGA Volume minimum value net: fec: don't reset irq coalesce settings to defaults on "ip link up" can: mcba_usb: Fix termination command argument can: sja1000: fix size of OCR_MODE_MASK define pinctrl: meditatek: Startup with the IRQs disabled libbpf: Use page size as max_entries when probing ring buffer map ASoC: ops: Check bounds for second channel in snd_soc_put_volsw_sx() ASoC: fsl_micfil: explicitly clear CHnF flags ASoC: fsl_micfil: explicitly clear software reset bit rtc: cmos: fix build on non-ACPI platforms libbpf: Fix uninitialized warning in btf_dump_dump_type_data x86/vdso: Conditionally export __vdso_sgx_enter_enclave() rtc: cmos: Fix wake alarm breakage rtc: cmos: Fix event handler registration ordering issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/2002673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
Build verified on Bionic for the debdiff provided above: https://launchpadlibrarian.net/650753152/18.04.4-5.debdiff -- 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/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Invalid Status in linux source package in Bionic: Incomplete Status in lttng-modules source package in Bionic: New Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: New Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: previous definition of ‘trace_jbd2_run_stats’ was here 778 21:14:39 DEBUG| [stdout] 243 | static inline void trace_##name(proto) \ 779 21:14:39 DEBUG| [stdout] | ^~ 780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: in expansion of macro ‘__DECLARE_TRACE’ 781 21:14:39 DEBUG| [stdout] 406 | __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \ 782 21:14:39 DEBUG| [stdout] | ^~~ 783 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:542:2: note: in expansion of macro ‘DECLARE_TRACE’
[Kernel-packages] [Bug 2002679] Re: Unset versioned gcc-12 for hwe-5.19 build
linux-generic-hwe-22.04: [0.00] Linux version 5.19.0-32-generic (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17) linux-lowlatency-hwe-22.04: [0.00] Linux version 5.19.0-1017-lowlatency (buildd@lcy02-amd64-110) (x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #18~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 27 15:36:48 UTC 2 (Ubuntu 5.19.0-1017.18~22.04.1-lowlatency 5.19.17) ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2002679 Title: Unset versioned gcc-12 for hwe-5.19 build Status in linux-hwe-5.19 package in Ubuntu: Invalid Status in linux-hwe-5.19 source package in Jammy: Fix Committed Bug description: [ Impact ] In order to use the same compiler as used for kinetic:linux (gcc-12) we have made some changes to explicitly compile jammy:linux-hwe-5.19 with the same compiler. These changes were mainly part of bug 1999750 and bug 1991664. However, such changes are breaking the build of a number of dkms packages. [ Fix ] The proposed temporary workaround is to revert commit "UBUNTU: [Packaging] use versioned gcc-12", which would make the kernel compile with the default GCC in Jammy (gcc-11), while a proper solution is being worked on. [ Where problems could occur ] gcc-12 is necessary to enable some of the new security-related kernel configs, so going back to gcc-11 will disable such features. However, this would not regress users when upgrading from the generic kernel to hwe-5.19 in Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2002679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004644] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2004644 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu Focal) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete ** Changed in: linux (Ubuntu Kinetic) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Invalid Status in linux source package in Bionic: Incomplete Status in lttng-modules source package in Bionic: New Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: New Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9,
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: New Status in lttng-modules package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in lttng-modules source package in Bionic: New Status in linux source package in Focal: New Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: New Status in lttng-modules source package in Jammy: New Status in linux source package in Kinetic: New Status in lttng-modules source package in Kinetic: New Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: previous definition of ‘trace_jbd2_run_stats’ was here 778 21:14:39 DEBUG| [stdout] 243 | static inline void trace_##name(proto) \ 779 21:14:39 DEBUG| [stdout] | ^~ 780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: in expansion of macro ‘__DECLARE_TRACE’ 781 21:14:39 DEBUG| [stdout] 406 | __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \ 782 21:14:39 DEBUG| [stdout] | ^~~ 783 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:542:2: note: in expansion of macro ‘DECLARE_TRACE’ 784 21:14:39 DEBUG| [stdout] 542 | DECLARE_TRACE(name, PARAMS(proto),
[Kernel-packages] [Bug 2006895] Re: kernel 5.15.0-60-generic out of memory on boot
Sadly, no, it didn't help me. But, wasn't this issue addressed in grub2 some time ago? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2006895 Title: kernel 5.15.0-60-generic out of memory on boot Status in linux-signed package in Ubuntu: New Bug description: Using kubuntu 22.04, and after a kernel update and after a reboot, the machine just spits out the "out of memory" message. The 5.15.0-58-generic works just fine. For what it's worth, I had the similar issue with the kernel prior to 58. Additionally, grub-efi-amd64-bin, grub-efi-amd64-signed, ubuntu-advantage-tools, update-notifier-common, software-properties-common and software-properties-qt updates are held back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2006895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002194] Re: minetest crashes
a recent dmesg snippet is:
[ 1438.094872] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:84db, in
minetest [8624]
[ 1438.094917] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on
rcs0
[ 1438.095694] i915 :00:02.0: [drm] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
[ 1438.096400] i915 :00:02.0: [drm] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
[ 1438.096467] i915 :00:02.0: [drm] minetest[8624] context reset due to GPU
hang
[ 1438.099582] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin
version 62.0 submission:enabled
[ 1438.099586] i915 :00:02.0: [drm] GuC SLPC: enabled
[ 1438.099588] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin
version 7.9 authenticated:yes
[ 1699.982301] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:84db, in
minetest:gdrv0 [8651]
[ 1699.982350] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on
rcs0
[ 1699.983133] i915 :00:02.0: [drm] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
[ 1699.983840] i915 :00:02.0: [drm] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
[ 1699.983888] i915 :00:02.0: [drm] minetest:gdrv0[8651] context reset due
to GPU hang
[ 1699.987801] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin
version 62.0 submission:enabled
[ 1699.987805] i915 :00:02.0: [drm] GuC SLPC: enabled
[ 1699.987806] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin
version 7.9 authenticated:yes
[ 2054.209190] perf: interrupt took too long (2538 > 2500), lowering
kernel.perf_event_max_sample_rate to 78750
[ 2232.970195] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:84db, in
minetest:gdrv0 [8651]
[ 2232.970241] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on
rcs0
[ 2232.971020] i915 :00:02.0: [drm] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
[ 2232.971726] i915 :00:02.0: [drm] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
[ 2232.971776] i915 :00:02.0: [drm] minetest:gdrv0[8651] context reset due
to GPU hang
[ 2232.975231] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin
version 62.0 submission:enabled
[ 2232.975234] i915 :00:02.0: [drm] GuC SLPC: enabled
[ 2232.975235] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin
version 7.9 authenticated:yes
--
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/2002194
Title:
minetest crashes
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hello, sometimes minetest hangs for tens of seconds, sometimes it just
crashes (interrupted (core dumped)), but sometimes it makes the
complete machine unrecoverably freeze which makes me believe it's a
kernel (gpu driver?) level issue.
steps to reproduce:
1, have an up-to-date ubuntu 22.04 lts installed
2. compile minetest from source: 587f6656a
3. play
expected result: user having fun, machine not crashing
actual result: machine crashing, hanging temporarily, game crashing
Thank you for the fix in advance.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-57-generic 5.15.0-57.63
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
Uname: Linux 5.15.0-57-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: imi3717 F pulseaudio
/dev/snd/controlC1: imi3717 F pulseaudio
/dev/snd/pcmC1D0p: imi3717 F...m pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 7 03:00:44 2023
InstallationDate: Installed on 2022-05-05 (246 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: Dell Inc. Latitude 5430
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=hu_HU.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic
root=/dev/mapper/vg_af1-root ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-5.15.0-57-generic N/A
linux-backports-modules-5.15.0-57-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2022
dmi.bios.release: 1.8
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.3
dmi.board.name: 04X33N
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
[Kernel-packages] [Bug 2007259] [NEW] Kernel 5.19.0-1013-raspi boots to blank screen (no gdm login shown)
Public bug reported: - Summary Kernel 5.19.0-1013-raspi boots to blank screen so no gdm login is shown. Previous kernel 5.19.0-1012-raspi boots to gdm login as expected. It's a Raspberry Pi 4 Model B Rev 1.4 - lsb_release -rd Description:Ubuntu 22.10 Release:22.10 - What you expected to happen Kernel 5.19.0-1013-raspi will boot to gdm login. - What happened instead Kernel 5.19.0-1013-raspi will boot to blank screen. Previous kernel 5.19.0-1012-raspi boots to gdm login as expected. I've attached these dmesg and journalctl log files to compare boot in 5.19.0-1013-raspi (BAD) and 5.19.0-1013-raspi (OK): - boot_5.19.0-1012-raspi_OK_dmesg.txt - boot_5.19.0-1012-raspi_OK_journalctl.txt - boot_5.19.0-1013-raspi_BAD_dmesg.txt - boot_5.19.0-1013-raspi_BAD_journalctl.txt ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Attachment added: "boot_5.19.0-1012-raspi_OK_dmesg.txt" https://bugs.launchpad.net/bugs/2007259/+attachment/5647041/+files/boot_5.19.0-1012-raspi_OK_dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2007259 Title: Kernel 5.19.0-1013-raspi boots to blank screen (no gdm login shown) Status in linux-raspi package in Ubuntu: New Bug description: - Summary Kernel 5.19.0-1013-raspi boots to blank screen so no gdm login is shown. Previous kernel 5.19.0-1012-raspi boots to gdm login as expected. It's a Raspberry Pi 4 Model B Rev 1.4 - lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 - What you expected to happen Kernel 5.19.0-1013-raspi will boot to gdm login. - What happened instead Kernel 5.19.0-1013-raspi will boot to blank screen. Previous kernel 5.19.0-1012-raspi boots to gdm login as expected. I've attached these dmesg and journalctl log files to compare boot in 5.19.0-1013-raspi (BAD) and 5.19.0-1013-raspi (OK): - boot_5.19.0-1012-raspi_OK_dmesg.txt - boot_5.19.0-1012-raspi_OK_journalctl.txt - boot_5.19.0-1013-raspi_BAD_dmesg.txt - boot_5.19.0-1013-raspi_BAD_journalctl.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2007259/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951422] Re: Ucore kernel snap size: netronome smartnic fw
For snaps this was actually fixed a while ago: https://git.launchpad.net/~canonical-kernel-snaps/+git/kernel-snaps-uc20/commit/?id=6d91407c39bfe31caf56291ce445f0084315f2b5 ** Changed in: linux-raspi (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1951422 Title: Ucore kernel snap size: netronome smartnic fw Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: Fix Released Bug description: [ Impact ] Pi kernel snaps are big in part due to included firmware binaries. A lot of these binaries are not needed/required by the Pi kernel. The size of the snap has a negative impact on boot speed. [ Fix ] Parse modinfo data from all modules to determine the list of required firmware files and remove the ones that are not necessary during snap build time. [ Test Case ] On core20 before: $ du -sh /lib/firmware/ 602M /lib/firmware/ And after: $ du -sh /lib/firmware/ 58M /lib/firmware/ [ Where Problems Could Occur ] We might accidentally drop needed firmware which might render the relevant HW unusable. Firmware load failures should be visible in the kernel log though. [ Original Description ] The size of the pi-kernel snap for UC20 is 254Mbytes (compressed) and 794Mbytes (uncompressed). 569Mbyte of this is caused by FW 140Mbyte -> Netronome SmartNIC Removing unreferenced FW and/or reducing number of drivers & their FW has exponential reduction of disk space usage. Additionally, downloaded image will be smaller; and storing 3x kernel snaps for upgrades will be smaller. Even more, snap seeding will be faster, so boot time will be faster. So it will be a nice gain in multiple aspects: download image, boot image, upgrade image, reboot image, start using image. stulluk ~/tmp $ ls -lah pi-kernel_353.snap -rw--- 1 stulluk stulluk 254M Kas 8 13:57 pi-kernel_353.snap stulluk ~/tmp $ cd pikern/ stulluk ~/tmp/pikern $ du -sh 794M . stulluk ~/tmp/pikern $ cd firmware/ stulluk ~/tmp/pikern/firmware $ du --block-size=MiB --max-depth=1 . | sort -rn 569MiB. 140MiB./netronome 40MiB ./amdgpu 34MiB ./intel 25MiB ./liquidio 24MiB ./qcom 20MiB ./qed 19MiB ./brcm 12MiB ./mellanox 12MiB ./dpaa2 12MiB ./ath10k ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1951422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951423] Re: Ucore kernel snap size: amd gpu fw
For snaps this was actually fixed a while ago: https://git.launchpad.net/~canonical-kernel-snaps/+git/kernel-snaps-uc20/commit/?id=6d91407c39bfe31caf56291ce445f0084315f2b5 ** Changed in: linux-raspi (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1951423 Title: Ucore kernel snap size: amd gpu fw Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: Fix Released Bug description: The size of the kernel snap for UC20 is 254Mbytes (compressed) and 794Mbytes (uncompressed). 569Mbyte of this is caused by FW 40Mbyte -> amdgpu IMO, removing unreferenced FW and/or reducing number of drivers & their FW has exponential reduction of disk space usage. Additionally, downloaded image will be smaller; and storing 3x kernel snaps for upgrades will be smaller. Even more, snap seeding will be faster, so boot time will be faster. So it will be a nice gain in multiple aspects: download image, boot image, upgrade image, reboot image, start using image. stulluk ~/tmp $ ls -lah pi-kernel_353.snap -rw--- 1 stulluk stulluk 254M Kas 8 13:57 pi-kernel_353.snap stulluk ~/tmp $ cd pikern/ stulluk ~/tmp/pikern $ du -sh 794M . stulluk ~/tmp/pikern $ cd firmware/ stulluk ~/tmp/pikern/firmware $ du --block-size=MiB --max-depth=1 . | sort -rn 569MiB. 140MiB./netronome 40MiB ./amdgpu 34MiB ./intel 25MiB ./liquidio 24MiB ./qcom 20MiB ./qed 19MiB ./brcm 12MiB ./mellanox 12MiB ./dpaa2 12MiB ./ath10k ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1951423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958518] Re: split some large, lesser-used firmware files into -extra package
Did this work in the past? Can you try older kernels? -- 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/1958518 Title: split some large, lesser-used firmware files into -extra package Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Confirmed Bug description: The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006895] Re: kernel 5.15.0-60-generic out of memory on boot
Have the same situation. This helps me https://unix.stackexchange.com/a/698895/414225 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2006895 Title: kernel 5.15.0-60-generic out of memory on boot Status in linux-signed package in Ubuntu: New Bug description: Using kubuntu 22.04, and after a kernel update and after a reboot, the machine just spits out the "out of memory" message. The 5.15.0-58-generic works just fine. For what it's worth, I had the similar issue with the kernel prior to 58. Additionally, grub-efi-amd64-bin, grub-efi-amd64-signed, ubuntu-advantage-tools, update-notifier-common, software-properties-common and software-properties-qt updates are held back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2006895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958518] Re: split some large, lesser-used firmware files into -extra package
to make my case once more: - Debian is more modular, what is the reason we don't follow what upstream does here? - the size of the package leads to problems as evidenced in bug 1951422 and bug 1951423 - it should be possible to carve out the larger bits into a separate package without making life hard for people who need those bits -> everybody happy -- 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/1958518 Title: split some large, lesser-used firmware files into -extra package Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Confirmed Bug description: The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2004534] Re: Lenovo IdeaPad 3 15ABA7 never wakes from sleep
OK, i disabled all suspend and dim of the screen. no sleep at all. after 10-12h the when i started to work with the system suddenly the cursor of the mouse became square and couldn't start anything neither with kbd or the nouse, nor i could reboot or shut down. the only exit is the power button. Any ideas? On Mon, Feb 13, 2023 at 10:50 AM Daniel van Vugt <2004...@bugs.launchpad.net> wrote: > Also, comment #numbers can be found on this page: > https://launchpad.net/bugs/2004534 > > That's probably easier to follow than email. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2004534 > > Title: > Lenovo IdeaPad 3 15ABA7 never wakes from sleep > > Status in linux package in Ubuntu: > Confirmed > > Bug description: >- on locked screen: the keyboard blocks after a while and I cannot > login anymore; >- on unlocked screen: >= apps do not start (failed to start); >= no icon pictures on desktop; >= no wallpaper anymore (black background); > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: xorg 1:7.7+23ubuntu2 > ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 > Uname: Linux 5.15.0-58-generic x86_64 > ApportVersion: 2.20.11-0ubuntu82.3 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: pass > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Thu Feb 2 07:15:13 2023 > DistUpgraded: Fresh install > DistroCodename: jammy > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, including running git bisection searches > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c2) > (prog-if 00 [VGA controller]) > Subsystem: Lenovo Device [17aa:3801] > InstallationDate: Installed on 2023-02-01 (1 days ago) > InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 > (20220809.1) > MachineType: LENOVO 82RN > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic > root=UUID=b63af605-bd2f-4b16-8bb4-1cc9bb85554c ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/04/2022 > dmi.bios.release: 1.38 > dmi.bios.vendor: LENOVO > dmi.bios.version: JTCN38WW > dmi.board.asset.tag: No Asset Tag > dmi.board.name: LNVNB161216 > dmi.board.vendor: LENOVO > dmi.board.version: NO DPK > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: IdeaPad 3 15ABA7 > dmi.ec.firmware.release: 1.38 > dmi.modalias: > dmi:bvnLENOVO:bvrJTCN38WW:bd08/04/2022:br1.38:efr1.38:svnLENOVO:pn82RN:pvrIdeaPad315ABA7:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315ABA7:skuLENOVO_MT_82RN_BU_idea_FM_IdeaPad315ABA7: > dmi.product.family: IdeaPad 3 15ABA7 > dmi.product.name: 82RN > dmi.product.sku: LENOVO_MT_82RN_BU_idea_FM_IdeaPad 3 15ABA7 > dmi.product.version: IdeaPad 3 15ABA7 > dmi.sys.vendor: LENOVO > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.110-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20210115-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.17-2build1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004534/+subscriptions > > -- 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/2004534 Title: Lenovo IdeaPad 3 15ABA7 never wakes from sleep Status in linux package in Ubuntu: Confirmed Bug description: - on locked screen: the keyboard blocks after a while and I cannot login anymore; - on unlocked screen: = apps do not start (failed to start); = no icon pictures on desktop; = no wallpaper anymore (black background); ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 2 07:15:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI]
