Device Specs are a HP Prodesk 600 G4 DM. 1 stick DDR4 2666mhz 16gb and I7-8600T CPU.
I am running an application that uses a touch screen that turns off the monitor when not used. It uses the DPMS time out commands on the monitor. I have manually triggered the crash using ssh into the computer. Turning off the monitor manually does not cause it. I have ran the monitor from usbc combined as well as power and hdmi only to verify that it is not an issue with the touch screen drivers.
Using tail -f on /var/log/Xorg.0.log, Xorg.1.log and on syslogd. I can see xserver issue the command and then starts spamming the mode line information from the monitor when the monitor disconnects. Within a second the syslog reports "snd_hda_codec_hdmi hdaudioC0D2: HDMI: pin nid 7 not registered" and then within 5 seconds the computer reboots. I have tried collecting a kdump, but when enabled, the computer is permanently frozen and the power button has to be held down to reboot the machine. When testing the Kdump with the ssh trigger crash, the crash log is generated properly.
This bug may be similar to https://patchwork<email address hidden>/ I cannot confirm however on the behavior. It could be that the xserver package is trying to use the something when the monitor is in suspend or off. No crash occurs when the monitor is disconnected or when the monitor shutsdown. Only when the monitor enters a DPMS state does the kernel panic.
I am attaching 4 ssh terminals from when I induced a crash.
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-30-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-05-19 (4 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 10000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 14: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 14: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: HP HP ProDesk 600 G4 DM (TAA)
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=c63b5c31-85f5-4103-a295-77a17bde4d47 ro
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
RelatedPackageVersions:
linux-restricted-modules-5.15.0-30-generic N/A
linux-backports-modules-5.15.0-30-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: jammy uec-images
Uname: Linux 5.15.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lxd plugdev sudo tty video
_MarkForUpload: True
dmi.bios.date: 03/28/2022
dmi.bios.release: 19.0
dmi.bios.vendor: HP
dmi.bios.version: Q22 Ver. 02.19.00
dmi.board.name: 83EF
dmi.board.vendor: HP
dmi.board.version: KBC Version 07.D1.00
dmi.chassis.type: 6
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 7.209
dmi.modalias: dmi:bvnHP:bvrQ22Ver.02.19.00:bd03/28/2022:br19.0:efr7.209:svnHP:pnHPProDesk600G4DM(TAA):pvr:rvnHP:rn83EF:rvrKBCVersion07.D1.00:cvnHP:ct6:cvr:sku4FZ41UT#ABA:
dmi.product.family: 103C_53307F HP ProDesk
dmi.product.name: HP ProDesk 600 G4 DM (TAA)
dmi.product.sku: 4FZ41UT#ABA
dmi.sys.vendor: HP
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/
To change the source package that this bug is filed about visit https:/
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]