From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Pavel Machek <pavel@ucw.cz>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: swsusp does not stop DMA properly during resume
Date: Wed, 21 Jan 2004 10:40:38 +1100 [thread overview]
Message-ID: <1074642037.739.49.camel@gaston> (raw)
In-Reply-To: <20040120150629.6949eda7.akpm@osdl.org>
> I _think_ what this patch is doing is suspending all devices from within
> the boot kernel before starting into the resumed kernel. Is this correct?
>
> > + update_screen(fg_console); /* Hmm, is this the problem? */
>
> Cryptic comment. To what "problem" does this refer?
Note that you should make sure all calls to update_screen (among others)
are guarded by the console semaphore, with my VT patch, not doing so
will result in WARN_ON's
Ben.
next prev parent reply other threads:[~2004-01-20 23:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 22:46 swsusp does not stop DMA properly during resume Pavel Machek
2004-01-20 23:06 ` Andrew Morton
2004-01-20 23:08 ` Pavel Machek
2004-01-20 23:40 ` Benjamin Herrenschmidt [this message]
2004-01-20 23:53 ` Pavel Machek
2004-01-21 0:01 ` Andrew Morton
2004-01-21 0:05 ` Pavel Machek
2004-01-21 0:09 ` Benjamin Herrenschmidt
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=1074642037.739.49.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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