public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Janek Kozicki <janek_listy@wp.pl>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [HELP (not patch)] Re: Resume from hibernation fails 40% of time, kernel 3.16.0 (64GB of RAM, 32 Xeon E5-2687W cores)
Date: Wed, 27 Aug 2014 11:32:13 +0200	[thread overview]
Message-ID: <20140827093213.GA30622@amd> (raw)
In-Reply-To: <20140804232447.5094b23e@absurd>

On Mon 2014-08-04 23:24:47, Janek Kozicki wrote:
> I see that this list is extremely busy, I thought this is the
> place to go asking for help in debugging hibernation. If that's not
> the right place, please tell me where should I go. If that's the
> right place, please get me started. First - how can I retrieve some
> useful logs from failed resume attempts?

You want to cc rjw.

> > The failure was always a reboot after resume had almost succeeded. In
> > cases when there was a success there was a ---[cut here]--- part
> > which is in the attachment. All of my successes are included in the
> > attachments (please note that method had 0 success rate, so no
> > success logs are attached for it).

Usually trying with minimum set of drivers loaded is useful debug
technique. Plus there are some debugging hints in Documentation/.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2014-08-27  9:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 16:56 Resume from hibernation fails 40% of time, kernel 3.16.0 (64GB of RAM, 32 Xeon E5-2687W cores) Janek Kozicki
2014-08-04 21:24 ` [HELP (not patch)] " Janek Kozicki
2014-08-27  9:32   ` Pavel Machek [this message]
2014-08-27 11:19     ` Janek Kozicki

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=20140827093213.GA30622@amd \
    --to=pavel@ucw.cz \
    --cc=janek_listy@wp.pl \
    --cc=linux-kernel@vger.kernel.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