Thread (1 message) 1 message, 1 author, 2003-02-10

Re: Weirdness in arch/i386/kernel/acpi_wakeup.S

From: Bjorn Wesen <hidden>
Date: 2003-02-10 22:29:25

On Mon, 10 Feb 2003, Ducrot Bruno wrote:
On Mon, Feb 10, 2003 at 01:43:54PM +0100, Bjorn Wesen wrote:
quoted
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)
Simple.  You can have only one physical page allowed for the wakup code.
If you make something bigger, or point the stack outside, you will
get memory corruption.
That's what I figured, but since the code was so blatantly wrong in that 
case it seemed more probable that I had missed something :) In the 2.4 
series of the ACPI patches, the org's are at 300 and 400 instead of 2000 and 
3000 I think so that made more sense.
I have send some time ago a patch to prevent that.  Don't know why
it is still not included.
Maybe it's in the ACPI cvs. I only checked the .tgz release.

Do you know if the S3 resume code is supposed to work wrgds to video 
restoration ?

/Bjorn




-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help