|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter"
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.
>
log-3.0-debugirq-dmesg
Description: Binary data
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", (continued)
- [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Liwei
- Message not available
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Liwei
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Liwei
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Liwei
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Liwei
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter",
Liwei <=
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Liwei
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Liwei
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Liwei
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Liwei
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Liwei
- Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter", Liwei
|
|
|
|
|