[Kernel-packages] [Bug 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages
Hoping to see the issue go away with the new Ubuntu 24.04 on a HP HP ProDesk 400 G3 DM/82A5 and it uses Intel HD Graphics 630. But nope still happens. I needed to pull the power for a bit before screen would come back properly. Is there additional information needed to troubleshoot the issue? 024-04-25T19:09:21.155484-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON mode hasn't settled 2024-04-25T19:09:21.429475-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON mode change timed out 2024-04-25T19:09:21.429481-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON mode change failed 2024-04-25T19:09:21.429482-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON resume failed 2024-04-25T19:09:21.438472-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful 2024-04-25T19:09:21.456511-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful 2024-04-25T19:09:23.289474-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON mode hasn't settled 2024-04-25T19:09:23.572475-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON mode change timed out 2024-04-25T19:09:23.572480-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON mode change failed 2024-04-25T19:09:23.572482-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON resume failed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1973098 Title: [i915] Intermittent freezing and LSPCON init failed kernel messages Status in linux package in Ubuntu: Confirmed Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: Hardware: Lenovo ThinkPad model 20ST0055AU Boot messages show: [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 During normal operation there will intermittently be a freeze for a second or two and then more of these messages display in the kernel logs: [ 505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D [ 506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D The system will then become operational again. The system is still usable, but it is annoying. I've switched onto this OEM kernel from the generic kernel (5.13), as I had other problems with 5.13 regarding external displays not coming back after idle timeouts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40 ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21 Uname: Linux 5.14.0-1036-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 12 10:29:31 2022 InstallationDate: Installed on 2021-05-05 (371 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058578] Re: Add support for several cs35l41 amplifier devices (laptop audio support)
I don't know how that got lost... "git clone" should be: git clone https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058578 Title: Add support for several cs35l41 amplifier devices (laptop audio support) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Support for the cs35l41_hda_property table has been already been backported to hwe-6.5-next: commit eec052d5cff271d7bf6854f28c62c4a6650c379b (HEAD -> hwe-6.5-next, tag: Ubuntu-hwe-6.5-6.5.0-27.28_22.04.1, origin/hwe-6.5-next) Support for several devices has been merged to torvalds/linux v6.8 tag: commit e8f897f4afef0031fe618a8e94127a0934896aba (HEAD, tag: v6.8) It would be great if the following commits for sound/pci/hda/cs35l41_hda_property.c could be cherry-picked for release in the near future (listed newest to oldest): b603d95692e47dc6f5f733e93c3841dc0c01e624 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d be220d2e5544ff094142d263db5cf94d034b5e39 c16dfab33f99fc3ff43d48253bc2784ccb84c1de 8c14dbf36424eb751d70c15f9a671549390057b2 7d65d70161ef75a3991480c91668ac11acedf211 ba7053b4b4a4ddcf530fa2b897e697004715d086 d110858a6925827609d11db8513d76750483ec06 ee694e7db47e1af00ffb29f569904a9ed576868f 916d051730ae48aef8b588fd096fefca4bc0590a ed7326a24a1a9af65fafefd86b505e7c3b968f6d 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 b592ed2e1d78a475f781802e441c499ab446975b 8c4c216db8fb84be9c4ca60d72b2066cf28f 2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f I am running on KDE neon 6.0 release 22.04 Linux Scott-Laptop 6.5.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 x86_64 x86_64 x86_64 GNU/Linux This works fine for me: #!/bin/bash git clone cd jammy git remote add upstream https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git fetch upstream git checkout hwe-6.5-next commits="2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f 8c4c216db8fb84be9c4ca60d72b2066cf28f b592ed2e1d78a475f781802e441c499ab446975b b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 ed7326a24a1a9af65fafefd86b505e7c3b968f6d 916d051730ae48aef8b588fd096fefca4bc0590a ee694e7db47e1af00ffb29f569904a9ed576868f d110858a6925827609d11db8513d76750483ec06 ba7053b4b4a4ddcf530fa2b897e697004715d086 7d65d70161ef75a3991480c91668ac11acedf211 8c14dbf36424eb751d70c15f9a671549390057b2 c16dfab33f99fc3ff43d48253bc2784ccb84c1de be220d2e5544ff094142d263db5cf94d034b5e39 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d b603d95692e47dc6f5f733e93c3841dc0c01e624" for c in $commits; do echo $c git cherry-pick $c done cp /boot/config-$(uname -r) .config make -j16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2058578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058578] [NEW] Add support for several cs35l41 amplifier devices (laptop audio support)
Public bug reported: Support for the cs35l41_hda_property table has been already been backported to hwe-6.5-next: commit eec052d5cff271d7bf6854f28c62c4a6650c379b (HEAD -> hwe-6.5-next, tag: Ubuntu-hwe-6.5-6.5.0-27.28_22.04.1, origin/hwe-6.5-next) Support for several devices has been merged to torvalds/linux v6.8 tag: commit e8f897f4afef0031fe618a8e94127a0934896aba (HEAD, tag: v6.8) It would be great if the following commits for sound/pci/hda/cs35l41_hda_property.c could be cherry-picked for release in the near future (listed newest to oldest): b603d95692e47dc6f5f733e93c3841dc0c01e624 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d be220d2e5544ff094142d263db5cf94d034b5e39 c16dfab33f99fc3ff43d48253bc2784ccb84c1de 8c14dbf36424eb751d70c15f9a671549390057b2 7d65d70161ef75a3991480c91668ac11acedf211 ba7053b4b4a4ddcf530fa2b897e697004715d086 d110858a6925827609d11db8513d76750483ec06 ee694e7db47e1af00ffb29f569904a9ed576868f 916d051730ae48aef8b588fd096fefca4bc0590a ed7326a24a1a9af65fafefd86b505e7c3b968f6d 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 b592ed2e1d78a475f781802e441c499ab446975b 8c4c216db8fb84be9c4ca60d72b2066cf28f 2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f I am running on KDE neon 6.0 release 22.04 Linux Scott-Laptop 6.5.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 x86_64 x86_64 x86_64 GNU/Linux This works fine for me: #!/bin/bash git clone cd jammy git remote add upstream https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git fetch upstream git checkout hwe-6.5-next commits="2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f 8c4c216db8fb84be9c4ca60d72b2066cf28f b592ed2e1d78a475f781802e441c499ab446975b b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 ed7326a24a1a9af65fafefd86b505e7c3b968f6d 916d051730ae48aef8b588fd096fefca4bc0590a ee694e7db47e1af00ffb29f569904a9ed576868f d110858a6925827609d11db8513d76750483ec06 ba7053b4b4a4ddcf530fa2b897e697004715d086 7d65d70161ef75a3991480c91668ac11acedf211 8c14dbf36424eb751d70c15f9a671549390057b2 c16dfab33f99fc3ff43d48253bc2784ccb84c1de be220d2e5544ff094142d263db5cf94d034b5e39 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d b603d95692e47dc6f5f733e93c3841dc0c01e624" for c in $commits; do echo $c git cherry-pick $c done cp /boot/config-$(uname -r) .config make -j16 ** Affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058578 Title: Add support for several cs35l41 amplifier devices (laptop audio support) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Support for the cs35l41_hda_property table has been already been backported to hwe-6.5-next: commit eec052d5cff271d7bf6854f28c62c4a6650c379b (HEAD -> hwe-6.5-next, tag: Ubuntu-hwe-6.5-6.5.0-27.28_22.04.1, origin/hwe-6.5-next) Support for several devices has been merged to torvalds/linux v6.8 tag: commit e8f897f4afef0031fe618a8e94127a0934896aba (HEAD, tag: v6.8) It would be great if the following commits for sound/pci/hda/cs35l41_hda_property.c could be cherry-picked for release in the near future (listed newest to oldest): b603d95692e47dc6f5f733e93c3841dc0c01e624 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d be220d2e5544ff094142d263db5cf94d034b5e39 c16dfab33f99fc3ff43d48253bc2784ccb84c1de 8c14dbf36424eb751d70c15f9a671549390057b2 7d65d70161ef75a3991480c91668ac11acedf211 ba7053b4b4a4ddcf530fa2b897e697004715d086 d110858a6925827609d11db8513d76750483ec06 ee694e7db47e1af00ffb29f569904a9ed576868f 916d051730ae48aef8b588fd096fefca4bc0590a ed7326a24a1a9af65fafefd86b505e7c3b968f6d 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 b592ed2e1d78a475f781802e441c499ab446975b 8c4c216db8fb84be9c4ca60d72b2066cf28f 2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f I am running on KDE neon 6.0 release 22.04 Linux Scott-Laptop 6.5.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 x86_64 x86_64 x86_64 GNU/Linux This works fine for me: #!/bin/bash git clone cd jammy git remote add upstream https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git fetch upstream git checkout hwe-6.5-next commits="2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f 8c4c216db8fb84be9c4ca60d72b2066cf28f b592ed2e1d78a475f781802e441c499ab446975b b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 ed7326a24a1a9af65fafefd86b505e7c3b968f6d 916d051730ae48aef8b588fd096fefca4bc0590a ee694e7db47e1af00ffb29f569904a9ed576868f d110858a6925827609d11db8513d76750483ec06 ba7053b4b4a4ddcf530fa2b897e697004715d086 7d65d70161ef75a3991480c91668ac11acedf211 8c14dbf36424eb751d70c15f9a671549390057b2 c16dfab33f99fc3ff43
[Kernel-packages] [Bug 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages
See same issue using Ubuntu 23.10 on a HP HP ProDesk 400 G3 DM/82A5 and it uses Intel HD Graphics 630. Occasionally I will get a black screen with no ability to activate which then requires a reboot. Sometimes I will need to power off and unplug hdmi cable. i915 :00:02.0: [drm] *ERROR* LSPCON mode hasn't settled 2024-02-27T13:33:30.125032-06:00 HPProDesk400 kernel: [ 3323.472414] i915 :00:02.0: [drm] *ERROR* LSPCON mode change timed out 2024-02-27T13:33:30.125049-06:00 HPProDesk400 kernel: [ 3323.472417] i915 :00:02.0: [drm] *ERROR* LSPCON mode change failed 2024-02-27T13:33:30.125049-06:00 HPProDesk400 kernel: [ 3323.472418] i915 :00:02.0: [drm] *ERROR* LSPCON resume failed 2024-02-27T13:33:30.133026-06:00 HPProDesk400 kernel: [ 3323.481193] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful 2024-02-27T13:33:30.149026-06:00 HPProDesk400 kernel: [ 3323.498313] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1973098 Title: [i915] Intermittent freezing and LSPCON init failed kernel messages Status in linux package in Ubuntu: Confirmed Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: Hardware: Lenovo ThinkPad model 20ST0055AU Boot messages show: [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 During normal operation there will intermittently be a freeze for a second or two and then more of these messages display in the kernel logs: [ 505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D [ 506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D The system will then become operational again. The system is still usable, but it is annoying. I've switched onto this OEM kernel from the generic kernel (5.13), as I had other problems with 5.13 regarding external displays not coming back after idle timeouts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40 ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21 Uname: Linux 5.14.0-1036-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 12 10:29:31 2022 InstallationDate: Installed on 2021-05-05 (371 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series
Been using 22.04 with Nvidia 390 for a long time now with no issues. Suddenly, I ran into the dkms problem with a kernel upgrade, Thankfully, I found the solution is to lock my kernel at 6.12. Hopefully I don't have to keep it that way for long! -- 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/2051457 Title: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series Status in dkms package in Ubuntu: Confirmed Status in gcc-defaults package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: Since Jammy went to the 6.5.0 kernel series, that kernel series was compiled with gcc-12. The previous 6.2.0 series kernels were compiled with gcc-11. The current version of gcc in jammy is 11.4. Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc fail to build the modules, because of a gcc compiler version mismatch between what the current running kernel was built by, and the module being built. I recognized this while helping Users with NVidia driver compile errors on the forum, and came up with this work-around for them: https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164 Summary: Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler. Since then, this work-around has helped to resolve problems with running the 6.5.0 series kernels and building modules for other applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for use with the 6.5.0 series. I have run this for over a month as my default with no ill affects. I have continued to recommend this work-around to many user to solve their problems... *** I think it is time to look at pushing through gcc-12 as the default compiler for 22.04.3 through the normal updates channel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gcc 4:11.2.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: GNOME Date: Sun Jan 28 08:23:37 2024 InstallationDate: Installed on 2022-09-19 (496 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2051457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054107] Re: Unable to boot with encrypted drive with linux-image-6.5.0-18-generic on Jammy
Not entirely sure what happened but I updated the firmware on my laptop and tried again and it worked. So not sure what the problem was, but doesn't seem to be a bug. ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054107 Title: Unable to boot with encrypted drive with linux-image-6.5.0-18-generic on Jammy Status in linux package in Ubuntu: Invalid Bug description: This morning, I installed the 6.5.0-18 updates on my Jammy system and rebooted. After rebooting, I'm unable to boot from my encrypted SSD. It reports that my passphrase is incorrect. Reverting back to 6.5.0-17 doesn't have this problem. ii linux-generic-hwe-22.04 6.5.0.18.18~22.04.10 amd64Complete Generic Linux kernel and headers ii linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-headers-generic-hwe-22.04 6.5.0.18.18~22.04.10 amd64Generic Linux kernel headers ii linux-hwe-6.5-headers-6.5.0-18 6.5.0-18.18~22.04.1 all Header files related to Linux kernel version 6.5.0 ii linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Signed kernel image generic ii linux-image-generic-hwe-22.046.5.0.18.18~22.04.10 amd64Generic Linux kernel image ii linux-modules-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054107] [NEW] Unable to boot with encrypted drive with linux-image-6.5.0-18-generic on Jammy
Public bug reported: This morning, I installed the 6.5.0-18 updates on my Jammy system and rebooted. After rebooting, I'm unable to boot from my encrypted SSD. It reports that my passphrase is incorrect. Reverting back to 6.5.0-17 doesn't have this problem. ii linux-generic-hwe-22.04 6.5.0.18.18~22.04.10 amd64Complete Generic Linux kernel and headers ii linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-headers-generic-hwe-22.04 6.5.0.18.18~22.04.10 amd64Generic Linux kernel headers ii linux-hwe-6.5-headers-6.5.0-18 6.5.0-18.18~22.04.1 all Header files related to Linux kernel version 6.5.0 ii linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Signed kernel image generic ii linux-image-generic-hwe-22.046.5.0.18.18~22.04.10 amd64Generic Linux kernel image ii linux-modules-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ** 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/2054107 Title: Unable to boot with encrypted drive with linux-image-6.5.0-18-generic on Jammy Status in linux package in Ubuntu: New Bug description: This morning, I installed the 6.5.0-18 updates on my Jammy system and rebooted. After rebooting, I'm unable to boot from my encrypted SSD. It reports that my passphrase is incorrect. Reverting back to 6.5.0-17 doesn't have this problem. ii linux-generic-hwe-22.04 6.5.0.18.18~22.04.10 amd64Complete Generic Linux kernel and headers ii linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-headers-generic-hwe-22.04 6.5.0.18.18~22.04.10 amd64Generic Linux kernel headers ii linux-hwe-6.5-headers-6.5.0-18 6.5.0-18.18~22.04.1 all Header files related to Linux kernel version 6.5.0 ii linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Signed kernel image generic ii linux-image-generic-hwe-22.046.5.0.18.18~22.04.10 amd64Generic Linux kernel image ii linux-modules-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045273] [NEW] Regression: cifs kernel module missing from linux-modules
Public bug reported: In 22.04 with the HWE kernel, the CIFS/SMB client kernel modules (cifs.ko and related ones) have been removed from linux-modules and are now in linux-modules-extra, between 6.2.0-35 and 6.2.0-36: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy $ dpkg -S cifs.ko linux-modules-6.2.0-35-generic: /lib/modules/6.2.0-35-generic/kernel/fs/cifs/cifs.ko linux-modules-extra-6.2.0-36-generic: /lib/modules/6.2.0-36-generic/kernel/fs/smb/client/cifs.ko linux-modules-extra-6.2.0-37-generic: /lib/modules/6.2.0-37-generic/kernel/fs/smb/client/cifs.ko As a result (for example), a VM with the linux-image-virtual-hwe-22.04 can no longer mount CIFS filesystems unless I switch to the full-fat linux-image-generic-hwe-22.04 kernel, which brings in several large dependencies unnecessary on a VM (firmware packages, microcode packages, thermald, upower, wireless-regdb...). Was cifs.ko removed from the base kernel packages deliberately? I consider this a regression. ** Affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045273 Title: Regression: cifs kernel module missing from linux-modules Status in linux-hwe-6.2 package in Ubuntu: New Bug description: In 22.04 with the HWE kernel, the CIFS/SMB client kernel modules (cifs.ko and related ones) have been removed from linux-modules and are now in linux-modules-extra, between 6.2.0-35 and 6.2.0-36: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy $ dpkg -S cifs.ko linux-modules-6.2.0-35-generic: /lib/modules/6.2.0-35-generic/kernel/fs/cifs/cifs.ko linux-modules-extra-6.2.0-36-generic: /lib/modules/6.2.0-36-generic/kernel/fs/smb/client/cifs.ko linux-modules-extra-6.2.0-37-generic: /lib/modules/6.2.0-37-generic/kernel/fs/smb/client/cifs.ko As a result (for example), a VM with the linux-image-virtual-hwe-22.04 can no longer mount CIFS filesystems unless I switch to the full-fat linux-image-generic-hwe-22.04 kernel, which brings in several large dependencies unnecessary on a VM (firmware packages, microcode packages, thermald, upower, wireless-regdb...). Was cifs.ko removed from the base kernel packages deliberately? I consider this a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2045273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981783]
Ubuntu 22.04 Jammy Jellyfish (x86-64) kernel 5.19.0-46-generic Started seeing this error 7/17/2023 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632255] ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20220331/psargs-330) Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632263] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632263] No Local Variables are initialized for Method [_OSC] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632264] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632264] Initialized Arguments for Method [_OSC]: (4 arguments defined for method invocation) Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632265] Arg0: dc18fbccBuffer(16) 5D A8 3B B2 B7 C8 42 35 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632270] Arg1: 34c27800Integer 0001 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632272] Arg2: 0dc8a41aInteger 0002 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632273] Arg3: 653f1daaBuffer(8) 00 00 00 00 05 00 00 00 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632277] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632278] ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20220331/psparse-529) -- 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/1981783 Title: there is an ACPI error message every time it booting Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: there is the following message every time it boots [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 11:15:30 2022 InstallationDate: Installed on 2022-04-21 (85 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1981783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983180]
Ubuntu 22.04 Jammy Jellyfish (x86-64) kernel 5.19.0-46-generic Started seeing this error 7/17/2023 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632255] ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20220331/psargs-330) Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632263] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632263] No Local Variables are initialized for Method [_OSC] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632264] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632264] Initialized Arguments for Method [_OSC]: (4 arguments defined for method invocation) Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632265] Arg0: dc18fbccBuffer(16) 5D A8 3B B2 B7 C8 42 35 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632270] Arg1: 34c27800Integer 0001 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632272] Arg2: 0dc8a41aInteger 0002 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632273] Arg3: 653f1daaBuffer(8) 00 00 00 00 05 00 00 00 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632277] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632278] ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20220331/psparse-529) -- 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/1983180 Title: ACPI Error _CPC not found Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: just recently (I guess since the last update) I get a few ACPI error messages during start up. Those are also visible with dmesg: ... [0.713907] ACPI: AC: AC Adapter [AC] (on-line) [0.713978] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 [0.714011] ACPI: button: Sleep Button [SLPB] [0.714040] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 [0.714061] ACPI: button: Lid Switch [LID] [0.714087] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [0.714105] ACPI: button: Power Button [PWRF] [0.714187] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714199] No Local Variables are initialized for Method [_CPC] [0.714201] No Arguments are initialized for method [_CPC] [0.714203] ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714395] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714404] No Local Variables are initialized for Method [_CPC] [0.714405] No Arguments are initialized for method [_CPC] [0.714407] ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714480] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714488] No Local Variables are initialized for Method [_CPC] [0.714490] No Arguments are initialized for method [_CPC] [0.714492] ACPI Error: Aborting method \_SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714640] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714651] No Local Variables are initialized for Method [_CPC] [0.714653] No Arguments are initialized for method [_CPC] [0.714655] ACPI Error: Aborting method \_SB.PR04._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714940] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714952] No Local Variables are initialized for Method [_CPC] [0.714953] No Arguments are initialized for method [_CPC] [0.714955] ACPI Error: Aborting method \_SB.PR05._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.715106] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.715118] No Local Variables are initialized for Method [_CPC] [0.715119] No Arguments are initialized for method [_CPC] [0.715121] ACPI Error: Aborting method \_SB.PR06._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.715309] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.715321] No Local Variables are initialized for Method [_CPC] [0.715322] No Arguments are initialized for method [_CPC] [0.715324] ACPI Error: Aborting method \_SB.PR07._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.715611] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00
[Kernel-packages] [Bug 2017807] Re: black screen blinking cursor upper left after updating or clean install 23.04
I removed the default nvida 390 driver and install nvida 418 driver and that resolved my issue. -- 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/2017807 Title: black screen blinking cursor upper left after updating or clean install 23.04 Status in linux package in Ubuntu: Confirmed Bug description: I have attempted to upgrade from working ubuntu 22.10 and do clean install of 23.04 and it will get to black screen with blinking cursor in upper left. Live iso boot seems to only work with software video driver. I have several lenovo ThinkPad W540 that have intel and nvidia graphics which have the same problem so its not machine specific. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017807] Re: black screen blinking cursor upper left after updating or clean install 23.04
I have attached xorg.log and syslog files. I am unable to send files directly from the os since I only have commandline and apport-collect needs gui so let me know what else is needed. It appears that nvida driver is the default driver and with 22.10 it was using version 390. ** Attachment added: "xorg and syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017807/+attachment/5668984/+files/Archive.zip ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017807 Title: black screen blinking cursor upper left after updating or clean install 23.04 Status in linux package in Ubuntu: Confirmed Bug description: I have attempted to upgrade from working ubuntu 22.10 and do clean install of 23.04 and it will get to black screen with blinking cursor in upper left. Live iso boot seems to only work with software video driver. I have several lenovo ThinkPad W540 that have intel and nvidia graphics which have the same problem so its not machine specific. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017807] [NEW] black screen blinking cursor upper left after updating or clean install 23.04
Public bug reported: I have attempted to upgrade from working ubuntu 22.10 and do clean install of 23.04 and it will get to black screen with blinking cursor in upper left. Live iso boot seems to only work with software video driver. I have several lenovo ThinkPad W540 that have intel and nvidia graphics which have the same problem so its not machine specific. ** 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/2017807 Title: black screen blinking cursor upper left after updating or clean install 23.04 Status in linux package in Ubuntu: New Bug description: I have attempted to upgrade from working ubuntu 22.10 and do clean install of 23.04 and it will get to black screen with blinking cursor in upper left. Live iso boot seems to only work with software video driver. I have several lenovo ThinkPad W540 that have intel and nvidia graphics which have the same problem so its not machine specific. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017442] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess
*** This bug is a duplicate of bug 2017340 *** https://bugs.launchpad.net/bugs/2017340 Public bug reported: this started as a 22.04 VM in parallels running on an M1 Max MacBook Pro. virgin VM, just installed vanilla ubuntu 22.04, went into the upgrade settings and selected 'any upgrade'. the upgrade tool then said I could upgrade to 22.10, which I did. waited for that to complete entirely and reboot, which all went smooth. the upgrade tool then said I could upgrade to 23.04, which I attempted. it seems to have gone well except for, unfortunately, a pretty critical piece, the kernel headers :o ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parallels 2300 F wireplumber /dev/snd/seq:parallels 2297 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Sun Apr 23 11:58:26 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-07 (289 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release arm64 (20220421) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=5a14ccf7-6bac-47b7-a3d6-6c10822fb10d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-23 (0 days ago) acpidump: dmi.bios.date: Fri, 10 Feb 2023 10:16:42 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 18.2.0 (53488) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr18.2.0(53488):bdFri,10Feb2023101642:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 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/2017442 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: this started as a 22.04 VM in parallels running on an M1 Max MacBook Pro. virgin VM, just installed vanilla ubuntu 22.04, went into the upgrade settings and selected 'any upgrade'. the upgrade tool then said I could upgrade to 22.10, which I did. waited for that to complete entirely and reboot, which all went smooth. the upgrade tool then said I could upgrade to 23.04, which I attempted. it seems to have gone well except for, unfortunately, a pretty critical piece, the kernel headers :o ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parallels 2300 F wireplumber /dev/snd/seq:parallels 2297 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Sun Apr 23 11:58:26 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-07 (289 days ago) InstallationMedia:
[Kernel-packages] [Bug 2008992] Re: suspend fails on Dell XPS 9350
Changing the BIOS Fastboot option to "Thorough" seems to have got it working again. Not sure why this would be necessary now. ** Changed in: linux-signed-oem-5.17 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2008992 Title: suspend fails on Dell XPS 9350 Status in linux-signed-oem-5.17 package in Ubuntu: Invalid Bug description: After upgrading to 5.17.0-1027-oem, my laptop fails to suspend. Instead it turns off. Journald output: Mar 02 17:31:47 nugget systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.3571] manager: sleep: sleep requested (sleeping: no enabled: yes) Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.3575] device (p2p-dev-wlp58s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 02 17:31:53 nugget ModemManager[1061]: [sleep-monitor] system is about to suspend Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.3593] manager: NetworkManager state is now ASLEEP Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.3602] device (wlp58s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') Mar 02 17:31:53 nugget dbus-daemon[939]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=940 comm="/usr/sbin/NetworkManager --> Mar 02 17:31:53 nugget systemd[1]: Starting Network Manager Script Dispatcher Service... Mar 02 17:31:53 nugget dbus-daemon[939]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Mar 02 17:31:53 nugget systemd[1]: Started Network Manager Script Dispatcher Service. Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DISCONNECTED bssid=6c:70:9f:ea:29:9f reason=3 locally_generated=1 Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.4826] device (wlp58s0): supplicant interface state: completed -> disconnected Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.4834] device (wlp58s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') Mar 02 17:31:53 nugget avahi-daemon[932]: Withdrawing address record for fe80::7389:c602:b63c:8452 on wlp58s0. Mar 02 17:31:53 nugget avahi-daemon[932]: Leaving mDNS multicast group on interface wlp58s0.IPv6 with address fe80::7389:c602:b63c:8452. Mar 02 17:31:53 nugget avahi-daemon[932]: Interface wlp58s0.IPv6 no longer relevant for mDNS. Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.5110] dhcp4 (wlp58s0): canceled DHCP transaction Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.5111] dhcp4 (wlp58s0): activation: beginning transaction (timeout in 45 seconds) Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.5112] dhcp4 (wlp58s0): state changed no lease Mar 02 17:31:53 nugget avahi-daemon[932]: Withdrawing address record for 192.168.1.217 on wlp58s0. Mar 02 17:31:53 nugget avahi-daemon[932]: Leaving mDNS multicast group on interface wlp58s0.IPv4 with address 192.168.1.217. Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client reset search domain list. Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client set default route setting: no Mar 02 17:31:53 nugget avahi-daemon[932]: Interface wlp58s0.IPv4 no longer relevant for mDNS. Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client reset DNS server list. Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.5824] device (wlp58s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 02 17:31:54 nugget wpa_supplicant[981]: p2p-dev-wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:54 nugget wpa_supplicant[981]: p2p-dev-wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:54 nugget wpa_supplicant[981]: nl80211: deinit ifname=p2p-dev-wlp58s0 disabled_11b_rates=0 Mar 02 17:31:54 nugget systemd[1]: Reached target Sleep. Mar 02 17:31:54 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:54 nugget systemd[1]: Starting Record successful boot for GRUB... Mar 02 17:31:54 nugget systemd[1]: Starting System Suspend... Mar 02 17:31:54 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:54 nugget wpa_supplicant[981]: nl80211: deinit ifname=wlp58s0 disabled_11b_rates=0 Mar 02 17:31:54 nugget systemd[1]: grub-common.service: Deactivated successfully. Mar 02 17:31:54 nugget systemd[1]: Finished Record
[Kernel-packages] [Bug 2008992] Re: suspend fails on Dell XPS 9350
Upgrading to linux-image- unsigned-6.2.1-060201-generic_6.2.1-060201.202302251141 did not fix the issue. Nor did rolling back to 5.17.0-1021-oem. And along the way I found a log file which showed suspend working one time with 5.17.0-1027-oem. So now I'm not sure what changed to stop this working. :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2008992 Title: suspend fails on Dell XPS 9350 Status in linux-signed-oem-5.17 package in Ubuntu: New Bug description: After upgrading to 5.17.0-1027-oem, my laptop fails to suspend. Instead it turns off. Journald output: Mar 02 17:31:47 nugget systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.3571] manager: sleep: sleep requested (sleeping: no enabled: yes) Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.3575] device (p2p-dev-wlp58s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 02 17:31:53 nugget ModemManager[1061]: [sleep-monitor] system is about to suspend Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.3593] manager: NetworkManager state is now ASLEEP Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.3602] device (wlp58s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') Mar 02 17:31:53 nugget dbus-daemon[939]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=940 comm="/usr/sbin/NetworkManager --> Mar 02 17:31:53 nugget systemd[1]: Starting Network Manager Script Dispatcher Service... Mar 02 17:31:53 nugget dbus-daemon[939]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Mar 02 17:31:53 nugget systemd[1]: Started Network Manager Script Dispatcher Service. Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DISCONNECTED bssid=6c:70:9f:ea:29:9f reason=3 locally_generated=1 Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.4826] device (wlp58s0): supplicant interface state: completed -> disconnected Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.4834] device (wlp58s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') Mar 02 17:31:53 nugget avahi-daemon[932]: Withdrawing address record for fe80::7389:c602:b63c:8452 on wlp58s0. Mar 02 17:31:53 nugget avahi-daemon[932]: Leaving mDNS multicast group on interface wlp58s0.IPv6 with address fe80::7389:c602:b63c:8452. Mar 02 17:31:53 nugget avahi-daemon[932]: Interface wlp58s0.IPv6 no longer relevant for mDNS. Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.5110] dhcp4 (wlp58s0): canceled DHCP transaction Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.5111] dhcp4 (wlp58s0): activation: beginning transaction (timeout in 45 seconds) Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.5112] dhcp4 (wlp58s0): state changed no lease Mar 02 17:31:53 nugget avahi-daemon[932]: Withdrawing address record for 192.168.1.217 on wlp58s0. Mar 02 17:31:53 nugget avahi-daemon[932]: Leaving mDNS multicast group on interface wlp58s0.IPv4 with address 192.168.1.217. Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client reset search domain list. Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client set default route setting: no Mar 02 17:31:53 nugget avahi-daemon[932]: Interface wlp58s0.IPv4 no longer relevant for mDNS. Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client reset DNS server list. Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.5824] device (wlp58s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 02 17:31:54 nugget wpa_supplicant[981]: p2p-dev-wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:54 nugget wpa_supplicant[981]: p2p-dev-wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:54 nugget wpa_supplicant[981]: nl80211: deinit ifname=p2p-dev-wlp58s0 disabled_11b_rates=0 Mar 02 17:31:54 nugget systemd[1]: Reached target Sleep. Mar 02 17:31:54 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:54 nugget systemd[1]: Starting Record successful boot for GRUB... Mar 02 17:31:54 nugget systemd[1]: Starting System Suspend... Mar 02 17:31:54 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:54 nugget wpa_supplicant[981]: nl80211: deinit ifname=wlp58s0 disabled_11b_rates=0 Mar 02 17:31:54 nugget systemd[1]:
[Kernel-packages] [Bug 2008992] [NEW] suspend fails on Dell XPS 9350
Public bug reported: After upgrading to 5.17.0-1027-oem, my laptop fails to suspend. Instead it turns off. Journald output: Mar 02 17:31:47 nugget systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.3571] manager: sleep: sleep requested (sleeping: no enabled: yes) Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.3575] device (p2p-dev-wlp58s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 02 17:31:53 nugget ModemManager[1061]: [sleep-monitor] system is about to suspend Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.3593] manager: NetworkManager state is now ASLEEP Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.3602] device (wlp58s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') Mar 02 17:31:53 nugget dbus-daemon[939]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=940 comm="/usr/sbin/NetworkManager --> Mar 02 17:31:53 nugget systemd[1]: Starting Network Manager Script Dispatcher Service... Mar 02 17:31:53 nugget dbus-daemon[939]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Mar 02 17:31:53 nugget systemd[1]: Started Network Manager Script Dispatcher Service. Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DISCONNECTED bssid=6c:70:9f:ea:29:9f reason=3 locally_generated=1 Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.4826] device (wlp58s0): supplicant interface state: completed -> disconnected Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.4834] device (wlp58s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') Mar 02 17:31:53 nugget avahi-daemon[932]: Withdrawing address record for fe80::7389:c602:b63c:8452 on wlp58s0. Mar 02 17:31:53 nugget avahi-daemon[932]: Leaving mDNS multicast group on interface wlp58s0.IPv6 with address fe80::7389:c602:b63c:8452. Mar 02 17:31:53 nugget avahi-daemon[932]: Interface wlp58s0.IPv6 no longer relevant for mDNS. Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.5110] dhcp4 (wlp58s0): canceled DHCP transaction Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.5111] dhcp4 (wlp58s0): activation: beginning transaction (timeout in 45 seconds) Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.5112] dhcp4 (wlp58s0): state changed no lease Mar 02 17:31:53 nugget avahi-daemon[932]: Withdrawing address record for 192.168.1.217 on wlp58s0. Mar 02 17:31:53 nugget avahi-daemon[932]: Leaving mDNS multicast group on interface wlp58s0.IPv4 with address 192.168.1.217. Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client reset search domain list. Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client set default route setting: no Mar 02 17:31:53 nugget avahi-daemon[932]: Interface wlp58s0.IPv4 no longer relevant for mDNS. Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client reset DNS server list. Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.5824] device (wlp58s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 02 17:31:54 nugget wpa_supplicant[981]: p2p-dev-wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:54 nugget wpa_supplicant[981]: p2p-dev-wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:54 nugget wpa_supplicant[981]: nl80211: deinit ifname=p2p-dev-wlp58s0 disabled_11b_rates=0 Mar 02 17:31:54 nugget systemd[1]: Reached target Sleep. Mar 02 17:31:54 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:54 nugget systemd[1]: Starting Record successful boot for GRUB... Mar 02 17:31:54 nugget systemd[1]: Starting System Suspend... Mar 02 17:31:54 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 02 17:31:54 nugget wpa_supplicant[981]: nl80211: deinit ifname=wlp58s0 disabled_11b_rates=0 Mar 02 17:31:54 nugget systemd[1]: grub-common.service: Deactivated successfully. Mar 02 17:31:54 nugget systemd[1]: Finished Record successful boot for GRUB. Mar 02 17:31:54 nugget systemd[1]: Starting GRUB failed boot detection... Mar 02 17:31:54 nugget systemd[1]: grub-initrd-fallback.service: Deactivated successfully. Mar 02 17:31:54 nugget systemd[1]: Finished GRUB failed boot detection. Mar 02 17:31:54 nugget systemd-sleep[3429]: Entering sleep state 'suspend'... Mar 02 17:31:54 nugget kernel: PM: suspend entry (deep) Suspend was working find when I was running 5.17.0-1021-oem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.17.0-1027-oem 5.17.0-1027.28
[Kernel-packages] [Bug 1999189] Re: Displayport monitors hang on blanking and must REISUB my 20.04.5 system
If I leave my system at the login screen, the monitors will go to sleep and then I cannot wake the monitors with mouse or keyboard. Can someone please look at this report? -- 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: Confirmed 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. Otherwise, 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 dmesg. 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. 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] Re: Displayport monitors hang on blanking and must REISUB my 20.04.5 system
I have tested the issue on the live 20.04.5 ISO usb, and the issue occurs in the Live config. If I choose the Safe Graphics config - the issue does NOT happen. My view of what is happening in the Safe Graphics mode that is notably different is that my "main monitor" never fully powers off when Blanking kicks in. This means there is always a display for the OS/driver to refer to. On my normal/default mode, the main monitor actually turns off (both monitors turn off) and I am immediately unable to wake them. I suspect there is some major issue when the count of displays present/connected becomes zero. That's my best guess. -- 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: Confirmed 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. Otherwise, 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 dmesg. 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. 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] Re: Displayport monitors hang on blanking and must REISUB my 20.04.5 system
The issue does not occur using the live version of ubuntu-22.04.1-desktop-amd64 ISO via usb. -- 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: Confirmed 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. Otherwise, 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 dmesg. 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. 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] 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. + blanking, the issue never occurs. Otherwise, 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 dmesg. 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. 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. -- 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: Confirmed 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. Otherwise, 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 dmesg. 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. 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:
[Kernel-packages] [Bug 1835509] Re: False warning "The kernel version is not supported." on xenial with -hwe kernels
I just targeted this to Focal as the focal version of makedumpfile will not work with the focal hwe kernel. Focal makedumpfile.h says: #define LATEST_VERSION KERNEL_VERSION(5, 4, 8) /* linux-5.4.8 */ linux-image-generic-hwe-20.04 currently points to linux-meta-hwe-5.15. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1835509 Title: False warning "The kernel version is not supported." on xenial with -hwe kernels Status in makedumpfile package in Ubuntu: New Status in makedumpfile source package in Xenial: New Status in makedumpfile source package in Focal: New Bug description: [Impact] The message appears as when running -hwe kernels (4.15) on Xenial. This happens because makedumpfile defines a LATEST_VERSION kernel that "officially" supports. Currently, makedumpfile package for xenial has this version set to 4.14.8 and this is why it shows this message with 4.15 kernels. [Test Case] TBD [Regression Potential] TBD [Other] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1835509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835509] Re: False warning "The kernel version is not supported." on xenial with -hwe kernels
** Also affects: makedumpfile (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1835509 Title: False warning "The kernel version is not supported." on xenial with -hwe kernels Status in makedumpfile package in Ubuntu: New Status in makedumpfile source package in Xenial: New Status in makedumpfile source package in Focal: New Bug description: [Impact] The message appears as when running -hwe kernels (4.15) on Xenial. This happens because makedumpfile defines a LATEST_VERSION kernel that "officially" supports. Currently, makedumpfile package for xenial has this version set to 4.14.8 and this is why it shows this message with 4.15 kernels. [Test Case] TBD [Regression Potential] TBD [Other] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1835509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Here is an example error/crash from journalctl: Dec 14 17:51:18 hostname kernel: [ cut here ] Dec 14 17:51:18 hostname kernel: WARNING: CPU: 3 PID: 2408 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:2807 decide_link_settings+0x11a/0x200 [amdgpu] Dec 14 17:51:18 hostname kernel: Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hd> Dec 14 17:51:18 hostname kernel: lp parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore ip_tables x_tables autofs4 dm_crypt hid_generic usbhid rtsx_usb_sdmmc rtsx_usb amdgpu iommu_v2 gpu_> Dec 14 17:51:18 hostname kernel: CPU: 3 PID: 2408 Comm: Xorg Not tainted 5.15.0-56-generic #62~20.04.1-Ubuntu Dec 14 17:51:18 hostname kernel: Hardware name: ASUSTeK COMPUTER INC. MINIPC PN51-E1/PN51-E1, BIOS 0503 06/21/2021 Dec 14 17:51:18 hostname kernel: RIP: 0010:decide_link_settings+0x11a/0x200 [amdgpu] Dec 14 17:51:18 hostname kernel: Code: 76 4c b9 f6 0a 00 00 48 c7 c2 a0 72 ca c0 bf 02 00 00 00 48 c7 c6 72 a0 d3 c0 e8 01 ba 87 ff 8b 43 64 85 c0 0f 85 67 ff ff ff <0f> 0b e9 60 ff ff ff ba 02 00 00> Dec 14 17:51:18 hostname kernel: RSP: 0018:b226836ab5a0 EFLAGS: 00010246 Dec 14 17:51:18 hostname kernel: RAX: RBX: 95d05a482800 RCX: 0af6 Dec 14 17:51:18 hostname kernel: RDX: c0ca72a0 RSI: c0d3a072 RDI: 0002 Dec 14 17:51:18 hostname kernel: RBP: b226836ab5d8 R08: 95d051a1d000 R09: b226836ab5b8 Dec 14 17:51:18 hostname kernel: R10: 0080 R11: R12: 95d051a1d000 Dec 14 17:51:18 hostname kernel: R13: b226836ab5f0 R14: 00093828 R15: 95d13df206a0 Dec 14 17:51:18 hostname kernel: FS: 7f57c4414a40() GS:95d556ec() knlGS: Dec 14 17:51:18 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Dec 14 17:51:18 hostname kernel: CR2: 55f5c0d69070 CR3: 000118f2c000 CR4: 00350ee0 Dec 14 17:51:18 hostname kernel: Call Trace: Dec 14 17:51:18 hostname kernel: Dec 14 17:51:18 hostname kernel: enable_link_dp+0xa0/0x250 [amdgpu] Dec 14 17:51:18 hostname kernel: enable_link+0x295/0x3c0 [amdgpu] Dec 14 17:51:18 hostname kernel: core_link_enable_stream+0x32a/0x5a0 [amdgpu] Dec 14 17:51:18 hostname kernel: dce110_apply_ctx_to_hw+0x749/0x7d0 [amdgpu] Dec 14 17:51:18 hostname kernel: dc_commit_state_no_check+0x2fb/0xf50 [amdgpu] Dec 14 17:51:18 hostname kernel: dc_commit_state+0xd4/0x150 [amdgpu] Dec 14 17:51:18 hostname kernel: amdgpu_dm_atomic_commit_tail+0x56e/0x1940 [amdgpu] Dec 14 17:51:18 hostname kernel: ? dml_rq_dlg_get_rq_params+0x3b0/0x3b0 [amdgpu] Dec 14 17:51:18 hostname kernel: ? dcn21_validate_bandwidth_fp+0x147/0x360 [amdgpu] Dec 14 17:51:18 hostname kernel: ? dcn21_validate_bandwidth_fp+0x147/0x360 [amdgpu] Dec 14 17:51:18 hostname kernel: ? save_fpregs_to_fpstate+0x3f/0xa0 Dec 14 17:51:18 hostname kernel: ? dc_fpu_end+0x7e/0x90 [amdgpu] Dec 14 17:51:18 hostname kernel: ? ttm_bo_mem_compat+0x30/0x90 [ttm] Dec 14 17:51:18 hostname kernel: ? ttm_bo_validate+0x50/0x110 [ttm] Dec 14 17:51:18 hostname kernel: ? dm_plane_helper_prepare_fb+0x1d9/0x290 [amdgpu] Dec 14 17:51:18 hostname kernel: ? __cond_resched+0x19/0x40 Dec 14 17:51:18 hostname kernel: ? __wait_for_common+0x3d/0x160 Dec 14 17:51:18 hostname kernel: ? wait_for_completion_timeout+0x1d/0x30 Dec 14 17:51:18 hostname kernel: commit_tail+0xc5/0x180 [drm_kms_helper] Dec 14 17:51:18 hostname kernel: ? drm_atomic_helper_swap_state+0x20f/0x370 [drm_kms_helper] Dec 14 17:51:18 hostname kernel: drm_atomic_helper_commit+0x12b/0x150 [drm_kms_helper] Dec 14 17:51:18 hostname kernel: drm_atomic_commit+0x4a/0x60 [drm] Dec 14 17:51:18 hostname kernel: drm_atomic_helper_set_config+0x80/0xc0 [drm_kms_helper] Dec 14 17:51:18 hostname kernel: drm_mode_setcrtc+0x1ff/0x7d0 [drm] Dec 14 17:51:18 hostname kernel: ? drm_mode_getcrtc+0x1e0/0x1e0 [drm] Dec 14 17:51:18 hostname kernel: drm_ioctl_kernel+0xb2/0x100 [drm] Dec 14 17:51:18 hostname kernel: drm_ioctl+0x275/0x4a0 [drm] Dec 14 17:51:18 hostname kernel: ? drm_mode_getcrtc+0x1e0/0x1e0 [drm] Dec 14 17:51:18 hostname kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] Dec 14 17:51:18 hostname kernel: __x64_sys_ioctl+0x95/0xd0 Dec 14 17:51:18 hostname kernel: do_syscall_64+0x5c/0xc0 Dec 14 17:51:18 hostname kernel: ? syscall_exit_to_user_mode+0x27/0x50 Dec 14 17:51:18 hostname kernel: ? do_syscall_64+0x69/0xc0 Dec 14 17:51:18 hostname kernel: ? __x64_sys_close+0x12/0x50 Dec 14 17:51:18 hostname kernel: ? do_syscall_64+0x69/0xc0 Dec 14 17:51:18 hostname kernel: ? do_syscall_64+0x69/0xc0 Dec 14 17:51:18 hostname kernel: ? do_syscall_64+0x69/0xc0 Dec 14 17:51:18 hostname kernel: entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 14 17:51:18 hostname kernel: RIP: 0033:0x7f57c47713ab Dec 14 17:51:18 hostname kernel: Code:
[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. + possibly dmesg. 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. ** 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 dmesg. 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
[Kernel-packages] [Bug 1999189] Re: Displayport monitors hang on blanking and must REISUB my 20.04.5 system
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999189 Title: Displayport monitors hang on blanking and must REISUB my 20.04.5 system Status in linux package in Ubuntu: Confirmed 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 dmesg. 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. 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] 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. + possibly dmseg. 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 + Â 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 + Â 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 + Â 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. -- 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
[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 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] 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 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] 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] 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] 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] 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] 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.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] 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] 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] 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] 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 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 1996740] Re: 5.15.0-53-generic no longer boots
I want to raise the possibility that this fix (or another one) in the new kernel update has begun preventing me from Blanking my DP monitors. I had previously been experiencing xorg cpu spikes and softlocks when my monitors Blanked, but now, they refuse to Blank at all. They disconnect for a brief moment and they reactivate. I can see my mouse cursor reappear on screen. I have an AMD Ryzen 5700u (includes renoir graphics). Using amdgpu (default). So this new kernel is better than the last kernel with xorg softlocks that prevented me from accessing my system but might have introduced/revealed another less severe bug. I tried to hunt down what amdgpu impacting changes were made to the latest ubuntu kernel and I think this is the only one? -- 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 1993968] [NEW] package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu9 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess retur
Public bug reported: fresh install on hp 550-153w ProblemType: Package DistroRelease: Ubuntu 22.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu9 Uname: Linux 6.1.0-060100rc1-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 AptOrdering: dctrl-tools:amd64: Install dh-dkms:amd64: Install dkms:amd64: Install bcmwl-kernel-source:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Oct 23 19:02:56 2022 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-10-23 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu9 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1993968 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu9 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: fresh install on hp 550-153w ProblemType: Package DistroRelease: Ubuntu 22.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu9 Uname: Linux 6.1.0-060100rc1-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 AptOrdering: dctrl-tools:amd64: Install dh-dkms:amd64: Install dkms:amd64: Install bcmwl-kernel-source:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Oct 23 19:02:56 2022 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-10-23 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu9 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1993968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982776] [NEW] linux-modules for -kvm does not include dm-crypt
Public bug reported: I was playing with an lxc virtual machine today and attempted some use of luks. a cryptseutp open fails with strange error message: $ printf %s foobar | cryptsetup open --type=luks --key-file=- /dev/atom0/smtest_enc smtest device-mapper: reload ioctl on failed: Invalid argument $ echo $? 1 The reason is that the '-kvm' variant does not include dm-crypt.ko kernel module. That by itself doens't seem like all that crazy of a thing, but if you notice the following 4 all do have dm-crypt, -kvm seems like it should not be an outlier. linux-modules-5.15.0-1013-aws: /lib/modules/5.15.0-1013-aws/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-azure: /lib/modules/5.15.0-1013-azure/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-gcp: /lib/modules/5.15.0-1013-gcp/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-oracle: /lib/modules/5.15.0-1013-oracle/kernel/drivers/md/dm-crypt.ko ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-5.15.0-1010-kvm 5.15.0-1010.11 ProcVersionSignature: Ubuntu 5.15.0-1010.11-kvm 5.15.35 Uname: Linux 5.15.0-1010-kvm x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Jul 25 16:01:09 2022 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images ** Also affects: linux-kvm (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1982776 Title: linux-modules for -kvm does not include dm-crypt Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Focal: New Status in linux-kvm source package in Jammy: New Bug description: I was playing with an lxc virtual machine today and attempted some use of luks. a cryptseutp open fails with strange error message: $ printf %s foobar | cryptsetup open --type=luks --key-file=- /dev/atom0/smtest_enc smtest device-mapper: reload ioctl on failed: Invalid argument $ echo $? 1 The reason is that the '-kvm' variant does not include dm-crypt.ko kernel module. That by itself doens't seem like all that crazy of a thing, but if you notice the following 4 all do have dm-crypt, -kvm seems like it should not be an outlier. linux-modules-5.15.0-1013-aws: /lib/modules/5.15.0-1013-aws/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-azure: /lib/modules/5.15.0-1013-azure/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-gcp: /lib/modules/5.15.0-1013-gcp/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-oracle: /lib/modules/5.15.0-1013-oracle/kernel/drivers/md/dm-crypt.ko ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-5.15.0-1010-kvm 5.15.0-1010.11 ProcVersionSignature: Ubuntu 5.15.0-1010.11-kvm 5.15.35 Uname: Linux 5.15.0-1010-kvm x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Jul 25 16:01:09 2022 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1982776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
I see this on every boot up but all it seems to do is slow down the boot process. -- 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Confirmed Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse:  USERPID ACCESS COMMAND  /dev/snd/controlC0: eugene16798 F pulseaudio  /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio  /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig:  lono wireless extensions.  enp2s0no wireless extensions.  virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron:  LANGUAGE=  PATH=(custom, no user)  XDG_RUNTIME_DIR=  LANG=uk_UA.UTF-8  SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 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: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Kernel-packages] [Bug 1967078] VarLogDistupgradeMainlog.txt
apport information ** Attachment added: "VarLogDistupgradeMainlog.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574702/+files/VarLogDistupgradeMainlog.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/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process Status in linux package in Ubuntu: Confirmed Bug description: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) dmi.bios.date: 04/25/2008 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB7WW (2.17 ) dmi.board.name: 6465CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T61 dmi.product.name: 6465CTO dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Package: ubuntu-release-upgrader-core 1:22.04.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Tags: jammy dist-upgrade Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967078] VarLogDistupgradeAptlog.txt
apport information ** Attachment added: "VarLogDistupgradeAptlog.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574699/+files/VarLogDistupgradeAptlog.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/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process Status in linux package in Ubuntu: Confirmed Bug description: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) dmi.bios.date: 04/25/2008 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB7WW (2.17 ) dmi.board.name: 6465CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T61 dmi.product.name: 6465CTO dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Package: ubuntu-release-upgrader-core 1:22.04.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Tags: jammy dist-upgrade Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967078] VarLogDistupgradeApttermlog.txt
apport information ** Attachment added: "VarLogDistupgradeApttermlog.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574700/+files/VarLogDistupgradeApttermlog.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/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process Status in linux package in Ubuntu: Confirmed Bug description: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) dmi.bios.date: 04/25/2008 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB7WW (2.17 ) dmi.board.name: 6465CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T61 dmi.product.name: 6465CTO dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Package: ubuntu-release-upgrader-core 1:22.04.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Tags: jammy dist-upgrade Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967078] VarLogDistupgradeLspcitxt.txt
apport information ** Attachment added: "VarLogDistupgradeLspcitxt.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574701/+files/VarLogDistupgradeLspcitxt.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/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process Status in linux package in Ubuntu: Confirmed Bug description: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) dmi.bios.date: 04/25/2008 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB7WW (2.17 ) dmi.board.name: 6465CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T61 dmi.product.name: 6465CTO dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Package: ubuntu-release-upgrader-core 1:22.04.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Tags: jammy dist-upgrade Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967078] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574696/+files/ProcEnviron.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/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process Status in linux package in Ubuntu: Confirmed Bug description: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) dmi.bios.date: 04/25/2008 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB7WW (2.17 ) dmi.board.name: 6465CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T61 dmi.product.name: 6465CTO dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Package: ubuntu-release-upgrader-core 1:22.04.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Tags: jammy dist-upgrade Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967078] VarLogDistupgradeAptHistorylog.txt
apport information ** Attachment added: "VarLogDistupgradeAptHistorylog.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574697/+files/VarLogDistupgradeAptHistorylog.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/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process Status in linux package in Ubuntu: Confirmed Bug description: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) dmi.bios.date: 04/25/2008 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB7WW (2.17 ) dmi.board.name: 6465CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T61 dmi.product.name: 6465CTO dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Package: ubuntu-release-upgrader-core 1:22.04.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Tags: jammy dist-upgrade Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967078] VarLogDistupgradeAptclonesystemstate.tar.gz
apport information ** Attachment added: "VarLogDistupgradeAptclonesystemstate.tar.gz" https://bugs.launchpad.net/bugs/1967078/+attachment/5574698/+files/VarLogDistupgradeAptclonesystemstate.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process Status in linux package in Ubuntu: Confirmed Bug description: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) dmi.bios.date: 04/25/2008 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB7WW (2.17 ) dmi.board.name: 6465CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T61 dmi.product.name: 6465CTO dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Package: ubuntu-release-upgrader-core 1:22.04.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Tags: jammy dist-upgrade Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967078] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574694/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process Status in linux package in Ubuntu: Confirmed Bug description: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) dmi.bios.date: 04/25/2008 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB7WW (2.17 ) dmi.board.name: 6465CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T61 dmi.product.name: 6465CTO dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Package: ubuntu-release-upgrader-core 1:22.04.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Tags: jammy dist-upgrade Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967078] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574695/+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/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process Status in linux package in Ubuntu: Confirmed Bug description: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) dmi.bios.date: 04/25/2008 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB7WW (2.17 ) dmi.board.name: 6465CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T61 dmi.product.name: 6465CTO dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Package: ubuntu-release-upgrader-core 1:22.04.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Tags: jammy dist-upgrade Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967078] Re: Firefox snap install fails due to disabled networking in upgrade process
apport information ** Tags added: apport-collected dist-upgrade ** Description changed: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) dmi.bios.date: 04/25/2008 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB7WW (2.17 ) dmi.board.name: 6465CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T61 dmi.product.name: 6465CTO dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu79 + Architecture: amd64 + CasperMD5CheckResult: unknown + CrashDB: ubuntu + CurrentDesktop: KDE + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-03-30 (0 days ago) + InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) + Package: ubuntu-release-upgrader-core 1:22.04.7 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 + Tags: jammy dist-upgrade + Uname: Linux 5.15.0-23-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + VarLogDistupgradeXorgFixuplog: + INFO:root:/usr/bin/do-release-upgrade running + INFO:root:No xorg.conf, exiting + _MarkForUpload: True ** Attachment added: "CurrentDmesg.txt.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574693/+files/CurrentDmesg.txt.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/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process Status in linux package in Ubuntu: Confirmed Bug description: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts:
[Kernel-packages] [Bug 1967078] [NEW] Firefox snap install fails due to disabled networking in upgrade process
Public bug reported: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) dmi.bios.date: 04/25/2008 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB7WW (2.17 ) dmi.board.name: 6465CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T61 dmi.product.name: 6465CTO dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process Status in linux package in Ubuntu: New Bug description: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). Upg
[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
This is still a bug in Ubuntu 21.04 and 21.10. -- 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/1848534 Title: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: AFter upgrade system shows graphic artefacts for a moment and then text cursor for about minute (it looks like hanged) and then starts. In 19.04 startup required 1 or 2 seconds. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 17:42:27 2019 InstallationDate: Installed on 2019-07-04 (104 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeLspcitxt: VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InstallationDate: Installed on 2019-07-04 (105 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: xorg-server (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash video=hyperv_fb:1900x900 elevator=noop vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 RfKill: Tags: eoan ubuntu Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939157] Re: HWE kernels: NFSv4.1 NULL pointer dereference
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939157 Title: HWE kernels: NFSv4.1 NULL pointer dereference Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-hwe-5.11 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-hwe-5.11 source package in Hirsute: Invalid Bug description: Ubuntu 20.04 systems running as NFSv4.1 clients are experiencing crashes (in this case with a NetApp filer mounted): [ 266.199481] BUG: kernel NULL pointer dereference, address: [ 266.199495] #PF: supervisor read access in kernel mode [ 266.199500] #PF: error_code(0x) - not-present page [ 266.199503] PGD 0 P4D 0 [ 266.199511] Oops: [#1] SMP PTI [ 266.199518] CPU: 15 PID: 2244 Comm: tracker-extract Not tainted 5.11.0-25-generic #27~20.04.1-Ubuntu [ 266.199525] Hardware name: Intel Corporation S2600GZ/S2600GZ, BIOS SE5C600.86B.02.06.0006.032420170950 03/24/2017 [ 266.199529] RIP: 0010:pnfs_mark_matching_lsegs_return+0xfe/0x140 [nfsv4] [ 266.199631] Code: f0 41 80 4d 50 08 49 8b 06 4d 89 f5 4c 39 75 d0 75 9b 8b 45 bc 85 c0 75 3b 48 8b 45 c8 48 8b 50 38 48 83 c0 38 48 39 c2 74 23 <41> 8b 34 24 48 8b 7d c8 44 89 fa e8 42 e0 ff ff 31 c0 48 83 c4 20 [ 266.199637] RSP: 0018:ae23a19a7c88 EFLAGS: 00010297 [ 266.199642] RAX: a048621ef238 RBX: a048621ef238 RCX: [ 266.199646] RDX: a04847636780 RSI: a04847636780 RDI: a048621ef200 [ 266.199650] RBP: ae23a19a7cd0 R08: 0001 R09: a086febdcc10 [ 266.199653] R10: a0677ffd6b80 R11: 0003 R12: [ 266.199657] R13: a048621ef228 R14: a048621ef228 R15: [ 266.199661] FS: 7f9de3440340() GS:a086febc() knlGS: [ 266.199665] CS: 0010 DS: ES: CR0: 80050033 [ 266.199669] CR2: CR3: 00012ed86006 CR4: 001706e0 [ 266.199674] Call Trace: [ 266.199682] _pnfs_return_layout+0x13d/0x2c0 [nfsv4] [ 266.199755] ? nfs_put_delegation+0x4c/0x70 [nfsv4] [ 266.199814] nfs4_evict_inode+0x78/0x80 [nfsv4] [ 266.199870] evict+0xd2/0x180 [ 266.199879] iput+0x18f/0x200 [ 266.199884] nfs_dentry_iput+0x33/0x60 [nfs] [ 266.199934] dentry_unlink_inode+0xb8/0x110 [ 266.199946] __dentry_kill+0xdf/0x180 [ 266.199953] dput+0x171/0x320 [ 266.199960] do_renameat2+0x387/0x500 [ 266.199968] __x64_sys_rename+0x45/0x50 [ 266.199974] do_syscall_64+0x38/0x90 [ 266.199987] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 266.16] RIP: 0033:0x7f9de644200b [ 266.23] Code: e8 aa ce 0a 00 85 c0 0f 95 c0 0f b6 c0 f7 d8 5d c3 66 0f 1f 44 00 00 b8 ff ff ff ff 5d c3 90 f3 0f 1e fa b8 52 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 51 4e 18 00 f7 d8 [ 266.28] RSP: 002b:7ffe70e5f008 EFLAGS: 0246 ORIG_RAX: 0052 [ 266.200014] RAX: ffda RBX: 55a5ed503070 RCX: 7f9de644200b [ 266.200018] RDX: 55a5ed37b940 RSI: 55a5ed1db250 RDI: 55a5ed4aea00 [ 266.200022] RBP: 55a5ed503060 R08: R09: [ 266.200025] R10: 000d R11: 0246 R12: 0001 [ 266.200029] R13: 55a5ed503078 R14: 55a5ed503040 R15: 55a5ed37b980 [ 266.200036] Modules linked in: nfs_layout_nfsv41_files rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace nfs_ssc fscache intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_ pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper mgag200 rapl joydev input_leds intel_cstate drm_kms_helper ipmi_si ipmi_devintf cec rc_core fb_sys_fops syscopyarea sysfillrect mei_me ipmi_msghandler s ysimgblt mei ioatdma mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment nf_log_ipv4 nf_log_common xt_addrtype xt_limit xt_LOG xt_recent xt_tcpudp sch_fq_codel xt_state xt_conn This bug occurs in all recent 20.04 HWE kernels (both 5.8 and 5.11). I believe it is fixed by https://patchwork.kernel.org/project/linux- nfs/patch/20210519165451.412566-1-anna.schuma...@netapp.com/ -- please consider backporting this patch. (The bug was briefly also present in the 5.4 kernels, but was fixed in 5.4.0-79: see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936673) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1939157] [NEW] HWE kernels: NFSv4.1 NULL pointer dereference
Public bug reported: Ubuntu 20.04 systems running as NFSv4.1 clients are experiencing crashes (in this case with a NetApp filer mounted): [ 266.199481] BUG: kernel NULL pointer dereference, address: [ 266.199495] #PF: supervisor read access in kernel mode [ 266.199500] #PF: error_code(0x) - not-present page [ 266.199503] PGD 0 P4D 0 [ 266.199511] Oops: [#1] SMP PTI [ 266.199518] CPU: 15 PID: 2244 Comm: tracker-extract Not tainted 5.11.0-25-generic #27~20.04.1-Ubuntu [ 266.199525] Hardware name: Intel Corporation S2600GZ/S2600GZ, BIOS SE5C600.86B.02.06.0006.032420170950 03/24/2017 [ 266.199529] RIP: 0010:pnfs_mark_matching_lsegs_return+0xfe/0x140 [nfsv4] [ 266.199631] Code: f0 41 80 4d 50 08 49 8b 06 4d 89 f5 4c 39 75 d0 75 9b 8b 45 bc 85 c0 75 3b 48 8b 45 c8 48 8b 50 38 48 83 c0 38 48 39 c2 74 23 <41> 8b 34 24 48 8b 7d c8 44 89 fa e8 42 e0 ff ff 31 c0 48 83 c4 20 [ 266.199637] RSP: 0018:ae23a19a7c88 EFLAGS: 00010297 [ 266.199642] RAX: a048621ef238 RBX: a048621ef238 RCX: [ 266.199646] RDX: a04847636780 RSI: a04847636780 RDI: a048621ef200 [ 266.199650] RBP: ae23a19a7cd0 R08: 0001 R09: a086febdcc10 [ 266.199653] R10: a0677ffd6b80 R11: 0003 R12: [ 266.199657] R13: a048621ef228 R14: a048621ef228 R15: [ 266.199661] FS: 7f9de3440340() GS:a086febc() knlGS: [ 266.199665] CS: 0010 DS: ES: CR0: 80050033 [ 266.199669] CR2: CR3: 00012ed86006 CR4: 001706e0 [ 266.199674] Call Trace: [ 266.199682] _pnfs_return_layout+0x13d/0x2c0 [nfsv4] [ 266.199755] ? nfs_put_delegation+0x4c/0x70 [nfsv4] [ 266.199814] nfs4_evict_inode+0x78/0x80 [nfsv4] [ 266.199870] evict+0xd2/0x180 [ 266.199879] iput+0x18f/0x200 [ 266.199884] nfs_dentry_iput+0x33/0x60 [nfs] [ 266.199934] dentry_unlink_inode+0xb8/0x110 [ 266.199946] __dentry_kill+0xdf/0x180 [ 266.199953] dput+0x171/0x320 [ 266.199960] do_renameat2+0x387/0x500 [ 266.199968] __x64_sys_rename+0x45/0x50 [ 266.199974] do_syscall_64+0x38/0x90 [ 266.199987] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 266.16] RIP: 0033:0x7f9de644200b [ 266.23] Code: e8 aa ce 0a 00 85 c0 0f 95 c0 0f b6 c0 f7 d8 5d c3 66 0f 1f 44 00 00 b8 ff ff ff ff 5d c3 90 f3 0f 1e fa b8 52 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 51 4e 18 00 f7 d8 [ 266.28] RSP: 002b:7ffe70e5f008 EFLAGS: 0246 ORIG_RAX: 0052 [ 266.200014] RAX: ffda RBX: 55a5ed503070 RCX: 7f9de644200b [ 266.200018] RDX: 55a5ed37b940 RSI: 55a5ed1db250 RDI: 55a5ed4aea00 [ 266.200022] RBP: 55a5ed503060 R08: R09: [ 266.200025] R10: 000d R11: 0246 R12: 0001 [ 266.200029] R13: 55a5ed503078 R14: 55a5ed503040 R15: 55a5ed37b980 [ 266.200036] Modules linked in: nfs_layout_nfsv41_files rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace nfs_ssc fscache intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_ pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper mgag200 rapl joydev input_leds intel_cstate drm_kms_helper ipmi_si ipmi_devintf cec rc_core fb_sys_fops syscopyarea sysfillrect mei_me ipmi_msghandler s ysimgblt mei ioatdma mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment nf_log_ipv4 nf_log_common xt_addrtype xt_limit xt_LOG xt_recent xt_tcpudp sch_fq_codel xt_state xt_conn This bug occurs in all recent 20.04 HWE kernels (both 5.8 and 5.11). I believe it is fixed by https://patchwork.kernel.org/project/linux- nfs/patch/20210519165451.412566-1-anna.schuma...@netapp.com/ -- please consider backporting this patch. (The bug was briefly also present in the 5.4 kernels, but was fixed in 5.4.0-79: see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936673) ** 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/1939157 Title: HWE kernels: NFSv4.1 NULL pointer dereference Status in linux package in Ubuntu: New Bug description: Ubuntu 20.04 systems running as NFSv4.1 clients are experiencing crashes (in this case with a NetApp filer mounted): [ 266.199481] BUG: kernel NULL pointer dereference, address: [ 266.199495] #PF: supervisor read access in kernel mode [ 266.199500] #PF: error_code(0x) - not-present page [ 266.199503] PGD 0 P4D 0 [ 266.199511] Oops: [#1] SMP PTI [ 266.199518] CPU: 15 PID: 2244 Comm: tracker-extract Not tainted 5.11.0-25-generic #27~20.04.1-Ubuntu [ 266.199525] Hardware name: Intel Corporation S2600GZ/S2600GZ, BIOS
[Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
It happened to me too ** Attachment added: "Crash log of amdgpu driver" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+attachment/5516220/+files/amdgu_crash.txt -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924785] [NEW] package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17
Public bug reported: Just loading the latest updates ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-53-generic 3.13.0-53.89 ProcVersionSignature: Ubuntu 3.13.0-53.88-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scottselk 1778 F pulseaudio Date: Fri Apr 16 10:22:23 2021 DpkgHistoryLog: DpkgTerminalLog: ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=c74bf797-318c-4292-a8de-4f37e2ee450a InstallationDate: Installed on 2015-03-25 (2213 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Dell Inc. Inspiron 1440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=bbab8bb0-ec2d-41ce-a32c-d604411dd3ef 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: grub-pc 2.02~beta2-9ubuntu1.17 SourcePackage: linux Title: package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0K138P dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd12/21/2009:svnDellInc.:pnInspiron1440:pvr:rvnDellInc.:rn0K138P:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1440 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- 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/1924785 Title: package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: New Bug description: Just loading the latest updates ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-53-generic 3.13.0-53.89 ProcVersionSignature: Ubuntu 3.13.0-53.88-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scottselk 1778 F pulseaudio Date: Fri Apr 16 10:22:23 2021 DpkgHistoryLog: DpkgTerminalLog: ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=c74bf797-318c-4292-a8de-4f37e2ee450a InstallationDate: Installed on 2015-03-25 (2213 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Dell Inc. Inspiron 1440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=bbab8bb0-ec2d-41ce-a32c-d604411dd3ef 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: grub-pc 2.02~beta2-9ubuntu1.17 SourcePackage: linux Title: package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0K138P dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd12/21/2009:svnDellInc.:pnInspiron1440:pvr:rvnDellInc.:rn0K138P:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1440 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912943] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456308/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456313/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456314/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456310/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456309/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456312/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456311/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456298/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456300/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456296/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0
[Kernel-packages] [Bug 1912943] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456295/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456304/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456307/+files/ProcEnviron.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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456299/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0
[Kernel-packages] [Bug 1912943] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456305/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456306/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456301/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0
[Kernel-packages] [Bug 1912943] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456302/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456303/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1912943/+attachment/5456297/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] Re: magicmouse driver causes soft panic intermittently at boot
apport information ** Tags added: apport-collected ** Description changed: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0
[Kernel-packages] [Bug 1912943] Re: magicmouse driver causes soft panic intermittently at boot
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912943/+attachment/5456293/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] Re: magicmouse driver causes soft panic intermittently at boot
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912943/+attachment/5456292/+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/1912943 Title: magicmouse driver causes soft panic intermittently at boot Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1912943] [NEW] magicmouse driver causes soft panic intermittently at boot
Public bug reported: Kubuntu 20.10 Kernel: 5.8.0-40-generic CPU: AMD Ryzen 7 3700X Motherboard: Asrock X570 Taichi Recently my system has been failing to boot often and I'm left with a blank screen before I even see my login screen. After a reset (or 2 or 3) I can usually persuade it to boot and look in my syslog. During the boot process I get what appear to be 3 soft panics (I believe that is the correct term) starting with this one below. Given it happens immediately after loading the magicmouse driver and given the call trace I believe it's magicmouse at fault here? I have an Apple Magic Trackpad 2 plugged in via USB most of the time. Though I also have it plugged in on a Ubuntu 20.04 machine quite often and see no issues at all with it over there. Excerpt from syslog: Jan 24 13:25:36 diplodocus systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 24 13:25:36 diplodocus haveged[1272]: haveged starting up Jan 24 13:25:36 diplodocus kernel: input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:01.2/:01:00.0/:02:08.0/:09:00.3/usb3/3-4/3-4.2/3-4.2:1.1/0003:05AC:0265.000E/input/input32 Jan 24 13:25:36 diplodocus kernel: magicmouse 0003:05AC:0265.000E: input,hiddev1,hidraw2: USB HID v1.10 Mouse [Apple Inc. Magic Trackpad 2] on usb-:09:00.3-4.2/input1 Jan 24 13:25:36 diplodocus kernel: general protection fault, probably for non-canonical address 0x745e0ac669a7401: [#1] SMP NOPTI Jan 24 13:25:36 diplodocus kernel: CPU: 5 PID: 262 Comm: kworker/5:2 Not tainted 5.8.0-40-generic #45-Ubuntu Jan 24 13:25:36 diplodocus kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Jan 24 13:25:36 diplodocus kernel: Workqueue: events deferred_probe_work_func Jan 24 13:25:36 diplodocus kernel: RIP: 0010:kmem_cache_alloc_trace+0x81/0x240 Jan 24 13:25:36 diplodocus kernel: Code: 99 01 00 00 4d 8b 01 65 49 8b 50 08 65 4c 03 05 ed 53 f3 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 41 20 49 8b 39 4c 01 e0 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jan 24 13:25:36 diplodocus kernel: RSP: 0018:be55c05e7890 EFLAGS: 00010202 Jan 24 13:25:36 diplodocus kernel: RAX: 0745e0ac669a7401 RBX: RCX: 0080 Jan 24 13:25:36 diplodocus kernel: RDX: 0a44 RSI: 0c00 RDI: 00031040 Jan 24 13:25:36 diplodocus kernel: RBP: be55c05e78c0 R08: 9c6e3eb71040 R09: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: R10: R11: 9c6e2d333ceb R12: 0745e0ac669a7401 Jan 24 13:25:36 diplodocus kernel: R13: 0c00 R14: 0008 R15: 9c6e3b407b80 Jan 24 13:25:36 diplodocus kernel: FS: () GS:9c6e3eb4() knlGS: Jan 24 13:25:36 diplodocus kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 13:25:36 diplodocus kernel: CR2: 557464ab55b8 CR3: 0007e5fbc000 CR4: 00340ee0 Jan 24 13:25:36 diplodocus kernel: Call Trace: Jan 24 13:25:36 diplodocus kernel: ? usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_control_msg+0x59/0x140 Jan 24 13:25:36 diplodocus kernel: usb_get_string+0x60/0xb0 Jan 24 13:25:36 diplodocus kernel: usb_string_sub+0x6f/0x100 Jan 24 13:25:36 diplodocus kernel: usb_string+0xda/0x1b0 Jan 24 13:25:36 diplodocus kernel: usbhid_probe+0x213/0x3d0 [usbhid] Jan 24 13:25:36 diplodocus kernel: usb_probe_interface+0xf1/0x2b0 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: device_add+0x3ad/0x6a0 Jan 24 13:25:36 diplodocus kernel: usb_set_configuration+0x490/0x860 Jan 24 13:25:36 diplodocus kernel: usb_generic_driver_probe+0x53/0x70 Jan 24 13:25:36 diplodocus kernel: usb_probe_device+0x3e/0x100 Jan 24 13:25:36 diplodocus kernel: really_probe+0x2f4/0x430 Jan 24 13:25:36 diplodocus kernel: driver_probe_device+0xe9/0x160 Jan 24 13:25:36 diplodocus kernel: __device_attach_driver+0x71/0xd0 Jan 24 13:25:36 diplodocus kernel: ? driver_allows_async_probing+0x50/0x50 Jan 24 13:25:36 diplodocus kernel: bus_for_each_drv+0x84/0xd0 Jan 24 13:25:36 diplodocus kernel: __device_attach+0xde/0x1e0 Jan 24 13:25:36 diplodocus kernel: device_initial_probe+0x13/0x20 Jan 24 13:25:36 diplodocus kernel: bus_probe_device+0x8f/0xa0 Jan 24 13:25:36 diplodocus kernel: deferred_probe_work_func+0x6f/0xc0 Jan 24 13:25:36 diplodocus kernel: process_one_work+0x1e8/0x3b0 Jan 24 13:25:36 diplodocus kernel:
[Kernel-packages] [Bug 1909856] Re: amdgpu intermittently fails to resume correctly
Sorry, I may not have made it obvious. The problem started on Focal but I have since upgraded to Groovy as I thought a newer kernel may help given various amdgpu fixes hit the kernel between 5.4 and 5.8. I do see a pending update for 5.8.0-34 though which I'll install. -- 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/1909856 Title: amdgpu intermittently fails to resume correctly Status in linux package in Ubuntu: Confirmed Bug description: I started seeing my system fail to resume from suspend over the last couple of weeks. It happens about 1 in 5 times maybe? I press the power button on my system to resume it and my screens stay blank. I am able to connect to the system remotely over ssh and check syslog to find out what went wrong. I then try to reboot the system with `sudo reboot`, the ssh session disconnects but it never actually reboots. I have to press the reset button after waiting a while to make it start up again. dmesg log is attached which contains more info and the call trace. I think the interesting part is this: kernel: amdgpu :0d:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110). kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -110 kernel: PM: Device :0d:00.0 failed to resume async: error -110 It first happened on 20.04 with kernel 5.4 (can't remember exactly what version of 5.4) a couple of weeks ago. I saw 20.10 was available with 5.8 so thought I'd try upgrading as there was a variety of amdgpu fixes go in between 5.4 and 5.8 but sadly no dice. From some research, I think what I'm seeing is similar to this bug, but that one looks like 5.4 solved it, whereas I guess some minor upgrade on 5.4 appeared to break it for me. https://bugs.freedesktop.org/show_bug.cgi?id=112221 I'm running a Ryzen 3700X on an X570 board with an AMD Radeon Pro WX 4100 GPU. Currently using Kubuntu 20.10. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-33-generic 5.8.0-33.36 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jan 2 12:40:36 2021 InstallationDate: Installed on 2020-06-18 (197 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/vgkubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-33-generic N/A linux-backports-modules-5.8.0-33-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-12-30 (3 days ago) dmi.bios.date: 09/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd09/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909856] Re: amdgpu intermittently fails to resume correctly
Ah, the included dmesg output doesn't actually have the useful snippet in it. Please see attached section of log output which runs from when I attempted to resume the system to when it was rebooted. ** Attachment added: "amd-gpu-resume-fail-syslog.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909856/+attachment/5448706/+files/amd-gpu-resume-fail-syslog.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/1909856 Title: amdgpu intermittently fails to resume correctly Status in linux package in Ubuntu: Confirmed Bug description: I started seeing my system fail to resume from suspend over the last couple of weeks. It happens about 1 in 5 times maybe? I press the power button on my system to resume it and my screens stay blank. I am able to connect to the system remotely over ssh and check syslog to find out what went wrong. I then try to reboot the system with `sudo reboot`, the ssh session disconnects but it never actually reboots. I have to press the reset button after waiting a while to make it start up again. dmesg log is attached which contains more info and the call trace. I think the interesting part is this: kernel: amdgpu :0d:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110). kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -110 kernel: PM: Device :0d:00.0 failed to resume async: error -110 It first happened on 20.04 with kernel 5.4 (can't remember exactly what version of 5.4) a couple of weeks ago. I saw 20.10 was available with 5.8 so thought I'd try upgrading as there was a variety of amdgpu fixes go in between 5.4 and 5.8 but sadly no dice. From some research, I think what I'm seeing is similar to this bug, but that one looks like 5.4 solved it, whereas I guess some minor upgrade on 5.4 appeared to break it for me. https://bugs.freedesktop.org/show_bug.cgi?id=112221 I'm running a Ryzen 3700X on an X570 board with an AMD Radeon Pro WX 4100 GPU. Currently using Kubuntu 20.10. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-33-generic 5.8.0-33.36 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jan 2 12:40:36 2021 InstallationDate: Installed on 2020-06-18 (197 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/vgkubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-33-generic N/A linux-backports-modules-5.8.0-33-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-12-30 (3 days ago) dmi.bios.date: 09/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd09/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909856] [NEW] amdgpu intermittently fails to resume correctly
Public bug reported: I started seeing my system fail to resume from suspend over the last couple of weeks. It happens about 1 in 5 times maybe? I press the power button on my system to resume it and my screens stay blank. I am able to connect to the system remotely over ssh and check syslog to find out what went wrong. I then try to reboot the system with `sudo reboot`, the ssh session disconnects but it never actually reboots. I have to press the reset button after waiting a while to make it start up again. dmesg log is attached which contains more info and the call trace. I think the interesting part is this: kernel: amdgpu :0d:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110). kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -110 kernel: PM: Device :0d:00.0 failed to resume async: error -110 It first happened on 20.04 with kernel 5.4 (can't remember exactly what version of 5.4) a couple of weeks ago. I saw 20.10 was available with 5.8 so thought I'd try upgrading as there was a variety of amdgpu fixes go in between 5.4 and 5.8 but sadly no dice. >From some research, I think what I'm seeing is similar to this bug, but that one looks like 5.4 solved it, whereas I guess some minor upgrade on 5.4 appeared to break it for me. https://bugs.freedesktop.org/show_bug.cgi?id=112221 I'm running a Ryzen 3700X on an X570 board with an AMD Radeon Pro WX 4100 GPU. Currently using Kubuntu 20.10. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-33-generic 5.8.0-33.36 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jan 2 12:40:36 2021 InstallationDate: Installed on 2020-06-18 (197 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/vgkubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-33-generic N/A linux-backports-modules-5.8.0-33-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-12-30 (3 days ago) dmi.bios.date: 09/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd09/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug groovy -- 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/1909856 Title: amdgpu intermittently fails to resume correctly Status in linux package in Ubuntu: Confirmed Bug description: I started seeing my system fail to resume from suspend over the last couple of weeks. It happens about 1 in 5 times maybe? I press the power button on my system to resume it and my screens stay blank. I am able to connect to the system remotely over ssh and check syslog to find out what went wrong. I then try to reboot the system with `sudo reboot`, the ssh session disconnects but it never actually reboots. I have to press the reset button after waiting a while to make it start up again. dmesg log is attached which contains more info and the call trace. I think the interesting part is this: kernel: amdgpu :0d:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110). kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -110 kernel: PM: Device :0d:00.0 failed to resume async: error -110 It first happened on 20.04 with kernel 5.4 (can't remember exactly what version of 5.4) a couple of weeks ago. I saw 20.10 was available with 5.8 so thought I'd try upgrading as there was a variety of
[Kernel-packages] [Bug 1906745] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
lspci | grep -i network 03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01) SOLUTION sudo apt-get purge bcmwl-kernel-source sudo apt-get install broadcom-sta-source broadcom-sta-dkms broadcom-sta-common reboot now wifi is OK -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1906745 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: apt-get upgrade caused crash of wireless bcmwl afterwards my wifi fails to work before updates had x86_64 5.4.0-57-generic DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" apt-get upgrade The following NEW packages will be installed: linux-headers-5.8.0-32-generic linux-hwe-5.8-headers-5.8.0-32 linux-image-5.8.0-32-generic linux-modules-5.8.0-32-generic linux-modules-extra-5.8.0-32-generic The following packages will be upgraded: linux-generic-hwe-20.04 linux-headers-generic-hwe-20.04 linux-image-generic-hwe-20.04 wireless-regdb Setting up linux-modules-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... Setting up linux-hwe-5.8-headers-5.8.0-32 (5.8.0-32.34~20.04.1) ... Setting up linux-headers-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 5.8.0-32-generic Kernel preparation unnecessary for this kernel. Skipping... applying patch 0002-Makefile.patch...patching file Makefile Hunk #1 succeeded at 113 with fuzz 1. Hunk #2 succeeded at 132 with fuzz 2 (offset 1 line). applying patch 0003-Make-up-for-missing-init_MUTEX.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 111 with fuzz 2 (offset 12 lines). applying patch 0010-change-the-network-interface-name-from-eth-to-wlan.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 221 (offset -14 lines). applying patch 0013-gcc.patch...patching file Makefile applying patch 0019-broadcom-sta-6.30.223.248-3.18-null-pointer-fix.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 2169 (offset 12 lines). applying patch 0020-add-support-for-linux-4.3.patch...patching file src/shared/linux_osl.c applying patch 0021-add-support-for-Linux-4.7.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c applying patch 0022-add-support-for-Linux-4.8.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c Hunk #1 succeeded at 2391 (offset 3 lines). Hunk #2 succeeded at 2501 (offset 3 lines). Hunk #3 succeeded at 2933 (offset 9 lines). applying patch 0023-add-support-for-Linux-4.11.patch...patching file src/include/linuxver.h patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 2919 (offset 4 lines). applying patch 0024-add-support-for-Linux-4.12.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c Hunk #1 succeeded at 55 (offset 5 lines). Hunk #2 succeeded at 472 (offset 5 lines). Hunk #3 succeeded at 2371 (offset 5 lines). Hunk #4 succeeded at 2388 (offset 5 lines). applying patch 0025-add-support-for-Linux-4.14.patch...patching file src/shared/linux_osl.c Hunk #1 succeeded at 1080 (offset 4 lines). applying patch 0026-add-support-for-Linux-4.15.patch...patching file src/wl/sys/wl_linux.c Hunk #2 succeeded at 2306 (offset 4 lines). Hunk #3 succeeded at 2368 (offset 4 lines). applying patch 0027-add-support-for-linux-5.1.patch...patching file src/include/linuxver.h Hunk #1 succeeded at 595 (offset 4 lines). Building module: cleaning build area... make -j8 KERNELRELEASE=5.8.0-32-generic -C /lib/modules/5.8.0-32-generic/build M=/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 5.8.0-32-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. ...done. Setting up linux-image-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-57-generic I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-57-generic I: /boot/vmlinuz is now a symlink to vmlinuz-5.8.0-32-generic I: /boot/initrd.img is now a symlink to initrd.img-5.8.0-32-generic Setting up linux-headers-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Setting up linux-modules-extra-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... Setting up linux-image-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Setting up linux-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for linux-image-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.8.0-32-generic Kernel
[Kernel-packages] [Bug 1906745] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
Public bug reported: apt-get upgrade caused crash of wireless bcmwl afterwards my wifi fails to work before updates had x86_64 5.4.0-57-generic DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" apt-get upgrade The following NEW packages will be installed: linux-headers-5.8.0-32-generic linux-hwe-5.8-headers-5.8.0-32 linux-image-5.8.0-32-generic linux-modules-5.8.0-32-generic linux-modules-extra-5.8.0-32-generic The following packages will be upgraded: linux-generic-hwe-20.04 linux-headers-generic-hwe-20.04 linux-image-generic-hwe-20.04 wireless-regdb Setting up linux-modules-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... Setting up linux-hwe-5.8-headers-5.8.0-32 (5.8.0-32.34~20.04.1) ... Setting up linux-headers-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 5.8.0-32-generic Kernel preparation unnecessary for this kernel. Skipping... applying patch 0002-Makefile.patch...patching file Makefile Hunk #1 succeeded at 113 with fuzz 1. Hunk #2 succeeded at 132 with fuzz 2 (offset 1 line). applying patch 0003-Make-up-for-missing-init_MUTEX.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 111 with fuzz 2 (offset 12 lines). applying patch 0010-change-the-network-interface-name-from-eth-to-wlan.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 221 (offset -14 lines). applying patch 0013-gcc.patch...patching file Makefile applying patch 0019-broadcom-sta-6.30.223.248-3.18-null-pointer-fix.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 2169 (offset 12 lines). applying patch 0020-add-support-for-linux-4.3.patch...patching file src/shared/linux_osl.c applying patch 0021-add-support-for-Linux-4.7.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c applying patch 0022-add-support-for-Linux-4.8.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c Hunk #1 succeeded at 2391 (offset 3 lines). Hunk #2 succeeded at 2501 (offset 3 lines). Hunk #3 succeeded at 2933 (offset 9 lines). applying patch 0023-add-support-for-Linux-4.11.patch...patching file src/include/linuxver.h patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 2919 (offset 4 lines). applying patch 0024-add-support-for-Linux-4.12.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c Hunk #1 succeeded at 55 (offset 5 lines). Hunk #2 succeeded at 472 (offset 5 lines). Hunk #3 succeeded at 2371 (offset 5 lines). Hunk #4 succeeded at 2388 (offset 5 lines). applying patch 0025-add-support-for-Linux-4.14.patch...patching file src/shared/linux_osl.c Hunk #1 succeeded at 1080 (offset 4 lines). applying patch 0026-add-support-for-Linux-4.15.patch...patching file src/wl/sys/wl_linux.c Hunk #2 succeeded at 2306 (offset 4 lines). Hunk #3 succeeded at 2368 (offset 4 lines). applying patch 0027-add-support-for-linux-5.1.patch...patching file src/include/linuxver.h Hunk #1 succeeded at 595 (offset 4 lines). Building module: cleaning build area... make -j8 KERNELRELEASE=5.8.0-32-generic -C /lib/modules/5.8.0-32-generic/build M=/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 5.8.0-32-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. ...done. Setting up linux-image-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-57-generic I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-57-generic I: /boot/vmlinuz is now a symlink to vmlinuz-5.8.0-32-generic I: /boot/initrd.img is now a symlink to initrd.img-5.8.0-32-generic Setting up linux-headers-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Setting up linux-modules-extra-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... Setting up linux-image-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Setting up linux-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for linux-image-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.8.0-32-generic Kernel preparation unnecessary for this kernel. Skipping... applying patch 0002-Makefile.patch...patching file Makefile Hunk #1 succeeded at 113 with fuzz 1. Hunk #2 succeeded at 132 with fuzz 2 (offset 1 line). applying patch 0003-Make-up-for-missing-init_MUTEX.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 111 with fuzz 2 (offset 12 lines). applying patch 0010-change-the-network-interface-name-from-eth-to-wlan.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 221 (offset -14 lines). applying patch 0013-gcc.patch...patching file Makefile applying patch 0019-broadcom-sta-6.30.223.248-3.18-null-pointer-fix.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 2169 (offset 12 lines). applying patch
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
lspci | grep -i network 02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter (rev 03) sudo lshw -C network *-network UNCLAIMED description: Network controller product: BCM4352 802.11ac Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:02:00.0 version: 03 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress cap_list configuration: latency=0 resources: memory:ed40-ed407fff memory:ed20-ed3f *-network description: Ethernet interface physical id: 1 bus info: usb@2:2 logical name: enx000edab6c1eb serial: 00:0e:da:b6:c1:eb size: 1Gbit/s capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=ax88179_178a driverversion=5.8.0-26-generic duplex=full ip=192.168.0.167 link=yes multicast=yes port=MII speed=1Gbit/s -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Fix Released Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
lspci | grep -i network 02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter (rev 03) sudo lshw -C network *-network UNCLAIMED description: Network controller product: BCM4352 802.11ac Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:02:00.0 version: 03 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress cap_list configuration: latency=0 resources: memory:ed40-ed407fff memory:ed20-ed3f *-network description: Ethernet interface physical id: 1 bus info: usb@2:2 logical name: enx000edab6c1eb serial: 00:0e:da:b6:c1:eb size: 1Gbit/s capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=ax88179_178a driverversion=5.8.0-26-generic duplex=full ip=192.168.0.167 link=yes multicast=yes port=MII speed=1Gbit/s -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Fix Released Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
