All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109239] Polaris10: Periodic random black screens for 1-2 seconds
Date: Mon, 07 Jan 2019 14:35:39 +0000	[thread overview]
Message-ID: <bug-109239-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1988 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=109239

            Bug ID: 109239
           Summary: Polaris10: Periodic random black screens for 1-2
                    seconds
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: rocketraman@gmail.com

Created attachment 142997
  --> https://bugs.freedesktop.org/attachment.cgi?id=142997&action=edit
Xorg.0.log with modesetting

I have 3 Dell WQHD Screens (2560x1440) screens, connected to a Radeon RX580
(XFX, RX-580 GTS Black Edition, 1425 MHz 8GB), running on Fedora 29.

My kernel is:

Linux edison 4.19.13-300.fc29.x86_64 #1 SMP Sat Dec 29 22:54:28 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux

On 2/3 monitors I get periodic random black screens for 1-2 seconds. The
display comes back and all appears normal after this happens.

I have tried both with and without modesetting enabled. Nothing at all appears
in  either the kernel log when this happens, or in Xorg.0.log. I have attached
complete Xorg.0.log's and the relevant parts of dmesg (from boot to the very
last drm-related message).

I was sure this was a hardware issue, and after a debugging process with XFX
support in which they had me swapping monitors and cables, they RMAed my card
and sent me a new one. However, the new card has very similar behavior (the old
card seemed to black screen only one monitor, the new seems to do two of them,
but in exactly the same way, and I have also updated my kernel and OS since
then, so its possible the hardware is completely unrelated to the minor change
in behavior).

Given the change in hardware, it seems likely to me this is a driver bug rather
than a hardware one.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3417 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-01-07 14:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 14:35 bugzilla-daemon [this message]
2019-01-07 14:35 ` [Bug 109239] Polaris10: Periodic random black screens for 1-2 seconds bugzilla-daemon
2019-01-07 14:36 ` bugzilla-daemon
2019-01-07 14:36 ` bugzilla-daemon
2019-01-07 16:52 ` bugzilla-daemon
2019-01-07 16:52 ` bugzilla-daemon
2019-01-07 16:52 ` bugzilla-daemon
2019-01-07 16:52 ` bugzilla-daemon
2019-01-07 17:29 ` bugzilla-daemon
2019-01-08 20:05 ` bugzilla-daemon
2019-01-15  9:41 ` bugzilla-daemon
2019-01-15 12:47 ` bugzilla-daemon
2019-01-15 20:24 ` bugzilla-daemon
2019-01-17 20:16 ` bugzilla-daemon
2019-02-13 10:33 ` bugzilla-daemon
2019-04-21 17:42 ` bugzilla-daemon
2019-04-26  8:08 ` bugzilla-daemon
2019-05-25 21:18 ` bugzilla-daemon
2019-07-12 21:14 ` bugzilla-daemon
2019-11-19  9:09 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-109239-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.