gmane.linux.swsusp.devel

Re: Freeing memory

Milan Oravec — 2012-05-21T07:47:48

Hi Nigel, Harald. I'm suffering memory freeing problems/ hibernation 
freezing from 3.3 version. 32 bit /64 bit doesn't matters - tested. One 
machine on 3.2.12 is working fine for 47 days by now. Another with 3.2 tree:

09:45:30 up 68 days, 20:34, 15 users,  load average: 0.18, 0.21, 0.31

TuxOnIce debugging info:
- TuxOnIce core  : 3.2.1
- Kernel Version : 3.2.10-05355-gf5dcb59
- Compiler vers. : 4.4
- Attempt number : 51
- Parameters     : 0 667648 0 0 -2 5
- Overall expected compression percentage: 0.
- Compressor is 'lzo'.
   Compressed 2247098368 bytes into 688314679 (69 percent compression).
- Block I/O active.
   Used 170584 pages from swap on /dev/sda3.
- Max outstanding reads 2901. Max writes 1837.
   Memory_needed: 1024 x (4096 + 368 + 112) = 4685824 bytes.
   Free mem throttle point reached 0.
- Swap Allocator enabled.
   Swap available for image: 753568 pages.
- I/O speed: Write 213 MB/s, Read 280 MB/s.
- Extra pages    : 50 used/2000.
- Result         : Succeeded.

It causes some commit in 3.3

Freeing memory

Harald Judt — 2012-05-21T06:46:53

Hi Nigel,

I've updated to current git in the hope the memory freeing problems 
would be solved. Unfortunately, they are still there and I've been 
trying to narrow the issue down. Actually, there are two issues:

First, the memory eating process seems to lock up the machine when it 
requests too much memory. Commmit 
f8262d476823a7ea1eb497ff9676d1eab2393c75 "PM / Hibernate: fix the number 
of pages used for hibernate/thaw buffering" doesn't help with that. 
Maybe tuxonice needs to play catch up on that? Using smaller values and 
more tries seems to help with the freezes, but I don't know what a safe 
value would be.

Next, there seems to be a limit to what amount of the pagecache is 
freeable using the tuxonice memory eater method. Having a total of 16 
GiB, I increased the max tries and set a limit of max 4096MiB to free 
per try so that it would not freeze, but the memory eater hit some limit 
(at that time 4973MiB) where it could not free more memory. Dropping the 
caches manually via "echo 1 > /proc/sys

BUG() during restore

Antonio Quartulli — 2012-05-01T09:16:18

Hello,

I'm using pf-sources-3.3.3 (vanilla patched with last toi I think..) and during
resume I'm getting a lot of

[  512.314188] BUG: using smp_processor_id() in preemptible [00000000] code:
ktoi_io/2/4196
[  512.314209] caller is worker_rw_loop+0x408/0xbe0
[  512.314212] Pid: 4196, comm: ktoi_io/2 Tainted: G        W    3.3.3-pf #4
[  512.314215] Call Trace:
[  512.314221]  [<ffffffff811f8978>] ? debug_smp_processor_id+0xd8/0xf0
[  512.314224]  [<ffffffff8105ed68>] ? worker_rw_loop+0x408/0xbe0
[  512.314228]  [<ffffffff8104d390>] ? add_wait_queue+0x60/0x60
[  512.314230]  [<ffffffff8105e960>] ? attempt_to_parse_resume_device2+0x20/0x20
[  512.314234]  [<ffffffff8104ca25>] ? kthread+0x85/0x90
[  512.314239]  [<ffffffff81488f94>] ? kernel_thread_helper+0x4/0x10
[  512.314242]  [<ffffffff8104c9a0>] ? kthread_freezable_should_stop+0x60/0x60
[  512.314245]  [<ffffffff81488f90>] ? gs_change+0xb/0xb

I tried to change one onvocation of smp_processor_id() in worker_rw_loop() to
get_cpu() but the result is the sa

Unable to free memory with current tuxonice-git

Harald Judt — 2012-04-26T09:06:44

Hi,

Actually the following error has already been there since >3.2-rc7, but 
until now I simply worked around it using echo 1 > /proc/sys/vm/drop_caches.

In short, tuxonice can't free enough memory:

TuxOnIce 3.2.1, with support for usm, compression, block i/o, swap 
storage, userui.
Initiating a hibernation cycle.
Using configuration file /etc/splash/tuxonice/1920x1080.cfg.
No silent picture specified in the theme config.
Framebuffer support initialised successfully.
Starting other threads.Freezing user space processes ... (elapsed 0.01 
seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Restarting kernel threads ... done.
Asked shrink_all_memory for 2028770 low pages & 610379 pages from 
anywhere, got 0.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Restarting kernel threads ... done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Restarting kernel threads ... done.
Asked shrink_all_memory for 2013849 low pages & 595383 pages from

Re: BFS vs Tuxonice issue

Nigel Cunningham — 2012-04-23T22:18:13

Hi.

On 24/04/12 04:08, Harald Judt wrote:
I got some debugging done, managing to confirm that it's definitely 
something going wrong when the image is written (I can enable 
multithreaded I/O for reading only and resume successfully). I also 
confirmed that there's no problem in the compressing itself (even 
running multithreaded, I can compress a page and decompress the result 
straight away without a problem). So I'm almost certain it's something 
in the paths used to coalesce the compressed pages and write them to 
disk. The hard part is figuring out what, especially when there's a 
mutex and a spinlock protecting the two parts of the code path that 
would be most likely to cause the problem!

I'll keep looking.

Nigel

BFS vs Tuxonice issue

Harald Judt — 2012-04-23T18:08:21

Hi Nigel,

Did you have time to look into the BFS compatibility issue when 
multi-threaded compression is enabled?

With the current tuxonice 3.2.1 linux-3.3.2 from git I get the following 
error now (it's the same message repeated many many many times):

BUG: scheduling while atomic: BFS/2/0/0x00000002
Modules linked in: tun ehci_hcd w83627ehf hwmon_vid coretemp ipt_REJECT 
ipt_LOG xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack 
xt_multiport ipv6 iptable_filter ip_tables x_tables vboxdrv(O) loop 
joydev gspca_pac207 gspca_main videodev v4l2_compat_ioctl32 usbhid 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_emu10k1 
snd_hwdep snd_util_mem snd_ac97_codec ac97_bus snd_rawmidi 
snd_seq_device snd_hda_codec sr_mod xhci_hcd usbcore 8250_pnp 8250 
serial_core emu10k1_gp gameport snd_pcm processor snd_page_alloc 
snd_timer snd soundcore usb_common i2c_i801 thermal_sys button [last 
unloaded: ehci_hcd]
Pid: 0, comm: BFS/2 Tainted: G      D    O 3.3.2+ #24
Call Trace:
  [<ffffffff813f

Cannot hibernate using tuxonice

Niren Sinha — 2012-04-20T11:28:57

Hi,

I have been trying to hibernate my desktop (AMD, Ubuntu 11.10, Nvidia
Graphic Drivers) and so far I am not able o successfully do it. Ubuntu
kernel was always a problem, but in earlier tuxonice use to work perfectly
alright. Every since I upgrade to 11.10, I can't hibernate using TOI.

Please help me in debugging this issue. Attached are the files.

Thanks,
Niren Sinha | nirensinha< at >gmail.com
_______________________________________________
TuxOnIce-devel mailing list
TuxOnIce-devel< at >lists.tuxonice.net
http://lists.tuxonice.net/listinfo/tuxonice-devel

Re: userspace ui doesn't work with latesttuxonice-head

François Valenduc — 2012-04-17T15:40:58

Le 17/04/12 13:29, Nigel Cunningham a écrit :
I don't pretend this patch is perfect as my ability to write C code is
extremely limited. So, you probably need to correct it. In fact I merge
the mainline kernel in my local copy of your tuxonice-head branch and I
did the same in my tuxonice version where I resolved the merge conflicts
in an other way. Then I did a "git-diff" between the two branches and
the patch is more or less the result of that. It also showed some
differences in tuxonice_atomic_copy.c that I removed as it seems it was
unrelated to the userui problem. But as already said, my changes prevent
tuxonice from being compiled as a module and I get this error:

ERROR: "__usermodehelper_disable" [kernel/power/tuxonice_core.ko] undefined!
ERROR: "__usermodehelper_set_disable_depth"
[kernel/power/tuxonice_core.ko] undefined!
make[1]: *** [__modpost] Erreur 1

Thanks,

François
_______________________________________________
TuxOnIce-devel mailing list
TuxOnIce-devel< at >lists.tuxonice.net
http://lists.tu

Re: userspace ui doesn't work with latesttuxonice-head

François Valenduc — 2012-04-17T11:16:55

Le 16/04/12 15:35, Andrey Rahmatullin a écrit :
I encounter this problem everytime with the latest tuxonice-head git
tree. The attached patch I made to solve the merge conflicts before
3.4-rc1 allows userspace ui to work correctly. However, with this,
TuxOnIce can't be compiled as a module.

Thanks for your help.
François
diff --git a/kernel/power/tuxonice.h b/kernel/power/tuxonice.h
index accce22..e2064cb 100644
--- a/kernel/power/tuxonice.h
+++ b/kernel/power/tuxonice.h
< at >< at > -217,7 +217,7 < at >< at > extern void toi_early_boot_message(int can_erase_image, int default_answer,
 extern int do_check_can_resume(void);
 extern int do_toi_step(int step);
 extern int toi_launch_userspace_program(char *command, int channel_no,
-int debug);
+int wait, int debug);
 
 extern char tuxonice_signature[9];
 
diff --git a/kernel/power/tuxonice_highlevel.c b/kernel/power/tuxonice_highlevel.c
index c928e37..49da167 100644
--- a/kernel/power/tuxonice_highlevel.c
+++ b/kernel/power/tuxonice_highlevel.c
< at >< at > -135,7 +135,7 < at >< at > static ch

Re: TOI fails with 3.3

Lamarque V. Souza — 2012-04-16T13:49:55

Em Monday 16 April 2012, Lamarque V. Souza escreveu:

The bluetooth problem seems to be this one:

http://www.spinics.net/lists/linux-bluetooth/msg23278.html

There is a simple patch in that thread. I will test it and report if it 
solves the problem.

Re: userspace ui doesn't work with latest tuxonice-head

Andrey Rahmatullin — 2012-04-16T13:35:58

I've had this just once on 3.3rc7. It didn't happen before or after that.

Re: TOI fails with 3.3

Lamarque V. Souza — 2012-04-16T12:41:02

Em Friday 06 April 2012, Milan Oravec escreveu:

A couple of days ago I switched from 3.2.9 to 3.3.2 and TOI works here 
but my bluetooth controller does not work after resuming from disk. By what I 
can see in dmesg there is an error when suspending the bluetooth driver and 
that blocks the driver. I need to reboot to get bluetooth working again.

Re: userspace ui doesn't work with latesttuxonice-head

François Valenduc — 2012-04-13T18:59:48

Le 08/04/12 12:05, François Valenduc a écrit :
Any ideas on this problem ?
Thanks in advance,

François Valenduc

ifdefs fixes for TOI

Oleksandr Natalenko — 2012-04-12T19:28:31

Hi. Nigel.

The following changes since commit ce3052791e80fd1cab87da52dd6e4d675b33ede5:

  add ifdefs to handle CONFIG_FREEZER properly (2012-04-12 22:14:42 +0300)

are available in the git repository at:

  git://github.com/pfactum/pf-kernel.git toi-fixes-for-3.3-1

for you to fetch changes up to ce3052791e80fd1cab87da52dd6e4d675b33ede5:

  add ifdefs to handle CONFIG_FREEZER properly (2012-04-12 22:14:42 +0300)

Regards,
  post-factum

_______________________________________________
TuxOnIce-devel mailing list
TuxOnIce-devel< at >lists.tuxonice.net
http://lists.tuxonice.net/listinfo/tuxonice-devel

userspace ui doesn't work with latest tuxonice-head

François Valenduc — 2012-04-08T10:05:40

Hello everybody,

I have tried the latest tuxonice-head git tree and I notice that the
userspace interface doesn't work. I get this message in the logs:
 pc-francois kernel: [   48.132314] userspace ui: Failed to contact
userspace process.
I don't encounter this problem with tuxonice on the 3.3 kernel.

Does anybody knows what's happening ?
Thanks in advance for your help.

Re: TOI fails with 3.3

Nigel Cunningham — 2012-04-06T20:28:01

Hi.

I'll look into it.

Nigel

On 07/04/12 02:59, Oleksandr Natalenko wrote:

_______________________________________________
TuxOnIce-devel mailing list
TuxOnIce-devel< at >lists.tuxonice.net
http://lists.tuxonice.net/listinfo/tuxonice-devel

Re: TOI fails with 3.3

Oleksandr Natalenko — 2012-04-06T16:59:34

Vanilla works pretty good. The issue appears with TOI.

06.04.12 17:14, Dmitry Nezhevenko написав(ла):

_______________________________________________
TuxOnIce-devel mailing list
TuxOnIce-devel< at >lists.tuxonice.net
http://lists.tuxonice.net/listinfo/tuxonice-devel

Re: TOI fails with 3.3

Milan Oravec — 2012-04-06T14:22:15

Hi, yes, 3.3 tree is practically unusable here too. Patching to 3.3.1 
doesn't help.


Milan


On 04/06/2012 02:27 PM, Oleksandr Natalenko wrote:

Re: TOI fails with 3.3

Dmitry Nezhevenko — 2012-04-06T14:14:34

Try original kernel from kernel.org with in-kernel hibernation. If it
panics too, report to https://bugzilla.kernel.org/

TOI fails with 3.3

Oleksandr Natalenko — 2012-04-06T12:27:31

Hi!

I've experienced bunch of problems with TOI branch for Linux 3.3. First,
kernel oopsed on b43 driver during hibernation, then I repeated
hibernation and got kernel panic. Third try was broken because TOI
didn't find storage…

Are those problem well-known? What should I try to report about first?

Regards,
  post-factum

_______________________________________________
TuxOnIce-devel mailing list
TuxOnIce-devel< at >lists.tuxonice.net
http://lists.tuxonice.net/listinfo/tuxonice-devel

Re: Cpu hotplugging problem 3.3 kernel

Milan Oravec — 2012-03-23T22:05:06

Hi, interesting is thing, that after closing some programs (firefox, 
thunderbird) hibernation cycle was successful (dmesg attached). It is 
memory related as my previous problems with 3.3 tree. This is on my 3th 
laptop. I'm attaching my .config.

Any ideas?

Best wishes,

Milan

TuxOnIce debugging info:
- TuxOnIce core  : 3.2.1
- Kernel Version : 3.3.0-06305-gb13601d
- Compiler vers. : 4.6
- Attempt number : 6
- Parameters     : 524289 667648 0 0 -2 5
- Overall expected compression percentage: 0.
- Compressor is 'lzo'.
- Block I/O active.
   Used 0 pages from swap on /dev/sda1.
- Max outstanding reads 1. Max writes 0.
   Memory_needed: 1024 x (4096 + 368 + 112) = 4685824 bytes.
   Free mem throttle point reached 0.
- Swap Allocator enabled.
   Swap available for image: 1454192 pages.
- No I/O speed stats available.
- Extra pages    : 0 used/2000.
- Result         : Hibernation was aborted.
                  : CPU Hotplugging failed.
EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro,commit=0
EXT4-fs (sda4