| Bug ID | 108753 |
|---|---|
| Summary | [RX570]GOG Dosbox game causes lockup |
| Product | DRI |
| Version | unspecified |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | baraclese@gmail.com |
Created attachment 142473 =
[details]
kernel trace
I have a two monitor setup connected to a RX 570, one via display port, one=
via
DVI.
I installed the GOG game 'Star Wars - Dark Forces' which runs in dosbox. Wh=
en
dosbox starts it switches to fullscreen and displays on the monitor attached
via DVI. At that point the computer locks up. This bug is always reproducib=
le.
The kernel trace shows errors such as:
[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR*
[CONNECTOR:64:DVI-D-1] flip_done timed out
| What | Removed | Added |
|---|---|---|
| CC | harry.wentland@amd.com, nicholas.kazlauskas@amd.com |
Please attach the corresponding Xorg log file, preferably capt= ured after the problem occurred.
Created attachment 142475 [det=
ails]
Xorg.0.log
What distro and desktop environment are you using? Does this problem occur when using xf86-video-amdgpu instead of the modeset= ting driver?
| What | Removed | Added |
|---|---|---|
| Attachment #142475 mime type | text/x-log | text/plain |
Arch Linux/Budgie Desktop. I tried a few other dosbox games an= d they work correctly. The game also works correctly when starting dosbox in windowed m= ode. Then I tried to start the game with only one monitor attached and I could reproduce the problem with the BENQ G2420HDBL monitor attached via DVI. The error also occurred when starting in windowed mode and then switching to fullscreen manually. Also the error does not occur with kernel version 4.14= .80. I will be able to test without modesetting driver tomorrow.
I can confirm that the problem does not occur when I load xf86= -video-amdgpu driver.
I'm glad to hear that, but it would still be good to rule out = a kernel bug. Can you bisect the kernel change which triggered the problem with the modesetti= ng driver?
Well, I'm having trouble compiling a bootable kernel v4.15, so=
I can't pinpoint
it excactly. The last kernel that shows the error that I was able to compile
was 4.16 and the last good kernel without the error is the 4.14 series.
| What | Removed | Added |
|---|---|---|
| Resolution | --- | MOVED |
| Status | NEW | RESOLVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/609.