[HELP (not patch)] Re: Resume from hibernation fails 40% of time, kernel 3.16.0 (64GB of RAM, 32 Xeon E5-2687W cores)
From: Janek Kozicki
Date: Mon Aug 04 2014 - 17:24:54 EST
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/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/