All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76558] New: GPU lockup: radeon: wait for empty RBBM fifo failed ! when playing sauerbraten
Date: Mon, 24 Mar 2014 16:16:54 +0000	[thread overview]
Message-ID: <bug-76558-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: high
            Bug ID: 76558
          Assignee: dri-devel@lists.freedesktop.org
           Summary: GPU lockup: radeon: wait for empty RBBM fifo failed !
                    when playing sauerbraten
          Severity: critical
    Classification: Unclassified
                OS: Linux (All)
          Reporter: fabio.ped@libero.it
          Hardware: x86 (IA32)
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

Created attachment 96295
  --> https://bugs.freedesktop.org/attachment.cgi?id=96295&action=edit
dmesg after the lockup, got switching to a VT

I am using kernel 3.11.0-18.32 (default Ubuntu 13.10 kernel) with mesa from git
on a RV530. The system is usually very stable, however when running
sauerbreaten with wake6 map (sauerbraten-wake6 package on Debian/Ubuntu) this
way:
sauerbraten -lwake6

after some minutes I get the following lockup:

[ 8425.176130] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[ 8425.176144] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000002845
last fence id 0x0000000000002844)
[ 8425.349835] radeon: wait for empty RBBM fifo failed ! Bad things might
happen.
[ 8425.523469] Failed to wait GUI idle while programming pipes. Bad things
might happen.
[ 8425.524520] radeon 0000:01:00.0: Saved 59 dwords of commands on ring 0.
[ 8425.530923] radeon 0000:01:00.0: (rs600_asic_reset:401)
RBBM_STATUS=0x9401C100
[ 8426.029068] radeon 0000:01:00.0: (rs600_asic_reset:421)
RBBM_STATUS=0x9401C100
[ 8426.526183] radeon 0000:01:00.0: (rs600_asic_reset:429)
RBBM_STATUS=0x9400C100
[ 8427.023299] radeon 0000:01:00.0: (rs600_asic_reset:437)
RBBM_STATUS=0x9400C100
[ 8427.023370] radeon 0000:01:00.0: failed to reset GPU
[ 8427.024701] radeon 0000:01:00.0: GPU reset failed
[ 8427.028124] radeon 0000:01:00.0: couldn't schedule ib
[ 8427.028133] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[ 8427.057855] radeon 0000:01:00.0: couldn't schedule ib
...

Full dmesg is attached. After the lockup I can switch to/from console, but I
have to reboot because the screen is corrupted/flashing.

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

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

             reply	other threads:[~2014-03-24 16:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24 16:16 bugzilla-daemon [this message]
2014-04-09 13:36 ` [Bug 76558] [radeon] GPU lockup: radeon: wait for empty RBBM fifo failed ! when playing sauerbraten bugzilla-daemon
2014-04-19  9:45 ` bugzilla-daemon
2014-05-21 10:29 ` bugzilla-daemon
2014-05-21 10:30 ` bugzilla-daemon
2014-05-21 10:31 ` bugzilla-daemon
2019-11-19  8:47 ` 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-76558-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.