| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter"
On 28 June 2011 00:32, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
> On Mon, Jun 27, 2011 at 11:12:43PM +0800, Liwei wrote:
>>
>> Does failure of the interpreter cause anything bad to happen? Common
>
> Well yes. It can't interpret the ACPI _PRT tables so the
> interrupt routing information is not present.
>
> Which means that the drivers fall back to polling mode or end up
> using the wrong IRQs.
>
----snip----
>> Yes I do:
>>
>> [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
>> [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 20 low level)
>> [ 0.000000] ACPI: IRQ0 used by override.
>> [ 0.000000] ACPI: IRQ2 used by override.
>> [ 0.000000] ACPI: IRQ9 used by override.
>> [ 0.000000] Using ACPI (MADT) for SMP configuration information
>> ----snip----
>> [ 3.405497] Memory: 776452k/13631488k available (3239k kernel code,
>> 3146184k absent, 9708852k reserved, 3423k data, 532k init)
>> [ 3.405579] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0,
>> CPUs=8, Nodes=1
>> [ 3.405616] Preemptible hierarchical RCU implementation.
>> [ 3.405630] NR_IRQS:33024 nr_irqs:2048 16
>> [ 3.405705] xen: sci override: global_irq=20 trigger=0 polarity=1
>> [ 3.405708] xen: registering gsi 20 triggering 0 polarity 1
>> [ 3.405721] xen: --> pirq=20 -> irq=20
>> [ 3.405728] xen: acpi sci 20
>
> Whoa. 20. That is unusual, but we do set it up. Perhaps ineptly thought.
> Is there an option in the BIOS to toggle some ACPI SCI option?
Did a reboot and checked the BIOS menus. Nothing about SCI in there.
Is the SCI requirement something new in the 2.6.39+ kernels? Because
things are working well with 2.6.32.
>
> Does /proc/interrupts have this for IRQ 20:
>
> 9: 3 0 0 0 0 0
> xen-pirq-ioapic-level acpi
>
> ?
Nope, IRQ 20 or any acpi related interrupts doesn't show up:
CPU0 CPU1 CPU2 CPU3 CPU4
CPU5 CPU6 CPU7
1: 4 0 0 0 0
0 0 0 xen-pirq-ioapic-edge i8042
3: 0 0 0 0 0
0 0 0 xen-pirq-ioapic-edge mvsas
5: 0 0 0 0 0
0 0 0 xen-pirq-ioapic-edge mvsas
8: 3 0 0 0 0
0 0 0 xen-pirq-ioapic-edge rtc0
10: 0 0 0 0 0
0 0 0 xen-pirq-ioapic-edge mvsas
11: 0 0 0 0 0
0 0 0 xen-pirq-ioapic-edge mvsas
12: 6 0 0 0 0
0 0 0 xen-pirq-ioapic-edge i8042
272: 7433262 0 0 0 0
0 0 0 xen-percpu-virq timer0
273: 260592 0 0 0 0
0 0 0 xen-percpu-ipi resched0
274: 28786 0 0 0 0
0 0 0 xen-percpu-ipi callfunc0
275: 0 0 0 0 0
0 0 0 xen-percpu-virq debug0
276: 112 0 0 0 0
0 0 0 xen-percpu-ipi callfuncsingle0
277: 0 5534620 0 0 0
0 0 0 xen-percpu-virq timer1
278: 0 430137 0 0 0
0 0 0 xen-percpu-ipi resched1
279: 0 1210410 0 0 0
0 0 0 xen-percpu-ipi callfunc1
280: 0 0 0 0 0
0 0 0 xen-percpu-virq debug1
281: 0 975 0 0 0
0 0 0 xen-percpu-ipi callfuncsingle1
282: 0 0 114181 0 0
0 0 0 xen-percpu-virq timer2
283: 0 0 134749 0 0
0 0 0 xen-percpu-ipi resched2
284: 0 0 1211915 0 0
0 0 0 xen-percpu-ipi callfunc2
285: 0 0 0 0 0
0 0 0 xen-percpu-virq debug2
286: 0 0 69666 0 0
0 0 0 xen-percpu-ipi callfuncsingle2
287: 0 0 0 30680 0
0 0 0 xen-percpu-virq timer3
288: 0 0 0 10670 0
0 0 0 xen-percpu-ipi resched3
289: 0 0 0 1223807 0
0 0 0 xen-percpu-ipi callfunc3
290: 0 0 0 0 0
0 0 0 xen-percpu-virq debug3
291: 0 0 0 1141 0
0 0 0 xen-percpu-ipi callfuncsingle3
292: 0 0 0 0 21732
0 0 0 xen-percpu-virq timer4
293: 0 0 0 0 6725
0 0 0 xen-percpu-ipi resched4
294: 0 0 0 0 1223929
0 0 0 xen-percpu-ipi callfunc4
295: 0 0 0 0 0
0 0 0 xen-percpu-virq debug4
296: 0 0 0 0 3068
0 0 0 xen-percpu-ipi callfuncsingle4
297: 0 0 0 0 0
16427 0 0 xen-percpu-virq timer5
298: 0 0 0 0 0
5746 0 0 xen-percpu-ipi resched5
299: 0 0 0 0 0
1224228 0 0 xen-percpu-ipi callfunc5
300: 0 0 0 0 0
0 0 0 xen-percpu-virq debug5
301: 0 0 0 0 0
1002 0 0 xen-percpu-ipi callfuncsingle5
302: 0 0 0 0 0
0 17731 0 xen-percpu-virq timer6
303: 0 0 0 0 0
0 7430 0 xen-percpu-ipi resched6
304: 0 0 0 0 0
0 1222899 0 xen-percpu-ipi callfunc6
305: 0 0 0 0 0
0 0 0 xen-percpu-virq debug6
306: 0 0 0 0 0
0 5066 0 xen-percpu-ipi callfuncsingle6
307: 0 0 0 0 0
0 0 15633 xen-percpu-virq timer7
308: 0 0 0 0 0
0 0 5719 xen-percpu-ipi resched7
309: 0 0 0 0 0
0 0 1224195 xen-percpu-ipi callfunc7
310: 0 0 0 0 0
0 0 0 xen-percpu-virq debug7
311: 0 0 0 0 0
0 0 1522 xen-percpu-ipi callfuncsingle7
312: 2194 0 0 0 0
0 0 0 xen-dyn-event xenbus
313: 0 0 0 0 0
0 0 0 xen-percpu-virq pcpu
314: 0 0 0 0 0
0 0 0 xen-pirq-msi PCIe PME
316: 0 0 0 0 0
0 0 0 xen-pirq-msi PCIe PME
318: 325412 0 0 0 0
0 0 0 xen-pirq-msi sky2@pci:0000:0c:00.0
319: 451 0 0 0 0
0 0 0 xen-pirq-msi sky2@pci:0000:0d:00.0
320: 164703 0 0 0 0
0 0 0 xen-pirq-msi ahci
321: 1351 0 0 0 0
0 0 0 xen-dyn-event evtchn:xenstored
322: 1 0 0 0 0
0 0 0 xen-dyn-event evtchn:xenstored
323: 9 0 0 0 0
0 0 0 xen-dyn-event evtchn:xenstored
324: 1 0 0 0 0
0 0 0 xen-dyn-event evtchn:xenconsoled
325: 2417960 0 0 0 0
0 0 0 xen-dyn-event evtchn:qemu-dm
326: 1825452 0 0 0 0
0 0 0 xen-dyn-event evtchn:qemu-dm
327: 4102938 0 0 0 0
0 0 0 xen-dyn-event evtchn:qemu-dm
328: 1921778 0 0 0 0
0 0 0 xen-dyn-event evtchn:qemu-dm
329: 1556828 0 0 0 0
0 0 0 xen-dyn-event evtchn:qemu-dm
330: 1580859 0 0 0 0
0 0 0 xen-dyn-event evtchn:qemu-dm
331: 1633228 0 0 0 0
0 0 0 xen-dyn-event evtchn:qemu-dm
332: 1940019 0 0 0 0
0 0 0 xen-dyn-event evtchn:qemu-dm
333: 9 0 0 0 0
0 0 0 xen-dyn-event evtchn:xenstored
334: 1 0 0 0 0
0 0 0 xen-dyn-event evtchn:xenconsoled
335: 3718012 0 0 0 0
0 0 0 xen-dyn-event evtchn:qemu-dm
336: 3364579 0 0 0 0
0 0 0 xen-dyn-event evtchn:qemu-dm
NMI: 0 0 0 0 0
0 0 0 Non-maskable interrupts
LOC: 0 0 0 0 0
0 0 0 Local timer interrupts
SPU: 0 0 0 0 0
0 0 0 Spurious interrupts
PMI: 0 0 0 0 0
0 0 0 Performance monitoring interrupts
IWI: 0 0 0 0 0
0 0 0 IRQ work interrupts
RES: 261162 432314 134760 10685 6740
5756 7441 5732 Rescheduling interrupts
CAL: 28902 1211389 1281588 1224956 1227002
1225236 1227982 1225717 Function call interrupts
TLB: 0 0 0 0 0
0 0 0 TLB shootdowns
TRM: 0 0 0 0 0
0 0 0 Thermal event interrupts
THR: 0 0 0 0 0
0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 0
0 0 0 Machine check exceptions
MCP: 0 0 0 0 0
0 0 0 Machine check polls
ERR: 0
MIS: 0
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] "ACPI: Unable to start the ACPI Interpreter", Liwei
- [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
|
|
|
| |
|
Home