From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Frank Subject: Re: [ACPI] Re: 1.1-rc9 acpi_disabled==0x30 on resume Date: Tue, 30 Sep 2003 08:38:52 +0800 Sender: swsusp-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <200309300838.52320.mhf@linuxmail.org> References: <200309270135.43786.mhf@linuxmail.org> <200309271316.45398.mhf@linuxmail.org> <1064644626.17857.1.camel@laptop-linux> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1064644626.17857.1.camel-udXHSmD1qAy4CTf7w+cZoA@public.gmane.org> Content-Disposition: inline Errors-To: swsusp-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Nigel Cunningham Cc: Karol Kozimor , swsusp-devel , ACPI List List-Id: linux-acpi@vger.kernel.org On Saturday 27 September 2003 14:37, Nigel Cunningham wrote: > My guess would be that the memory is being freed and reused, and that's > where the 0x30 comes from. Could you use kdb to check it prior to > suspending? > Manual checking would not be practical, so the script unloads/loads/unloads ac prior to suspend and loads it on resume and logs/beeps when failure. It last happend with -rc9 but not yet with -rc9D. Last time data from the memory dump were remains of an ascii file: in len */ /* lowowrd last bytes sought */ #define ..... Guess data not initialized on resume, but can't be major or other problems would pop up. Regards Michael ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf