Kernel Panic
-
@george1421 didnt solve. Do I need to have specific files in server for it to work ?
-
@ricardomartins said in Kernel Panic:
my fog version needs a newer TomElliot ?
You can use the FOG Configuration->Kernel update function inside the FOG UI to do the kernel update. Version 1.3.x was a bit quirky with the kernel updates, plus with that version of FOG I wanted you to load that specific kernel version not knowing if the latest kernel would break FOG 1.3.x. With 1.5.9RC2 you can upgrade to the latest version in the 4.19.x series. The developers just released a 5.6.18 version of the kernel to address an issue with the very latest hardware, but 5.6.18 has not been fully tested yet with FOG. It should work and work well, it just doesn’t have the testing completed that went into the 4.19.x series of linux kernels to date.
-
@ricardomartins said in Kernel Panic:
didnt solve. Do I need to have specific files in server for it to work ?
Well over time it appears that the linux kernel is having an issue with those specific computers. In other cases disabling acpi resolved the issue. Other times we had the FOG Admins make sure the bios was updated on these computers.
For testing go to the URL that I provided before with the kernels. Download 4.15.2 that was listed in the ref post. You only need the 64 bit version for this test. Rename the 64 bit version to bzImage4152 and move that file to /var/www/html/fog/service/ipxe directory. Make sure the case is correct. In this test we will NOT overwrite the existing kernel for FOG 1.5.9RC2. Now go back into the host settings where you manually defined this host. Set the “Host Kernel” field to
bzImage4152leave the “Host Kernel Arguments” withnoapci=1and then try to pxe boot this computer. -
@george1421 I followed everything you said but it is still trying to kill himself.
Very similar error but a little bit different
-
@ricardomartins Are you sure you saw that bzImage4152 was transferred to the target computer, it would be just after boot.php is called then it should transfer bzImage4152 and then init.xz to the target computer.
Back on the kernel parameters lets try this one
acpi=offinstead ofnoacpi=1They “should” do the same thing.Also is this hardware at the latest bios version supported by the hardware?
-
Hello @george1421 !
I updated the bios version from 1.53 to 1.60 (newer version in HP website) and tried to run the deply again with
acpi=off.
It give the exact same error and I confirmed that it uses bzImage4152
-
Maybe is missing something in my host config
-
@ricardomartins So in this case you are not getting the kernel panic, its just not starting linux? Your host configuration looks good.
-
@george1421 after loading correctly the bzImage 4152 and init.xz it goes to the error again (kernel panic error )
-
A nickle (may be helpful)
https://stackoverflow.com/questions/50115956/kernel-panic-not-syncingattempted-to-kill-initSomething wicked is happening to your init image. Mb try to replace it?
-
@ricardomartins Does it do this on all DCS5800 models or just this single computer. If its just this single computer there may be a hardware issue with this computer like a bad RAM chip. I don’t understand why the acpi off is not fixing the issue because others have reported it works.
-
@Single said in Kernel Panic:
A nickle (may be helpful)
I don’t think that one fits here since we are not doing nfs at this time. What we really need to see is the actual error that happened just before the stack dump that we see on the screen. Possibly if you can get a slow mode video of the kernel booting process we can see what the actual error message is. I’m not sure what we can do about it because its in the linux kernel but it might give us an idea where to look.
