Bug 105744 - randomly flashing screen with RX 580
Summary: randomly flashing screen with RX 580
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-26 08:56 UTC by sam.halliday
Modified: 2019-11-19 08:33 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg.log (78.09 KB, text/plain)
2018-03-26 20:35 UTC, sam.halliday
no flags Details
Xorg.0.log (32.58 KB, text/plain)
2018-03-26 20:35 UTC, sam.halliday
no flags Details

Description sam.halliday 2018-03-26 08:56:45 UTC
I recently bought a Sapphire Radeon RX 580 Nitro+ 4 GB GDDR5 and I'm using the amdgpu drivers on ArchLinux with xmonad.

Unfortunately the entire screen flashes randomly, usually correlated with clicking the mouse button in chrome. Enabling TearFree makes no difference, disabling the hardware cursor makes no difference.

I do not wish to use amdgpupro, for ethical reasons.

I can perform more diagnostics if needed, but I appreciate that this is a very difficult to reproduce problem so my hopes of a solution are low...


Version / info dumps:

xf86-video-amdgpu 18.0.1

4.15.12-1-ARCH #1 SMP PREEMPT Wed Mar 21 15:14:56 UTC 2018 x86_64 GNU/Linux

~ sudo lshw -C video
  *-display                 
       description: VGA compatible controller
       product: Ellesmere [Radeon RX 470/480/570/580]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:01:00.0
       version: e7
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
       configuration: driver=amdgpu latency=0
       resources: irq:123 memory:d0000000-dfffffff memory:e0000000-e01fffff ioport:e000(size=256) memory:ef400000-ef43ffff memory:c0000-dffff


~ cat /etc/X11/xorg.conf.d/20-radeon.conf 
Section "Device"
        Identifier "AMD"
        Driver "amdgpu"
        Option "SWcursor" "on"
        Option "DRI" "3"
        Option "TearFree" "on"
        Option "AccelMethod" "glamor"
EndSection


I version control my user-level dotfiles:

- https://gitlab.com/fommil/dotfiles
- plus machine specific customisations https://gitlab.com/fommil/dotfiles/tree/master/Profiles/Samurai
Comment 1 Alex Deucher 2018-03-26 15:46:26 UTC
Please attach your dmesg output and xorg log.
Comment 2 sam.halliday 2018-03-26 20:35:25 UTC
Created attachment 138361 [details]
dmesg.log
Comment 3 sam.halliday 2018-03-26 20:35:43 UTC
Created attachment 138362 [details]
Xorg.0.log
Comment 4 Michel Dänzer 2018-04-05 10:40:25 UTC
Does it also happen with amdgpu.dc=0 on the kernel command line?

Can you make a video showing what the flashes look like?
Comment 5 sam.halliday 2018-04-05 11:38:10 UTC
Unfortunately, making a video would be extremely difficult. The
flashes are completely random, I have not found any way to reproduce
it and sometimes it can be 30 minutes or an hour without a problem.

I have added this kernel parameter and have not seen any flashes since
the reboot 10 minutes ago. Fingers crossed we have isolated the issue
to the new DC logic!

On 5 April 2018 at 11:40,  <bugzilla-daemon@freedesktop.org> wrote:
> Comment # 4 on bug 105744 from Michel Dänzer
>
> Does it also happen with amdgpu.dc=0 on the kernel command line?
>
> Can you make a video showing what the flashes look like?
>
> ________________________________
> You are receiving this mail because:
>
> You reported the bug.
Comment 6 sam.halliday 2018-04-19 22:51:09 UTC
This seems to be much better in kernel build 4.16.2-2-ARCH and I no longer need the amdgpu.dc=0 kernel flag.
Comment 7 sam.halliday 2018-04-19 23:01:44 UTC
sod's law... 5 minutes after closing the ticket I got a screen flash. *sigh*

At least it seems a lot less frequent than before.
Comment 8 Michel Dänzer 2018-10-04 16:37:54 UTC
Is this still happening with current kernels? Still only with DC?
Comment 9 Martin Peres 2019-11-19 08:33:44 UTC
-- 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/338.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.