public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: "Randy.Dunlap" <rddunlap-3NddpPZAyC0@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI stops working after memory upgrade vpr Matrix 175b4
Date: Wed, 4 Feb 2004 18:28:52 +0100	[thread overview]
Message-ID: <20040204172852.GL882@poupinou.org> (raw)
In-Reply-To: <20040204073941.05d71e0b.rddunlap-3NddpPZAyC0@public.gmane.org>

On Wed, Feb 04, 2004 at 07:39:41AM -0800, Randy.Dunlap wrote:
> > My ACPI stopped working when I added an additional 256mb RAM to my vpr 
> > Matricx 174b4 laptop. It has 256mb already, I added 256mb to make it 
> > 512mb and I got a bunch of AE_NO_MEMORY errors in the ACPI code.
> > 
> > I took the extra RAM out, and the ACPI support works.
> > 
> > I am using kernel 2.6.1 with acpi patches. I had the same problem on 
> > 2.6.0. On 2.4.20 with acpi patches the machine would not even boot with 
> > the extra memory.
> > 
> > I have a custom DSDT file that I fixed errors in. When it was working on 
> > 2.4.20 It looked like all the ACPI features were active and functional.
> 
> < Recompile your DSDT. Since the amount of RAM changed and you're probably
> < using old DSDT containing wrong addresses, no wonder you're hitting
> < errors.
> 
> Is this correct?  If a user adds or removes memory, then the
> DSDT must be rebuilt?  Sheesh!!  That's bad if this is correct.
> 

Most DSDT are actually build on POST stage.

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  parent reply	other threads:[~2004-02-04 17:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04 15:39 ACPI stops working after memory upgrade vpr Matrix 175b4 Randy.Dunlap
2004-02-04 16:18 ` Sergey Vlasov
     [not found] ` <20040204073941.05d71e0b.rddunlap-3NddpPZAyC0@public.gmane.org>
2004-02-04 17:28   ` Bruno Ducrot [this message]
     [not found]     ` <20040204172852.GL882-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-09 20:21       ` Nate Lawson
2004-02-05 11:21   ` Bas Mevissen
2004-02-05 12:30   ` Karol Kozimor
     [not found]     ` <20040205123049.GC22034-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-02-05 16:27       ` Randy.Dunlap
     [not found]         ` <20040205082758.1917e71a.rddunlap-3NddpPZAyC0@public.gmane.org>
2004-02-06  0:51           ` Karol Kozimor
2004-02-07 12:23           ` Bruno Ducrot
  -- strict thread matches above, loose matches on Subject: below --
2004-02-11  8:19 Yu, Luming
2004-02-05 20:45 Brown, Len
     [not found] ` <BF1FE1855350A0479097B3A0D2A80EE0CC8ABD-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2004-02-05 20:41   ` Dave Bauer
2004-02-03  7:07 Yu, Luming
2004-02-03  2:12 Dave Bauer
     [not found] ` <401F0395.1090407-eQMij45H2SHXYFsarriMmxagbA6BzR3y@public.gmane.org>
2004-02-03  8:31   ` Karol Kozimor

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=20040204172852.GL882@poupinou.org \
    --to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=rddunlap-3NddpPZAyC0@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