ACPI stops working after memory upgrade vpr Matrix 175b4

ACPI stops working after memory upgrade vpr Matrix 175b4

[Dave Bauer]

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.

Any ideas on what to look for?

Here is a sample of the boot log:

Feb  2 20:35:54 einstein kernel: ACPI: Subsystem revision 20040116
Feb  2 20:35:54 einstein kernel:    tbget-0291: *** Info: Table [DSDT] 
replaced by host OS
Feb  2 20:35:54 einstein kernel:  tbxface-0117 [03] 
acpi_load_tables      : ACPI Tables successfully acquired
Feb  2 20:35:54 einstein kernel: Parsing all Control 
Methods:..........................................................................................................................................................................
Feb  2 20:35:54 einstein kernel: Table [DSDT](id F005) - 554 Objects 
with 49 Devices 170 Methods 17 Regions
Feb  2 20:35:54 einstein kernel: Parsing all Control Methods:
Feb  2 20:35:54 einstein kernel: Table [SSDT](id F003) - 3 Objects with 
0 Devices 0 Methods 0 Regions
Feb  2 20:35:54 einstein kernel: ACPI Namespace successfully loaded at 
root c039ba9c
Feb  2 20:35:54 einstein kernel: ACPI: IRQ9 SCI: Edge set to Level Trigger.
Feb  2 20:35:54 einstein kernel: evxfevnt-0093 [04] 
acpi_enable           : Transition to ACPI mode successful
Feb  2 20:35:54 einstein kernel: evgpeblk-0747 [06] 
ev_create_gpe_block   : GPE 00 to 15 [_GPE] 2 regs at 0000000000001028 
on int 9
Feb  2 20:35:54 einstein kernel: evgpeblk-0747 [06] 
ev_create_gpe_block   : GPE 16 to 31 [_GPE] 2 regs at 000000000000102C 
on int 9
Feb  2 20:35:54 einstein kernel: Completing Region/Field/Buffer/Package 
initialization:.............................................................
Feb  2 20:35:54 einstein kernel: Initialized 17/17 Regions 0/0 Fields 
24/24 Buffers 20/20 Packages (565 nodes)
Feb  2 20:35:54 einstein kernel: Executing all Device _STA and_INI 
methods:....exregion-0164 [25] ex_system_memory_space: Could not map 
memory at 000000000FF7FDBD, size 190
Feb  2 20:35:54 einstein kernel: evregion-0347: *** Error: Handler for 
[SystemMemory] returned AE_NO_MEMORY
Feb  2 20:35:54 einstein kernel:  psparse-1120: *** Error: Method 
execution failed [\_SB_.PHS1] (Node c15d9428), AE_NO_MEMORY
Feb  2 20:35:54 einstein kernel:  psparse-1120: *** Error: Method 
execution failed [\_SB_.BAT1._STA] (Node c15d8328), AE_NO_MEMORY
Feb  2 20:35:54 einstein kernel:   uteval-0098: *** Error: Method 
execution failed [\_SB_.BAT1._STA] (Node c15d8328), AE_NO_MEMORY
Feb  2 20:35:54 einstein kernel: ....exregion-0164 [23] 
ex_system_memory_space: Could not map memory at 000000000FF7FD9D, size 20
Feb  2 20:35:54 einstein kernel: evregion-0347: *** Error: Handler for 
[SystemMemory] returned AE_NO_MEMORY
Feb  2 20:35:54 einstein kernel:  psparse-1120: *** Error: Method 
execution fail:
Feb  2 20:35:54 einstein kernel:   nsinit-0408 [06] 
ns_init_one_device    : \_SB_.PCI0._INI failed: AE_NO_MEMORY
Feb  2 20:35:54 einstein kernel: ...........................................
Feb  2 20:35:54 einstein kernel: 51 Devices found containing: 50 _STA, 1 
_INI methods
Feb  2 20:35:54 einstein kernel: ACPI: Interpreter enabled
Feb  2 20:35:54 einstein kernel: ACPI: Using PIC for interrupt routing
Feb  2 20:35:54 einstein kernel: exregion-0164 [23] 
ex_system_memory_space: Could not map memory at 000000000FF7FDBD, size 190
Feb  2 20:35:54 einstein kernel: evregion-0347: *** Error: Handler for 
[SystemMemory] returned AE_NO_MEMORY
Feb  2 20:35:54 einstein kernel:  psparse-1120: *** Error: Method 
execution failed [\_SB_.PHS1] (Node c15d9428), AE_NO_MEMORY
Feb  2 20:35:54 einstein kernel:  psparse-1120: *** Error: Method 
execution failed [\_SB_.BAT1._STA] (Node c15d8328), AE_NO_MEMORY
Feb  2 20:35:54 einstein kernel: ACPI: PCI Root Bridge [PCI0] (00:00)
Feb  2 20:35:54 einstein kernel: PCI: Probing PCI hardware (bus 00)
Feb  2 20:35:54 einstein kernel: Transparent bridge - 0000:00:1e.0
Feb  2 20:35:54 einstein kernel: ACPI: PCI Interrupt Routing Table 
[\_SB_.PCI0._PRT]
Feb  2 20:35:54 einstein kernel: ACPI: PCI Interrupt Routing Table 
[\_SB_.PCI0.AGPB._PRT]
Feb  2 20:35:54 einstein kernel: ACPI: PCI Interrupt Routing Table 
[\_SB_.PCI0.PCIB._PRT]
Feb  2 20:35:54 einstein kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 
10 *11)
Feb  2 20:35:54 einstein kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 
*10 11)
Feb  2 20:35:54 einstein kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 
*10 11)
Feb  2 20:35:54 einstein kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 
10 *11)
Feb  2 20:35:54 einstein kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 
*10 11)
Feb  2 20:35:54 einstein kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 
10 11)
Feb  2 20:35:54 einstein kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 
10 11)
Feb  2 20:35:54 einstein kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 
10 11)
Feb  2 20:35:54 einstein kernel: ACPI: Embedded Controller [H_EC] (gpe 24)
Feb  2 20:35:54 einstein kernel: exregion-0164 [38] 
ex_system_memory_space: Could not map memory at 000000000FF7FDBD, size 190
Feb  2 20:35:54 einstein kernel: evregion-0347: *** Error: Handler for 
[SystemMemory] returned AE_NO_MEMORY
Feb  2 20:35:54 einstein kernel:  psparse-1120: *** Error: Method 
execution failed [\_SB_.PHS1] (Node c15d9428), AE_NO_MEMORY
Feb  2 20:35:54 einstein kernel:  psparse-1120: *** Error: Method 
execution failed [\_SB_.PCI0.LPCB.H_EC._REG] (Node c15cf9a8), AE_NO_MEMORY
Feb  2 20:35:54 einstein kernel: ACPI: Power Resource [PFAN] (on)
Feb  2 20:35:54 einstein kernel: PCI: Probing PCI hardware

Thanks
Dave



-------------------------------------------------------
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

Re: ACPI stops working after memory upgrade vpr Matrix 175b4

[Karol Kozimor]

Thus wrote Dave Bauer:
> 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.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
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

RE: ACPI stops working after memory upgrade vpr Matrix 175b4

[Yu, Luming]

> methods:....exregion-0164 [25] ex_system_memory_space: Could not map 
> memory at 000000000FF7FDBD, size 190

Maybe the root of this error is that __ioremap don't allow anybody to
remap
normal RAM. Could you verify it by checking it in arch/i386/mm/ioremap.c



-------------------------------------------------------
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

Re: ACPI stops working after memory upgrade vpr Matrix 175b4

[Randy.Dunlap]

> 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.

--
~Randy


-------------------------------------------------------
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

Re: ACPI stops working after memory upgrade vpr Matrix 175b4

[Sergey Vlasov]

On Wed, 4 Feb 2004 07:39:41 -0800 Randy.Dunlap wrote:

> < 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.

Many BIOSes patch the DSDT according to the system configuration (e.g.
rename \_S3 to something other if Suspend to RAM is disabled in the
setup).  Probably some BIOSes put the memory size into DSDT this
way...



-------------------------------------------------------
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

Re: ACPI stops working after memory upgrade vpr Matrix 175b4

[Bruno Ducrot]

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

Re: ACPI stops working after memory upgrade vpr Matrix 175b4

[Nate Lawson]

On Wed, 4 Feb 2004, Bruno Ducrot wrote:
> 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.

To clarify this further, most AML I've seen uses various named regions to
store information about the platform that is dynamic.  For instance, the
actual clock rates and power consumption of the various ACPI performance
states on my Thinkpad are set up at boot time by an _INI method under the
Processor object.  That way if I plugged in a different CPU, it would be
detected at boot time, not hard coded in the AML.  For the case of memory
size and this laptop, that should really be done through the E820 table by
the BIOS and not hardcoded in the AML.

-Nate


-------------------------------------------------------
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

Re: ACPI stops working after memory upgrade vpr Matrix 175b4

[Bas Mevissen]

Randy.Dunlap wrote:
>>
> 
> < 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.
> 

Patch the DSDT on runtime. Or add a checksum on the original DSDT.

Regards,

Bas.



-------------------------------------------------------
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

Re: ACPI stops working after memory upgrade vpr Matrix 175b4

[Karol Kozimor]

Thus wrote Randy.Dunlap:
> < 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.

Yes, that's a necessity in most cases. Why do you consider it that bad?
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
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

Re: ACPI stops working after memory upgrade vpr Matrix 175b4

[Randy.Dunlap]

On Thu, 5 Feb 2004 13:30:49 +0100 Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org> wrote:

| Thus wrote Randy.Dunlap:
| > < 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.
| 
| Yes, that's a necessity in most cases. Why do you consider it that bad?

That seems quite backwards to me.
Why should we consider that a good thing?

I discussed this with Andy Grover and he said that the DSDT isn't
where the memory size is defined.  It should just be coming from
the e820 BIOS calls, not from ACPI DSDT etc., which certainly
made sense to me, as that is something that a user wouldn't need
to modify after changing the memory size of a system.

--
~Randy


-------------------------------------------------------
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

Re: ACPI stops working after memory upgrade vpr Matrix 175b4

[Karol Kozimor]

Thus wrote Randy.Dunlap:
> I discussed this with Andy Grover and he said that the DSDT isn't
> where the memory size is defined.  It should just be coming from

I think you're getting me wrong here: the DSDT clearly does not define the
amount of RAM used by the system, but being dynamically generated by BIOS,
it may include references to fixed memory addresses that can vary with the
amount of RAM installed.

If those addresses change due to such an upgrade, overriding the
BIOS-generated DSDT (containing the right addresses) with one that was
obtained from a system with a different amount of RAM (with addresses
correct for that amount) may indeed not work.

> the e820 BIOS calls, not from ACPI DSDT etc., which certainly
> made sense to me, as that is something that a user wouldn't need
> to modify after changing the memory size of a system.

The user shouldn't need to supply his own DSDT in the first place.

Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
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

Re: ACPI stops working after memory upgrade vpr Matrix 175b4

[Bruno Ducrot]

On Thu, Feb 05, 2004 at 08:27:58AM -0800, Randy.Dunlap wrote:
> On Thu, 5 Feb 2004 13:30:49 +0100 Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org> wrote:
> 
> | Thus wrote Randy.Dunlap:
> | > < 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.
> | 
> | Yes, that's a necessity in most cases. Why do you consider it that bad?
> 
> That seems quite backwards to me.
> Why should we consider that a good thing?

IMHO that a bad thing.

> I discussed this with Andy Grover and he said that the DSDT isn't
> where the memory size is defined.  It should just be coming from
> the e820 BIOS calls, not from ACPI DSDT etc., which certainly
> made sense to me, as that is something that a user wouldn't need
> to modify after changing the memory size of a system.

I'm not sure if the tables are copied upon e820 calls, but I think
there are copied on POST at least on Phoenix BIOS (that what I
understood from their documentations).  Also most of time, the
AML need somehow to access to the nvram, which is located typically
relative to TOM.  Also, when you add/remove memory modules, there
there is chance that mmio regions are not the same, and
aml need to know that.

-- 
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

RE: ACPI stops working after memory upgrade vpr Matrix 175b4

[Brown, Len]

Dave,
Can you capture the e820 messages from the beginning of dmesg for the
success and failure case so we what the BIOS says about your RAM?  Also,
it would be good to try w/o the custom DSDT.

Thanks,
-Len

Ps. Contrary to popular perception, e820 is defined in the ACPI spec.

> -----Original Message-----
> From: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org 
> [mailto:acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of 
> Yu, Luming
> Sent: Tuesday, February 03, 2004 2:07 AM
> To: Dave Bauer; acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> Subject: RE: [ACPI] ACPI stops working after memory upgrade 
> vpr Matrix 175b4
> 
> 
> > methods:....exregion-0164 [25] ex_system_memory_space: 
> Could not map 
> > memory at 000000000FF7FDBD, size 190
> 
> Maybe the root of this error is that __ioremap don't allow anybody to
> remap
> normal RAM. Could you verify it by checking it in 
> arch/i386/mm/ioremap.c
> 
> 
> 
> -------------------------------------------------------
> 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
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
> 


-------------------------------------------------------
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

Re: ACPI stops working after memory upgrade vpr Matrix 175b4

[Dave Bauer]

Sure! I got it 99% working, but I am getting an AML_UNINITIALIZED_LOCAL
error message, which is pretty annoying because I can't see why its
throwing that error.

Trying with an unmodified DSDT doesn't really show much because it has
several bugs that cause the ACPI features to not work at all. I can
capture the two different streams of error messages.

Dave

On Thu, Feb 05, 2004 at 03:45:00PM -0500, Brown, Len wrote:
> Dave,
> Can you capture the e820 messages from the beginning of dmesg for the
> success and failure case so we what the BIOS says about your RAM?  Also,
> it would be good to try w/o the custom DSDT.
> 
> Thanks,
> -Len
> 
> Ps. Contrary to popular perception, e820 is defined in the ACPI spec.
> 
> > -----Original Message-----
> > From: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org 
> > [mailto:acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of 
> > Yu, Luming
> > Sent: Tuesday, February 03, 2004 2:07 AM
> > To: Dave Bauer; acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > Subject: RE: [ACPI] ACPI stops working after memory upgrade 
> > vpr Matrix 175b4
> > 
> > 
> > > methods:....exregion-0164 [25] ex_system_memory_space: 
> > Could not map 
> > > memory at 000000000FF7FDBD, size 190
> > 
> > Maybe the root of this error is that __ioremap don't allow anybody to
> > remap
> > normal RAM. Could you verify it by checking it in 
> > arch/i386/mm/ioremap.c
> > 
> > 
> > 
> > -------------------------------------------------------
> > 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
> > _______________________________________________
> > Acpi-devel mailing list
> > Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > https://lists.sourceforge.net/lists/listinfo/acpi-devel
> > 
> 

-- 
Dave Bauer
dave-eQMij45H2SHXYFsarriMmxagbA6BzR3y@public.gmane.org
http://www.thedesignexperience.org


-------------------------------------------------------
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

RE: ACPI stops working after memory upgrade vpr Matrix 175b4

[Yu, Luming]

> Sure! I got it 99% working, but I am getting an 
> AML_UNINITIALIZED_LOCAL
> error message, which is pretty annoying because I can't see why its
> throwing that error.

I'm interested in the AML code that cause AML_UNINITIALIZED_LOCAL,
Can you show me. Maybe we can come up with some generic solution.

> 
> Trying with an unmodified DSDT doesn't really show much because it has
> several bugs that cause the ACPI features to not work at all. I can
> capture the two different streams of error messages.
> 

Great!

> > > > methods:....exregion-0164 [25] ex_system_memory_space: 
> > > Could not map 
> > > > memory at 000000000FF7FDBD, size 190
> > > 
> > > Maybe the root of this error is that __ioremap don't 
> allow anybody to
> > > remap
> > > normal RAM. Could you verify it by checking it in 
> > > arch/i386/mm/ioremap.c

Did you check memory at 000000000FF7FDBD, size 190 has
been reservered. 

--Luming


-------------------------------------------------------
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