Bug 344197 – sys-kernel/tuxonice-sources-2.6.34-r6: Hibernation processes is repeated

• Status: RESOLVED NEEDINFO
• Product: Gentoo Linux

[Description svenvermant 2010-11-04 20:11:14 UTC]

Sometimes when I hibernate my notebook running tuxonice-sources-2.6.34-r6, the hibernation processes starts, the image is written to Swap. But when the system is assumed to switch off, a second hibernation process is started, i.e., memory is tried to be freed and then the image is written to swap again. Upon rebooting, the image is loaded, but when the system should come back to live, you just get a black screen (probably you end up where the first hibernation processes ended). The only thing that helps in this case is switching off the computer and rebooting, resulting in possible data loss

Reproducible: Sometimes

Steps to Reproduce:
1. Hibernate
Actual Results:  
The hibernation process is performed. At the end, the hibernation process starts again.

Expected Results:  
The computer should be turned off after the successful first hibernation process

This bug occurs very infrequently. I could not observe any reason for this behaviour, it seems to be rather random. So unfortunately, I am not able to reproduce it upon will.

[Comment 1 Krzysztof Pawlik (RETIRED) 2010-11-14 15:41:32 UTC]

Can you please test newer kernel, like tuxonice-sources-2.6.36 (or -r1)?

[Comment 2 svenvermant 2010-11-14 15:46:00 UTC]

I must admit that I feel uncomfortable about using an unstable kernel as I need the notebook for productive purposes.

[Comment 3 Krzysztof Pawlik (RETIRED) 2010-11-14 15:54:05 UTC]

I understand that you need your machine for work, nevertheless I recommend testing latest kernel, at least for few hours. For example on my laptop (Lenovo IdeaPad U350) 2.6.36 is the first kernel to sanely work (I mean that everything is supported as it should be, well.. except brightness setting).

Also: please note that 2.6.36 has been deemed stable enough to be released by upstream. Unstable kernels (or if you prefer, 'testing') are marked with -rcX.

[Comment 4 Marcin Rybarski 2010-11-25 08:52:20 UTC]

(In reply to comment #3)

> Also: please note that 2.6.36 has been deemed stable enough to be released by
> upstream. Unstable kernels (or if you prefer, 'testing') are marked with -rcX.
> 
I that case how to interpret infromation from syslog:

Nov 25 06:15:25 discovery kernel: [  827.945489] - TuxOnIce core  : 3.2-rc2
Nov 25 06:15:25 discovery kernel: [  827.945490] - Kernel Version : 2.6.36-tuxonice-r2

Or maybe 2.6.36 uses different Tuxonice core?

[Comment 5 Krzysztof Pawlik (RETIRED) 2010-12-03 07:27:18 UTC]

(In reply to comment #4)
> (In reply to comment #3)
> 
> > Also: please note that 2.6.36 has been deemed stable enough to be released by
> > upstream. Unstable kernels (or if you prefer, 'testing') are marked with -rcX.
> > 
> I that case how to interpret infromation from syslog:
> 
> Nov 25 06:15:25 discovery kernel: [  827.945489] - TuxOnIce core  : 3.2-rc2
> Nov 25 06:15:25 discovery kernel: [  827.945490] - Kernel Version :
> 2.6.36-tuxonice-r2
> 
> Or maybe 2.6.36 uses different Tuxonice core?

2.6.36 is stable, TOI patch is at 3.2-rc2, all I was saying was that 2.6.36 base kernel is stable, not TOI.

[Comment 6 Marcin Rybarski 2010-12-05 20:02:02 UTC]

Thanks for clarification. Anyway I have no problems with =sys-kernel/tuxonice-sources-2.6.36-r2. Maybe its worth to try?

[Comment 7 Krzysztof Pawlik (RETIRED) 2010-12-12 13:56:32 UTC]

[e-mail]: please reopen the bug if issues persist with newer kernels.