public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham-oKK1aGe2n869koe0gwxAeg@public.gmane.org>
To: Michael Frank <mhf-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org>
Cc: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>,
	swsusp-devel
	<swsusp-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	ACPI List
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [ACPI] Re: 1.1-rc9 acpi_disabled==0x30 on resume
Date: Sat, 27 Sep 2003 18:37:07 +1200	[thread overview]
Message-ID: <1064644626.17857.1.camel@laptop-linux> (raw)
In-Reply-To: <200309271316.45398.mhf-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org>

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?

Regards,

Nigel

On Sat, 2003-09-27 at 17:29, Michael Frank wrote:
>   mhf76 2.4.22 
>     +kdb
>     +win4lin +win4lin-option 
>     +acpi-option
>     +/acpi-20030916-2.4.22.diff
>     +swsusp-1.1-rc9
> 
> arch/i386/kernel/acpi.c:
> 
> #ifdef	CONFIG_ACPI_INTERPRETER
> 	int acpi_disabled __initdata = 0;
> #else
> 	int acpi_disabled __initdata = 1;
> #endif
> 
> This should be irrelevant anyway as that kernel 
> is overwritten...
> 
> I find the value 0x30 strange. Are we hunting phantoms?
> 
> Regards
> Michael




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  parent reply	other threads:[~2003-09-27  6:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200309270135.43786.mhf@linuxmail.org>
     [not found] ` <200309270135.43786.mhf-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org>
2003-09-26 20:02   ` 1.1-rc9 acpi_disabled==0x30 on resume Nigel Cunningham
     [not found]     ` <1064606502.5722.2.camel-udXHSmD1qAy4CTf7w+cZoA@public.gmane.org>
2003-09-27  0:09       ` [ACPI] " Karol Kozimor
     [not found]         ` <20030927000908.GB8008-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-09-27  0:16           ` Nigel Cunningham
     [not found]             ` <1064621813.3322.0.camel-udXHSmD1qAy4CTf7w+cZoA@public.gmane.org>
2003-09-27  5:29               ` Michael Frank
     [not found]                 ` <200309271316.45398.mhf-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org>
2003-09-27  6:37                   ` Nigel Cunningham [this message]
     [not found]                     ` <1064644626.17857.1.camel-udXHSmD1qAy4CTf7w+cZoA@public.gmane.org>
2003-09-27 13:58                       ` Karol Kozimor
     [not found]                         ` <20030927135856.GA16612-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-09-27 17:09                           ` Sérgio Monteiro Basto
2003-09-30  0:38                       ` Michael Frank
2003-09-27  0:22           ` Nigel Cunningham
2003-09-27  5:19           ` Michael Frank

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1064644626.17857.1.camel@laptop-linux \
    --to=ncunningham-okk1age2n869koe0gwxaeg@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=mhf-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org \
    --cc=swsusp-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox