public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Faye Pearson <faye-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
To: VOLTZ st?phane <svoltz-39ZsbGIQGT5GWvitb5QawA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Wakeup code way too big
Date: Wed, 12 Feb 2003 15:41:58 +0000	[thread overview]
Message-ID: <20030212154158.GA32406@clara.net> (raw)
In-Reply-To: <3E451DDA.7010309-39ZsbGIQGT5GWvitb5QawA@public.gmane.org>

VOLTZ st?phane [svoltz-39ZsbGIQGT5GWvitb5QawA@public.gmane.org] wrote:
>        while booting 2.5.59, I got the following message :
> ACPI: Wakeup code way too big, will crash on attempt to suspend

2.5.60 same message, Sony GRX516MD.

>        I added some printk to arch/i386/kernel/acpi.c in
> acpi_reserve_bootmem() to get wakeup_end and wakeup_start values, and I got:
> 
> ACPI: have wakeup address 0xc0001000
> ACPI: have wakeup_end     0x00000000
> ACPI: have wakeup_start   0xffffffb8

I have an identical wakeup address, haven't put the printks in yet, but
I bet they're the same too :)

I don't think there's that many bytes from ffffffb8 to 100000000
Perhaps that's the problem?

I see a couple of patches about wakeup, so I'll apply those first.

I'm very interested in getting suspend working.


Faye

-- 
Faye Pearson,
Covert Development
ClaraNET Ltd.       Tel 020 7903 3000

Never be led astray onto the path of virtue.


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

      parent reply	other threads:[~2003-02-12 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08 15:10 Wakeup code way too big VOLTZ stéphane
     [not found] ` <3E451DDA.7010309-39ZsbGIQGT5GWvitb5QawA@public.gmane.org>
2003-02-12 15:41   ` Faye Pearson [this message]

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=20030212154158.GA32406@clara.net \
    --to=faye-6jsjyq0qj1reowh0uzbu5w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=svoltz-39ZsbGIQGT5GWvitb5QawA@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