public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: suspend-to-ram hangs on HP NX7010
Date: Wed, 09 Jun 2004 14:06:28 +0200	[thread overview]
Message-ID: <40C6FD44.7090606@drzeus.cx> (raw)

Hi!

I've been spending a few days trying to get suspend-to-ram to work on my 
new HP NX7010 laptop. Haven't had much success though so I thought I 
might get some help from the more experienced.

I'm running FC2 with linux 2.6.6. S3 has been tested using vanilla 
kernel and with the patch from acpi.sf.net. I've also included a patch 
from the ACPI bugzilla to be able to control which devices can wake the 
unit. The behaviour has been the same for all tests.

I don't think the unit actually gets all the way into S3 though. If I 
turn on ACPI debug in the kernel I can see a debug message that says 
'Entering S3' but the laptop doesn't power down anything. After this 
point the only way to get control of the machine again is to hold down 
the power button for a couple of seconds, bypassing the OS. Also, for 
some strange reason I have to do this twice because the machine hangs 
during POST after the first reset (after a failed suspend-to-ram that 
is, works fine otherwise).

I've started looking in the ACPI spec. since I suspect the bug might be 
in the DSDT. I doesn't even compile cleanly with Intel's compiler as it 
is. ACPI is new to me however so I could use some pointers on where I 
should start looking. I'm also fluent in C so I intend to have a look at 
the kernel code and insert some debug statements. Might help me pinpoint 
where it hangs.

I'd appreciate any help I can get. Just tell me what information you 
need and what I should test and I'll gladly do it. Suspend-to-ram is a 
badly needed function so I'm ready to devote whatever time is required 
to get this fixed.

Regards
Pierre Ossman


-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org

             reply	other threads:[~2004-06-09 12:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 12:06 Pierre Ossman [this message]
     [not found] ` <40C6FD44.7090606-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
2004-06-14 22:58   ` suspend-to-ram hangs on HP NX7010 Pierre Ossman
     [not found]     ` <40CE2DB0.9050208-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
2004-06-16 12:36       ` Pierre Ossman
2004-06-18 19:56   ` Pierre Ossman
     [not found]     ` <40D348EC.8030903-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
2004-06-19  3:29       ` Michael Frank
     [not found]         ` <opr9tnzbol4evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
2004-06-19  7:23           ` Pierre Ossman
  -- strict thread matches above, loose matches on Subject: below --
2004-06-09 12:33 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8404991407-4yWAQGcml66Amxt+E6XRvg@public.gmane.org>
2004-06-09 15:09   ` Pierre Ossman
     [not found]     ` <40C72816.70908-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
2004-06-09 15:25       ` Matthew Wilcox

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=40C6FD44.7090606@drzeus.cx \
    --to=drzeus-list-p3sgcrwkh8cezlla646fqq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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