ACPI Errors during host registration

[Alf]

Hello, I also have the same problem (Tywyn Sep 7, 2017, 1:10 PM). Not being an expert on Linux, I was able to register, reset and capture customer images, after performing a FOG upgrade (from 1.5.4 to 1.5.7) I can no longer register or capture or reset the errors that appear when I make The registration of a client pc are as they appear in the images below. Someone can help me, I already searched the Net and tried some solutions but I had no results and urgently needed a solution because it is a school and facilitated the task of maintenance / replacement of images.
O.S. - Ubuntu 18.04.3 LTS
FOG - 1.5.7
Registration PC - HP Compaq dc7800 SFF com Win 7

[Quazz]

Your images didn’t seem to upload correctly.

You could try adding the kernel argument noacpi in the FOG settings, though potentially the real culprit might not be ACPI related at all, hard to say without the images being visible.

[Alf]

@Quazz said in ACPI Errors during host registration:

kernel argument noacpi

Thanks for the answer. As I have little experience with Linux / FOG, where can I change “noacpi” on FOG server version 1.5.7 and on client pc I have to do something? I took new photos with the phone, may it be more visible now?

[Sebastian Roth]

@Alf Usually the ACPI errors don’t actually cause a halt. See them as warning more than errors. Still you can ad noacpi in the host settings as Host Kernel Arguments.

In that one picture you have rcu ... errors after the ACPI warning. Those are really causing a problem/system halt! Other users report those on other systems as well and we are not sure how those can be fixed.

If I get you right you said you have used FOG 1.5.4 before and exactly those systems showing the problems did work fine with FOG 1.5.4, right?

[Alf]

@Sebastian-Roth Thanks for the answer. As I have little experience with Linux / FOG, I can’t find the “Host Kernel Arguments” in the FOG version 1.5.7 server menus.
It is correct with FOG version 1.5.4 there was no problem, I just ran out of disk space and changed to a disk with higher storage capacity and re-installed Ubuntu and FOG.

[Sebastian Roth]

@Alf said in ACPI Errors during host registration:

Thanks for the answer. As I have little experience with Linux / FOG, I can’t find the “Host Kernel Arguments” in the FOG version 1.5.7 server menus.

This is not Linux specific. Go to the FOG web UI, edit the host settings for this particular host you get the errors on. There you find one setting called Host Kernel Arguments. In that field put noacpi, save and reboot the client to see if it makes a difference. If this host is not registered in FOG yet, then you want to manually add the host via the web UI and add the setting as mentioned. Then schedule a capture/deploy task and see if you still have the same errors when booting it up.

It is correct with FOG version 1.5.4 there was no problem, I just ran out of disk space and changed to a disk with higher storage capacity and re-installed Ubuntu and FOG.

Ok, so this is not an upgrade but a complete fresh FOG install? Just wondering if you have had some modifications (e.g. the Kernel Arguments mentioned above) on the old server that were lost when you re-installed. On the other hand I can imagine that the newer kernel coming with FOG 1.5.7 is making trouble on older systems. The HP Compaq dc7800 is from 2007! We might try downgrading the kernel on your FOG 1.5.7 system to see if that helps. But try the noacpi parameter first.

[george1421]

We had a similar message in a different thread. The OP at that time had a 486 industrial machine that was stalling issues even after I rebuilt a 486 kernel. Anyway, to the point we had to add acpi=off as a kernel parameter for that 486 to boot correctly. Once that was done it imaged correctly.

So lets try a host specific kernel parameter of acpi=off for this host.