From mboxrd@z Thu Jan 1 00:00:00 1970 From: matthieu castet Subject: Re: suspend to ram problem Date: Wed, 06 Feb 2008 23:40:35 +0100 Message-ID: <47AA3763.7000106@free.fr> References: <47A5C399.7010405@free.fr> <47A6B758.7070405@free.fr> <47A8EB02.90502@free.fr> <200802060020.12289.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from smtp2-g19.free.fr ([212.27.42.28]:57737 "EHLO smtp2-g19.free.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756183AbYBFWkj (ORCPT ); Wed, 6 Feb 2008 17:40:39 -0500 In-Reply-To: <200802060020.12289.rjw@sisk.pl> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: "Rafael J. Wysocki" Cc: Pavel Machek , linux-acpi@vger.kernel.org, pm list Rafael J. Wysocki wrote: > On Wednesday, 6 of February 2008, matthieu castet wrote: >> 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. > > Hm, can you place a "pushl %eax; popl %eax;" in place of the removed code and > see if that breaks? Yes that also break. Matthieu