Kernal Panic when attempting Full Host Registration and Inventory

[ForCom5]

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?

[george1421]

@forcom5 The first thing I would do is upgrade the FOS Linux kernel to 5.15.x. The error is an issue between FOS Linux (the engine that does the imaging) and the hardware. So first step is to update the version of the FOS Linux kernel (FOG Web UI->FOG Configuration->Kernel update)

Also make sure the firmware is up to date on the hardware.

If there is still an error after that add the noacpi kernel parameter in the FOG settings page. Understand this is a global setting, but will help you get past registration. Once the device is registered you can set the kernel parameter field in the host definition page.

[ForCom5]

@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?

[george1421]

@forcom5 As I mentioned before this error is specifically between FOS Linux and the hardware. I would try also the kernel parameters of noapic acpi=off to see if we can skip past this issue.

For the record what mfg and model of computer is this? I haven’t seen acpi issues in a few years… OK my dyslexia is defeating me today. You have noapic that is different than noapci. Try with both of the above kernel parameters set at the same time.

ref: second post here explains what each are: https://www.linuxquestions.org/questions/linux-software-2/difference-between-noapic-and-acpi%3Doff-kernel-parameters-454675/

[ForCom5]

@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]

@forcom5 Well we typically see this with older hardware. It looks like thise 280 G1 systems have a 4 gen processor in them, so that makes me think they are on the older side. BUT if you have a working solution, run with it.