From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: nigel@suspend2.net
Cc: LKML <linux-kernel@vger.kernel.org>,
"suspend2-devel" <suspend2-devel@lists.suspend2.net>
Subject: Re: PID namespaces break initrd+hibernate combination?
Date: Mon, 5 Nov 2007 00:45:24 +0100 [thread overview]
Message-ID: <200711050045.24876.rjw@sisk.pl> (raw)
In-Reply-To: <200711050936.36615.nigel@nigel.suspend2.net>
On Sunday, 4 of November 2007, Nigel Cunningham wrote:
> Hi all.
>
> Please excuse me if this has already been answered. I'm not currently subscribed to LKML.
>
> I've just been preparing a new tux-on-ice release against Linus' current tree, and encountered a failure to freeze pid 1 when seeking to resume, using an initrd:
>
> [ 74.192734] Freezing of tasks failed after 19.99 seconds (1 tasks refusing to freeze):
> [ 74.193502] task PC stack pid father
> [ 74.193504] swapper S ffff810002023030 4968 1 0
> [ 74.193512] ffff81000203fdb0 0000000000000046 ffff810002023040 ffff810003249140
> [ 74.194296] ffff81000203fd80 ffffffff803150a1 ffff81000203fdb0 ffff810002023180
> [ 74.195087] ffff810002023030 0000000000000004 0000000000000001 0000000000000001
> [ 74.195860] Call Trace:
> [ 74.196123] [<ffffffff803150a1>] security_task_wait+0x11/0x20
> [ 74.196692] [<ffffffff802320cd>] do_wait+0x51d/0xda0
> [ 74.197187] [<ffffffff802292f0>] default_wake_function+0x0/0x10
> [ 74.197772] [<ffffffff8023297c>] sys_wait4+0x2c/0x30
> [ 74.198264] [<ffffffff805f4bb5>] initrd_load+0x175/0x370
> [ 74.198794] [<ffffffff805f211f>] prepare_namespace+0x8f/0x1d0
> [ 74.199362] [<ffffffff805f174d>] kernel_init+0x1ad/0x2b0
> [ 74.199889] [<ffffffff8047e526>] _spin_unlock_irq+0x26/0x60
> [ 74.200439] [<ffffffff8022afc7>] finish_task_switch+0x67/0xc0
> [ 74.201008] [<ffffffff8020c548>] child_rip+0xa/0x12
> [ 74.201494] [<ffffffff80364770>] acpi_os_acquire_lock+0x9/0xb
> [ 74.202063] [<ffffffff805f15a0>] kernel_init+0x0/0x2b0
> [ 74.202570] [<ffffffff8020c53e>] child_rip+0x0/0x12
>
> I believe it might be related to pid namespaces, but am not completely sure yet (will do a git bisect if needs be).
>
> So, then, I'm writing to ask: Is this a known issue? Is there any fix already available that I've not found in my googling?
Not known to me and I haven't tried the PID namespaces yet.
Greetings,
Rafael
next prev parent reply other threads:[~2007-11-04 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 22:36 PID namespaces break initrd+hibernate combination? Nigel Cunningham
2007-11-04 23:45 ` Rafael J. Wysocki [this message]
2007-11-06 3:25 ` Sukadev Bhattiprolu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200711050045.24876.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@suspend2.net \
--cc=suspend2-devel@lists.suspend2.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.