public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Lorenz <martin-2WKW0nu+7nMiq3RsQ1AnAw@public.gmane.org>
To: Stefan Seyfried
	<seife-T+3qhDtrTvDv8lqoKu5MV4HBZQ1bDw0s@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: kern 2.6.1 - suspend/resume still malfunctioning
Date: Thu, 15 Jan 2004 15:53:35 +0100	[thread overview]
Message-ID: <4006A96F.1020502@lorenz.eu.org> (raw)
In-Reply-To: <20040115135532.GA11298-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>

Stefan Seyfried wrote:

> On Thu, Jan 15, 2004 at 02:10:57PM +0100, Martin Lorenz wrote:
> 
>>Dear all,
>>
>>well I am playing around to get suspend/resume working on my PC-MM10 for
>>quite a while now, and have run from one failing into the next...
> 
> 
>>all the data, i reported about my laptop is recorded with bug #1773
>>http://bugme.osdl.org/show_bug.cgi?id=1773
> 
> 
> have you tried S4, e.g. "echo 4 > /proc/acpi/sleep"?
> S3 is probably harder to get working than S4, so try S4 first.
> 
well...

with S4 i get a message, saying that my drive was not ready for that
command and it keeps telling me (lines by lines and never ending)

end_request: I/O error, dev hda, sector 1596164

so i it doesent even go to suspend(off)

greets
mlo
-- 
martin lorenz
--
	They that can give up essential liberty
	to obtain a little temporary safety
	deserve neither liberty nor safety.
				-- Benjamin Franklin



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html

  parent reply	other threads:[~2004-01-15 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 13:10 kern 2.6.1 - suspend/resume still malfunctioning Martin Lorenz
     [not found] ` <40069161.4040703-2WKW0nu+7nMiq3RsQ1AnAw@public.gmane.org>
2004-01-15 13:55   ` Stefan Seyfried
     [not found]     ` <20040115135532.GA11298-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2004-01-15 14:53       ` Martin Lorenz [this message]
     [not found]         ` <4006A96F.1020502-2WKW0nu+7nMiq3RsQ1AnAw@public.gmane.org>
2004-01-15 15:25           ` Martin Lorenz
     [not found]             ` <4006B0DD.4020801-2WKW0nu+7nMiq3RsQ1AnAw@public.gmane.org>
2004-01-16 19:39               ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2004-01-18  5:49 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720CEA-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-18 18:37   ` Pavel Machek
     [not found]     ` <20040118183744.GB215-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-01-18 19:57       ` Nigel Cunningham
     [not found]         ` <1074455861.2361.1.camel-udXHSmD1qAy4CTf7w+cZoA@public.gmane.org>
2004-01-18 19:59           ` 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=4006A96F.1020502@lorenz.eu.org \
    --to=martin-2wkw0nu+7nmiq3rsq1anaw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=seife-T+3qhDtrTvDv8lqoKu5MV4HBZQ1bDw0s@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