Kernel panics after upgrade to R1

Started by computeralex92, July 16, 2024, 08:21:29 PM

Previous topic - Next topic
just sent another crash report for 24.7.r1_7

And, yup, if the bectl with 24.1 cannot see the crash from another bectl, I have no idea why it prompted me to send the crash reports.
OPNsense HW:

Minisforum Venus series UN100C, 16 GB RAM, 512 GB SSD
T-bao N9N Pro, 16 GB RAM, 512 GB SSD

Quote from: csutcliff on July 18, 2024, 11:34:19 PM
just sent another crash report for 24.7.r1_7

Just to make sure we're on the same page here, there can be crashes in programs that you can report from the GUI, restart said program and everything else on the FW continues working normally. The OPNsense team receives the crash reports and the issue is fixed one way or another and available shortly in an update.


This thread is about kernel panics on 24.1.r1 and the OS being rebooted automatically --  of which I had none for the last few kernels I tested on 3 FWs.

Uptime on 24.7.r1_7 is now over 10 hours.




Yes there were a few PHP crash reports as well and we fixed them where we could.

It looks like the pf state unlink stuff works fine now but there's still a strange panic so we will go ahead with RC2 and I've also uploaded a debug kernel to work on the remaining panic because there's nothing that sticks out in the code about this one (ip6_input() related).


Cheers,
Franco

Installed RC2. Lobby: Dashboard is blank no info at all.

Here is a screenshot.

Other than that, all the rest is functioning properly.

I wouldn't call it blank but I also wouldn't want to start discussing this in a kernel panic thread. Thanks.

So now we're at RC2. I'm hoping someone running into the ip6_input() panic will try the associated debug kernel to be able to share a core dump.

Only use the command if you are sure about your panic:

# opnsense-update -kr dbg-24.7.r2

The debug kernel will be detected by the reboot and configure itself to produce a core dump instead of a text dump. The dump files will not submit due to their size, so putting them on a file share would be the best option for us to grab it.


Thanks,
Franco

Quote from: newsense on July 19, 2024, 07:44:31 AM
Quote from: csutcliff on July 18, 2024, 11:34:19 PM
just sent another crash report for 24.7.r1_7

Just to make sure we're on the same page here, there can be crashes in programs that you can report from the GUI, restart said program and everything else on the FW continues working normally. The OPNsense team receives the crash reports and the issue is fixed one way or another and available shortly in an update.


This thread is about kernel panics on 24.1.r1 and the OS being rebooted automatically --  of which I had none for the last few kernels I tested on 3 FWs.

Uptime on 24.7.r1_7 is now over 10 hours.

Yes I'm talking about kernel crashes where it dumps page after page of debug into the screen and reboots, I'm submitting the reports it has generated after reboot which do include kernel dump info etc. had 2 kernel crashes with _7 yesterday but none so far today.

csutcliff, you are our only hope!

You're a prime candidate for the RC2 debug kernel since you have that non-obvious ip6_input() crash.


Cheers,
Franco

Help us, Obi-Franco Kenobi  :)
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)


I have a bad feeling about this ...
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

Quote from: franco on July 19, 2024, 02:35:33 PM
csutcliff, you are our only hope!

You're a prime candidate for the RC2 debug kernel since you have that non-obvious ip6_input() crash.


Cheers,
Franco

Thank you, I wasn't sure if I was "the one" since I didn't save the output from the crashes, only submitted it to you

I'm already on the rc2 but I'll install that debug kernel now.

Thanks. Don't forget to reboot before waiting for the crash. :)


Cheers,
Franco