Kernel Panic when Upgrading to 2.8.0 beta

[stewartv8]

@stephenw10 sorry i have no idea its running on a dl 360 g5 server tho if that helps i have had no problems with any updates in years this is the first one that is giving the problem

[stephenw10]

Check the bootlog in 2.7.2. If it's failing to load there too, but obviously not crashing, then you can probably just disable that device in the BIOS.

[stewartv8]

yep i see it there

[stephenw10]

Ok and it's not loading so isn't in use, you can disable it. Either in the BIOS (if you can) or using a hint as shown above:

hint.isp.0.disabled="1"

[stewartv8]

@stephenw10 will this work i blacklisted it

[stephenw10]

I would use the disabled hint. I don't think I've ever tried blacklisting something lie that. But I'd expect it to be for the driver name isp.

Reboot in 2.7.2 and it will show you.

[stewartv8]

@stephenw10 dame nope different problem now the 2400 is gone but get this

starting to think im going to be stuck on this ver for ever

[stephenw10]

And you still can't run bt?

[stewartv8]

@stephenw10 nope hard freeze no keyboard input after the error

[stephenw10]

Hmm, I guess the firmware loader has the issue then and it's triggered on a different firmware.

Can you enable a serial console and get a more complete log?

[stewartv8]

@stephenw10 no idea how i only have experience with the web interface might need some guidance

[stephenw10]

Well first the hardware have a serial port you can access?

If so you can just enable it in Sys > Adv > Admin Access initially.

Then you need to connect to it with a serial terminal client of some sort. So that might be putty running on a laptop with a some sort of USB to serial adapter.

Trivial if you've done it before but....

[stewartv8]

@stephenw10 yea i dont have any of those adopters and sounds complicated. I guess no more updates for me :(

[stephenw10]

Well I'd expect it to be possible. We just need to see more logging.

How did you disable isp0 in the end?

Did you try disabling it in the BIOS?

A good option here would be to disable any hardware not in use there.

[stewartv8]

@stephenw10 i just used the command in the web interface to disable it so it would no load on update. I used both the hint and blacklist command

[stephenw10]

Do you have the option of disabling it in the BIOS? Can you test that?

[stewartv8]

@stephenw10 i know i can disable the usb legacy in the bios no shore about the 2400 but i guess i could open it up and pull all cards not in use if any as well then try with no usb enabled ?. If i disable the usb legacy that will mean i wont be able to get back into the bios with the keyboard tho wont it?

[Spacecase]

I just ran into the same issue with the release version. Update went smoothly until it didn't. It presents the same modality and fault codes, but different addresses and hardware details.

I reverted back to 2.7.2.

[stewartv8]

@stephenw10 good news i pulled the card from the server unplugged the keyboard while updateing and all went well. Now on the latest ver thanks for ya help :)

[stephenw10]

@Spacecase said in Kernel Panic when Upgrading to 2.8.0 beta:

It presents the same modality and fault codes, but different addresses and hardware details.

Could be a very different panic then. Do you have the details? Did the console also become unresponsive?