dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 28 Nov 2014 20:30:22 +0000	[thread overview]
Message-ID: <bug-85421-2300-EbDrBFs1af@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-85421-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=85421

Jorn Amundsen <jorn.amundsen@ntnu.no> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jorn.amundsen@ntnu.no

--- Comment #13 from Jorn Amundsen <jorn.amundsen@ntnu.no> ---
I also experience similar hangs, with a F20 system with mesa 10.3.3. In total,
I have F20 installed on four systems, two using the nvidia kernel driver, one
with i915 and one with radeon. Only the radeon system experience hangs. I get

Nov 28 10:17:15 t kernel: radeon 0000:01:00.0: ring 5 stalled for more than
10000msec
Nov 28 10:17:15 t kernel: radeon 0000:01:00.0: GPU lockup (waiting for
0x0000000000000004 last fence id 0x0000000000000002 on ring 5)
Nov 28 10:17:15 t kernel: [drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait
failed (-35).
Nov 28 10:17:15 t kernel: [drm:radeon_ib_ring_tests] *ERROR* radeon: failed
testing IB on ring 5 (-35).
Nov 28 10:17:15 t kernel: [drm:si_dpm_set_power_state] *ERROR* si_set_sw_state
failed
Nov 28 10:17:15 t kernel: radeon 0000:01:00.0: GPU fault detected: 146
0x06c24804
Nov 28 10:17:15 t kernel: radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x000125B6
Nov 28 10:17:15 t kernel: radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02048004
Nov 28 10:17:15 t kernel: VM fault (0x04, vmid 1) at page 75190, read from TC
(72)
Nov 28 10:17:15 t kernel: radeon 0000:01:00.0: GPU fault detected: 146
0x04a33d04
Nov 28 10:17:15 t kernel: radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00012EA5
Nov 28 10:17:15 t kernel: radeon 0000:01:00.0: 
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0303D004
Nov 28 10:17:15 t kernel: VM fault (0x04, vmid 1) at page 77477, write from
DMA1 (61)
Nov 28 10:17:42 t sh: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did
not process its input
...

I can not pinpoint one specific action which triggers the hang. First time it
was firefox, next time Konsole and other times it simply hangs a while after
locking the screen. I am considering downgrading mesa. Let me know if there are
other measures I can take to help resolving this bug.

-- 
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

  parent reply	other threads:[~2014-11-28 20:30 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 [this message]
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
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-EbDrBFs1af@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).