I have a test Raspberry Pi 4 + 64bit Bookworm setup (
6.1.0-rpi7-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24)
aarch64 GNU/Linux ) using the
Linux AX.25 stack +
VE7FET
Ax.25 libs/apps/tools + Direwolf 1.7 (with GPIO PTT) and a Syba USB
sound device but it's NOT connected to a radio to send RF traffic.?
That said, it's been running beacon for several *months* w/o any
crashes:
?? /usr/sbin/beacon -c KI6ZHD-8 -d beacon -t 60
vhfdrop KI6ZHD/k KI6ZHD-1/b SCLARA/n 44.128.0.1/ip : Linpac in
Santa Clara
One thing I notice below fJon's most recent post is that they are
using a
32bit kernel (aka amrv6l) but 64bit binaries
(Pat) where my setup is using using the 64bit kernel.? That might
be an important difference.
--David
KI6ZHD
On 01/31/2024 09:04 AM, Jon Bousselot
KK6VLO wrote:
toggle quoted message
Show quoted text
Crash club.? I think I've overpaid my dues to this
club over the years.? I like it.
I'm currently testing the rmsgw without beacon running at all, see
if I can make it past two days.? Telling the TNC to beacon should
be easy and that is next on my list.? I think the final production
deployment for our club gateway will be on an x86 system, a GMKTEK
N5105, also using a TNC.? The out the door price for that pc is
really close to all the peripherals needed to deploy a Pi, and we
have bigger plans for the system, not just RMSGW.? For other club
members who want the pi solution at their home (like myself) I
want to figure it out.
Here is my current kernel on the Pi-1.?? Linux rms-gw
6.1.0-rpi7-rpi-v6 #1 Raspbian 1:6.1.63-1+rpt1 (2023-11-24) armv6l GNU/Linux
And the kernel on the Pi-3 which has the same issue.? Linux
wa6bgs-rms 6.1.0-rpi7-rpi-v7 #1 SMP Raspbian 1:6.1.63-1+rpt1
(2023-11-24) armv7l GNU/Linux
I do have a serial console attached to the Pi-1 to catch kernel
panic messages.
Here is the string I saw from prior crashes.? I was only able to
capture some because I had journalctl -af running in a shell.? The
serial console prints this automatically.
Some crash strings from this month.
Jan 25 19:22:40 wa6bgs-rms kernel: CPU: 0 PID: 976 Comm: beacon
Tainted: G??????? WC???????? 6.1.0-rpi7-rpi-v7 #1? Raspbian
1:6.1.63-1+rpt1
Jan 26 09:06:37 wa6bgs-rms kernel: CPU: 0 PID: 988 Comm: beacon
Tainted: G???????? C???????? 6.1.0-rpi7-rpi-v7 #1? Raspbian
1:6.1.63-1+rpt1
[208158.485745] CPU: 0 PID: 850 Comm: beacon Tainted: G????????
C???????? 6.1.0-rpi7-rpi-v6 #1? Raspbian 1:6.1.63-1+rpt1
And this happened when the system was only up for 3.5 hours, and I
ran the beacon command manually.
root@rms-gw:~# beacon -c WA6BGS -d "beacon" -s radio "RMS Gate
= WA6BGS-10"
It crashed instantly.
[12716.423664] CPU: 0 PID: 1217 Comm: beacon Tainted: G????????
C???????? 6.1.0-rpi7-rpi-v6 #1? Raspbian 1:6.1.63-1+rpt1
This is when I was convinced beacon was causing the problem.?
Going back one raspbian release is possible, but not permanent.
