[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter"
On Tue, Jun 28, 2011 at 12:59:04AM +0800, Liwei wrote: > 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 No. > things are working well with 2.6.32. Hmm. Can you attach the full serial log and on the Linux kernel line have 'loglevel=10 debug initcall_debug' please? 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? > > > > > 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 Yeah, that is messed up. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |