Comment 4 for bug 2022981

Unfortunately, it looks like removing drm.debug=0xe makes reproduction of this bug impossible for me so far. So it sounds like we're dealing with some sort of timing issue.

the journal.log file doesn't want to attach to a comment here, so I just uploaded it to Google Drive (from a boot with drm.debug=0xe):
https://drive.google.com/file/d/1zQdwnHwaeaMnlSTMeSv2H_ObjGtQObep/view?usp=drive_link