lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:  <49A48CD2.7070305@gmail.com>
Date:	Tue, 24 Feb 2009 18:12:02 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux-kernel@...r-kernel.org
Subject:  Re: ACPI exception with 2.6.29-rc6

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ