Firmware bug: TSC_DEADLINE disable due errata with FOG 1.5.9-RC2.10

[mgep]

Hi,

I have updated fog to version 1.5.9-RC2.10
I was able to take a image correctly but now when sending it, we have this error :

Firmware Bug : TSC_DEADLINE disable due to errata: please update version : 0xb2 or later

My server is Ubuntu TSL 16.04.

Any idea why I have this problem?

Thanks !!!

[Sebastian Roth]

@mgep Can you please take a picture of the error and post that here in the forums?

[george1421]

Please also include the hardware (mfg and model) of the source image where it was take from and the hardware of where you send it to. Without a picture of the actual error we can only guess the problem is with the send to computer hardware and the FOS linux kernel.

[fabiano.matos]

@sebastian-roth
I’ve found this error with one notebook here too.

This notebook is a DATEN-DCM2B-4
http://www.daten.com.br/fotos/projetos/5/arquivos_arquivos/Manual Notebook.pdf

Maybe its a hardware/bios problem?

My server is FOG 1.5.7 running on Debian 10 (kernel 4.19.0-22-amd64). Registration, Capture and Deploy is working with other computers

On “AskUbuntu” I found this answer:

Just install intel-microcode with sudo apt-get install intel-microcode and reboot.

But this need to be installed on image running on client. How can we do this?

[Tom Elliott]

@fabiano-matos et al.

The TSC DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later)

Isn’t really an issue in the context of imaging. This is just meaning the microcode of the controller is older than what the kernel is expecting. Itself, is not an issue you should have to be worried about.

As far as your DHCP failed or we were unable to access…, that’s seeming to indicate the issue in your case is specific to not being able to get a DHCP address for some reason. This could be due to STP going alive, then down, then alive but the down period is longer than the period that FOG is trying to get the IP address. I haven’t been around very often recently, but I do recall there was a version or hold pattern that was set by the UI that could hopefully determine if this was indeed the issue.

Please see if STP is enabled on your network and maybe enable Fast STP RSTP or whatever it is called in your environment or disable STP altogether if you can.

[fabiano.matos]

@tom-elliott Thanks for your help, but I’m not sure if I understand it right.

Please see if STP is enabled on your network and maybe enable Fast STP RSTP or whatever it is called in your environment or disable STP altogether if you can.

Sorry for dumb question, but You mean this is a config to be done in my network (switchs, router, etc) or something to config in FOG server?

The weird thing is: The other hosts are working normally. They can register with server and capture and deploy images. I’m having this trouble only with model/hardware of one client machine (DATEN-DCM2B-4)

*sorry for my rust/bad english

[Tom Elliott]

@fabiano-matos I’m only giving information that I know when I don’t know all the details.

If other machines aren’t having an issue, maybe try changing the port the machine is linking up to to see if that helps.

[fabiano.matos]

@tom-elliott
There’s not port/cable issue. I’ve changed it and still with same error. I’m thinking this can be something with hardware/bios of this notebook (DATEN-DCM2B-4).

Does someone have another ideia?