From: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
To: Bjorn Wesen <bjorn.wesen-VrBV9hrLPhE@public.gmane.org>
Cc: ACPI mailing list
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Weirdness in arch/i386/kernel/acpi_wakeup.S
Date: Mon, 10 Feb 2003 18:09:28 +0100 [thread overview]
Message-ID: <20030210170928.GD443@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.33.0302101340590.2171-100000-Hi2dXqvvzfEtpH44vsTDoQ@public.gmane.org>
Hi!
> The acpi.c code in the same directory insists on wakeup_end - wakeup_start
> being less than a page big, but in the .S file, the org statements force
> them to be at least 3 pages apart :) (2.5.59 with latest ACPI patches)
>
> It seems to work anyway because the relevant _code_ is in the beginning and
> is thus copied into the low page anyway during S3 suspend, but there is a
> reference to a wakeup_stack and it all looks a bit funny, not to mention
> the big warning message "will crash upon attempt to suspend".. can anyone
> say how this code is supposed to work and I'll dive into it :)
Well, it seems that code needs to get smaller...
> (The problem I'm having is that the console VGA is not re-initialized upon
> coming back from an S3 suspend and I am trying to debug that)
Have you tried acpi_sleep=s3_bios and acpi_sleep=s3_mode (not yet in
2.5.59, but already in 2.5.59-acpi?)
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-02-10 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 12:43 Weirdness in arch/i386/kernel/acpi_wakeup.S Bjorn Wesen
[not found] ` <Pine.LNX.4.33.0302101340590.2171-100000-Hi2dXqvvzfEtpH44vsTDoQ@public.gmane.org>
2003-02-10 13:16 ` Ducrot Bruno
[not found] ` <20030210131601.GF25625-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-02-10 22:29 ` Bjorn Wesen
2003-02-10 17:09 ` Pavel Machek [this message]
[not found] ` <20030210170928.GD443-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2003-02-12 11:50 ` Bjorn Wesen
[not found] ` <Pine.LNX.4.33.0302121245090.6226-100000-Hi2dXqvvzfEtpH44vsTDoQ@public.gmane.org>
2003-02-12 14:24 ` Pavel Machek
[not found] ` <20030212142405.GB13327-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
2003-02-12 17:07 ` Ole Myren Rohne
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=20030210170928.GD443@elf.ucw.cz \
--to=pavel-alswssmvlrq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=bjorn.wesen-VrBV9hrLPhE@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