On Monday, March 25, 2019 at 3:41:08 AM UTC+1, thengu wrote:
> Hi,
> 
> I'd appreciate it if someone can help me debug an issue with the qubes 
> installer. I am not able to enable legacy booting on my bios, so I am only 
> booting the installation ISO using UEFI. My hardware is 
> https://www.gigabyte.com/Mini-PcBarebone/GB-BLCE-4105-rev-10#sp, and 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
> 
> ENABLING IO_APIC IRQs
> 
> -> 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=... portion of BOOTX64.cfg 
> (under [qubes-verbose] heading), and also add the `noapic` option to the 
> kernel command line, 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:
> 
> GENERAL PROTECTION FAULT
> 
> [error_code=0000]
> 
> ****************************
> 
> ------------
> 
> 
> 
> I ommitted the stack trace and register contents since I'm manually 
> transcribing the logs from my monitor onto another computer.
> 
> 
> 
> I also tried booting with the "noexitboot=1" and "mapbs=1" lines commented, 
> which didn't help.
> 
> 
> 
> Finally, I tried various combinations of adding more xen options to the 
> "options=..." line:
> 
> - nolapic=true
> 
> - nosmp=true
> 
> - x2apic=false
> 
> - apci=false
> 
> 
> 
> Booting with all of those options together didn't help, but I only tried a 
> couple random combinations of booting with less than all of them together.
> 
> 
> 
> Does anyone have any suggestions? At some point I might try updating the 
> motherboard firmware, but I'm not sure if that would help with this kind of 
> issue...
> 
> 
> 
> The one benefit of updating the firmware is that it may allow me to boot in 
> legacy mode, which could possibly yield a different result? I'm not sure if 
> the boot mode has anything to do with this APIC stuff...
> 
> 
> 
> Thank you

i assume the right format is ' noapic nolapic smp=off x2apic=off? acpi=off ' 
etc. << and not true or false.

greetings

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a2783616-5cac-4eaf-a1b9-9e39d81b5689%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to