public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: dtor_core@ameritech.net
Cc: Bj?rn Mork <bmork@dod.no>, linux-kernel@vger.kernel.org
Subject: Re: Resume from swsusp stopped working with 2.6.14 and 2.6.15-rc1
Date: Fri, 18 Nov 2005 12:40:32 +0100	[thread overview]
Message-ID: <20051118114032.GD15825@elf.ucw.cz> (raw)
In-Reply-To: <d120d5000511171357g4d7a8d54hcc1c1d1cffa8856e@mail.gmail.com>

Hi!

> > IPv6 over IPv4 tunneling driver
> > NET: Registered protocol family 17
> > Using IPI Shortcut mode
> > Stopping tasks: ===<6>Synaptics Touchpad, model: 1, fw: 5.9, id: 0x2c6ab1, caps: 0x884793/0x0
> > serio: Synaptics pass-through port at isa0060/serio1/input0
> > input: SynPS/2 Synaptics TouchPad as /class/input/input1
> >
> >  stopping tasks failed (1 tasks remaining)
> > Restarting tasks...<6> Strange, kseriod not stopped
> >  done
> 
> Crazy idea - did you let it finish booting or you hit suspend as soon
> as you could? It looks like kseriod was busy discovering your
> touchpad/trackpoint for the first time...
> 
> Anyway, Pavel, I think 6 seconds it too short of a timeout for
> stopping all tasks. PS/2 is pretty slow, trackpad reset can take up to
> 2 seconds alone...
> 
> Bjorn, does it help if you change TIMEOUT in kernel/power/process.c to 30 * HZ?

Funny, I thought that 6 seconds is way too much. Bjorn, please let us
know if 30 seconds timeout helps.
								Pavel
-- 
Thanks, Sharp!

  parent reply	other threads:[~2005-11-18 11:40 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
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 [this message]
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=20051118114032.GD15825@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=bmork@dod.no \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    /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