Re: 2.6.24-rc2 STD with s2disk fails to activate suspended system after loading

Rafael J. Wysocki
2007-11-11T18:29:17Z

On Saturday, 10 of November 2007, Chris Friedhoff wrote:
> please cc me, I'm not not subscribed to LKML
>
> Hello,
>
> with kernel 2.6.24-rc2 STD with s2disk suspends the system to disk, but
> when I start the system and the suspended systemimage is loaded, it
> fails to "activate" this suspended systemimage and continues after some
> time with following the normal boot sequence.
>
> I can sucessfully STD the system with the following sequence
> echo platform > /sys/power/disk
> echo disk > /sys/power/state
> and when I start the laptop the suspended system is sucessfully
> restored.
>
> Both behaviors are reliable reproducable.

Thanks for the report.

> googling for >"Freezing of tasks failed" swapper< brought
> "Nigel Cunningham - PID namespaces break initrd+hibernate combination?"
> http://lkml.org/lkml/2007/11/4/140

Yes, this looks similarly.

> dmesg output:
> <<snip>>
> RAMDISK: ext2 filesystem found at block 0
> RAMDISK: Loading 2000KiB [1 disk] into ram disk... done.
> EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
> VFS: Mounted root (ext2 filesystem).
> swsusp: Marking nosave pages: 000000000009f000 - 0000000000100000
> swsusp: Basic memory bitmaps created
> Clocksource tsc unstable (delta = -128791628 ns)
> Syncing filesystems ... done.
> Freezing user space processes ... (elapsed 0.00 seconds) done.
> Freezing remaining freezable tasks ...
> Freezing of tasks failed after 20.00 seconds (1 tasks refusing to
> freeze): task PC stack pid father
> swapper S c1835a88 0 1 0
> 00000000 00000046 c0118c80 c1835a88 00000004 00000001 c011e875
> 00000286 c01025a6 00000000 00000000 c1835b64 00000000 ffffffff c1835a90
> 00000001 00000000 00000000 00000000 00000000 0000007b 00000000 c1835a90
> c0118c80 Call Trace:
> [<c0118c80>] default_wake_function+0x0/0x10
> [<c011e875>] do_wait+0x335/0xac0
> [<c01025a6>] kernel_thread+0x96/0xb0
> [<c0118c80>] default_wake_function+0x0/0x10
> [<c011f031>] sys_wait4+0x31/0x40
> [<c04b7a23>] initrd_load+0x1b3/0x3a0
> [<c04b5108>] prepare_namespace+0x98/0x1b0
> [<c016090f>] sys_access+0x1f/0x30
> [<c04b47c6>] kernel_init+0x166/0x260
> [<c0103f4a>] ret_from_fork+0x6/0x1c
> [<c04b4660>] kernel_init+0x0/0x260
> [<c04b4660>] kernel_init+0x0/0x260
> [<c0104b8f>] kernel_thread_helper+0x7/0x18
> =======================
> kthreadd S 0000038f 0 2 0
> 00000000 00000046 c0487790 0000038f c183ff1c 00000000 c012d81b
> c012d7b0 00000000 00000000 c0104b8f 00000000 00000000 00000000 00000000
> 00000000 00000000
> Call Trace:
> [<c012d81b>] kthreadd+0x6b/0xd0
> [<c012d7b0>] kthreadd+0x0/0xd0
> [<c0104b8f>] kernel_thread_helper+0x7/0x18
> =======================
> ksoftirqd/0 S 00000000 0 3 2
> 00000000 00000046 fffffffc 00000000 c0120f00 00000000 c0120f7a
> c012d782 c012d740 00000000 00000000 c0104b8f c183ff3c 00000000 00000000
> 00000000 00000000 00000000
> Call Trace:
> [<c0120f00>] ksoftirqd+0x0/0x80
> [<c0120f7a>] ksoftirqd+0x7a/0x80
> [<c012d782>] kthread+0x42/0x70
> [<c012d740>] kthread+0x0/0x70
> [<c0104b8f>] kernel_thread_helper+0x7/0x18
>
> <<snip>>

Can you please attach your kernel configuration file to the bugzilla entry
at http://bugzilla.kernel.org/show_bug.cgi?id=9345 ?

Thanks,
Rafael