mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: Maximilian Engelhardt <maxi@daemonizer.de>,
	Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: software suspend doesn't work with 2.6.22-rc3
Date: Sat, 26 May 2007 19:53:53 +1000	[thread overview]
Message-ID: <1180173233.9773.79.camel@nigel.suspend2.net> (raw)
In-Reply-To: <200705261128.57332.maxi@daemonizer.de>

[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]

Hi.

On Sat, 2007-05-26 at 11:28 +0200, Maximilian Engelhardt wrote:
> Hello,
> 
> When I try software suspend on my laptop it always returns to my running 
> system after some time.
> This is what's logged by the kernel:
> 
> swsusp: Basic memory bitmaps created
> Stopping tasks ... 
> Stopping kernel threads timed out after 20 seconds (1 tasks refusing to 
> freeze):
>  cryptd
> Restarting tasks ... done.
> swsusp: Basic memory bitmaps freed
> 
> I have no idea what's the problem, but if you tell me what I should do I can 
> create debugging information and/or test patches.

Could you try this patch, please? It should help.

Herbert, is this right? If cryptd is going to be used for block devs,
the task should probably be PF_NOFREEZE (or whatever it is today)
instead.

Regards,

Nigel

 crypto/cryptd.c         |    1 +
 include/linux/freezer.h |    3 +++
 kernel/power/process.c  |    2 +-
 3 files changed, 5 insertions(+), 1 deletion(-)
diff -ruNp 991-fix-cryptd.patch-old/crypto/cryptd.c 991-fix-cryptd.patch-new/crypto/cryptd.c
--- 991-fix-cryptd.patch-old/crypto/cryptd.c	2007-05-19 18:16:47.000000000 +1000
+++ 991-fix-cryptd.patch-new/crypto/cryptd.c	2007-05-26 19:45:42.000000000 +1000
@@ -341,6 +341,7 @@ static int cryptd_thread(void *data)
 
 		mutex_unlock(&state->mutex);
 
+		try_to_freeze();
 		schedule();
 	} while (!stop);
 


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-05-26  9:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26  9:28 Maximilian Engelhardt
2007-05-26  9:53 ` Nigel Cunningham [this message]
2007-05-26 11:08   ` Herbert Xu
2007-05-26 11:14     ` Nigel Cunningham
2007-05-26 11:55       ` Herbert Xu
2007-05-26 20:23         ` Rafael J. Wysocki
2007-05-26 12:49   ` Maximilian Engelhardt
2007-05-26 20:20     ` Rafael J. Wysocki
2007-05-26 21:33     ` Nigel Cunningham
2007-05-27 16:01       ` Maximilian Engelhardt
2007-05-27 18:19         ` Rafael J. Wysocki
2007-05-27 20:41           ` Maximilian Engelhardt
2007-05-27 21:27             ` Rafael J. Wysocki
2007-05-28  0:21               ` Maximilian Engelhardt
2007-05-28  7:59                 ` Rafael J. Wysocki
2007-05-28 18:21                   ` Rafael J. Wysocki
2007-05-28 21:02                     ` Maximilian Engelhardt
2007-05-29  0:39                     ` Herbert Xu
2007-05-29 12:01                       ` Rafael J. Wysocki
2007-05-31  6:54                       ` Rafael J. Wysocki
2007-05-31  7:04                         ` Rafael J. Wysocki
2007-05-31  7:13                           ` Rafael J. Wysocki
2007-05-31  8:08                             ` Herbert Xu
2007-05-27 20:35 ` Pavel Machek

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=1180173233.9773.79.camel@nigel.suspend2.net \
    --to=nigel@nigel.suspend2.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxi@daemonizer.de \
    /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®