From: Jason Dagit <dagit-LP0vGzdgvNwj5TC/SZClsA@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Resume from mem state == Reboot (Averatec)
Date: Tue, 22 Mar 2005 00:12:45 -0800 [thread overview]
Message-ID: <87br9cxfnm.fsf@www.codersbase.com> (raw)
In-Reply-To: <87eke94hul.fsf-mMfbam+mt929kzlf/Hu3QdBPR1lH4CV8@public.gmane.org> (Jason Dagit's message of "Sun, 20 Mar 2005 22:45:54 -0800")
Jason Dagit <dagit-LP0vGzdgvNwj5TC/SZClsA@public.gmane.org> writes:
> Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org> writes:
>
>> This is likely to be the same problem as
>> http://bugzilla.kernel.org/show_bug.cgi?id=3691
I made a discovery today. This bug says the following:
http://bugme.osdl.org/show_bug.cgi?id=3586
---- Begin Paste ----
Code from arch/i386/kernel/acpi/wakeup.S:
[...]
mov $(wakeup_stack - wakeup_code), %sp # Private stack is needed for ASUS board
movw $0x0e00 + 'S', %fs:(0x12)
pushl $0 ###THIS LINE CAUSES REBOOT! # Kill any dangerous flags
popfl
movl real_magic - wakeup_code, %eax
[...]
Commenting out pushl $0 and popfl wakeup code goes on until another
issue blocks it later (more on this to be added as soon as we point
something out on the acpi-devel mailing list)
---- End Paste ----
I tried commenting out those lines (both the pushl and popfl) and my
laptop suspends and resumes! The screen is blank when the machine
resumes, but I can toggle capslock and if I type "find /" the hard
drive light comes on. So it would appear that the machine is setting
the firmware_wake_vector correctly, but something about that push and
pop is not good for this machine. Now I'm off to debug the video
resume problems, which appears to be a pretty common problem with
suspend/resume.
I hope this is helpful to others. Matthew can you try this on your
laptop?
Thanks,
Jason
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-03-22 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 20:28 Resume from mem state == Reboot (Averatec) Jason Dagit
[not found] ` <87k6oaug4a.fsf-mMfbam+mt929kzlf/Hu3QdBPR1lH4CV8@public.gmane.org>
2005-03-14 22:45 ` Matthew Garrett
2005-03-21 6:45 ` Jason Dagit
[not found] ` <87eke94hul.fsf-mMfbam+mt929kzlf/Hu3QdBPR1lH4CV8@public.gmane.org>
2005-03-22 8:12 ` Jason Dagit [this message]
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=87br9cxfnm.fsf@www.codersbase.com \
--to=dagit-lp0vgzdgvnwj5tc/szclsa@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