From: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
To: Daugirdas-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org,
Ra-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: PROBLEM: ACPI S1 stanby doesn't work
Date: Mon, 5 Jul 2004 16:44:33 +0200 [thread overview]
Message-ID: <20040705144432.GC5054@openzaurus.ucw.cz> (raw)
In-Reply-To: <1088960221.6107.18.camel-6QS4qyVsFRo@public.gmane.org>
Hi!
> 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
UHCI refuses to suspend, try asking on usb list.
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next prev parent reply other threads:[~2004-07-05 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-06 20:05 Daugirdas Račys
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=20040705144432.GC5054@openzaurus.ucw.cz \
--to=pavel-alswssmvlrq@public.gmane.org \
--cc=Daugirdas-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org \
--cc=Ra-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@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.