All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111010] Cemu Shader Cache Corruption Displaying Solid Color After commit 11e16ca7ce0
Date: Thu, 27 Jun 2019 02:32:23 +0000	[thread overview]
Message-ID: <bug-111010-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 111010
           Summary: Cemu Shader Cache Corruption Displaying Solid Color
                    After commit 11e16ca7ce0
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: felix.adrianto@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 144651
  --> https://bugs.freedesktop.org/attachment.cgi?id=144651&action=edit
shader cache corruption

Background:
Using Cemu emulator with shader cache functionality breaks after commit
11e16ca7ce0. Screen display only solid colors with very low fps.

System:
AMD Ryzen 2600
RX580
Linux 5.0.9, amdgpu, mesa master

How to reproduce the issue:
1. Run Cemu, enable shader cache functionality
2. Play a game then let shader cahce be generated. Game can be played normally
and shader can be built normally. No graphical issue is found at this stage.
3. Quit Cemu
4. Play the same game again utilizing the generated shader cache
5. Game display shows flickering solid colors as shown in this ticket
attachment. 

Expected result:
Playing the same game with previously generated shader cache should display the
correct graphic instead of flickering solid colors.

Can you address this issue?

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

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

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

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

             reply	other threads:[~2019-06-27  2:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27  2:32 bugzilla-daemon [this message]
2019-07-01  2:31 ` [Bug 111010] Cemu Shader Cache Corruption Displaying Solid Color After commit 11e16ca7ce0 bugzilla-daemon
2019-07-01  2:32 ` bugzilla-daemon
2019-07-01  3:38 ` bugzilla-daemon
2019-07-01 11:23 ` bugzilla-daemon
2019-07-11 23:32 ` 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-111010-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.