Hi everyone,
I was wondering if anyone has run into kernel panic issues on Bookworm? ?About a month ago, I decided to finally upgrade my fairly reliable RPi3 on Stretch to a 8G RPi 4 running Bookworm. ?I used the RPi3 mostly for packet, an RMS station, and Pat client. ?When I say upgrade, I mean I built the new Pi from scratch, merged prior configs into new configs, etc. ?After moving everything over, I started noticing crashes every 4 - 5 days.
It took me a few crashes to figure things out. ?The usual suspects were ruled out (power, temperature, load, RAM, apt-get upgrade); I wasn't receiving any log messages indicating any type of issue. ?I also run all of my Pi's headless, so as it turns out I had to order one of those Micro HDMI cables to finally see the panic, relevant section below:
[455824.423915] Unable to handle kernel paging request at virtual address 0000100000400000
<snip>
[455824.449897] CPU: 0 PID: 5851 Comm: beacon Tainted: G ? ? ? ?WC ? ? ?6.1.0-rpi4-rpi-u8 #1 Debian 1:6.1.54-1+rpt2
[455824.451459] Hardware name: Raspberry Pi 4 Model B Rev 1.5 (DT)
[455824.453007] pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[455824.454566] рс : ax25cmp+0x14/0x60 [ax25]
[455834.456161] lr : ax25_addr_ax25dev+0x60/0xf0 [ax25]
Curious to see if anyone is having issues like this. ?My uneducated read of this is that /usr/sbin/beacon did something bad with a pointer. ?I was able to verify that PID 5851 was the "beacon" process and this is the second panic I caught which names beacon as the culprit.
My short term work around is to have Direwolf beacon for me and prevent /usr/sbin/beacon from running. ?It will take a week or two in order to know whether that work around is helpful. ?I usually prefer to use the native AX.25 tools whenever I can, but that toolset doesn't seem to be aging well.
? Thanks
? Mike
