After upgrade last version fog z400 problem boot

[Quazz]

What kind of CPU is in there? Afaik this happens when the microcode isn’t loaded, so the model of the CPU is necessary information.

Alternatively, for the devs, turning off interrupt remapping would also solve this afaik.

edit: try adding pcie_aspm=off to kernel parameters in fog options.

[george1421]

Can we collect some additional hard numbers here?

What is the latest version of FOG (numbers on the cloud on the Web GUI management page)?
What version is the kernel version you are using. You can either find this in the Setup section of the FOG management gui or by navigating to /var/www/html/fog/service/ipxe and issuing the following command file bzImage

Also on the z400 please make sure you are running the latest firmware.

And one final question, does this error happen on any other target computer or only this one z400?

[Abuelika]

@george1421 @Quazz

Sorry for my brief information.

FOG SERVER : 7931

The problem occurs only with the z400

I tried the kernel Kernel - 4.5.3 Tom Elliott and I get this error when I try to make a download of an image. I went down to the 4.1.6 TomElliott kernel, and with this kernel works with z400 and z440 Z420

[Quazz]

@Abuelika Alright, so it’s definitely something to do with the kernel.

Could you try adding pcie_aspm=off to kernel parameters at FOG General settings - FOG_KERNEL_ARGS ?

[george1421]

@Quazz said in After upgrade last version fog z400 problem boot:

@Abuelika Alright, so it’s definitely something to do with the kernel.

Could you try adding pcie_aspm=off to kernel parameters at FOG General settings - FOG_KERNEL_ARGS ?

FYI: This value should be set in the host definition for this specific z400 computer that way the kernel args only apply to this computer. The above kernel arg may not be appropriate or needed for all systems.

[Abuelika]

@george1421 @Quazz

I put pcie_aspm=off in FOG_KERNEL_ARGS and I see this error:

[Quazz]

@Abuelika Going to have to wait on the devs in that case, beyond the scope of what I know I’m afraid.

[george1421]

@Abuelika Do you have another z400 to test on? This “could be” a hardware issue (failure) or a real kernel issue. The differences in the kernels could be simply a SMP version vs a uni processor version. If it can be isolated to this specific computer or this specific model.

For clarity this is the processor in this system Xeon Quad-Core model W3565

[Abuelika]

@george1421

ok. I will try another z400 to narrow the problem.

[Abuelika]

@george1421 @Quazz

Hello,

I tried it with two other z400 and have obtained the same fault.

[Sebastian Roth]

@Abuelika Can you please try booting any kind of live linux on this machine to see if this is working?

Another thing to test would be sending ICMP pings to the client while it is booting. This way you might find out if the kernel is actually freezing the machine or just kind of waiting there.

Then one more thing that comes to my mind. Please go to FOG configuration -> FOG settings -> FOG Boot Settings and enable FOG_KERNEL_DEBUG plus crank up FOG_KERNEL_LOGLEVEL to 7 to see if we can get any more information on this.

See there are people saying that they have issues with linux on a z400 machine. But this is not on boot up but while it is running the GUI already.

[Abuelika]

@Sebastian-Roth

No problem with linux live cd.

ICMP ping to client lost

I put FOG_KERNEL_LOGLEVEL to 7 and check FOG_KERNEL_DEBUG

[Quazz]

@Abuelika You might want to update the BIOS of the Z400 and see if that helps, latest BIOS dates from April this year and fixed a couple of issues with certain CPUs.

http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=3718669&swLangOid=8&swEnvOid=4059

[Abuelika]

@Quazz said in After upgrade last version fog z400 problem boot:

You might want to update the BIOS of the Z400 and see if that helps, latest BIOS dates from April this year and fixed a couple of issues with certain CPUs.

I upgrade bios to 3,60 ( last ) and the error is diferent:

[Quazz]

@Abuelika Looking a lot better already, I can’t spot an error right now, just information about its boot process. Does it stop there when you try to image? Or does something else happen/show up?

[Sebastian Roth]

Great catch with the BIOS update @Quazz! I don’t see any error on that the latest picture either! The only issue I can think of (as live CD is booting fine - by the way which one did you try?) is that we have all the drivers compiled directly into the kernel while most distros use kernel modules that are not automatically loaded on boot up. Possibly one of the modules is causing the issue. But if we don’t get any error on screen we are pretty lost with this.

[Abuelika]

@Quazz said in After upgrade last version fog z400 problem boot:

Looking a lot better already, I can’t spot an error right now, just information about its boot process. Does it stop there when you try to image? Or does something else happen/show up?

It appears kernel panic :

[Sebastian Roth]

I guess we need @Tom-Elliott to compile a kernel including the symbols. Just looking at the hex numbers won’t help us. When you have time Tom - no need to hurry.

[Abuelika]

@Sebastian-Roth said in After upgrade last version fog z400 problem boot:

I guess we need @Tom-Elliott to compile a kernel including the symbols. Just looking at the hex numbers won’t help us. When you have time Tom - no need to hurry.

Ok. No problem. Use an earlier version of bzImage works for computer models that have

[george1421]

@Abuelika One thing you can do in the mean time (as you noted) use an older kernel for this model. You can install this bzImage in the same directory fog/service/ipxe but name it bz400Image (or what ever) and then for the host definition you will have to manually register the system but you can specify the kernel name in the host configuration in the FOG web gui.