From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Linux 3.4 dom0 kernel error loading
 xen-acpi-processor: Input/output error
Date: Mon, 18 Mar 2013 09:06:59 -0400
Message-ID: <20130318130659.GA24560@phenom.dumpdata.com>
References: <20130307074808.GV8912@reaktio.net>
	<20130308202457.GA21875@phenom.dumpdata.com>
	<20130308221820.GE8912@reaktio.net>
	<20130312205118.GN8912@reaktio.net>
	<20130315150527.GA16632@phenom.dumpdata.com>
	<20130315151934.GZ8912@reaktio.net>
	<20130315193706.GA8912@reaktio.net>
	<20130315211518.GA32252@phenom.dumpdata.com>
	<20130315213227.GB8912@reaktio.net>
	<20130317170047.GA13486@konrad-lan.dumpdata.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <20130317170047.GA13486@konrad-lan.dumpdata.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= <pasik@iki.fi>
Cc: David Vrabel <david.vrabel@citrix.com>, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

> On my box, I took the SSDT but it did not give any insight, except that
> the _PDC and _OSC end up calling in the  \_PR.OSC method pasted above:
> 
>     Scope (\_PR)                                                                
>     {                                                                           
>         Processor (P000, 0x01, 0x00000410, 0x06)                                
>         {                             
> .. snip..                                          
>             Method (_OSC, 4, NotSerialized)                                     
>             {                                                                   
>                 Return (\_PR.OSC)                                               
>                 Arg0                                                            
>                 Arg1                                                            
>                 Arg2                                                            
>                 Arg3                                                            
>             }                                                                   
>         }                                                                       
>                                       
>     }
> 
> It looks like the magic incantations are in:
> 
>         OperationRegion (CSDT, SystemMemory, 0xBAE0BE18, 0x0084)
> 
> so physical address 0xBAE0BE18. The machine is offline so it will have
> to wait until I can get the contents of that physical address.


And if I dug deep enough and looked in: /sys/firmware/acpi/tables/dynamic/
I would have found SSDT2 and SSDT3 and SSDT2 sure enough has:

  Scope (\_PR.P000)
    {
        Name (_PCT, Package (0x02)
        {

. .. snip..

and also the _PSS, _PPC, etc.