From: Pavel Machek <pavel@suse.cz>
To: dtor_core@ameritech.net
Cc: Pavel Machek <pavel@ucw.cz>, Bj?rn Mork <bjorn@mork.no>,
linux-kernel@vger.kernel.org
Subject: Re: Resume from swsusp stopped working with 2.6.14 and 2.6.15-rc1
Date: Sat, 19 Nov 2005 23:48:50 +0000 [thread overview]
Message-ID: <20051119234850.GC1952@spitz.ucw.cz> (raw)
In-Reply-To: <d120d5000511181532g69107c76x56a269425056a700@mail.gmail.com>
Hi!
> > > >> 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.
> > >
> > > It does.
> >
> > Ouch, yes, that's clear. It is stopping tasks during *resume*... So I
> > guess it gets wrong timing by design. Question is what to do with
> > that. Could we make keyboard driver pause the boot until it is done
> > resetting hardware? Or we can increase the timeout... would 10 seconds
> > be enough?
>
> Well, I think 10 seconds when suspending is a nice and resonable
> number. For resume though I think we should wait much longer, maybe
> even indefinitely - the only thing that timeout achieves is makes
> people fsck because the system can't recover from that state.
I see your point, but it does not seem we need that changes this far. Your
patch is better, because we *could* hit that during suspend, just after
keyboard hotplug... right? And it will make resume faster for affected people.
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2005-11-20 21:22 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
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 [this message]
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=20051119234850.GC1952@spitz.ucw.cz \
--to=pavel@suse.cz \
--cc=bjorn@mork.no \
--cc=dtor_core@ameritech.net \
--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