From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Re: "ACPI: Unable to start the ACPI Interpreter" Date: Mon, 27 Jun 2011 13:33:30 -0400 Message-ID: <20110627173330.GC2430@dumpdata.com> References: <20110627133936.GB6978@dumpdata.com> <20110627163247.GT6978@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Liwei Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Tue, Jun 28, 2011 at 12:59:04AM +0800, Liwei wrote: > On 28 June 2011 00:32, Konrad Rzeszutek Wilk w= rote: > > 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: > >> > >> [ =A0 =A00.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 d= fl dfl) > >> [ =A0 =A00.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 20 = low level) > >> [ =A0 =A00.000000] ACPI: IRQ0 used by override. > >> [ =A0 =A00.000000] ACPI: IRQ2 used by override. > >> [ =A0 =A00.000000] ACPI: IRQ9 used by override. > >> [ =A0 =A00.000000] Using ACPI (MADT) for SMP configuration informati= on > >> ----snip---- > >> [ =A0 =A03.405497] Memory: 776452k/13631488k available (3239k kernel= code, > >> 3146184k absent, 9708852k reserved, 3423k data, 532k init) > >> [ =A0 =A03.405579] SLUB: Genslabs=3D15, HWalign=3D64, Order=3D0-3, M= inObjects=3D0, > >> CPUs=3D8, Nodes=3D1 > >> [ =A0 =A03.405616] Preemptible hierarchical RCU implementation. > >> [ =A0 =A03.405630] NR_IRQS:33024 nr_irqs:2048 16 > >> [ =A0 =A03.405705] xen: sci override: global_irq=3D20 trigger=3D0 po= larity=3D1 > >> [ =A0 =A03.405708] xen: registering gsi 20 triggering 0 polarity 1 > >> [ =A0 =A03.405721] xen: --> pirq=3D20 -> irq=3D20 > >> [ =A0 =A03.405728] xen: acpi sci 20 > > > > Whoa. 20. That is unusual, but we do set it up. Perhaps ineptly thoug= ht. > > Is there an option in the BIOS to toggle some ACPI SCI option? >=20 > 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=3D10 debug initcall_debug' please? Is the serial log when running under 2.6.32 any different? (up to the ACP= I interpretter blowing up)? What does the /proc/interrupts look under 2.6.32? >=20 > > > > Does /proc/interrupts have this for IRQ 20: > > > > =A0 9: =A0 =A0 =A0 =A0 =A03 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00= =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0xen-pi= rq-ioapic-level =A0acpi > > > > ? >=20 > Nope, IRQ 20 or any acpi related interrupts doesn't show up: >=20 > 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.