Hello Mike,
Do you have a more complete kernel panic screen capture?? I see
it's showing "AX.25" but there should be a full screen worth of
detail.? Regardless, there are a few known issues with modern
Linux kernels and it's AX.25 stack though nothing I'm aware with
UI packets sent from tools like beacon.? Which ax25apps /
ax25tools are you using??? The ones included from the Raspberry Pi
OS repo?? Maybe the VE7FET repo (recommended) or maybe the
Official AX.25 repo (somewhat out of date)?
If you're using the Raspberry Pi OS packages, I recommend you
remove them, build up the VE7FET ones, and see if that helps.? I
have that all documented here:
??
If that doesn't help, I have received a few proposed Ax.25 kernel
module changes that are supposed to fix a few of these known
connected-mode packet connection issues (decent description is
here:?? ) but to use
them, it requires recompiling the AX.25 kernel module.? It's not
to difficult to do once you have the setup but it has to be redone
whenever there is a new kernel released as part of the usual
patching process.
--David
KI6ZHD
On 12/26/2023 12:36 PM, Michael Dunn
wrote:
toggle quoted message
Show quoted text
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
