dri-devel.lists.freedesktop.org archive mirror
 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: Mon, 08 Jul 2013 18:41:04 +0000	[thread overview]
Message-ID: <bug-66425-502-9FMWGSNieM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66425-502@http.bugs.freedesktop.org/>


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

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

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

A bit different with in-kernel hibernate (vanilla kernel, current git), using
the same config.

Hibernate worked the first time. Again, it took a long time hanging at a blank
screen and the computer did not shut off. Yet, after a hard reset, it resumed.
There were no messages in dmesg about ring 5 this time (see attachment).
However, the second hibernation attempt failed. It hang there immediately with
a blank screen, and no image was written. This was with a 3.11-pre-rc1 kernel,
maybe I'll better retest with 3.10 release...

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

[-- Attachment #1.2: Type: text/html, Size: 1836 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-08 18:41 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 [this message]
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
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-9FMWGSNieM@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;
as well as URLs for NNTP newsgroup(s).