WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter"

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter"
From: Liwei <xieliwei@xxxxxxxxx>
Date: Tue, 28 Jun 2011 03:18:21 +0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 27 Jun 2011 12:19:15 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=vboQIrdg7jA96LM1JrQUHiRpjkkW7vOlViKJQZMCWsQ=; b=QchbbNbZx0BxnPtzmnPA9qwQllz/MPsWyM5vk7EkmuxSfRNxBNc6T9uvdSzaNrewEJ Qi1y8zCcWCeCsvENd/flHljrMm/7GRVEOcDOGMLdiU6giWB4w6he8ejH2cik4/5mbm+A c/E2nj4/hTf6IgeRvZAtn7XWGfCeFtW5RoAwA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=peXJNxqQOq0p4mPOBz9WvwW7pdo4igQxP2/wzp3NO4vJS/oZxdNvypNAh+UnQ4a9nl o+8Dty4gTcvgr/p/PUEqpCATi4gm0PvGnp8Be6m37lPfrfNRIOSfoWCjjNd06/Ufxxhm U5oVamtEKWQi8ddDGd5BTULRP7TdzmEm8byUo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110627191031.GD15703@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BANLkTinaNMbstBGopDyGcWQpjr=oF-myQQ@xxxxxxxxxxxxxx> <BANLkTi=WAm3Bz0apgZ8B5P5ZvJhR=k4eMA@xxxxxxxxxxxxxx> <20110627133936.GB6978@xxxxxxxxxxxx> <BANLkTinFEVngVMBCZDRKkV+3kKOooPFR8w@xxxxxxxxxxxxxx> <20110627163247.GT6978@xxxxxxxxxxxx> <BANLkTikwvCdTPoXfANbiFMsOFa1-e6AvmQ@xxxxxxxxxxxxxx> <20110627173330.GC2430@xxxxxxxxxxxx> <BANLkTinq11kUiCF-ZwC6gk7y3+dDiGAnBQ@xxxxxxxxxxxxxx> <20110627191031.GD15703@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 28 June 2011 03:10, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
>
> 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.
>

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.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>