Help with debugging intermittent crash on resume from hibernation

Help with debugging intermittent crash on resume from hibernation

[Nikolaus Rath]

Hello,

In about one out of 10 resumes from hibernation, my system resets after
the hibernation image has been loaded. I am hibernating using

# echo platform > /sys/power/disk
# echo disk > /sys/power/state

When testing hibernation using

# echo core > /sys/power/pm_test
# echo platform > /sys/power/disk
# echo disk > /sys/power/state

I was not able to produce the same failure.

I then tried attaching a serial console and booted with
console=ttyS0,115200n8 no_console_suspend. For the failed attempt, the
last messages before the reset are:

[   25.192978] Disabling non-boot CPUs ...
[   25.234496] intel_pstate CPU 1 exiting
[   25.270548] NOHZ: local_softirq_pending 10
[   25.274657] NOHZ: local_softirq_pending 10
[   25.279892] smpboot: CPU 1 is now offline
[   25.318618] intel_pstate CPU 2 exiting
[   25.454816] smpboot: CPU 2 is now offline
[   25.494879] intel_pstate CPU 3 exiting
[   25.647097] smpboot: CPU 3 is now offline
[   25.687158] intel_pstate CPU 4 exiting
[   25.819349] smpboot: CPU 4 is now offline
[   25.859411] intel_pstate CPU 5 exiting
[   25.995610] smpboot: CPU 5 is now offline
[   26.015640] intel_pstate CPU 6 exiting
[   26.155843] smpboot: CPU 6 is now offline
[   26.175874] intel_pstate CPU 7 exiting
[   26.201040] smpboot: CPU 7 is now offline

For the successful attempt, the last messages before the jump in the
time (which I assume indicate that resume was complete) are:

[   25.428213] Disabling non-boot CPUs ...^M
[   25.549875] intel_pstate CPU 1 exiting^M
[   25.694081] smpboot: CPU 1 is now offline^M
[   27.092141] intel_pstate CPU 2 exiting^M
[   27.232341] smpboot: CPU 2 is now offline^M
[   27.364542] intel_pstate CPU 3 exiting^M
[   27.404597] NOHZ: local_softirq_pending 10^M
[   27.408704] NOHZ: local_softirq_pending 10^M
[   27.413942] smpboot: CPU 3 is now offline^M
[   27.556820] intel_pstate CPU 4 exiting^M
[   27.582000] smpboot: CPU 4 is now offline^M
[   27.600891] intel_pstate CPU 5 exiting^M
[   27.745093] smpboot: CPU 5 is now offline^M
[   27.849247] intel_pstate CPU 6 exiting^M
[   28.538259] smpboot: CPU 6 is now offline^M
[   28.558292] intel_pstate CPU 7 exiting^M
[   28.583457] smpboot: CPU 7 is now offline^M
[23880.929604] Enabling non-boot CPUs ...^M
[23880.933432] x86: Booting SMP configuration:^M

(I uploaded the complete logs to https://dl.dropboxusercontent.com/u/11545826/logfiles.tar.xz).

At least to me, this unfortunately gives absolutely no indication of
what might be going wrong.

Other than trying again with the -rc3 (which I'll do next), is there
anything else I can do to debug this further?


Thanks,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

Re: Help with debugging intermittent crash on resume from hibernation

[Nikolaus Rath]

On Mar 13 2015, Nikolaus Rath <Nikolaus@rath.org> wrote:
> Hello,
>
> In about one out of 10 resumes from hibernation, my system resets after
> the hibernation image has been loaded. I am hibernating using
>
> # echo platform > /sys/power/disk
> # echo disk > /sys/power/state
>
> When testing hibernation using
>
> # echo core > /sys/power/pm_test
> # echo platform > /sys/power/disk
> # echo disk > /sys/power/state
>
> I was not able to produce the same failure.
>
> I then tried attaching a serial console and booted with
> console=ttyS0,115200n8 no_console_suspend. For the failed attempt, the
> last messages before the reset are:
[...]

I reproduced the same problem with 4.0.0-rc3. Is there anything I can do
to get more debugging information?

Thanks,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

Re: Help with debugging intermittent crash on resume from hibernation

[Mike Galbraith]

(+CC)

On Thu, 2015-03-19 at 20:21 -0700, Nikolaus Rath wrote:
> On Mar 13 2015, Nikolaus Rath <Nikolaus@rath.org> wrote:
> > Hello,
> >
> > In about one out of 10 resumes from hibernation, my system resets after
> > the hibernation image has been loaded. I am hibernating using
> >
> > # echo platform > /sys/power/disk
> > # echo disk > /sys/power/state
> >
> > When testing hibernation using
> >
> > # echo core > /sys/power/pm_test
> > # echo platform > /sys/power/disk
> > # echo disk > /sys/power/state
> >
> > I was not able to produce the same failure.
> >
> > I then tried attaching a serial console and booted with
> > console=ttyS0,115200n8 no_console_suspend. For the failed attempt, the
> > last messages before the reset are:
> [...]
> 
> I reproduced the same problem with 4.0.0-rc3. Is there anything I can do
> to get more debugging information?
> 
> Thanks,
> -Nikolaus
> 

Re: Help with debugging intermittent crash on resume from hibernation

[Nikolaus Rath]

On 03/19/2015 08:57 PM, Mike Galbraith wrote:
> (+CC)
> 
> On Thu, 2015-03-19 at 20:21 -0700, Nikolaus Rath wrote:
>> On Mar 13 2015, Nikolaus Rath <Nikolaus@rath.org> wrote:
>>> Hello,
>>>
>>> In about one out of 10 resumes from hibernation, my system resets after
>>> the hibernation image has been loaded. I am hibernating using
>>>
>>> # echo platform > /sys/power/disk
>>> # echo disk > /sys/power/state
>>>
>>> When testing hibernation using
>>>
>>> # echo core > /sys/power/pm_test
>>> # echo platform > /sys/power/disk
>>> # echo disk > /sys/power/state
>>>
>>> I was not able to produce the same failure.
>>>
>>> I then tried attaching a serial console and booted with
>>> console=ttyS0,115200n8 no_console_suspend. For the failed attempt, the
>>> last messages before the reset are:
>> [...]
>>
>> I reproduced the same problem with 4.0.0-rc3. Is there anything I can do
>> to get more debugging information?

I also found that blacklisting the nouveau module seems to dramatically
reduce the occurence of this problem (it only happened once since I
blacklisted the module which is probably about ~30 resumes ago).

Is there anything I can do to help debug this issue?


Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

Re: Help with debugging intermittent crash on resume from hibernation

[Mike Galbraith]

On Fri, 2015-04-17 at 20:15 -0700, Nikolaus Rath wrote:
> 
> Is there anything I can do to help debug this issue?

You could try to bisect it, but judging from the problem description, 
that could be more like a career than a troubleshooting session.

        -Mike

Re: Help with debugging intermittent crash on resume from hibernation

[Nikolaus Rath]

On Apr 17 2015, Mike Galbraith <umgwanakikbuti@gmail.com> wrote:
> On Fri, 2015-04-17 at 20:15 -0700, Nikolaus Rath wrote:
>> 
>> Is there anything I can do to help debug this issue?
>
> You could try to bisect it, but judging from the problem description, 
> that could be more like a career than a troubleshooting session.

Furthermore, I have yet to find a kernel version that does *not* exhibit
the problem (I went back to 3.14).

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

Re: Help with debugging intermittent crash on resume from hibernation

[Mike Galbraith]

On Fri, 2015-04-17 at 21:13 -0700, Nikolaus Rath wrote:
> On Apr 17 2015, Mike Galbraith <umgwanakikbuti@gmail.com> wrote:
> > On Fri, 2015-04-17 at 20:15 -0700, Nikolaus Rath wrote:
> > > 
> > > Is there anything I can do to help debug this issue?
> > 
> > You could try to bisect it, but judging from the problem 
> > description, 
> > that could be more like a career than a troubleshooting session.
> 
> Furthermore, I have yet to find a kernel version that does *not* 
> exhibit
> the problem (I went back to 3.14).

My solution would be don't do that then.  Hibernation doesn't save 
much time anyway, so is worth zero annoyance.

I would like to be able to suspend, but went from GeForce 8600 GT in 
old box that suspended great, resumed not at all to GeForce GTX 980 in 
new box which suspends great and resumes not at all, and is supported 
by nothing that makes eyecandy, so I have roughly a zillion unused 
transistors.  The thing occupies nearly the same volume of space as my 
laptop... but lappy doesn't have sexy big green leds to remind me that 
it's a Satellite lest I forget :)

        -Mike