From: Ian Soboroff <ian.soboroff@nist.gov>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org, Patrick Mochel <mochel@osdl.org>
Subject: Re: APM suspend still broken in -test9
Date: Wed, 29 Oct 2003 08:43:37 -0500 [thread overview]
Message-ID: <9cf7k2o2m7q.fsf@rogue.ncsl.nist.gov> (raw)
In-Reply-To: <9cffzhezd9i.fsf@rogue.ncsl.nist.gov> (Ian Soboroff's message of "Mon, 27 Oct 2003 14:33:45 -0500")
Scratch that. I attempted to wake up the laptop yesterday after it
had been sleeping for several hours, and it was locked hard. My
success report was based on just a quick sleep of a minute or so.
The last -test kernel that works properly for APM suspend and resume
for me is -test7.
Ian
Ian Soboroff <ian.soboroff@nist.gov> writes:
> Yes, that patch solves it for me, and applies cleanly to -test9.
> Ian
>
> David Brownell <david-b@pacbell.net> writes:
>
>> Those are the same symptoms I saw in test7, fixed by:
>>
>> http://marc.theaimsgroup.com/?l=linux-kernel&m=106606272103414&w=2
>>
>> Patrick, were you going to submit your patch to resolve this?
>> I'm thinking this kind of problem would meet Linus's test10
>> integration criteria.
>>
>> (That's not an APM problem, it's a generic PM problem that'd
>> show up with swsusp too. And likely even some ACPI systems.)
>>
>> - Dave
next prev parent reply other threads:[~2003-10-29 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 18:24 David Brownell
2003-10-27 19:33 ` Ian Soboroff
2003-10-29 13:43 ` Ian Soboroff [this message]
2003-10-27 20:20 ` Patrick Mochel
2003-10-27 20:48 ` David Brownell
2003-10-27 20:53 ` Johannes Erdfelt
2003-10-27 21:19 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2003-10-23 20:54 2.6.0-test8 - APM suspend not working Ian Soboroff
2003-10-27 16:03 ` APM suspend still broken in -test9 Ian Soboroff
2003-10-27 23:56 ` bill davidsen
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=9cf7k2o2m7q.fsf@rogue.ncsl.nist.gov \
--to=ian.soboroff@nist.gov \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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
all inboxes | Powered by JetHome®