All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	"Brian J. Murrell" <brian@interlinx.bc.ca>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: suspend/resume fails on second attempt in LNXVIDEO:00
Date: Thu, 18 Dec 2008 00:11:06 -0800	[thread overview]
Message-ID: <494A059A.8050602@gmail.com> (raw)
In-Reply-To: <20081218075226.GD2110@ucw.cz>

Pavel Machek wrote:
> On Tue 2008-12-16 20:53:35, Matthew Garrett wrote:
>   
>> On Tue, Dec 16, 2008 at 06:07:15PM +0000, Brian J. Murrell wrote:
>>     
>>> On Tue, 16 Dec 2008 16:37:46 +0000, Matthew Garrett wrote:
>>>       
>>>> I seem to be missing the original message, but: no, s2ram doesn't exist
>>>> in Ubuntu because pm-utils handles that role.
>>>>         
>>> Well, that's *their* argument but lots of people think otherwise.  There 
>>> appears to be no shortage of people for whom pm-utils does NOT work yet 
>>> s2ram does.  https://bugs.launchpad.net/ubuntu/+source/uswsusp/+bug/134238
>>>       
>> The right answer to "This piece of software contains bugs" is not 
>> "Provide two pieces of software with the same features but different 
>> bugs". The only real functional difference between the two is that
>>     
>
> Yes, and that's why pm-utils should die: they have design problems
> (depend on hal, can't be pagelocked, unusable for suspend debugging).
> 									Pavel
>   
When using ubuntu intrepid, s2ram
did work, but instead of grabbing
the package from ubuntu, I used Debian
SID instead. (I have a tendency of mixing
packages);

regards;

Justin P. Mattock



  reply	other threads:[~2008-12-18  8:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-14  5:06 suspend/resume fails on second attempt in LNXVIDEO:00 Brian J. Murrell
2008-12-14  6:43 ` Justin P. Mattock
2008-12-14 20:55   ` Brian J. Murrell
2008-12-14 22:29     ` Justin P. Mattock
2008-12-15 15:56 ` Pavel Machek
2008-12-15 17:00   ` Brian J. Murrell
2008-12-15 17:33     ` Alexey Starikovskiy
2008-12-15 17:56       ` Brian J. Murrell
2008-12-15 20:19         ` Rafael J. Wysocki
2008-12-15 20:52           ` Brian J. Murrell
2008-12-15 23:02             ` Rafael J. Wysocki
2008-12-16  2:34               ` Brian J. Murrell
2008-12-16 15:25                 ` Rafael J. Wysocki
2008-12-16 16:02                   ` Brian J. Murrell
2008-12-16 16:13                     ` Rafael J. Wysocki
2008-12-16 16:18                       ` Brian J. Murrell
2008-12-16 16:22                         ` Rafael J. Wysocki
2008-12-16 23:54                           ` Brian J. Murrell
2008-12-16 16:37                       ` Matthew Garrett
2008-12-16 18:07                         ` Brian J. Murrell
2008-12-16 20:53                           ` Matthew Garrett
2008-12-18  7:52                             ` Pavel Machek
2008-12-18  8:11                               ` Justin P. Mattock [this message]
2008-12-18  4:24               ` Brian J. Murrell
2008-12-18 23:57                 ` Brian J. Murrell
2008-12-19 17:33                   ` Rafael J. Wysocki
2008-12-19 21:10                     ` Brian J. Murrell
2008-12-20 17:43     ` Sergio Monteiro Basto
2008-12-20 21:08       ` Brian J. Murrell
2008-12-14  9:16 Robby Workman
2008-12-14 14:08 ` Brian J. Murrell
2008-12-14 15:35   ` Justin P. Mattock
2008-12-14 17:06     ` Brian J. Murrell

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=494A059A.8050602@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=brian@interlinx.bc.ca \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=pavel@suse.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 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.