Re: sony-laptop: ACPI Exception when a Fn-Key is pressed

[Len Brown <lenb@kernel.org>]

On Mon, 6 Apr 2009, Mattia Dongili wrote:

> On Sun, Apr 05, 2009 at 09:27:06PM -0300, Rodrigo Luiz wrote:
> > Hi.
> > 
> > I have a Vaio VGN-FW235J and I tried today the latest kernel version
> > in git to test the latest changes in sony-laptop.
> > 
> > When I press any Fn-keys, i.e. brightness control, I received these
> > messages in syslog:
> > 
> > ACPI Error (hwvalid-0186): Denied AML access to port 0x00000080/4
> > (DMA1 0x0081-0x0083) [20090320]

this looks like a write to port 80 -- the debug port -- which is valid.

however, it looks like the size is 4, which overlaps with protected ports?


> > ACPI Exception (evregion-0422): AE_AML_ILLEGAL_ADDRESS, Returned by
> > Handler for [SystemIO] [20090320]
> > ACPI Error (psparse-0537): Method parse/execution failed [\P8XH] (Node
> > f7418c30), AE_AML_ILLEGAL_ADDRESS
> > ACPI Error (psparse-0537): Method parse/execution failed
> > [\_SB_.PCI0.LPCB.EC__._Q58] (Node f741bc00), AE_AML_ILLEGAL_ADDRESS
> > ACPI Error (hwvalid-0186): Denied AML access to port 0x00000080/4
> > (DMA1 0x0081-0x0083) [20090320]
> > ACPI Exception (evregion-0422): AE_AML_ILLEGAL_ADDRESS, Returned by
> > Handler for [SystemIO] [20090320]
> > ACPI Error (psparse-0537): Method parse/execution failed [\P8XH] (Node
> > f7418c30), AE_AML_ILLEGAL_ADDRESS
> > ACPI Error (psparse-0537): Method parse/execution failed
> > [\_SB_.PCI0.LPCB.EC__._Q59] (Node f741bc18), AE_AML_ILLEGAL_ADDRESS
> 
> Interesting. This is due to a change in current git it was not present
> in 2.6.29.
> 
> Does booting with acpi_osi=Linux makes things any worse? (it should fix
> the above error but might make some other functionality behave
> differently).
> Or eventually also see if there is a bios upgrade available for your
> laptop.
> 
> Len,
> it looks like most of the vaios define this in global scope:
> 
>     OperationRegion (PRT0, SystemIO, 0x80, 0x04)
>     Field (PRT0, DWordAcc, Lock, Preserve)
>     {   
>         P80H,   32
>     }
> 
> which falls in the DMA1 reserved area in >WinXP.
> No idea how windows copes with it if the same restrictions area really
> in place.

just defining the opregion is okay.

in 2.6.29 we checked at opregion definition time -- but had some false
hits on regions that were defined and never used.

so in 2.6.30 we have run-time checks only.

-Len Brown, Intel Open Source Technology Center