dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99278] kwin corruption when desktop effects enabled
Date: Wed, 04 Jan 2017 22:56:44 +0000	[thread overview]
Message-ID: <bug-99278-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 99278
           Summary: kwin corruption when desktop effects enabled
           Product: Mesa
           Version: 13.0
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: vedran@miletic.net
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 128760
  --> https://bugs.freedesktop.org/attachment.cgi?id=128760&action=edit
Photo

Using Fedora 25 with Mesa 13 and LLVM 3.8 on:

04:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Venus
XTX [Radeon HD 8890M / R9 M275X/M375X] [1002:6820] (rev 81)

identified as "AMD CAPE VERDE" by Mesa. Photo is attached. This is a dual GPU
laptop (Lenovo Z51-70), main GPU being

00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)

While corruption happens, dmesg | grep radeon does not show anything
suspicious, just:

[21253.931482] radeon 0000:04:00.0: WB enabled
[21253.931484] radeon 0000:04:00.0: fence driver on ring 0 use gpu addr
0x0000000100000c00 and cpu addr 0xffff99e2d0bb1c00
[21253.931485] radeon 0000:04:00.0: fence driver on ring 1 use gpu addr
0x0000000100000c04 and cpu addr 0xffff99e2d0bb1c04
[21253.931486] radeon 0000:04:00.0: fence driver on ring 2 use gpu addr
0x0000000100000c08 and cpu addr 0xffff99e2d0bb1c08
[21253.931486] radeon 0000:04:00.0: fence driver on ring 3 use gpu addr
0x0000000100000c0c and cpu addr 0xffff99e2d0bb1c0c
[21253.931487] radeon 0000:04:00.0: fence driver on ring 4 use gpu addr
0x0000000100000c10 and cpu addr 0xffff99e2d0bb1c10
[21253.932296] radeon 0000:04:00.0: fence driver on ring 5 use gpu addr
0x0000000000075a18 and cpu addr 0xffffbefe01235a18
[21253.952686] radeon 0000:04:00.0: fence driver on ring 6 use gpu addr
0x0000000100000c18 and cpu addr 0xffff99e2d0bb1c18
[21253.952687] radeon 0000:04:00.0: fence driver on ring 7 use gpu addr
0x0000000100000c1c and cpu addr 0xffff99e2d0bb1c1c

Should I test LLVM 3.9/4.0-git? Any other info that could be useful?

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

[-- Attachment #1.2: Type: text/html, Size: 3801 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-01-04 22:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 22:56 bugzilla-daemon [this message]
2018-04-03  5:26 ` [Bug 99278] kwin corruption when desktop effects enabled bugzilla-daemon
2019-09-25 17:56 ` 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-99278-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