public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Janek Kozicki <janek_listy@wp.pl>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [HELP (not patch)] Re: Resume from hibernation fails 40% of time, kernel 3.16.0 (64GB of RAM, 32 Xeon E5-2687W cores)
Date: Mon, 4 Aug 2014 23:24:47 +0200	[thread overview]
Message-ID: <20140804232447.5094b23e@absurd> (raw)
In-Reply-To: <20140804185644.05a56986@absurd>

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?

(details in my previous email)

best regards
Janek Kozicki

Janek Kozicki said:     (by the date of Mon, 4 Aug 2014 18:56:44 +0200)

> Hi,
> 
> I have an up-to-date recently installed debian wheezy. I downloaded
> https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.16.tar.xz and compiled it using:
> 
>   cp /boot/config-`uname -r` ./.config
>   make menuconfig
>   fakeroot make-kpkg --initrd --append-to-version=-vanilla.1 kernel_image kernel_headers -j38
>   dpkg -i linux-image-3.16.0-vanilla.1_3.16.0-vanilla.1-10.00.Custom_amd64.deb linux-headers-3.16.0-vanilla.1_3.16.0-vanilla.1-10.00.Custom_amd64.deb
> 
> where .config was taken from debian /boot/config-3.14-0.bpo.1-amd64
> 
> my PC has 64GB of RAM, 32 Xeon E5-2687W cores and motherboard SuperMicro MBD-X9DRI
> 
> I just did 25 tries of suspend/resume cycle. I tried 4 different
> methods of hibernation, you will find a full summary of my tries
> (including how many failures for each method) in attached script
> SLEEP.sh which I always used to perform hibernation.
> 
> 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).
> 
> I post here to get your help, and my first question: how can I
> retrieve some useful logs from a failed resume attempt?
> 
> best regards
> -- 
> Janek Kozicki                               http://janek.kozicki.pl/  |


-- 
Janek Kozicki                               http://janek.kozicki.pl/  |

  reply	other threads:[~2014-08-04 21:24 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 ` Janek Kozicki [this message]
2014-08-27  9:32   ` [HELP (not patch)] " Pavel Machek
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=20140804232447.5094b23e@absurd \
    --to=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