From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85421] radeon stalled, GPU lockup, reset and failed on resume; crashed by firefox.
Date: Mon, 09 Feb 2015 16:43:38 +0000 [thread overview]
Message-ID: <bug-85421-2300-72KoD3jpGH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-85421-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=85421
--- Comment #27 from Hin-Tak Leung <htl10@users.sourceforge.net> ---
Created attachment 166191
--> https://bugzilla.kernel.org/attachment.cgi?id=166191&action=edit
screen corruption just before suspend & GPU crash on resume
See screenshot.
I had been playing a few videos with mplayer -vo xv http://*.mp4 from the BBC
web site, on and off; then I did some browsing and noticed a few firefox tabs
are corrupted (as shown - only about 3 out of those are). I then checked and
see some messages in dmesg:
[14452.823499] radeon 0000:00:01.0: GPU fault detected: 146 0x02050004
[14452.823512] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00015A90
[14452.823516] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x05000004
[14452.823521] VM fault (0x04, vmid 2) at page 88720, write from 'CB0'
(0x43423000) (0)
So I suspended anyway; and the GPU crashed on resume. I was able to switch to a
vt to reboot safely (not always the case) - so if there is anything say, I can
look while the GPU is still stuck, please left me know.
Been on 10.4.3 since 29 Jan (just routine fedora upgrade) and never did have
problem with 10.4.2 before that, so I guess 10.4.2/10.4.3 is at least as good
as 10.2.9 + patch.
kernel is 3.18.6-200.fc21.x86_64.
oh! I rebooted from from 3.18.5-200.fc21 and libdrm-2.4.58-3.fc21.* ->
2.4.59-4.fc21.*
So if the screen corruption or the lock-up a regression from 25 days of
goodness under 10.4.2/10.4.3 (and perhaps even a month in you include 10.4.1),
than either the kernel or libdrm might be it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-02-09 16:43 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 23:21 [Bug 85421] New: radeon stalled, GPU lockup, reset and failed on resume; crashed by firefox bugzilla-daemon
2014-10-07 21:41 ` [Bug 85421] " bugzilla-daemon
2014-10-08 12:28 ` bugzilla-daemon
2014-10-13 15:41 ` bugzilla-daemon
2014-10-13 16:09 ` bugzilla-daemon
2014-10-13 16:37 ` bugzilla-daemon
2014-10-13 21:28 ` bugzilla-daemon
2014-10-23 15:50 ` bugzilla-daemon
2014-10-28 9:52 ` bugzilla-daemon
2014-10-29 1:06 ` bugzilla-daemon
2014-11-09 9:48 ` bugzilla-daemon
2014-11-09 9:51 ` bugzilla-daemon
2014-11-21 22:33 ` bugzilla-daemon
2014-11-28 20:30 ` bugzilla-daemon
2014-12-01 2:13 ` bugzilla-daemon
2014-12-01 3:07 ` bugzilla-daemon
2014-12-05 0:35 ` bugzilla-daemon
2014-12-05 7:47 ` bugzilla-daemon
2014-12-10 22:35 ` bugzilla-daemon
2014-12-12 9:54 ` bugzilla-daemon
2014-12-16 17:18 ` bugzilla-daemon
2014-12-17 2:19 ` bugzilla-daemon
2014-12-17 20:07 ` bugzilla-daemon
2014-12-18 6:03 ` bugzilla-daemon
2014-12-18 19:40 ` bugzilla-daemon
2014-12-19 3:23 ` bugzilla-daemon
2015-01-24 1:08 ` bugzilla-daemon
2015-02-09 16:43 ` bugzilla-daemon [this message]
2015-02-09 16:48 ` bugzilla-daemon
2015-02-14 15:29 ` bugzilla-daemon
2015-02-24 23:48 ` bugzilla-daemon
2015-03-17 5:16 ` bugzilla-daemon
2015-03-17 5:21 ` bugzilla-daemon
2015-03-23 14:50 ` bugzilla-daemon
2015-03-23 23:08 ` bugzilla-daemon
2015-03-24 14:29 ` bugzilla-daemon
2015-03-24 15:39 ` bugzilla-daemon
2015-03-24 16:19 ` bugzilla-daemon
2015-03-25 3:50 ` bugzilla-daemon
2015-03-25 9:41 ` bugzilla-daemon
2015-04-26 2:11 ` bugzilla-daemon
2021-09-24 18:28 ` 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-85421-2300-72KoD3jpGH@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.