From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Alberto Piai <albeclemit-whZMOeQn8C0@public.gmane.org>
Cc: HIROIT-JE5g2YyFxFHQT0dZR+AlfA@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: S3 resume on Fujitsu-Siemens Amilo A7620 (CONTINUES)
Date: Mon, 18 Oct 2004 14:47:56 +0200 [thread overview]
Message-ID: <20041018124756.GA28463@elf.ucw.cz> (raw)
In-Reply-To: <20041018134238.4cf1b380.albeclemit-whZMOeQn8C0@public.gmane.org>
Hi!
> Please refer to threads "ACPI S3 resume only reboots" and "[PATCH] GDT table patch for resume only reboots problem" for history on this thread. I moved to a new one because was becoming hard to follow.
>
> Properly using beeping code by Pavel I was able to follow the code after
> wakeup_pmode_return:
> movw $__KERNEL_DS, %ax
> movw %ax, %ss
> and verified that it doesn't hang at that point.
>
> Wakeup works until:
> [...]
> # and restore the stack ... but you need gdt for this to work
> movl saved_context_esp, %esp
>
> movl %cs:saved_magic, %eax
> cmpl $0x12345678, %eax
> jne bogus_magic
>
> # jump to place where we left off
> movl saved_eip,%eax
> jmp *%eax ###BEFORE THE JMP IT'S STILL ALIVE!
> [...]
>
> If i let it enter the jmp, it hangs. How can i follow that jump? Does that mean that we're going out of wakeup.S, finally? That would be a progress.
>
Yes, you are going out of wakeup.S... Actually no. You are going to
ret_point down in do_suspend_lowlevel.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-18 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 11:42 S3 resume on Fujitsu-Siemens Amilo A7620 (CONTINUES) Alberto Piai
[not found] ` <20041018134238.4cf1b380.albeclemit-whZMOeQn8C0@public.gmane.org>
2004-10-18 12:47 ` Pavel Machek [this message]
[not found] ` <20041018124756.GA28463-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-10-18 20:54 ` Alberto Piai
[not found] ` <20041018225412.397dcd1f.albeclemit-whZMOeQn8C0@public.gmane.org>
2004-10-18 21:22 ` Pavel Machek
[not found] ` <20041018212208.GA10490-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-10-18 22:21 ` Alberto Piai
[not found] ` <20041019002115.2faa9436.albeclemit-whZMOeQn8C0@public.gmane.org>
2004-10-18 23:00 ` Pavel Machek
[not found] ` <20041018230008.GC10490-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-10-27 22:44 ` Alberto Piai
[not found] ` <20041028004424.1b0f95fb.albeclemit-whZMOeQn8C0@public.gmane.org>
2004-10-27 23:47 ` 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=20041018124756.GA28463@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=HIROIT-JE5g2YyFxFHQT0dZR+AlfA@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=albeclemit-whZMOeQn8C0@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@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