All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76558] [radeon] GPU lockup: radeon: wait for empty RBBM fifo failed ! when playing sauerbraten
Date: Wed, 21 May 2014 10:29:09 +0000	[thread overview]
Message-ID: <bug-76558-502-tqDJ56zVhC@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-76558-502@http.bugs.freedesktop.org/>


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

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

--- Comment #3 from Fabio Pedretti <fabio.ped@libero.it> ---
Created attachment 99497
  --> https://bugs.freedesktop.org/attachment.cgi?id=99497&action=edit
dmesg after the lockup with kernel 3.13.0-24.47, got switching to a VT

Here is an updated dmesg with kernel 3.13.9 (ubuntu 3.13.0-24.47), only
relevant difference is "on ring 0" is added to this line:
[11757.716140] radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000003dd41
last fence id 0x000000000003dd40 on ring 0)

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

[-- Attachment #1.2: Type: text/html, Size: 1722 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:[~2014-05-21 10:29 UTC|newest]

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