| 2022-12-08 22:40:31 |
Scott P |
bug |
|
|
added bug |
| 2022-12-08 22:41:04 |
Scott P |
attachment added |
|
lspci-vnvn.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+attachment/5635171/+files/lspci-vnvn.log |
|
| 2022-12-08 22:41:31 |
Scott P |
attachment added |
|
version.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999189/+attachment/5635172/+files/version.log |
|
| 2022-12-08 22:56:41 |
Scott P |
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) |
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) |
|
| 2022-12-08 23:00:06 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2022-12-08 23:10:26 |
Scott P |
tags |
|
apport-collected focal |
|
| 2022-12-08 23:10:27 |
Scott P |
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) |
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:
USER PID 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=<set>
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. |
|
| 2022-12-08 23:10:28 |
Scott P |
attachment added |
|
AlsaInfo.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635173/+files/AlsaInfo.txt |
|
| 2022-12-08 23:10:29 |
Scott P |
attachment added |
|
CRDA.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635174/+files/CRDA.txt |
|
| 2022-12-08 23:10:31 |
Scott P |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635175/+files/CurrentDmesg.txt |
|
| 2022-12-08 23:10:32 |
Scott P |
attachment added |
|
IwConfig.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635176/+files/IwConfig.txt |
|
| 2022-12-08 23:10:33 |
Scott P |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635177/+files/Lspci.txt |
|
| 2022-12-08 23:10:34 |
Scott P |
attachment added |
|
Lspci-vt.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635178/+files/Lspci-vt.txt |
|
| 2022-12-08 23:10:35 |
Scott P |
attachment added |
|
Lsusb.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635179/+files/Lsusb.txt |
|
| 2022-12-08 23:10:36 |
Scott P |
attachment added |
|
Lsusb-t.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635180/+files/Lsusb-t.txt |
|
| 2022-12-08 23:10:38 |
Scott P |
attachment added |
|
Lsusb-v.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635181/+files/Lsusb-v.txt |
|
| 2022-12-08 23:10:39 |
Scott P |
attachment added |
|
ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635182/+files/ProcCpuinfo.txt |
|
| 2022-12-08 23:10:40 |
Scott P |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635183/+files/ProcCpuinfoMinimal.txt |
|
| 2022-12-08 23:10:41 |
Scott P |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635184/+files/ProcInterrupts.txt |
|
| 2022-12-08 23:10:43 |
Scott P |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635185/+files/ProcModules.txt |
|
| 2022-12-08 23:10:44 |
Scott P |
attachment added |
|
PulseList.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635186/+files/PulseList.txt |
|
| 2022-12-08 23:10:45 |
Scott P |
attachment added |
|
RfKill.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635187/+files/RfKill.txt |
|
| 2022-12-08 23:10:47 |
Scott P |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635188/+files/UdevDb.txt |
|
| 2022-12-08 23:10:49 |
Scott P |
attachment added |
|
acpidump.txt https://bugs.launchpad.net/bugs/1999189/+attachment/5635189/+files/acpidump.txt |
|
| 2022-12-09 14:21:30 |
Scott P |
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:
USER PID 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=<set>
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. |
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.
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:
USER PID 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=<set>
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. |
|
| 2022-12-09 15:24:16 |
Scott P |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2022-12-09 15:29:55 |
Scott P |
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.
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:
USER PID 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=<set>
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. |
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 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:
USER PID 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=<set>
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. |
|
| 2022-12-09 15:30:14 |
Scott P |
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.
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:
USER PID 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=<set>
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. |
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:
USER PID 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=<set>
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. |
|
| 2022-12-22 23:20:15 |
Scott P |
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:
USER PID 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=<set>
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. |
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:
USER PID 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=<set>
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. |
|
