All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109319] [radeonsi] Two Point Hospital: rendered in mostly black on an Oland XT GPU
Date: Fri, 11 Jan 2019 19:42:50 +0000	[thread overview]
Message-ID: <bug-109319-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 109319
           Summary: [radeonsi] Two Point Hospital: rendered in mostly
                    black on an Oland XT GPU
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Keywords: have-backtrace
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: kai@dev.carbon-project.org
        QA Contact: dri-devel@lists.freedesktop.org
            Blocks: 77449

Created attachment 143074
  --> https://bugs.freedesktop.org/attachment.cgi?id=143074&action=edit
Image showing the rendering issues of TPH with radeonsi on OLAND

A friend of mine for whom I'm doing the Linux tech support has trouble playing
Two Point Hospital (TPH) on his Oland XT GPU with radeonsi. With older versions
of Mesa the game locked up the GPU after a while, therefore I built him a Mesa
from Git, linked against LLVM 8 (see below for details on the complete stack).
But with the Git version the game becomes completely unplayable, because most
of the screen is rendered in black. Menus and some outlines are shown. See the
attached picture my friend sent me for details on how this looks. [NB: I've
been able to play TPH on my HAWAII PRO based system without any issues so far.]
He uses the radeon stack, due to the limitations of amdgpu with this GPU
generation.

At <https://c.1und1.de/@519917343397118178/ZZXLY27mRj-iQZQsH0GFmQ> you'll find
an apitrace my friend recorded, which reproduces the issue on his system when
played back.

The stack my friend uses is (Debian Stretch with backports as a base):
GPU: Oland XT [R7 250] (ChipID = 0x6610)
Mesa: Git:master/8847370424
libdrm: 2.4.95-1~bpo9+1
LLVM: SVN:trunk/r350064 (8.0 devel)
X.Org: 2:1.19.2-1+deb9u5
Linux: 4.20-1~exp1
Firmware: 20180825+dfsg-1~bpo9+1
DDX: 1:7.8.0-1+b1

Let me know, if you need anything else.


Referenced Bugs:

https://bugs.freedesktop.org/show_bug.cgi?id=77449
[Bug 77449] Tracker bug for all bugs related to Steam titles
-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4471 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-11 19:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 19:42 bugzilla-daemon [this message]
2019-01-11 19:46 ` [Bug 109319] [radeonsi] Two Point Hospital: rendered in mostly black on an Oland XT GPU bugzilla-daemon
2019-01-11 19:46 ` bugzilla-daemon
2019-07-05  6:34 ` 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-109319-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.