From mboxrd@z Thu Jan  1 00:00:00 1970
From: matthieu castet <castet.matthieu@free.fr>
Subject: Re: suspend to ram problem
Date: Wed, 06 Feb 2008 00:02:26 +0100
Message-ID: <47A8EB02.90502@free.fr>
References: <47A5C399.7010405@free.fr> <47A5DE60.1080402@free.fr> <200802031839.02397.rjw@sisk.pl> <20080203181855.GB1629@elf.ucw.cz> <47A60AA8.8050407@free.fr> <47A6B758.7070405@free.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <linux-acpi-owner@vger.kernel.org>
Received: from smtp2-g19.free.fr ([212.27.42.28]:55026 "EHLO smtp2-g19.free.fr"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752688AbYBEXCb (ORCPT <rfc822;linux-acpi@vger.kernel.org>);
	Tue, 5 Feb 2008 18:02:31 -0500
In-Reply-To: <47A6B758.7070405@free.fr>
Sender: linux-acpi-owner@vger.kernel.org
List-Id: linux-acpi@vger.kernel.org
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, linux-acpi@vger.kernel.org, pm list <linux-pm@lists.linux-foundation.org>

Hi,

matthieu castet wrote:
> matthieu castet wrote:
>> Pavel Machek wrote:
> 
>>> Hmm, maybe I know where problem could be. Try
>>>
>>>         movl     $(wakeup_stack - wakeup_code), %esp              # 
>>> Private stack is needed for ASUS bo\
>>>
>>> instead of existing stack setup. That helped on one of my test-boxes
>> Thanks, I will try that.
>> Because clearing the flags imply pop/push in the stack it could be the 
>> problem
> That doesn't help : it still crash in pushl $0.
> 
All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are 
clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the 
failure can only happen if the stack wrap which is not the case here.
Any x86 guru advice ?

If I remove stack access (remove clearing flag stuff, not call to video 
stuff) the resume works.


Matthieu