From: Pavel Machek <pavel@suse.cz>
To: Rob Landley <rob@landley.net>
Cc: mochel@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Patrick's Test9 suspend code.
Date: Thu, 13 Nov 2003 14:08:42 +0100 [thread overview]
Message-ID: <20031113130841.GC643@openzaurus.ucw.cz> (raw)
In-Reply-To: <200311090404.40327.rob@landley.net>
Hi!
> This brings us to 2B) Snapshotting is way too opaque. It sits there for 15
> seconds sometimes doing inscrutable things, with no progress indicator or
> anything, and then either suspends, panics, or fails and fires the desktop
> back up with no diagnostic message.
>
> On the whole, this is really really cool, and if you have any suggestions how
> I could help, I'm all ears. (I'm unlikely to poke into the code too
Try "my" swsusp code. It should not fail silently; it may
panic the box but at that point you at least have a message.
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
next prev parent reply other threads:[~2003-11-15 20:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-09 10:04 Patrick's Test9 suspend code Rob Landley
2003-11-13 13:08 ` Pavel Machek [this message]
2003-11-16 0:30 ` Rob Landley
2003-11-16 13:13 ` Pavel Machek
2003-11-17 2:38 ` Rob Landley
2003-11-17 8:42 ` Pavel Machek
2003-11-17 16:45 ` Patrick Mochel
2003-11-17 21:11 ` Rob Landley
2003-11-18 12:02 ` Rob Landley
2003-11-18 18:22 ` Pavel Machek
2003-11-18 22:12 ` Rob Landley
2003-11-18 23:21 ` Pavel Machek
2003-11-19 5:26 ` Rob Landley
2003-11-19 9:18 ` Pavel Machek
2003-11-19 9:41 ` Rob Landley
-- strict thread matches above, loose matches on Subject: below --
2003-11-19 13:15 Samium Gromoff
2003-11-19 19:06 ` Pavel Machek
2003-11-20 17:26 Shaheed
2003-11-20 19:39 ` Rob Landley
2003-11-20 22:33 ` Shaheed
2003-11-20 22:41 ` Nigel Cunningham
2003-11-20 23:02 ` Shaheed
2003-11-21 6:46 ` Rob Landley
2003-11-21 20:09 ` Nigel Cunningham
2003-11-21 0:06 ` 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=20031113130841.GC643@openzaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=rob@landley.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.