From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92428] Sword Coast Legends causing GPU lockup. radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000000afd1 last fence id 0x000000000000b194 on ring 3)
Date: Sun, 11 Oct 2015 03:07:21 +0000 [thread overview]
Message-ID: <bug-92428-502-BlK8kPNwXS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92428-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 497 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92428
--- Comment #2 from James <h0ser@h0sed.org> ---
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] [1002:6819]
Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB
GDDR5 DVI-I/DVI-D/HDMI/DP [174b:e221]
Kernel driver in use: radeon
Kernel modules: radeon
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1457 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
next prev parent reply other threads:[~2015-10-11 3:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 3:05 [Bug 92428] Sword Coast Legends causing GPU lockup. radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000000afd1 last fence id 0x000000000000b194 on ring 3) bugzilla-daemon
2015-10-11 3:06 ` bugzilla-daemon
2015-10-11 3:07 ` bugzilla-daemon [this message]
2015-10-23 20:22 ` bugzilla-daemon
2015-12-18 8:51 ` bugzilla-daemon
2015-12-18 8:52 ` bugzilla-daemon
2015-12-18 20:15 ` bugzilla-daemon
2015-12-19 6:01 ` bugzilla-daemon
2015-12-21 7:34 ` bugzilla-daemon
2015-12-22 4:59 ` bugzilla-daemon
2015-12-22 5:00 ` bugzilla-daemon
2016-10-17 20:37 ` bugzilla-daemon
2019-09-25 17:53 ` 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-92428-502-BlK8kPNwXS@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.