This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1974267
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1974267
Title:
XSET dpms force suspend causes kernel panic
Status in linux package in Ubuntu:
Incomplete
Bug description:
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.kernel.org/project/alsa-
devel/patch/20190716144111.1470-1-ti...@suse.de/ 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1974267/+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
