dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100726] [REGRESSION][BISECTED] Severe flickering with an R9 290
Date: Wed, 19 Apr 2017 18:55:45 +0000	[thread overview]
Message-ID: <bug-100726-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 100726
           Summary: [REGRESSION][BISECTED] Severe flickering with an R9
                    290
           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: hiwatari.seiji@gmail.com

As of the commit:
    d8d1721cfb3162abbda078d67a928792d6552b84 : A series of fixup patches meant
to fix the usage of DMA on stack, plus one warning fixup

My R9 290 produces heavy flickering artifacts in 1 of 3 or 4 cases when
starting Linux.
I am using the amdgpu kernel module, and have not tested this with radeon.
When the bug occurs, the system is completely unusable.

Since the occurence of this bug is not really deterministic, bisecting it was
not that easy. I hope I didn't make any mistake.

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

[-- Attachment #1.2: Type: text/html, Size: 2395 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:[~2017-04-19 18:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 18:55 bugzilla-daemon [this message]
2017-04-19 18:56 ` [Bug 100726] [REGRESSION][BISECTED] Severe flickering with an R9 290 bugzilla-daemon
2017-04-20  1:42 ` bugzilla-daemon
2017-04-24 16:08 ` bugzilla-daemon
2017-04-24 17:54 ` bugzilla-daemon
2017-11-26 10:56 ` bugzilla-daemon
2017-11-26 10:57 ` bugzilla-daemon
2017-11-27 10:32 ` bugzilla-daemon
2017-11-27 10:34 ` bugzilla-daemon
2017-11-27 12:01 ` bugzilla-daemon
2017-11-28 16:13 ` bugzilla-daemon
2018-03-14  1:28 ` bugzilla-daemon
2018-03-14  1:29 ` bugzilla-daemon
2018-03-20 19:14 ` bugzilla-daemon
2018-03-24 11:15 ` bugzilla-daemon
2019-11-19  8:15 ` 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-100726-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).