All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Colitti <lorenzo-Z4WAQ3j+MphBDgjK7y7TUQ@public.gmane.org>
To: ncunningham-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org
Cc: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>,
	ACPI List
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: S3 freezes on wake on NC6000 laptop
Date: Tue, 08 Feb 2005 03:07:28 +0100	[thread overview]
Message-ID: <42081EE0.9050108@colitti.com> (raw)
In-Reply-To: <1107823331.2756.32.camel-r49W/1Cwd2ff0s6lnCXPXw0QcLn3kwYh@public.gmane.org>

Nigel Cunningham wrote:
>>- swsusp2 on its own also freezes on wakeup (but even worse:
>>   you can't even power off by holding the power button)
> 
> If that's the case, something is broken in Suspend2. Can you confirm
> that please by removing Radeon but adding Suspend2?

Actually it's not swsusp2's fault. The working kernel has a rather 
stripped-down config, and the non-working kernel has a much more 
complicated configuration. If I add swsusp2 to the stripped-down kernel, S3 
sleep still works.

I'm currently trying to find out what it is wrong in the other .config that 
breaks S3; I suspect preemption, but I'm not sure yet.


Cheers,
Lorenzo


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  parent reply	other threads:[~2005-02-08  2:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 17:23 S3 freezes on wake on NC6000 laptop Lorenzo Colitti
     [not found] ` <4207A416.8030400-Z4WAQ3j+MphBDgjK7y7TUQ@public.gmane.org>
2005-02-07 17:42   ` Carl-Daniel Hailfinger
     [not found]     ` <4207A8A2.1040202-hi6Y0CQ0nG0@public.gmane.org>
2005-02-07 17:53       ` Karol Kozimor
     [not found]         ` <20050207175354.GA20662-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2005-02-07 20:38           ` Stefan Schweizer
     [not found]             ` <e796392205020712384885b728-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-02-08  9:02               ` Karol Kozimor
2005-02-07 22:36   ` Pavel Machek
     [not found]     ` <20050207223644.GA1394-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-02-08  0:11       ` Nigel Cunningham
2005-02-08  0:19       ` Lorenzo Colitti
     [not found]         ` <4208057C.6090707-Z4WAQ3j+MphBDgjK7y7TUQ@public.gmane.org>
2005-02-08  0:42           ` Nigel Cunningham
     [not found]             ` <1107823331.2756.32.camel-r49W/1Cwd2ff0s6lnCXPXw0QcLn3kwYh@public.gmane.org>
2005-02-08  2:07               ` Lorenzo Colitti [this message]
     [not found]                 ` <42081EE0.9050108-Z4WAQ3j+MphBDgjK7y7TUQ@public.gmane.org>
2005-02-08  2:20                   ` Nigel Cunningham
2005-02-08  9:04           ` Karol Kozimor
     [not found]             ` <20050208090411.GB9391-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2005-02-08 12:30               ` Lorenzo Colitti
2005-02-08 13:07           ` Pavel Machek
2005-02-08  0:21       ` Lorenzo Colitti

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=42081EE0.9050108@colitti.com \
    --to=lorenzo-z4waq3j+mphbdgjk7y7tuq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ncunningham-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org \
    --cc=pavel-+ZI9xUNit7I@public.gmane.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 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.