On Sat, 19 Feb 2022 11:52:59 -0500 (EST) [email protected] wrote: > >Synopsis: X Hangs, seemingly randomly, on amd64 -current for > >about a month now. Category: amd64 > >Environment: > System : OpenBSD 7.0 > Details : OpenBSD 7.0-current (GENERIC.MP) #365: Thu Feb > 17 23:02:26 MST 2022 > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > Architecture: OpenBSD.amd64 > Machine : amd64 > >Description: > Starting around Jan 22 2022 X started hanging randomly on my > Thinkpad T450 with integrated intel graphics. I have emptied my > user's .xsession file of everything except starting a window manager > (cwm). Sometimes X hangs while firefox is doing something (loading a > new tab or page), sometimes while thunderbird is active, sometimes > while showing the cwm menu by using a key-combo or clicking on the > root screen. Sometimes X hangs while I am trying to log in on the > xenodm screen. The only customization I have on xenodm is to show the > wallpapers from the openbsd-wallpaper pkg.
I've had the exact same issue on my Thinkpad X1 Carbon gen 6. X will hang very consistently after opening a new tab in firefox. I've been able to work around the issue by using Chrome, but will occaisionally experience a random hang. I started experiencing the issues around late January. If I restore my laptop to a backup from Jan 15, I no longer have any issues. > Once the screen freezes, I have to turn my machine off by > holding the power button down for several seconds. I will try to > include my Xorg log from the last time this happened, though I am > unsure how to do that, so if you do not see it here, please ask along > with any other info you may need. Regarding the old Xorg log, I think there should be a /var/log/Xorg.0.log.old file that contains the log from the previous X session. I've taken a look at mine after a hang + reboot, but I haven't seen anything conspicuous. The next time I get a crash I will attach it to this thread, along with my dmesg output. I suspect there is a change in the inteldrm firmware from mid-Jan that's causing the issue. If anyone has any information on how to go about debugging the inteldrm firmware, I'd love to be able to help out in anyway.
