From: "Daugirdas Račys" <daugirdas.racys-QUe+8C9cO5A@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: PROBLEM: ACPI S1 stanby doesn't work
Date: Tue, 06 Jul 2004 23:05:08 +0300 [thread overview]
Message-ID: <1089144266.5947.1.camel@nuodai> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1671 bytes --]
Dear developer,
I am writing to inform you about my problems with acpi S1 support. I am
using 2.6.7 from kernel.org (config included). System: Debian Sid.
Please note, that problem described here happened before installing
nvidia drivers. This is from kern.log when "echo 1 > /proc/acpi/sleep"
was executed in root linux console (without X):
Jul 1 14:29:47 nuodai kernel: PM: Preparing system for suspend
Jul 1 14:29:57 nuodai kernel: Stopping tasks:
======================================================================|
Jul 1 14:29:57 nuodai kernel: Could not suspend device 0000:00:11.4:
error -5
Jul 1 14:29:57 nuodai kernel: Restarting tasks... done
Jul 1 14:30:34 nuodai kernel: PM: Preparing system for suspend
Jul 1 14:30:35 nuodai kernel: Stopping tasks:
======================================================================|
Jul 1 14:30:35 nuodai kernel: Could not suspend device 0000:00:11.4:
error -5
Jul 1 14:30:35 nuodai kernel: Restarting tasks... done
As you see these attempts just failed. In contrast, knoppix-3.4 (2.6)
managed to enter S1, but the screen (TFT LCD Samsung SM151N) was not
blanked, nut rather displayed linux console. Resume from S1 left my USB
mouse disabled (needed to rerun hotplug). Strangely, knoppix couldn't
enter S3 (haven't tried in debian).
The just released nvidia drivers works well except standby. The system
enter standby, but will never resume. The only working key set is
C+SysRq+o (even no umount possible). Nvidia declares drivers support
acpi suspend. All in all I guess thats related to the first issue.
Please, let me know what you think.
Yours sincerely,
Daugirdas
[-- Attachment #1.2: info.tar.gz --]
[-- Type: application/x-compressed-tar, Size: 8647 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-07-06 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 20:05 Daugirdas Račys [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-04 17:07 PROBLEM: ACPI S1 stanby doesn't work Daugirdas Račys
[not found] ` <1088960221.6107.18.camel-6QS4qyVsFRo@public.gmane.org>
2004-07-05 14:44 ` Pavel Machek
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=1089144266.5947.1.camel@nuodai \
--to=daugirdas.racys-que+8c9co5a@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