From: Mirko Werneke <mirko.werneke-hi6Y0CQ0nG0@public.gmane.org>
To: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Acer TM 661 does not wake up from STR
Date: Thu, 26 Aug 2004 14:41:06 +0200 [thread overview]
Message-ID: <412DDA62.5030505@gmx.net> (raw)
In-Reply-To: <412CC887.9080706-Y6VGUYTwhu0@public.gmane.org>
Nate Lawson wrote:
> Mirko Werneke wrote:
>
>> I compiled a minimal kernel (without usb/wlan drivers, etc.) with a
>> little patch in wakeup.S.
>> I inserted after .code16 the line "lcall $0xffff,$0". This should -
>> according to Stefan - immediatly call the BIOS reset code after the
>> kernel gets control back from BIOS. But the situation did not change
>> (no "automatic" reboot after resume). So we came to the conclusion,
>> that the kernel does not get the control back when the system wakes up.
>> So i think that there is a problem with the BIOS or the kernel does
>> something wrong while suspending.
>
>
> So the BIOS is not calling the wake vector.
But why? Because i don't know very much about acpi and there is no error
message i simply don't know where to start to solve the problem.
> I've been wondering about
> several deviations from the spec in the sleep path (hwsleep.c).
>
> I think _GTS should be run immediately before writing the sleep value in
> EnterSleepState (not Prep). [...]
> I'm suspicious of writing the SLP_TYP and SLP_EN on separate passes. The
> sample code in the spec (7.3.4) writes this in one pass.
Do you think that this deviations are responsible for the problems i
encounter? My laptop does not have a _GTS method and writing SLP_TYP and
SLP_EN in one pass does not make any difference.
best wishes
Mirko
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
next prev parent reply other threads:[~2004-08-26 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 14:51 Acer TM 661 does not wake up from STR Mirko Werneke
[not found] ` <412CA779.8000602-hi6Y0CQ0nG0@public.gmane.org>
2004-08-25 17:12 ` Nate Lawson
[not found] ` <412CC887.9080706-Y6VGUYTwhu0@public.gmane.org>
2004-08-26 12:41 ` Mirko Werneke [this message]
2004-08-25 17:17 ` Nate Lawson
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=412DDA62.5030505@gmx.net \
--to=mirko.werneke-hi6y0cq0ng0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=nate-Y6VGUYTwhu0@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.