[Kernel-packages] [Bug 1982104] Re: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- 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/1982104 Title: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server which is targeting Telco workloads. Attaching the console logs. Currently, it looks like disabling VT-D option in BIOS settings helps mitigate the issue. Console logs indicate something is wrong in iommu/dmar subsystem. [Fix] The IOMMU driver shares the pasid table for PCI alias devices. When the RID2PASID entry of the shared pasid table has been filled by the first device, the subsequent device will encounter the "DMAR: Setup RID2PASID failed" failure as the pasid entry has already been marked as present. As the result, the IOMMU probing process will be aborted. On the contrary, when any alias device is hot-removed from the system, for example, by writing to /sys/bus/pci/devices/.../remove, the shared RID2PASID will be cleared without any notifications to other devices. As the result, any DMAs from those rest devices are blocked. Sharing pasid table among PCI alias devices could save two memory pages for devices underneath the PCIe-to-PCI bridges. Anyway, considering that those devices are rare on modern platforms that support VT-d in scalable mode and the saved memory is negligible, it's reasonable to remove this part of immature code to make the driver feasible and stable. [Test Case] 1. use the target machine(Intel Sapphire Rapids) and install the kernel with the fix. 2. boot the target machine 3. check dmesg if the error message exists [ 8.120527] pci :03:01.0: DMAR: Setup RID2PASID failed [Where problems could occur] After enable intel_iommu, the errors may be occurred. We need to figure out one by one once the related errors are triggered in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975454] Re: [Dell XPS 15 7590] Cannot resume after suspend
Philippe, please open a new bug from that machine by running: ubuntu-bug linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975454 Title: [Dell XPS 15 7590] Cannot resume after suspend Status in linux package in Ubuntu: Incomplete Bug description: For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text: ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` (There might be typos, I retyped it from a photo) Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous session. I noticed it seemed to happen since 22.04 came out of beta, but the timing also coincides with me starting using a Bluetooth mouse, so that might be connected. Let me know if you need more information or digging into the logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.129.06 Thu May 12 22:52:02 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 23 08:44:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905] Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905] InstallationDate: Installed on 2020-04-03 (779 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982319] [NEW] DELL XPS-15-9500 fails to resume after suspend
Public bug reported: On Ubuntu 22.04, after a suspend (lid close) the system does not wake up any more. I have to hard-resetthe system to reboot. I have a Dell XPS-15 9500 with Nvidia Drivers 515 (they are probably the cause of the issue). Description:Ubuntu 22.04 LTS Release:22.04 see also: https://bugs.launchpad.net/bugs/1975454 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 2022 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 20 10:12:46 2022 InstallationDate: Installed on 2022-07-03 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=809645c5-d7c6-4ae8-9a08-351edabdbb7b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2022 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd05/13/2022:br1.15:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1982319 Title: DELL XPS-15-9500 fails to resume after suspend Status in linux package in Ubuntu: New Bug description: On Ubuntu 22.04, after a suspend (lid close) the system does not wake up any more. I have to hard-resetthe system to reboot. I have a Dell XPS-15 9500 with Nvidia Drivers 515 (they are probably the cause of the issue). Description: Ubuntu 22.04 LTS Release: 22.04 see also: https://bugs.launchpad.net/bugs/1975454 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 2022 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 20 10:12:46 2022 InstallationDate: Installed on 2022-07-03 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=809645c5-d7c6-4ae8-9a08-351edabdbb7b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2022 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd05/13/2022:br1.15:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975454] Re: [Dell XPS 15 7590] Cannot resume after suspend
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982319 -- 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/1975454 Title: [Dell XPS 15 7590] Cannot resume after suspend Status in linux package in Ubuntu: Incomplete Bug description: For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text: ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` (There might be typos, I retyped it from a photo) Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous session. I noticed it seemed to happen since 22.04 came out of beta, but the timing also coincides with me starting using a Bluetooth mouse, so that might be connected. Let me know if you need more information or digging into the logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.129.06 Thu May 12 22:52:02 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 23 08:44:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905] Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905] InstallationDate: Installed on 2020-04-03 (779 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982319] Re: DELL XPS-15-9500 fails to resume after suspend
Attaxched is the boot log of the session where the but happened. The relevant section is: Jul 20 08:21:07 philippe-XPS-15 systemd-logind[805]: Lid opened. Jul 20 08:21:09 philippe-XPS-15 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Jul 20 08:21:20 philippe-XPS-15 gsd-power[2784]: Failed to acquire idle monitor proxy: Timeout was reached Jul 20 08:21:20 philippe-XPS-15 gsd-power[2784]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24) Jul 20 08:21:20 philippe-XPS-15 gsd-power[2784]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24) Jul 20 08:21:20 philippe-XPS-15 gsd-power[2784]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24) Jul 20 08:21:20 philippe-XPS-15 systemd[1]: Reached target Sleep. Jul 20 08:21:20 philippe-XPS-15 systemd[1]: Starting Record successful boot for GRUB... Jul 20 08:21:20 philippe-XPS-15 systemd[1]: Starting NVIDIA system suspend actions... Jul 20 08:21:20 philippe-XPS-15 suspend[8292]: nvidia-suspend.service Jul 20 08:21:20 philippe-XPS-15 logger[8292]: <13>Jul 20 08:21:20 suspend: nvidia-suspend.service Jul 20 08:21:20 philippe-XPS-15 systemd[1]: grub-common.service: Deactivated successfully. Jul 20 08:21:20 philippe-XPS-15 systemd[1]: Finished Record successful boot for GRUB. Jul 20 08:21:20 philippe-XPS-15 systemd[1]: Starting GRUB failed boot detection... Jul 20 08:21:20 philippe-XPS-15 systemd[1]: grub-initrd-fallback.service: Deactivated successfully. Jul 20 08:21:20 philippe-XPS-15 systemd[1]: Finished GRUB failed boot detection. Jul 20 08:21:28 philippe-XPS-15 gsd-color[2772]: failed to set xrandr-Sharp Corporation color transform matrix: Timeout was reached Jul 20 08:21:29 philippe-XPS-15 systemd-logind[805]: Power key pressed. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982319/+attachment/5604278/+files/prevboot.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/1982319 Title: DELL XPS-15-9500 fails to resume after suspend Status in linux package in Ubuntu: New Bug description: On Ubuntu 22.04, after a suspend (lid close) the system does not wake up any more. I have to hard-resetthe system to reboot. I have a Dell XPS-15 9500 with Nvidia Drivers 515 (they are probably the cause of the issue). Description: Ubuntu 22.04 LTS Release: 22.04 see also: https://bugs.launchpad.net/bugs/1975454 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 2022 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 20 10:12:46 2022 InstallationDate: Installed on 2022-07-03 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=809645c5-d7c6-4ae8-9a08-351edabdbb7b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2022 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd05/13/2022:br1.15:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982319] 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/1982319 Title: DELL XPS-15-9500 fails to resume after suspend Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 22.04, after a suspend (lid close) the system does not wake up any more. I have to hard-resetthe system to reboot. I have a Dell XPS-15 9500 with Nvidia Drivers 515 (they are probably the cause of the issue). Description: Ubuntu 22.04 LTS Release: 22.04 see also: https://bugs.launchpad.net/bugs/1975454 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 2022 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 20 10:12:46 2022 InstallationDate: Installed on 2022-07-03 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=809645c5-d7c6-4ae8-9a08-351edabdbb7b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2022 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd05/13/2022:br1.15:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982319] Re: DELL XPS-15-9500 fails to resume after suspend
Does that log show it sleeping twice? Jul 19 23:00 - System is suspended Jul 20 08:20 - System wakes up Jul 20 08:21 - Lid opened and system put to sleep again? -- 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/1982319 Title: DELL XPS-15-9500 fails to resume after suspend Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 22.04, after a suspend (lid close) the system does not wake up any more. I have to hard-resetthe system to reboot. I have a Dell XPS-15 9500 with Nvidia Drivers 515 (they are probably the cause of the issue). Description: Ubuntu 22.04 LTS Release: 22.04 see also: https://bugs.launchpad.net/bugs/1975454 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 2022 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 20 10:12:46 2022 InstallationDate: Installed on 2022-07-03 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=809645c5-d7c6-4ae8-9a08-351edabdbb7b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2022 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd05/13/2022:br1.15:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982319] Re: DELL XPS-15-9500 fails to resume after suspend
What I did was: open the lid -> system did not wake properly close lid -> system did not go back to sleep either open lid -> system was still in the same state press and hold power button for hard reset -> system rebooted -- 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/1982319 Title: DELL XPS-15-9500 fails to resume after suspend Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 22.04, after a suspend (lid close) the system does not wake up any more. I have to hard-resetthe system to reboot. I have a Dell XPS-15 9500 with Nvidia Drivers 515 (they are probably the cause of the issue). Description: Ubuntu 22.04 LTS Release: 22.04 see also: https://bugs.launchpad.net/bugs/1975454 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 2022 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 20 10:12:46 2022 InstallationDate: Installed on 2022-07-03 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=809645c5-d7c6-4ae8-9a08-351edabdbb7b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2022 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd05/13/2022:br1.15:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981669] Re: After updated from linux-image-5.14.0-1042-oem VirtualBox VMs started crashing
i can confirm the bug. things i tried that did not help: - reducing guest CPUs to 1 - turning off hardware acceleration for the guest VM - setting kernel parameter "split_lock_detect=off" with kernel 5.15.0-41-generic no VM crashes (windows 10) so far. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1981669 Title: After updated from linux-image-5.14.0-1042-oem VirtualBox VMs started crashing Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: With kernel linux-image-5.14.0-1042-oem VirtualBox VM runs stable With kernel linux-image-5.14.0-1044-oem VirtualBox VM crashed constantly Wiht kernel linux-image-5.14.0-1045-oem VirtualBox VM crash multiple times a day ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1045-oem 5.14.0-1045.51 ProcVersionSignature: Ubuntu 5.14.0-1045.51-oem 5.14.21 Uname: Linux 5.14.0-1045-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Jul 14 09:15:24 2022 InstallationDate: Installed on 2021-07-22 (356 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1981669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981074] Re: Drivers with unsatisfied dependencies on the Allwinner D1
This bug was fixed in the package linux-allwinner-5.17 - 5.17.0-1003.3 --- linux-allwinner-5.17 (5.17.0-1003.3) jammy; urgency=medium * jammy/linux-allwinner-5.17: 5.17.0-1003.3 -proposed tracker (LP: #1981729) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.06.20) * CVE-2022-1679 - SAUCE: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * Drivers with unsatisfied dependencies on the Allwinner D1 (LP: #1981074) - phy: sun4i-usb: Rework HCI PHY (aka "pmu_unk1") handling - SAUCE: phy: sun4i-usb: Add D1 variant - SAUCE: PM / devfreq: Add dummy R329/D1 MBUS driver - [Config] Enable additional Allwinner D1 options * Miscellaneous Ubuntu changes - [Config] review-master-changes: apply config updates [ Ubuntu: 5.17.0-8.8~22.04.6 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.6 -proposed tracker (LP: #1980479) * Jammy update: v5.17.15 upstream stable release (LP: #1980389) - pcmcia: db1xxx_ss: restrict to MIPS_DB1XXX boards - staging: greybus: codecs: fix type confusion of list iterator variable - iio: adc: ad7124: Remove shift from scan_type - lkdtm/bugs: Check for the NULL pointer after calling kmalloc - lkdtm/bugs: Don't expect thread termination without CONFIG_UBSAN_TRAP - tty: goldfish: Use tty_port_destroy() to destroy port - tty: serial: owl: Fix missing clk_disable_unprepare() in owl_uart_probe - tty: n_tty: Restore EOF push handling behavior - serial: 8250_aspeed_vuart: Fix potential NULL dereference in aspeed_vuart_probe - tty: serial: fsl_lpuart: fix potential bug when using both of_alias_get_id and ida_simple_get - remoteproc: imx_rproc: Ignore create mem entry for resource table - phy: rockchip-inno-usb2: Fix muxed interrupt support - usb: usbip: fix a refcount leak in stub_probe() - usb: usbip: add missing device lock on tweak configuration cmd - USB: storage: karma: fix rio_karma_init return - usb: musb: Fix missing of_node_put() in omap2430_probe - staging: fieldbus: Fix the error handling path in anybuss_host_common_probe() - pwm: lp3943: Fix duty calculation in case period was clamped - pwm: raspberrypi-poe: Fix endianness in firmware struct - rpmsg: qcom_smd: Fix irq_of_parse_and_map() return value - usb: dwc3: gadget: Replace list_for_each_entry_safe() if using giveback - usb: dwc3: pci: Fix pm_runtime_get_sync() error checking - scripts/get_abi: Fix wrong script file name in the help message - misc: fastrpc: fix an incorrect NULL check on list iterator - firmware: stratix10-svc: fix a missing check on list iterator - usb: typec: mux: Check dev_set_name() return value - rpmsg: virtio: Fix possible double free in rpmsg_probe() - rpmsg: virtio: Fix possible double free in rpmsg_virtio_add_ctrl_dev() - rpmsg: virtio: Fix the unregistration of the device rpmsg_ctrl - iio: adc: stmpe-adc: Fix wait_for_completion_timeout return value check - iio: proximity: vl53l0x: Fix return value check of wait_for_completion_timeout - iio: adc: sc27xx: fix read big scale voltage not right - iio: adc: sc27xx: Fine tune the scale calibration values - rpmsg: qcom_smd: Fix returning 0 if irq_of_parse_and_map() fails - misc/pvpanic: Convert regular spinlock into trylock on panic path - phy: qcom-qmp: fix pipe-clock imbalance on power-on failure - power: supply: axp288_fuel_gauge: Drop BIOS version check from "T3 MRD" DMI quirk - power: supply: ab8500_fg: Allocate wq in probe - serial: sifive: Report actual baud base rather than fixed 115200 - export: fix string handling of namespace in EXPORT_SYMBOL_NS - watchdog: rzg2l_wdt: Fix 32bit overflow issue - watchdog: rzg2l_wdt: Fix Runtime PM usage - watchdog: rzg2l_wdt: Fix 'BUG: Invalid wait context' - watchdog: rzg2l_wdt: Fix reset control imbalance - soundwire: intel: prevent pm_runtime resume prior to system suspend - coresight: cpu-debug: Replace mutex with mutex_trylock on panic notifier - ksmbd: fix reference count leak in smb_check_perm_dacl() - extcon: ptn5150: Add queue work sync before driver release - dt-bindings: remoteproc: mediatek: Make l1tcm reg exclusive to mt819x - soc: rockchip: Fix refcount leak in rockchip_grf_init - clocksource/drivers/riscv: Events are stopped during CPU suspend - ARM: dts: aspeed: ast2600-evb: Enable RX delay for MAC0/MAC1 - rtc: mt6397: check return value after calling platform_get_resource() - rtc: ftrtc010: Fix error handling in ftrtc010_rtc_probe - staging: r8188eu: add check for kzalloc - serial: meson: acquire port->lock in startup() - serial: 8250_fintek: Check SER_RS485_RTS_* only with RS485 - serial: cpm_uart: Fix build error without CONFIG_SERIAL_CPM_CONSOLE - serial: u
[Kernel-packages] [Bug 1953613] Re: GPIO character device API not enabled in kernel
** Description changed: + [Impact] + + * The libgpiod2 library and gpiod tools shipped in Jammy don't work. + + * These tools are meant to replace the old sysfs interface and be +a better and more efficient way to manipulate GPIOs from userspace. +Unfortunately the latest release is still using v1 of the character +device kernel API which is not enabled in Ubuntu kernels. + + * This is Kent Gibsons reply on the linux-gpio mailing list: + + On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote: + > Hi, + > + > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the + > libgpiod package that we ship is still based on the latest version + > 1.6.3 which does not implement the API v2. So I'd like to update + > libgpiod, do you have any recommendations about what branch/sha1 I + > should use? Do you plan to make a release that implements the API v2? + > + + Firstly, libgpiod is Bart's library so he is the authority, but this + is my understanding... + + TLDR: You should keep GPIO_CDEV_V1 enabled. + + v1 is deprecated from a development perspective, so all new feature + development will occur on v2, and new applications should target v2. + Existing apps targetting v1, be that directly or via libgpiod v1.6.3, + will require GPIO_CDEV_V1 until they migrate to v2. + The mainline kernel will continue to support v1 while userspace + transitions. + + libgpiod v2 is in active development, and should reach its first release + shortly. + Note that it is NOT a plugin replacement for v1. It has a different API, + for similar reasons to why we had to switch in the kernel, so apps will + need to be actively migrated. + + I wouldn't suggest making any effort to package libgpiod v2 until Bart + makes an official release. + + Cheers, + Kent. + + [Test Plan] + + * Run gpioinfo on a machine with exposed GPIOs and check that it lists +the GPIOs and doesn't error with + +gpioinfo: error creating line iterator: Invalid argument + + [Where problems could occur] + + * There may be code and scripts that hasn't been tested with a working +libgpiod2/gpiod tools and uncover latent bugs. + + [Other Info] + + Original bug text: + The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * The libgpiod2 library and gpiod tools shipped in Jammy don't work. * These tools are meant to replace the old sysfs interface and be a better and more efficient way to manipulate GPIOs from userspace. Unfortunately the latest release is still using v1 of the character device kernel API which is not enabled in Ubuntu kernels. * This is Kent Gibsons reply on the linux-gpio mail
[Kernel-packages] [Bug 1977764] Re: kernel modules "zstd" and "z3fold" missing.
** Also affects: ubuntu-seeds Importance: Undecided Status: New ** Changed in: ubuntu-seeds Assignee: (unassigned) => Dave Jones (waveform) -- 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/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in Ubuntu Seeds: New Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: Invalid Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: Invalid Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981577] Re: Azure: Add support for multi-MSI
This bug is awaiting verification that the linux-azure/5.4.0-1087.92 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1981577 Title: Azure: Add support for multi-MSI Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] The Hyper-V vPCI driver (pci-hyperv) doesn't work with a PCIe devcie that supports multiple MSI interrupts (Note: MSI-X has been working fine). Recently Jeffrey Hugo made 4 patches to the vPCI driver so multiple-MSI can work now. Please consider picking up the 4 patches into the linux-azure kernels for Ubuntu LTS 18.04, 20.04 and 22.04: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=08e61e861a0e47e5e1a3fb78406afd6b0cea6b6d https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=455880dfe292a2bdd3b4ad6a107299fce610e64b https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b4b8ecc5bfbd4e77de1b2fd5c1dd3c655f1f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a2bad844a67b1c7740bda63e87453baf63c3a7f7 Microsoft is working to bring up a Qualcomm PCIe device to Linux VMs running on Azure. We need the 4 patches for the device to work on Azure/Hyper-V. [Test Plan] Microsoft tested [Where things could go wrong] MSI vectors could be mis-wired or ignored. [Other Info] SF: #00339521 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1981577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981968] Re: bcmwl fails to build on the latest kinetic kernel 5.19
** Changed in: bcmwl (Ubuntu Kinetic) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: bcmwl (Ubuntu Kinetic) Status: New => In Progress ** Changed in: bcmwl (Ubuntu Kinetic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1981968 Title: bcmwl fails to build on the latest kinetic kernel 5.19 Status in bcmwl package in Ubuntu: In Progress Status in bcmwl source package in Kinetic: In Progress Bug description: [Impact] bcmwl fails to build on kernel 5.19 with the following errors: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:603:14: error: implicit declaration of function ‘pci_alloc_consistent’; did you mean ‘osl_dma_alloc_consistent’? [-Werror=implicit-function-declaration] 603 | va = pci_alloc_consistent(osh->pdev, size, (dma_addr_t*)pap); | ^~~~ | osl_dma_alloc_consistent /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3307:26: error: implicit declaration of function ‘PDE_DATA’; did you mean ‘NODE_DATA’? [-Werror=implicit-function-declaration] 3307 | wl_info_t * wl = PDE_DATA(file_inode(filp)); | ^~~~ | NODE_DATA /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In function ‘osl_dma_map’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:626:38: error: ‘PCI_DMA_TODEVICE’ undeclared (first use in this function); did you mean ‘DMA_TO_DEVICE’? 626 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: PCI_DMA_FROMDEVICE; | ^~~~ | DMA_TO_DEVICE /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:626:38: note: each undeclared identifier is reported only once for each function it appears in /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:626:56: error: ‘PCI_DMA_FROMDEVICE’ undeclared (first use in this function); did you mean ‘DMA_FROM_DEVICE’? 626 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: PCI_DMA_FROMDEVICE; | ^~ |DMA_FROM_DEVICE /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:659:17: error: implicit declaration of function ‘pci_map_single’; did you mean ‘dma_map_single’? [-Werror=implicit-function-declaration] 659 | return (pci_map_single(osh->pdev, va, size, dir)); | ^~ | dma_map_single /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In function ‘osl_dma_unmap’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:668:38: error: ‘PCI_DMA_TODEVICE’ undeclared (first use in this function); did you mean ‘DMA_TO_DEVICE’? 668 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: PCI_DMA_FROMDEVICE; | ^~~~ | DMA_TO_DEVICE /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:668:56: error: ‘PCI_DMA_FROMDEVICE’ undeclared (first use in this function); did you mean ‘DMA_FROM_DEVICE’? 668 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: PCI_DMA_FROMDEVICE; | ^~ |DMA_FROM_DEVICE /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:669:9: error: implicit declaration of function ‘pci_unmap_single’; did you mean ‘dma_unmap_single’? [-Werror=implicit-function-declaration] 669 | pci_unmap_single(osh->pdev, (uint32)pa, size, dir); | ^~~~ | dma_unmap_single [Test case] $ sudo apt install bcmwl-kernel-source [Fix] Patch bcmwl to support the new 5.18+ kernel ABI (PCI/DMA-related functions). [Regression potential] We may experience regressions with bcmwl in kernels >= 5.18. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1981968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981658] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008
@squirrelsc - Kernels with this fix are due for release Aug 1, 2022. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024] start_secondary+0x166/0x1c0 | [ 351.103977] secondary_startup_64+0xa4/0xb0 | [ 351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_table
[Kernel-packages] [Bug 1982357] [NEW] i2c-mlxbf.c: fix wrong variable name
Public bug reported: SRU Justification: [Impact] We are using the wrong variable name priv->smbus->io instead of priv->mst_cause->io. This could result in unexpected i2c behavior. [Fix] * replace priv->smbus->io with priv->mst_cause->io [Test Case] * Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created * check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course) [Regression Potential] Any of the test cases above could be impacted due to these changes. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1982357 Title: i2c-mlxbf.c: fix wrong variable name Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] We are using the wrong variable name priv->smbus->io instead of priv->mst_cause->io. This could result in unexpected i2c behavior. [Fix] * replace priv->smbus->io with priv->mst_cause->io [Test Case] * Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created * check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course) [Regression Potential] Any of the test cases above could be impacted due to these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1982357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981669] Re: After updated from linux-image-5.14.0-1042-oem VirtualBox VMs started crashing
Today I installed the latest Virtualbox: 3.1.36r152435. So I figured I give it a try and the Windows VM is running stable since 1,5 h on 5.14.0-1045-oem. If it keeps running for the rest of today, I'll give it a full day test tomorrow and report back. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1981669 Title: After updated from linux-image-5.14.0-1042-oem VirtualBox VMs started crashing Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: With kernel linux-image-5.14.0-1042-oem VirtualBox VM runs stable With kernel linux-image-5.14.0-1044-oem VirtualBox VM crashed constantly Wiht kernel linux-image-5.14.0-1045-oem VirtualBox VM crash multiple times a day ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1045-oem 5.14.0-1045.51 ProcVersionSignature: Ubuntu 5.14.0-1045.51-oem 5.14.21 Uname: Linux 5.14.0-1045-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Jul 14 09:15:24 2022 InstallationDate: Installed on 2021-07-22 (356 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1981669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980145] Re: New upstream release 2022.06.06
I can see how that's a bit confusing; possibly I should be handling the backport changelogs differently. But yes, I did not remove the Suggests: crda in the backports except in jammy where the crda package had also been removed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1980145 Title: New upstream release 2022.06.06 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Impish: In Progress Status in wireless-regdb source package in Jammy: Fix Committed Status in wireless-regdb source package in Kinetic: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1980145/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980145] Re: New upstream release 2022.06.06
The autopkgtest failure for linux-oracle is a timeout during the rebuild test. Clearly this isn't caused by the wireless-regdb update, so the test should be retried or hinted (I can do neither). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1980145 Title: New upstream release 2022.06.06 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Impish: In Progress Status in wireless-regdb source package in Jammy: Fix Committed Status in wireless-regdb source package in Kinetic: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1980145/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980145] Re: New upstream release 2022.06.06
I tested the jammy, focal, and bionic patches as described in the test case from the description. The kernel was able to load the database, and I was able to successfully query and change the regulatory domain. Marking verification as done. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1980145 Title: New upstream release 2022.06.06 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Impish: In Progress Status in wireless-regdb source package in Jammy: Fix Committed Status in wireless-regdb source package in Kinetic: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1980145/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981901] Re: Weird behavior on display, since kernel versions 5.15.x
@vanvugt Thanks, will see... * I have to wait until >= 5.15.0-40 is available or set the kernel parameter, but how/where to set it? * I'm not sure if I use Xorg, but assume that is the default in Lubuntu. Where/how to check if Xorg ist used? And usually I would use the new stuff, so what is the old Intel graphics driver and what is the new one? How to switch between old and new? I read in regards to xserver-xorg-video-intel: This package is built from the X.org xf86-video-intel driver module. The use of this driver is discouraged if your GPU is new enough (ca. 2007 and newer). Mine is an Intel Celereon J4105 with Intel UHD 600 (which is from 2017), so I can remove in fact xserver-xorg-video-intel. After removal my Lubuntu Kinetic uses the Intel graphics drivers which are in the kernel? The only thing I see in Lubuntu > Preferences > LXQt Settings > Window Effects are the 2 options: X Render and GLX (OpenGL)... I selected GLX (OpenGL). But I think, that is not what you mean, this is only related to window effects when Compton is used, I understand. * I dont't have a laptop, I have a mini-pc and use an external monitor via HDMI. Anyway, where to set that parameter, just to try out? -- 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/1981901 Title: Weird behavior on display, since kernel versions 5.15.x Status in linux package in Ubuntu: Incomplete Bug description: Since kernel versions 5.15.x I have a problem with graphics unit and display on screen. I described it first time here https://discourse.lubuntu.me/t/lubuntu-jammy-weird-artifacts-on- display-choose-older-kernel-version-to-boot-with/3034 and recently here https://discourse.lubuntu.me/t/weird-behavior-on-display-since-kernel- versions-5-15-x/3446 Don't know what information else to provide, please advice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970127] Re: Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7 3700U)
I also have the same issue on my HP Aero 13-be0xxx (AMD Ryzen 5 5600U). Strangely enough, but the system always boots just fine if I insert a USB-drive into laptop's Type-C port. Works for both the live/installer system and the installed one. The Type-A ports don't do this magic, only the Type-C one. If I remove the USB-drive, the installed system fails to boot with these errors in logs: ucsi_acpi USBC000:00: UCSI_GET_PDOS returned 0 bytes BUG: kernel NULL pointer dereference, address: 0058 #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page I have no idea, why the trick with Type-C port works, possibly the bug is somewhere in thunderbolt or USB drivers? -- 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/1970127 Title: Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7 3700U) Status in linux package in Ubuntu: Confirmed Bug description: The ubuntu-22.04-desktop-amd64.iso live cd does not boot on a HP ENVY X360 notebook (Ryzen 7 3700U). Model: HP ENVY X360 13-ar0777ng 9YN58EA#ABD After a few minutes the screen simply switches to black. No possibility to get a console by pressing CTRL-ALT-F1, F2, ... I removed the boot options "quiet splash" and recorded the boot via video. (just ask if you need the full video) I attach a significantly looking screenshot from that video, showing a kernel bug message. Currently the notebook runs with Ubuntu-20.04 using the Linux-5.11 HWE kernel. But suspend to memory isn't working. Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] Re: GPIO character device v1 API not enabled in kernel
** Summary changed: - GPIO character device API not enabled in kernel + GPIO character device v1 API not enabled in 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/1953613 Title: GPIO character device v1 API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * The libgpiod2 library and gpiod tools shipped in Jammy don't work. * These tools are meant to replace the old sysfs interface and be a better and more efficient way to manipulate GPIOs from userspace. Unfortunately the latest release is still using v1 of the character device kernel API which is not enabled in Ubuntu kernels. * This is Kent Gibsons reply on the linux-gpio mailing list: On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote: > Hi, > > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the > libgpiod package that we ship is still based on the latest version > 1.6.3 which does not implement the API v2. So I'd like to update > libgpiod, do you have any recommendations about what branch/sha1 I > should use? Do you plan to make a release that implements the API v2? > Firstly, libgpiod is Bart's library so he is the authority, but this is my understanding... TLDR: You should keep GPIO_CDEV_V1 enabled. v1 is deprecated from a development perspective, so all new feature development will occur on v2, and new applications should target v2. Existing apps targetting v1, be that directly or via libgpiod v1.6.3, will require GPIO_CDEV_V1 until they migrate to v2. The mainline kernel will continue to support v1 while userspace transitions. libgpiod v2 is in active development, and should reach its first release shortly. Note that it is NOT a plugin replacement for v1. It has a different API, for similar reasons to why we had to switch in the kernel, so apps will need to be actively migrated. I wouldn't suggest making any effort to package libgpiod v2 until Bart makes an official release. Cheers, Kent. [Test Plan] * Run gpioinfo on a machine with exposed GPIOs and check that it lists the GPIOs and doesn't error with gpioinfo: error creating line iterator: Invalid argument [Where problems could occur] * There may be code and scripts that hasn't been tested with a working libgpiod2/gpiod tools and uncover latent bugs. [Other Info] Original bug text: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter
** Description changed: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] - spin up azure vm + Create VM on Azure - sudo apt-get install azure-cli + Install crash dump utilies (from guide: + https://ubuntu.com/server/docs/kernel-crash-dump) sudo apt install linux-crashdump Say (y) to all questions during install - reboot + Reboot the VM + As root on the VM after reboot: kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1085-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1085-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1085-azure root=UUID=a117a689-aa1d-4cdc-8a30-7b9fbf174437 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline - crashkernel=512M-:192M + ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System RAM: 4095MB) cat /proc/sys/kernel/sysrq # make sure this value is greater than 0 + #set it to 1 sudo sysctl -w kernel.sysrq=1 - #set it to 1 - + Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su - echo c > sysrq-trigger + echo c > /proc/sysrq-trigger - #kdump doesnt work on Azure and hangs indefiantly - #reboot VM + #kdump doesnt work and hangs indefinitely + #force reboot VM from Azure console + Outcome after removing "ata_piix.prefer_ms_hyperv=0" in kexec command: + # perform crash + sudo su + echo c > /proc/sysrq-trigger + + #kdump works, VM eventually (several minutes) reboots + # Login to VM and check that there is a core file in /var/crash: + ls /var/crash [Where Problems Could Occur] This change modifies the debian/rules. The package could fail to build properly if mistyped. [Other] Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0" parameter. - target series - Kinetic-> Bionic + target series - Kinetic -> Bionic upstream patch https://salsa.debian.org/debian/kdump- tools/-/commit/b1bac9396ddbbce3817c34be3161630698e4a503 *Note: There are two source packages needed changes, kdump-tools for Impish -> Kinetic and makedumpfile for series Focal -> Bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Committed Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: New Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: New Status in kdump-tools source package in Impish: New Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: Incomplete Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Committed Status in makedumpfile source package in Kinetic: Invalid Bug description: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] Create VM on Azure Install crash dump utilies (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) sudo apt install linux-crashdump Say (y) to all questions during install Reboot the VM As root on the VM after reboot: kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1085-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1085-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1085-azure root=UUID=a117a689-aa1d-4cdc-8a30-7b9fbf174437 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at
[Kernel-packages] [Bug 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1046.53 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980829 Title: System freeze after resuming from suspend due to PCI ASPM settings Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The 2 patches look pretty safe to me, they try to preserve the ASPM state of devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980700] Re: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1046.53 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980700 Title: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: The fix is already in the upstream kernel v5.19-rc1, no need to send the patches to unstable kernel. And for Jammy kernel, this SRU depends on #1949245, after merging the patchset for #1949245, then could apply this SRU to jammy. [Impact] On the AMD YC platforms, the internal mic can't be detected and there is no internal mic for users to use. [Fix] Backport 2 patches from mainline kernel to fix this problem. [Test] boot the patched kernel on the machine which has updated BIOS, after loging into the desktop, open the gnome-sound-setting, there is internal mic, and could record sound via internal mic. [Where problems could occur] This only impacts intenal mic detection on AMD yc machines, it will check the acpi variable first, if not detected, it will check the acpi dmi table as before, so the regression possibility is very low, and we already tested these patches on a couple of Lenovo YC machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1087.84)
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1087.84) for focal have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.55.5+20.04 (arm64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure [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 1981968] Re: bcmwl fails to build on the latest kinetic kernel 5.19
This bug was fixed in the package bcmwl - 6.30.223.271+bdcom-0ubuntu9 --- bcmwl (6.30.223.271+bdcom-0ubuntu9) kinetic; urgency=medium * debian/dkms.conf.in, debian/patches/0040-add-support-for-linux-5.18.patch (LP: #1981968): - Add support for Linux 5.18. -- Andrea Righi Mon, 18 Jul 2022 08:40:44 + ** Changed in: bcmwl (Ubuntu Kinetic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1981968 Title: bcmwl fails to build on the latest kinetic kernel 5.19 Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Kinetic: Fix Released Bug description: [Impact] bcmwl fails to build on kernel 5.19 with the following errors: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:603:14: error: implicit declaration of function ‘pci_alloc_consistent’; did you mean ‘osl_dma_alloc_consistent’? [-Werror=implicit-function-declaration] 603 | va = pci_alloc_consistent(osh->pdev, size, (dma_addr_t*)pap); | ^~~~ | osl_dma_alloc_consistent /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3307:26: error: implicit declaration of function ‘PDE_DATA’; did you mean ‘NODE_DATA’? [-Werror=implicit-function-declaration] 3307 | wl_info_t * wl = PDE_DATA(file_inode(filp)); | ^~~~ | NODE_DATA /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In function ‘osl_dma_map’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:626:38: error: ‘PCI_DMA_TODEVICE’ undeclared (first use in this function); did you mean ‘DMA_TO_DEVICE’? 626 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: PCI_DMA_FROMDEVICE; | ^~~~ | DMA_TO_DEVICE /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:626:38: note: each undeclared identifier is reported only once for each function it appears in /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:626:56: error: ‘PCI_DMA_FROMDEVICE’ undeclared (first use in this function); did you mean ‘DMA_FROM_DEVICE’? 626 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: PCI_DMA_FROMDEVICE; | ^~ |DMA_FROM_DEVICE /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:659:17: error: implicit declaration of function ‘pci_map_single’; did you mean ‘dma_map_single’? [-Werror=implicit-function-declaration] 659 | return (pci_map_single(osh->pdev, va, size, dir)); | ^~ | dma_map_single /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In function ‘osl_dma_unmap’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:668:38: error: ‘PCI_DMA_TODEVICE’ undeclared (first use in this function); did you mean ‘DMA_TO_DEVICE’? 668 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: PCI_DMA_FROMDEVICE; | ^~~~ | DMA_TO_DEVICE /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:668:56: error: ‘PCI_DMA_FROMDEVICE’ undeclared (first use in this function); did you mean ‘DMA_FROM_DEVICE’? 668 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: PCI_DMA_FROMDEVICE; | ^~ |DMA_FROM_DEVICE /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:669:9: error: implicit declaration of function ‘pci_unmap_single’; did you mean ‘dma_unmap_single’? [-Werror=implicit-function-declaration] 669 | pci_unmap_single(osh->pdev, (uint32)pa, size, dir); | ^~~~ | dma_unmap_single [Test case] $ sudo apt install bcmwl-kernel-source [Fix] Patch bcmwl to support the new 5.18+ kernel ABI (PCI/DMA-related functions). [Regression potential] We may experience regressions with bcmwl in kernels >= 5.18. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1981968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter
EOL ** Changed in: kdump-tools (Ubuntu Impish) Status: New => Invalid ** Changed in: kdump-tools (Ubuntu Impish) Assignee: Heather Lemon (hypothetical-lemon) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Committed Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: New Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: New Status in kdump-tools source package in Impish: Invalid Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: Incomplete Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Committed Status in makedumpfile source package in Kinetic: Invalid Bug description: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] Create VM on Azure Install crash dump utilies (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) sudo apt install linux-crashdump Say (y) to all questions during install Reboot the VM As root on the VM after reboot: kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1085-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1085-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1085-azure root=UUID=a117a689-aa1d-4cdc-8a30-7b9fbf174437 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System RAM: 4095MB) cat /proc/sys/kernel/sysrq # make sure this value is greater than 0 #set it to 1 sudo sysctl -w kernel.sysrq=1 Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger #kdump doesnt work and hangs indefinitely #force reboot VM from Azure console Outcome after removing "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger #kdump works, VM eventually (several minutes) reboots # Login to VM and check that there is a core file in /var/crash: ls /var/crash [Where Problems Could Occur] This change modifies the debian/rules. The package could fail to build properly if mistyped. [Other] Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0" parameter. target series - Kinetic -> Bionic upstream patch https://salsa.debian.org/debian/kdump- tools/-/commit/b1bac9396ddbbce3817c34be3161630698e4a503 *Note: There are two source packages needed changes, kdump-tools for Impish -> Kinetic and makedumpfile for series Focal -> Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1978333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter
Hi Steve, The test plan of the description has been updated. I'm currently testing the Azure bionic vm and confirmed the bug. The Impish series is EOL and I will remove the series tag. Thank You, Heather -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Committed Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: New Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: New Status in kdump-tools source package in Impish: Invalid Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: Incomplete Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Committed Status in makedumpfile source package in Kinetic: Invalid Bug description: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] Create VM on Azure Install crash dump utilies (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) sudo apt install linux-crashdump Say (y) to all questions during install Reboot the VM As root on the VM after reboot: kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1085-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1085-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1085-azure root=UUID=a117a689-aa1d-4cdc-8a30-7b9fbf174437 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System RAM: 4095MB) cat /proc/sys/kernel/sysrq # make sure this value is greater than 0 #set it to 1 sudo sysctl -w kernel.sysrq=1 Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger #kdump doesnt work and hangs indefinitely #force reboot VM from Azure console Outcome after removing "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger #kdump works, VM eventually (several minutes) reboots # Login to VM and check that there is a core file in /var/crash: ls /var/crash [Where Problems Could Occur] This change modifies the debian/rules. The package could fail to build properly if mistyped. [Other] Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0" parameter. target series - Kinetic -> Bionic upstream patch https://salsa.debian.org/debian/kdump- tools/-/commit/b1bac9396ddbbce3817c34be3161630698e4a503 *Note: There are two source packages needed changes, kdump-tools for Impish -> Kinetic and makedumpfile for series Focal -> Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1978333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.4/5.4.0.1087.64)
All autopkgtests for the newly accepted linux-meta-azure-5.4 (5.4.0.1087.64) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) asic0x/1.0.1-1 (amd64, arm64) dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) v4l2loopback/0.10.0-1ubuntu1.2 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-azure-5.4 [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 1982409] [NEW] Focal update: v5.4.198 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.198 upstream stable release
from git://git.kernel.org/
binfmt_flat: do not stop relocating GOT entries prematurely on riscv
ALSA: hda/realtek - Fix microphone noise on ASUS TUF B550M-PLUS
USB: serial: option: add Quectel BG95 modem
USB: new quirk for Dell Gen 2 devices
perf/x86/intel: Fix event constraints for ICL
ptrace/um: Replace PT_DTRACE with TIF_SINGLESTEP
ptrace/xtensa: Replace PT_SINGLESTEP with TIF_SINGLESTEP
ptrace: Reimplement PTRACE_KILL by always sending SIGKILL
btrfs: add "0x" prefix for unsupported optional features
btrfs: repair super block num_devices automatically
drm/virtio: fix NULL pointer dereference in virtio_gpu_conn_get_modes
mwifiex: add mutex lock for call in mwifiex_dfs_chan_sw_work_queue
b43legacy: Fix assigning negative value to unsigned variable
b43: Fix assigning negative value to unsigned variable
ipw2x00: Fix potential NULL dereference in libipw_xmit()
ipv6: fix locking issues with loops over idev->addr_list
fbcon: Consistently protect deferred_takeover with console_lock()
ACPICA: Avoid cache flush inside virtual machines
drm/komeda: return early if drm_universal_plane_init() fails.
ALSA: jack: Access input_dev under mutex
spi: spi-rspi: Remove setting {src,dst}_{addr,addr_width} based on DMA direction
tools/power turbostat: fix ICX DRAM power numbers
drm/amd/pm: fix double free in si_parse_power_table()
ath9k: fix QCA9561 PA bias level
media: venus: hfi: avoid null dereference in deinit
media: pci: cx23885: Fix the error handling in cx23885_initdev()
media: cx25821: Fix the warning when removing the module
md/bitmap: don't set sb values if can't pass sanity check
mmc: jz4740: Apply DMA engine limits to maximum segment size
scsi: megaraid: Fix error check return value of register_chrdev()
drm/plane: Move range check for format_count earlier
drm/amd/pm: fix the compile warning
arm64: compat: Do not treat syscall number as ESR_ELx for a bad syscall
drm: msm: fix error check return value of irq_of_parse_and_map()
ipv6: Don't send rs packets to the interface of ARPHRD_TUNNEL
net/mlx5: fs, delete the FTE when there are no rules attached to it
ASoC: dapm: Don't fold register value changes into notifications
mlxsw: spectrum_dcb: Do not warn about priority changes
drm/amdgpu/ucode: Remove firmware load type check in amdgpu_ucode_free_bo
HID: bigben: fix slab-out-of-bounds Write in bigben_probe
ASoC: tscs454: Add endianness flag in snd_soc_component_driver
s390/preempt: disable __preempt_count_add() optimization for
PROFILE_ALL_BRANCHES
spi: stm32-qspi: Fix wait_cmd timeout in APM mode
dma-debug: change allocation mode from GFP_NOWAIT to GFP_ATIOMIC
ACPI: PM: Block ASUS B1400CEAE from suspend to idle by default
ipmi:ssif: Check for NULL msg when handling events and messages
ipmi: Fix pr_fmt to avoid compilation issues
rtlwifi: Use pr_warn instead of WARN_ONCE
media: coda: limit frame interval enumeration to supported encoder frame sizes
media: cec-adap.c: fix is_configuring state
openrisc: start CPU timer early in boot
nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags
ASoC: rt5645: Fix errorenous cleanup order
nbd: Fix hung on disconnect request if socket is closed before
net: phy: micrel: Allow probing without .driver_data
media: exynos4-is: Fix compile warning
ASoC: max98357a: remove dependency on GPIOLIB
rxrpc: Return an error to sendmsg if call failed
eth: tg3: silence the GCC 12 array-bounds warning
selftests/bpf: fix btf_dump/btf_dump due to recent clang change
IB/rdmavt: add missing locks in rvt_ruc_loopback
ARM: dts: ox820: align interrupt controller node name with dtschema
PM / devfreq: rk3399_dmc: Disable edev on remove()
fs: jfs: fix possible NULL pointer dereference in dbFree()
ARM: OMAP1: clock: Fix UART rate reporting algorithm
powerpc/fadump: Fix fadump to work with a different endian capture kernel
fat: add ratelimit to fat*_ent_bread()
ARM: versatile: Add missing of_node_put in dcscb_init
ARM: dts: exynos: add atmel,24c128 fallback to Samsung EEPROM
ARM: hisi: Add missing of_node_put after of_find_compatible_node
PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store()
tracing: incorrect isolate_mote_t cast in mm_vmscan_lru_isolate
powerpc/xics: fix refcount leak in icp_opal_init()
powerpc/powernv: fix missing of_node_put in uv_init()
macintosh/via-pmu: Fix build failure when CONFIG_INPUT is disabled
powerpc/iommu: Add missing of_node_put in iommu_init_early_dart
RDMA/hfi1: Prevent panic when SDMA is disabled
drm: fix EDID struct for old ARM OABI format
ath9k
[Kernel-packages] [Bug 1981390] Re: Mass Storage Gadget driver truncates device >2TB
Thanks for identifying the fix! This should go into the main Ubuntu kernel, not just the raspi derivative. ** Package changed: linux-raspi (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => 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/1981390 Title: Mass Storage Gadget driver truncates device >2TB Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: New Bug description: I tried to use f_mass_storage to expose a 16TB hard drive attached to Raspberry Pi to another computer. On the remote computer the recognised drive has incorrect capacity and the data is truncated. After some debugging I noted the problem is caused by a bug in the read capacity function of f_mass_storage in kernel version prior to 5.15, which had already been fixed upstream in mainline kernel since v5.16 https://lore.kernel.org/all/20210914052728.23369-1-nikita.yo...@cogentembedded.com/ I tried the kernel from https://github.com/raspberrypi/linux version rpi-5.16.y and confirmed that the problem is fixed at v5.16. I wonder if the fix can be backported to the Ubuntu kernel. Thank you very much! Current kernel package version: linux-raspi (5.15.0-1011.13) jammy Hardware: Raspberry Pi 4B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981883] Re: amdgpu module crash after 5.15 kernel update
Patch now posted upstream for linux stable kernel 5.15 https://lore.kernel.org/stable/20220719185659.2068735-1-alexander.deuc...@amd.com/T/#u -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1981883 Title: amdgpu module crash after 5.15 kernel update Status in linux-aws-5.15 package in Ubuntu: New Bug description: The kernel 5.15 amdgpu module crashes on load with a “BUG: kernel NULL pointer dereference” on Amazon EC2 G4ad hardware (custom AMD Radeon V520 Pro datacenter GPU) on focal (HWE) and jammy with kernel 5.15.0-1011 and possibly earlier, up through latest (revision 1015.19). This crash bug did not exist in any of the focal HWE 5.13 kernels. This is probably an upstream kernel bug, but I am also filing it here because existing focal users on EC2 will suddenly stop having access to their AMD GPUs after a reboot once the new 5.15 HWE kernel is installed. The full backtrace from dmesg is below. The offending function call which crashes in the 5.15 kernel corresponds to this source (sorry, not the right source tree, but the same driver) https://github.com/torvalds/linux/blob/8bb7eca972ad531c9b149c0a51ab43a417385813/drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c#L345 A workaround that I have discovered is adding “options amdgpu virtual_display=;” to a new modprobe.d configuration file - something which shouldn’t be required, but is at least harmless. Here is the relevant BUG message and backtrace from dmesg: [ 318.111721] BUG: kernel NULL pointer dereference, address: [ 318.115443] #PF: supervisor instruction fetch in kernel mode [ 318.118443] #PF: error_code(0x0010) - not-present page [ 318.121177] PGD 0 P4D 0 [ 318.122688] Oops: 0010 [#1] SMP NOPTI [ 318.124592] CPU: 6 PID: 13667 Comm: modprobe Tainted: GW 5.15.0-1015-aws #19~20.04.1-Ubuntu [ 318.129711] Hardware name: Amazon EC2 g4ad.2xlarge/, BIOS 1.0 10/16/2017 [ 318.133167] RIP: 0010:0x0 [ 318.134704] Code: Unable to access opcode bytes at RIP 0xffd6. [ 318.138291] RSP: 0018:9841828d78e0 EFLAGS: 00010246 [ 318.140938] RAX: RBX: 8a4f16ae8000 RCX: 0001 [ 318.144604] RDX: RSI: 0003 RDI: 8a4f16ae8000 [ 318.148319] RBP: 9841828d7908 R08: 8a4f02460278 R09: 8a4f06422c40 [ 318.152151] R10: c01c42494f8a R11: 8a4f01dcb5b8 R12: 8a4f024602e8 [ 318.155929] R13: c107e4a0 R14: R15: 8a4f02460010 [ 318.159685] FS: 7f8afdc1c740() GS:8a55f098() knlGS: [ 318.163897] CS: 0010 DS: ES: CR0: 80050033 [ 318.167038] CR2: ffd6 CR3: 00011817e000 CR4: 003506e0 [ 318.170758] Call Trace: [ 318.173964] [ 318.176822] __drm_helper_disable_unused_functions+0xe7/0x100 [drm_kms_helper] [ 318.184230] drm_helper_disable_unused_functions+0x44/0x50 [drm_kms_helper] [ 318.189761] amdgpu_fbdev_init+0x104/0x110 [amdgpu] [ 318.194264] amdgpu_device_init.cold+0x7cc/0xc48 [amdgpu] [ 318.199061] ? pci_read_config_byte+0x27/0x40 [ 318.203206] amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] [ 318.207901] amdgpu_pci_probe+0x1ea/0x290 [amdgpu] [ 318.212445] local_pci_probe+0x4b/0x90 [ 318.216386] pci_device_probe+0x182/0x1f0 [ 318.220407] really_probe.part.0+0xcb/0x370 [ 318.224460] really_probe+0x40/0x80 [ 318.228232] __driver_probe_device+0x115/0x190 [ 318.232412] driver_probe_device+0x23/0xa0 [ 318.236436] __driver_attach+0xbd/0x160 [ 318.240348] ? __device_attach_driver+0x110/0x110 [ 318.244637] bus_for_each_dev+0x7e/0xc0 [ 318.248570] driver_attach+0x1e/0x20 [ 318.252474] bus_add_driver+0x161/0x200 [ 318.256412] driver_register+0x74/0xd0 [ 318.260332] __pci_register_driver+0x68/0x70 [ 318.264496] amdgpu_init+0x7c/0x1000 [amdgpu] [ 318.268841] ? 0xc146e000 [ 318.272521] do_one_initcall+0x48/0x1d0 [ 318.276446] ? __cond_resched+0x19/0x30 [ 318.280378] ? kmem_cache_alloc_trace+0x15a/0x420 [ 318.284736] do_init_module+0x52/0x230 [ 318.288644] load_module+0x1372/0x1600 [ 318.292529] __do_sys_finit_module+0xbf/0x120 [ 318.296706] ? __do_sys_finit_module+0xbf/0x120 [ 318.300947] __x64_sys_finit_module+0x1a/0x20 [ 318.305265] do_syscall_64+0x5c/0xc0 [ 318.308984] ? do_syscall_64+0x69/0xc0 [ 318.312841] ? do_syscall_64+0x69/0xc0 [ 318.316693] ? do_syscall_64+0x69/0xc0 [ 318.320545] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 318.324975] RIP: 0033:0x7f8afdd6273d [ 318.328700] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 23 37 0d 00 f7 d8 64 89 01 48 [ 318.34360
[Kernel-packages] [Bug 1973485] Re: upgrade to 22.04 on raspberry pi can leave ethernet interface unreachable if vlans are used
** Changed in: linux-raspi (Ubuntu Impish) Status: In Progress => Won't Fix -- 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/1973485 Title: upgrade to 22.04 on raspberry pi can leave ethernet interface unreachable if vlans are used Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Impish: Won't Fix Status in linux-raspi source package in Jammy: Fix Released Bug description: [Impact] The 8021q kernel module was moved from the linux-modules package to the linux-modules-extras package for the Raspberry Pi. This means that vlans cannot be configured if the linux-modules-extras package is not installed. The release notes mention that some modules have been moved and to install the linux-modules-extra package if your application doesn't work. This would be adequate warning except for one issue. Systemd-networkd will fail to configure an ip address for the raspberry pi's ethernet interface when the vlans cannot be configured leaving headless systems inaccessible. I suffered this exact scenario upon upgrading since my netplan file included vlans assigned to the Pi's ethernet interface. I would recommend either updating the release notes to specifically call out this scenario or move the 8021q module back to the linux-modules package. [Test Case] See above. [Fix] Move 8021q modules to linux-modules package. [Where Problems Could Occur] None expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1973485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981390] Re: Mass Storage Gadget driver truncates device >2TB
Can you test the kernel from here? https://kernel.ubuntu.com/~juergh/lp1981390/ This is linux-raspi 5.15.0-1012.14 with that patch that you identified. ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- 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/1981390 Title: Mass Storage Gadget driver truncates device >2TB Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Bug description: I tried to use f_mass_storage to expose a 16TB hard drive attached to Raspberry Pi to another computer. On the remote computer the recognised drive has incorrect capacity and the data is truncated. After some debugging I noted the problem is caused by a bug in the read capacity function of f_mass_storage in kernel version prior to 5.15, which had already been fixed upstream in mainline kernel since v5.16 https://lore.kernel.org/all/20210914052728.23369-1-nikita.yo...@cogentembedded.com/ I tried the kernel from https://github.com/raspberrypi/linux version rpi-5.16.y and confirmed that the problem is fixed at v5.16. I wonder if the fix can be backported to the Ubuntu kernel. Thank you very much! Current kernel package version: linux-raspi (5.15.0-1011.13) jammy Hardware: Raspberry Pi 4B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982412] [NEW] xhci lockup
Public bug reported: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 ** 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/1982412 Title: xhci lockup Status in linux package in Ubuntu: New Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982412/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1982412] Re: xhci lockup
lsusb contents ** Attachment added: "lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982412/+attachment/5604418/+files/lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982412 Title: xhci lockup Status in linux package in Ubuntu: New Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982412/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982412] Re: xhci lockup
May be related to #1979886 -- 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/1982412 Title: xhci lockup Status in linux package in Ubuntu: New Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982412/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982412] 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 1982412 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/1982412 Title: xhci lockup Status in linux package in Ubuntu: Incomplete Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982412/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965241] Re: Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events
Basic sanity test shows positive results with 5.15.0-43.46 kernel from -proposed repo. ** 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/1965241 Title: Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events Status in dellserver: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. [Fix] These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=00823dcbdd415c868390feaca16f0265101efab4 PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=ea401499e943c307e6d44af6c2b4e068643e7884 3134689f98 PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() [Test Case] 1. Disable the memory space of NVMe end point device 2. Issue IO to the device 3. Observe dmesg. dmesg shows that EDR event is generated, link is contained and NVMe device is recovered. 2. Observe the dmesg [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/test_dpc_1965241 To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1965241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981901] Re: Weird behavior on display, since kernel versions 5.15.x
@vanvugt I tried to set intel_iommu=igfx_off on boot, so to test temporarily with that parameter, and it looks like it solved the problem, excellent! So best to wait until >= 5.15.0-40 comes out, when will that happen (for Lubuntu)? -- 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/1981901 Title: Weird behavior on display, since kernel versions 5.15.x Status in linux package in Ubuntu: Incomplete Bug description: Since kernel versions 5.15.x I have a problem with graphics unit and display on screen. I described it first time here https://discourse.lubuntu.me/t/lubuntu-jammy-weird-artifacts-on- display-choose-older-kernel-version-to-boot-with/3034 and recently here https://discourse.lubuntu.me/t/weird-behavior-on-display-since-kernel- versions-5-15-x/3446 Don't know what information else to provide, please advice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1976398] Re: Screen flickering in Ubuntu 22.04 and Intel UHD graphics (adding "i915.enable_dc=0 intel_idle.max_cstate=2" doesn't help)
** Changed in: linux-signed-lowlatency (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/1976398 Title: Screen flickering in Ubuntu 22.04 and Intel UHD graphics (adding "i915.enable_dc=0 intel_idle.max_cstate=2" doesn't help) Status in linux-signed-lowlatency package in Ubuntu: Fix Released Bug description: Intermittent screen flickering (random moving image sideways). Issues started after upgrade to 22.04 (kernel 5.15, last 5.13 kernel from 21.10 was fine). A similar bug to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 but adding below line to grub options: "i915.enable_dc=0 intel_idle.max_cstate=2" and executing "sudo update-grub" doesn't help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-lowlatency 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-lowlatency 5.15.30 Uname: Linux 5.15.0-33-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue May 31 20:06:18 2022 InstallationDate: Installed on 2021-05-12 (383 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: linux-signed-lowlatency UpgradeStatus: Upgraded to jammy on 2022-05-07 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/1976398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982412] Re: xhci lockup
apport information ** Tags added: apport-collected jammy wayland-session ** Description changed: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC3: lizf 2691 F pulseaudio + /dev/snd/controlC2: lizf 2691 F pulseaudio + /dev/snd/controlC0: lizf 2691 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2020-04-14 (826 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-41-generic N/A + linux-backports-modules-5.15.0-41-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.2 + Tags: jammy wayland-session + Uname: Linux 5.15.0-41-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/23/2021 + dmi.bios.release: 5.17 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: L2.02 + dmi.board.name: B550 Phantom Gaming-ITX/ax + 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604420/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing
[Kernel-packages] [Bug 1982412] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604424/+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/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982412/+s
[Kernel-packages] [Bug 1982412] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604423/+files/IwConfig.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/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198
[Kernel-packages] [Bug 1982412] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604422/+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/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/
[Kernel-packages] [Bug 1982412] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604421/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982412/+sub
[Kernel-packages] [Bug 1982412] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604425/+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/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198
[Kernel-packages] [Bug 1982412] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604430/+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/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+b
[Kernel-packages] [Bug 1982412] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604428/+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/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/19824
[Kernel-packages] [Bug 1982412] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604429/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982412/
[Kernel-packages] [Bug 1982412] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604432/+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/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/li
[Kernel-packages] [Bug 1982412] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604434/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1
[Kernel-packages] [Bug 1982412] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604436/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982412/
[Kernel-packages] [Bug 1982412] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604427/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/19824
[Kernel-packages] [Bug 1982412] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604435/+files/RfKill.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/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982412/
[Kernel-packages] [Bug 1982412] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604431/+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/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+s
[Kernel-packages] [Bug 1982412] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604426/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982412/+s
[Kernel-packages] [Bug 1982412] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604433/+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/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+b
[Kernel-packages] [Bug 1982412] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604437/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug
[Kernel-packages] [Bug 1982412] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1982412/+attachment/5604438/+files/acpidump.txt ** 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/1982412 Title: xhci lockup Status in linux package in Ubuntu: Confirmed Bug description: when I'm playing music through a Blue Yeti audio device, the audio occasionally dies at PulseAudio (device disconnect) and then exactly 10 seconds later all of xHCI restarts and refuses to come back up. this happens sporadically about every 2-3 hours if the audio device is in use. I tried disabling usb autosuspend with no effect. the system otherwise works fine even when usb subsystem is dead (can ssh in etc) Linux lily 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Jul 20 10:48:22 lily gnome-shell[2719]: libinput error: event6 - Keychron Keychron K1: client bug: event processing lagging behind by 33ms, your system is too slow Jul 20 10:49:43 lily pulseaudio[2617]: Got POLLNVAL from ALSA Jul 20 10:49:43 lily pulseaudio[2617]: Error opening PCM device iec958:1: No such file or directory Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default sink Jul 20 10:49:43 lily gsd-media-keys[2948]: Unable to get default source Jul 20 10:49:53 lily kernel: [43643.757737] xhci_hcd :0b:00.3: xHCI host not responding to stop endpoint command. Jul 20 10:49:53 lily kernel: [43643.757740] xhci_hcd :0b:00.3: USBSTS: 0x Jul 20 10:49:53 lily kernel: [43643.773641] xhci_hcd :0b:00.3: xHCI host controller not responding, assume dead Jul 20 10:49:53 lily kernel: [43643.773652] xhci_hcd :0b:00.3: HC died; cleaning up Jul 20 10:49:53 lily kernel: [43643.773674] usb 3-3: USB disconnect, device number 2 Jul 20 10:49:53 lily kernel: [43643.773677] usb 3-3.1: USB disconnect, device number 3 Jul 20 10:49:53 lily kernel: [43643.773747] usb 4-3: USB disconnect, device number 2 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 17 Jul 20 10:49:53 lily kernel: [43643.849981] usb 3-3.2: USB disconnect, device number 4 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 20 Jul 20 10:49:53 lily acpid: input device has been disconnected, fd 21 Jul 20 10:49:53 lily kernel: [43644.062063] usb 3-3.3: USB disconnect, device number 5 Jul 20 10:49:54 lily acpid: input device has been disconnected, fd 19 Jul 20 10:49:54 lily kernel: [43644.173985] usb 3-3.4: USB disconnect, device number 6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lizf 2691 F pulseaudio /dev/snd/controlC2: lizf 2691 F pulseaudio /dev/snd/controlC0: lizf 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-14 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-16 (94 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.02 dmi.board.name: B550 Phantom Gaming-ITX/ax 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.:bvrL2.02:bd03/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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. To manage notifications about th
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
The XPS 13 Plus 9320 webcam does not work for me since upgrading to 22.04 from the original 20.04 OEM installation. BIOS: 1.4.0 Kernel:5.17.0-1013-oem libcamhal-ipu6ep0 is installed from the mentioned PPA v4l2-ctl --list-devices Intel MIPI Camera (platform:v4l2loopback-000): /dev/video0 Neither chrome nor Firefox show video. Similar to the issue described here https://askubuntu.com/questions/1414767/dell-xps-plus-9320-webcam- not-detected-in-ubuntu-22-04?atw=1#comment2465343_1417193 -- 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (prob
[Kernel-packages] [Bug 1981658] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008
Fwiw I deployed this for our server yesterday and it's been up 21 hours, whereas before it didn't really survive for more than ~6 hours on 122... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024] start_secondary+0x166/0x1c0 | [ 351.103977] secondary_startup_64+0xa4/0xb0 | [ 351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr ib_iser rdma_
Re: [Kernel-packages] [Bug 1982113] Re: My screen is horizontally divided into two parts.
Hi, I think this is not a hardware issue because sometimes my laptop works very well. Kind Regards, *Monjoy Saha* On Tue, 19 Jul 2022 at 23:11, Daniel van Vugt <1982...@bugs.launchpad.net> wrote: > ** Package changed: xorg (Ubuntu) => linux (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1982113 > > Title: > My screen is horizontally divided into two parts. > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I'm using Ubuntu 16.04 on my HP laptop. My screen is horizontally > divided into two parts. The upper part is fine but the lower part is > flickering. This is not a hardware issue because sometimes I don't see > any issues. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3.1 > ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 > Uname: Linux 4.4.0-210-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.1-0ubuntu2.30 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity > Date: Tue Jul 19 07:51:12 2022 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation 3rd Gen Core processor Graphics Controller > [8086:0166] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics > Controller [103c:218f] > InstallationDate: Installed on 2021-10-14 (278 days ago) > InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 > (20160803) > MachineType: Hewlett-Packard HP 15 Notebook PC > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-210-generic > root=UUID=6debcebe-2bf3-4433-9714-f6cbfe13fa37 ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > XorgLog: > > dmi.bios.date: 12/04/2014 > dmi.bios.vendor: Insyde > dmi.bios.version: F.1A > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 218F > dmi.board.vendor: Hewlett-Packard > dmi.board.version: 39.17 > dmi.chassis.asset.tag: Chassis Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: Hewlett-Packard > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnInsyde:bvrF.1A:bd12/04/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097510005F1600087:rvnHewlett-Packard:rn218F:rvr39.17:cvnHewlett-Packard:ct10:cvrChassisVersion: > dmi.product.name: HP 15 Notebook PC > dmi.product.version: 097510005F1600087 > dmi.sys.vendor: Hewlett-Packard > version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.91-2~16.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.12 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.1-1ubuntu2 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20160325-1ubuntu1.2 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.12-1build2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982113/+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/1982113 Title: My screen is horizontally divided into two parts. Status in linux package in Ubuntu: Incomplete Bug description: I'm using Ubuntu 16.04 on my HP laptop. My screen is horizontally divided into two parts. The upper part is fine but the lower part is flickering. This is not a hardware issue because sometimes I don't see any issues. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Jul 19 07:51:12 2022 DistUpgraded: Fresh install DistroCodename: xenial
[Kernel-packages] [Bug 1981901] Re: Weird behavior on display, since kernel versions 5.15.x
Yes Lubuntu with LXQT uses Xorg FYI: the X in LXQt; Lubuntu doesn't support LWQt which currently is only for testing. -- 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/1981901 Title: Weird behavior on display, since kernel versions 5.15.x Status in linux package in Ubuntu: Incomplete Bug description: Since kernel versions 5.15.x I have a problem with graphics unit and display on screen. I described it first time here https://discourse.lubuntu.me/t/lubuntu-jammy-weird-artifacts-on- display-choose-older-kernel-version-to-boot-with/3034 and recently here https://discourse.lubuntu.me/t/weird-behavior-on-display-since-kernel- versions-5-15-x/3446 Don't know what information else to provide, please advice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980700] Re: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines
Installed the kernel 5.14.0-1046 oem kernel, open the gnome-sound- setting, there is a dmic in the input device list, and it could record the sound. Verification done on focal. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980700 Title: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: The fix is already in the upstream kernel v5.19-rc1, no need to send the patches to unstable kernel. And for Jammy kernel, this SRU depends on #1949245, after merging the patchset for #1949245, then could apply this SRU to jammy. [Impact] On the AMD YC platforms, the internal mic can't be detected and there is no internal mic for users to use. [Fix] Backport 2 patches from mainline kernel to fix this problem. [Test] boot the patched kernel on the machine which has updated BIOS, after loging into the desktop, open the gnome-sound-setting, there is internal mic, and could record sound via internal mic. [Where problems could occur] This only impacts intenal mic detection on AMD yc machines, it will check the acpi variable first, if not detected, it will check the acpi dmi table as before, so the regression possibility is very low, and we already tested these patches on a couple of Lenovo YC machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982104] Re: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes
** Description changed: [Impact] - Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server which is targeting Telco workloads. + Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server. Attaching the console logs. Currently, it looks like disabling VT-D option in BIOS settings helps mitigate the issue. Console logs indicate something is wrong in iommu/dmar subsystem. [Fix] The IOMMU driver shares the pasid table for PCI alias devices. When the RID2PASID entry of the shared pasid table has been filled by the first device, the subsequent device will encounter the "DMAR: Setup RID2PASID failed" failure as the pasid entry has already been marked as present. As the result, the IOMMU probing process will be aborted. On the contrary, when any alias device is hot-removed from the system, for example, by writing to /sys/bus/pci/devices/.../remove, the shared RID2PASID will be cleared without any notifications to other devices. As the result, any DMAs from those rest devices are blocked. Sharing pasid table among PCI alias devices could save two memory pages for devices underneath the PCIe-to-PCI bridges. Anyway, considering that those devices are rare on modern platforms that support VT-d in scalable mode and the saved memory is negligible, it's reasonable to remove this part of immature code to make the driver feasible and stable. [Test Case] 1. use the target machine(Intel Sapphire Rapids) and install the kernel with the fix. 2. boot the target machine 3. check dmesg if the error message exists [ 8.120527] pci :03:01.0: DMAR: Setup RID2PASID failed [Where problems could occur] After enable intel_iommu, the errors may be occurred. We need to figure out one by one once the related errors are triggered in the future. -- 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/1982104 Title: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server. Attaching the console logs. Currently, it looks like disabling VT-D option in BIOS settings helps mitigate the issue. Console logs indicate something is wrong in iommu/dmar subsystem. [Fix] The IOMMU driver shares the pasid table for PCI alias devices. When the RID2PASID entry of the shared pasid table has been filled by the first device, the subsequent device will encounter the "DMAR: Setup RID2PASID failed" failure as the pasid entry has already been marked as present. As the result, the IOMMU probing process will be aborted. On the contrary, when any alias device is hot-removed from the system, for example, by writing to /sys/bus/pci/devices/.../remove, the shared RID2PASID will be cleared without any notifications to other devices. As the result, any DMAs from those rest devices are blocked. Sharing pasid table among PCI alias devices could save two memory pages for devices underneath the PCIe-to-PCI bridges. Anyway, considering that those devices are rare on modern platforms that support VT-d in scalable mode and the saved memory is negligible, it's reasonable to remove this part of immature code to make the driver feasible and stable. [Test Case] 1. use the target machine(Intel Sapphire Rapids) and install the kernel with the fix. 2. boot the target machine 3. check dmesg if the error message exists [ 8.120527] pci :03:01.0: DMAR: Setup RID2PASID failed [Where problems could occur] After enable intel_iommu, the errors may be occurred. We need to figure out one by one once the related errors are triggered in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
@bufke Hello, May I know how you upgrade ubuntu from 20.04 oem to 22.04? by $ do- release-upgrade or $ sudo apt dist-upgrade. I am curious how you have 5.17.0-1013-oem installed. May I know if you keep using 5.14.0-10XX-oem, does it work for webcamtest or any application utilize camera by browser? Thanks, -- 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/02/2021 dmi.bios.release: 0.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.2.7 dmi.board.vendor:
[Kernel-packages] [Bug 1981901] Re: Weird behavior on display, since kernel versions 5.15.x
*** This bug is a duplicate of bug 1958191 *** https://bugs.launchpad.net/bugs/1958191 To set a kernel parameter permanently, add it to /etc/default/grub in GRUB_CMDLINE_LINUX_DEFAULT. Then run: sudo update-grub and reboot. ** This bug has been marked a duplicate of bug 1958191 [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) -- 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/1981901 Title: Weird behavior on display, since kernel versions 5.15.x Status in linux package in Ubuntu: Incomplete Bug description: Since kernel versions 5.15.x I have a problem with graphics unit and display on screen. I described it first time here https://discourse.lubuntu.me/t/lubuntu-jammy-weird-artifacts-on- display-choose-older-kernel-version-to-boot-with/3034 and recently here https://discourse.lubuntu.me/t/weird-behavior-on-display-since-kernel- versions-5-15-x/3446 Don't know what information else to provide, please advice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: High Status: Confirmed ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux (Ubuntu Kinetic) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Triaged Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Triaged 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 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
@bufke, Can you help to provide logs from /var/log and `dpkg -l`? I also tried one 9320 and do-release-upgrade to Jammy. I didn't install 5.17 after do-release-upgrade. -- 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/02/2021 dmi.bios.release: 0.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.2.7:bd12/02/2021:br0.2:svnDellInc.:pn
