All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas J. Thorvaldsen" <ajthorva-pC9TGHjoBLc@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Dell i5100 resume from ram probl. (2.6.0-test11)
Date: Mon, 08 Dec 2003 11:50:35 +0100	[thread overview]
Message-ID: <3FD4577B.60406@start.no> (raw)

I have run some tests with suspend-to-ram (S3) on my Dell Inspiron 5100
laptop (bios rev. A23, Radeon 7500, ps2-type keyb.), and these are the
symptoms I have encountered:

1. The display stays black after resume (text). If suspending/resuming
from X, some "scary" visual effects resembling "LCD hypothermia"
appears, followed by a dark (but backlit) screen. Typing commands on the 
keyboard gives no response.

2. echo 3 > /proc/acpi/sleep; sleep 10; reboot; does run, indicating
that at least one process resumes correctly.

3. A key logger (Linux Key Logger; userspace) stops logging after resume
(though /var/log/messages continues to write (no errors)), indicating
that it has died somehow (although ...; ps -A > dump; indicates that it 
hasn't).

What are the likely causes of this problem? Is it a timer-, interrupt-, 
keyb.-, or video-problem or a pure ACPI problem? Where should I start 
debugging? Any help og advice is greatly appreciated.

-andreas




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

             reply	other threads:[~2003-12-08 10:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 10:50 Andreas J. Thorvaldsen [this message]
     [not found] ` <3FD4577B.60406-pC9TGHjoBLc@public.gmane.org>
2003-12-12 21:19   ` Dell i5100 resume from ram probl. (2.6.0-test11) Karol Kozimor

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=3FD4577B.60406@start.no \
    --to=ajthorva-pc9tghjoblc@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 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.