public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Dawid <oliver-csNNzRR391izQB+pC5nmwQ@public.gmane.org>
To: Matthias Hentges <mailinglisten-H4PcyxPeSRnR7s880joybQ@public.gmane.org>
Cc: Oliver Dawid
	<od-VRmHG7Xu4f31qYPpFx2fzhvVK+yQ3ZXh@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: S3 broken Samsung P35 - howto debug?
Date: Mon, 22 Nov 2004 09:20:21 +0100	[thread overview]
Message-ID: <41A1A145.4090006@helios.de> (raw)
In-Reply-To: <1101064133.7220.15.camel@mhcln03>

Hi Matthias,

Matthias Hentges wrote:

> Did you say yes to "Power management options / ACPI / Use compatibily
> PCI resume code" after patching?

Yes I did as you proposed.

> For testing purposes, I'd go with the buggy Samsung DSDT.

Since errors in dsdt seem not to touch any suspend-to-* problem, this is 
a good idea.

>>- which modules are known not to work properly with acpi sleep/ resume? Which 
>>should be unloaded before going to sleep?
> 
> The following things break resume on the P30 (break == freeze on resume)
> 
> - Active sound driver, be it OSS or ALSA. Must be unloaded before
> suspending.
> - radeonfb
> - Accelerated X (DRI or fglrx)
> 
> For testing purposes I'd recommend using a minimalistic kernel .config
> (no usb, firewire, preempt, AGP etc.)

Hmm wouldn't it be good to collect which modules are hanging? Or is it 
platform-dependent?

As dri or fglrx are freezing the system, do you need to abandon X before 
going to sleep?

> There's a little script to restore lost PCI configuration DATA after a
> resume. 
> I've managed to get the backlight on, but that's it heh.

so you aren't sitting totally in the dark but have some miserable lamp 
to illuminate your keyboard ;-)

Oliver


-------------------------------------------------------
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://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-11-22  8:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-21 15:00 S3 broken Samsung P35 - howto debug? Oliver Dawid
     [not found] ` <200411211600.01820.od-VRmHG7Xu4f31qYPpFx2fzhvVK+yQ3ZXh@public.gmane.org>
2004-11-21 18:05   ` Pavel Machek
2004-11-21 19:08   ` Matthias Hentges
2004-11-22  8:20     ` Oliver Dawid [this message]
     [not found]       ` <41A1A145.4090006-csNNzRR391izQB+pC5nmwQ@public.gmane.org>
2004-11-22 12:26         ` Matthias Hentges
2004-11-24 10:23     ` Oliver Dawid
     [not found]       ` <41A4613F.2020905-csNNzRR391izQB+pC5nmwQ@public.gmane.org>
2004-11-24 12:54         ` Stefan Dösinger
     [not found]           ` <200411241354.53598.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-11-24 16:28             ` Matthias Hentges
2004-11-24 17:42               ` Christoph Tavan
2004-11-25  7:02             ` Oliver Dawid
2004-11-24 13:13         ` Matthias Hentges
     [not found] ` <200411242012.36750.stefandoesinger@gmx.at>
     [not found]   ` <1101328293.7299.15.camel@mhcln03>
2004-11-24 21:21     ` Stefan Dösinger
     [not found]       ` <200411242221.45175.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-11-25  6:41         ` Matthias Hentges
2004-11-25 13:03           ` Stefan Dösinger
     [not found]             ` <200411251403.02800.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-11-25 13:57               ` Stefan Schweizer
  -- strict thread matches above, loose matches on Subject: below --
2004-11-24 15:01 Pallipadi, Venkatesh

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=41A1A145.4090006@helios.de \
    --to=oliver-csnnzrr391izqb+pc5nmwq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=mailinglisten-H4PcyxPeSRnR7s880joybQ@public.gmane.org \
    --cc=od-VRmHG7Xu4f31qYPpFx2fzhvVK+yQ3ZXh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox