Re: [PATCH] reduce AER init error information

[Greg KH]

On Tue, May 29, 2007 at 04:10:14PM +0200, Michal Piotrowski wrote:
> Hi all,
> 
> Zhang, Yanmin napisa??(a):
> > PCI-Express AER support in kernel requires BIOS to provide _OSC support
> > to allow the AER Root port service driver to request for native control
> > of AER. If a root port supports AER capablity, but BIOS doesn't provide
> > _OSC for it, aerdriver will print many debug information to system console.
> > Below is a log example.
> > 
> > *******************Error information example************
> > 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
> > 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:06.0:pcie01 failed with error 2
> > ******************End of Error information example******
> > 
> > 
> > As _OSC is an optional capability of BIOS, such error information looks
> > like overly-verbosed. The patch against kernel 2.6.21 changes it to just
> > print one line report messages if aerdriver fails to attach the root port
> > service device.
> > 
> > Below is an example of new output.
> > AER service couldn't init device 0000:00:02.0:pcie01 - no _OSC support
> > 
> > 
> > Signed-off-by: Zhang Yanmin <yanmin.zhang@xxxxxxxxx>
> > 
> > ---
> > 
> [..]
> 
> This patch fixes a 2.6.21 regression. Please add this to the -stable and mainline queue.

Care to forward the above patch to the stable@xxxxxxxxxx address after
it goes into Linus's tree?

thanks,

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