All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66425] "failed testing IB on ring 5" when suspending to disk
Date: Wed, 10 Jul 2013 22:23:57 +0000	[thread overview]
Message-ID: <bug-66425-502-UxynuCcLtx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66425-502@http.bugs.freedesktop.org/>


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

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

--- Comment #18 from Harald Judt <h.judt@gmx.at> ---
Created attachment 82304
  --> https://bugs.freedesktop.org/attachment.cgi?id=82304&action=edit
dmesg-hibernate.out

Ok, this is not a problem with tuxonice. I tried hibernating with current
vanilla git again, and indeed the error message occurred when resuming from
disk:

[  168.118207] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[  168.118208] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000006
last fence id 0x0000000000000004)
[  168.118209] [drm:r600_uvd_ib_test] *ERROR* radeon: fence wait failed (-35).
[  168.118212] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
ring 5 (-35).

Full dmesg attached. The computer resumed but would crash soon afterwards.
Crashes persisted until reboot.

The long delay when suspending was caused by the serial console I had attached
for debugging purposes; It really took a long time to resume but worked
eventually.

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

[-- Attachment #1.2: Type: text/html, Size: 2036 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-07-10 22:23 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01  1:19 [Bug 66425] New: "failed testing IB on ring 5" when suspending to disk bugzilla-daemon
2013-07-01 13:24 ` [Bug 66425] " bugzilla-daemon
2013-07-01 21:35 ` bugzilla-daemon
2013-07-02  9:00 ` bugzilla-daemon
2013-07-02 11:23 ` bugzilla-daemon
2013-07-03  4:56 ` bugzilla-daemon
2013-07-03 13:55 ` bugzilla-daemon
2013-07-08 14:46 ` bugzilla-daemon
2013-07-08 14:59 ` bugzilla-daemon
2013-07-08 16:46 ` bugzilla-daemon
2013-07-08 17:32 ` bugzilla-daemon
2013-07-08 18:11 ` bugzilla-daemon
2013-07-08 18:41 ` bugzilla-daemon
2013-07-08 18:49 ` bugzilla-daemon
2013-07-08 22:23 ` bugzilla-daemon
2013-07-09  7:55 ` bugzilla-daemon
2013-07-09 11:38 ` bugzilla-daemon
2013-07-10  1:29 ` bugzilla-daemon
2013-07-10 22:23 ` bugzilla-daemon [this message]
2013-07-10 22:37 ` bugzilla-daemon
2013-07-11  9:33 ` bugzilla-daemon
2013-07-11  9:51 ` bugzilla-daemon
2013-07-11 12:59 ` bugzilla-daemon
2013-07-11 18:58 ` bugzilla-daemon
2013-07-14  8:23 ` bugzilla-daemon
2013-07-14  8:37 ` bugzilla-daemon
2013-08-12 22:17 ` bugzilla-daemon
2013-08-12 22:18 ` bugzilla-daemon
2013-08-12 22:21 ` bugzilla-daemon
2013-08-12 22:22 ` bugzilla-daemon
2013-08-12 22:23 ` bugzilla-daemon
2013-08-12 22:50 ` bugzilla-daemon
2013-08-13 13:16 ` bugzilla-daemon
2013-08-13 13:21 ` bugzilla-daemon
2013-08-13 13: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-66425-502-UxynuCcLtx@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.