From: Andy Isaacson <adi@hexapodia.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Pavel Machek <pavel@ucw.cz>, Dave Jones <davej@codemonkey.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: swsusp 'disk' fails in bk-current - intel_agp at fault?
Date: Fri, 27 May 2005 10:44:58 -0700 [thread overview]
Message-ID: <20050527174458.GA28455@hexapodia.org> (raw)
In-Reply-To: <20050525171825.51a06908.akpm@osdl.org>
On Wed, May 25, 2005 at 05:18:25PM -0700, Andrew Morton wrote:
> Andy Isaacson <adi@hexapodia.org> wrote:
> > I was previously running 2.6.11-rc3 and swsusp was working quite nicely:
> > echo shutdown > /sys/power/disk
> > echo disk > /sys/power/state
> >
> > Now I've upgraded to 2.6.12-rc1, 423b66b6oJOGN68OhmSrBFxxLOtIEA, and it
> > no longer works reliably. Almost every time I do the above it blocks in
> > device_resume() (I haven't had time to track it deeper than that).
>
> Andy, can you please retest 2.6.12-rc5 and if these problems remain,
> generate new reports at bugme.osdl.org?
After two quick tests, it appears to be fixed in 2.6.12-rc5. Thanks for
the follow-up.
-andy
prev parent reply other threads:[~2005-05-27 17:45 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 18:49 swsusp 'disk' fails in bk-current - intel_agp at fault? Andy Isaacson
2005-03-24 14:27 ` Stefan Seyfried
2005-03-24 18:10 ` Andy Isaacson
2005-03-24 19:18 ` Dmitry Torokhov
2005-03-24 20:20 ` Andy Isaacson
2005-03-24 21:10 ` Dmitry Torokhov
2005-03-24 23:54 ` Andy Isaacson
2005-03-25 9:22 ` Stefan Seyfried
2005-03-25 10:13 ` Pavel Machek
2005-03-25 14:19 ` Dmitry Torokhov
2005-03-25 14:24 ` Pavel Machek
2005-03-25 14:52 ` Dmitry Torokhov
2005-03-25 15:42 ` Pavel Machek
2005-03-25 16:04 ` Dmitry Torokhov
2005-03-28 23:00 ` Pavel Machek
2005-03-29 23:19 ` Rafael J. Wysocki
2005-03-29 21:49 ` Rafael J. Wysocki
2005-03-25 18:36 ` Andy Isaacson
2005-03-29 16:18 ` Dmitry Torokhov
2005-03-29 18:18 ` Pavel Machek
2005-03-29 19:11 ` Dmitry Torokhov
2005-03-29 19:23 ` Pavel Machek
2005-03-29 20:05 ` Dmitry Torokhov
2005-03-29 20:52 ` Pavel Machek
2005-03-29 21:07 ` Dmitry Torokhov
2005-03-29 21:12 ` Pavel Machek
2005-03-29 21:33 ` Dmitry Torokhov
2005-03-29 21:44 ` Pavel Machek
2005-03-29 22:31 ` [linux-pm] " Nigel Cunningham
2005-03-29 22:35 ` Pavel Machek
2005-03-29 23:46 ` Nigel Cunningham
2005-03-31 7:26 ` Dmitry Torokhov
2005-03-31 8:39 ` Pavel Machek
2005-03-31 15:02 ` Dmitry Torokhov
2005-03-31 16:02 ` Patrick Mochel
2005-03-31 16:32 ` Dmitry Torokhov
2005-03-31 22:16 ` Nigel Cunningham
2005-03-31 22:18 ` Pavel Machek
2005-03-31 22:28 ` Nigel Cunningham
2005-04-01 8:49 ` Rafael J. Wysocki
2005-04-01 10:33 ` Stefan Seyfried
2005-03-29 23:05 ` Rafael J. Wysocki
2005-03-29 21:23 ` [linux-pm] " Patrick Mochel
2005-03-29 21:38 ` Dmitry Torokhov
2005-03-30 9:52 ` Greg KH
2005-03-25 14:58 ` Dmitry Torokhov
2005-03-30 7:26 ` Andy Isaacson
2005-03-24 21:14 ` Dmitry Torokhov
2005-03-24 20:38 ` Stefan Seyfried
2005-03-29 18:42 ` Dmitry Torokhov
2005-03-30 7:24 ` Andy Isaacson
[not found] ` <20050525171825.51a06908.akpm@osdl.org>
2005-05-27 17:44 ` Andy Isaacson [this message]
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=20050527174458.GA28455@hexapodia.org \
--to=adi@hexapodia.org \
--cc=akpm@osdl.org \
--cc=davej@codemonkey.org.uk \
--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