mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: suspend/resume fails on second attempt in LNXVIDEO:00
Date: Sun, 14 Dec 2008 07:35:21 -0800	[thread overview]
Message-ID: <9695C60B-CC91-41B3-87BB-D687E764BE30@gmail.com> (raw)
In-Reply-To: <1229263715.330.29.camel@pc.interlinx.bc.ca>

Is there quite possibly another
Graphics module you can plug-in,
Just to see

justin P. Mattock



On Dec 14, 2008, at 6:08 AM, "Brian J. Murrell"  
<brian@interlinx.bc.ca> wrote:

> On Sun, 2008-12-14 at 03:16 -0600, Robby Workman wrote:
>> In linux.kernel, Brian J. Murrell wrote:
>>> I'm trying to debug a resume problem on a compaq presario C700  
>>> laptop
>>> on the Ubuntu 2.6.24-22-generic kernel.
>>>
>>> SNIPPED
>>>
>>> These symptoms mirror a lot of other reports with this machine in  
>>> that
>>> the first suspend/resume cycle works but a second attempts
>>> (apparently) suspends fine but fails on resume.  The backlight on  
>>> the
>>> video does not come back and neither does the wireless connection,  
>>> so
>>> I'm not positive the problems are purely video related.
>>>
>>> How can I proceed from here to further debug what kind of  
>>> workarounds
>>> or solutions I might be able to use to get reliable suspend/resume
>>> functionality?
>>
>>
>> Assuming Ubuntu uses pm-utils for suspend/hibernate operations,  
>> then I
>> suspect you're needing this patch - the symptoms fit (suspend works
>> the first time, but fails thereafter), especially if a reboot causes
>> suspend to work fine again the first time...
>>
>> http://cgit.freedesktop.org/pm-utils/commit/?id=6c9f2959a36e608e4d1f71230a9eaaa77940c54e
>
> I wish (and was hoping) it was that simple.  The problem is the nature
> of that patch really has no effect on my system because $acpi_flag  
> == 0
> when the sysctl on line 147 is applied.  Presumably this patch has  
> more
> effect if $acpi_flag != 0, by nature of either $QUIRK_S3_BIOS or
> $QUIRK_S3_MODE being == true, neither of which is in my case.  Maybe  
> one
> or both should be.  I dunno.  I'm not sure how these "video quirks"
> work.
>
> b.
>

  reply	other threads:[~2008-12-14 15:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-14  9:16 Robby Workman
2008-12-14 14:08 ` Brian J. Murrell
2008-12-14 15:35   ` Justin P. Mattock [this message]
2008-12-14 17:06     ` Brian J. Murrell
  -- strict thread matches above, loose matches on Subject: below --
2008-12-14  5:06 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
     [not found]       ` <gi65ol$bnf$7@ger.gmane.org>
2008-12-15 20:19         ` Rafael J. Wysocki
     [not found]           ` <gi6g21$bnf$8@ger.gmane.org>
2008-12-15 23:02             ` Rafael J. Wysocki
     [not found]               ` <gi7433$m5f$1@ger.gmane.org>
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 16:37                       ` Matthew Garrett
     [not found]                         ` <gi8qoj$m5f$7@ger.gmane.org>
2008-12-16 20:53                           ` Matthew Garrett
2008-12-18  7:52                             ` Pavel Machek
2008-12-18  8:11                               ` Justin P. Mattock
2008-12-20 17:43     ` Sergio Monteiro Basto
     [not found] ` <gicjac$m5f$11@ger.gmane.org>
     [not found]   ` <gieo1h$u78$1@ger.gmane.org>
2008-12-19 17:33     ` Rafael J. Wysocki

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=9695C60B-CC91-41B3-87BB-D687E764BE30@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=brian@interlinx.bc.ca \
    --cc=linux-kernel@vger.kernel.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®