Kernel Panic when Upgrading to 2.8.0 beta

CCNewb

@patient0 thanks! I will try one night this week and report back

stephenw10

Or physically remove the wifi device? Disabling it in the BIOS doesn't seem to be working as it should. A jumper maybe?

But it also might be something else, the panic string there is unhelpful. Try running bt at the db> prompt there and see what the backtrace is. That should where it's panicking.

CCNewb

@patient0 Dude, you rock!!! That totally fixed the issue. 2.8.0 upgrade went super smooth after adding that /boot/loader.conf.local file

Thanks man

CCNewb

@stephenw10 thank you, didn't know about bt, patient0's tip about disabling the hardware via the loader.conf.local file did the trick. I was able to upgrade, it went super fast.

CCNewb

The crashes on 2.8.0 only got worse. Typical state level espionage, I hate the attention. No crash data, no console messages, nothing, just compete system lock. Every single day on 2.8.0 it’s locking up. Replaced the riser card and 10g nic the other day. Didn’t help. Just ordered another replacement mobo and newer CPU, thus completing replacing every single piece of hardware.

patient0

@CCNewb

No crash data, no console messages, nothing, just compete system lock

It's frustrating, I understand.
Have you done the classic, memory testing for a few hours? pfSense is default configured to create core dump and for me it's rare to have no logs or core dumps at all.

If your setup allows, switching to another router OS (temporarily, OS: Untangle, VyOS, OPNsense) would be an option to see if other OS run into the same issue. Boot/Install from another disk and run it for a few days.

stephenw10

How locked is locked? Does the caps lock button still work on an attached keyboard for example?

A hard lock with no output is almost always hardware though.

stewartv8

I have the same problem but i have no wifi boards in the server and no usb devices attached apart from a keyboard
alt text

can anyone help me!

stephenw10

Run bt at the db> prompt there to see the backtrace from the panic.

Though it looks like a problem with the firmware for the isp_2400 device.
Are you actually using that? If not I'd remove or disable it.

stewartv8

@stephenw10 hi thanks for the reply i can't use bt as its frozen and no key inputs work also i have no idea what that device even is as there is nothing plugged into the server apart from the usb keyboard.

stephenw10

On-board fibrechannel adapter I'd guess.

I assume the keyboard works before that? Capslock LED still work after the crash?

stewartv8

@stephenw10 yes the keyboard works right up to to the error then freezes and i have to hard reset im now back on ver 2.7.2 witch works fine.

stephenw10

Do you see the isp_2400 device in 2.7.2? Are you using it to boot from? A SCSI disk?

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.