From mboxrd@z Thu Jan 1 00:00:00 1970 From: Karol Kozimor Subject: Re: [ACPI] Re: 1.1-rc9 acpi_disabled==0x30 on resume Date: Sat, 27 Sep 2003 15:58:56 +0200 Sender: swsusp-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <20030927135856.GA16612@hell.org.pl> References: <200309270135.43786.mhf@linuxmail.org> <20030927000908.GB8008@hell.org.pl> <1064621813.3322.0.camel@laptop-linux> <200309271316.45398.mhf@linuxmail.org> <1064644626.17857.1.camel@laptop-linux> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Return-path: Content-Disposition: inline In-Reply-To: <1064644626.17857.1.camel-udXHSmD1qAy4CTf7w+cZoA@public.gmane.org> Errors-To: swsusp-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Nigel Cunningham Cc: Michael Frank , swsusp-devel , ACPI List List-Id: linux-acpi@vger.kernel.org Thus wrote Nigel Cunningham: > 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? Your guess is right. Prior to fixing, acpi_disabled value was inconsistent over suspends. Getting rid of __initdata fixes those problems, and AFAIR this has already been done in linux-acpi bk tree (see linux-acpi.bkbits.com). Best regards, -- Karol 'sziwan' Kozimor sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf