Re: ACPI interpreter errors (aer_init)

[Len Brown <lenb@kernel.org>]

On Friday 27 April 2007 14:05, Moore, Robert wrote:
> Status 5 from ACPICA is AE_NOT_FOUND.
> 
> _OSC is an optional control method, so whatever code is squawking about it probably handle it and shut up.
> 
> 
> -----Original Message-----
> From: linux-acpi-owner@vger.kernel.org [mailto:linux-acpi-owner@vger.kernel.org] On Behalf Of Udo A. Steinberg
> Sent: Friday, April 27, 2007 5:08 AM
> To: Linux Kernel Mailing List
> Cc: Linux ACPI Mailing List
> Subject: ACPI interpreter errors
> 
> Hello,
> 
> With 2.6.21 I am getting the following errors from the ACPI interpreter on an
> Intel S5000PSL board:
> 
> Allocate Port Service[0000:02:02.0:pcie20]
> Allocate Port Service[0000:02:02.0:pcie21]
> Evaluate _OSC Set fails. Status = 0x0005
> Evaluate _OSC Set fails. Status = 0x0005
> aer_init: AER service init fails - Run ACPI _OSC fails
> aer: probe of 0000:00:02.0:pcie01 failed with error 2
> aer_init: AER service init fails - No ACPI _OSC support
> aer: probe of 0000:00:03.0:pcie01 failed with error 1
> Evaluate _OSC Set fails. Status = 0x0005
> Evaluate _OSC Set fails. Status = 0x0005
> aer_init: AER service init fails - Run ACPI _OSC fails
> aer: probe of 0000:00:04.0:pcie01 failed with error 2
> Evaluate _OSC Set fails. Status = 0x0005
> Evaluate _OSC Set fails. Status = 0x0005
> aer_init: AER service init fails - Run ACPI _OSC fails
> aer: probe of 0000:00:05.0:pcie01 failed with error 2
> Evaluate _OSC Set fails. Status = 0x0005
> Evaluate _OSC Set fails. Status = 0x0005
> aer_init: AER service init fails - Run ACPI _OSC fails
> aer: probe of 0000:00:06.0:pcie01 failed with error 2
> aer_init: AER service init fails - No ACPI _OSC support
> aer: probe of 0000:00:07.0:pcie01 failed with error 1
> 
> The complete dmesg output is attached. If you need more information, please let
> me know.

On a quick glance, it appears that these messages have been in the aer driver
since it was born.
Did you run with CONFIG_PCIEAER in 2.6.19 or 2.6.20 and not have them there?

I agree with Bob, as status 5 is AE_NOT_FOUND,
it appears that the driver is being overly verbose,
even though these appear to all be KERN_DEBUG messages.

-Len