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 05:09:55 +0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 27 Jun 2011 14:12:02 -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=7icntLfACmypuZshbk3Q5xwqv669dbH1mVe8i439KkI=; b=wqho3QwlO76PK6yqmVFFe0YVaK5nz8q1ILnLObU/TMfZ4DuqkBBw4IqP4kLK6+wSp6 WE1xAlouKR3rAP9da2gNPXBClpI4MZXOA30JgDVHxh3JODslNH87H5a/2h5cX1vbI72K G/ItTmG7Fcfr0Py7HXcv0FTh2kn+MGbnkWJIw=
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=cTVHdB5Ny93yD+z5uOR1FCmf7/ACjVP1LpPi+YChBPArJsnxREc0TiuOm9fSNGkxIT NsrNtWC5q77o6nRNX5U1JL1IRN3jzE8DCwaJTLKk94uxa0eLDBgkMNhJ/dx7eqLvFwWv e9aFTlMS+FD3zSN57efIu5PnEC3+WDZdrnBnk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BANLkTi=u-W4K-WDV0czNChqJnpXMKEA7Ng@xxxxxxxxxxxxxx>
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> <BANLkTim7suw8ZU5xUkCD6AzJBCWJUN_9mw@xxxxxxxxxxxxxx> <20110627193051.GA14665@xxxxxxxxxxxx> <BANLkTi=u-W4K-WDV0czNChqJnpXMKEA7Ng@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hmm, here's the mapped IRQ list, interestingly IRQ 20 is on the list but not 9?

[    3.611820] acpi_get_override_irq:
[    3.611821] find_irq_entry:
[    3.611823] apic: 0 pin: 9 type: 0 mpc_ioapic_id: 8 MP_APIC_ALL: 255
[    3.611825] i: 0 irqtype: 0 dstapic: 8 dstirq: 2
[    3.611827] i: 1 irqtype: 0 dstapic: 8 dstirq: 20
[    3.611829] i: 2 irqtype: 0 dstapic: 8 dstirq: 1
[    3.611831] i: 3 irqtype: 0 dstapic: 8 dstirq: 3
[    3.611833] i: 4 irqtype: 0 dstapic: 8 dstirq: 4
[    3.611835] i: 5 irqtype: 0 dstapic: 8 dstirq: 5
[    3.611836] i: 6 irqtype: 0 dstapic: 8 dstirq: 6
[    3.611838] i: 7 irqtype: 0 dstapic: 8 dstirq: 7
[    3.611840] i: 8 irqtype: 0 dstapic: 8 dstirq: 8
[    3.611842] i: 9 irqtype: 0 dstapic: 8 dstirq: 10
[    3.611844] i: 10 irqtype: 0 dstapic: 8 dstirq: 11
[    3.611846] i: 11 irqtype: 0 dstapic: 8 dstirq: 12
[    3.611848] i: 12 irqtype: 0 dstapic: 8 dstirq: 13
[    3.611850] i: 13 irqtype: 0 dstapic: 8 dstirq: 14
[    3.611852] i: 14 irqtype: 0 dstapic: 8 dstirq: 15
[    3.611853] idx = -1 < 0, returning -1

On 28 June 2011 04:32, Liwei <xieliwei@xxxxxxxxx> wrote:
> Sorry this took a while. Somehow make decided to recompile everything.
>
> Seems like the reason for IRQ 9 not being remapped is idx = -1.
>
> On 28 June 2011 03:30, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
>> On Tue, Jun 28, 2011 at 03:18:21AM +0800, Liwei wrote:
>>> 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.
>>
>> Just splash some printk's around there and print out the values of gsi and 
>> pins.
>> Nothing fancy.
>>
>

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

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