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

[Xen-users] "IO-APIC + timer doesn't work" error when booting

Can someone tell me what I should do to debug the following issue?

I am booting the Qubes 4.0.1 installation ISO using UEFI, which boots xen. I am 
booting on this hardware 
https://www.gigabyte.com/Mini-PcBarebone/GB-BLCE-4105-rev-10#sp (it is running 
F1 version of the firmware).

When I boot from the ISO I see the following:

APIC boot state is 'xapic'
ACPI: 32/64X FACS address mismatch in FADT - 79807080/0000000000000000, using 32
IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-119
Enabling APIC mode:  Flat. Using 1 I/O APICs
mapped APIC to ffff82cfffffb000 (fee00000)
mapped IOAPIC to ffff82cfffffa000 (fec00000)
Switched to APIC driver x2apic_cluster
xstate: size: 0x440 and states: 0x1b
Using scheduler: SMP Credit Scheduler (credit)
Platform timer is 19.200MHz HPET
Detected 1497.650 MHz processor.
Initing memory sharing.
CPU0: Noirq handler for vector 7c (IRQ -2147483648, LAPIC)
Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB
Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB
Intel VT-d Snoop Control not enabled.
Intel VT-d Dom0 DMA Passthrough not enabled.
Intel VT-d Queued Invalidation enabled.
Intel VT-d Interrupt Remapping enabled.
Intel VT-d Posted Interrupt not enabled.
Intel VT-d Shared EPT tables enabled.
I/O  virtualisation enabled
- Dom0 mode: Relaxed
Interrupt remapping enabled
Getting VERSION: 1060014
Getting VERSION: 1060014
Enabled directed EOI with ioapic_ack_old on!
Getting ID: 0
Getting LVT0: 700
Getting LVT1: 400
Suppress EOI broadcast on CPU#0
enabled ExtINT on CPU#0
-> Using old ACK method
..MP-BIOS bug: 8254 timer not connected to IO-APIC
CPU0: No irq handler for vector e7 (IRQ -8)
IRQ7 a=0001[0001,0000] v=60[ffffffff] t=IO-APIC-edge s=00000002
failed :(.

Panic on CPU 0:
IO-APIC + timer doesn't work! Boot with apic_verbosity=debug and send a report. 
Then try booting with the 'noapic' option


When I add the `noapic` option to the options I see the following:

APIC boot state is 'xapic'
ACPI: 32/64X FACS address mismatch in FADT - 79807080/0000000000000000, using 32
Found and enabled local APIC!
mapped APIC to ffff82cfffffb000 (fee00000)
Switched to APIC driver x2apic_cluster.

Following this line is a crash dump of the CPU registers and Xen stack trace. 
Additionally, it prints the Xen call trace:
init_bsp_APIC, init_IRQ, __start_xen

and the panic message is
Panic on CPU 0:

I omitted the stack trace and register contents since I'm manually transcribing 
the logs from my monitor onto another computer.

What should be my next steps toward resolving this problem? My firmware does 
not support legacy boot, is it possible that booting via UEFI instead of legacy 
boot causes this problem? Is this likely a problem with the firmware? Should I 
contact gigabyte about an update?

Thank you for any help you can provide.

Xen-users mailing list



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