From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96585] R7 260X multiple soft lockups while playing TF2
Date: Sun, 19 Jun 2016 05:48:22 +0000 [thread overview]
Message-ID: <bug-96585-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1205 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96585
Bug ID: 96585
Summary: R7 260X multiple soft lockups while playing TF2
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: toni.spets@iki.fi
Created attachment 124600
--> https://bugs.freedesktop.org/attachment.cgi?id=124600&action=edit
Full dmesg
On my Radeon R260X, I get random soft locks that last for around 10 seconds
each while playing Team Fortress 2. This happens around once or twice per hour
and usually they are close to each other. The system becomes completely
unresponsive until the outputs reset and everything continues normally.
This system has suspended and resumed multiple times so it's not a "clean boot"
and all the cycles are in the attached dmesg, including the lockups.
It's a Fedora 24 system with their 4.5.5 kernel, Mesa version 11.2.1.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2622 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
next reply other threads:[~2016-06-19 5:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 5:48 bugzilla-daemon [this message]
2016-08-19 17:11 ` [Bug 96585] R7 260X multiple soft lockups while playing TF2 bugzilla-daemon
2016-08-28 4:43 ` 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-96585-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.