dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71864] [RS690] GPU Lockup CP Stall and Resulting Kernel Oops (Kernel 3.2.0)
Date: Sat, 23 Nov 2013 21:41:56 +0000	[thread overview]
Message-ID: <bug-71864-502-FITOuPrHAP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71864-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1603 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=71864

--- Comment #14 from reimth@gmail.com ---
(In reply to comment #13)
> (In reply to comment #12)
> > (In reply to comment #11)
> > > (In reply to comment #10)
> > > > Is this still an issue with a newer kernel?  Did you also update your
> > > > userspace stack (mesa, xf86-video-ati)?
> 
> Bad news: I confirm this bug also on linux kernel 3.8:
> 
Again a kernel crash:
[ 1825.192038] radeon 0000:01:05.0: GPU lockup CP stall for more than 10000msec
[ 1825.192072] radeon 0000:01:05.0: GPU lockup (waiting for 0x0000000000004ac4)
[ 1825.192100] radeon 0000:01:05.0: failed to get a new IB (-35)
[ 1825.192108] [drm:radeon_cs_ib_chunk] *ERROR* Failed to get ib !
[ 1825.333066] radeon: wait for empty RBBM fifo failed ! Bad things might
happen.
[ 1825.473624] Failed to wait GUI idle while programming pipes. Bad things
might happen.
[ 1825.484893] radeon 0000:01:05.0: Saved 5403 dwords of commands on ring 0.
[ 1825.498544] radeon 0000:01:05.0: (rs600_asic_reset:401)
RBBM_STATUS=0x9401C100
[ 1825.996650] radeon 0000:01:05.0: (rs600_asic_reset:421)
RBBM_STATUS=0x9401C100
[ 1826.493732] radeon 0000:01:05.0: (rs600_asic_reset:429)
RBBM_STATUS=0x9400C100
[ 1826.990803] radeon 0000:01:05.0: (rs600_asic_reset:437)
RBBM_STATUS=0x9400C100
[ 1826.990854] radeon 0000:01:05.0: failed to reset GPU
[ 1826.999117] radeon 0000:01:05.0: GPU reset failed
[ 1827.000816] radeon 0000:01:05.0: couldn't schedule ib
[ 1827.000831] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2628 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

  parent reply	other threads:[~2013-11-23 21:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21  8:42 [Bug 71864] New: [RS690] GPU Lockup CP Stall and Resulting Kernel Oops (Kernel 3.2.0) bugzilla-daemon
2013-11-21  8:44 ` [Bug 71864] " bugzilla-daemon
2013-11-21  8:44 ` bugzilla-daemon
2013-11-21  8:45 ` bugzilla-daemon
2013-11-21  8:45 ` bugzilla-daemon
2013-11-21  8:50 ` bugzilla-daemon
2013-11-21  8:51 ` bugzilla-daemon
2013-11-21  8:55 ` bugzilla-daemon
2013-11-21  8:56 ` bugzilla-daemon
2013-11-21  9:00 ` bugzilla-daemon
2013-11-21 16:10 ` bugzilla-daemon
2013-11-22 14:49 ` bugzilla-daemon
2013-11-22 15:08 ` bugzilla-daemon
2013-11-23 11:39 ` bugzilla-daemon
2013-11-23 21:41 ` bugzilla-daemon [this message]
2013-11-24 15:37 ` bugzilla-daemon
2013-11-24 16:17 ` bugzilla-daemon
2013-11-24 17:15 ` bugzilla-daemon
2013-12-02 10:00 ` bugzilla-daemon
2013-12-02 17:55 ` bugzilla-daemon
2013-12-05 10:23 ` bugzilla-daemon
2013-12-05 15:10 ` bugzilla-daemon
2019-11-19  8:40 ` 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-71864-502-FITOuPrHAP@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