public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: "Bjørn Mork" <bmork@dod.no>
Cc: linux-kernel@vger.kernel.org, Pavel Machek <pavel@suse.cz>
Subject: Re: Resume from swsusp stopped working with 2.6.14 and 2.6.15-rc1
Date: Sat, 12 Nov 2005 10:23:22 -0500	[thread overview]
Message-ID: <200511121023.23245.dtor_core@ameritech.net> (raw)
In-Reply-To: <87zmoa0yv5.fsf@obelix.mork.no>

On Saturday 12 November 2005 08:39, Bjørn Mork wrote:
> I have had swsusp working for ages on a IBM Thinkpad T42, but since
> 2.6.14 it hasn't been willing to resume anymore.  Both suspending to
> disk and ACPI S3 still works. 
> 
> Output of dmesg below (running 2.6.15-rc1). Notice the line:
> 
>   Restarting tasks...<6> Strange, kseriod not stopped
> 
> I guess that's the explanation.  Could it be the new TrackPoint
> driver, maybe?  (This PC has both a TrackPoint and a Touchpad).
>

This is unlikely... serio has the proper support for freezing as
far as I understand:

static int serio_thread(void *nothing)
{
        do {
                serio_handle_events();
                wait_event_interruptible(serio_wait,
                        kthread_should_stop() || !list_empty(&serio_event_list));
                try_to_freeze();
        } while (!kthread_should_stop());

        printk(KERN_DEBUG "serio: kseriod exiting\n");
        return 0;
}

Pavel, any ideas?

-- 
Dmitry

  reply	other threads:[~2005-11-12 15:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-12 13:39 Resume from swsusp stopped working with 2.6.14 and 2.6.15-rc1 Bjørn Mork
2005-11-12 15:23 ` Dmitry Torokhov [this message]
2005-11-12 20:01   ` Pavel Machek
2005-11-12 20:39   ` Pavel Machek
2005-11-13  1:53     ` Dmitry Torokhov
2005-11-13 10:09       ` Bjørn Mork
2005-11-17 21:57 ` Dmitry Torokhov
2005-11-18  9:37   ` Bjørn Mork
2005-11-18 11:40   ` Pavel Machek
2005-11-18 11:49     ` Bjørn Mork
2005-11-18 18:31       ` Pavel Machek
2005-11-18 23:32         ` Dmitry Torokhov
2005-11-19 23:48           ` Pavel Machek
2005-11-22  5:26             ` Dmitry Torokhov
2005-11-22  8:57               ` Bjørn Mork
2005-11-22 17:46                 ` Pavel Machek
2005-11-22 18:41                   ` Bjørn Mork
2005-11-22 18:53                     ` Pavel Machek
2005-11-22 18:45                   ` Dmitry Torokhov
2005-11-22 18:59                     ` Pavel Machek
2005-11-22 19:08                       ` Dmitry Torokhov
2005-11-22 20:37                         ` Dmitry Torokhov
2005-11-22 18:47               ` Pavel Machek
2005-11-22 22:15                 ` Rafael J. Wysocki
2005-11-22 22:51                   ` Pavel Machek
2005-11-23 10:09                     ` Bjørn Mork
2005-11-23 12:01                       ` Pavel Machek
2005-11-23 13:14                         ` Bjørn Mork
2005-11-23 13:25                           ` Pavel Machek
2005-11-23 10:53                     ` Rafael J. Wysocki
2005-11-18 13:46   ` Bernd Donner
  -- strict thread matches above, loose matches on Subject: below --
2005-11-13  3:08 Bernd Donner
2005-11-13 12:13 ` Jacek Kawa

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=200511121023.23245.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=bmork@dod.no \
    --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