From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86357] [RadeonSI] GPU lockup with mesa 10.3.3 / kernel 3.17.2
Date: Sun, 16 Nov 2014 22:42:59 +0000 [thread overview]
Message-ID: <bug-86357-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2726 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=86357
Bug ID: 86357
Summary: [RadeonSI] GPU lockup with mesa 10.3.3 / kernel 3.17.2
Product: Mesa
Version: 10.3
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: madcatx@atlas.cz
Created attachment 109569
--> https://bugs.freedesktop.org/attachment.cgi?id=109569&action=edit
journalctl crash info, contains both dmesg and Xorg logs
After a recent update of my Fedora 21 box I've experienced this crash twice.
The entire desktop except for mouse freezes and I cannot even VT switch to
console. If the keypress gets registered I end up with a powered down display
and a switch back to X results in a completely corrupted screen. If I don't try
a VT switch I can still move the mouse but other than that the machine appears
dead. It eventually stops responding to ping and the only way out is a hard
reboot.
I have been using this machine for quite a while and I haven't experienced this
before until yesterday. I checked the yum logs but there doesn't seem to be
anything directly related to the graphics except maybe for this:
Updated xkeyboard-config-2.13-2.fc21.noarch
@updates-testing
Update 2.13-3.fc21.noarch
@updates-testing
Updated xorg-x11-font-utils-1:7.5-23.fc21.x86_64
@updates-testing
Update 1:7.5-25.fc21.x86_64
@updates-testing
Updated xorg-x11-fonts-Type1-7.5-11.fc21.noarch
@updates-testing
Update 7.5-14.fc21.noarch
@updates-testing
Updated xorg-x11-server-utils-7.7-9.fc21.x86_64
@updates-testing
Update 7.7-10.fc21.x86_64
@updates-testing
Updated xorg-x11-xkb-utils-7.7-10.fc21.x86_64
@fedora
Relevant packages installed:
xorg-x11-drv-ati - 7.5.0-1.fc21
xorg-x11-server-Xorg.x86_64 - 1.16.1-1.fc21
kernel.x86_64 - 3.17.2-300.fc21
Custom-built mesa 10.3.3 with "Fix v5" from "BUG 60879" applied
My card is a 7730 LE, PID:VID 1002:aab0
X and kernel apparently caught and logged the problem, relevant journalctl
output is attached. It usually takes a few hours for this to happen, the only
thing the two crashes I've had so far have in common is a Flash video playing
in the background when the system froze.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4376 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 reply other threads:[~2014-11-16 22:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 22:42 bugzilla-daemon [this message]
2014-11-17 21:16 ` [Bug 86357] [RadeonSI] GPU lockup with mesa 10.3.3 / kernel 3.17.2 bugzilla-daemon
2014-11-18 7:15 ` bugzilla-daemon
2014-11-18 12:15 ` bugzilla-daemon
2015-08-02 11:18 ` bugzilla-daemon
2015-08-02 12:17 ` bugzilla-daemon
2015-08-02 12:57 ` 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-86357-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox