mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Frans Pop <elendil@planet.nl>
Cc: Ondrej Zary <linux@rainbow-software.org>,
	linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Hibernation oops with 2.6.31 won't fit the screen - how to debug?
Date: Sun, 20 Sep 2009 00:08:57 +0200	[thread overview]
Message-ID: <4AB55679.7010300@gmail.com> (raw)
In-Reply-To: <200909192344.55258.elendil@planet.nl>

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?

  reply	other threads:[~2009-09-19 22:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19 19:55 Ondrej Zary
2009-09-19 21:44 ` Frans Pop
2009-09-19 22:08   ` Jiri Slaby [this message]
2009-09-22 19:56   ` Hibernation oops with 2.6.31 won't fit the screen - bisected Ondrej Zary
2009-09-30 12:03 ` Hibernation oops with 2.6.31 won't fit the screen - how to debug? Pavel Machek

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=4AB55679.7010300@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rainbow-software.org \
    --cc=rjw@sisk.pl \
    /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

Powered by JetHome