On 10/22/21 12:46, Chris Murphy wrote:
Following the hard reset, there should still be logs available if
you
have a persistent journal (the default). You can grab the entire
previous boot with:
journalctl -b -1 > journal.log
And attach that log file to a bug report.
It might also be useful to add drm.debug=0x06 as a kernel parameter, e.g.
grubby --args=drm.debug=0x06 --update-kernel=ALL
Reboot. Reproduce the problem. Hard reset (or possibly remote ssh will
still be functional). And then grab the log. To remove that boot
param:
grubby --remove-args=drm.debug=0x06 --update-kernel=ALL
Thanks, I thought the last boot journalctl might have something in it but wasn't sure.
I've taken these steps and sent in a bug report here:
https://bugzilla.redhat.com/show_bug.cgi?id=2016703
Leander
--
---
Leander Hutton
leander(a)one-button.org
www.one-button.org