linux-kernel - Re: Hibernation oops with 2.6.31 won't fit the screen

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4AB55679.7010300@gmail.com>
Date:	Sun, 20 Sep 2009 00:08:57 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	Frans Pop <elendil@...net.nl>
CC:	Ondrej Zary <linux@...nbow-software.org>,
	linux-kernel@...r.kernel.org, "Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: Hibernation oops with 2.6.31 won't fit the screen - how to debug?

On 09/19/2009 11:44 PM, Frans Pop wrote:
> Ondrej Zary wrote:
>> hibernation worked great with 2.6.30 - I had over a month of uptime (it
>> never worked so well before - always crashed after some time). But in
>> 2.6.31, it's broken again - and completely. The first hibernation works
>> but it always crashes on the second one.
>>
>> The problem is that the oops is so long that it does not fit the screen -
>> even 1280x1024 is not enough. Scrolling does not work (as it used to do
>> on 2.4 kernels), netconsole does not catch it. So how can I debug this?
> 
> One way to get at least an indication of what broke the hibernation is to 
> run a bisection to find the change that broke hibernation. That could 
> provide sufficient clues for a next step.

And if it is reproducible with some debugging mode (see
Documentation/power/basic-pm-debugging.txt, section Test modes of
hibernation), you may not need to do a full hibernation/thaw cycle.

Could you attach at least the part of the oops you see?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/