Bug 276757 - graphics/drm-515-kmod: Black screen freeze (RX 6600, FreeBSD-14.0-RELEASE-p3)
Summary: graphics/drm-515-kmod: Black screen freeze (RX 6600, FreeBSD-14.0-RELEASE-p3)
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-x11 (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-01 01:10 UTC by illegalcoding
Modified: 2024-02-02 06:14 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (x11)


Attachments
/var/log/messages file (474.71 KB, text/plain)
2024-02-01 01:10 UTC, illegalcoding
no flags Details
Weird colored blocks on terminal (629.51 KB, image/jpeg)
2024-02-02 00:50 UTC, illegalcoding
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description illegalcoding 2024-02-01 01:10:10 UTC
Created attachment 248111 [details]
/var/log/messages file

Whenever X11 has been running for roughly 4,5 - 5 hours (although sometimes (rarely) this happens in just some tens of minutes) both my screens go black, and I have to hard reset my PC (i.e.: press the reset button on the front of the case) to get a working system again.

It's important to note that this doesn't panic or fully crash the system, audio still works, and it doesn't panic, but it's effectively useless, and the screens will not come back on no matter what.

I'm using an RX 6600 with 2 displays: 1 DP display @ 1920x1080 165hz, and 1 HDMI display @ 1920x1080 60hz. I'm also using the xf86-video-amdgpu driver with XDM as my display manager and DWM as my window manager. 

I believe this is an issue in drm-515-kmod as /var/log/messages includes some drm-related errors when this "crash" happens. Mainly stuff about "waiting for fences timed out" and "GPU reset failed". I initially had the same issues as in bug #274770, but the panics were fixed with compiling drm-kmod from the 5.15-lts-focal branch, and I now have these black screen freezes instead.

Apologies if this makes this a duplicate, but as that one isn't very active and not exactly about the same issue (no panics or anything), I thought i'd try opening a new bug specifically for the black screen freeze.

I doubt this is a hardware issue, as my GPU works flawlessly under OpenBSD 7.4 and Linux. Under Windows I get some weird artifacting and screen resets occasionally, but that sounds like a driver issue as it works on OpenBSD & Linux.

I've attached my /var/log/messages file which contains the drm-related errors.
I've also done a hw-probe, it's at https://bsd-hardware.info/?probe=b41ed8f957
Comment 1 illegalcoding 2024-02-01 02:28:04 UTC
I'm not sure why, all I did was run freebsd-update to update to FreeBSD-14.0-RELEASE-p3 (I intially wrote most of this bug report then realized I forgot to try that, but the /var/log/messages is from after I updated), but now the crashes are much more frequent, I can get about an hour of use before it crashes.
Comment 2 illegalcoding 2024-02-02 00:50:05 UTC
Created attachment 248125 [details]
Weird colored blocks on terminal

Another strange thing just happened, I had just restarted my PC after another one of these freezes, and after running my startup script, which includes starting picom and setting a monitor to 165hz (one of these is probably the culprit), the text on my terminal (alacritty) got replaced by these weird colored blocks, and I had to restart again.
Comment 3 illegalcoding 2024-02-02 06:14:59 UTC
I removed picom from my startup script, and my system has been up without a problem for 5 hours and 40 minutes now, so it seems that the issue is either caused by, or at least related to picom?