[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] pvops acpi and xen 4 issues



> make sure it was indeed being called. I think this might have something
> to do with what Jeremy mentioned about my SCI being on 9 and not 20, but
> honestly, I haven't a clue. I have the full log if you need more.

I am attaching a debug patch that will help in troubleshooting this and
potentially fix this.

Couple of things:
 1). Turn the Enable ACPI SCI in the BIOS to Enable. 

 2). Compile your Linux kernel with the attached patch and these two options:
CONFIG_ACPI_DEBUG=y
CONFIG_ACPI_DEBUG_FUNC_TRACE=y

Do use your old .config that was triggering the failure in the first
case.

 3). Edit your kernel line to have:
debug  initcall_debug acpi.debug_level=0xffffffff acpi.debug_layer=0x2 
xen_sci=fun

 4). Boot your kernel. You should see something like this:

... snip..
[    0.000000] acpi_sci_ioapic_setup: 0 -> 9 (3, 1)
...
[    1.483956] xen_setup_pirqs: FADT.SCI: 9 ACPI.SCI:9. Using 9 IRQ,
[    1.490025] xen_setup_pirqs: SCI override: trigger: level->level,
polarity: high->high
[    1.497824] xen: registering gsi 9 triggering 0 polarity 0
[    1.503282] xen_allocate_pirq: returning irq 9 for gsi 9 
[    1.508572] xen: --> irq=9 
[    1.511254] Already setup the GSI :9

.. and then later:
[    3.058890] ACPI: Core revision 20090903
[    3.084701] acpi_early_init: FADT.SCI = 9
.. and then lots of ACPI debug stuff.


Thought in your case, the IRQ that should show up is 20 and the 'Already
setup the GSI :20' might not show up.

Please e-mail the full serial log (even if it does work).

> I used Xen 4-rc4 : xen/stable 2.6.32.9 - latest git from today.

Attachment: debug-apic-sci.patch
Description: Text document

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.