https://bugzilla.kernel.org/show_bug.cgi?id=203431
--- Comment #6 from Adam Grigolato (adam.grigol...@balcora.net) --- So, to update, noapic doesn't allow boot. noacpi or nolapic are the only things that allow me to pass "Calibrating APIC timer..." Both result in only a single CPU detected, noacpi boots, nolapic locks up. Also after nolapic it spits a ton of "[Firmware Bug]: cpu 0, try to use APIC510 (LVT offset 1) for vector 0xf9, but the register is already in use for vector 0x0 on this cpu" and "[Firmware Bug]: cpu 0, failed to setup threshold interrupt for bank X, block 0 (MSRC0002003=0xd0100000000000000" (With X incrementing) , then finally "[Firmware Bug]: cpu 0, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu" before finally locking up after 'crytpd: max_cpu_qlen set to 1000'. As to the ACPI tables, Cleaning up the extra NMI/LAPIC's in the APIC table (via override); although cleaning up the boot messages, didn't help booting in the slightest. Sadly even with a lot of debugging enabled, I can't seem to get any kernel messages that indicate anywhere to look even. (Other than those via nolapic; I haven't seen any [Firmware Bug] messages to help :/) -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
