public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Pavel Machek <pavel@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: swsusp not able to stop tasks
Date: Wed, 02 Nov 2005 16:29:32 +0100	[thread overview]
Message-ID: <4368DB5C.7070609@drzeus.cx> (raw)
In-Reply-To: <20051102133825.GG30194@elf.ucw.cz>

Pavel Machek wrote:
> Hi!
>
>   
>> I'm having problem with swsusp in the recent kernels (somewhere around 
>> the late 2.6.14 rc:s). It says it cannot suspend all tasks:
>>     
>
>   
>> [ 7223.525225] Stopping tasks: 
>> =======================================================================================================================================
>> [ 7229.532506]  stopping tasks failed (1 tasks remaining)
>> [ 7229.532529] Restarting tasks...<6> Strange, kauditd not stopped
>>     
>
> What is this kauditd? Try turning auditing off in kernel config, and
> it should go away. If it does, add try_to_freeze() at place where
> sleep is possible into kauditd...
>
>   

That it did. And the machine suspends fine with audit removed. I'll have 
a look at inserting those try_to_freeze().

>> Some late addition (post 2.6.14) also makes my keyboard crap out after 
>> one of these cycles. Not sure it the TSC funkiness was present
>> before this.
>>     
>
> Is that reproducible?
> 								Pavel
>   

Somewhat. My short test now seems to indicate that it happens about 50% 
of the time.

Rgds
Pierre

  reply	other threads:[~2005-11-02 15:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02 13:22 swsusp not able to stop tasks Pierre Ossman
2005-11-02 13:38 ` Pavel Machek
2005-11-02 15:29   ` Pierre Ossman [this message]
2005-11-02 21:03     ` Pavel Machek
2005-11-03  8:47       ` Pierre Ossman
2005-11-06 21:34         ` 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=4368DB5C.7070609@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.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