[Kernel-packages] [Bug 1995966] Re: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10
sudo dmesg | grep -vw "UFW BLOCK" [0.327796] ACPI: PM: Power Resource [P0NV] [0.331078] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff]) [0.331083] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3] [0.331144] acpi PNP0A08:00: _OSC: platform does not support [SHPCHotplug LTR DPC] [0.331249] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [0.331250] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [0.331259] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-3f] only partially covers this bridge [0.331424] PCI host bridge to bus :00 [0.331425] pci_bus :00: root bus resource [mem 0x000a-0x000e window] [0.331426] pci_bus :00: root bus resource [mem 0xd000-0xf7ff window] [0.331428] pci_bus :00: root bus resource [mem 0xfc00-0xfdff window] [0.331428] pci_bus :00: root bus resource [mem 0x83000-0xff window] [0.331429] pci_bus :00: root bus resource [io 0x-0x0cf7 window] [0.331430] pci_bus :00: root bus resource [io 0x0d00-0x window] [0.331430] pci_bus :00: root bus resource [bus 00-ff] [0.331440] pci :00:00.0: [1022:1630] type 00 class 0x06 [0.331497] pci :00:00.2: [1022:1631] type 00 class 0x080600 [0.331559] pci :00:01.0: [1022:1632] type 00 class 0x06 [0.331617] pci :00:02.0: [1022:1632] type 00 class 0x06 [0.331665] pci :00:02.1: [1022:1634] type 01 class 0x060400 [0.331715] pci :00:02.1: PME# supported from D0 D3hot D3cold [0.331767] pci :00:02.2: [1022:1634] type 01 class 0x060400 [0.331820] pci :00:02.2: PME# supported from D0 D3hot D3cold [0.331872] pci :00:02.3: [1022:1634] type 01 class 0x060400 [0.331922] pci :00:02.3: PME# supported from D0 D3hot D3cold [0.331972] pci :00:02.4: [1022:1634] type 01 class 0x060400 [0.332021] pci :00:02.4: PME# supported from D0 D3hot D3cold [0.332071] pci :00:02.5: [1022:1634] type 01 class 0x060400 [0.332120] pci :00:02.5: PME# supported from D0 D3hot D3cold [0.332169] pci :00:02.6: [1022:1634] type 01 class 0x060400 [0.332219] pci :00:02.6: PME# supported from D0 D3hot D3cold [0.332271] pci :00:02.7: [1022:1634] type 01 class 0x060400 [0.332320] pci :00:02.7: PME# supported from D0 D3hot D3cold [0.332380] pci :00:08.0: [1022:1632] type 00 class 0x06 [0.332428] pci :00:08.1: [1022:1635] type 01 class 0x060400 [0.332447] pci :00:08.1: enabling Extended Tags [0.332476] pci :00:08.1: PME# supported from D0 D3hot D3cold [0.332558] pci :00:14.0: [1022:790b] type 00 class 0x0c0500 [0.332643] pci :00:14.3: [1022:790e] type 00 class 0x060100 [0.332749] pci :00:18.0: [1022:166a] type 00 class 0x06 [0.332781] pci :00:18.1: [1022:166b] type 00 class 0x06 [0.332811] pci :00:18.2: [1022:166c] type 00 class 0x06 [0.332843] pci :00:18.3: [1022:166d] type 00 class 0x06 [0.332873] pci :00:18.4: [1022:166e] type 00 class 0x06 [0.332903] pci :00:18.5: [1022:166f] type 00 class 0x06 [0.332937] pci :00:18.6: [1022:1670] type 00 class 0x06 [0.332967] pci :00:18.7: [1022:1671] type 00 class 0x06 [0.333275] pci :01:00.0: [144d:a808] type 00 class 0x010802 [0.333291] pci :01:00.0: reg 0x10: [mem 0xfda0-0xfda03fff 64bit] [0.333485] pci :00:02.1: PCI bridge to [bus 01] [0.333489] pci :00:02.1: bridge window [mem 0xfda0-0xfdaf] [0.333534] pci :02:00.0: [10ec:8168] type 00 class 0x02 [0.333550] pci :02:00.0: reg 0x10: [io 0x4000-0x40ff] [0.333572] pci :02:00.0: reg 0x18: [mem 0xfd904000-0xfd904fff 64bit] [0.333585] pci :02:00.0: reg 0x20: [mem 0xfd90-0xfd903fff 64bit] [0.333673] pci :02:00.0: supports D1 D2 [0.333674] pci :02:00.0: PME# supported from D0 D1 D2 D3hot D3cold [0.333802] pci :00:02.2: PCI bridge to [bus 02] [0.333805] pci :00:02.2: bridge window [io 0x4000-0x4fff] [0.333807] pci :00:02.2: bridge window [mem 0xfd90-0xfd9f] [0.333868] pci :03:00.0: [10ec:8852] type 00 class 0x028000 [0.333887] pci :03:00.0: reg 0x10: [io 0x3000-0x30ff] [0.333909] pci :03:00.0: reg 0x18: [mem 0xfd80-0xfd8f 64bit] [0.334023] pci :03:00.0: supports D1 D2 [0.334023] pci :03:00.0: PME# supported from D0 D1 D2 D3hot D3cold [0.334161] pci :00:02.3: PCI bridge to [bus 03] [0.334163] pci :00:02.3: bridge window [io 0x3000-0x3fff] [0.334165] pci :00:02.3: bridge window [mem 0xfd80-0xfd8f] [0.334207] pci :04:00.0: [10ec:522a] type 00 class 0xff [0.334220] pci :04:00.0: reg 0x10: [mem 0xfd70-0xfd700fff] [
[Kernel-packages] [Bug 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
since gcc-12 is now in main, this does not affect the OEM project any longer. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in OEM Priority Project: Fix Released Status in dkms package in Ubuntu: Invalid Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
** Changed in: oem-priority Assignee: (unassigned) => Atlas Yu (pseudoc) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in OEM Priority Project: Fix Released Status in dkms package in Ubuntu: Invalid Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-oem-5.17/5.17.0.1025.23)
All autopkgtests for the newly accepted linux-meta-oem-5.17 (5.17.0.1025.23) for jammy have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu11 (amd64) r8168/8.049.02-1ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-oem-5.17 [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 1990876] Re: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module
Today this bug returned, perhaps because I plugged in a USB-A mouse, or the ethernet USC-C expansion card. As usual, this made the kworker at 90% CPU go away: ```$ sudo modprobe -r xhci_pci``` ... but now the USB ports don't work, of course. -- 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/1990876 Title: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module Status in linux package in Ubuntu: Incomplete Bug description: Using Ubuntu 22.04, as of yesterday night upon rebooting the framework laptop (which had not been rebooted for several weeks), the fans come on strong and I see, with top, a kworker process at nearly 100% CPU utilization, which makes the laptop unusable. I have an early Framework laptop with an 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz. I removed all USB-c expansion cards except for one with an USB-c pass through, to no avail. With perf I have been able to determine that the xhci_hub_control and perhaps xhci_bus_suspend are at fault. As a matter of fact, the laptop cannot suspend any more, when it was working flawlessly until the reboot. $ sudo apt install linux-tools-common linux-tools-$(uname -r) $ sudo -i # echo -1 > /proc/sys/kernel/perf_event_paranoid # perf record control-c # perf report Samples: 125K of event 'cycles', Event count (approx.): 142991820424 Overhead Command Shared Object Symbol 54.11% kworker/5:2+usb [kernel.kallsyms] [k] xhci_hub_control ◆ 7.94% kworker/5:2+usb [kernel.kallsyms] [k] xhci_bus_suspend ▒ 0.98% kworker/5:2+usb [kernel.kallsyms] [k] kfree ▒ 0.86% kworker/5:2+usb [kernel.kallsyms] [k] _raw_spin_lock_irqsave ... What can be done to address this issue with a kworker? I suspect perhaps the new kernel is at fault. I tried rebooting to the prior kernel 5.15.0-47-generic and 5.15.0-46-generic, but with the same result. What has changed? What can be done about this kworker and the xchi_hub_control? A temporary solution: $ sudo modprobe -r xhci_pci … which results in the kworker process disappearing from `top` (reduced CPU usage to near zero), the fans wind down, and unfortunately the ethernet expansion bay doesn’t work anymore but at least wifi does. Keyboard and touchpad also work. And suspend with deep also work well, just tested it. I assume other expansion bays will stop working too, but the laptop is at least charging: the USB-c pass-through works. See also: https://community.frame.work/t/kworker-stuck-at-near-100-cpu-usage-with-ubuntu-22-04/23053/2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 4870 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 18:14:26 2022 InstallationDate: Installed on 2022-03-11 (199 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (150 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku:
[Kernel-packages] [Bug 1990876] Re: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module
Spoke too early: today, for some reason, this bug returned. Perhaps because I plugged in a mouse, or the ethernet expansion card. -- 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/1990876 Title: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module Status in linux package in Ubuntu: Incomplete Bug description: Using Ubuntu 22.04, as of yesterday night upon rebooting the framework laptop (which had not been rebooted for several weeks), the fans come on strong and I see, with top, a kworker process at nearly 100% CPU utilization, which makes the laptop unusable. I have an early Framework laptop with an 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz. I removed all USB-c expansion cards except for one with an USB-c pass through, to no avail. With perf I have been able to determine that the xhci_hub_control and perhaps xhci_bus_suspend are at fault. As a matter of fact, the laptop cannot suspend any more, when it was working flawlessly until the reboot. $ sudo apt install linux-tools-common linux-tools-$(uname -r) $ sudo -i # echo -1 > /proc/sys/kernel/perf_event_paranoid # perf record control-c # perf report Samples: 125K of event 'cycles', Event count (approx.): 142991820424 Overhead Command Shared Object Symbol 54.11% kworker/5:2+usb [kernel.kallsyms] [k] xhci_hub_control ◆ 7.94% kworker/5:2+usb [kernel.kallsyms] [k] xhci_bus_suspend ▒ 0.98% kworker/5:2+usb [kernel.kallsyms] [k] kfree ▒ 0.86% kworker/5:2+usb [kernel.kallsyms] [k] _raw_spin_lock_irqsave ... What can be done to address this issue with a kworker? I suspect perhaps the new kernel is at fault. I tried rebooting to the prior kernel 5.15.0-47-generic and 5.15.0-46-generic, but with the same result. What has changed? What can be done about this kworker and the xchi_hub_control? A temporary solution: $ sudo modprobe -r xhci_pci … which results in the kworker process disappearing from `top` (reduced CPU usage to near zero), the fans wind down, and unfortunately the ethernet expansion bay doesn’t work anymore but at least wifi does. Keyboard and touchpad also work. And suspend with deep also work well, just tested it. I assume other expansion bays will stop working too, but the laptop is at least charging: the USB-c pass-through works. See also: https://community.frame.work/t/kworker-stuck-at-near-100-cpu-usage-with-ubuntu-22-04/23053/2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 4870 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 18:14:26 2022 InstallationDate: Installed on 2022-03-11 (199 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (150 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0B dmi.product.version: AB dmi.sys.vendor: Framework To manage notifications about this bug go to:
[Kernel-packages] [Bug 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in OEM Priority Project: Fix Released Status in dkms package in Ubuntu: Invalid Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] Re: SSD disappears on Reboot but on cold boot is detected
I have a similar problem. is there any solution for it? -- 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/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer
I've successfully tested and verified this on kinetic and jammy as part of LP#1996069. Now tested on focal on top: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.5 LTS Release:20.04 Codename: focal $ uname -a Linux hwe0008 5.4.0-136-generic #153-Ubuntu SMP Thu Nov 24 15:57:18 UTC 2022 s390x s390x s390x GNU/Linux ubuntu@hwe0008:~$ ls check_sb_trailer.sh $ sudo ./check_sb_trailer.sh /boot/vmlinuz-5.4.0-136-generic Checking secure boot trailer of file /boot/vmlinuz-5.4.0-136-generic * Read 32 bytes at offset 0091f218: 02107e4d6f64756c65207369676e617475726520617070656e6465647e0a * Found signature marker - skipping 568 bytes * Read 32 bytes at offset 0091efe0: 00207a49504c * Success - Linux kernel trailer found $ I'm adjusting the tags accordingly ... ** Tags removed: verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-focal verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996071 Title: [UBUNTU 20.04] boot: Add s390x secure boot trailer Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: SRU Justification: == [Impact] * Secure boot of Linux on s390x will no longer be possible with an upcoming IBM zSystems firmware update. [Fix] * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add secure boot trailer" for kinetic and jammy * https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch backport for focal [Test Plan] * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is required. * Ensure that 'Enable Secure Boot for Linux' is marked in case 'SCSI Load' is selected at the HMCs Load task and Activation Profile. * Perform an Ubuntu Server installation, either 20.04 or 22.04 (latest ISO). It will be a secure boot installation by default in case 'Enable Secure Boot for Linux' was marked. * Check sysfs: /sys/firmware/ipl/has_secure '1' indicates hw support for secure boot, otherwise '0' /sys/firmware/ipl/secure '1' indicates that secure IPL was successful, otherwise '0' * Navigate to the HMC task 'System information' and check the active firmware release. * Ensure that Ubuntu is still bootable in secure-boot mode with the updated firmware active, by for example doing a reboot after the firmware upgrade. * There is also a way to test the trailer on systems that do not have the updated firmware yet - in this case use the following script: https://launchpadlibrarian.net/633126861/check_sb_trailer.sh [Where problems could occur] * The 'trailer' might be broken, invalid or in a wrong format and can't be identified or read properly, or may cause issues while compressing/decompressing the kernel. * In worst case secure boot might become broken, even on systems that are still on the unpatched firmware level. * Or secure boot will become broken in general. [Other Info] * The above commit was upstream accepted with v6.1-rc3. * And it got tagged for upstream stable with: "Cc: # 5.2+" * But since this bug is marked as critical, and the patch is relatively short, traceable and s390x-specific, I'll go ahead and submit this patch for Jammy and Focal ahead of upstream stable. * Since on focal file 'vmlinux.lds.S' is at a different location 'arch/s390/boot/compressed/' instead of 'arch/s390/boot/' and the context is slightly different, the backport is needed. * It's planned to have kernel 6.2 in lunar (23.04), hence it will have the patch incl. when at the planned target level. __ Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel To manage notifications about this bug go to:
[Kernel-packages] [Bug 1945868] Re: focal kvm virtio_net set_features failed (-22)
Could be closed meanwhile. I needed to shut kvm down on this system and can not get/generate the required reports/infos any more. It has been working with e1000 drivers last. -- 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/1945868 Title: focal kvm virtio_net set_features failed (-22) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Setup linux-modules-5.4.0-88-generic within focal guest on a (equal) ubuntu 20.04 kvm bare metal machine. When using virtio as network driver it is failing with: net eth0: Fail to set guest offload. virtio_net virtio1 eth0: set_features() failed (-22); wanted 0x008000174a29, left 0x0 0800017ca29 followed by further kern log entries: [ cut here ] netdevice: br0: failed to disable 0x8000 on eth0! WARNING: CPU: 0 PID: 1048 at net/core/dev.c:8683 __netdev_update_features+0x4d1/0x9f0 Modules linked in: macvlan virtio_gpu ttm drm_kms_helper fb_sys_fops input_leds syscopyarea joydev sysfillrect serio_raw sysimgblt mac_hid sch_fq_codel 9p fscache 9pnet_virtio 9pnet bridge stp llc drm virtio_rng ip_tables x_tables autofs4 dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c psmouse virtio_net i2c_piix4 virtio_blk net_failover failover pata_acpi floppy CPU: 0 PID: 1048 Comm: brctl Tainted: GW 5.4.0-88-generic #99-Ubuntu Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 RIP: 0010:__netdev_update_features+0x4d1/0x9f0 Code: c7 c2 9b 30 9b a0 4c 8b 4d 88 48 85 c0 4d 0f 44 d4 4d 89 f0 48 8d 4d b8 4c 89 ca 4c 89 d6 48 c7 c7 d0 94 a3 a0 e8 dc 2d 19 00 <0f> 0b e9 5b fe ff ff 8b 45 9c 85 c0 0f 84 96 00 00 00 8b 45 9c f7 RSP: 0018:bf1840e0ba98 EFLAGS: 00010282 RAX: RBX: 000f RCX: 0006 RDX: 0007 RSI: 0082 RDI: 9c2c13a178c0 RBP: bf1840e0bb10 R08: 02d1 R09: 0004 R10: R11: 0001 R12: 9c2c0b258000 R13: 9c2c0b2580c0 R14: 9c2c0615a000 R15: 000f FS: 7f98be558580() GS:9c2c13a0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fffc24a1080 CR3: 00030b3e4000 CR4: 06f0 Call Trace: netdev_update_features+0x25/0x60 br_device_event+0x20f/0x300 [bridge] notifier_call_chain+0x55/0x80 raw_notifier_call_chain+0x16/0x20 call_netdevice_notifiers_info+0x2e/0x60 netdev_update_features+0x59/0x60 dev_disable_lro+0x21/0xf0 br_add_if+0x301/0x650 [bridge] add_del_if+0x67/0x80 [bridge] br_dev_ioctl+0x54/0x80 [bridge] dev_ifsioc+0xe5/0x3e0 ? _cond_resched+0x19/0x30 dev_ioctl+0x2dd/0x470 sock_do_ioctl+0xa8/0x140 ? evict+0x14c/0x1b0 sock_ioctl+0x24f/0x3c0 ? _cond_resched+0x19/0x30 ? get_max_files+0x20/0x20 do_vfs_ioctl+0x407/0x670 ksys_ioctl+0x67/0x90 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f98be47c50b Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 RSP: 002b:7ffd783321e8 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 0002 RCX: 7f98be47c50b RDX: 7ffd78332210 RSI: 89a2 RDI: 0003 RBP: 7ffd78332210 R08: 0020 R09: fefefeff77686d74 R10: 7ffd78333e80 R11: 0246 R12: 7ffd78333e7e R13: 7ffd78333e7e R14: R15: ---[ end trace 240d361752e8f3f0 ]--- [ cut here ] Temporary solution is to return to the old rtl8139 driver and slow network down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995903] Re: Can't boot with kernel 5.15.0-52
I think so. Good to hear it's working on latest kernel, since I am not that familiar with the nvidia driver dependency :) -- 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/1995903 Title: Can't boot with kernel 5.15.0-52 Status in linux package in Ubuntu: Confirmed Bug description: These packages are installed: linux-image-5.15.0-50-generic/jammy-updates,jammy-security,now 5.15.0-50.56 amd64 [installed,automatic] linux-image-5.15.0-52-generic/jammy-updates,jammy-security,now 5.15.0-52.58 amd64 [installed,automatic] After grub and booting, there's some text appears, and then the screen goes blank. After forcing the computer to turn off, I boot again but using 5.15.0-50, it can boot like usual. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fikr4n 2015 F pulseaudio /dev/snd/controlC0: fikr4n 2015 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 8 08:57:48 2022 InstallationDate: Installed on 2021-06-05 (520 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ENVY Laptop 15-ep0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-28 (71 days ago) dmi.bios.date: 07/30/2021 dmi.bios.release: 15.7 dmi.bios.vendor: AMI dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 878E dmi.board.vendor: HP dmi.board.version: 18.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 18.33 dmi.modalias: dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6: dmi.product.family: 103C_5335KV HP ENVY dmi.product.name: HP ENVY Laptop 15-ep0xxx dmi.product.sku: 16P91PA#AR6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use
Does this issue happen when lg-laptop module is blacklisted? -- 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/1987829 Title: LG Gram 12gen high CPU use when USB-C/TB is in use Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: LG Gram laptop 17Z90Q with a Core i7-1260P CPU. Whenever an external monitor is connected to USB-C/Thunderbolt 4, average load goes above 3.0 and the machine is getting very hot. Output from top -H shows a lot of kworker CPU usage: top - 11:45:06 up 33 min, 2 users, load average: 3,30, 3,08, 2,79 Threads: 1442 total, 2 running, 1440 sleeping, 0 stopped, 0 zombie %Cpu(s): 0,1 us, 3,7 sy, 0,0 ni, 96,1 id, 0,0 wa, 0,0 hi, 0,1 si, 0,0 st MiB Mem : 15684,6 total, 8510,2 free, 2580,8 used, 4593,6 buff/cache MiB Swap: 3815,0 total, 3815,0 free, 0,0 used. 11326,9 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ WCHAN COMMAND 7766 root 20 0 0 0 0 R 19,8 0,0 0:56.05 worker_th+ kworker/0:2-events 196 root 20 0 0 0 0 D 15,8 0,0 1:18.12 ec_guard kworker/u32:2+USBC000:00-con0 10237 root 20 0 0 0 0 I 12,9 0,0 0:26.44 worker_th+ kworker/0:0-events 1027 root 20 0 0 0 0 I 6,6 0,0 0:43.30 worker_th+ kworker/1:3-events 10971 root 20 0 0 0 0 I 4,0 0,0 0:00.20 worker_th+ kworker/15:0-events 175 root 20 0 0 0 0 I 2,3 0,0 0:03.24 worker_th+ kworker/11:1-events 2410 root 20 0 0 0 0 I 1,7 0,0 0:05.49 worker_th+ kworker/9:3-events Perf shows a lot of time spent inside handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read. Additionally, kernel log is getting spammed with these lines every 4 seconds (but also without any USB-C device attached): [ 223.514304] ACPI Error: No handler for Region [XIN1] (f2ad4f1f) [UserDefinedRegion] (20210730/evregion-130) [ 223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no handler (20210730/exfldio-261) [ 223.514337] Initialized Local Variables for Method [_TMP]: [ 223.514339] Local0: 21495082Integer 0034 [ 223.514349] No Arguments are initialized for method [_TMP] [ 223.514354] ACPI Error: Aborting method \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1678 F pulseaudio /dev/snd/controlC1: me 1678 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Aug 26 11:57:05 2022 InstallationDate: Installed on 2022-08-25 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LG Electronics 17Z90Q-G.AA78N ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=e2f96916-a67c-432e-b687-730071271216 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: A1ZG0380 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17Z90Q dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.ec.firmware.release: 33.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrA1ZG0380X64:bd07/06/2022:br0.1:efr33.0:svnLGElectronics:pn17Z90Q-G.AA78N:pvr0.1:rvnLGElectronics:rn17Z90Q:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:skuEVO: dmi.product.family: LG gram PC dmi.product.name: 17Z90Q-G.AA78N dmi.product.sku: EVO dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1997213] Re: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add
The AHCI controller LPM policy was default to low power, which doesn't support hotplug. Please change "/sys/class/scsi_host/hostX/link_power_management_policy" to max_performance [1] to support hotplug. https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class- scsi_host -- 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/1997213 Title: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add Status in linux package in Ubuntu: Confirmed Bug description: Description: After installing Ubuntu 22.04 and boot to OS, we try to hot add a SATA disk to the Onboard AHCI controller in our system by plugging a SATA disk into the SATA slot, However, the OS can not recognize the added disks, both running command "lsblk" and "lsscsi", even "ll /sys/class/block/" couldn't find these disks we added before, and there isn't any log show up in /var/log/syslog after adding this SATA disks. Produce Steps: 1. Install Ubunut 22.04 (kernel 5.15.0-25.25-generic) 2. Boot into OS 3. Hot plug a SATA disk into SATA slot in the front bay 4. wait and observe whether the disks are show up by command "lsblk" Configuration: Systems：Lenovo SR655, AMD GENOA platform OS:ubuntu-22.04-live-server-amd64.iso CPU:AMD EPYC 9654 96-Core Processor *1 Memory:Hynix 32GB 2RX8 DDR5-4800 16Gbit RDIMM M-Die *12 storage： 7MM Drive 0-1：7.68TB 7MM NVMe SSD（PN：MTFDKCB7T6TFR，FW：E2MU110） Drive 0：240GB SATA SSD （PN：SSS7B07725 ，FW：MQ31） Drive 1-2：1.92TB NVMe SSD（PN：SSDPF2KX019T1O，FW：9CV10320） Drive 3-4：400GB NVMe SSD（PN：SSDPF21Q400GB，FW：L0310600） Drive 5-8：12.0TB SATA HDD（PN：01GV193，FW：LEGNK9R5） Drive 9：240GB SATA SSD（PN：SSS7B07725，FW：MQ31） Drive 10-11：960GB SATA SSD（PN：SSS7A43198，FW：MP33） Expected results: OS can recognize the SATA disks we hot added in. Actual results: OS cannot recognize SATA disks we hot added in. Additional info: 1. Hot add more SATA disks to different slot, "lsblk" couldn't show up the added disks as well. 2. Other OS like RHEL9.0 can recognize this hot added disks. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Nov 14 17:16 seq crw-rw+ 1 root audio 116, 33 Nov 14 17:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-14 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Lenovo ThinkSystem SR645 V3 MB,Genoa,DDR5,Oahu,1U Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/14/2022 dmi.bios.release: 1.20 dmi.bios.vendor: Lenovo dmi.bios.version: KAE105D-1.20 dmi.board.asset.tag: None dmi.board.name: SB27B31174 dmi.board.vendor: Lenovo dmi.board.version: 04 dmi.chassis.asset.tag: None dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLenovo:bvrKAE105D-1.20:bd11/14/2022:br1.20:efr1.20:svnLenovo:pnThinkSystemSR645V3MB,Genoa,DDR5,Oahu,1U:pvr04:rvnLenovo:rnSB27B31174:rvr04:cvnLenovo:ct23:cvrNone:sku7D9DRCZ000: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR645 V3 MB,Genoa,DDR5,Oahu,1U dmi.product.sku: 7D9DRCZ000 dmi.product.version: 04 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
Try 5.19.0-27.28 on Lunar. So let me mark it as verified since I no longer see the issue. ** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1988797 Title: pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- Fatal), type=Transaction Layer, (Requester ID) Status in HWE Next: Fix Committed Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: My kernel log periodically bursts with: [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.598564] pcieport :00:1b.0:[20] UnsupReq (First) [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.620296] pcieport :00:1b.0:[20] UnsupReq (First) [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.641867] pcieport :00:1b.0:[20] UnsupReq (First) [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.663803] pcieport :00:1b.0:[20] UnsupReq (First) [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.686267] pcieport :00:1b.0:[20] UnsupReq (First) [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 0152 This has happened even since I got the machine. It also happened with 5.15. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2477 F wireplumber /dev/snd/seq:dan2474 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 6 13:52:35 2022 InstallationDate: Installed on 2022-07-20 (47 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
file a new bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: == SRU Justification == [Impact] "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp displays" caused AMD Navi10 GFX to panic at boot. [Fix] Backport the revised version of "drm/amd/display: Add helper for blanking all dp displays". [Test] Users confirmed the issue went away with this fix. We also verified the original issue we fixed didn't reappear. [Where problems could occur] We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many cases are untested, hence the potential risk is there. == Original Bug Report == Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
Verified on 5.17.0-1025, the max brightness is changed along with the edid. ** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released 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-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980621] Re: Fix blank screen on Thinkpad ADL 4K+ panel
Verified on 5.17.0-1025.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1980621
Title:
Fix blank screen on Thinkpad ADL 4K+ panel
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-5.14 source package in Focal:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Bug description:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
It's a upstream kernel regression.
And reverted by upstream.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
Low risk, it reverts a regression and may break i915 driver.
On 5.14-oem and Jammy kernel, This commit was claimed to backport
commit 73867c8709b5 ("drm/i915/display: Remove check for low voltage sku for
max dp source rate")
But it's not kind of it.
So revert it instead.
On 5.17 kernel, revert it by upstream commit.
Unstable kernel already got it.
V2:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
Reload link rate as WA to fix the issue.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
It may break DP output on Intel platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1980621/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995941] Re: [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin2004
--
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/1995941
Title:
[UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW
wait
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification:
==
[Impact]
* In a secure execution guest, the external interrupt for the SIGP
external call order is delivered twice to a VCPU even though it was
only sent once.
* Under PV (protected virtualization), external call interrupts are
delivered by the SIGP interpretation facility, without KVM's
involvement.
But, if the receiving CPU is in enabled wait, KVM needs to wake the
receiving CPU such that the interrupt can be delivered.
Hence, in this case, the SIGP external call order causes
an interception.
* In response, KVM only needs to wake the receiving VCPU.
Interrupt delivery is then handled by the SIGP interpretation facility.
* KVM wrongly assumed it also needs to request injection for the
external call interrupt after the respective intercept, causing the
interrupt to be delivered twice:
* once through the SIGP interpretation facility
* and once through the interrupt injection control by KVM.
* Solution is to add appropriate special handling for 108 external
call intercepts.
[Fix]
* c3f0e5fd2d33 c3f0e5fd2d33d80c5a5a8b5e5d2bab2841709cc8
"KVM: s390: pv: don't present the ecall interrupt twice"
[Test Case]
* Have an Secure Execution (PV) environment setup on an
IBM z15 or LinuxONE III LPAR using Ubuntu Server 20.04 (latest).
* Apply kvm-unit-test submitted upstream:
"[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP call \
orders in enabled wait"
* Run the smp_PV kvm-unit-test: ./run_tests.sh smp_PV
* Check logs/smp_PV.log.
If system is affected, the following line can be found:
"ABORT: smp: psw wait: ecall: Unexpected external call interrupt \
(code 0x1202): on cpu 1 at 0x11958"
* If the system is not affected, the line should look like this:
"PASS: smp: psw wait: ecall: received"
[Regression Potential / What can go wrong]
* The handle_pv_notification can be wrong and misleading
in case 'ret' is not handled correctly.
* trace_kvm_s390_handle_sigp_pei might not be called correctly,
now after the if condition.
* In worst case the external interrupt could not be delivered
at all or still too often.
[Other]
* The fix/patch c3f0e5fd2d33 got upstream accepted with kernel v6.0,
so it not only needs to be applied to 20.04/5.4, but also to 22.04/5.15
and 22.10/5.19.
* But the patch got properly tagged for upstream stable:
Cc: # 5.7
Fixes: da24a0cc58ed ("KVM: s390: protvirt: Instruction emulation")
* And with that it got already picked up and is included in:
22.04 with Ubuntu-5.15.0-53.59 (currently in jammy-proposed)
22.10 with Ubuntu-5.19.0-16.16 means incl. in the release kernel.
* So the only Ubuntu release that is affected is 20.04/focal.
__
Description: KVM: PV: ext call delivered twice when receiver in PSW wait
Symptom: In a secure execution guest, the external interrupt for the
SIGP external call order is delivered twice to a VCPU even
though it was only sent once.
Problem: Under PV, external call interrupts are delivered by the SIGP
interpretation facility, without KVM's involvement. But, if the
receiving CPU is in enabled wait, KVM needs to wake the
receiving CPU such that the interrupt can be delivered. Hence,
in this case, the SIGP external call order causes an
interception. In response, KVM only needs to wake the receiving
VCPU. Interrupt delivery is then handled by the SIGP
interpretation facility.
KVM wrongfuly assumed it also needs to request injection for
the
external call interrupt after the respective intercept, causing
the interrupt to be delivered twice: once through the SIGP
interpretation facility and once through the interrupt
injection
control by KVM.
Solution: Add appropriate special handling for 108 external call
intercepts.
Reproduction: 0. Apply kvm-unit-test submitted upstream
("[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP
call orders in enabled wait").
1. Run the smp_PV kvm-unit-test:
./run_tests.sh smp_PV
[Kernel-packages] [Bug 1995041] Re: Fix ath11k deadlock on WCN6855
Verified on 5.17.0-1025 5.19.0-27 ** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995041 Title: Fix ath11k deadlock on WCN6855 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] ath11k is in deadlock when stress reboot or suspend on WCN6855. sometimes kernel hang. Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211] [Fix] Fix this by switching from using regulatory_set_wiphy_regd_sync() to regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue which handles the locking on it's own. So the ath11k workqueue can simply exit without taking any locks, avoiding the deadlock. [Test] Verified on hardware, stress reboot and suspend 30 times OK. [Where problems could occur] It may break ath11k wifi driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
Verified on 5.17.0-1025 ** 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. These commits are already in oem-6.0 and unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999153] [NEW] Azure: Fix race on per-CQ variable napi_iperf panic fix
Public bug reported: SRU Justification [Impact] This patch is requested by MSFT Linux Systems Group to backport in the 20.04 and 22.04 images in ATK. This patch set is needed for the MANA fix. [Fix] net: mana: Fix race on per-CQ variable napi work_done https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=18010ff776fa42340efc428b3ea6d19b3e7c7b21 [Test Case] Microsoft tested [Where things could go wrong] NAPI could continue to cause memory corruption and panic. [Other Info] SF: #00350135 ** Affects: linux-azure (Ubuntu) Importance: High Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Focal) Importance: High Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Jammy) Importance: High Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Kinetic) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Changed in: linux-azure (Ubuntu) Importance: Undecided => High ** Changed in: linux-azure (Ubuntu) Status: New => In Progress ** Changed in: linux-azure (Ubuntu) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Kinetic) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1999153 Title: Azure: Fix race on per-CQ variable napi_iperf panic fix Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Kinetic: In Progress Bug description: SRU Justification [Impact] This patch is requested by MSFT Linux Systems Group to backport in the 20.04 and 22.04 images in ATK. This patch set is needed for the MANA fix. [Fix] net: mana: Fix race on per-CQ variable napi work_done https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=18010ff776fa42340efc428b3ea6d19b3e7c7b21 [Test Case] Microsoft tested [Where things could go wrong] NAPI could continue to cause memory corruption and panic. [Other Info] SF: #00350135 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1999153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996112] Re: Virtual GPU driver packaging regression
Sent a fix to the kernel mailing list https://lists.ubuntu.com/archives/kernel-team/2022-December/135535.html should make it into the kernel in the next cycle ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996112 Title: Virtual GPU driver packaging regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: Several virtual machine GPU drivers were moved from linux-modules- extra to linux-modules in bug #1960633 so that users running virtualized Linux would not need to install the drivers for real hardware in linux-modules-extra. linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these drivers, but linux-modules-extra-5.19.0-23-generic does. This is a regression. Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was limited to sub-HD resolutions until I installed linux-modules- extra-5.19.0-23-generic. A previous kernel (5.15) had the modules in linux-modules: $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ The current kernel (5.19) has the modules in linux-modules-extra: $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ccherlin 2582 F wireplumber /dev/snd/seq:ccherlin 2580 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-05 (675 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 zswap.compressor=lz4 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware N/A RfKill: Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1945868] Re: focal kvm virtio_net set_features failed (-22)
Thanks for the ping Markus, let us know if you run into it again on another system e1000 as fallback is fine, but also slow IMHO. So I hope you we can one day find what it was. ** Changed in: qemu (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945868 Title: focal kvm virtio_net set_features failed (-22) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Invalid Bug description: Setup linux-modules-5.4.0-88-generic within focal guest on a (equal) ubuntu 20.04 kvm bare metal machine. When using virtio as network driver it is failing with: net eth0: Fail to set guest offload. virtio_net virtio1 eth0: set_features() failed (-22); wanted 0x008000174a29, left 0x0 0800017ca29 followed by further kern log entries: [ cut here ] netdevice: br0: failed to disable 0x8000 on eth0! WARNING: CPU: 0 PID: 1048 at net/core/dev.c:8683 __netdev_update_features+0x4d1/0x9f0 Modules linked in: macvlan virtio_gpu ttm drm_kms_helper fb_sys_fops input_leds syscopyarea joydev sysfillrect serio_raw sysimgblt mac_hid sch_fq_codel 9p fscache 9pnet_virtio 9pnet bridge stp llc drm virtio_rng ip_tables x_tables autofs4 dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c psmouse virtio_net i2c_piix4 virtio_blk net_failover failover pata_acpi floppy CPU: 0 PID: 1048 Comm: brctl Tainted: GW 5.4.0-88-generic #99-Ubuntu Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 RIP: 0010:__netdev_update_features+0x4d1/0x9f0 Code: c7 c2 9b 30 9b a0 4c 8b 4d 88 48 85 c0 4d 0f 44 d4 4d 89 f0 48 8d 4d b8 4c 89 ca 4c 89 d6 48 c7 c7 d0 94 a3 a0 e8 dc 2d 19 00 <0f> 0b e9 5b fe ff ff 8b 45 9c 85 c0 0f 84 96 00 00 00 8b 45 9c f7 RSP: 0018:bf1840e0ba98 EFLAGS: 00010282 RAX: RBX: 000f RCX: 0006 RDX: 0007 RSI: 0082 RDI: 9c2c13a178c0 RBP: bf1840e0bb10 R08: 02d1 R09: 0004 R10: R11: 0001 R12: 9c2c0b258000 R13: 9c2c0b2580c0 R14: 9c2c0615a000 R15: 000f FS: 7f98be558580() GS:9c2c13a0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fffc24a1080 CR3: 00030b3e4000 CR4: 06f0 Call Trace: netdev_update_features+0x25/0x60 br_device_event+0x20f/0x300 [bridge] notifier_call_chain+0x55/0x80 raw_notifier_call_chain+0x16/0x20 call_netdevice_notifiers_info+0x2e/0x60 netdev_update_features+0x59/0x60 dev_disable_lro+0x21/0xf0 br_add_if+0x301/0x650 [bridge] add_del_if+0x67/0x80 [bridge] br_dev_ioctl+0x54/0x80 [bridge] dev_ifsioc+0xe5/0x3e0 ? _cond_resched+0x19/0x30 dev_ioctl+0x2dd/0x470 sock_do_ioctl+0xa8/0x140 ? evict+0x14c/0x1b0 sock_ioctl+0x24f/0x3c0 ? _cond_resched+0x19/0x30 ? get_max_files+0x20/0x20 do_vfs_ioctl+0x407/0x670 ksys_ioctl+0x67/0x90 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f98be47c50b Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 RSP: 002b:7ffd783321e8 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 0002 RCX: 7f98be47c50b RDX: 7ffd78332210 RSI: 89a2 RDI: 0003 RBP: 7ffd78332210 R08: 0020 R09: fefefeff77686d74 R10: 7ffd78333e80 R11: 0246 R12: 7ffd78333e7e R13: 7ffd78333e7e R14: R15: ---[ end trace 240d361752e8f3f0 ]--- [ cut here ] Temporary solution is to return to the old rtl8139 driver and slow network down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996112] Re: Virtual GPU driver packaging regression
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow) -- 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/1996112 Title: Virtual GPU driver packaging regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: New Bug description: Several virtual machine GPU drivers were moved from linux-modules- extra to linux-modules in bug #1960633 so that users running virtualized Linux would not need to install the drivers for real hardware in linux-modules-extra. linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these drivers, but linux-modules-extra-5.19.0-23-generic does. This is a regression. Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was limited to sub-HD resolutions until I installed linux-modules- extra-5.19.0-23-generic. A previous kernel (5.15) had the modules in linux-modules: $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ The current kernel (5.19) has the modules in linux-modules-extra: $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ccherlin 2582 F wireplumber /dev/snd/seq:ccherlin 2580 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-05 (675 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 zswap.compressor=lz4 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware N/A RfKill: Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1960633] 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/1960633
Title:
Move virtual graphics drivers from linux-modules-extra to linux-
modules
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[SRU justification]
Impact: We split the drivers into linux-modules and linux-modules-extra. The
latter is only included for setups geared towards real hardware (desktops,
laptops). For VM guests the recommended setup is to use linux-virtual which
does not include linux-modules-extra but also does not depend on other
packages, like linux-firmware.
We already include most VM related drivers in the linux-modules package and
vboxvideo (since 21.10/Impish). So it makes sense to include the missing ones.
Fix: Move the following modules from linux-modules-extra into linux-modules:
- bochs-drm (though a bit aged, this was the predecessor of qemu)
- cirrus (this is a standard emulated gfx card, might not give the best
performance but better than nothing)
- virtio-gpu (KVM)
- vmwgfx (VMWare)
- drm-xen-front (Xen)
Testcase: Check linux-modules for the mentioned modules.
Regression Potential: There should be no change noticeable. Users with
linux-modules-extra installed will see no difference and those without
have additional drivers. Maybe this shows as moving from low-
resolution graphics to higher ones which maybe perform less.
--- Original Description ---
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains
kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko, so at the moment I need to
keep it installed and updated. The only way to do so conveniently is
to install linux-image-generic, which also pulls in linux-firmware,
which is ~760MB installed.
If vmwgfx was moved from linux-modules-extra to linux-modules, I could
use linux-image-virtual instead of linux-image-generic, remove linux-
firmware, linux-modules-extra, and the microcode packages, saving
substantial disk space and bandwidth.
Other virtual graphics drivers in linux-modules-extra that might be
worth moving are:
kernel/drivers/gpu/drm/bochs/bochs-drm.ko
kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
kernel/drivers/gpu/drm/xen/drm_xen_front.ko
Thank you for your consideration.
Note: Edited significantly in response to
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128103.html and
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128104.html to better reflect the underlying
problem and solution.
P.S. There are three other drivers in linux-modules-extra that seem
VMWare-related, but they are not in use in my VM and I don't know
whether they are in common enough use to justify moving them to linux-
modules. I have listed them here for completeness.
kernel/drivers/net/vsockmon.ko
kernel/drivers/ptp/ptp_vmw.ko
kernel/drivers/infiniband/hw/vmw_pvrdma/vmw_pvrdma.ko
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
[Kernel-packages] [Bug 1960633] Re: Move virtual graphics drivers from linux-modules-extra to linux-modules
** Also affects: linux (Ubuntu Lunar)
Importance: Medium
Assignee: Stefan Bader (smb)
Status: Fix Released
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Lunar)
Status: Fix Released => New
** No longer affects: linux (Ubuntu Lunar)
** No longer affects: linux (Ubuntu Kinetic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Move virtual graphics drivers from linux-modules-extra to linux-
modules
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[SRU justification]
Impact: We split the drivers into linux-modules and linux-modules-extra. The
latter is only included for setups geared towards real hardware (desktops,
laptops). For VM guests the recommended setup is to use linux-virtual which
does not include linux-modules-extra but also does not depend on other
packages, like linux-firmware.
We already include most VM related drivers in the linux-modules package and
vboxvideo (since 21.10/Impish). So it makes sense to include the missing ones.
Fix: Move the following modules from linux-modules-extra into linux-modules:
- bochs-drm (though a bit aged, this was the predecessor of qemu)
- cirrus (this is a standard emulated gfx card, might not give the best
performance but better than nothing)
- virtio-gpu (KVM)
- vmwgfx (VMWare)
- drm-xen-front (Xen)
Testcase: Check linux-modules for the mentioned modules.
Regression Potential: There should be no change noticeable. Users with
linux-modules-extra installed will see no difference and those without
have additional drivers. Maybe this shows as moving from low-
resolution graphics to higher ones which maybe perform less.
--- Original Description ---
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains
kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko, so at the moment I need to
keep it installed and updated. The only way to do so conveniently is
to install linux-image-generic, which also pulls in linux-firmware,
which is ~760MB installed.
If vmwgfx was moved from linux-modules-extra to linux-modules, I could
use linux-image-virtual instead of linux-image-generic, remove linux-
firmware, linux-modules-extra, and the microcode packages, saving
substantial disk space and bandwidth.
Other virtual graphics drivers in linux-modules-extra that might be
worth moving are:
kernel/drivers/gpu/drm/bochs/bochs-drm.ko
kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
kernel/drivers/gpu/drm/xen/drm_xen_front.ko
Thank you for your consideration.
Note: Edited significantly in response to
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128103.html and
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128104.html to better reflect the underlying
problem and solution.
P.S. There are three other drivers in linux-modules-extra that seem
VMWare-related, but they are not in use in my VM and I don't know
whether they are in common enough use to justify moving them to linux-
modules. I have listed them here for completeness.
kernel/drivers/net/vsockmon.ko
kernel/drivers/ptp/ptp_vmw.ko
kernel/drivers/infiniband/hw/vmw_pvrdma/vmw_pvrdma.ko
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
[Kernel-packages] [Bug 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
I've tested linux-azure/5.19.0-1014.15 in kinetic-proposed and confirmed it fixes the issue uname -a Linux myvm-k 5.19.0-1014-azure #15-Ubuntu SMP Mon Nov 28 19:54:09 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux steps: create an ARM64 VM on azure create 8 VFs and attach to the VM with 5.19.0-1014-azure, VM can boot successfully without any issue ** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1996117 Title: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] SRIOV tests fail where sometimes 0 and other times only 6 VF devices are detected instead of 8. This is using the 5.19 Edge kernel. Example failure from LISA test run - Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected <6> to be equal to <8>, but was not. Microsoft has requested the inclusion of [1], now in linux-next. 1 - https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] Microsoft tested [Where things could go wrong] VNICs could go undetected. [Other Info] SF: #00346751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
Hi Tim, I've tested kinetic azure kernel and it works perfectly but when I check jammy azure kernel, this patch seems not in the git tree has it been merged to the jammy azure kernel too? Thanks, Gerald -- 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/1996117 Title: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] SRIOV tests fail where sometimes 0 and other times only 6 VF devices are detected instead of 8. This is using the 5.19 Edge kernel. Example failure from LISA test run - Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected <6> to be equal to <8>, but was not. Microsoft has requested the inclusion of [1], now in linux-next. 1 - https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] Microsoft tested [Where things could go wrong] VNICs could go undetected. [Other Info] SF: #00346751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996112] Re: Virtual GPU driver packaging regression
** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** No longer affects: linux (Ubuntu Lunar) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996112 Title: Virtual GPU driver packaging regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: New Bug description: Several virtual machine GPU drivers were moved from linux-modules- extra to linux-modules in bug #1960633 so that users running virtualized Linux would not need to install the drivers for real hardware in linux-modules-extra. linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these drivers, but linux-modules-extra-5.19.0-23-generic does. This is a regression. Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was limited to sub-HD resolutions until I installed linux-modules- extra-5.19.0-23-generic. A previous kernel (5.15) had the modules in linux-modules: $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ The current kernel (5.19) has the modules in linux-modules-extra: $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ccherlin 2582 F wireplumber /dev/snd/seq:ccherlin 2580 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-05 (675 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 zswap.compressor=lz4 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware N/A RfKill: Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996112/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1989334] Re: remove circular dep between linux-image and modules
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989334 Title: remove circular dep between linux-image and modules Status in linux package in Ubuntu: Expired Bug description: remove circular dep between linux-image and modules Currently we have circular dependencies between linux-image and linux- modules/linux-modules-extra packages. This is redundant, and harmful when additional types of linux-images are provided (i.e. kernel.efi). Break the circular dependency by only keeping linux-image -> linux- modules dep, remove linux-modules -> linux-image dep, remove linux- modules-extra -> linux-image dep, add linux-modules-extra -> linux- modules dep. this is now applied in kinetic:linux, next need to apply to this to derivative kernels, and then we can roll it out to jammy too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync
The second of the patches mentioned in #27 (with git SHA 1e2677...) has, I believe, been backported to Ubuntu kernels 5.15.0-48 and 5.4.0-126. We've still hit this with Ubuntu Jammy on 5.15.0-53, so I guess the first commit needs to be backported as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062] md_handle_request+0x12d/0x1a0 [921588.559065] ? __part_start_io_acct+0x51/0xf0 [921588.559068] md_submit_bio+0xca/0x100 [921588.559071] submit_bio_noacct+0x112/0x4f0 [921588.559075] submit_bio+0x51/0x1a0 [921588.559077] ? _cond_resched+0x19/0x30 [921588.559081] ? kmem_cache_alloc+0x38e/0x440 [921588.559084] ? ext4_init_io_end+0x1f/0x50
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
It is a minipc - Asus PN51-E1, using a laptop class chipset I'd guess. There is no internal display. I forgot to mention I'm on Focal. based on my rudimentary assessment, this bug was fixed in the latest focal kernel. As this bug report only indicates Jammy, I figured I'd point out I'm using Focal and it seems to have changed behavior (for the better). I will create a new bug if the crashes/freezes return. -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: == SRU Justification == [Impact] "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp displays" caused AMD Navi10 GFX to panic at boot. [Fix] Backport the revised version of "drm/amd/display: Add helper for blanking all dp displays". [Test] Users confirmed the issue went away with this fix. We also verified the original issue we fixed didn't reappear. [Where problems could occur] We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many cases are untested, hence the potential risk is there. == Original Bug Report == Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
** Tags removed: kernel-spammed-bionic-linux-azure-4.15 kernel-spammed-jammy-linux-bluefield kernel-spammed-kinetic-linux verification-needed-bionic verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-bionic verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Bug description: IMPACT: Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak Suggested-by: Rafael J. Wysocki Signed-off-by: Dave Hansen Reviewed-by: Mario Limonciello Tested-by: K Prateek Nayak Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com FIX: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 TESTCASE: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
This bug is awaiting verification that the linux/5.19.0-27.28 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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 removed: verification-done-kinetic ** Tags added: kernel-spammed-kinetic-linux verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Bug description: IMPACT: Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak Suggested-by: Rafael J. Wysocki Signed-off-by: Dave Hansen Reviewed-by: Mario Limonciello Tested-by: K Prateek Nayak Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com FIX: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 TESTCASE: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998857] Re: tick/rcu: Stop allowing RCU_SOFTIRQ in idle
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Bodong Wang (bodong-wang) ** Changed in: linux-bluefield (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Jammy) Assignee: (unassigned) => Bodong Wang (bodong-wang) -- 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/1998857 Title: tick/rcu: Stop allowing RCU_SOFTIRQ in idle Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: In Progress Status in linux-bluefield source package in Jammy: In Progress Bug description: * Explain the bug RCU_SOFTIRQ used to be special in that it could be raised on purpose within the idle path to prevent from stopping the tick. Some code still prevents from unnecessary warnings related to this specific behaviour while entering in dynticks-idle mode. However the nohz layout has changed quite a bit in ten years, and the removal of CONFIG_RCU_FAST_NO_HZ has been the final straw to this safe-conduct. Now the RCU_SOFTIRQ vector is expected to be raised from sane places. * Brief explanation of fixes Stop allowing RCU_SOFTIRQ in idle * How to test In boot dmesg, the warning should be gone. * What it could break. N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1998857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998863] Re: mlxbf-pmc: Fix event string typo
** Also affects: linux-bluefield (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-bluefield (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux-bluefield (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-bluefield (Ubuntu Focal)
Assignee: (unassigned) => James Hurley (hurleyjames)
** Changed in: linux-bluefield (Ubuntu Focal)
Assignee: James Hurley (hurleyjames) => James Hurley (jamesp-hurl)
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-bluefield (Ubuntu Jammy)
Assignee: (unassigned) => James Hurley (jamesp-hurl)
** Changed in: linux-bluefield (Ubuntu Jammy)
Importance: Undecided => Medium
--
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/1998863
Title:
mlxbf-pmc: Fix event string typo
Status in linux-bluefield package in Ubuntu:
New
Status in linux-bluefield source package in Focal:
In Progress
Status in linux-bluefield source package in Jammy:
In Progress
Bug description:
SRU Justification:
[Impact]
Due to a typo, duplicate events are shown
[Fix]
* Fix event name typo.
[Test Case]
* cd /sys/class/hwmon/hwmon0/tilenetX ("X" may be 0..7)
root@localhost:/sys/class/hwmon/hwmon0/tilenet3# cat event_list | grep CRED
15: CDN_DIAG_N_OUT_OF_CRED
16: CDN_DIAG_S_OUT_OF_CRED
17: CDN_DIAG_E_OUT_OF_CRED
18: CDN_DIAG_W_OUT_OF_CRED
19: CDN_DIAG_C_OUT_OF_CRED
25: DDN_DIAG_N_OUT_OF_CRED
26: DDN_DIAG_S_OUT_OF_CRED
27: DDN_DIAG_E_OUT_OF_CRED
28: DDN_DIAG_W_OUT_OF_CRED
29: DDN_DIAG_C_OUT_OF_CRED
35: NDN_DIAG_N_OUT_OF_CRED <== Incorrectly was set to NDN_DIAG_S_OUT_OF_CRED
36: NDN_DIAG_S_OUT_OF_CRED
37: NDN_DIAG_E_OUT_OF_CRED
38: NDN_DIAG_W_OUT_OF_CRED
39: NDN_DIAG_C_OUT_OF_CRED
[Regression Potential]
* Duplicate events still get shown
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1998863/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999179] [NEW] Focal update: v5.4.223 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.223 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999179 Title: Focal update: v5.4.223 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.223 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
Crash just happened again (with nvidia 515 drivers). Here's the Xorg crash; let me know if you want any of the others: https://drive.google.com/file/d/19qiKkTHZH5iuxUpmMTmxjn5fTZpg- RVc/view?usp=share_link I tried ubuntu-bug, but it generated a 0-length .upload file so I have no ID. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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.141.03 Thu Jun 30 18:45:31 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: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=30826023-39fe-4d5c-8720-a3a2d86c4839 ro enable_mtrr_cleanup
[Kernel-packages] [Bug 1999179] Re: Focal update: v5.4.223 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.223 upstream stable release + from git://git.kernel.org/ -v5.4.223 upstream stable release -from git://git.kernel.org/ + can: j1939: transport: j1939_session_skb_drop_old(): spin_unlock_irqrestore() before kfree_skb() + can: kvaser_usb: Fix possible completions during init_completion + ALSA: Use del_timer_sync() before freeing timer + ALSA: au88x0: use explicitly signed char + USB: add RESET_RESUME quirk for NVIDIA Jetson devices in RCM + usb: dwc3: gadget: Stop processing more requests on IMI + usb: dwc3: gadget: Don't set IMI for no_interrupt + usb: bdc: change state when port disconnected + usb: xhci: add XHCI_SPURIOUS_SUCCESS to ASM1042 despite being a V0.96 controller + mtd: rawnand: marvell: Use correct logic for nand-keep-config + xhci: Remove device endpoints from bandwidth list when freeing the device + tools: iio: iio_utils: fix digit calculation + iio: light: tsl2583: Fix module unloading + fbdev: smscufx: Fix several use-after-free bugs + mac802154: Fix LQI recording + drm/msm/dsi: fix memory corruption with too many bridges + drm/msm/hdmi: fix memory corruption with too many bridges + mmc: core: Fix kernel panic when remove non-standard SDIO card + kernfs: fix use-after-free in __kernfs_remove + perf auxtrace: Fix address filter symbol name match for modules + s390/futex: add missing EX_TABLE entry to __futex_atomic_op() + s390/pci: add missing EX_TABLE entries to __pcistg_mio_inuser()/__pcilg_mio_inuser() + xfs: finish dfops on every insert range shift iteration + xfs: clear XFS_DQ_FREEING if we can't lock the dquot buffer to flush + xfs: force the log after remapping a synchronous-writes file + Xen/gntdev: don't ignore kernel unmapping error + xen/gntdev: Prevent leaking grants + mm,hugetlb: take hugetlb_lock before decrementing h->resv_huge_pages + net: ieee802154: fix error return code in dgram_bind() + media: v4l2: Fix v4l2_i2c_subdev_set_name function documentation + drm/msm: Fix return type of mdp4_lvds_connector_mode_valid + arc: iounmap() arg is volatile + ALSA: ac97: fix possible memory leak in snd_ac97_dev_register() + tipc: fix a null-ptr-deref in tipc_topsrv_accept + net: netsec: fix error handling in netsec_register_mdio() + x86/unwind/orc: Fix unreliable stack dump with gcov + amd-xgbe: fix the SFP compliance codes check for DAC cables + amd-xgbe: add the bit rate quirk for Molex cables + kcm: annotate data-races around kcm->rx_psock + kcm: annotate data-races around kcm->rx_wait + net: fix UAF issue in nfqnl_nf_hook_drop() when ops_init() failed + net: lantiq_etop: don't free skb when returning NETDEV_TX_BUSY + tcp: fix indefinite deferral of RTO with SACK reneging + can: mscan: mpc5xxx: mpc5xxx_can_probe(): add missing put_clock() in error path + PM: hibernate: Allow hybrid sleep to work with s2idle + media: vivid: s_fbuf: add more sanity checks + media: vivid: dev->bitmap_cap wasn't freed in all cases + media: v4l2-dv-timings: add sanity checks for blanking values + media: videodev2.h: V4L2_DV_BT_BLANKING_HEIGHT should check 'interlaced' + i40e: Fix ethtool rx-flow-hash setting for X722 + i40e: Fix VF hang when reset is triggered on another VF + i40e: Fix flow-type by setting GL_HASH_INSET registers + net: ksz884x: fix missing pci_disable_device() on error in pcidev_init() + PM: domains: Fix handling of unavailable/disabled idle states + ALSA: aoa: i2sbus: fix possible memory leak in i2sbus_add_dev() + ALSA: aoa: Fix I2S device accounting + openvswitch: switch from WARN to pr_warn + net: ehea: fix possible memory leak in ehea_register_port() + nh: fix scope used to find saddr when adding non gw nh + net/mlx5e: Do not increment ESN when updating IPsec ESN state + net/mlx5: Fix possible use-after-free in async command interface + net: enetc: survive memory pressure without crashing + can: rcar_canfd: rcar_canfd_handle_global_receive(): fix IRQ storm on global FIFO receive + Linux 5.4.223 + UBUNTU: Upstream stable to v5.4.223 -- You received this bug notification because you are a member of
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
Oh actually not being fully up to date might make your crash reports get rejected. Please do: sudo apt update sudo apt full-upgrade and reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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.141.03 Thu Jun 30 18:45:31 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: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=30826023-39fe-4d5c-8720-a3a2d86c4839 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=8M mtrr_chunk_size=32M quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus:
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
Alright we can give up on the automated crash reports for now. Next would be to improve the quality of the stack trace that Xorg writes to its log. You can do that by installing the debug symbols packages. Assuming your system is fully up to date: sudo apt update sudo apt full-upgrade then next install the "dbgsym" files from: https://launchpad.net/ubuntu/+source/xorg- server/2:21.1.3-2ubuntu2.4/+build/24877323 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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.141.03 Thu Jun 30 18:45:31 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: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H
[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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 removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-bluefield verification-needed-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/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Bug description: IMPACT: Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak Suggested-by: Rafael J. Wysocki Signed-off-by: Dave Hansen Reviewed-by: Mario Limonciello Tested-by: K Prateek Nayak Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com FIX: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 TESTCASE: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989334] Re: remove circular dep between linux-image and modules
This bug is awaiting verification that the linux- lowlatency/5.19.0-1013.14 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-kinetic' to 'verification- done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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 removed: verification-done-kinetic ** Tags added: kernel-spammed-kinetic-linux-lowlatency verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989334 Title: remove circular dep between linux-image and modules Status in linux package in Ubuntu: Expired Bug description: remove circular dep between linux-image and modules Currently we have circular dependencies between linux-image and linux- modules/linux-modules-extra packages. This is redundant, and harmful when additional types of linux-images are provided (i.e. kernel.efi). Break the circular dependency by only keeping linux-image -> linux- modules dep, remove linux-modules -> linux-image dep, remove linux- modules-extra -> linux-image dep, add linux-modules-extra -> linux- modules dep. this is now applied in kinetic:linux, next need to apply to this to derivative kernels, and then we can roll it out to jammy too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency/5.19.0.1013.10)
All autopkgtests for the newly accepted linux-meta-lowlatency (5.19.0.1013.10) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: linux-lowlatency/5.19.0-1013.14 (amd64, arm64) dm-writeboost/unknown (arm64) digimend-dkms/unknown (arm64) systemd/251.4-1ubuntu7 (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/kinetic/update_excuses.html#linux-meta-lowlatency [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing 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 1999189] Re: Displayport monitors hang on blanking and must REISUB my 20.04.5 system
lspci-vnvn.log ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+attachment/5635171/+files/lspci-vnvn.log -- 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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: New Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] Re: Displayport monitors hang on blanking and must REISUB my 20.04.5 system
version.log ** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+attachment/5635172/+files/version.log -- 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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: New Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] [NEW] Displayport monitors hang on blanking and must REISUB my 20.04.5 system
Public bug reported: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. OS: Description: Ubuntu 20.04.5 LTS Release:20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) ** 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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: New Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] Re: Displayport monitors hang on blanking and must REISUB my 20.04.5 system
** Description changed: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test - anything with some decent instructions. + anything with some decent instructions. This issue has been going on for + a few weeks, and due to a recent hardware change I cannot confirm if + there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) -- 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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] 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 1999189 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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] Re: Displayport monitors hang on blanking and must REISUB my 20.04.5 system
apport information ** Tags added: apport-collected focal ** Description changed: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.24 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: test 20733 F pulseaudio + /dev/snd/controlC0: test 20733 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2022-02-17 (294 days ago) + InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) + MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 + 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-56-generic N/A + linux-backports-modules-5.15.0-56-generic N/A + linux-firmware 1.187.35 + Tags: focal + Uname: Linux 5.15.0-56-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 06/21/2021 + dmi.bios.release: 5.3 + dmi.bios.vendor: ASUSTeK COMPUTER INC. + dmi.bios.version: 0503 + dmi.board.asset.tag: Default string + dmi.board.name: PN51-E1 + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: To be filled by O.E.M. + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 35 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: + dmi.product.family: Vivo PC + dmi.product.name: MINIPC PN51-E1 + dmi.product.version: 0503 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635173/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition,
[Kernel-packages] [Bug 1999189] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635182/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635183/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635184/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635185/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635186/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635188/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635187/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635189/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992468] Re: segfault in ld-linux-x86-64.so
Now here's an odd thing. I just created a new mint 21 cinnamon 64bit vm: pete@pete-VirtualBox:~/phix$ ./p64 Segmentation fault (core dumped) pete@pete-VirtualBox:~/phix$ /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 ./p64 Phix hybrid interpreter/compiler. Version 1.0.2 (64 bit Linux) Copyright Pete Lomax 2006..2022 Enter ? for options or filename to execute:-test which completes fine... Though not entirely surprisingly, "-c -test" segfaults on the first one... I'm going to report this upstream as suggested as well. -- 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/1992468 Title: segfault in ld-linux-x86-64.so Status in linux package in Ubuntu: Incomplete Bug description: My manually built elf x64 file has started crashing on load, within the last month or so. It worked fine on Ubuntu 20.04.x, but fails on 22.04 - same problem on Mint 19.3 and Fedora 36. dmesg ... gives this: [ 107.121214] p[4370]: segfault at 0 ip 7f3d725b8350 sp 7ffea111fba0 error 4 in ld-linux-x86-64.so.2[7f3d72598000+2a000] [ 107.121230] Code: ff ff 00 45 31 db 48 8d 15 c9 ac 00 00 4c 8d 05 46 8f 01 00 4c 8d 2d 1f 8f 01 00 49 89 c2 48 8d 58 ff 48 89 f8 49 f7 da 66 90 <8b> 08 83 f9 07 77 19 85 c9 74 45 83 f9 07 77 40 48 63 0c 8a 48 01 You can download the offending file (a single plain 4MB ELF x64) from http://phix.x10.mx/p64 It almost certainly contains older/rarer forms of relocations and suchlike, but only about ten or so and meant to be as simple as possible. If I need to change the binary content of that file, I can, but might need a wee bit of help. Of course, if/once it gets through ld-linux-x86-64.so and complains about something else, ignore it, or should you be at all intrigued you can visit http://phix.x10.mx/download.php to get the full package. References, just in case you need them, or to ask a wider set than just me for more details direct: https://openeuphoria.org/forum/136972.wc?last_id=136973 https://github.com/petelomax/Phix/issues/13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635178/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635176/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635177/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635174/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635179/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635175/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635181/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999189] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1999189/+attachment/5635180/+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/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Incomplete Bug description: I've been getting issues with my 2 DP monitors (and system) not recovering from blanking (possibly 100% of the time). If I disable blanking, the issue never occurs. I am forced to REISUB the system to regain access. As I'm using amdgpu from the HWE kernel, my best guess is thats where the issue lies. When the issue occurs I am completely unable to access the system due to a softlock and CPU getting maxed by Xorg. SSH barely works and the system doesn't respond to request to perform dumps like Alt- PrintScreen-1. The only relevant output I have seen (as a user) is in syslog, and possibly dmseg. I am not sharing anything yet until I get some clear directions on exactly what is required and how I can share it. In addition, when I try to submit an apport-bug it fails (multiple times). Here is the Error ID: OOPS-108b77945d65b4a0f23eba000f0d8a8e while trying to wait for the launchpad page to process my data. As of now I have no way to share any data other than pasting it in a bug report. Unless there is another way to automate the data collection. Which I'd prefer by far. Finally, as I'm more of a user, I can only likely manage to test anything with some decent instructions. This issue has been going on for a few weeks, and due to a recent hardware change I cannot confirm if there was a time when my current system did not have the issue. OS: Description: Ubuntu 20.04.5 LTS Release: 20.04 System: Asus PN51-E1 (minipc), 32 GB RAM, AMD Ryzen 7 5700U with Radeon Graphics 2 DP monitors DP to DP cable USB-C to DP cable (tested without this connected and it makes no difference) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 20733 F pulseaudio /dev/snd/controlC0: test 20733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-17 (294 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-E1 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-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 1.187.35 Tags: focal Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 5.3 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: PN51-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0503:bd06/21/2021:br5.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-E1:pvr0503:rvnASUSTeKCOMPUTERINC.:rnPN51-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-E1 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
I think you probably only need https://launchpad.net/ubuntu/+source/xorg- server/2:21.1.3-2ubuntu2.4/+build/24877323/+files/xserver-xorg-core- dbgsym_21.1.3-2ubuntu2.4_amd64.ddeb assuming that's the version of xserver-xorg-core already installed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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.141.03 Thu Jun 30 18:45:31 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: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=30826023-39fe-4d5c-8720-a3a2d86c4839 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=8M
[Kernel-packages] [Bug 1996093] Re: [RELEASE BLOCKER] Call trace during nvme storage performance test in bionic/linux-azure 4.15.0-1154
This bug is awaiting verification that the linux- azure-4.15/4.15.0-1158.173 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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: kernel-spammed-bionic-linux-azure-4.15 verification-needed-bionic -- 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/1996093 Title: [RELEASE BLOCKER] Call trace during nvme storage performance test in bionic/linux-azure 4.15.0-1154 Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: In Progress Status in linux-azure source package in Focal: In Progress Status in linux-azure-4.15 source package in Focal: Invalid Bug description: SRU Justification [Impact] Hypervisor only allocates interrupts to happen on a single physical GPU, which can lead to CPU soft locks when using PCI NVME under heavy load. [Test Case] Microsoft tested [Where things could go wrong] Hypervisor PCI driver may not load correctly. Patch did not apply cleanly and could lead to merge conflicts once the upstream patch is pulled in. [Other Info] SF: #00347669 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
*** This bug is a duplicate of bug 1999213 *** https://bugs.launchpad.net/bugs/1999213 Thank you -- let me know if there's anything else I can do to help. Would crash reports from me be useful at this point or should I uninstall those debug symbols? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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.141.03 Thu Jun 30 18:45:31 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: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=30826023-39fe-4d5c-8720-a3a2d86c4839 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
*** This bug is a duplicate of bug 1999213 *** https://bugs.launchpad.net/bugs/1999213 Keep reporting crashes in case your system is experiencing multiple different ones. And it doesn't affect the system whether you leave the debug symbols installed or not. Though keeping them installed should help the stack traces in your logs to make more sense. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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.141.03 Thu Jun 30 18:45:31 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: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
Thanks, will do -- should I install all five dbgsym .ddeb files that I see there? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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.141.03 Thu Jun 30 18:45:31 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: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=30826023-39fe-4d5c-8720-a3a2d86c4839 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=8M mtrr_chunk_size=32M quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-05-14 (174 days ago) dmi.bios.date: 03/18/2014
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
Thanks -- after updating and reboot I now have ".uploaded" files. _usr_lib_xorg_Xorg.0.uploaded: c0b761f4-7781-11ed-b5f8-fa163ef35206 I have installed that .ddeb and will report when/if another crash happens (it is indeed the same version). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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.141.03 Thu Jun 30 18:45:31 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: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=30826023-39fe-4d5c-8720-a3a2d86c4839 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=8M
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
*** This bug is a duplicate of bug 1999213 *** https://bugs.launchpad.net/bugs/1999213 Thanks. That crash is now being tracked in bug 1999213. ** This bug has been marked a duplicate of bug 1999213 Xorg crashed with SIGABRT in ActivateGrabNoDelivery() from ActivatePassiveGrab() from CheckPassiveGrabsOnWindow() from CheckDeviceGrabs() from ProcessDeviceEvent() -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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.141.03 Thu Jun 30 18:45:31 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: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine:
[Kernel-packages] [Bug 1995573] Re: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
Bug 1985869 tracks a related (same?) issue. ** Tags added: matrox ** Tags added: mgag200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995573 Title: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Screen cannot turn on after screen is off [Fix] Below commit from v6.0-rc1 fixes the issue c577b2f43e80 drm/mgag200: Enable atomic gamma lut update And applied some other commits to fix the conflicts c48a36301634 drm/mgag200: Optimize damage clips 3064debaf55e drm/mgag200: Add FB_DAMAGE_CLIPS support 5913ab941d6e drm/mgag200: Acquire I/O lock while reading EDID 931e3f3a0e99 drm/mgag200: Protect concurrent access to I/O registers with lock e13f13e039dc drm: Add DRM-managed mutex_init() [Tests] Verified on the machine with Matrox G200eW3 [102b:0536] graphics card. [Where problems could occur] The commits to solve the conflicts are trivial, and not likely to introduce regressions. The fix patch change a lot of code and hard to evaluate the risk, but check the latest linus/master tree and linux-next/master tree, there is no fixed commit for all these cherry-picked commits, so should be safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
Please upload crash files using ubuntu-bug, or try apport-cli if that fails. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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.141.03 Thu Jun 30 18:45:31 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: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=30826023-39fe-4d5c-8720-a3a2d86c4839 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=8M mtrr_chunk_size=32M quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-05-14 (174 days ago) dmi.bios.date: 03/18/2014
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
I have tried both ubuntu-bug and apport-cli; they both just return without generating an ID number (that I'm aware of), and /var/crash/_usr_lib_xorg_Xorg.0.upload is zero-length: --- # ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.0.crash *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.8 MB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s # ls -lah /var/crash/_usr_lib_xorg_Xorg.0.upload -rw-r--r-- 1 root whoopsie 0 Dec 8 11:52 /var/crash/_usr_lib_xorg_Xorg.0.upload # -- Is there something wrong with my approach there? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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.141.03 Thu Jun 30 18:45:31 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: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
Try looking for /var/crash/*.uploaded and check the contents of those files. Also try step 2 from comment #2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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.141.03 Thu Jun 30 18:45:31 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: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=30826023-39fe-4d5c-8720-a3a2d86c4839 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=8M mtrr_chunk_size=32M quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-05-14 (174 days ago)
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
Thanks -- the .upload file is zero-length (see previous comment for how I determined that.) There are no *.uploaded files present. The GUI version of the crash reporter also came up and I submitted all of those. The errors.ubuntu.com page for the whoopsie ID has none of the recent crashes shown (last one November 17th). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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.141.03 Thu Jun 30 18:45:31 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: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
