All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 155141] New: [KMS] Artifacts with OpenSource Radeon driver
Date: Sat, 27 Aug 2016 20:04:26 +0000	[thread overview]
Message-ID: <bug-155141-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=155141

            Bug ID: 155141
           Summary: [KMS] Artifacts with OpenSource Radeon driver
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.7
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: tinctura.ginseng@gmail.com
        Regression: No

OS: Arch Linux
Hardware: Notebook ASUS F8Vr, CPU Intel Core 2 Duo P8400 2.26GHz, 4 GB RAM,
Mobility Radeon HD 3470 (RV620)

After update kernel from 4.6.4 to 4.7 I found artifacts when KMS activated -
blue dots drop down in console and graphics mode. Downgrade to 4.6.4 - not
found any artifacts. Upgrade to 4.7.1 and 4.7.2 - artifacts is found. When I
disable KMS with 'nomodeset' kernel parameter the artifacts disappear.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2016-08-27 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-27 20:04 bugzilla-daemon [this message]
2016-08-27 23:01 ` [Bug 155141] [KMS] Artifacts with OpenSource Radeon driver bugzilla-daemon
2017-10-03 20:04 ` 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-155141-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.