Hibernation oops with 2.6.31 won't fit the screen - how to debug?
Hello,
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?
Signature · 1 line
Ondrej Zary
Quoted 8 lines · Ondrej Zary
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.
Would that be an option for you?
Cheers,
FJP
Quoted 6 lines · Frans Pop
Quoted 5 lines · Ondrej Zary
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.
Quoted 7 lines
Quoted 3 lines
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?
Re: Hibernation oops with 2.6.31 won't fit the screen - bisected
In reply to Frans PopQuoted 10 lines · On Saturday 19 September 2009 23:44:54 Frans Pop wrote:
Quoted 8 lines · Ondrej Zary
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?
Quoted 5 lines
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.
Would that be an option for you?
I bisected it and found this:
c7121843685de2bf7f3afd3ae1d6a146010bf1fc is first bad commit commit c7121843685de2bf7f3afd3ae1d6a146010bf1fc
Author: Magnus Damm <[email protected]> Date: Tue Jul 28 14:09:55 2009 -0700
clocksource: Save mult_orig in clocksource_disable()
To fix the common case where ->enable() does not set up mult, make sure mult_orig is saved in mult on disable.
Also add comments to explain why we do this.
LKML-Reference: <[email protected]>
:040000 040000 c965062bc79af46cdb3522fc7ab1cc81d2f84de3 26616c88a8128b25fd15c3da39ac6251cd9723b6 M include
Reverting this commit fixes the problem.
Signature · 1 line
Ondrej Zary
Quoted 9 lines · Ondrej Zary
Hello,
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?
I see you solved that already but... vga=6 and mdelay(1000) in printk/oops code is canonical way to debug that.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html