Lenovo ThinkCentre M900: kernel panic with latest fog 1.5.10.1622 version "Kernel Panic" Issue "XZ decompressor ran out of memory"

[fabritrento]

Lenovo ThinkCentre M900: kernel panic with latest fog 1.5.10.1622 version. “Kernel Panic” Issue “XZ decompressor ran out of memory”

with version 1.5.10 all works without problems.

with latest version of fog (1.5.10.1622) i get a kernel panic after iPXE:

i think that is the same bug of this thread: https://forums.fogproject.org/topic/17699/lenovo-thinkcentre-m900-kernel-panic-with-latest-fog-1-5-10-1622-version

[Tom Elliott]

@fabritrento That appears to be the correct method.

git clone https://github.com/FOGProject/fogproject.git --branch=dev-branch

Would have done the same thing (when you didn’t have the fogproject cloned.

The method you chose is correct though, and moving forward you would simply:

cd fogproject
git checkout dev-branch
git pull

To update to the latest information.

When you want to install stable you would:

cd fogproject
git checkout stable
git pull

Then follow the install instructions as normal.

Thanks!

[Tom Elliott]

@fabritrento Please try to update to the latest dev-branch and see if htis works properly

Yes I want the 32 bit stuff to work properly, but since this is likely a 64 bit machine anyway.

I am thinking this is due to the amount of memory on the machine far exceeding the amount of memory the 32 bit binaries can actually even handle. (Just my suspicions)

[fabritrento]

@Tom-Elliott sorry but i can’t test i’m in a production environment… i wait until the patch is released to stable branch

[fabritrento]

@Tom-Elliott the memory of the machine is 8GB. but with fog 1.5.10 works.

[Tom Elliott]

@fabritrento I understand you have more memory than what would typically be required, but 32 bit only allows up to 4gb of memory (generally) and for some reason, I’m postulating, that because there’s more it’s saying “no, we aren’t putting anything into memory” hence the ran out of memory issue.

That said, if you could test it would be great.

I know you’re in a production environment, but right now (as I see it) your prod environment isn’t working at all. So the “test” is what will be in the next stable release on Nov 15th. If you can test, just to validate you’re able to image again, it would be great.

If you cannot, I understand, just hoping to have more information and provide a solution for you.

Thank you!

[fabritrento]

@Tom-Elliott ok if next stable release is planned for 15 nov i can install the developement version and test the bug.
please can you give me the link to download the developement version? i cannot browse the directory in github, i cannot see where developement version is located to download it

[fabritrento]

@fabritrento i tryed to use git to download the developement version giving these commands:

git clone https://github.com/FOGProject/fogproject.git
cd fogproject
git checkout dev-branch
git pull

is correct? i never used git
doing as it i get Version: 1.5.10.1629 printed on screen when i try to install fog via installfog.sh

[Tom Elliott]

@fabritrento That appears to be the correct method.

git clone https://github.com/FOGProject/fogproject.git --branch=dev-branch

Would have done the same thing (when you didn’t have the fogproject cloned.

The method you chose is correct though, and moving forward you would simply:

cd fogproject
git checkout dev-branch
git pull

To update to the latest information.

When you want to install stable you would:

cd fogproject
git checkout stable
git pull

Then follow the install instructions as normal.

Thanks!

[fabritrento]

@Tom-Elliott said in Lenovo ThinkCentre M900: kernel panic with latest fog 1.5.10.1622 version "Kernel Panic" Issue "XZ decompressor ran out of memory":

git clone https://github.com/FOGProject/fogproject.git --branch=dev-branch

but i can update a developement installed version to a stable release via installfog.sh?

[fabritrento]

@Tom-Elliott problem solved i tested It Just now. Thankyou very much!

[Tom Elliott]

@fabritrento yes, you can interchange them though sometimes (not the case here) the biggest concern is schema updates between different versions.

In this case, dev-branch is the basis of stable, so these should be effectively interchangable.