From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: pavel@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: swsusp console change/userspace hang
Date: Mon, 29 Aug 2005 10:50:31 +1000 [thread overview]
Message-ID: <1125276632.14185.74.camel@gaston> (raw)
In-Reply-To: <20050829002652.GA23582@srcf.ucam.org>
On Mon, 2005-08-29 at 01:26 +0100, Matthew Garrett wrote:
> Hi!
>
> I'm currently working on an entirely userspace bootsplash program. It
> works quite happily, except in the case of resuming from hibernation.
> The splash program is launched at the start of initramfs, and at the
> end of initramfs (after the disk modules have been loaded) we attempt to
> trigger resume from userspace.
>
> The code registers a signal that's fired on VT change. If a console
> change is requested when it's currently drawing, it disables drawing and
> schedules an alarm to fire 0.1 seconds later in order to avoid switching
> the console when part-way through a framebuffer operation.
>
> The problem seems to be that swsusp tries to change the console and then
> immediately freezes userspace. For reasons I don't entirely understand,
> this freezes the machine. If I remove the pm_prepare_console call from
> pm_prepare_processes, resume functions correctly.
Hrm.. it uses pm_prepare_console(), which should wait for the console to
become active... However, it calls vt_waitactive without dealing with
-EINTR. You might be getting a signal or something, can you check what's
going on inside pm_prepare_console ?
> For now I'll probably just work around this by removing the console
> change from our kernels (we can do that in userspace scripting instead),
> but this still seems to be a less than ideal situation - I'm guessing
> that the same would happen if we were displaying the splash on suspend.
> Any ideas what might be causing this, and how to rectify it?
prev parent reply other threads:[~2005-08-29 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 0:26 Matthew Garrett
2005-08-29 0:50 ` Benjamin Herrenschmidt [this message]
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=1125276632.14185.74.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pavel@ucw.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®