@george1421 You know what’s funny, as you typed your reply I had figured out your typo and I made the same mistake - inputting it as acpi… several times. Sure enough, setting noapic in the kernel argument worked like a charm. Thanks.
To humor your question though, this is running on an HP 280 G1 MT. I also found it mildly disconcerting that my searches of that specific issue came from well over a decade ago.
@george1421 - Thank you for the reply. I appreciate your input. So there was in fact a listed FOG Kernel update available. After making sure the firmware on the machine was up to date, the kernel update was run.
Unfortunately, after this was complete, we still ran into the same issue. So naturally, we set the noacpi option in the kernel args setting, but we hit the same kernel panic.
We could try a rip and rebuild, but I can’t imagine what could have gone wrong during installation. Any further thoughts?
Howdy all,
Now, this may well not have anything to do with FOG, but I’ve gotta start somewhere. FOG Installation went off without a hitch. But first the basics.
FOG Version: 1.5.9.122 - dev branch
Host OS: Debian 11
And as the title states, when attempting a Full Host Registration and Inventory. The entire error is as follows:
..MP-BIOS bug: 8254 timer not connected to IO-APIC
Kernal Panic - not syncing: IO-APIC + timer doesn't work! Boot with apic-debug and send a report. Then try booting with the 'noapic' option.
---[ end <<message repeats>>
Pretty wild. Very obviously, it gives a potential solution, but I’m unsure where/how to execute it in this scenario. If relevant, FOG is running on a bare-metal computer that has previously worked fine with FOG imaging (upgraded after Spring Cleaning).
Any thoughts?