* [Bug 110510] Radeon VII HDMI issues: Flicking/system crashing
2019-04-24 22:54 [Bug 110510] Radeon VII HDMI issues: Flicking/system crashing bugzilla-daemon
@ 2019-04-24 23:07 ` bugzilla-daemon
2019-04-24 23:21 ` bugzilla-daemon
` (4 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: bugzilla-daemon @ 2019-04-24 23:07 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 886 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110510
--- Comment #1 from Tom B <tom@r.je> ---
This may be relevant: The crash does not happen if I run the HDMI monitor at
30hz. This means the monitors can be run at different refresh rates.
The DisplayPort monitor does not support 59.94hz or 50hz. My conclusion is that
the crash occurs if the HDMI monitor is set to a refresh rate that the
DisplayPort monitor does not support.
And that explains why the HDMI monitor works on its own. With only the HDMI
monitor connected, all the connected displays support 59.94 so everything is
fine.
I did try adding 3840x2160 59.94 to the displayport monitor via xrandr to see
if I could run both displays at 59.94, unfortunately it does not seem to
support it and I just get a black screen.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1649 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 7+ messages in thread* [Bug 110510] Radeon VII HDMI issues: Flicking/system crashing
2019-04-24 22:54 [Bug 110510] Radeon VII HDMI issues: Flicking/system crashing bugzilla-daemon
2019-04-24 23:07 ` bugzilla-daemon
@ 2019-04-24 23:21 ` bugzilla-daemon
2019-04-25 0:42 ` bugzilla-daemon
` (3 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: bugzilla-daemon @ 2019-04-24 23:21 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 5334 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110510
--- Comment #2 from Tom B <tom@r.je> ---
After freezing the system, here's the output from journalctl --boot=-1 | grep
amdgpu
Apr 25 00:10:18 desktop kernel: [drm] amdgpu kernel modesetting enabled.
Apr 25 00:10:18 desktop kernel: fb0: switching to amdgpudrmfb from EFI VGA
Apr 25 00:10:18 desktop kernel: amdgpu 0000:44:00.0: No more image in the PCI
ROM
Apr 25 00:10:18 desktop kernel: amdgpu 0000:44:00.0: VRAM: 16368M
0x0000008000000000 - 0x00000083FEFFFFFF (16368M used)
Apr 25 00:10:18 desktop kernel: amdgpu 0000:44:00.0: GART: 512M
0x0000000000000000 - 0x000000001FFFFFFF
Apr 25 00:10:18 desktop kernel: amdgpu 0000:44:00.0: AGP: 267894784M
0x0000008400000000 - 0x0000FFFFFFFFFFFF
Apr 25 00:10:18 desktop kernel: [drm] amdgpu: 16368M of VRAM memory ready
Apr 25 00:10:18 desktop kernel: [drm] amdgpu: 16368M of GTT memory ready.
Apr 25 00:10:18 desktop kernel: amdgpu 0000:44:00.0: Direct firmware load for
amdgpu/vega20_ta.bin failed with error -2
Apr 25 00:10:18 desktop kernel: amdgpu 0000:44:00.0: psp v11.0: Failed to load
firmware "amdgpu/vega20_ta.bin"
Apr 25 00:10:19 desktop kernel: fbcon: amdgpudrmfb (fb0) is primary device
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: fb0: amdgpudrmfb frame
buffer device
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring gfx uses VM inv eng 0
on hub 0
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring comp_1.0.0 uses VM
inv eng 1 on hub 0
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring comp_1.1.0 uses VM
inv eng 4 on hub 0
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring comp_1.2.0 uses VM
inv eng 5 on hub 0
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring comp_1.3.0 uses VM
inv eng 6 on hub 0
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring comp_1.0.1 uses VM
inv eng 7 on hub 0
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring comp_1.1.1 uses VM
inv eng 8 on hub 0
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring comp_1.2.1 uses VM
inv eng 9 on hub 0
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring comp_1.3.1 uses VM
inv eng 10 on hub 0
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring kiq_2.1.0 uses VM inv
eng 11 on hub 0
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring sdma0 uses VM inv eng
0 on hub 1
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring page0 uses VM inv eng
1 on hub 1
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring sdma1 uses VM inv eng
4 on hub 1
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring page1 uses VM inv eng
5 on hub 1
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring uvd_0 uses VM inv eng
6 on hub 1
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring uvd_enc_0.0 uses VM
inv eng 7 on hub 1
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring uvd_enc_0.1 uses VM
inv eng 8 on hub 1
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring uvd_1 uses VM inv eng
9 on hub 1
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring uvd_enc_1.0 uses VM
inv eng 10 on hub 1
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring uvd_enc_1.1 uses VM
inv eng 11 on hub 1
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring vce0 uses VM inv eng
12 on hub 1
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring vce1 uses VM inv eng
13 on hub 1
Apr 25 00:10:19 desktop kernel: amdgpu 0000:44:00.0: ring vce2 uses VM inv eng
14 on hub 1
Apr 25 00:10:19 desktop kernel: [drm] Initialized amdgpu 3.27.0 20150101 for
0000:44:00.0 on minor 0
Apr 25 00:11:10 desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
sdma0 timeout, signaled seq=590, emitted seq=591
Apr 25 00:11:10 desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
page0 timeout, signaled seq=2654, emitted seq=2656
Apr 25 00:11:10 desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
sdma1 timeout, signaled seq=23, emitted seq=25
Apr 25 00:11:10 desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
page1 timeout, signaled seq=1051, emitted seq=1053
Apr 25 00:11:10 desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
Process information: process pid 0 thread pid 0
Apr 25 00:11:10 desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
Process information: process plasmashell pid 1388 thread plasmashel:cs0 pid
1666
Apr 25 00:11:10 desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
Process information: process pid 0 thread pid 0
Apr 25 00:11:10 desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
Process information: process kwin_x11 pid 1379 thread kwin_x11:cs0 pid 1615
Apr 25 00:11:10 desktop kernel: amdgpu 0000:44:00.0: GPU reset begin!
Apr 25 00:11:10 desktop kernel: amdgpu 0000:44:00.0: GPU reset begin!
Apr 25 00:11:10 desktop kernel: amdgpu 0000:44:00.0: GPU reset begin!
Apr 25 00:11:10 desktop kernel: amdgpu 0000:44:00.0: GPU reset begin!
Apr 25 00:11:21 desktop kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR*
[CRTC:47:crtc-0] hw_done or flip_done timed out
Apr 25 00:11:31 desktop kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR*
[CRTC:49:crtc-1] hw_done or flip_done timed out
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 6107 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 7+ messages in thread* [Bug 110510] Radeon VII HDMI issues: Flicking/system crashing
2019-04-24 22:54 [Bug 110510] Radeon VII HDMI issues: Flicking/system crashing bugzilla-daemon
2019-04-24 23:07 ` bugzilla-daemon
2019-04-24 23:21 ` bugzilla-daemon
@ 2019-04-25 0:42 ` bugzilla-daemon
2019-04-25 13:42 ` bugzilla-daemon
` (2 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: bugzilla-daemon @ 2019-04-25 0:42 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 1233 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110510
--- Comment #3 from Tom B <tom@r.je> ---
Further testing after reading this:
https://bugs.freedesktop.org/show_bug.cgi?id=102646
If I run:
echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level
Before setting the refresh rate to 59.94hz it works perfectly! The system does
not freeze at all (at least not for the 5 minutes since I tried it.)
The second I ran
echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_level
X froze.
A rather annoying chain of bugs:
1. I have to set the refresh rate to 59.94hz to stop the screen flickering
(Don't really care about this, I'd happily do this if it was the only issue)
2. It works perfectly with a single display
3. With multiple displays, setting the refresh rate to 59.94 causes the system
to freeze and I have to to a hard reset
4. Points 2 and 3 are only relevant if power_dpm_force_performance_level is
set to auto.
This is an acceptable compromise for now. The additional temperature/power
usage is far more palatable than the flickering screen or system freezes.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2179 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 7+ messages in thread* [Bug 110510] Radeon VII HDMI issues: Flicking/system crashing
2019-04-24 22:54 [Bug 110510] Radeon VII HDMI issues: Flicking/system crashing bugzilla-daemon
` (2 preceding siblings ...)
2019-04-25 0:42 ` bugzilla-daemon
@ 2019-04-25 13:42 ` bugzilla-daemon
2019-05-01 19:28 ` bugzilla-daemon
2019-11-19 9:19 ` bugzilla-daemon
5 siblings, 0 replies; 7+ messages in thread
From: bugzilla-daemon @ 2019-04-25 13:42 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 416 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110510
--- Comment #4 from Tom B <tom@r.je> ---
Unfortunately this workaround does not work.
As soon as I launch a game on either monitor the whole system freezes despite
the performance setting.
Nothing appeared in journalctl this time but it seems like the same kind of
freeze.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1179 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 7+ messages in thread* [Bug 110510] Radeon VII HDMI issues: Flicking/system crashing
2019-04-24 22:54 [Bug 110510] Radeon VII HDMI issues: Flicking/system crashing bugzilla-daemon
` (3 preceding siblings ...)
2019-04-25 13:42 ` bugzilla-daemon
@ 2019-05-01 19:28 ` bugzilla-daemon
2019-11-19 9:19 ` bugzilla-daemon
5 siblings, 0 replies; 7+ messages in thread
From: bugzilla-daemon @ 2019-05-01 19:28 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 336 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110510
--- Comment #5 from Tom B <tom@r.je> ---
Having swapped my HDMI monitor to use DisplayPort, everything is now perfectly
fine. Both monitors work entirely as expected, no flickering or system freezes.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1099 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 7+ messages in thread* [Bug 110510] Radeon VII HDMI issues: Flicking/system crashing
2019-04-24 22:54 [Bug 110510] Radeon VII HDMI issues: Flicking/system crashing bugzilla-daemon
` (4 preceding siblings ...)
2019-05-01 19:28 ` bugzilla-daemon
@ 2019-11-19 9:19 ` bugzilla-daemon
5 siblings, 0 replies; 7+ messages in thread
From: bugzilla-daemon @ 2019-11-19 9:19 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 805 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110510
Martin Peres <martin.peres@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |MOVED
--- Comment #6 from Martin Peres <martin.peres@free.fr> ---
-- 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/757.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2368 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 7+ messages in thread