All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93352] GRID Autosport crashes on start of race
Date: Sat, 16 Jan 2016 19:27:46 +0000	[thread overview]
Message-ID: <bug-93352-502-bbJ4lEXqfc@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93352-502@http.bugs.freedesktop.org/>


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

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

--- Comment #28 from Maxim Sheviakov <mrader3940@gmail.com> ---
> and I believe unrelated to the one discussed here
Actually, it is. All the logs and fixes comply with my problem (not only mine,
heh). I think that the problem lies deeper than we think - here's why it is so:
My rig is equipped with Radeon R7 370 Armor 2X from MSI. It's a GCN1.0 GPU
based off Cape Verde/Curacao PRO chip from R9 270X. It doesn't matter that the
memory clock is lower than it should at 800MHz (if quad-pumped, or 200MHz if
you like), another thing does: people with GCN1.1+ GPUs can run the game
flawlessly without issues like mine/Jurgen's - it just works. However, many
GCN1.0-cards owners claim they have the same issue. Maybe we should look into
RadeonSI driver's source if there are any acting differences between GCN1.0 and
1.1+ GPUs' code?

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

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

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

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

  parent reply	other threads:[~2016-01-16 19:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 16:44 [Bug 93352] GRID Autosport crashes on start of race bugzilla-daemon
2015-12-11 16:59 ` bugzilla-daemon
2015-12-11 17:27 ` bugzilla-daemon
2015-12-11 18:01 ` bugzilla-daemon
2015-12-11 19:38 ` bugzilla-daemon
2015-12-11 19:46 ` bugzilla-daemon
2015-12-11 20:20 ` bugzilla-daemon
2015-12-12  2:19 ` bugzilla-daemon
2015-12-12  2:35 ` bugzilla-daemon
2015-12-12  6:09 ` bugzilla-daemon
2015-12-12 12:44 ` bugzilla-daemon
2015-12-12 14:58 ` bugzilla-daemon
2015-12-13 16:11 ` bugzilla-daemon
2015-12-13 16:40 ` bugzilla-daemon
2015-12-14  0:57 ` bugzilla-daemon
2015-12-14  1:08 ` bugzilla-daemon
2015-12-14  1:37 ` bugzilla-daemon
2015-12-14  1:40 ` bugzilla-daemon
2015-12-14  7:17 ` bugzilla-daemon
2015-12-14  7:28 ` bugzilla-daemon
2015-12-14 10:13 ` bugzilla-daemon
2015-12-15 18:01 ` bugzilla-daemon
2015-12-26 21:04 ` bugzilla-daemon
2015-12-29 19:07 ` bugzilla-daemon
2016-01-16 18:34 ` bugzilla-daemon
2016-01-16 19:01 ` bugzilla-daemon
2016-01-16 19:05 ` bugzilla-daemon
2016-01-16 19:06 ` bugzilla-daemon
2016-01-16 19:27 ` bugzilla-daemon [this message]
2016-01-18  6:40 ` 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-93352-502-bbJ4lEXqfc@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.