public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-kernel@vger-kernel.org
Subject: Re: ACPI exception with 2.6.29-rc6
Date: Tue, 24 Feb 2009 18:12:02 -0600	[thread overview]
Message-ID: <49A48CD2.7070305@gmail.com> (raw)
In-Reply-To: <871vtpqex0.wl%htd@fancy-poultry.org>

Heinz Diehl wrote:
> Hi,
> 
> booting 2.6.29-rc6 shows the following in boot.log:
> 
> [....]
> <7>bus: 00 index 4 mmio: [230000000, fcffffffff]
> <6>ACPI: bus type pci registered
> <5>PCI: MCFG configuration 0: base f0000000 segment 0 buses 0 - 127
> <5>PCI: MCFG area at f0000000 reserved in E820
> <6>PCI: Using MMCONFIG at f0000000 - f7ffffff
> <6>PCI: Using configuration type 1 for base access
> <4>bio: create slab <bio-0> at 0
> <7>ACPI: EC: Look up EC in DSDT
> --> <3>ACPI: Denied BIOS AML access to invalid port 0x4d0+0x2 (ELCR)
> --> <4>ACPI Exception (dsopcode-0419): AE_AML_ILLEGAL_ADDRESS, During address validation of OpRegion [ELCR] [20081204]

Your BIOS defines an operation region on some IO addresses that the 
kernel will not allow it to access since they are things that BIOS AML 
code is not supposed to be poking with. This check was recently added. 
Windows XP and later also disallow AML access to these registers.

Note that this doesn't necessarily mean that the BIOS is actually trying 
to access those registers. On my A8N-SLI Deluxe machine, the ACPI AML 
defines an operation region for the ELCR register, but it doesn't seem 
like it is ever used.

In any case.. nothing to really worry about.


      reply	other threads:[~2009-02-25  0:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23 16:46 ACPI exception with 2.6.29-rc6 Heinz Diehl
2009-02-25  0:12 ` Robert Hancock [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=49A48CD2.7070305@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=linux-kernel@vger-kernel.org \
    --cc=linux-kernel@vger.kernel.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