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:10:31 -0400
Message-ID: <20110627191031.GD15703@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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <BANLkTinq11kUiCF-ZwC6gk7y3+dDiGAnBQ@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 02:23:09AM +0800, Liwei wrote:
> On 28 June 2011 01:33, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> >
> > Hmm. Can you attach the full serial log and on the Linux kernel line have
> > 'loglevel=10 debug initcall_debug' please?
> 
> See attached.
> 
> >
> > Is the serial log when running under 2.6.32 any different? (up to the ACPI interpretter
> > blowing up)? What does the /proc/interrupts look under 2.6.32?
> 
> There's too much noise for me to compare, but I think they're more or
> less the same until the the interpreter blows up for 3.0 whereas
> 2.6.32 does not.

Another glance shows:

(2.6.32):
[    3.502771] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 20 low level)
[    3.502773] xen: sci override: source_irq=9 global_irq=20 trigger=c polarity=3
[    3.502775] xen: registering gsi 20 triggering 0 polarity 1
[    3.502780]   alloc irq_desc for 20 on node 0

So it has IRQ 9 mapped to IRQ 20 while in 3.0:

[    3.803695] xen: --> pirq=7 -> irq=7
[    3.803699] xen: --> pirq=8 -> irq=8
[    3.803702] xen: --> pirq=10 -> irq=10

we skip over IRQ 9. We should have gotten something like this:

[    7.059735] xen_map_pirq_gsi: returning irq 20 for gsi 9
[    7.064933] xen: --> pirq=20 -> irq=9

But we did not. If you can instrument 'acpi_get_override_irq' to see
at which of the numerous 'return -1' it fails  that might narrow down
the issue.