From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Re: "ACPI: Unable to start the ACPI Interpreter"
Date: Mon, 27 Jun 2011 15:30:51 -0400
Message-ID: <20110627193051.GA14665@dumpdata.com>
References: <BANLkTinaNMbstBGopDyGcWQpjr=oF-myQQ@mail.gmail.com>
	<BANLkTi=WAm3Bz0apgZ8B5P5ZvJhR=k4eMA@mail.gmail.com>
	<20110627133936.GB6978@dumpdata.com>
	<BANLkTinFEVngVMBCZDRKkV+3kKOooPFR8w@mail.gmail.com>
	<20110627163247.GT6978@dumpdata.com>
	<BANLkTikwvCdTPoXfANbiFMsOFa1-e6AvmQ@mail.gmail.com>
	<20110627173330.GC2430@dumpdata.com>
	<BANLkTinq11kUiCF-ZwC6gk7y3+dDiGAnBQ@mail.gmail.com>
	<20110627191031.GD15703@dumpdata.com>
	<BANLkTim7suw8ZU5xUkCD6AzJBCWJUN_9mw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <BANLkTim7suw8ZU5xUkCD6AzJBCWJUN_9mw@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Liwei <xieliwei@gmail.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On Tue, Jun 28, 2011 at 03:18:21AM +0800, Liwei wrote:
> On 28 June 2011 03:10, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> w=
rote:
> >
> > Another glance shows:
> >
> > (2.6.32):
> > [ =A0 =A03.502771] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 20 l=
ow level)
> > [ =A0 =A03.502773] xen: sci override: source_irq=3D9 global_irq=3D20 =
trigger=3Dc polarity=3D3
> > [ =A0 =A03.502775] xen: registering gsi 20 triggering 0 polarity 1
> > [ =A0 =A03.502780] =A0 alloc irq_desc for 20 on node 0
> >
> > So it has IRQ 9 mapped to IRQ 20 while in 3.0:
> >
> > [ =A0 =A03.803695] xen: --> pirq=3D7 -> irq=3D7
> > [ =A0 =A03.803699] xen: --> pirq=3D8 -> irq=3D8
> > [ =A0 =A03.803702] xen: --> pirq=3D10 -> irq=3D10
> >
> > we skip over IRQ 9. We should have gotten something like this:
> >
> > [ =A0 =A07.059735] xen_map_pirq_gsi: returning irq 20 for gsi 9
> > [ =A0 =A07.064933] xen: --> pirq=3D20 -> irq=3D9
> >
> > But we did not. If you can instrument 'acpi_get_override_irq' to see
> > at which of the numerous 'return -1' it fails =A0that might narrow do=
wn
> > the issue.
> >
>=20
> Erm, do you want me to set up some kernel tracing or just add a printk
> to acpi_get_override_irq? My kernel hacking foo is very limited.

Just splash some printk's around there and print out the values of gsi an=
d pins.
Nothing fancy.